yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aron7awol:
Ok, so it's not that having a lower frequency makes the device wake up more often; it just stays awake longer because it's processing slower. That makes more sense.

Let me do some quick and dirty math.

Using stock voltages:

f*V^2 = 350*1.025^2 = 368

f*V^2 = 700*1.203^2 = 1013

Performance ratio = 2:1

Power consumption ratio = 2.75:1

Well this math suggests 350 MHz is more efficient. Even though 700 MHz is twice as fast to get its work done, it uses 2.75 times more power in the process.

And with the UV values I've been running:

f*V^2 = 350*0.850^2 = 253

f*V^2 = 700*0.975^2 = 665

Performance ratio = 2:1

Power consumption ratio = 2.63:1

Since I am assuming that performance scales linearly with frequency, f, it is clear that any drop in voltage, V, would have a positive effect on efficiency. This would suggest that if we can run at 180 MHz at any voltage lower than we run at 350 MHz, that it would be worthwhile to add the stepping. Performance generally does not scale perfectly linearly with frequency, but taking that into account only favors lower frequencies more.

However, an important thing to consider is that this math is assuming that the total CPU power consumption is proportional to f*V^2, which is not an assumption I'm sure we can make. Does reaching idle state save additional power other than what I'm considering with f*V^2? It very well may. If only there were an easy way to measure live power draw on the Galaxy Nexus. The Nexus One had a great battery chip that could do it.

Edit: Maybe it's time to fire up the Nexus One and do some real world testing to shed some light on this...
[Samsung Galaxy Nexus] TAMIM2007:
Great work

I have in the official kernel

Problem in the yellowing of the screen

And tested all Kernal and still the problem

See here

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

Please fix the problem in a special Version

thanks :)
[Samsung Galaxy Nexus] lynxboy:
What happened to XDA!!! :-(

(Shakes Head)
[Samsung Galaxy Nexus] MultiCulti:
just to let you also know franco:

beamed in through my brain ...

edit:

ok, the gov "ondemond" is faulty on faux kernel :thumbup:
[Samsung Galaxy Nexus] franciscofranco:
I see what you mean, but I dont agree with your test, its good on the paper, but not in the real world. I will answer you better when Im back home.
[Samsung Galaxy Nexus] TAMIM2007:
I did not ask for a problem outside the subject

But said the subject

* Tweaked the default colors - whites are more white, and colors are more Vibrant

Wana and I remember a proposal is like voodoo colors

Need not shake your head :)
[Samsung Galaxy Nexus] WillyWonka23:
I'm running the stock kernel right now. How is the battery life with the latest nightlies? Is is worth the transition over now? I would be fine with a little battery drain. All the features with the kernel look well worth it. :)
[Samsung Galaxy Nexus] franciscofranco:
There isnt Voodoo Color yet, I already told this 40 times.
[Samsung Galaxy Nexus] franciscofranco:
I think I just fixed the high battery drain while idle, been running just fine for the last 4 hours.
[Samsung Galaxy Nexus] ttlycnfuzd:
/me smells a new nightly

:D
[Samsung Galaxy Nexus] Enhanced:
Just wanted to throw my experiences in here too.

With your kernel, my overnight drain (8 hours of sleep) is around 15%. With the stock kernel, it's consistently 4-5%. This is just my experience with the phone idle. Not too sure how the drain is while screen-on.

But I gotta say, 4.0.3 ROMs are smooth as hell with your kernel. Very very noticeable.
[Samsung Galaxy Nexus] franciscofranco:
Not yet ;)

Yes, its noticeable, if I really nailed the drain source, then I'll be happy as hell and can focus my strength to other things.
[Samsung Galaxy Nexus] irishrally:
Franco #6:

Min/Max: 1200/1200

Performance Gov.

Faux #6b2

Min/Max: 1350/1350

Performance Gov.

I don't understand how faux kernel would get lower cpu integer/floating point scores with the cpu running at higher frequencies.

