yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sishgupta:
I am getting amazing battery life with Franco's Kernel 7.1 and AOKP Build 11.

The CPU spy wasn't reset for this battery but it does show relevant information.

4 Hours of screen on time, I took some 1080p Videos, lots of facebook and twitter, texting, some google maps with full GPS, some games, lots of web surfing, a couple of phone calls. I have 5 accounts syncing, wifi, bluetooth. Auto brightness. No CPU undervolts or underclocks I just kept all of that at default.
[Samsung Galaxy Nexus] adamleerusse:
Wow, that really is good battery life. There either must be something wrong with my phone or me ha. I'll buy the app and flash 7.1. I'll report back with results!

Thanks for the help!
[Samsung Galaxy Nexus] dajmanjt:
Franco imo has fixed the voltage problems with his latest stable release for his lean kernel... Would love to have the voltage working on your next release if that's something that could be incorporated :) thanks for everything you have done. Love your kernel
[Samsung Galaxy Nexus] franciscofranco:
New nightly is up. Enjoy please and provide all the feedback possible.
[Samsung Galaxy Nexus] Spronx_:
Bought the app - would just like to confirm if any wipe is needed when flashing new kernels?

I was under the impression that cache and dalvik should be wiped, but the app says just flash new kernel...
[Samsung Galaxy Nexus] Dr_Ownage:
You doing anything special?
[Samsung Galaxy Nexus] franciscofranco:
Your challenge succeeded, I laughed :)
[Samsung Galaxy Nexus] rogersnm:
I think I've finally gotten there and perfected the voltage settings:

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1175 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
384 MHz: 725 mV

I'm running 384 MHz min and 1536 MHz and I've tested it with the wheatley and interactive governors (extensive general use + scaling stability test). 192 MHz doesn't want to play ball for me so I'm just not going to use it.
[Samsung Galaxy Nexus] franciscofranco:
Thats with SR disabled right?
[Samsung Galaxy Nexus] rogersnm:
Yep, with an extra init.d script to disable it earlier in the boot cycle.
[Samsung Galaxy Nexus] krex:
Nice work! Would be nice if SR could use this values... :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Giving these ago, stable for a couple of minutes so far. I forgot to turn off sr first and had an instant reboot, now its so far good. Thanks for taking the time in finding these values

Sent with a shake
[Samsung Galaxy Nexus] bigeyes0x0:
@rogersnm: Did you UV IVA and Core, too? They are kinda high if you disable SR for them or did you just disable SR for MPU?
[Samsung Galaxy Nexus] metalspring:
Going to give those voltages a try...I doubt they will work since my gnex is touchy about voltages sometimes

I don't have much to lose though since I'm fairly certain I've had data corruption from messing with the voltages earlier
[Samsung Galaxy Nexus] rogersnm:
IVA:

266 MHz: 960 mV
113 MHz: 825 mv

CORE:

512 MHz: 1025 mV
384 MHz: 1025 mV
307 MHz: 1025 mv
153 MHz: 825 mV

I'll do some work on the CORE voltage but without any way of testing the IVA's reliability I'll probably leave them as they are.

These are only very rough values set from SR before I disabled it, far from optimized.
[Samsung Galaxy Nexus] jhericurls:
Check out this post, its a good starting point.

http://xdaforums.com/showpost.php?p=26468950&postcount=1614

The settings in the link doesn't work for me, they are too low. Makes my phone unstable, sound gets mess up.
[Samsung Galaxy Nexus] :
@franciscofranco,about a toggle in your app for disable thermal limit (or increase the temp limit)?

http://xdaforums.com/showthread.php?p=27059944#post27059944 :D

Thanks!;)
[Samsung Galaxy Nexus] rogersnm:
Curious, that link (and indeed the file) contain 4 voltages for IVA, whereas franco's app only contains (the lower) 2 voltages.

My new core voltages are 850/850/800. 800 mV for 384 MHz caused a screen freeze (although adb still worked), 825 mV caused slow down, 850 mV seems as slick as always. I think I'll stick with those settings for CORE, now for IVA.
[Samsung Galaxy Nexus] CaspaTheGhost:
Yeah, perfect combination.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Yes it's planned. It requires a few kernel modifications, so I'd say I'll have it ready in 1 or 2 days depending on the time I have :)
[Samsung Galaxy Nexus] jhericurls:
You need to use terminal or buy the GLaDOS app to access the other voltages.
[Samsung Galaxy Nexus] jhondidfool:
ignore this :P
[Samsung Galaxy Nexus] nodstuff:
Hey Francisco, I posted this a good few pages back and I'm not sure if you saw it and I was just wondering if it would be of any use to us.

