yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] illcat2000:
Hello I've been using this kernal for some time and really enjoy it. However I just woke up and went to unlock my screen and it would not respond no matter what. I took the case off pulled the battery and manually booted into recovery. I got into recovery but could not use it the screen just started reacting to touches I wasn't making I watched my phone highlight various recovery options till luckily reboot was selected. Rebooted and working fine I'm pretty positive this is a kernal issue cause the last thing I did was go from imos kernal to Franco's about a day ago. On cna btw 1.4.0. I do not play with undervolting and if it matters it was on the charger any suggestions?
[Samsung Galaxy Nexus] mike216:
Ive tried 18.2 and when I woke up 8 hours later I only lost 4%, that's pretty good with data off. No SOD with a good UV going. If you guys are trying other kernels and getting SOD then reflash your rom then Francos kernel or extract the boot.img from your rom and fastboot flash the boot boot.img.

Franco's kernel changes the ram disc and if your experimenting with other kernels this could be the reason for weird behavior?
[Samsung Galaxy Nexus] Gwanatu:
I've only ever used franco's kernel. I haven't done a full wipe since the 17 kernel, just the normal cache/dalvik wipe before flashing the update.
[Samsung Galaxy Nexus] upther:
I just got the phone on Tuesday. AOKP is the first ROM I've put on here and Franco's 18.2 is the first kernel I've used.
[Samsung Galaxy Nexus] yhbrandon:
After checking my battery usage, i see that andoird OS is taking up 50 percent of my usage. This must be the cause of my battery drain. Im running kang toro build 25, with 18.2. Both were installed from a full wipe. Any recommendations for fixing this issue?
[Samsung Galaxy Nexus] mike216:
It might be time to do some spring cleaning :)
[Samsung Galaxy Nexus] mike216:
I think its your guys roms that could be causing it. I'm running codename android current 1.4, francos 18.2 350-1350 with the 350 and 700 uv by 100 and the 1000,1200,1350 uv by 50
[Samsung Galaxy Nexus] pvspencer22:
Anyone tried this to solve SoD?
[Samsung Galaxy Nexus] rgoyena:
I don't know why my phone is laggy when I turn it on and I switch screens. Do you guys notice this too? I think I will revevert to the older versions
[Samsung Galaxy Nexus] TEK112:
Sounds like a governor problem, unless you are hotplugged, UV'd and running a low frequency on the low end.
[Samsung Galaxy Nexus] otis_bartleh:
Running the Apex ROM and using the stock kernel from it, not unhappy, but just flashed, and "Android is updating" right now... Always looking for better battery life... :)

Still need to let everything settle in I guess, and I know benchmark scores don't really mean much, but with the stock kernel from apex, cpu at 350/1200 i was getting 3,200+ results from Quadrant. With the Franco kernel, at 700/1600, the 2 Quadrant results from 2 runs are 2,879 and 2,664. Is this a strange result?

Another edit: Tried undervolting to the same #' as http://xdaforums.com/showpost.php?p=22819397&postcount=2220 and did get better results, but not by much, 2,931 and 2,940...
[Samsung Galaxy Nexus] Rootuser3.0:
+1 did the same
[Samsung Galaxy Nexus] pvspencer22:
I did the same and still experienced the SOD...wonder what it could be.
[Samsung Galaxy Nexus] sway40:
I like 18.2 as well but im not getting the battery I got out of 16.2 especially screen time. It seems like I could keep the screen on longer with less better drain than with 18.2.

~ Sent from my GNexus @1.66ghz~
[Samsung Galaxy Nexus] dmmarck:
Same here.

He just said in another thread that an update will be out soon, though. So good on him.
[Samsung Galaxy Nexus] dug-e-fresh:
so far its been a great kernel! Thanks for all the hard work.

Regarding benchmarks, I have noticed more variation between runs using both linpack and quadrant... when its running on all cylinders I'm getting 100+ on linpack multithread and 3800+ on quadrant (this on 1.65 with -100 uv). However, there are times linpack will be as low as 30 and quadrant in the upper 2000's.

That said, those performance dips never seem to bear out in normal use, so I don't worry about it. It is a little odd though.

