yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] splus:
Voltages are stock on Franco kernel r217, 512 GPU, and ROM is bigxie completely stock 4.1.1, no mods. Just for Quadrant tests min and max CPU were 1.8GHz, fsync off, force GPU rendering (from Developer settings) checked, and thermal throttling disabled for higher result of the two.

In my normal use I'm on 384 MHz min CPU and 1536 MHz max, fsync on, GPU rendering off, enabled thermal throttling.

My battery life is worse on JB than on ICS, at least with overclocked CPU. I noticed with CPU Spy that with interactive governor on Jelly Bean CPU is practically using only min and max frequencies (unlike ICS, but I guess that behavior helps with responsiveness on JB) and spends much more time in max CPU frequency compared to ICS.

I think that's the reason for worse battery life. On ICS overclocking the CPU to 1.5GHz didn't have much effect on battery life compared to stock 1.2GHz, but on JB that difference is bigger. Probably because JB likes to use max frequency more than it was the case on ICS...

I still haven't tried ondemand on JB, might be much better than interactive for battery life...

EDIT: I just played with ondemand for a few min, and I'm noticing a lot of micro lag in touch responsiveness. It's nowhere as smooth as interactive. This wasn't the case on ICS.

Back to interactive, and probably 1.2GHz max CPU...
[Samsung Galaxy Nexus] ourakot:
hi.i jusr flashed nightly 9.i have one problem...when i am makin a phone call and the screen turns off...then when pressing the power button to wake up the phone nothing happens.the call is still active as well as the phone but the screen is dead.any ideas why is this happening?
[Samsung Galaxy Nexus] sluflyer06:
@Franco

I'm assuming your wanting us to use the default governor you've set (ondemand) with the current #9 kernel?
[Samsung Galaxy Nexus] ourakot:
anyone?my phone is unusable at the moment
[Samsung Galaxy Nexus] StuMcBill:
I have posted in the thread over at MoDaCo, since I thought he would be more likely to check that.

No reply yet though, give it time, he will fix it.

I guess its something with his 4.0.3 compatibility pack.

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] daandman:
Oh, well I guess that explains why my battery life is always so bad, lol. I never put the thing down, I know the screen kills battery but didn't realize it was normal for it to drain THAT much.
[Samsung Galaxy Nexus] ro_explorer:
Apparently no one has this issue .. I know for sure I don't have it ...
[Samsung Galaxy Nexus] aron7awol:
Pull your battery and go back to 1.2 if you were OCed.
[Samsung Galaxy Nexus] franciscofranco:
Thanks everyone for the useful feedbacks. Time to fix what needs to be fixed.
[Samsung Galaxy Nexus] marc.tulley:
Earwax over the proximity sensor?

Jokes. Dont have this issue myself. Sounds more ROM related anyway.

FRANCO - Running like a peach as usuel mate sorry no useful feedback from me!
[Samsung Galaxy Nexus] energie:
I have a problem. My battery wont charge more then 99% even if i leave the phone plugged overnight?

Could be a rom or kernel problem?
[Samsung Galaxy Nexus] daandman:
My phone froze & I had to pull the battery 3 times on nightly 9, twice in the last like 20 minutes. Went back to 7.1 for now.
[Samsung Galaxy Nexus] Redflea:
Had my first sleep of death this morning. Running this kernel totally stock no over clock, default governor. Was browsing this forum. Turned off screen, turned back on would not wake up, had to pull battery. I'd never had any issues at all with the previous builds.
[Samsung Galaxy Nexus] Redflea:
Had my first sleep of death this morning. Running this kernel stock no over clock, default governor, but did enable cpu 1 turn off. Was browsing this forum. Turned off screen, turned back on would not wake up, had to pull battery. I'd never had any issues at all with the previous builds.
[Samsung Galaxy Nexus] ourakot:
i am running bigxies rom..had no problems with nightly 8.back to 7.1 for now.
[Samsung Galaxy Nexus] franciscofranco:
What kind of lag is happening on screen on? It takes a while to screen or the system is slow after screen on?
[Samsung Galaxy Nexus] energie:
just some milliseconds to bring the screen on, no lag or slowing effects after that.
[Samsung Galaxy Nexus] franciscofranco:
That always happened as far as I know. I'd rather have it do that and wake up at max frequency to prevent any type of lag caused by waking up the system, than having it wake up instantly but the system waking up lag like there was no tomorrow.