Its a test bedalus did in regards to memory allocators.

http://xdaforums.com/showthread.php?t=1696284
[Samsung Galaxy Nexus] rogersnm:
@Franco is this an intentional decision by you to leave them out?

I can overwrite the highest voltage value using terminal but as soon as I overwrite the second highest (1291 mV) it instantaneously resets to 1291 mV.

---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------

Seriously?

Essentially SmartReflex attempts to automatically calibrate the MPU/IVA/CORE voltages but it doesn't do a fantastic job and you can still gain battery improvements from manual overvolting.
[Samsung Galaxy Nexus] bongostl:
Hey Franco--

Any clue why your kernel won't work with Boot Manager? Any other kernel works fine, but when I have yours installed on one of my sd-card images, it won't run properly (it either creates a boot loop, or sometimes it just won't allow that image to see the rest of the SD card). I assume that this is due to the SD card tweak that you include.

This means that I can't, for instance, run Paranoid Rom as an image, because it includes your kernel.

ANy thoughts would be appreciated!
[Samsung Galaxy Nexus] rogersnm:
If the sdcard tweak is the issue (and it probably isn't) then you can overwrite the sdcard binary with one from another rom (eg. aokp)
[Samsung Galaxy Nexus] bongostl:
I would assume that the sd card tweak is the issue...I can't imagine what else would make Franco work differently from the rest of the kernels available...especially since it manifests itself by that particular install (whatever rom has franco) not being able to see any of the sdcard other than its own install).

How could I overwrite that prior to installation? would I modify the zip file in some way? Any advice would be appreciated!

(and I wish that this weren't a problem... I hate that I have to run other kernel's on my other installations).
[Samsung Galaxy Nexus] rogersnm:
I'm unsure of how Boot Manager... manages things. Essentially yes, you need to find a way to overwrite the file. It's in /system/bin, I leave the rest to you.
[Samsung Galaxy Nexus] bongostl:
fantastic! Do you know what file it is exactly that I'm looking for in /system/bin ?

Edit: dumb question! The file name is 'sdcard' doh!

Edit 2: Worked like a charm! For anyone else having problems: you can get franco's kernel to work fine on roms with boot manager by replacing the /system/bin/sdcard with the file from another rom (I used AOKP...worked great).
[Samsung Galaxy Nexus] Erofich:
hi

i have some problems, and think it's kernel related

so, rom is ParanoidAndroid

i'm using usb host feature, and when disconnecting usb-stick, sd card automatically disconnects too (i dont know is it really exists inside of nexus), and "usb storage ejected please insert another storage device" appers in notification bar. Only reboot helps to close this notification

Andrew
[Samsung Galaxy Nexus] Theshawty:
I don't think the reception to this problem will be positive, I'm afraid, since ParanoidAndroid is CM9-based.
[Samsung Galaxy Nexus] :
Yes!,ok thanks for the reply ;)

I do not bother you more with that,it was just for know and take your time this is not the most important thing ;)

In any case thank you for taking it into account ;)

And maybe make a warning,or you'll have 100 posts about "I enabled the thermal limit toggle (or something like that,depends on what you spell it)) and now my CPU is at 90°C","is it normal?","I tick your new toggle,run a few bench at 1.53Ghz and now my CPU is at 95°C,franciscofranco is it normal?","franciscofranco my phone runs hotter since I enable the new toggle!",etc,etc... :D:p:D

I think you know what I mean :D:D:D

:)
[Samsung Galaxy Nexus] metalspring:
Franco, for those having issues with data corruption from random reboots can they manually force fsync in terminal? (Especially if trying to work out custom voltages)

I found an fsync.bin in /system/xbin so could anyone use that option somehow to force fsync?
[Samsung Galaxy Nexus] rogersnm:
I can't figure out these IVA voltages, I'm running 600/600/750/750 and everything appears to be fine :\
[Samsung Galaxy Nexus] jhondidfool:
Like a charmn :DçShadowgun runs smooth as butter and no reboots.

EDIT: Talked too soon :/
[Samsung Galaxy Nexus] rogersnm:
My current config:

MPU:

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1175 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
384 MHz: 725 mV

IVA:

Voltage 4: 750 mV
Voltage 3: 750 mV
266 MHz: 600 mV
113 MHz: 600 mv

CORE:

384 MHz: 850 mV
307 MHz: 850 mv
153 MHz: 800 mV

