yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zeppelinmad4:
No problem. I have no problem resetting it after each boot. I just figured I would bring it to your attention since it definitely seemed like a bug. Thanks.

---------- Post added at 11:23 AM ---------- Previous post was at 11:21 AM ----------

Yes, with the Galaxy Nexus' processor, it is pointless and wasteful to use a screen off profile.
[Samsung Galaxy Nexus] Musik847:
Sorry if somebody's asked this: latest miui is stable, just released today.

Is it safe/ smooth to run with vicious miui?
[Samsung Galaxy Nexus] mfish123:
Lol....you got it....charging up to 100% now.....then I'll get poked and prodded for a day and report back
[Samsung Galaxy Nexus] EyeOfTruth:
Your right the screen off profile really is more harmful then good, on my phone atleast. I posted in this thread earlier about using screen off setting the screen off to force it to 350. The problem is the processor has a built in feature that puts it into a deep sleep state and potentially turns off one cpu if you have hotplug enabled. From what appeared to be happening with me the phone never went into the deep sleep state and used more power.
[Samsung Galaxy Nexus] nycdiplomat:
Anyone have a link to #13? I'm on #12 right now.and I want to upgrade but I've been seeing a lot of ppl posting their issues with 13.1. Thanks in advamce
[Samsung Galaxy Nexus] Clarkkent434:
Question on hotplugg is there a way that CPU1 does not turn on with screen on till CP0 load hits a certain threashold.
[Samsung Galaxy Nexus] franciscofranco:
I think it's possible, but that is really a bad idea.
[Samsung Galaxy Nexus] Gwanatu:
So I've been trying everything to get my battery life better and it seems like this one thing is still holding me up. Android OS shows abnormally high usage, and betterbatterystats shows the following:

I turner off the screen and lock sounds as is widely reported to fix the issue and that definitely helped, but that is way too high. Any ideas? I'm running the 13.1 kernel and Kang build 19.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TEK112:
I agree. I can foresee hot boots or really bad lag.

---------- Post added at 02:59 PM ---------- Previous post was at 02:57 PM ----------

Have you tried the google+/facebook fix? then can cause the high usage. Also, depending on the ROM there may be a bluetooth bug.
[Samsung Galaxy Nexus] Gwanatu:
I don't use Bluetooth on this phone, but I'd be willing to give whatever fix it is a shot.

As far as Google+/Facebook, I don't have Facebook sync on, and I forced all syncs to only sync once per hour through this ROM. That should include Google+ but again I'm willing to try anything at this point. 40% drain in 3 hours is awful. What's the fix?
[Samsung Galaxy Nexus] Clarkkent434:
I know that another developer had his hotplugg like this but I loose most of my battery to the screen on and I have the brightness set at 7%.
[Samsung Galaxy Nexus] TEK112:
First try unsyncing FB and G+ and then try the bluetooth fix.

I remember with Codename Android that there was a bug where you had to turn on and off bluetooth when the ROM boots (every time). It was killing the battery behind the scenes.
[Samsung Galaxy Nexus] Clarkkent434:
So the bluetooth fix is you had to turn on and off bluetooth when the ROM boots (every time)? I have the same audio issue on AOKP rom but I just ignored it.
[Samsung Galaxy Nexus] TEK112:
I was not affected, but there were some who were. However, I have done clean installs for every ROM I have tried so orphaned data may be their issue.
[Samsung Galaxy Nexus] revolt1:
question

have you guys notice a slow charge with this kernel
[Samsung Galaxy Nexus] zeppelinmad4:
There's going to be a slow charge on any Galaxy Nexus kernel as it's one really big battery that needs to be charge. But no, I haven't noticed a "slower" charge than other kernels out there.
[Samsung Galaxy Nexus] JustusIV:
Is CIFS going to make it back in?

This is a feature i am starting to play with and it looks like you pulled it way back in December because of battery drain. I am using it on other kernels and don't mind if it is using my battery.
[Samsung Galaxy Nexus] Gahh Its Lee:
Bought the app. I'm feeling the kernel. Love the undervolting ease. But I was trying to figure out where I'm stable my phone rebooted and most apps didn't work had to restore with titanium.
[Samsung Galaxy Nexus] MasterRy88:
Didnt see this in the OP

Is the GPU overclocked or stock?
[Samsung Galaxy Nexus] EyeOfTruth:
9th December

* Added two versions - one CPU/GPU OC free and another with CPU/GPU overclocked

* Slightly undervolted

* Add dynamic writeback feature from 3.1

* block: strict rq_affinity

* vmscan patched up with some fixes

* arm: Allow CPU-supported unaligned accesses