Although I just changed some code, maybe it helps a bit, expect #9.1 in some hours.
[Samsung Galaxy Nexus] DarthPiggie:
Anyone notice a higher than usual temperature while running nightly #8?
[Samsung Galaxy Nexus] Redflea:
I haven't seen this issue. My screen comes on very quickly when I press the power button.
[Samsung Galaxy Nexus] jhericurls:
If you have no problems with 8, why are you flashing back to 7.1?

Been running 9 for over 8 hours and not a single issue. On the Kang Rom.
[Samsung Galaxy Nexus] theMaDHakkeR:
I'm actually finding 217 to be much more stable at higher frequencies that other released. I'm able yo stay at 1.8Ghz with no reboots, and the the phone could never handle it before.
[Samsung Galaxy Nexus] theMaDHakkeR:
Just want to add I'm also trying to get max Payne working. Can someone please point me in the right direction. I'm not seeing anything in the OP.

Thanks.
[Samsung Galaxy Nexus] The Gingerbread Man:
6. GTA3, FIFA2012 or any game of the type isn't opening?[/b]

A: Flash this on CWM http://xdaforums.com/showpost.php?p=27515966&postcount=20011

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stark_br:
Do you guys recommend to flash this kernel?

I'm now on default one.

Any advice or no worries?

Tks

Edit: there are 4 files on op, which one should I go for?
[Samsung Galaxy Nexus] AdrianE46:
Mine never ramps up the cpu unnecesarily. Might be a different problem than you think. Maybe reflashing the rom or kernel with a dalvik + cache wipe could help? Or a full wipe +reflash? I dunno. Worth trying i guess.

Sent from my Galaxy Nexus.
[Samsung Galaxy Nexus] franciscofranco:
If you take a few minutes searching you'll see that this kernel is a good choice. Theres plenty of information around for all your needs.
[Samsung Galaxy Nexus] krolla03:
So when i installed JB4.1.1 it reinstalled the stock Kernal. Before i reinstalled your Kernal (#217) i messed around with android to see what kind of changes were done to Android. I noticed that Google now was working perfectly when saying "google" to have the voice command come up.

Then i installed #217 GPU512 and now when i say "Google" it doesnt work. So im assuming its because of your Kernal.

Not sure if this wa already reported.
[Samsung Galaxy Nexus] franciscofranco:
The kernel doesn't touch any of that. I think you have to enable a card or something, I have no clue but I've seen it explained somewhere in the thread or somewhere else.
[Samsung Galaxy Nexus] stark_br:
I did read about, but this stuff around SuperUser that I did not get...
[Samsung Galaxy Nexus] timbck2:
That's great but really has nothing to do with the point.
[Samsung Galaxy Nexus] LNJ:
Sorry if this has been mentioned before but I can't seem to get OC to persist after reboot!

Any ideas?

I have the Trinity kernel app as well but cleared data on it just in case it was conflicting. Didn't make a difference!

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] franciscofranco:
Superuser apk from ChainDD isn't working optimally with JB, and I recommend using SuperSu or flashing the supersu.zip from Chainfire's thread.
[Samsung Galaxy Nexus] laureanop:
This or supersu from the market open it and update the binaries

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] stark_br:
Done Boss :D

Installed and running good! Tks
[Samsung Galaxy Nexus] mikeandjaimie:
Mines the exact opposite lol 217 is the only one I CAN'T run above 1.5, but 216 is loving 1.8
[Samsung Galaxy Nexus] nikulogical:
Those running r217, are you guys getting better/equiv screen on battery life to the stock JB kernel?

