yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] TEK112:
Did you read up on DCC and possible issues with the GNex CPU? I posted it a little back in this thread. Just search my name. If 17.2 gave you boot loops, 17 will probably be stable.
[Samsung Galaxy Nexus] edgie168:
Unfortunately, still bootloop city. Will wait.
[Samsung Galaxy Nexus] Natolx:
Delete your init.d folder in etc/ that solved the boot loop problem for me
[Samsung Galaxy Nexus] Zane_Grey:
You shouldn't have to delete the whole folder it was probably just a script in the folder causing the issue. Try just deleting the overclock script then installing. If you want such things as min free and sdboost or other scripts to run at boot you need the init.d folder.
[Samsung Galaxy Nexus] cuzzinz:
What kind of battery life are you guys getting with 17.2. I am getting worse than stock after about a day.

Should I wait a few days for things to normalize?

I am using francoGazelle 700/1350 on the almost stock 4.0.4 rom. Things seemed to be a little choppy with francoTurtle.

Any recommendations?
[Samsung Galaxy Nexus] kichard:
Personally when I ran this kernel (optimized for 4.0.3) with a 4.0.4 from my battery was horrid. Its either the rom itself never sleeping (my case) or the two not playing nicely.
[Samsung Galaxy Nexus] sway40:
Everytime I flash this kernel on the newer cm9 alphas, my gallery is completely out of order. My pics are everywhere, it's only been doing it the last couple of builds but doesn't matter what version of the kernel I use.

~Sent from my GNexus running Cm9~
[Samsung Galaxy Nexus] rgoyena:
What's the sqlite option for?
[Samsung Galaxy Nexus] sway40:
Ok it's not just the cm9 roms, just flashed aokp b23 with this kernel and gallery is f'ed up. Anybody have a solution???

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
8 hours is not so bad with moderate use. No streaming but a few phone calls and a lot of web browsing...some on wifi some on 4g. I am still on the stock battery. Waiting for my extended battery to come in the mail.

Is this the same most of you are seeing?
[Samsung Galaxy Nexus] sway40:
What was your screen time, that's really not that good to be honest. I've had over 3hrs screen time and just shy of a day on a full charge. Was on cm9 and 16.2 I think.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
Just a little over 2 hours on auto brightness. Should I try switching to 16.2?

Some people have said to wait a few days. I'm on day 2 with this kernel... should I wait or just try 16.2 or a different kernel. Btw I'm on the almost stock 4.0.4 rom.

Edit: been thinking of going back to the stock kernel from the rom.

Lmk what you think.
[Samsung Galaxy Nexus] Takeoisblack:
Happening on Bugless Beast also. Solution needed.
[Samsung Galaxy Nexus] kjwalker:
Look at his awake time. Something kept your phone awake for a LONG time. I would say 8 hours with that long of awake time is pretty damn good.
[Samsung Galaxy Nexus] AcE XBOX:
I am using modaco's 4.0.4 rom with the 17.2 kernel and apparently it ain't that bad. Not sure how the battery increased since I fell asleep on top of the phone lol.
[Samsung Galaxy Nexus] cuzzinz:
What is your screen on time?

Lol when my phone is just off I get amazing battery life :-)

I haven't gotten anything like 3 hour screen on time though.
[Samsung Galaxy Nexus] itch808:
Here's my $0.02

13.1 -- Buttery smooth, avg battery life (conservative/hotplug)

16.2 -- Slightly rougher than 13.1, amazing battery life! But 2 SODs within a couple days. (francoturtle/hotplug)

17.2 -- Slightly rougher than 13.1, avg battery life (francoturtle/hotplug)

If only I could have the butter of 13.1 and battery life of 16.2 w/o the SODs.
[Samsung Galaxy Nexus] kingoanklebreakn:
I don't get SODs with 16.2 so that's the kernel I'm running with atm.
[Samsung Galaxy Nexus] dw3bb10:
What are SOD's?