* Graphical glitch should be now fixed

It should be OC.
[Samsung Galaxy Nexus] sinik420:
that is quite old, there is currently only one version posted lol im curious too
[Samsung Galaxy Nexus] bowsersoulstar:
We could likely go on the assumption that if he didn't explicitly mention reverting back to something, it's been there since inception. This is based on the fact that Franco tends to note that in his logs if he reverts back to something.
[Samsung Galaxy Nexus] sinik420:
i dont understand the relevance, there was two kernels one with gpu oc and one without. it doesnt mention which he dropped, so i dont know what the assumption would be. if it wasnt oc'ed last time, i would understand but he dropped a kernel and the changlelogs dont mention which
[Samsung Galaxy Nexus] bobby janow:
The kernel is 1200 / 700 by default. You can go up to 1350 if you so choose.
[Samsung Galaxy Nexus] Gahh Its Lee:
OK so I've discovered just because you can run undervolted to a certain point doesn't mean you should click start at boot or whatever the option is. This is a warning to other. My phone went to start stalled out and then wouldn't start at all wouldn't even go to my boot screen. Idle what I did beyond too low of voltages even though I kept the voltages being ran for at least an hour.
[Samsung Galaxy Nexus] sinik420:
Lol good lesson. And this is why some devs don't allow it
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea... I finally found some stable voltages for me. They are a good bit lower than stock so I'm happy I played with it I use titanium so I didn't lose data anyway. Just wasted time.
[Samsung Galaxy Nexus] Gahh Its Lee:
Also if I use the color thing do I just set all 0 to go back to normal?

Edit... can't figure the colors out.
[Samsung Galaxy Nexus] JustusIV:
are there any plans to put CIFS back in the kernal?
[Samsung Galaxy Nexus] zeppelinmad4:
Good lesson. I always run a stress test in SetCPU after every time I change the voltages.

---------- Post added at 07:55 AM ---------- Previous post was at 07:54 AM ----------

Franco replies to posts in the thread once every one to two days. Please give a little time before posting this a third time.
[Samsung Galaxy Nexus] JustusIV:
I Apologize......

Forgot this was geared at one person and not just anyone could answer.
[Samsung Galaxy Nexus] TEK112:
He was being nice when he posted that.

Duplicate posts clutter threads and make it harder for people to search. If anyone had an answer they would have given it. However, it is Franco's kernel and we have no way of knowing his intentions. If you want to know about CIFS and feel as though a proper time has elapsed since you first posted, PM Franco and ask.

Please accept this as the constructive feedback it was meant to be.
[Samsung Galaxy Nexus] Gwanatu:
I've found that I can only undervolt on 350 and 700mhz. Anything above those speeds just crashes after a few minutes no matter how little I undervolt them (even only 25mV under!). I currently have 350mhz at 750mV and 700mhz at 900mV, stable for days.
[Samsung Galaxy Nexus] MasterRy88:
Yeah I understand that the CPU has that OC im wondering about the GPU. I mean im not gonna abandon this kernel just becuase it doesnt have it im just very curious as its impossible to tell from the OP
[Samsung Galaxy Nexus] gnocchi_ny:
What rom are you running with these results? Thanks.
[Samsung Galaxy Nexus] Gwanatu:
Yeah that's downright INCREDIBLE! I must know what your settings are and what ROM you are running!
[Samsung Galaxy Nexus] aohus:
He was on wifi most of the time. look at his screenshots... i can go 4hours too with LTE disabled as well if need be.
[Samsung Galaxy Nexus] GermanGuy:
I apologize if this has been asked before. What settings of the Franco Kernel offer the best compromise between battery savings and performance? I am running AOPK ROM. And do I need to install the Franco updater APP from the market to achieve those settings? Thanks
[Samsung Galaxy Nexus] sinik420:
Everyone asks this and never gets an answer, its all based on how you use the phone. Try figuring it out for yourself, since you're the only one who can! Good luck
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm using conservative and getting great performance which is odd... I bought the app and enabled hot plug which helps battery life a lot. I also under bolted a bit but I don't recommend that.
[Samsung Galaxy Nexus] dincfool:
Everyone asking about what settings to use i have a little funny for you not funny for me story from last weekend.

Im at a bar and a girl i kind of know (like literally a 9/10 no bs) comes up to me and asks why we haven't hung out since the last hockey game i saw her at. Shes like "do you have my #?". I reach to give her my nexus, she types the first 2 numbers in and the phone kind of freezes up. NOOOOOOOOOOOOO. So you know what she does, pulls out her iphone and calls me from it....ugh saved but still. . . My settings that night were like conservative 350-1200 or something like that. . Since then i've kicked onto ondemand 700-1200. . How embarrassing haha.