Either way, both kernels are awesome. I still don't see the color changes in Francisco's kernel but maybe my eyes are just bad or I'm expecting a more drastic change like how I have the NS set up.
[Samsung Galaxy Nexus] RonnieRuff:
Sometimes with some 100 times is not enough. (Shaking head)

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] RonnieRuff:
Noticed the same

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] irishrally:
Oh ****, Ronald got a GN.
[Samsung Galaxy Nexus] Danny80y:
Anybody noticed battery drain when out of service? Not sure whats the deal but its a bit odd....
[Samsung Galaxy Nexus] akellar:
Not sure what else you would expect? The phone is constantly working to find a signal.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk
[Samsung Galaxy Nexus] Metallice:
That would make sense considering we are in the GSM section... lol screw those guys over in the cdma forums. Even though I'm with Verizon I like you guys better :)
[Samsung Galaxy Nexus] whatzup282:
Getting awesome battery life on latest nightly.

AOKP m4

r156

Min 192

Max 1036

No hotplug

No UV

Auto brightness on

Stock battery. 1750mAh
[Samsung Galaxy Nexus] ch33kybutt:
dmesg | grep Information
[Samsung Galaxy Nexus] :
MIUI 2.5.4

Nightly 156
[Samsung Galaxy Nexus] splus:
Sounds like you're coming closer to making OC problem free for all, that would be great!

Just some input on this topic.

I just checked and I'm on HW rev 9. I don't know if CPU overclocking has anything to do with GPU overclocking but I can run 512 GPU, no problems.

I don't know if I would have problems with 1.5 GHz or higher frequencies, but I tried 1480 MHz CPU when I installed AOKP which came with Faux kernel, and my phone run without problems even during benchmarks.

I wonder if a small difference in frequency matters a lot or does it all depend on bunch of different settings that make it all work or not...

But whatever it is, it would be great if we can find the exact factors that affect the CPU overclocking!
[Samsung Galaxy Nexus] blackdub370:
SetCPU --> Info --> CPU --> Processor or revision??
[Samsung Galaxy Nexus] CaspaTheGhost:
Yeah, GSM is where its at!

Franco, after a major late night watching the Mayweather vs Cotto fight, yesterday was an 'idle' day for me and that doesn't happen much.

Running 156/384, interactive, 729/1228, SR on and I had 11% drop in 15hrs with all syncs active.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] qballe:
screen time ? 50 minutes ? :p
[Samsung Galaxy Nexus] yyz71:
Nice :)

Sent from M5
[Samsung Galaxy Nexus] blackdub370:
Very nice

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] yyz71:
That is very nice :)

Sent from M5
[Samsung Galaxy Nexus] vndkmr97:
Am a new GN user and am on AOKP rom... after searching the forum and many recomendations , found this kernal .. after download the FRANCO-KERNEL milestone 3.zip (only 3.13 mb) .. how do i flash this kernel ..

1.simply can i flash the zip via recovery from MTP ?

2. or else any other file need to download or flash via recovery along with milestone zip??

correct me if am wrong
[Samsung Galaxy Nexus] Stretlow:
Before you get hunted down by the search police....

Just flash it in recovery pal ;)
[Samsung Galaxy Nexus] maniac2403:
Download it to your SD card, boot into recovery and flash it there :)
[Samsung Galaxy Nexus] ceejay83:
franco, any plans to include touchwake feature?
[Samsung Galaxy Nexus] franciscofranco:
Not really, sorry.
[Samsung Galaxy Nexus] Gahh Its Lee:
Nope he's said that many times.
[Samsung Galaxy Nexus] chakra:
What ROM?
[Samsung Galaxy Nexus] Antob125:
Can anyone help me out? First time using BBS so not sure how to read it. Here's the kernel and partial wake locks attached

http://db.tt/ku5VetdW

http://db.tt/A5ooaRDb

Also some pics

I'm on Aokp M5 and Franco kernel 156 512gpu

Any help would be awesome thx!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] republitarian:
Your biggest wake lock is rijl and that means your service is poor. Try staying on wifi if u can or your phone will drain when searching for signal and data
[Samsung Galaxy Nexus] niallmcg:
using nightly #156 and got a random reboot while screen was off, not sure if the phone was sleeping or not, but the phone continued to bootloop for 4-5mins. wipe dalvik and cache. no luck. flasing an old backup saved me in the end.