I'm happy with CPU and CORE but IVA is suspiciously low so I'm trying to find a good way to stress it atm
[Samsung Galaxy Nexus] nikulogical:
Have you done any tests regarding differences in governors?
[Samsung Galaxy Nexus] rogersnm:
With respect to stability or battery usage?
[Samsung Galaxy Nexus] jhericurls:
Them setting are extremely low. When I set it too low I get a popping sound when playing sound. Also get loads of lag when I receive a phone call.
[Samsung Galaxy Nexus] nikulogical:
Both and performance? For some reason wheatley has been finicky for me.
[Samsung Galaxy Nexus] The Gingerbread Man:
Grab your headphones, stick on some music and crack it up :D

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I've got spotify playing at max volume and it's fine :\, any other ideas?
[Samsung Galaxy Nexus] xorob0:
I tested it, but no problem with 350 and 400mv. Those are very low and no problem, I think this won't test de iva voltage

Edit :tested with 300mV for both slot, that don't work.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] The Gingerbread Man:
Flash video or you tube perhaps. I'm copying your settings as you post and all stable for me so far.

Also can I just say,

Google

Y u no make nexus like this in the first place :D

Sent with a shake
[Samsung Galaxy Nexus] gdmlaz:
using ur setting everything seems to be running smooth on my end also thanks for the settings :D
[Samsung Galaxy Nexus] rogersnm:
Are you also setting Voltage 3/4 or are you just doing 133/266 via franco's app?
[Samsung Galaxy Nexus] mert2go:
@franco what gcc version are you using to compile ?
[Samsung Galaxy Nexus] xorob0:
It made strange sound with iva at 100mV but work well with 200. It's very mysterious.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Antob125:
@Franco I must say after a few days with #180 I must say I've had the best battery life and performance on 729/1229 512gpu Wheatley gov.

Oh and by the way this is a great game Germany vs Portugal. But still rooting for my team tomorrow. Forza Italia!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Um sorry don't quite understand your question. I'm basicly just copying you bro, I just don't have 181 and running 384 version

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
Under IVA in Franco's app it only shows 133 MHz and 266 MHz, however in the voltage config file it actually has two voltage levels above this that can be set with GLADoS' app.
[Samsung Galaxy Nexus] jhericurls:
franco's app doesn't have Voltage 3/4 IVA settings. So you can't just copy the settings as there's no way to enter them.
[Samsung Galaxy Nexus] gparmar76:
Did a freash install of Bug less Beast with r181 today...I was able to use 512gpu with 1536 CPU speed with no issues...great work Franco...it just keeps getting better every day...I was planning on sticking with M4 for a few weeks...that plan just went out the window ;)
[Samsung Galaxy Nexus] rogersnm:
Pics attached to better explain :)
[Samsung Galaxy Nexus] jhondidfool:
I can't drop that much on 1228 MHz (I end in 850 for 192, on a clean scale), and my IVA are 800 and 950; also my CORE 384/512 is on 1050 (freezes if less than 1000, on 1K gives artifacts) ... but still pretty cool. Your UV helped mine a lot!
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah sorry my bad I was reading 3/4 as three quarters. I'm using Franco's app to change the two slots I can

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
Yeah my bad for writing it in a daft way lol, I don't spose you have shadowgun installed? I get some strange kmesg errors when I first start the game regarding IVA, even with stock voltages.

<6>omap-iommu omap-iommu.0: iommu_get: ducati qos_request
<4>omap_hwmod: ipu: failed to hardreset
<6>omap-iommu omap-iommu.0: ducati: version 2.1
<6>rpmsg_omx rpmsg6: conn rsp: status 0 addr 101
<4>omap_hwmod: iva_seq0: failed to hardreset
<4>omap_hwmod: iva_seq1: failed to hardreset
[Samsung Galaxy Nexus] The Gingerbread Man:
Its fine now I know what you meant I understand in was just like wtf but also just been watching a movie so was only half concentrating on what I was reading. I don't have shadow gun, my one and only game I have installed is gta 3. Is the game trying to change your values back if its coming up saying failed to hard reset or even reboot you?

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
Everything appears to be fine, no freezes or glitches, and the voltage levels don't change, I just get the random kmsg errors.

ps.
[Samsung Galaxy Nexus] franciscofranco:
4.4.3.
[Samsung Galaxy Nexus] Diger36:
These are my settings. Running for 24 hrs with different governors and no instability. Several combinations, 192-1536 and 729-1536. This rocks!

Thanks Franco for a fantastic kernel and rogersnm for getting me on track...

EDIT: BTW: Francisco: I'm sorry for the outcome of the match tonight... As a Dutchy I can relate tonight ;-)
[Samsung Galaxy Nexus] Gucci.Nexus:
Oops
[Samsung Galaxy Nexus] Gucci.Nexus:
I use akop. Where can i find those two widgets?