I personally have a GS2, but ive been experimenting with kernels for my girlfriends GNex. Running 13.1 now, Thinking about flashing 16.2 though.
[Samsung Galaxy Nexus] Esteway.619:
I think it means "Sleep Of Death"
[Samsung Galaxy Nexus] sway40:
You are correct.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
Trying 16.2.

Will report back.
[Samsung Galaxy Nexus] kichard:
So far 15.2 has given me the best results..........., .
[Samsung Galaxy Nexus] cuzzinz:
Ya got SOD while the phone was charging last night. Lol. Gunna give 16.2 a day or two and then I'm gunna try something else.
[Samsung Galaxy Nexus] bendirkss:
Franco you should have a free version of your app then a way to upgrade via PayPal, for people like me with no credit card:(
[Samsung Galaxy Nexus] bendirkss:
I wanna know the same thing. Just flashed 16.2 and found out there's 17.2. Dunno if I should stay or flash
[Samsung Galaxy Nexus] kjwalker:
I've been running 17, 700/1350, francoTurtle. Smooth as butter and getting great battery life.
[Samsung Galaxy Nexus] Gahh Its Lee:
Franco does have a way to buy the app from PayPal.
[Samsung Galaxy Nexus] bendirkss:
You'd recommend flash 17.2?

I guess were always pushed to run the latest. That's the most supported
[Samsung Galaxy Nexus] franciscofranco:
#18 is out. Feedback is needed.
[Samsung Galaxy Nexus] Gja88:
Working fine as well here. Flashed with your app with no problems. Just to confirm. It boots in 1350/350 correct? One last question. I've noticed the screen color is back to stock. Is that 0/0/0 in the color settings for future reference, Since I know you change it to something else. Is it normal for the phone to get hot/warm in 1350? I've noticed mine does even in your past updates.
[Samsung Galaxy Nexus] Gja88:
I must mention. This thing flies. Good stuff man. Thanks for the awesome work.
[Samsung Galaxy Nexus] far_star:
Just flashed 18 wiping cache and davlik-cache. So far so good.

I noticed that 1500MHz is no longer available. Any reason for this ?

Great work as usual.
[Samsung Galaxy Nexus] bendirkss:
Just flashed 18.

I booted with 400-1200 interactive.
[Samsung Galaxy Nexus] ErichMoraga:
Flashed 18 here as well, but can't say I miss 1500 MHz since it was choppy at every voltage. Running 1350 MHz fine.

-Erich
[Samsung Galaxy Nexus] far_star:
Antutu score is in. 3607 with default clocks/govenors/voltages. Running AOKP build 23.

I thought the low scores were already addressed, or should I not be concerned with benchmarks ?

[EDIT]

After letting the phone sit for a while it went to 5804. Perhaps wiping cache and davlik-cache had something to do with the initial low score ?
[Samsung Galaxy Nexus] jtj1825:
Wish benchmarks were never created...so dumb who the **** ever uses their phone to its peak capacity over constant, long periods of time that benchmarks even matter? Just carrot on a stick mentality IMO...

P.S. Not a personal attack in the poster above just a general opinion
[Samsung Galaxy Nexus] luckylui:
Its like a diagnostics check but for the phone. That's how ic it..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Droid316:
Does this kernel work on liquid beta 5?

Anyone running it on that rom?
[Samsung Galaxy Nexus] DirtySimpleClean:
flashing 18 now, will report back later with results.
[Samsung Galaxy Nexus] bendirkss:
No problems with 18 so far
[Samsung Galaxy Nexus] bendirkss:
Well, how..
[Samsung Galaxy Nexus] eman3316@optonline.net:
Try clearing data for the gallery.
[Samsung Galaxy Nexus] nklenchik:
Testing this coming from Trinity. What frequencies are you guys running at?
[Samsung Galaxy Nexus] Droid316:
Anyone
[Samsung Galaxy Nexus] Droid316:
Anyone know
[Samsung Galaxy Nexus] DirtySimpleClean:
350/135000 ondemand
[Samsung Galaxy Nexus] Gahh Its Lee:
Working well so far 350 min makes it buggy I'd like to see 400 back it seems like it makes it that bit quicker. Can't wait to see 1.5 and turtle come back.
[Samsung Galaxy Nexus] neederishelp:
Try it and tell us
[Samsung Galaxy Nexus] Droid_JD:
Anyone else getting SOD's on 18?

No UV , running winner ROM with on demand and 350-1000.

Sent from my limited edition Galaxy Nexus!
[Samsung Galaxy Nexus] DirtySimpleClean:
no SOD here, on aokp 23, franco #18, 350/135000 ondemand, heavily undervolted

flashed 18 as soon as it was released
[Samsung Galaxy Nexus] _Dennis_:
Dumb question. Is this heavy undervolting? I'm running stable so far but only for testing.

By the way, what is the best method to determine the lowest stable voltages? Basically I set min and Max frequency to the 'test' frequency and lower voltages slowly while using setCPU built in benchmarks.
[Samsung Galaxy Nexus] Wicked4u2c:
Anyone running 4.0.4?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
I am on 4.0.4 and 18 has been smooth as butter. By tomorrow I should know of there are ant SODs and/or how a full days battery life is. I am also playing around with undervolting so let's see how this goes.
[Samsung Galaxy Nexus] Xezuka:
17.2 running on 4.0.4 (new radios as well)

(dead spot in Mobile Network Signal was while I was sleeping -- not sure what happened there?)

Real usage from Sunday-Monday evening... default settings, no UC/OC, realistic use (aka not randomly loading things for 5 minutes and continually looking at the battery stats -- actual use == checking email, texts, making a call, check a site real quick, etc), and no charging at all during this time. A huge difference from when I first picked up my Nexus at launch and it was gasping after 7-8 hours regardless of light/moderate use.

:cool:
[Samsung Galaxy Nexus] davidukfl:
18 is running fine for me. Undervolted and on AOKP M3
[Samsung Galaxy Nexus] mrwebb:
Do i need to be rooted to flash this kernal? I unlocked the bootloader and flashed the 4.0.4 radios already.
[Samsung Galaxy Nexus] Wicked4u2c:
Do you know what your on screen time was? Did you have 4G, Bluetooth, GPS, on?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 2.0t03speed:
I upgraded from 17.2 to the newest kernel today but I find I can't undervolt as much. Before I had my 350mhz voltage at 750mv but now I can't seem to go below 875mv with out getting random lockups
[Samsung Galaxy Nexus] nklenchik:
#18 was giving me problems with sod on AOKP b24...downgraded to 17.2, still smooth and fast.
[Samsung Galaxy Nexus] tr4656:
Flash the kernel with clockwork recovery
[Samsung Galaxy Nexus] Stadsport:
Ran 13.1 for a little bit, didn't seem to run better/have longer battery life than any other release. Went ahead and upgraded to 18 earlier today and it seems to be doing fine, too.

By the way, what are franco's default color values? -4 0 4?
[Samsung Galaxy Nexus] nklenchik:
Do you have the link to the older kernels?
[Samsung Galaxy Nexus] Stadsport:
Yep, here you go:

http://www.world-of-nexus.com/download-section/category/4-franco-kernel

It's dated January 20th, if you can't recognize it from the filename.
[Samsung Galaxy Nexus] cuzzinz:
:-D

Will report on battery life tomorrow.

EDIT: Oh #18 UV and OC
[Samsung Galaxy Nexus] nklenchik:
Hmm I didn't see just plain v17 on there...anyone have a link for that? lol
[Samsung Galaxy Nexus] wayneb02:
If im not mistaking it was really buggy so it was banished never to be seen again ha! But this may just be the beer talking
[Samsung Galaxy Nexus] mild7intl:
18 is my favorite so far Franco. Excellent battery life no sod or lag. Running with b24aokp.

Could u include voltage set on boot option. Using rooms built in option right now

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk
[Samsung Galaxy Nexus] psohn:
Anyone know where the repo mentioned in the change log is?
[Samsung Galaxy Nexus] eman3316@optonline.net:
Can someone please comment on the color control feature on how it works and if it improves the screen a lot? This screen needs some serious help with it's colors and sharpness and curious if this will fix it...
[Samsung Galaxy Nexus] sway40:
yeah post screen time, if people post pics screen time is a must. I could get that much time out off my phone with any kernel if I don't use it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] DooMMeeR:
franco could you include your current kernel config in your repo?
[Samsung Galaxy Nexus] rgoyena:
No screen lag on ondemand buy when I switch to interactive, there's a slight hickup when swiping to a different screen.
[Samsung Galaxy Nexus] Droid_JD:
I got another SOD with 18 last night. I don't think it likes my phone. Back to 17.2 i suppose.

Still, thanks for all your work on these Franco! Much appreciated!

Sent from my limited edition Galaxy Nexus!
[Samsung Galaxy Nexus] RussianMenace:
Looking forward to trying this out as soon as I get out of class. On 17.2 right now and it drops from ~96% to ~36% overnight (8 hours)...seems a little silly to go through 60% battery in 8 hours with no use.
[Samsung Galaxy Nexus] TEK112:
Wipe cache and Dalvik. It sounds like your phone is not entering deep sleep.
[Samsung Galaxy Nexus] RussianMenace:
That was the first thing I did. Also cpu spy reporting deep sleep is being used :(
[Samsung Galaxy Nexus] TEK112:
Go into CPUSpy and reset the counter. Turn the screen off and let it sit for 2 minutes. Turn it on and refresh CPUSpy and look at the deep sleep time. Please report back.
[Samsung Galaxy Nexus] RussianMenace:
Just tried it. 4 minutes in the clock , 3:27 in deep sleep. So it's definitely working....very strange. Might have to calibrate the battery.
[Samsung Galaxy Nexus] bendirkss:
Woke up and my phone wouldn't wake up. Needed a battery pull, running 18.
[Samsung Galaxy Nexus] cuzzinz:
:-( hopefully I don't get any SODs.

###CROSSES FINGERS###
[Samsung Galaxy Nexus] bendirkss:
It was my first on any franco kernel.
[Samsung Galaxy Nexus] cuzzinz:
over an entire day what is the right... or a good percentage of time the phone should be in a deep sleep mode?
[Samsung Galaxy Nexus] TEK112:
What does the phone say is using most of your battery?
[Samsung Galaxy Nexus] Gahh Its Lee:
It depends. If you don't touch your phone much than a 10 hour day maybe 8 hours in deep sleep? It deep sleeps when its not being used if you use it a lot it'll be a lot lower.
[Samsung Galaxy Nexus] far_star:
I would say at least 90% if not more. Of course it depends on what you're running app-wise int eh background. If you're charging I find that the phone doesn't go into deep sleep so make sure you're not charging.
[Samsung Galaxy Nexus] lenard_hester:
Same here. I have had this happen twice now.
[Samsung Galaxy Nexus] Gja88:
So I switched my min CPU from 350 to 700 earlier today and after having the phone on sleep for a bit got an Sod. Had to battery pull to restart phone. Anyone else on 1350 Max and 700 min having these sod problems by any chance?
[Samsung Galaxy Nexus] zman6900:
My desktop has only 4 cores.
[Samsung Galaxy Nexus] sway40:
Im having to good of results from 16.2

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] cuzzinz:
What are your settings? UV...OC... governor?
[Samsung Galaxy Nexus] sway40:
Francoturtle, hotplug enabled, 1200 max 400 min, screen half brightness, and juice defender is how I roll. I don't undervolt that's cheating!!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
And I know it's all this kernel bc I got almost identical battery life on cm9 and 16.2. Before this kernel aokp has horrible battery life.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] itch808:
Is this with Wifi or 4G? What juice defender settings are you using?
[Samsung Galaxy Nexus] kichard:
+1
[Samsung Galaxy Nexus] sway40:
Some wifi, no 4g that's a waste. Juice defender is on aggressive that's all no custom setup. Data is just turned off and on when screen is off with default jd settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] luckylui:
18.1 @ 1500 is GODD DAMN! Awesome ****. Thank you sir!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] holysnikey:
So I flashed 18 today and I was on 17.2 but I went to flash back to 17.2 and flash to 18.1 but no kernel works besides 18. I tried other kernels and even a "reset" kernel but nothing works. Has anyone heard of this before? I tried wiping cache and dalvik but it didn't work. I would really like to not wipe data but I might have to in order to upgrade again. Is it maybe because I used the autoflash feature?
[Samsung Galaxy Nexus] Gwanatu:
I just had to pull my battery for the first time ever AFAIK because the phone wouldn't wake up. Using 18.1 and AOKP 25.
[Samsung Galaxy Nexus] dwvenus:
dwvenus