anyone else have this problem? or know how to help if so i would greatly appreciate it.

don't get me wrong im not complaining or trolling i looooove this kernel and i understand i was using an experimental kernel but i thought the bug needed to be reported
[Samsung Galaxy Nexus] Antob125:
Thank you! Other than that was there any other big stuff to worry about?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Using 192mhz min cpu freq right?
[Samsung Galaxy Nexus] audibalso:
Very strange. I'm not sure if I some how broke it, but set CPU freq at boot no longer works for me. Never had an issue before. Perhaps its user error just thought to ask the group.
[Samsung Galaxy Nexus] niallmcg:
Re: [KERNEL][GPL][26 APR - #Milestone 3][NIGHTLY - 156] franco.Kernel | 4.0.3/4 |

Yeah is that the problem?
[Samsung Galaxy Nexus] hotnikkelz:
It will appear so. Some phones can't handle the frequency apparently. Troubleshoot it.
[Samsung Galaxy Nexus] niallmcg:
Okay thanks for the help and the quick replies...but it hasn't happened on previous builds and I've been running 192 as min since #151 or whenever it was first introduced
[Samsung Galaxy Nexus] jhericurls:
Whats you voltage for 192Mhz, you can't take it below 800 mV.
[Samsung Galaxy Nexus] franciscofranco:
**** happens. Try 384mhz and see if it fixes your instability.
[Samsung Galaxy Nexus] niallmcg:
I haven't got a manual UV been letting smart reflex to do it for me...its saying 820mv at the moment in Franco's app
[Samsung Galaxy Nexus] niallmcg:
Okay will do... I won't argue with the dev...thanks and sorry for wasting your time
[Samsung Galaxy Nexus] franciscofranco:
If it fixes your problem report back ;)
[Samsung Galaxy Nexus] :
As for me Nightly 151 seems to be the best version for latest releases..
[Samsung Galaxy Nexus] Metallice:
My smart reflex calibrates it to 710mV with no problem. You definitely can go below 800mv.
[Samsung Galaxy Nexus] hawkye:
I lose my signal running 192 min. So I am sticking with 729 min.
[Samsung Galaxy Nexus] niallmcg:
The guy who made your CPU deserves a medal...could you post your voltages please?
[Samsung Galaxy Nexus] franciscofranco:
I lost your previous post about SR calibrating the higher freqs, so I will just reply here.

I have been talking with imoseyon as well about this issue. I think SR is only one problem because with DCC most of the users wont be able to use anything above 1350 without ****ting lags everywhere. So unless we disable DCC fixing SR for high freqs wont solve the problem entirely. Then disabling DCC we have other problems, then we try disabling the trim, which helps, but then again some users device will be unstable. Understand the simbiose that we need to achieve in order to have higher freqs available and working and not **** other users at the same time? ;)
[Samsung Galaxy Nexus] dpaine88:
is there really that big of a need for higher speeds? phone is fast as hell as it is, can't imagine what you need 1.5 for aside from benchmarks

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mazubo:
Would anyone be able to help me out as to know if these wakelocks are too much? And if so, how to go about minimizing them? Thanks kindly!

:-D
[Samsung Galaxy Nexus] kolyan:
Thanks, donated.
[Samsung Galaxy Nexus] eivi91:
Got severe wakelocks with R156 today. Especially one called NetworkLocationLocator. Anyone know what this is?

Tried flashing R121 as it was the only one I had on my phone, and the graph in deep sleep flattened. NetworkLocationLocator is still present, but not as much.

Got 45 minutes of screen on time at 50%.

Using ondemand 729min/1366max, no hotplugmod or anything else.
[Samsung Galaxy Nexus] schizophrenia:
networklocationlocator probably relates to some map related app (e.g. Google map) which periodically fetch your location (e.g. GPS if it is on, or Wifi location)