Running AOKP M2
[Samsung Galaxy Nexus] EyeOfTruth:
Currently with 32% used and on battery for 6hrs and 57% of that used by voice calls. Now that I'm done with most of the calls for today Ill goto the gym and stream music for 90 minutes to 2 hours, thru bluetooth, I still probably have 7 to 10 hours. And I never use wifi and I leave bluetooth on.
[Samsung Galaxy Nexus] hajabooja:
Running 13.1 on AOKP #19 (just updated to #20) with 700/1200 and the Conservative Gov. Did not touch the voltages at all. Thanks Franco!
[Samsung Galaxy Nexus] franciscofranco:
That's a bit embarrassing :p

I've been working the last days on the #14 build. It's taking a little while longer than the usual because I'm being a real pick as I want it to close to perfection. Blame my high standards =)
[Samsung Galaxy Nexus] mike216:
High standards for great work and high expectations!
[Samsung Galaxy Nexus] dincfool:
Good stuff my friend, I like the app and the constant updates.
[Samsung Galaxy Nexus] jbdan:
That is AOKP build #19

Here ya go :)

AOKP #19 franco kernel #13.1 conservative governor

1850mAh standard battery

WIFI on 18.5 hrs - 4G on 3.7 hrs

Screen on auto-brightness

15 min of voice calls (not normal I usually talk much more)

2 email accounts push notify

Weather updating every hour

Sync'ing browser, google+, contacts, calender, music

Surfed the net for 3hrs 30min

3 widgets on 3 screens (android weather, calender, music)

Cell signal at home is -105dbm to -115dbm. While on 4G it was around -90dbm

The only change I made in setCPU was lower min freq to 350MHz

I did my "LTE Only" test the day after those screenies and got 2hrs 47min screen on time. Wifi makes a difference as we all know. Problem for me is, my cell signal when I am at home hovers around -110dbm. I feel I could easily get 4hrs screen on while on "LTE only" if my cell signal was green throughout the graph. Moving soon, maybe I'll have that chance ;)
[Samsung Galaxy Nexus] Gahh Its Lee:
Am I supposed to be leaving the min at 700? Mines set at 350-1200 conservative with hot plug enabled and its faster than I could even want.
[Samsung Galaxy Nexus] jbdan:
I think you're supposed to set it where ever you want that gives you the best results.

I'm so happy with my battery life and I use the 350MHz slot no hotplugging enabled and it's dreamy =)
[Samsung Galaxy Nexus] EyeOfTruth:
Electronics are very sensitive and no 2 are a like. So two phones could look identical but one person running 350-1200 could get great results and the next 700/1250 give them the best. Its really trial and error and find what works best for your phone. Plus remember its also going to depend on how many running services you have and everything else. I get better battery life by running 700/920 then running 350/920 but I was able to undervolt my 700 to 900mv which has it running about the same as 350.

The other thing to look at if you have 350mhz uv to 850 and run 700mhz at 875mV or 900mV there isn't probably enough of a power save to notice.
[Samsung Galaxy Nexus] Znomon:
Edit: I just read the thread and realized that my comment is useless, and not helping with the point you were trying to prove. I will keep it here just in case your hunger for knowledge of everything overcomes you. Haha.

My useless post:

What you may not be aware of... I have been running 350mhz @ 750mV stable for 5 days now. 750 is a huge improvement from 850-900
[Samsung Galaxy Nexus] Gahh Its Lee:
So I have been running the same undervolting for a day or so now. And I had to restore apps when I hit under volt my phone keeps freezing and crashing it worked at those voltages twenty minutes ago.
[Samsung Galaxy Nexus] Wicked4u2c:
Love your Kernel and have seen battery improvements however, these random reboots are getting annoying. I'm not UV if anything I'm running 350 / 950 with hot plug enabled. I get about 3-5 a day.
[Samsung Galaxy Nexus] EyeOfTruth:
Actually that goes with my post because I tried to run my phone at like 350 @800 mv and 700@ like 850 and my phone rebooted within a minute. I have not tried to run 350 @ 800 to see if that was stable on my phone. Its great to have people post what works for them but people have to remember what works for one may or may not work for another.
[Samsung Galaxy Nexus] GermanGuy:
Does this Kernel allow GPU overclock like Faux's Kernel? I purchased the Franco app, but don't see this listed.
[Samsung Galaxy Nexus] zeppelinmad4:
They don't necessarily conflict with one another but I've noticed it's best to just stick with one. I still have SetCPU installed as I like to use it fro stress tests when playing with undervolting but I just you Franco's app for tweaks to the kernel.
[Samsung Galaxy Nexus] TEK112:
To elaborate a bit more, having them both installed won't cause an issue. However, you can only use one at a time to mess with frequencies and voltages. Otherwise they will try and fight each other.
[Samsung Galaxy Nexus] zeppelinmad4:
Yes, that is basically what I was trying to say. It's fine to keep both installed, just only use one for changes.