My tests (one day of similar activities on each) gave me much worse screen on time for r217.
[Samsung Galaxy Nexus] craigbailey1986:
Has nothing to do with the kernel. You must have turned the setting off in Google now. To turn it back on do the following:

Open Google now

Menu

Setting

Voice

Turn on hot voice detection

You should be good to go.
[Samsung Galaxy Nexus] craigbailey1986:
Are you over clocking past stock 1200? If so chances are you will see a decrease in battery life with an increase in performance
[Samsung Galaxy Nexus] nikulogical:
Nah, stock settings or 1344 max dont remember. I'd retest it but I can't for a few days, I work long days without an access to a charger.
[Samsung Galaxy Nexus] craigbailey1986:
Ok. When you get a chance going to need to know the CPU setting as well as power mode.. and any setting you have checked in the Franco app
[Samsung Galaxy Nexus] nikulogical:
I'm not new to franco's kernel. On ICS, 1200 or 1344 max gave me the same battery so I stuck to 1344. On the new jellybean I'm not sure which one I did. Most likely was 1200 since I was testing it against stock. No full power mode, extra settings, undervolting, none of that.
[Samsung Galaxy Nexus] franciscofranco:
Try to use Ondemand, it will be much less agressive than interactive that is pushing the device for the smoothest experience.
[Samsung Galaxy Nexus] herzzreh:
How come CPUSpy says that deep sleep is not used with 217?

A reboot fixed it. Go figure...
[Samsung Galaxy Nexus] krolla03:
there is no "hot voice detection"
[Samsung Galaxy Nexus] LNJ:
I see it on mine!

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] krolla03:
Weird this is what mine looks like
[Samsung Galaxy Nexus] LNJ:
Maybe it's regional!

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] ballaz:
Had the same issue so running stock for now. Even after a clean wipe with just stock Franco settings, no deep sleep. It worked fine on bigxie's 4.1, don't know what happened with 4.1.1. Still awesome kernel and will try again when Franco release His next iteration.
[Samsung Galaxy Nexus] Exostenza:
Anyone else experiencing the WiFi just stop working all the time? I'll have to disable it and reenable it to get it going again. I don't remember this being a problem on ICS.
[Samsung Galaxy Nexus] krolla03:
i figured it out. if i turn accessibly off/on for light flow it for some reason gets rid of Hotword all together.
[Samsung Galaxy Nexus] theMaDHakkeR:
I had to change the language from English UK to English US to get mine to work.
[Samsung Galaxy Nexus] nikulogical:
try enabling wifi pm fast
[Samsung Galaxy Nexus] digver:
Do you have it set to use English as the language? That could be the problem.
[Samsung Galaxy Nexus] mike216:
Its your buggy rom not the kernel. Try to get a gps lock then back out and close maps. This is a known issue on buggy JB roms

sent from my precious nexus
[Samsung Galaxy Nexus] Tommy_FIN:
I'm getting weird idle drain with r217. I lost 8% in 7 hours. No kernel wakelocks. With r210 drain was 2% in 7 hours. With r217 I was using interactive and r210 I used lazy if that matters.
[Samsung Galaxy Nexus] mike216:
I loose this now and I think it's because my battery is taking a ****. I come to this conclusion because I got the same results on ICS with many different kernels and now on JB. I just ordered a new battery to see if this is the case

sent from my precious nexus
[Samsung Galaxy Nexus] zenzip:
On bixie 4.1.1. clean install no wakelock issue, but volume boost not working.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Tommy_FIN:
I don't think it's my battery. I got OEM 2000 mah extended battery and I got it couple of months ago. So it's technically new.
[Samsung Galaxy Nexus] yankee12jd:
Question OTA franco kernel