a side question which I would like to borrow your example

I know a lot of users do recommend min 729 as it puts the phone to sleep faster by finishing tasks faster. But a lot of users play musics with the phone which will keep the phone awake for quite a long time. in this case, would a lower min CPU (e.g. 192 or 384) be more battery efficient than higher min CPU (e.g. 729)?
[Samsung Galaxy Nexus] Treatcon:
Don't leave us Franco!! :eek:

HTC Releases Kernel Source for the One X :eek: :eek:

:cool:
[Samsung Galaxy Nexus] lynxboy:
Held off from commenting about battery life earlier, as I like to give it a few days with varying activity to benchmark it. Anyway, I've been getting such awesome battery life since the 15x kernels and amazing performance since the experimental patches were removed.

Using 384 GPU I've managed to hit over 5 hours screen time on a quiet day (not many calls/txts, wifi pretty much all day) and always reaching 4 hours without fail on normal days with calls, 3G, music etc etc. I have a 2000mAh battery and run 192/384-1228 undervolted with SR.

I know some people want to overclock their phones to ridiculous frequencies just so they can open the Franco Kernel app that microsecond faster, but please don't deviate too far from the current set up right now as it's my Nexus has never felt better.

Regards.
[Samsung Galaxy Nexus] :
Which one you use? stable ir the latest nightly ?

Taptalked by GNexus
[Samsung Galaxy Nexus] rmcsc:
OK, so I got the app, hooray for me.

Flashed 156 and set minimum to 192 while leaving max at 1228; scaling governor is interactive.

Don't know how to undervolt yet, so after I brush up on how that works, I might work with them. Any recommendations?

[Addendum] GPU @ 384
[Samsung Galaxy Nexus] lynxboy:
156 latest nightly.

Regards.
[Samsung Galaxy Nexus] RayGarden:
Hi Franco,

I recognized that when i lower the Max CPU frequency then 1344 mhz, my Facebook app doesn't work properly on Nightly 156.

Can you, or anybody else, confirm?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] nklenchik:
r152 = My M3.5

This gives me the best battery out of the most recent kernels. Had to switch back this morning when in 8 hours I got a 13% idle drain on r156
[Samsung Galaxy Nexus] :
Is there any app to see how hot the mobile gets ?

Taptalked by GNexus
[Samsung Galaxy Nexus] Metallice:
That may be the case, and i agree that all of threse things are interconnected, but for (most) everyone who has tried my build and insta-rebooted when using 1.5/1.65, disabling smart reflex has allowed them to run these freqs just fine.
[Samsung Galaxy Nexus] dropback:
Francos App:)
[Samsung Galaxy Nexus] Flukester69:
Ya I noticed that too, maybe be fixed in next build.
[Samsung Galaxy Nexus] nklenchik:
Lets hope so :P I actually had to look back in my posts to see if it was 152 or 154 haha
[Samsung Galaxy Nexus] CaspaTheGhost:
So, here's the rest of it. Good performance and decent life.

View attachment 1047276

View attachment 1047278

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] lynxboy:
Thinking back I also hit 5+ hours screen time on 152, but performance is better since the experimental patches were removed, especially at lower frequencies. Might have to give it another go sometime though.

Regards.
[Samsung Galaxy Nexus] superbobup:
Was this due to any wake lock? I lost 6% over 6 hours (when I usually lose 1%) and had an extremely large "BTLowPower" wakelock which I also had last time I had this big drain. The wakelock seems to appear randomly.

I'm still testing to see if it is kernel, rom, or (most likely) user issue...
[Samsung Galaxy Nexus] oned:
Pls what kind of settings do u use for these résults ? Am on AOKP M5 + R156/384gpu. Radio xxla2

Thx

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] :
My mobile gets much more warm then usually like with the Milestone 3 !