Franco- again great work. Quick question (and it may have been covered), what's your gpu clocking in these kernels? Your's and Trinity's are the only two kernels I use and I have a love for both of them. I like the cpu overclocking and stability you've seem to found... and his destroys all in the gpu area. Have you two ever collaborated?
[Samsung Galaxy Nexus] neverhappy:
Been running great since release. I too am running codename android current 1.4, francos 18.2 350-1650, Ondemand & HotPlug with the uv set to:

1650Mhz-1450mv

1500Mhz-1400mv

1350Mhz-1380mv

1200Mhz-1380mv

1000Mhz-1317mv

700Mhz-1203mv

350Mhz-1025mv

second charge since install and on 10hr 20min with 70% still left. 4g off, 3g on, wifi always on, screen set to auto. couple of 5 min phone calls, check news on browser for 10 min, check email thru the day for about 30 min. So lite use, but still happy No SOD since installed. Only time I got SOD on all these various kernels/ROMs is when playing with uv.
[Samsung Galaxy Nexus] dw3bb10:
Which version has gotten the most positive reviews for performance and battery life? I underclock the CPU. Mainly just concerned with maximizing the battery. Any recommendations on undervolting and a kernel would be awesome and greatly appreciated! Thanks!
[Samsung Galaxy Nexus] dmmarck:
I had the best experiences with 16.2.
[Samsung Galaxy Nexus] dw3bb10:
Deleted.......
[Samsung Galaxy Nexus] dug-e-fresh:
Ok, so regarding gpu overclock, I see you are not a believer in that (read that blurb about it). Be that as it may, with the 512 gpu overclock in Trinity's kernel, I pick up about 7-8 fps (24.6->32.2, 30% improvement!) during a Nenamark 2 test. Not trying to tell you what to do, just FYI. :)
[Samsung Galaxy Nexus] timbck2:
I'm still having SOD issues with my Galaxy Nexus with Franco 18.2. I'm running craigacgomez's 4.04 IMM30B based ROM.
[Samsung Galaxy Nexus] jr313:
I cant even get this up and running at all on 4.0.4 or 4.0.3. I have your app and have downloaded the 18.2 kernel and manually installed wiped cache before and after installation just like any other kernel and no luck, you app also FC'z when i try using Colors Multipliers setting. anyone else having this problem?
[Samsung Galaxy Nexus] franciscofranco:
Get me logs, I can't work without seeing what crashed.