Guys, I have a short question. I am on franco kernel with stock IMM76I. Does having custom kernel is obstacle in receiving OTA update to jelly bean? Or should I revert firstly to pure stock (i.e. stock kernel).

Thanks in advance for reply
[Samsung Galaxy Nexus] jaycarag:
I'm not sure but, I think it won't really be an obstacle for you to receive the OTA update. As long as you're not using any custom deodexed ROM then I think you should not worry.
[Samsung Galaxy Nexus] yankee12jd:
Thanks.

Simply I still have not receive OTA whereas other users enjoy new android and I am getting worried...
[Samsung Galaxy Nexus] BrUhNiGGs:
The new update to your app is causing fc's when I switch to any frequency to "maximum frequency for screen off" then I relaunch the app and it is actually set. Also Im not sure if you intended to do this but, I have interactive governor set and when I try to go to governor control it says, "Your governor is not supported by this utility." And if I switch to ondemand, it force closes. Just letting you know if you are aware.

I am running Jelly Belly 3.3 - Android 4.1.1
[Samsung Galaxy Nexus] jaycarag:
You can always flash OTA ROMs found here. :-) If you want the stock experience, you can try flashing Bigxie's JB ROM or Android Revolution HD ROM. Both are now using the 4.1.1 version of Jellybean. :highfive:
[Samsung Galaxy Nexus] yankee12jd:
I would prefer to have stock ROM for the beginning. I tried to flash official OTA via CWM, but I had status 7...so now I am looking for a way to downgrade to original IMM76I kernel (it is a pity as franco kernel is so good....), update to 4.1.1 and then apply franco kernel again...

Or maybe someone has other idea? Or maybe someone can confirm that she/he received OTA on franco kernel simply...
[Samsung Galaxy Nexus] beekay201:
I updated to JRO03C (was on 4.0.4) through source building, found an error (status 7), updated to cwm 6.x, flashed fine this time, now running #217, and man it is butter smooth. Nice, Francisco, very nice.

One more thing, you wont receive OTA updates since you're running a custom kernel/recovery.

Sent from my i9250
[Samsung Galaxy Nexus] ragnarokx:
Same here - app version 5.8, kernel version r217 on Bugless Beast Jelly Bean.
[Samsung Galaxy Nexus] yankee12jd:
I updated to cwm 6.0 (http://xdaforums.com/showthread.php?t=1757146) but it did not work....I even downgraded kernel to stock IMM76I (3.08 from Apr 13) and no success...
[Samsung Galaxy Nexus] splus:
I flashed the JB OTA ROM, and was playing with the stock kernel. I was able to open governor control in kernel app for interactive, but when I switched to ondemand, and later tried to open governor control I also got this "governor not supported" message.

Then I switched back to interactive, but now getting the same message even for interactive when trying to open governor control.

Some bug in the kernel app?
[Samsung Galaxy Nexus] slyzzz:
ROM

What's the best ROM for this kernel? :) Recommend guys thanks!
[Samsung Galaxy Nexus] Treatcon:
Thanks for the update Franco, keep'em coming! With the latest 5.8 and 216/512 the "Turn fsync() on" toggle stays checked for me through reboots. When I uncheck it and reboot it's checked again. I only reboot so often because I'm moding SystemUI and framework-res. Govenor Control also does not open for any scaling governors, not that I use or change anything, but just backing up what was said already above.
[Samsung Galaxy Nexus] dwang:
Unable to set governor control settings with 5.8
[Samsung Galaxy Nexus] farazafs:
Hello

Can i install these two for 4.1.1 android revolution ? what is recommended ?

franco.Kernel-r217-384GPU.zip

franco.Kernel-r217-512GPU.zip
[Samsung Galaxy Nexus] krolla03:
Yes
[Samsung Galaxy Nexus] farazafs:
what version ? 512 or the 384 one?
[Samsung Galaxy Nexus] The Gingerbread Man:
Which ever works best for you

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
I get the same thing after update, gotta be a bug.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tcchuin:
go for 512 one if you wan't better performance

but keep in mind that not all devices can support it and if artifacts occurs, flash the 384 one.
[Samsung Galaxy Nexus] timbck2:
The 384 vs 512 is referring to GPU over clock. Some phones can handle 512 others can't (like mine). You just have to try them to see what works.
[Samsung Galaxy Nexus] farazafs:
And this can be flashed on 4.1.1 ? or its just for 4.1 ?
[Samsung Galaxy Nexus] sam razzy:
Where can I find su zip ? My root is not working

sent from jElly Belly NeXus PrimE
[Samsung Galaxy Nexus] spaceman860:
http://xdaforums.com/showthread.php?t=1538053

[03.07.2012] SuperSU v0.93

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] TyroneLT:
I know this is a pretty general question but with ICS it seemed like the ondemand governor was the most stable and best for battery life for ICS based on my experience, reading this thread and even based on what Franco himself said at one point.