Taptalked by GNexus
[Samsung Galaxy Nexus] heo_con184:
I think r156 solved the heat problem in previous builds.
[Samsung Galaxy Nexus] :
I dont know I just can tell what I feel :( Flashed back to Milestone3 and everything is fine...I usually never flash nightlys, now I know why. :rolleyes:

Milestone 3 is perfect runs great for me.

I like that app !

Taptalked by GNexus
[Samsung Galaxy Nexus] rmcsc:
How's the experience with the hotplug feature enabled? Is battery life that much better?

Edit: Generic Hotplug, not the governor.
[Samsung Galaxy Nexus] franciscofranco:
SR disabled by default isn't ideal at all :/
[Samsung Galaxy Nexus] johno168:
hi franco i just emailed you.... :)
[Samsung Galaxy Nexus] Akik:
Hi Franco, I'm new with your kernel, which one do you recommand for daily use, milestone 3 or r156? Thanks man!
[Samsung Galaxy Nexus] franciscofranco:
r156 is working better in my opinion. I should release r157 in a few though.
[Samsung Galaxy Nexus] Akik:
Thanks dude. I will give it a try and report back! I'll buy the app too. Thanks for your work ;)
[Samsung Galaxy Nexus] nodstuff:
Looking forward to that release, the battery on 156 is... unpredictable.

Idle drain is higher than normal.
[Samsung Galaxy Nexus] audibalso:
The new 5/07 cm9 "experimental" nightly does not work nice with Franco app / kernel. Set CPU at boot broken, force closures, crazy super user spam. Not asking for help, solved my own, just reporting in case others on cm9 or thinking about it as the new features was tantalizing.
[Samsung Galaxy Nexus] mingkee:
Thanks for your kernel; in addition, I purchased your app for your support.

This app is like one from supercurio, but this one setting sticks even after reboot (a plus).

I don't need any OC/OV fancy stuff but I need color control and USB host mode in order to use USB flash drive.
[Samsung Galaxy Nexus] Akik:
Installed r156 version (milestone 5 rom) and bought the app to set the kernel.

Used this http://xdaforums.com/wiki/Samsung_Galaxy_Nexus/GT-I9250/ROMs/FrancoKernel to make good config. Hope the result will be good :)
[Samsung Galaxy Nexus] franciscofranco:
r157

* Increase wi-fi voltage from 1.75mV to 1.8mV for stability purposes

* Added an extra OPP to link the low 192mhz MPU slot. This will decrease the amount of voltage Smartreflex calibrates this slot

* Few MUSB patches from mainline Linux kernel in hope to fix some derp that was present since 3.0.y.

* Two VFP reverts from previous merged android-omap-3.0 patches
[Samsung Galaxy Nexus] joeyfong:
the voltage for 192 is lower, mine is 710 now, btw, some setting will be reset after flashed the kernel since r156
[Samsung Galaxy Nexus] franciscofranco:
Setting reset? What are you talking about?
[Samsung Galaxy Nexus] Felixpau86:
Auto flash keeps installing 156
[Samsung Galaxy Nexus] Meannekes:
Flashing r157(387) ends in 790mV by 192mhz

r157(512) ends in 710mV by 192 MHz

And flashin r157(only 387) IT says im running r156

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
Thanks for noticing, fixed just now.
[Samsung Galaxy Nexus] stellaryt:
r157-384Mhz 192Mhz-710mV here.

I didn't use autoflash this time and app showed the right version.
[Samsung Galaxy Nexus] joeyfong:
min max freq, governor, color setting, in your apps
[Samsung Galaxy Nexus] Meannekes:
After Franco fixed it here too now.

With r157 all frequencies need 10mV less voltage. Some more battery savings.. great!

And i dont know why, but since r157 i can use 192mhz without any lag!

If i could, i would buy your app a second time. Great work!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] martin.capeletto:
192Mhz-710mV here, using 512.

So far it's working great, will test and report back if anything happens
[Samsung Galaxy Nexus] superbobup:
Governor settings do not stick on reboot intentionally
[Samsung Galaxy Nexus] joeyfong:
how about the otherss??
[Samsung Galaxy Nexus] Sveke:
192-1228 interactive

Just had a freeze/reboot reading the forum.

No reboots on 156 in 3 days use.

Same settings, changed nothing, no undervolt. Just wanted to let you know Franco.

