yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Berzerker7:
I'm not going to turn this into something to debate about, but I believe your input in the matter was highly unnecessary and just of a straight provoking nature itself.
[Samsung Galaxy Nexus] Clarkkent434:
Does the hotplug governer by defualt turn off one of the CPU when screen is off or not? I am confused on the OP.
[Samsung Galaxy Nexus] Gil Smash:
Is anyone able to download the app?
[Samsung Galaxy Nexus] Zorachus:
Great kernel, goes well with Codenamed 1.1.1. Strange thing is, I seem to get better battery life with it on the stock LTE-NExus battery, my extended battery seems to drain faster now ? On the stock battery I could get 4 hours display time, and 9 hours total use, of heavy workday use. The extended battery is at 50% now with 3 hours use so far.

On weekend light use, with WiFi, I can go a full day easily on the stock battery. Oh yeah the color control is awesome, makes the phone pop even more :)
[Samsung Galaxy Nexus] sinik420:
lmao judging by all the feedback I'd say yes. If youre having problems, read the thread at least once and there are many responses
[Samsung Galaxy Nexus] EyeOfTruth:
Are you opening the camera and then closing it? Franco posts that he thinks there is a camera glitch.
[Samsung Galaxy Nexus] Magnus_CA:
I'm assuming you reset battery stats after a full charge on your extended battery? That would be a good place to start if not. I would also be hesitant to rotate in the standard battery with the extended. I'm not sure this or any phone can maintain battery stats by battery and I would expect your results to go further south if you are using two or more batteries in a rotation with different capacities or even two batteries of the same capacity where one is old and the other new.
[Samsung Galaxy Nexus] sinik420:
wiping battery stats is pointless, it does nothing other than cause a placebo effect
[Samsung Galaxy Nexus] UnknownPleasures:
Hmm after a reboot, -10 0 -5 no longer makes it green.

Any who, mine is set to -2 0 -5.
[Samsung Galaxy Nexus] Magnus_CA:
Has everyone that's having the deep sleep issue and running Franco's #12 tried opening and closing the camera app as he directed in the OP? Maybe it's just a coincidence but after reboot and opening and killing the camera app my 350MHz usage is back down and my deep sleep % usage is up again. I noticed I was having high Android OS activity (+40%) as well but I can't verify if that's still a problem or whether the high Android OS usage % is caused by the camera issue.

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

With the flashaholics we have here I don't know that wiping battery stats is pointless especially if those reporting poor battery performance are using those stats to monitor performance.
[Samsung Galaxy Nexus] sinik420:
im speaking on the fact that wiping battery stats does nothing for improving battery life or anything else that would help when everyone says "wipe your batt stats"

source, sure first who links to hope this source is good enough
[Samsung Galaxy Nexus] zeppelinmad4:
I'll try to find it, but there was a blog post by a Google engineer stating that it is in fact a pointless to wipe battery stats.

I still do it because I like taking placebos, though.
[Samsung Galaxy Nexus] sinik420:
already linked in previous post
[Samsung Galaxy Nexus] TEK112:
Wiping battery stats really doesn't affect battery life:

http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/
[Samsung Galaxy Nexus] Zorachus:
I thought wiping battery stats will help tell a realistic reading of the current battery ? Of course I know it does nothing for helping battery life itself.
[Samsung Galaxy Nexus] sinik420:
already linked ;] and were a day late behind rootzwiki who posted it a day earlier lol
[Samsung Galaxy Nexus] zeppelinmad4:
Wiping Battery Stats Debunked

edit:

Guess I'm behind on being behind. Delete the post if need be.

Found it:

There you have it, in the title. Google engineer Dianne Hackborn, who has previously explained Android’s hardware acceleration, took to Google+ again to clarify some myths about the Android operating system. This time, it’s a point of common advice that you’ll see in virtually every FAQ thread about custom ROMs and flashing: wiping battery stats in order to improve battery life.

The reasoning behind that piece of advice was something like this: If you, at some point, did not charge your Android device fully (for example, only to 80%), it would supposedly remember that battery level as “fully charged” – in this case, you’d only ever get to use 80% of your battery, which is of course less than optimal. So, if you wipe the battery stats, usually done in ClockWord Mod Recovery, the device would “forget” the previous level, here 80%, and instead charge to the full 100% once again, thereby re-calibrating the battery. Or, as Hackborn puts it in more technical terms:

The battery indicator in the status/notification bar is a reflection of the batterystats.bin file in the data/system/ directory.

However, as she explains, that’s not the case. Because those battery stats, stored in the batterystats.bin file, are only used to maintain information about what is using the battery when not recharging. That is, it essentially holds the information displayed in the Settings > Battery screen. Nothing more, nothing less. Thus:

It has no impact on the current battery level shown to you.

It has no impact on your battery life.

What’s more, you’ve probably noticed that the battery usage data is reset once you recharge your device anyway. From this you can correctly deduce that the battery stats are wiped as well – every time your device is recharged. More or less every day. If there was any effect, you would’ve noticed it without going into recovery and doing that stuff. Typical placebo, eh?
[Samsung Galaxy Nexus] sinik420:
linked twice lol read back -.-
[Samsung Galaxy Nexus] zeppelinmad4:
Yeah I know. I sat here in the reply to thread screen for four in a half minutes because I don't have posts yet.

Oh well.
[Samsung Galaxy Nexus] Magnus_CA:
Lol to all the links and reposts regarding resetting battery stats. However, while it is clear it has no effect on battery life it may provide value for the flashaholic who is using those battery stats to test and compare the impact on battery performance when flashing new kernels and rom's. It also may affect the results reported from many of the third party battery monitor apps out there.
[Samsung Galaxy Nexus] VinceT3:
Didn't work for me either.. :(
[Samsung Galaxy Nexus] foueddyf:
I don't know if that would make a difference but can you try using the "Music" power mode in Franco's app under the settings tab?
[Samsung Galaxy Nexus] kingoanklebreakn:
I don't think that'll change anything. It has more to do with the volume hack. I usually just put the hack on 0 and it fixes it.
[Samsung Galaxy Nexus] Gahh Its Lee:
I have mine at two with zero issues
[Samsung Galaxy Nexus] kingoanklebreakn:
Maybe I should have clarified, I put it to 0 then back to whatever I want it on and then it works fine. I haven't had this issue on 175 though.
[Samsung Galaxy Nexus] Gahh Its Lee:
Oh lol my bad. Yea I just always leave mine at two with no issues.
[Samsung Galaxy Nexus] smittycg:
174 with trickster mod is awesome, hour and twenty minutes on screen, with 80% remaining. 4 hours on battery
[Samsung Galaxy Nexus] Jordanelliott84:
what is trickster mod?
[Samsung Galaxy Nexus] laureanop:
A new rom that came out last week

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] Droid316:
MOD
[Samsung Galaxy Nexus] laureanop:
My bad . Had it mixed up with something else.

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

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] adambomb6:
I'm having the same problem, but I think you should better state your issues since there are two things in there:

#1 the voice dialer volume is SUPER low on bluetooth. I have found the volume+ app to be helpful. I'm hesitate to try your flashable zip. Can you provide your source?

#2. Bluetooth call volume is low. Best I can do is with volume+, but it's still not great. I think there may be kernel level things that can be done here.
[Samsung Galaxy Nexus] TEK112:
I really think the data drops are radio related and not kernel related. I have been having issues with trinity, IMOs, and francos ever since updating to the recently leaked ones.
[Samsung Galaxy Nexus] kingoanklebreakn:
Anyone else having problems with one of the cores cutting off and then never coming back on? I'm on 175 and once a core shuts off, the only way to get it to cut back on is to change the power mode from none to something like full power.
[Samsung Galaxy Nexus] laureanop:
IMO they're radio AND hardware related. My wife and I run the the same rom and kernel. She misses phone calls (phone doesn't receive the calls ) and drops data and I don't

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] sway40:
Color multipliers still aren't sticking after the update franco, at least for me.
[Samsung Galaxy Nexus] mike216:
Me too and I read many others are experiencing this also. I bet your on AOKP like me. Don't know if it has anything to do with AOKP but most that bring this up are on it?
[Samsung Galaxy Nexus] sway40:
No sir I switched to cm9 for a bit, it's in the app that's the prob.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] upther:
Yeah, I'm on Paranoid Android and the multipliers don't stick for me either.
[Samsung Galaxy Nexus] gaming09:
since updating to the latest franco app my screen goes "dark" its like a dark technicolor type of thing going on frustrating to say the least

edit, got to see the display by turning the brightness all the way up, seems the color picker changed everything to max, couldnt see anything, mini heart attack averted
[Samsung Galaxy Nexus] TEK112:
It is a bug reported on AOKP B38 without Francos app. I would assume that rules out the app as the culprit:

http://rootzwiki.com/topic/26919-torob38-software-gamma-doesnt-stick/
[Samsung Galaxy Nexus] sway40:
Then what could it be since it was two different roms.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] grim281:
Weird thing happened this morning. I woke up and my phone was sitting at the activation screen and now better battery stats keeps fc'ing on me. Running 175.
[Samsung Galaxy Nexus] TEK112:
For people with BT volume issues and voice prompts:

http://rootzwiki.com/topic/16707-mo...e-for-android-403/page__p__431332#entry431332

---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

Wipe both caches.

---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------

I know AOKP grabs some code from CM (it may be limited to just the theme changer). I can't say for sure if it is the devs code or ICS itself. However, the stock people wouldn't know either since they need root to adjust gamma.
[Samsung Galaxy Nexus] mikaeldalc:
OK, I'm running CM9 with Franco's kernel. I have the 2100 Samsung mah battery. Starting @ 100%, my G.Nexus is fully dead by the time I wake up. (7-8 hrs)

I always turn off my data before I sleep.

I have system tuner but haven't messed with CPU speeds.

Any tips or CPU settings are much appreciated.

(Btw I'm running version 175 nightly)
[Samsung Galaxy Nexus] TEK112:
Install CPUSpy from the market. Reboot into recovery and wipe both caches. Reboot normally, after phone fully loads turn screen off for 10 seconds. Then wake phone and open setcpu. You should see the state Deep Sleep. If you do, you should now be OK. If you do not, you may have a rogue app keeping your device awake. For that you can get Badass Battery Monitor or Better Battery Stats from the market.
[Samsung Galaxy Nexus] djk21108:
How did you manage to see the screen to increase the brightness? Mine is so dark I can't see a thing.
[Samsung Galaxy Nexus] nycdiplomat:
Same thing for me, I'm on liquid
[Samsung Galaxy Nexus] seegs11:
Anyone else getting awful battery life on these recent nightlies?
[Samsung Galaxy Nexus] tcsfinest:
Yup 175 drained mine went back to 174 ..
[Samsung Galaxy Nexus] baldcyclops:
Yeah, installed 175 nightly and now my phone is completely dark and I cannot do a ****ing thing with it. Thanks Franco! Hopefully I have an old version sitting on my phone somewhere.
[Samsung Galaxy Nexus] mikaeldalc:
any advice on Good CPU settings for SetCpu to conserve battery? Such as profiles, voltages etc

While still having a speedy phone btw.
[Samsung Galaxy Nexus] stick1300:
Don't be a crybaby. YOU are the one responsible for modifying your phone. Sometimes things go wrong, but you take responsibility when you flash a version that you

know

is an experimental build. Franco does a lot of amazing work for us for free (although some of us donate/buy his app to show our appreciation), so maybe consider that before posting this crap.
[Samsung Galaxy Nexus] baldcyclops:
I do donate. Yes, I realize it is a nightly. But, I don't think it is too much to ask that you make sure the screen actually works before you release it? :rolleyes:

P.S. 174 does the same thing but even worse.
[Samsung Galaxy Nexus] blaine07:
I had the dark screen of death as well. Same as user above, got brightness turned all the way up and installed last backup of application. Scared me about 4/5 to death too haha. But yeah, all is well now.
[Samsung Galaxy Nexus] EDNYLaw:
It was just a bug in his updater app for 4.9.1, update to 4.9.2 and the bug is gone. You can just change your color multipliers while the screen is dark and once you do it'll fix it. It wasn't the kernel, just the app. Fixed, Franco's the man!
[Samsung Galaxy Nexus] baldcyclops:
How is any of this possible when you can't see anything on the screen at all?
[Samsung Galaxy Nexus] laureanop:
If you are trying to be funny... well you're not. If you aren't , this kind of post is useless and it pisses off devs and members.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] EDNYLaw:
You can either turn up the brightness all the way and go into a low light situation and you're able to navigate, the screen isn't off it's just really dim. Or try updating the app through the play store on the web. Oh and something I've also recently learned, check out Franco's thread in the GSM section, it's the exact same as for Verizon but it's a lot more active, they reported the bug a bunch of hours ago to Franco and Franco posted the fix. I've found that if I run into a problem and it's not addressed in this thread, before posting anything, I check the GSM thread and the issue is usually covered over there as well. Not to say I have a lot of issues with Franco's kernels they're the best in my opinion.
[Samsung Galaxy Nexus] TEK112:
Depending on the ROM the drop down has the brightness slider on it or built in. Just drag down and keep sliding your finger under the screen gets brighter. From what I understand, full brightness is just enough to see your way around.