I've been using these kernels and updates for a long time now and as far as I am concerned they are the best around. I have tried others but keep coming back. When I went from 17.2 to 18, I noticed an immediate and significant increase is speed and battery life. I don't know what was so different with 18 but it was definitely great. I just today upgraded to 18.1 and have no reason to expect anything less than great performance from this one as well. I am using craigacgomez's [ROM]IMM30B 4.0.4 Stock, rooted, deodexed, zipaligned, busybox, insecure boot + mods zips found in xda developers. So far this is by far the best combination I have found.
[Samsung Galaxy Nexus] luckylui:
Auto flash works. That's how I did it and always have. Running AOKP 25 @ 1500-350 ondemand. Love it!!!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stevessvt:
Using 18.1, and for th first time it is working well at 1500, not crawling like a baby over broken glass. I thought most phones couldn't handle it, I know mine couldn't. What changed?
[Samsung Galaxy Nexus] Gja88:
Checking on CPU spy. My phone never gets into deep sleep. Is this normal? It was fine on 18 but it has yet to do this on 18.1. Reflashed through your app and still nothing.
[Samsung Galaxy Nexus] franciscofranco:
Just a small if clause commented to help on >1.2ghz frequencies stability.
[Samsung Galaxy Nexus] franciscofranco:
Your issue sorry. Both kernels are 100% the same besides 1.5ghz addition and sod fix.
[Samsung Galaxy Nexus] zerocool79346:
Meh, just rename the versions when you download them if you plan on keeping a previous. Franco assumes (since it's a nightly) that you'll delete the previous version.
[Samsung Galaxy Nexus] hajabooja:
I feel the same way. Anyone have a link to 9.2?
[Samsung Galaxy Nexus] sinik420:
As long as its turned on it doesn't matter what you do with it
[Samsung Galaxy Nexus] androidmichael:
Will setting the low frequency at 350 help or hurt battery life. I've had lots on it and would like to know which is right
[Samsung Galaxy Nexus] TEK112:
The lower the clock speed the lower the voltage. The lower the voltage the less power it needs. Lower clock speeds mean better battery life. Now, some kernels may have lower voltage than others with the same clock speed. However as far as any individual kernel is concerned, lower clock speeds are better for battery.
[Samsung Galaxy Nexus] sinik420:
to a certain extent, this requires the phone to be awake longer due to decreased speed at functioning and can actually make battery life worse
[Samsung Galaxy Nexus] TEK112:
Remember, not all Rom's support Long pressing the back button to kill the process. Even if it is included in the ROM, sometimes it does not work. It is best to open up the multitask built in application and close it from there. Passing the back button with minimize (throwing out a loose windows term) the application, but it will still be running.
[Samsung Galaxy Nexus] androidmichael:
But the default on this is 700 and all other kernels are 350 so what does Franco think is better other than a bit of performance
[Samsung Galaxy Nexus] stevessvt:
Me too, and I've got a couple Franco kernels on m computer, but I don't know which ones they are.
[Samsung Galaxy Nexus] sinik420:
Most files are dated by modified date or created date
[Samsung Galaxy Nexus] mike216:
Franco sets your minimum at 700 so your phone can finish tasks quicker and enter into deep sleep quicker. Also for less wake ups. This was much discussed over on his nexus s kernel development and debated
[Samsung Galaxy Nexus] grinch247:
where I am @ now...with alot of phone calls...texting...etc....

I am HIGHLY impressed with #11!!!!
[Samsung Galaxy Nexus] razzbaronz:
I am running Roman's AOKP Milestone 2 and Franco's nightly 11, just tested microphone and it's working perfectly in a sound recorder app. Your problem is unrelated to the kernel.
[Samsung Galaxy Nexus] mrDmola:
First off I want to say thanks for creating this amazing kernel. The first few days for this, I was getting awesome battery life. But, for some reason last night this all changed and I have NO idea what is causing this. To give you an idea what I was able to achieve in terms of battery life, skim through my post of screenshots: (Well this was suppose to be a link to a forum where I posted my observations, but links are not allowed by users with LESS than 8 posts. I was able to get 41 hours of battery life with light usage. PM me if you want me to send you the link).

I'm currently using franco's nightly build #10 + gummynex 0.4.2 with the LTE Nexus

Last night, I decided drain the battery to 0% and charge back up to 100% full. After I was done, I made sure to close the camera and I also decided to uninstall the facebook app and install facebook messenger instead as someone suggested and the facebook app can keep the phone awake unnecessarily. Therefore, I decided to do this. I also added the widget ColorNote to one of my home screens. My wifi policy has been set to sleep only when plugged in for the past few days. In addition Google Location services has been ON the past few days, but for last night I decided to turn that off.

So as a recap, the main things I did was to drain the battery to 0% (until it shutdown) and recharged back to 100%, uninstalled facebook app and installed facebook messenger instead, download and usef as a widget ColorNote, and turn OFF Google location services...

Can you tell me why this morning, I turn on my phone only to find it at 83% battery left??? Android OS was at 50%! The CPU total was around 40 mins and the keep awake time was almost an hour... I have no idea what caused this change all in a sudden. Before I was getting less than 1% battery drain an hour with this rom and kernel set up (proof is in the thread link I posted above). Now all in a sudden it's back to how it was before when I was on stock except worse! Now I thought for sure, ok... this has to be the facebook messenger app causing this. Well, I stopped the application from running this morning and closely monitored the battery life throughout the day. It sits at 69% now with probably only 10 mins of on screen time and Android OS taking around 48%. Therefore, the battery drain is still going.

I'm just completely clueless now and have no idea what has caused this sudden change. This is disappointing because this should not even be an issue at all. Any help would be greatly appreciated because I have no idea what to do. I just want a setup that works well and doesn't cause any surprises randomly.
[Samsung Galaxy Nexus] jknisley:
This is with the LTE Gnex?
[Samsung Galaxy Nexus] luckylui:
Silly question im about to ask but, is this the verizon nexus forum? Im getting my gnex in a couple days wanted to hit the right thread :P

Thanks!

hTc T-Bolt
[Samsung Galaxy Nexus] TEK112:
Yes, CDMA is Verizon, GSM is not.
[Samsung Galaxy Nexus] luckylui:
Thank you sir :)

Just switched from poo sprint lol

hTc T-Bolt
[Samsung Galaxy Nexus] superkeest:
this is the galaxy nexus CDMA section. and the CDMA GN is carried by verizon.

so kinda.
[Samsung Galaxy Nexus] sway40:
It's prolly an app that keeps running download better battery stats it's free on xda in a thread.It'll tell you exactly what's going on, helped me on several occasions.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rsantana:
Color issues

So I just flashed Kernel 18.1 from 17, and when I rebooted my blacks are now looking brown any reason why this might be? I haven't touched any of the color settings btw.

---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------

Anyone have a copy of kernel version 18 I can download to compare with 18.1 please.
[Samsung Galaxy Nexus] luckylui:
Up top. It was a couple pages back..

Thank the man! :P

Sent from my Galaxy Nexus