Still running very well regardless
[Samsung Galaxy Nexus] franciscofranco:
Everything sets on boot besides the voltages and governor settings.
[Samsung Galaxy Nexus] rmcsc:
Man, that app is worth it.
[Samsung Galaxy Nexus] franciscofranco:
Understandable, not every phone will handle 192 with the crazy low voltage ;)
[Samsung Galaxy Nexus] Sveke:
Had another one, reverted back to 156.

Yeah mine doesn't like the crazy low voltage.

Oh well, no big deal. 156 was great. All good.
[Samsung Galaxy Nexus] tribaleps:
SMS Center broken

Not sure if it is coincidental. SMS stopped working after flashing #156. Since ICS doesn't have settings to change the SMSC number, I had to do it through '#*#*4636*#*#*'....tried 'retrieving' the number via 'Refresh' but it returns '00' instead of carrier's SMSC number. Tried keying in the SMSC number manually but when I click 'update', it returns 'update error'.

The SIM works on another phone which I have that allowed me to set the SMSC number manually...and even automatically. I even got a new SIM from the mobile operator to make sure its not a SIM card problem.

Flashed #157 this morning...in the #*#*4636*#*# menu, when I click 'refresh', it returned a series of numbers, which I believe is the PDU number for the carrier's SMSC...but I still couldn't send SMSes. Tried refreshing again, and it returned '00'.

Would really appreciate the help on this. Hope I don't have to resort to GoSMS Pro (which supports manual SMSC settings) for the rest of my life.

I'm also on AOKP M5 ROM.
[Samsung Galaxy Nexus] Emilius:
I use to run at 192 with 725mV but I have one reboot with r156 so now I am up to 750mV and its looks good so far. BTW I have turned off smartreflexs and I am using even lower voltages then smartreflex dues. All you need to do is to find out how low your device can go.

r157 looks good so far. Tonight I will do again that idle test. Right now all I can say is r157 382 gpu keep up really strong with screen on and battery. Hmmm, something has been changed. Tnx Franco
[Samsung Galaxy Nexus] joeyfong:
The color multipliers & omap4 gamma interface will reset too, also the min/max freq
[Samsung Galaxy Nexus] wisey18:
I had a similar issue to this. You need to convert the smsc number into hexadecimal then it will work.

http://www.twit88.com/home/utility/sms-pdu-encode-decode
[Samsung Galaxy Nexus] dpaine88:
For me 729mhz as a min is running better than 384 or 192 but with equal battery performance.
[Samsung Galaxy Nexus] tribaleps:
SMS Centre broken

Thanks bro...but that was the first thing I tried..and it says 'update error'.

I've checked the PDU code through and through...
[Samsung Galaxy Nexus] stellaryt:
r157 -1% 2hrs without use (2G mode only).

--

I use lazy or interactive in most days.And I found my phone would not awake(Battery - History deatils) without screen on,but it always awake itself without screen on in lazy.Although it didn't waste more battery,it still weird for me.

I saw betterbatterystats,nothing special,everything seemed fine but just awake.

No other different with my phone,just change the governor,and found this weird thing.It's not a big deal,just strange.:o
[Samsung Galaxy Nexus] monkey hung:
I saw the change log on 157 and I believe Franco said he reverted back to the OMAP patches? On 156, without the patches, my battery lasted a while. Now on 157 my battery is at 73% with 2 hours phone time and 53 minute screen time with low brightness and on airplane mode
[Samsung Galaxy Nexus] monkey hung:
And ondemand
[Samsung Galaxy Nexus] wisey18:
Weird, it worked for me. Good luck.
[Samsung Galaxy Nexus] nklenchik:
Really? That's strange but to each their own
[Samsung Galaxy Nexus] jcmm11:
Reverted back to 156.

192/1344 interactive, sr

Playing angry birds, reboot, data partition corrupted, had to restore nandroid + titanium (nandroid 2 days old)

I like 192 and 156 is running great for me. Might try 157 again but bump the minimum, although for my normal usage 192 is good.