Thanks, using my Gucci Nexus on XDA premium
[Samsung Galaxy Nexus] metalspring:
Franco, are your latest builds made with the linaro toolchain?

I've heard imo's latest is and I was wondering if yours was as well?
[Samsung Galaxy Nexus] nodstuff:
I think he said before that linaro's optimisations are in userspace and not kernelspace. i.e. only the roms benefit.

This whole linaro thing is interesting though, cm are thinking of using it, liquidsmooths next release will be built with it and rascream too.

exciting times in androidland.
[Samsung Galaxy Nexus] Theshawty:
after roughly three to four days of GLaDOS kernel testing, I am now back on Franco kernel. Damn, it's a notable difference between the two ^^

This being the better choice for me, that is.
[Samsung Galaxy Nexus] nodstuff:
Welcome home. ;)
[Samsung Galaxy Nexus] metalspring:
Yeah, but apparently the leankernel uses it so it has to do something for the kernel?

I'm tempted to try out the cm9 kang built with it though...
[Samsung Galaxy Nexus] fatappel:
Don't want to go off topic but you must buy frano's app which comes with the widget. Well worth the small donation for his hard work. Then enable navigation bar widgets under settings/rom control/navigation bar/add new widget. Must have latest aokp b38.
[Samsung Galaxy Nexus] Gahh Its Lee:
Hope aokp get built with it :)
[Samsung Galaxy Nexus] Meannekes:
From where do you know that, with liquid 1.5 , and the next rascream android? I only know cm9

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] SupWiz17:
I have been having problems with the system info widget the past two days. I have never had a problem with it not working before. Is this a known issue or is it just me? I'm on the cm9 nightlies and the widget won't refresh for me when i tap on it like it normally would. I really like having that widget. Anyone know how to fix it?
[Samsung Galaxy Nexus] nodstuff:
Check liquid thread, it says it there and since trinity thread is rascreram support thread rascarlo posted there saying it.
[Samsung Galaxy Nexus] superbobup:
Not sure if I understand ROMs completely, but I think rascarlo said future rascream will have it solely because AOSP will have it (since rascream is built off aosp, I think)
[Samsung Galaxy Nexus] Gucci.Nexus:
1) i am having troubles with it set as my nav bar widget (long press back button). the system info displays, however, the height is too small, so all the numbers are not properly displayed. i tried changing the height dpi, but that didn't help. any ideas please?
[Samsung Galaxy Nexus] spaceman860:
Reboot your phone

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] Gucci.Nexus:
thanks i tried rebooting, but nav bar toggle widgets is still too small
[Samsung Galaxy Nexus] spaceman860:
Did you try resetting the widget

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] Gucci.Nexus:
i am sorry about having a few questions as i try to figure this out.

1) i set my scaling governor to 'interactive' but everytime i reboot it goes back to wheatly. anyone know how to make it stay as interactive?

2) if anyone can please reccomend their full settings, that would be great. For example: max cpu? min cpu? cpu/iva/core undervolt? disable SF? ... any other settings that may help, or check boxes I should change?

cheers. thanks Franco, and all supporters!

---------- Post added at 05:34 PM ---------- Previous post was at 05:30 PM ----------

thanks. just tried resetting the widget. then i had to add new nav widget again. the toggle window is still too small. :confused:

EDIT: i got it displaying properly now. i added a second widget, when I swiped to the second one, then swiped back, the window became proper size. thanks for your help
[Samsung Galaxy Nexus] spaceman860:
My settings SF on I get 4+ screen on time and about 20 hours on battery

View attachment 1118643View attachment 1118644

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] Gucci.Nexus:
any way to put all settings back to default? i started changing some of the CPU Undervolt settings, and now my phone is freezing/rebooting.
[Samsung Galaxy Nexus] fatappel:
Just go to manage applications and clear data. As for widget, it works everywhere on the fly in the correct size.

View attachment 1118761
[Samsung Galaxy Nexus] SupWiz17:
I was not understanding this new widget in the navbar function but now that I see it I think it's awesome. Can you add a widget to every soft key?
[Samsung Galaxy Nexus] metalspring:
Google should have made the navbar like this to begin with...custom number of soft keys, reordering them, custom color and now the widgets with a long press...oh well maybe it can be stock in jellybean lol

Sorry for the off topicness of this post
[Samsung Galaxy Nexus] spaceman860:
One key brings up Widgets then you can swipe for more Widgets

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] wkh1113:
I have already change my colors multipliers setting,but after reboot my phone,it will revert to the default setting. How can I solve this problem?
[Samsung Galaxy Nexus] fatappel:
You can pick any soft key of your choice but only one. Then you have to Swype left and right to select. I only have music and franco. Don't need any others but these two are mighty useful. #hardtohate