On a side note, I commented a couple pages back on how Franco's app wasn't showing the correct values for undervolting and applying "set on boot" would cause deep sleep to not function. I would just like to state that with the latest release of the app in the market, using "cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table", I notice the values do stick after a reboot and that deep sleep is still enabled. Thanks for the fix, Franco.
[Samsung Galaxy Nexus] Gwanatu:
This phone is so weird, because it's the only phone I know of where wifi drains LESS battery than cellular network. I have mine on 3G all the time to save battery unless I'm trying to download something large, otherwise it's not worth my time. Battery is getting better, I've tweaked everything I could find/think of using betterbatterystats and I'm sitting at 53% after nearly 5 hours of pretty heavy use. That's great life, almost as good as my G2 now!

I'm Running 13.1 on AOKP build 20, set to 350/1200 with Conservative gov. I posted my voltages earlier. I'm not synching Google+ or Facebook, and I made sure Words With Friends and Hanging With Friends are not using their stupid buggy and battery hogging notification system which was probably a huge issue for me from what I can tell. I'm also using the power saver mode in AOKP to delay sync to only once per hour.
[Samsung Galaxy Nexus] TEK112:
Just wanted to mention I am running CNA 1.2.0 at Franco's 13.1, still not getting deep sleep unless I open and close the camera at boot.
[Samsung Galaxy Nexus] PapaWangsta:
Thanks for every1's help!!!

:)
[Samsung Galaxy Nexus] zeppelinmad4:
Are you undervolting and have set on boot enabled? I wasn't getting deep sleep with those settings even after closing the camera but Franco's newest app update seems to have fixed it.
[Samsung Galaxy Nexus] MasterRy88:
I too would really like to know this. Maybe Franco can shed some light on the situation..... :p
[Samsung Galaxy Nexus] threepio:
gonna use this kernel. Just downloaded the app.
[Samsung Galaxy Nexus] aquariumdrinker:
Hey everybody, threepio is going to use the kernel. S/he just downloaded the app.

Sorry. Bad impulse control.
[Samsung Galaxy Nexus] TEK112:
Nope, running bone stock. I was getting deep sleep, but only after opening and closing the camera.
[Samsung Galaxy Nexus] threepio:
thnx brahmosapian.
[Samsung Galaxy Nexus] Gahh Its Lee:
Undervolting is the devil... Went from stable to randomly unstable... Then my battery was going down on my charger and jumping all over. Then I decided to give my last known stable settings again and boom perfectly fine... WHY YOU HATE ME PHONE??
[Samsung Galaxy Nexus] franciscofranco:
Ok #14 is up =)
[Samsung Galaxy Nexus] zeppelinmad4:
Just flashed #14, thanks for the build. Since there's a long explication for what the conservative governor does, I was hoping that someone can explain the difference between the four different governors and why one would choose one over the other. You can get a vague idea by the name but I was hoping to get a better idea of exactly what each does.
[Samsung Galaxy Nexus] GooTz66:
Hey Franco. First time loading up your kernels and had a few questions:

What governor do you recommend as well as min settings?

Does the deep sleep/camera bug still exist? If so does the camera need to be opened then closed after every reboot?

**Just got a random reboot while typing, just before it happened the screen brighness lit up then device rebooted :confused:

Also WIFI doesnt seem to be working now, has this been an issue?
[Samsung Galaxy Nexus] franciscofranco:
http://www.setcpu.com/#7

Just use the defaults, I set whatever I think it's best for everyone!

Dunno about that camera bug yet, but I think it's not there anymore.

Random reboot? Are you undervolting? I'm undervolting and I have no issues.

About the wifi...I never had anyone reporting that, ever, so I'm 100% sure it's on your end.
[Samsung Galaxy Nexus] GooTz66:
No undervolting and as for the wifi I had stock on there before loading up #14 and it was working fine and after kernel flash I couldnt get it to work for anything. I will keep playing around. Thanks for your help
[Samsung Galaxy Nexus] DarkGruf:
I had a boot loop too after installing #14. No undervolting. Restoring nandroid now.
[Samsung Galaxy Nexus] mike216:
I flashed way too many kernels today but I had to try this and holy **** its fast as **** I just hope battery holds to after a few charge cycles