I know JB hasn't been around for long but can it still be said that so far ondemand is the most stable and best for battery life on average or have things changed with JB? I ask this because I've noticed by default the Franco kernel starts on interactive and I'm just looking for feedback from the community.
[Samsung Galaxy Nexus] franciscofranco:
Works for both.

Yep, it's a bug.

Search XDA for SuperSu thread from Chainfire.
[Samsung Galaxy Nexus] farazafs:
Anyone?
[Samsung Galaxy Nexus] LNJ:
Both.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] franciscofranco:
I answered you in the post above...
[Samsung Galaxy Nexus] HuMpS 97 DoHc:
I'm also curious about this.
[Samsung Galaxy Nexus] TEK112:
It is 100000000000% user dependent. Only you will know which works best for you and your habits. You just have to try it and see. There is no easy answer.
[Samsung Galaxy Nexus] noobiekins:
The default governer on jelly bean is interactive, Franco possibly just stuck to the default to see how it handles to you guys
[Samsung Galaxy Nexus] laureanop:
At this point interactive works the best . Even when I bump the up threshold down to 80 there seems to be a tiny hesitation with on demand.

On a related note , max CPU speed of 1228 yields better results as far as ui smoothness and fluidity than any other higher frequency while on interactive. For on demand 1306 is the sweet spot.

As far as battery life , the difference between both governors is negligible. Same can be said about the 384 and 512 gpu speeds.

Jelly Belly 3.3

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] arhung:
Now, my phone is running r217 512gpu with ARHD 6.0.0, I did some undervoltage for CPU and gpu, running 384/1036 ondemand governor, power save mode that only use one core of CPU and I hope I can get a good battery result for those setting.

Or any suggestion?
[Samsung Galaxy Nexus] laureanop:
So you basically turned your phone into a samsung galaxy one :)

Why why why ?

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] TEK112:
I always wondered the same thing. Why take one of the most powerful phones and castrate it into giving better battery life? That's like buying a V8 and removing two spark plugs to get better mileage.

It's like:

I got 10hrs hours of on screen time!!!!! All I did was turn the screen on to an all black picture, set brightness at 15%, enable airplane mode, shut down one core and set the max frequency to 192MHz.

That's nice, but what happens when you need to make a call or search the web while navigation is on??? Oh, that's right! The phone hot boots or freezes.... awesome!
[Samsung Galaxy Nexus] tcchuin:
limiting maximum frequency to 1036mhz is understandable, but limiting one core only is useless.
[Samsung Galaxy Nexus] franciscofranco:
That made me laugh :)