View attachment 1118913
[Samsung Galaxy Nexus] Gucci.Nexus:
i keep trying to mess around with the cpu and undervolt settings, but I must be missing something that needs to be changed, because my phone keeps freezing and rebooting when I hit 'apply values'

still hoping someone can be kind enough to please share step by step directions to all the settings they change in franco's kernel, to make it the most effective and stable that they know how to.

cheers,
[Samsung Galaxy Nexus] nikulogical:
Anyone getting stuttering when typing with 384 min and wheatley?
[Samsung Galaxy Nexus] simms22:
most likely either your phone doesnt like to be undervolted or you are undervolting to much. take as small as steps possible when changing the default voltages, up or down. find out what your phone likes. every phones perfect voltages are going to vary, and not every phone can undervolt. besides, undervolting too much can cause more battery drain than not undervolting at all.
[Samsung Galaxy Nexus] Gucci.Nexus:
thanks. i will try with small steps. just wondering if there are any other settings i should change? like for example: set CPU settings on boot (on or off), Set Governor Control on boot (on or off) SF (on or off).

One thing I get the impression I should do (according to most people here) is change my scaling governor to 'interactive.' I did that, but every time the phone reboots, it goes back to wheatley. anyone know how to make it stay on interactive?
[Samsung Galaxy Nexus] metalspring:
To use custom voltages you need to disable smart reflex

Also having the CPU settings set to run at boot is fine since it doesn't auto apply voltages unless you use the widget
[Samsung Galaxy Nexus] Gucci.Nexus:
ok, i will disable smart reflex.

i use the widget... finally got it working on my navigation bar. so, that means i should not have CPU settings set to run at boot, because i use the widget?

do you know how I can make 'interactive' stay set a scaling governor, after reboots?

if I continue having lots of trouble after this, I will go back to stable kernel because I am obv not tech smart enough...yet. and I hate clogging up the forum with my noob questions. thanks
[Samsung Galaxy Nexus] tcchuin:
Don't under clock manually if you want your phone to be stable
[Samsung Galaxy Nexus] metalspring:
Just having the widget active (home screen or navbar) will cause voltages to be set on boot so you could get bootloops, best to wait till you have stable voltages to use it

And having the CPU settings applied on boot doesn't effect voltages, it applies the min/Max speed and governor on boot

Btw, you don't really need to use custom voltages, smart reflex usually does a pretty good job by itself
[Samsung Galaxy Nexus] drawde40599:
Most effective and stable = Do Nothing!! Franco don't spend countless hours doing this for nothing ....;)
[Samsung Galaxy Nexus] despard:
This maybe a dumb question, but can undervolting squeeze heaps of battery for a more decent usage time?
[Samsung Galaxy Nexus] rogersnm:
Ok, lets compare running only the 1228 MHz slot at stock (1320 mV with SR off) vs at 775 mV.

Bit of physics: P=IV, V=IR therefore I=V/R. Put this back in to P=IV and you get P=V^2/R.

If you assume that the electrical resistance of the CPU remains roughly constant given the same load and frequency, you can just simplify 1/R to a constant k, meaning that P=kV^2.

If you call 1320 mV 1 arbitrary unit, then 775 mV is (775/1320) arbitrary units. Putting this into P=kV^2 means that the power usage originally was 1k, and the power usage now is P=k(775/1320)^2=0.345k (to three sig figs). To work out the percentage reduction in power usage you do (1k-0.345k)/1k * 100=65.5%. Therefore by undervolting the CPU you have reduced the power consumption of it by approximately 65% (at that specific frequency, for a specific load etc.etc.).

To put it a way the marketing men would, going back to stock voltage levels would increase your CPU power consumption by 190%.

Of course as I mentioned before, there are several other components to the power drain of your phone; radio, gpu, screen etc. So it doesn't mean your battery is going to last three times as long, but every little helps :)
[Samsung Galaxy Nexus] jnr21:
You are using cm9 based rom, right? Cm9 is not supported by franco. If you want cpu settings stick on boot, you need to set gov, freqs and set on boot via performance settings, not via franco app.
[Samsung Galaxy Nexus] ArmanUV:
except that nobody runs stock voltages with SR off, and very few chips can handle 775. So for 99% of phones, you should compare 1200 (typical SR calibrated voltage) to 1000 (the minimum voltage that most phone can handle).

Redo the calculations and consider the radio and screen and BAM, you get no real life improvements whatsoever.