BEST DAMN PHONE BECAUSE WE HAVE THE BEST DEVELOPERS! ROUND 2
[Samsung Galaxy Nexus] PapaWangsta:
Just use the defaults, I set whatever I think it's best for everyone!

Hey Franco, what do you mean by default? In English please! :)
[Samsung Galaxy Nexus] Znomon:
*error* please ignore.
[Samsung Galaxy Nexus] winner00:
He means use it how it comes. Don't change any settings. Just leave it. Default is the Conservative governor at 700-1200mhz.
[Samsung Galaxy Nexus] aquariumdrinker:
I had a bootloop after wiping Dalvik and installing 14. I re-flashed my prior kernel and am not having problems now.
[Samsung Galaxy Nexus] zeppelinmad4:
You're the best. Thanks for the link.
[Samsung Galaxy Nexus] DarkGruf:
Wiped cache and dalvik cache too. Just I restored backup instead reflashing 13.1. I had no way to get out of loop ==> battery pull.
[Samsung Galaxy Nexus] DirtySimpleClean:
#14=WOW, fast, smooth, waiting for battery :D
[Samsung Galaxy Nexus] franciscofranco:
Just re-uploaded it, I reverted some patch that I hope it was causing the reboots/bootloops in some devices.
[Samsung Galaxy Nexus] PapaWangsta:
Sweet, thanks winner00!!! :)
[Samsung Galaxy Nexus] mark manning:
Everyone should take a day and give this a shot as well. Its kinda awesome

http://xdaforums.com/showthread.php?t=1414876

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] doublea500:
I got the wifi issue too. TOok a bit of googling (research...) and this is what worked for me. Shut your phone off, take the battery out. let it sit for like 5 minutes. put it back in power the phone on and shazam.
[Samsung Galaxy Nexus] winner00:
Yep something is messed up in #14. I installed it and it booted up fine. I then redownloaded it when you said and now it bootloops. Guess I should have stayed on that first #14.
[Samsung Galaxy Nexus] MasterRy88:
Hmm I installed before franco said he messed something up and im fine, I was gonna flash the new one but now im scareddddd
[Samsung Galaxy Nexus] mark manning:
Try fauxs kernel, that will never happen with him

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] winner00:
There's no need for you come in here and dis franco and sell fauxs kernel.
[Samsung Galaxy Nexus] GooTz66:
First of all its not cool to come into a devs thread and promote another devs work. Second, its even more BS to bash a dev who works his ass off for the community. Get lost TROLL!!!!!!!
[Samsung Galaxy Nexus] mark manning:
Not bashing by any means, I have nothing but admiration for Franco. Just giving honest true feedback to help others who don't understand otherwise out. Trust me I have been around a long time and help a lot of people out constantly.

There was never offense intended for you Franco

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GooTz66:
Could have done that in a better and more appropriate way!
[Samsung Galaxy Nexus] luckylui:
Sticking w the first round on #14 and no reboot!!! :) first time trying this kernel too. Usually run faux or stock. I did change my governor to on demand as that is the best governor no matter what people say. Its called on demand for a reason lol.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] EyeOfTruth:
You cant say it won't never happen. All it takes if for a a bad upload which can happen. Besides it could have also been a bad download. About the only thing extra I wish franco would do is include a MD5 hash of the upload so we can check to see if we have a good download. Also We do not know if the guy had voltage set at boot and the new kernel might not like. If the person has sent on boot voltages, which lets be honest is not a good idea when there are as many updates for this kernel which is nothing against franco its new and to be expected, it could have been to low of voltages and if thats the case there is no way to state that those voltages would have been to low unless his kernel doesn't allow undervolting. There are lots of reasons that could have caused the bootloop and none of them would be francos fault and could happen to the other kernel.

You can say it would never happen cause it is always possible.

But thats why I make a nandroid backup and I have the pervious kernels so if something happens I can quickly revert back no harm no foul.
[Samsung Galaxy Nexus] doubleojon:
Bootloops and a curve ball

So I got the dreaded boot loops, and did a battery pull, and tried rebooting into bootloader/recovery. For some reason I'm in "Odin Mode", with a different bootloader screen, as well as a message saying "Downloading... Do not turn off target!!" I've been waiting for quite some time, and this message is still being displayed. I cannot access the Recovery option, as "Start" is the only option. WTF happened here, and how do I fix this?

Edit: Nevermind, I just wasn't holding both buttons down.
[Samsung Galaxy Nexus] jjrudey:
Boot loops here
[Samsung Galaxy Nexus] Gahh Its Lee:
So the conservative gov now only uses min and Max settings? How well does it stay at the lower?