As for bashing his release, I understand your frustration, but bad form. I think we all have gotten too comfortable flashing without backups because of awesome devs like Franco and have let our guard down. So, when the occasional hiccup comes up everyone freaks because they did not prepare for a failure, especially when it works for the majority of people.

Simple rules for flashing ROMs/kernels:

Always make a backup in clockwork

Always verify the MD5 on the device

Always keep another ROM/Kernel on the device as a fall back
[Samsung Galaxy Nexus] baldcyclops:
Yeah, not trying to be funny. I am genuinely pissed. And, if others get pissed then good, they can feel what I'm feeling.

What I mean is that my phone is so dim that I cannot even see enough to go into the settings to turn the brightness up all the way. What I ended up doing was going into recovery and installed a super old version I had sitting on the phone (like r48 or something) and then I could update Franco's app and then re-install 175. Thanks for the heads up!
[Samsung Galaxy Nexus] djk21108:
Thank you very much for that tip! I'll keep that in handy.
[Samsung Galaxy Nexus] laureanop:
Yeah , like Franco thought of how he could f..k with us so he decided to black out our screens... This is all experimental and when **** like this happens we report it and period. ! Verbal abuse not necessary !

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] baldcyclops:
What verbal abuse? And I realize that this wasn't done on purpose. I guess maybe I have a little higher expectations than some, but I think the first thing I would test if I was developing anything on a phone is make sure the screen is working before I release it. I mean, call me crazy all you want to, but that's just basic testing right there.
[Samsung Galaxy Nexus] theneighbor:
I saw this for the first time today when I flashed 175 on slim rom. Go into your color multipliers in Franco app and change them back to 200 or whatever you like. I found they were maxed out. This fixed it for me.
[Samsung Galaxy Nexus] theneighbor:
Dude its a nightly for a reason. Your expectations are flawed. Ease up. Your fighting a losing battle.
[Samsung Galaxy Nexus] DammitCubs:
Yeah. I ran into the same issue. I panic for 2 minutes and then figured out how to fix it.

No biggie. It happens. We are all developers. Not everything is perfect. He's doing us a favor not the other way around.

The world would be less cool without franco kernels
[Samsung Galaxy Nexus] zeke1988:
im running 175 on my phone and nothing wrong with it.
[Samsung Galaxy Nexus] exzacklyright:
Just some dumb questions about francos app:

I'm trying to get the best battery I can get. I'm using interativex governor. 350mhz to 1200mhz cpu.

Under cpu undervolt.. basically i've been undervolting each step by 25mv. Should I just keep doing this till the phone crashes?

right now it's stable at this:

I've also enabled SQlite, turned off logger. Anything else you recommend? Thanks.
[Samsung Galaxy Nexus] djk21108:
Fantastic work Franco.
[Samsung Galaxy Nexus] thenewnoise:
Just flashed milestone 4. Thanks for the awesome kernel
[Samsung Galaxy Nexus] rdoane:
When downloading from the app it is still naming the kernel Milestone 3. Just a heads up Franco. Thanks!
[Samsung Galaxy Nexus] neederishelp:
What (if any) changes are there from 175 to m4?
[Samsung Galaxy Nexus] SocialReject:
Umad?

They're called experimental for a reason son

Sent from the future.
[Samsung Galaxy Nexus] Drew66:
Anyone else having display issues after the kernel application update today?
[Samsung Galaxy Nexus] kuronosan:
Newp.
[Samsung Galaxy Nexus] mike216:
the fix is to go in settings/performance and raise your color multipliers up some
[Samsung Galaxy Nexus] mike216:
Its always amazing how fast Franco's kernels are. Way to early for battery life but for nothing else its simply an amazing performer

I'd also like to add I'm on AOKP 39 and no problems :D
[Samsung Galaxy Nexus] Gahh Its Lee:
39 you say? :P yea im on 38 zero issues what so ever.
[Samsung Galaxy Nexus] mike216:
Was feeling a little happy with performance and life so I decided to throw a little wrench/joke in the comment :)
[Samsung Galaxy Nexus] Gahh Its Lee:
Figured as much idk everyone speaks of bugs I never even find guess I'm lucky
[Samsung Galaxy Nexus] mike216:
I'm doing my normal screen on drain test that ive been doing for a couple years now and so far its looking extremely good! Maybe the best I've seen in a very long time. Maybe better then M2

