yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
You have no idea how many messages, replies, emails, PM's I get per hour... I only have two eyes =( What did you ask before?
[Samsung Galaxy Nexus] Exostenza:
I was wondering if your kernel flashing app clears the cache and the dalvik when it flashes a kernel. If it does I will buy it to support you as I like your work and if it does not then it would make the app useless for me as I would have to flash it in CWM recovery my self anyways to clear the cache and the dalvik.

I have always cleared those when flashing a new kernel and I have always had much less problems than the general population so I continue to do it.
[Samsung Galaxy Nexus] drawde40599:
Can you post picture of screen on time?
[Samsung Galaxy Nexus] bendirkss:
Maybe the same thing as me. Buy your app via PayPal without androidpit cause it makes me pay a min of $5
[Samsung Galaxy Nexus] insanemal:
Just crack open the kernel zip.

#!/system/bin/sh
# clean modules
rm -f /system/modules/*

# clean init.d scripts
INITD_DIR=/system/etc/init.d

# franco.Kernel / updater app scripts
rm -f $INITD_DIR/13overclock
rm -f $INITD_DIR/00turtle

# wipe Dalvik-cache
rm -rf /data/dalvik-cache
rm -rf /cache/dalvik-cache

There is your answer.
[Samsung Galaxy Nexus] sishgupta:
Well I'm stable at 1650 but unfortunately I get throttled for running too hot.

My epeen isn't as large as I'd hoped so I guess I'll just have to keep it in my pants :)
[Samsung Galaxy Nexus] ArmanUV:
@franco, can I ask what you did to make 1.65 work for most people? I remember people had problems with 1.5ghz on 17.2?

Isn't it the same method GlaDOS 1.14 uses? (According to ezekeel changelogs: "Override factory-set limitations for the MPU greatly increasing the OC potential.")
[Samsung Galaxy Nexus] nikulogical:
1.65 runs fine, no lag or reboots but horrible benchmarks. with 1200 my benchmarks are amazing. don't see a point in OC right now.
[Samsung Galaxy Nexus] Thracks:
Checked on Twitter, and yes: https://twitter.com/#!/franciscof_1990/statuses/172160381937123328
[Samsung Galaxy Nexus] JTECJ:
Obviously it does and its worth it even if it didn't, it gives tons of great tools and options as well as a quick way to download the newest kernel and monitor the complete change log without dealing with the xda app or a computer.

Not Useless especially for such an insignificant price that goes to someone that offers development that you like.
[Samsung Galaxy Nexus] bendirkss:
So I assume there's no way to buy the app other than the market?
[Samsung Galaxy Nexus] yyz71:
Thank you :)
[Samsung Galaxy Nexus] franciscofranco:
insanemal answered your question =)

Why $5? The app only costs 1,46€. Theres no way to sell the app via PayPal because I can't manage updates like that :/
[Samsung Galaxy Nexus] drawde40599:
Huh? So 1200 is faster on ur phone because an app says so? 1500-1650 on my phone is flying don't care what a benchmark says!! Ur phone must be broken if u can't feel the difference
[Samsung Galaxy Nexus] nikulogical:
I really don't feel a huge difference between 1200 and 1650 when using my phone. 1200 is pretty much flawless already and performs/runs everything I throw at it with minimal to no lag. Whatever speed boost I'm getting with 1650 isn't great enough for me to reduce battery life for (I'm assuming) and 1650 runs fairly hot.. so I'm pretty sure its being throttled.
[Samsung Galaxy Nexus] drawde40599:
volume

@Franco, did u tweak the volumes? Phone volumes seem louder?

---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------

I've been on 1650 since he uploaded it and haven't reached temp over 106°f same as 1200 setting for my phone guess u could call that hot but both my Gs2 's and my skyrocket run same temp after 30 - min internet use so its my normal . 1650 is soooooo noticeably faster its crazy . I can understand battery part tho its sucking juice like crazy , I'm sure when I'm done playing I'll be back to 1350. Myself .
[Samsung Galaxy Nexus] minooch:
You don't look back very far do you!

http://xdaforums.com/showpost.php?p=22808168&postcount=6902
[Samsung Galaxy Nexus] EsPeHil:
1.65GHz no problem. Thermal throttling kicks in very fast though...:D

Any chance for bigger frequencies? ;)
[Samsung Galaxy Nexus] bendirkss:
Idk. Makes me top up my androidpit account with $5. Now I have to wait 5 days for the bank process to go through. So bloody annoying.
[Samsung Galaxy Nexus] Jimmy Flip:
You can 'adb push' another kernel to your phone while in recovery and flash it. While still in recovery, format cache and wipe davlik-cache (franco's kernel packages will wipe davik-cache for you so no need if you're flashing one of his).

If you're still having issues, you can 'fastboot erase boot' in bootloader and then immediately flash a kernel and clear caches in recovery. Or if you want to go back to stock and start again, you could flash the boot.img from the Google factory image ('fastboot flash boot boot.img') or use the reset kernel.
[Samsung Galaxy Nexus] joelteixeira:
Zenonia 4 don't seem to like the great Francisco's work. Since release (on franco #16) I'm trying to get back to franco.kernel but even on @1.650 it lags a lot.

Using morfic or faux123 it runs smoothly even on @1.200. Maybe a bad programming on game since the overall system seems very smooth on franco.kernel.

Anyone here tried Zenonia 4?

Thanks.
[Samsung Galaxy Nexus] nklenchik:
Franco you've done it again on this one...1.65 isn't buttery smooth, it's I can't believe it's not butter smooth
[Samsung Galaxy Nexus] sishgupta:
This is exactly correct actually. Many galaxy nexus phones will throttle at these speeds due to the temperature increase.
[Samsung Galaxy Nexus] EsPeHil:
Indeed. Try running consecutive benchmark tests (@1.65) and you'll see how the score drops. That's called thermal throttling.
[Samsung Galaxy Nexus] nklenchik:
Everything was going so well...had a freeze and a reboot on 1.65 ghz haha pushing it down a bit
[Samsung Galaxy Nexus] MasK:
Awesome.. I'm running at 1.65Ghz as well without problems. I'm also curious as some fellas.. whats in this that makes it work as mine failed at 1.5Ghz on Glados kernel. Is there anything I can do to stress the device more to test stability? Continuous quadrant benchmarking?

@Franco Thanks for whatever ya did so far. I would propose if you can rename the zip file before uploading into your FTP so we're sure of downloading the right one :)
[Samsung Galaxy Nexus] Kurokikaze:
Yep this did it. Thanks for the suggestion.
[Samsung Galaxy Nexus] THE_KINGDOM:
Can I just confirm what apply on boot means for CPU frequencies.

Thanks
[Samsung Galaxy Nexus] gsxraddict:
It means the frequency you set will be applied at boot instead of reverting to default speeds.
[Samsung Galaxy Nexus] THE_KINGDOM:
OK thanks but if I change the frequency then and there while phone is on it will be adjusted right away, correct?
[Samsung Galaxy Nexus] momomok:
Got a SOD on 18.2, right after a phone call...

No log is available... reverting back to 17.2 for this moment...
[Samsung Galaxy Nexus] AzzaD:
yep noticed the same thing too, really good that it is louder - just not sure if its the kernel or the AOKP rom, though I haven't read it in either changelog
[Samsung Galaxy Nexus] nklenchik:
Anyone not getting deep sleep on 18.2?

I'm running 1500/700 ondemand

Edit: Fixed itself after a reboot
[Samsung Galaxy Nexus] iankellogg:
Undervolting is not working on 18.2. I haven't used this kernel for a while so i don't know what that started happening. I can set all my voltages to 600mv with no crash...
[Samsung Galaxy Nexus] drawde40599:
Don't understand ur reply? U get back running ?
[Samsung Galaxy Nexus] Dylerium:
Addicted, but im not having any problems with it so far, i have occasionally lag moments but nothing to bad, how long does it lag for?
[Samsung Galaxy Nexus] drawde40599:
Ya no I'm way happy its louder!!! Love it, I think volume is built into controlled by kernel?
[Samsung Galaxy Nexus] chiensibut:
why min is so high 700mhz?? isn't it better at 400mhz... can someone explain because i dont get the point
[Samsung Galaxy Nexus] hosmsdos:
Franco build 18 is laggy in games, if you want to confirm this. Open Quadrant on build 18 and 17 and see the difference in 3d tests, in 18 it’s dropping from 59 fps to 15 fps. In build 17 there are no sudden drops in fps
[Samsung Galaxy Nexus] bendirkss:
Don't like these new colors on 18.2.
[Samsung Galaxy Nexus] drawde40599:
600 huh? That's pretty amazing
[Samsung Galaxy Nexus] ChongoDroid:
I can't believe 1.65 is completely stable for me. This is incredible. You sir, are a genius.
[Samsung Galaxy Nexus] drawde40599:
There is no 400, u can read about 700 on first page take a look

---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------

Finally found an issue =O,very serious lag while on phone with charger connected making almost unusable 18.2 -700/1200 on demand, no hot plug, no UV . Normal? Off charger its flawless at any and all settings phone temp 115°F ( kinda normal for my phone while on internet )
[Samsung Galaxy Nexus] Thracks:
So change them.

---------- Post added at 01:28 AM ---------- Previous post was at 01:26 AM ----------

You must not have run the GLaDOS kernel since its developer (Ezekeel) discovered the MPLL trim CPU register that hard-codes CPU frequency at 1.2GHz +/- about 15%, and how to disable it. Since then, his kernel is stable up to 1.65GHz, and so is Franco's, as they've been sharing code.
[Samsung Galaxy Nexus] gsxraddict:
Yes sir only time it will revert is a reboot unless you have set on boot checked.
[Samsung Galaxy Nexus] mklass:
Wow no need for the hostility dude.. i dont know how to provide the dmseg or logcat but ill have a look now
[Samsung Galaxy Nexus] joackie27:
I've been rocking this kernel since this morning. I have the following UV and it's working good for me. Haven't experienced any FC's yet. Looks like I have a good chip! :D

1400 @ 1200

1200 @ 1100

920 @ 1000

700 @ 900

350 @ 800
[Samsung Galaxy Nexus] The Gingerbread Man:
Look many speeds there are here. This is borrowed from doomlords op and screeny from xda app lol
[Samsung Galaxy Nexus] beekay201:
No FC here, as you can see from the picture... taken just now, also just flashed 12/12 rls (just got home). try to clear app data.

hey ock, my phone's been sleeping pretty well too.

this was right after i woke up today. :D i was pleased.

so, feedback on 12/12.

i can almost tell for sure that the kernel has issues with low power mode+cwm. booted fine nevertheless. turn on wifi... wait, where's my power widget? gone. no big deal, add it again. setcpu, apply UV profile, lockup followed by reboot. okay... clear setcpu data, reset previous UV, all good. pushed 350mhz UV to 850mv, stress test for 3 mins. good. save. :D

no flickering yet.
[Samsung Galaxy Nexus] franciscofranco:
Sorry I didn't meant to be hostile, its my way to talk, no offense intended ;)

Btw in this release I forgot to include the IO init.d file, I'll add it again in the next update -.-
[Samsung Galaxy Nexus] The Gingerbread Man:
These settings seem to be good for me so far

No deep sleep as I'm charging up battery currently. Trying to add screeny but xda a is playing up.
[Samsung Galaxy Nexus] beekay201:
we are some lucky bastards :D although i don't think i can go lower than 1100 at 1.2ghz.
[Samsung Galaxy Nexus] The Gingerbread Man:
Say that when your feeling brave enough to turn on set on boot :D currently I'm not that brave and need much more time to test these settings and I'm charging up which I expect my make results differ than as if I was to not be charging up
[Samsung Galaxy Nexus] beekay201:
Me neither :D you think I'm crazy? I just bought this like, 2 weeks ago, not on a contract! ;)

Hmm, I may have to agree with you on that charging could influence testing, I'm not taking any risks. but.. normally, it locks up right after you set it too low. at least for me it does.
[Samsung Galaxy Nexus] joackie27:
I have it set on boot (SetCPU). I just did a reboot and it's fine. :D
[Samsung Galaxy Nexus] beekay201:
We'll follow pretty soon, I would hope. But, with changing kernel versions often, not sure if I will. Sure there's ways to recover from it, but still.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just checking you guys know about this. You may need it one day in case you make bad settings choices. Should get you out of a tight spot if needed
[Samsung Galaxy Nexus] beekay201:
That's a nice cheat. Thanks for sharing with us, mate.
[Samsung Galaxy Nexus] The Gingerbread Man:
Its like a condom, better have it and not need it than to need and not have ;)
[Samsung Galaxy Nexus] joackie27:
Can't agree more! :D Thanks again!
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco, I know I'm on a version a few days old here but I don't think set CPU is stopping me from going to 1.4ghz properly if you look at m screen shots. I'm on ARHD 1.3.2 and as you can see if set Max speed at 1.2ghz. Everything is smooth and not stuttering like it was trying to use 1.4ghz in the past, I don't know if the phone is entering 1.4 ghz or the graphs and charts are lying to me lol First few cycles of boot animation are kind of laggy but other wise all is going very well, intact I might just update to latest version now.
[Samsung Galaxy Nexus] franciscofranco:
Try this latest version and get back to me, its easier to compare because I changed few ****s.
[Samsung Galaxy Nexus] The Gingerbread Man:
Still seems to look like its going into 1.4ghz but if it is the system is running very smoothly and not lagging like on previous versions so looks like the general smoothness at over clock is fixed. Boot animation still sometimes lags a little and only a very little bit at points.

See what you make of the screenies.

Also if I turn set CPU to 1.4 ghz then the slight lags in changing home screens or app drawer seem to return, again this has improved but to me leaving set CPU at 1.2 ghz gives better smoothness and looks like it uses 1.4 ghz a little bit here and there.
[Samsung Galaxy Nexus] dwang:
yeah I just recently noticed that as well. I thought maybe it was the cheap plastic cover, but I removed that and I can still hear that.

EDIT: Disable touch sounds in the Sound Settings menu and that should fix the clicking.

EDIT2: Nope still have the faint clicking. Easy to reproduce. Go into twitter app and pull down to refresh. Do it a couple of times and you can hear the faint click. If it doesn't work the first time, exit twitter and come back in and pull to refresh. Not seeing anything out of the ordinary from logcat.

Looks like its also happening with stock kernel. Its been reported to google.

http://code.google.com/p/android/issues/detail?id=22307
[Samsung Galaxy Nexus] franciscofranco:
Two new testing builds are up on my FTP. They are mainly to test jRCU as I need users feedback.

Joe's tiny single-cpu RCU, for small SMP systems.

+ *

+ * Running RCU end-of-batch operations from a single cpu relieves the

+ * other CPUs from this periodic responsibility. This will eventually

+ * be important for those realtime applications requiring full use of

+ * dedicated cpus. JRCU is also a lockless implementation, currently,

+ * although some anticipated features will eventually require a per

+ * cpu rcu_lock along some minimal-contention paths.

+*
[Samsung Galaxy Nexus] Exostenza:
Thank you!

So it wiped dalvik, but not cache. Franco can you make it wipe cache as well? I know this had adverted problems for me in the past and might be good for you to have as a process to keep away some unneeded bugs/glitches.
[Samsung Galaxy Nexus] goldleader:
Getting awesome battery life on 18.1, Thanx Franco, u da man!!! :D

ROM: aokp ms2

Radio: KL1
[Samsung Galaxy Nexus] pearse:
Can't agree there, this is the best my display has ever looked!
[Samsung Galaxy Nexus] nklenchik:
It was too blue for my taste
[Samsung Galaxy Nexus] Exostenza:
Well I bought the kernel updater to show my support. It would be nice if it cleared the cache as well as the dalvik. Looking forward to more awesome kernel support by Franco! Thanks for all of your hard work.
[Samsung Galaxy Nexus] Shetlander:
Does this mean that in Franco's kernel he is overclocking the MPU like in Glados?
[Samsung Galaxy Nexus] EddieN:
I have to say my phone works better than it ever has before since 13.1 with the ondemand governor.

Thanks again for your work franco!
[Samsung Galaxy Nexus] refaa:
What happening to the governors???

I got only 3 the gazeel and the other one

is fine?????
[Samsung Galaxy Nexus] refaa:
Turtule is gone
[Samsung Galaxy Nexus] aquavalanche:
for a moment, franco delete it to optimize it better.. use ondemand if you prefer medium speed i guess..
[Samsung Galaxy Nexus] 3c:
CPU @ 1.65, any throttling?

I'm testing #18.2 with 1.65GHz, and it's very stable, though I noticed the Antutu benchmark results are much lower than on 1.35GHz! ~5800 instead of ~7000!

Then I monitored the CPU frequency and temperature (with System Tuner) to realize the CPU was throttling frequency back to 1.2Ghz when temperature raises above 60°C!

Does anyone knows where to find the temperature throttling values and how to change them?
[Samsung Galaxy Nexus] CaspaTheGhost:
Had an overnight SOD on 18.1... Phone was on charge, I awoke to a flashing light but the GN stayed asleep!

I'll be giving 18.2 a go then...

Cheers Franco...
[Samsung Galaxy Nexus] da blitz:
Please ad gpu overclock in francokernel app
[Samsung Galaxy Nexus] Niksko:
Please don't ask for this. It's been explained multiple times why this is not in the kernel.

Check the first post.
[Samsung Galaxy Nexus] ~coolphoenix~:
you should apply this patch to close a root exploit by /proc/<pid>/mem:

https://git.kernel.org/?p=linux/ker...ff&h=e268337dfe26dfc7efd422a804dbb27977a3cccc

I looked at your kernel sources and see the patch is not applied. I'm not sure whether your kernel config disables mem-access, but since on my phone I have /proc/<pid>/mem files, I assume it is vulnerable. If it's not, you should state this in the op (and also why).

See https://github.com/saurik/mempodroid for a program trying to exploit this vuln. (didn't test it though).
[Samsung Galaxy Nexus] dostimexist:
Same Here. I'm on Faux'es kernel with stock gpu, and cpu now on 1066mhz and its runs without any lag.

I Love the franko kernel but for some reason it does not like this game :(

tried different governors no change in the gameplay all lag.

This is still my favorite kernel smoothness and battery life wise.
[Samsung Galaxy Nexus] zenzip:
testing this new kernel on my AOKP build 25, coming from Trinity....

can you suggest me best configuration and settings for this kernel with AOKP ROm? min/max freq, governor and UV settings please :D

Thanks
[Samsung Galaxy Nexus] joelteixeira:
Most of the time when using some skill or running. It's not impossible to play, but, like I said, it's not smooth as it should. I tried aokp and cm7 with the same results. :-\
[Samsung Galaxy Nexus] ChongoDroid:
Flash the latest and keep it at stock speeds. 700mhz min and 1350mhz max seems fast and good battery life. However 1000 mhz max is still quick
[Samsung Galaxy Nexus] zenzip:
what governor you use? no undervolt ? Thanks :D
[Samsung Galaxy Nexus] minipaolo:
SOD overnight.

I'm on 18.2 stock 700-1200 ondemand, no UV.

Strange that never happened with 18 and 18.1 (same settings)

I know it's weird, but I find this much worse than 17.2 when it comes to battery life.

I had no issues at all with 17.x and francoturtle set at 350-1000.
[Samsung Galaxy Nexus] Niksko:
I'm using ondemand, but I was loving francoTurtle, so look out for that when it's added back in.

As for voltages, I'm experimenting with some undervolting. I can tell you that my device can tolerate ~200mV below the stock voltages without locking or acting strange.

I'm in the process of testing some undervolting right now. I'll post back with my voltages when I'm done.

--------------------------------------------------------------------

I'm getting this too, but I think it might be to do with the governor. I'm given to understand that francoturtle is more conservative than ondemand.

--------------------------------------------------------------------

On a related topic, I'm using an overlay to tell me what cpu state I'm in in order to test undervolts. The issue is with transitions between states, so I want to make sure that the state I'm undervolting is actually being passed through before I declare it stable(ish) and move on to a lower voltage.

My question is, if my cpu state jumps from 350Mhz to 1200Mhz, does it necessarily go through 700Mhz and 1000Mhz, or can it just jump straight to 1200Mhz? Does it depend on the governor? (I'm assuming yes) Which governors will pass through all intermediate states? (as this will allow me to better test transitions between states) Am I completely off the mark and asking irrelevent questions to my goal, which is getting a stable undervolt?
[Samsung Galaxy Nexus] zenzip:
thanks for suggest...last questione after flashing I see strange color on my screen...all is most "blue/cyan" ...can I restore stock color setting? I tried to set 0,0,0 but don't seems like stock color that I have..
[Samsung Galaxy Nexus] insanemal:
I've been saying this for ages.. and nobody listens!! I thought it was my Hardware!

Have you tried GunBros? For me that game runs AWESOME then jumps off a cliff at random and locks up! But only the game.. I can still call notifcation bar and such at full speed!

EDIT: And it only happens with Franco kernels!
[Samsung Galaxy Nexus] timsen11:
I have always lags after i get back from a app like Facebook for example ! It takes some seconds and runs fine...on Jame Bond Kernel I dont have these lags, so it has to be a problem with the kernel

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] mieru:
Yes, with franco kernel i discover the same issue when playing Zenonia 4. With Trinity kernel it runs smoothly. It would be nice if francisco can fix this. Thanks for your work!
[Samsung Galaxy Nexus] danielvc:
I dont have any lag when I exit the Facebook app, so the problem is you. And if Jame Bonds kernel works, why whine here? You have found your solution.
[Samsung Galaxy Nexus] d.brown:
+1 even at 1.65 launcher is not as smooth as Trinity...something wrong.?

Back into the Nexus...
[Samsung Galaxy Nexus] timsen11:
@ daniel

Maybe because i payed for the app ???!!! And on 17.2 i didnt had any problems like that. Si calm down and if you cant help..just be quiet

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] mrcool007:
Yes, you're right i'm facing the same issues.

i don't get fps drops on other kernels while when i'm using Franco's i get lags with zenonia, NFS Hot poursuit GTAIII etc etc ..

He said previously that GTA was bad coded or the other games too, so why it is just with his kernel ?

@Franco Sorry to tell you that i like your work, BATTERY IS AWESOME, it is SMOOTH, but you did some **** related to GPU or 3D or .. i don't know. You're the expert.

EDIT : if you don't trust us, flash any of them and try by yourself.
[Samsung Galaxy Nexus] Niksko:
Ok, so I've done some experimenting and found some good undervolt values. This is on #18.2 with Modaco's Ir11-Beta 2.5 (It was cooked in the kitchen half way between beta 2 and beta 3)

Bear in mind that this will vary from device to device, so your Nexus may be stable at lower or higher voltages than mine. These are running nicely on my phone right now, although they will need further testing in regular use.

Finally, see if you can spot the anomaly. Can anyone explain it to me?

350Mhz -> 725mV

700Mhz -> 875mV

1000Mhz -> 975mV

1200Mhz -> 600mV

1350Mhz -> 1150mV

There are no typos there ;) I haven't experimented with higher voltages yet, though I may in the future if these prove stable (which would validate my methodology)

PS. Also, I haven't tested for excessive battery drain, which I'm given to understand can be a symptom of over-undervolting.
[Samsung Galaxy Nexus] nerotix:
asap I flash 18.2.. and boot the phone it freezes and reboot after ~20 seconds.

No, nothing is changed, its default.