#18.3 is out.
[Samsung Galaxy Nexus] hredder:
Ok will run for 24 hours and send you the log
[Samsung Galaxy Nexus] mrwebb:
Hey anybody having issues with the app not downloading a kernel each time one is available? I saw 18.3 was available and tried to download the zip but it never initiated after several tries...just curious, nor would it flash either.
[Samsung Galaxy Nexus] dmmarck:
Is your app/updater up to date? I'd check that. I had that issue once, but I rebooted, updated the app and it was good to go.
[Samsung Galaxy Nexus] Stadsport:
Just flashed 18.3. Froze on the unlock screen after booting. Had to battery pull, and when it rebooted every single app just crashed non-stop. Flashed #17 back (since it was on /sdcard/) and I'm trying to get it to boot now... might end up having to wipe data/factory reset. :(
[Samsung Galaxy Nexus] seegs11:
i just flashed 18.3 as well and my phone is going crazy .... keeps rebooting !!! :(
[Samsung Galaxy Nexus] dmmarck:
I just saw the same thing on another forum (Android Central). Did you auto flash or do it manually? Wipe cache/dalvik?
[Samsung Galaxy Nexus] seegs11:
this totally fuc*ed my phone up

---------- Post added at 03:16 AM ---------- Previous post was at 03:16 AM ----------

yes... wiped both. flashed through CWM
[Samsung Galaxy Nexus] Dylerium:
Well. Had 18.2 and 1.65 worked fine now every time I try to set Max it instantly freezes. Even on 1.5. Which worked fine before on multiple kernels.

Sent from my 1.65ghz galaxy nexus :D
[Samsung Galaxy Nexus] dmmarck:
Wow. Interesting. Try flashing an older version, deleting the download, re-downloading, and try again?

Also, you have 2 PMs lol
[Samsung Galaxy Nexus] seegs11:
where can i get older versions? what older verision is the best to use?
[Samsung Galaxy Nexus] dmmarck:
Check your downloads folder on your sdcard. I'm not sure about autoflashing (I may be wrong, but it might automatically place a zip somewhere), but I always download manually so I have a whole slew of them. I keep the ones I like (like 16.2 or 17.1) and delete the rest.

Wipe cache/dalvik, flash the old one, re-download 18.3, wipe again, flash again, ???, hopefully profit?
[Samsung Galaxy Nexus] seegs11:
i just did a restore from my latest back up.... back on a different ROM now haha

---------- Post added at 03:29 AM ---------- Previous post was at 03:26 AM ----------

well im a newbie and deleted old ones ... and the oldest one i had was 18.2. i definately wont be flashing this again
[Samsung Galaxy Nexus] alphanu22:
Kernel auto-flash 18.3

worked fine-
[Samsung Galaxy Nexus] dmmarck:
lol you're not the same guy on AC are you?

That's kinda odd. Mine was flawless. :shrugs:
[Samsung Galaxy Nexus] seegs11:
no not me haha. it's werid becaue it was fine at first. i belive i set to 1.5mhz O/C then i put my phone to the side and noticed it just reboot. then it never stopped. what is the OC highest settings on 18.3? i thought it got reduced. i wonder if something just went wrong with the install
[Samsung Galaxy Nexus] dmmarck:
He said 1.6/1.65 won't work for 90% of people. He said on G+ he's running 700-1500, so that's what I'm running too lol.

It could be simply a bad download. That happens (unfortunately).
[Samsung Galaxy Nexus] jr313:
I installed 18.3 successfully! And your app is no longer FC'n brotha, thank you sir!
[Samsung Galaxy Nexus] franciscofranco:
Users with reboots - don't overclock too much, maybe your device doesn't handle that frequency. If you use >1,2ghz you're on your own, I take no responsibility from data loss or whatever happens.
[Samsung Galaxy Nexus] Dylerium:
why did my phone work at 1.65 on 18.2 but on 18.3 it wont, it wont even work on 1.5, which also worked in 18.2 :( :(

EDIT: back on 18.2 and all is well. my phone is not cooperating with something in the last update...
[Samsung Galaxy Nexus] DarkKnight62:
just a thought. if you are coming from another kernel you can try and flash faux's reset kernel and then flash this kernel and see if that works.
[Samsung Galaxy Nexus] franciscofranco:
Reading the changelog helps...
[Samsung Galaxy Nexus] mike216:
Thanks franco! 18.2 was insane on performance and battery life I hope ondemand is the tweaked version that's included on 18.3
[Samsung Galaxy Nexus] Dylerium:
sorry i figured that the 90% was the number of people to begin with, not the people after the update, unless im still misunderstanding...
[Samsung Galaxy Nexus] franciscofranco:
Ondemand is untouched from 18.2 to 18.3.

It would be much easy on my if people actually read the changelog. I specifically stated that > 1,5ghz wouldn't probably work anymore because I had to enable Smartreflex 1.5 again for stability issues. Obviously users got stuck at boot because I'm 99,9% sure those users had 1,6ghz or 1,65ghz set on boot, which would cause the bootloop. It's really really hard on me seeing that those issues are easily avoided if users actually READ the changelog and prepare their devices accordingly before updating the kernel. Now that I was going to sleep I have to rebuild the kernel without >1,5ghz frequencies support to prevent more bootloops and release it within the hour.
[Samsung Galaxy Nexus] far_star:
Francisco,

I've been using your kernels for a while, but this change to 18.3 has been the most dramatic I have ever seen. Fantastic speed and responsiveness running the default governor and 350-1500Mhz. Just Wow !

Thank you so much for your work. Donation inbound.
[Samsung Galaxy Nexus] alphanu22:
after flashing 18.3 - my light flow app stop working, anyone had this happen?
[Samsung Galaxy Nexus] upther:
18.3 downloaded and installed perfectly for me. Looking forward to the end of the SODs. Thanks Franco!
[Samsung Galaxy Nexus] seegs11:
FYI well I changed my settings back to stock @ 1200 before i flashed the update and was stuck rebooting. I'm not trying to be a pest but it was not an eventual night for me! I'm sure i will get it to work the next time i flash it. 18.2 was running incredibly fast and i loved it.
[Samsung Galaxy Nexus] Dylerium:
im going to have to agree with 18.2's performance, and i had no SOD's thankfully so i think ill stay at 18.2 for a while, and i had read the change log and mis-understood...
[Samsung Galaxy Nexus] alphanu22:
DL'ed 18.4 smooth-
[Samsung Galaxy Nexus] mike216:
Good move franco 1.6 and 1.65 is just stupid! Luckily we have a good kernel that doesn't need to be maxed out at some ridiculous high clock speed. Your kernels run fluid :)
[Samsung Galaxy Nexus] dmmarck:
Running at 700-1500, conservative w/ hot plug enabled. So far so good ;).
[Samsung Galaxy Nexus] Stadsport:
I wasn't overclocked at all, set to 1200mhz ondemand. For what it's worth, I always read the changelog before flashing newer versions, I almost always check this very thread to see opinions before flashing, I always disable "Set on Boot" options in SetCPU, disable undervolting, etc. I always fully prepare my phone prior to flashing kernels, but this doesn't guarantee that it's going to work smoothly every time for every user. Please don't assume we're all neglecting to read the changelogs or something.

I'll give 18.4 a try, but not before making a fresh TiBu backup.
[Samsung Galaxy Nexus] dmmarck:
Did you auto flash? Had to have had a conflict somewhere . . .
[Samsung Galaxy Nexus] mike216:
1300 is perfect for me 1400 is perfect for our speed freeks out there:D

I love your decision! Stability and battery life rule!

Does anyone know which one is better for battery between conservative or ondemand? Thanks for any help
[Samsung Galaxy Nexus] Stadsport:
I did auto flash with franco's app (and I do always check for updates before doing so).
[Samsung Galaxy Nexus] rgoyena:
I love this version!!! My lagginess is gone again. Thanks Franco! Awesome ****!
[Samsung Galaxy Nexus] mike216:
I totally agree with your assessment. 18.2 was amazing on battery and im hoping 18.4 is the same. I'm very happy with these new steps 1300 and 1400 there perfect and should be a good balance for us user's. Benchmark scores are not as important to me is battery and stability. That's basically what it boils down to. Nice work franco and I'm making my monthly donation.
[Samsung Galaxy Nexus] idkwhothatis123:
Anyone have 18.3 still? I can run 1.65 flawlessly and love it. Share a dl link please?
[Samsung Galaxy Nexus] dmmarck:
I'm flashing CM9 nighty #1 as we speak. I'll report back with any issues/compliments/hallejulahs.
[Samsung Galaxy Nexus] nerdgenius:
Yea I'm loving 17.2 with brightness at 35%. Pulling 5 hrs screen time on standard battery. Hot plug enabled. Sync on!!!!
[Samsung Galaxy Nexus] cuzzinz:
I have only been going for an hour or so on 18.3 I will report back tomorrow in case I get a SOD.

I always make sure I wipe cache and dalvik before and after the flash. So far so good.

I have found that I don't get consistent benchmark scores unless I under volt. I run daily at 700/1200 but have been successful at 700/1350 and 700/1000 for daily use. Battery seems a lot better now. I was on track for about 11 hours of battery today and that was with moderate use running quadrant a few times and texting, few phone calls, browsing, etc. I had 4g on and brightness on auto.

This kernel is awesome!!! I'm testing from now on at 700/1200 w/ hotplug on so lets see how things go.

These are my under volt settings:
[Samsung Galaxy Nexus] Esteway.619:
Where are the nightlies at???
[Samsung Galaxy Nexus] Berzerker7:
Too bad. 1.65GHz was working perfectly for me. Looks like I'm staying on 18.2
[Samsung Galaxy Nexus] mrwebb:
I been trying to download 18.4 thru the App still not downloading or flashing...frustrating.
[Samsung Galaxy Nexus] dmmarck:
http://get.cm/

goo-inside.me has the GAPPS
[Samsung Galaxy Nexus] Esteway.619:
Thanks buddy.
[Samsung Galaxy Nexus] dmmarck:
No problem. Running 700-1500mhz, conservative, HP enabled with it.
[Samsung Galaxy Nexus] ArtnerC:
Getting lots of these exceptions in LogCat, using 18.3 but had them in previous versions as well. Works great in general but feels like this shouldn't be happening...

E/sdwatch(125): Error 4 reading event buffer (Interrupted system call)
[Samsung Galaxy Nexus] jbzcar:
Could someone please share 18.3? I missed the download and just want to give it a shot. Thanks!
[Samsung Galaxy Nexus] dmmarck:
I don't have the link but make sure you're not at 1.6/1.65 ghz ;).
[Samsung Galaxy Nexus] idkwhothatis123:
18.2 ran like butter and i had killer battery life. I want 18.3 cause 1.65 was perfect for me
[Samsung Galaxy Nexus] dmmarck:
1.65 probably won't work with 18.3. Please read the logs! Franco is re-using SmartReflex 1.5 (which works fine from 1.5 ghz down) so reduce/eliminate the SODs/overheating of 18.1/.2. Therefore, if you're on 1.6/1.65ghz, AND you set on boot, then you're phone will be stuck rebooting/in a boot loop.

If 1.65 was perfect stick with 18.2 b/c 18.3 will simply cause you to have nightmares until you flash back. OR stay to 1500 or below.
[Samsung Galaxy Nexus] jbzcar:
Yes, I read the thread, just need the kernel. K thx.
[Samsung Galaxy Nexus] idkwhothatis123:
Problem being I did the auto flash on 18.2 and I can't find that kernel anywhere. I just flashed the tabaokp version. Can someone reupload the 18.2 kernel please?

Thanks for the response btw.
[Samsung Galaxy Nexus] dmmarck:
No problem. Search a few pages back or in the GSM one a few pages back. I remember seeing it but I'm on my way to work so I can't grab it. It was either .2 or .1, so don't quote me ;).
[Samsung Galaxy Nexus] neverhappy:
Link to most of the kernels. Save as bookmark:

http://www.world-of-nexus.com/download-section
[Samsung Galaxy Nexus] dmmarck:
And just so people know--these are good for both CDMA/GSM phones, or are there separate locations for both? Can't check now (at work), but I just want to double check.
[Samsung Galaxy Nexus] neverhappy:
Good point. I did not see that level of specificity. I sent your suggestion to the webpage site dev.
[Samsung Galaxy Nexus] dmmarck:
Thank you. I bookmarked the site a day or so ago (you might have been the one to post it as well lol) but I held off on downloading until clarification. I appreciate it!
[Samsung Galaxy Nexus] mrwebb:
Anybody else experience random reboots with 18.4? Im running the kernal with stock settings that came set in the app and have had 2 random reboots in the past hour. Also any explanation on why the colors sliders dont stay set in the app once you back out of the app?
[Samsung Galaxy Nexus] yhbrandon:
Big improvement with the 18.4!!! with 18.2 I was dropping 1% battery every 2-3 minutes. With this, at 700-1400 on conservative and Hotplug enabled, after 3 hours only have dropped 10 percent, with some text messaging and 15 mins of spotify. I'm sure with time that number will increase, but preliminary testing looks good.

Any tips for better battery life would be appreciated!

EDIT: I take that back, im set at 700-1200 on conservative with Hotplug enabled, and during normal use(twitter, facebook, web browsing) with wifi and 4g enabled, i was back to dropping 1% per minute. I dont know why I'm seeing such results. Flashed from full wipe. cleared cache and/dalvik. Nothing usual in the battery usage either. Screen 34%, anroid OS 20%.

Maybe i just need to give it a couple of days to settle.
[Samsung Galaxy Nexus] dmmarck:
Try wiping cache/dalvik and reinstalling a fresh download. (Go in, delete the downloaded file, re-download it from the app).

The sliders reverting back threw me off, but the settings stay the same so that's nice :cool:
[Samsung Galaxy Nexus] mike216:
It seems a lot of people running aokp are experiencing reboots. I'm on codename android and haven't gotten any on 18.2 or 18.4?
[Samsung Galaxy Nexus] otis_bartleh:
Well, after using 18.2 for almost a day, I can say I'm really impressed with my battery life. Especially since it seemed to charge itself ~5% overnight! :D Just over 21 hours on battery, almost 3 1/2 hours of screen on time. This is with a standard battery...

The huge dip in battery life was when I was playing Random Mahjong for a while. The rest is somewhat normal use, 4G on almost the whole time, sync on, screen on auto, lightflow running my led, playing music, browsing, some games, and a few quadrant tests and speakeasy speed tests at the beginning of the chart... (except while overnight on airplane mode)
[Samsung Galaxy Nexus] dmmarck:
I didn't have any except a SOD on 18.1 (but only 1 lol). I presume it's more to do with settings, but ya never know at this rate.
[Samsung Galaxy Nexus] TEK112:
Cheers!

&

Welcome!
[Samsung Galaxy Nexus] luckylui:
Cheers!! :D

&

Thank you sir.

hTc T-Bolt
[Samsung Galaxy Nexus] Ma5heen:
I'm hearing mixed things about setting the low frequency to 350. Wouldn't this mean that the phone switches from 350 to 1200 mHz on demand, when necessary? So when the screen is off the resting state of the phone is 350 instead of 700 therefore having less battery consumption?

So the best way to find something out is to do it, and from what I can see I'm getting great battery life with the low being 350.
[Samsung Galaxy Nexus] mikeacela:
is this kernel undervolted?
[Samsung Galaxy Nexus] sinik420:
come on -.-

* UV interface is disabled - don't bother ask me 50 times for this. It has been proved that it creates a huge stall if a user undervolts too much. This kernel is already undervolted with this settings: 925000, 1103000, 1217000, 1280000 - values suggested by faux on his thread on rootzwiki and they seem to play along pretty well
[Samsung Galaxy Nexus] mikeacela:
-.- Thanks, thats all I wanted to know. I know its bad to uv too much, I just wanted to know that it comes default uv and now i do.
[Samsung Galaxy Nexus] kjwalker:
Franco, just a small suggestion for your application - perhaps move Check for Updates to the top of the list. It's just a small thing that bugs me when I use it :P

But keep up the awesome work!
[Samsung Galaxy Nexus] TheBiles:
+1. Or let it check automatically when you open it!
[Samsung Galaxy Nexus] sinik420:
be careful, some people have to pay for data
[Samsung Galaxy Nexus] djh816:
Anyone with a data plan should be able to handle a 1kb text fetch...
[Samsung Galaxy Nexus] mikeacela:
Does this have a direct impact on battery life? A link the the thread with that debate would be much appreciated.
[Samsung Galaxy Nexus] sinik420:
Sounds like he's talking about race to idle.

edit-nevermind, setting the low to 700 is still not as good as race to idle. If the phone wakes and runs at highest cpu for a lower time and goes back sleep it is the ideal situation
[Samsung Galaxy Nexus] franciscofranco:
Nightly 12 is out.
[Samsung Galaxy Nexus] mike216:
It will save you battery! In theory your phone will wake up less because it has the power to finish tasks quicker and enter into deep sleep faster. I think I'm explaining it correctly
[Samsung Galaxy Nexus] sing1gnis:
I am having the same issue. I fully charged last night and let it sit off the charger while I slept. Wake up the next morning and it's down to 90%. Android OS was at 56%. Really strange.
[Samsung Galaxy Nexus] mike216:
Franco first of all we love ya man! Will donate today when I get home from work. Can you please give me your opinion of the best numbers to put in your app for very bright colors, thanks I wouldn't even know where to start to guess
[Samsung Galaxy Nexus] Berzerker7:
I'm confused as to what this ColorControl does...I understand it's a gamma offset...but what values are we supposed to enter, is it 8-bit color? +1? -1? What?
[Samsung Galaxy Nexus] 9wire:
Not finding the color control...I have the updater app.

Nvrmnd...updated app through market.
[Samsung Galaxy Nexus] mike216:
Its there under kernel settings

You might have to update in market