In about 1h I'll release an update to the app with the power modes FC being fixed and a few changes to the preseted modes, Power Save mode won't turn off cpu1 anymore but instead of 1036 max it will be 729mhz. I don't like the idea of messing with cpu1 anymore.
[Samsung Galaxy Nexus] laureanop:
I hear ya. We're privileged to have a phone that's two OS ahead of 80 % of all android users with arguably the best kernel and rom developers in the land and yet we constantly try to repress the beast inside this phone.

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] The Gingerbread Man:
I used a single core power save mode for a while but now use a duel core limited to 1036 with lazy governor, it runs great

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Also, are we likely to see a 1.7 GHz speed choice in the future? On 217 using 1.8 ghz it reboots after a while and 216 it seemed stable, I'm just curious to see how 1.7 ghz would run really

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CADude:
Those people are definitely crazy, but most people just want to get regular performance with as little battery drain as possible, which is what I'm after.
[Samsung Galaxy Nexus] mikeandjaimie:
I'm curious to know what changes from 216 to 217 made the instabilities for some and improved for others.. I.didn't see anything in the changelog from what I could tell, Though I'm no dev
[Samsung Galaxy Nexus] franciscofranco:
Im probably going to remove 1.9ghz and add 1.7ghz. 1.9ghz is unusable for most of the users.
[Samsung Galaxy Nexus] franciscofranco:
I changed some stuff in the fuse opp. Its some little entries in a table for the voltage dependencies etc
[Samsung Galaxy Nexus] franciscofranco:
Just pushed 5.8.1

5.8.1

* Fixed a bunch of code, errors & one force close when choosing a power mode

* SGS3 settings should persist on reboot now

Will be up as soon as Google refreshes their servers
[Samsung Galaxy Nexus] bat0nas:
Thanks! You are fast with bug fixing :) Force close is really annoying.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
Sorry for the noobie question, but please help me so I can understand better.

I'm running JB. What is the difference between the 384mhz & 512mhz kernel and what is recommended.

Thank you.
[Samsung Galaxy Nexus] TyroneLT:
512 will give you better performance if your phone can handle it. If you experience issues just stick with 384. I switched to 512 and its working great.
[Samsung Galaxy Nexus] mikeandjaimie:
Been asked and answered many times, and but it comes down to gpu clock speed. 512 is a higher oc... Some phones are unstable on the higher clock speed, and so they use the 384 version. The try 512, if you have problems with 512 use 384
[Samsung Galaxy Nexus] Wynnded:
Isn't this info in the OP? I'd look, but....;)
[Samsung Galaxy Nexus] herzzreh:
Hm.. Uninstalled app and now when I'm trying to reinstall it says that package is invalid...
[Samsung Galaxy Nexus] defconoi:
Hey guys how is the battery life on this compared to JB stock?
[Samsung Galaxy Nexus] Tommy_FIN:
I switched back r210 and the idle drain is gone.
[Samsung Galaxy Nexus] mike216:
Does 210 have all the color mods in it? Thanks

sent from my precious nexus
[Samsung Galaxy Nexus] Stretlow:
on pretty much every rom i have ever used with Franco i get roughly 3 hours screen on time with my set up so i use that as a bench.

on jelly I'm getting about 2. I'm testing trinity today to see if it's the JB Rom before passing judgment
[Samsung Galaxy Nexus] Tommy_FIN:
Yes.
[Samsung Galaxy Nexus] lwclam:
Is USB HOST function disable with Jelly Bean 4.1.1?
[Samsung Galaxy Nexus] mike216:
217 is way faster then 210. Both great but 217 is riding lightning

sent from my precious nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
217 has been great, definitely my favourite and amazing now the app is fully functional. 218 I reckon will be really special, another milestone can't be far off although I don't think its possible to get much more buttery smoothness than this already. Even in power save mode transititions are smooth and quick. Honestly I can't think of much to be improved upon which hasn't been mentioned (1.9ghz step remove and add 1.7 GHz step ;) )

My brother has an s3 perhaps if I can convince him to root I'll get him to try Franco kernels too

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mike216:
He's probably a new Android user or else he would have root before making a call. Give him time curiosity will get him sooner or later. No Franco no voodoo (in his case) no way root that *****

sent from my precious nexus