Ended up at an hour and seventeen minutes at 80%. Damn good and performance is through the roof. Going to chill out on crack flashing and enter rehab for a week or so. Been getting a little to high on Android :D
[Samsung Galaxy Nexus] pluto22:
It still downloads as milestone 3 for me as well.
[Samsung Galaxy Nexus] neederishelp:
Something is define wrong, phone was charging all might, and didn't get to charge fully, because of two kernel wakelocks. Any help? I'm on 175, and works fine for most of the day, until I go to change it
[Samsung Galaxy Nexus] TEK112:
Sounds like you should wipe both caches and flash M4. Then report back.
[Samsung Galaxy Nexus] supernova_00:
I get those exact same wakelocks all the time and I can't figure out what causes them. Some days they are only 5 minutes and other days 5 hours.
[Samsung Galaxy Nexus] laureanop:
The excessive wake locks are a documented and known issue with Google s 4.0.4 release.Google , rom and kernel devs are working really hard at trying to stop these.

That being said , some wake locks are necessary to keep the phone working properly during sleep.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] hlaalu:
Franco or anyone,

I just purchased the kernel updater app, and I can't get anything to download. Is that something on my end?
[Samsung Galaxy Nexus] neederishelp:
Well, it's not letting my phone sleep at all when I get these two
[Samsung Galaxy Nexus] timbck2:
Just rename it to Milestone4.zip and flash away. It's all good.
[Samsung Galaxy Nexus] TEK112:
Did you follow my suggestion?
[Samsung Galaxy Nexus] franciscofranco:
The server must've been overloaded last night, it was hit massively with the large influx of requests. Try again.
[Samsung Galaxy Nexus] jbdan:
M4 is kicking! Great work
[Samsung Galaxy Nexus] mike216:
I would certainly agree that M4 is treating me very well. Great on battery and very fast. Didn't know ondemand could kick ass like this
[Samsung Galaxy Nexus] mike216:
Hi franco, could you throw wheetley on milestone 4 and maybe call it M4+? Thanks loving M4

I can't believe how fast my UI is even on 3G!
[Samsung Galaxy Nexus] djk21108:
Wheatley governor looks amazing. It's really kicking. Great work my man.

We really don't have much need to OC on this phone, but it's glad that 1.5ghz is an option now.
[Samsung Galaxy Nexus] bamfart:
Having the option for 1.5ghz is awesome lol I myself uc to 1ghz. What power mode are you guys using?
[Samsung Galaxy Nexus] spinkick:
Seriously. You are running a nightly. Suck it up.
[Samsung Galaxy Nexus] mursepaolo:
What CPU controller are you guys using for this kernel?
[Samsung Galaxy Nexus] TEK112:
Almost everyone is using Franco's app.

However, most ROMs have performance mods built in (AOKP based) that govern the CPU. Alternatively, you can get setcpu (paid) or CPUMaster (free) from the market.
[Samsung Galaxy Nexus] upther:
Giving the Wheatley governor a shot. I read a couple issues about it not handling streaming music well. I'll find that out pretty quickly today.
[Samsung Galaxy Nexus] pluto22:
180....... Give us a chance to flash M4 first. Lol. :)
[Samsung Galaxy Nexus] jbdan:
I've used 4 different apps over the last 2 years to control cpu. I like franco app better than all of them, by far. It gets updated like every week too :D

+ it's important to donate to/support the ones who make our phones so much more fun to use!
[Samsung Galaxy Nexus] tallnerd1985:
Ditto, I had to revert to Faux kernel until this issue is resolved.
[Samsung Galaxy Nexus] ozymandiaz:
No luck installing 180 (either the 384 or the 512) using either auto flash or download and install through recovery. It hangs on the google screen for 20 minutes or more. Restoring back to milestone 4 is flawless though, so no worries. Going to download on my pc and push it over that way and flash again. Looking forward to trying the wheatley governor. If I can't get 180 to work though, m4 looks to be pretty solid and won't hurt me to stay there for a few days till the next nightly comes out. :)
[Samsung Galaxy Nexus] kuronosan:
This phone is flying.
[Samsung Galaxy Nexus] mroneeyedboh:
I bought Francos app and I enabled both sound settings.But I don't hear a difference...how can I get it to enable?