yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rogersnm:
I bumped 1.2 GHz up to 800 mV, still trying to find that sweet spot.
[Samsung Galaxy Nexus] maddoggin:
R181 nightly not booting for me. Using milestone 4 and I tried auto flashing 181 as well as downloading the flashing and hangs at Google boot screen every time! Anyone else or just me?
[Samsung Galaxy Nexus] rogersnm:
Yeah a few people seem to have the same problem, which ROM are you on?
[Samsung Galaxy Nexus] Tommy_FIN:
My phone gets very hot with 180 and 181. I'm only surfing and it goes over 75 degrees. Didn't notice this with 175 or m4. I'm using lazy with 384gpu, 384min, 1536max, sr on. Also noticed this with lower frequencies.
[Samsung Galaxy Nexus] thoth_19:
I had too bump up 192 by 25v. seems much better.
[Samsung Galaxy Nexus] nikulogical:
Why can't sr calibrate higher frequencies
[Samsung Galaxy Nexus] maddoggin:
Gummy rom! For sprint!
[Samsung Galaxy Nexus] ploep678:
somebody out there, havin' the same problem?
[Samsung Galaxy Nexus] zjmdp:
amazing uv setting, but to my experience,if you turn on SR, maybe freeze very soon
[Samsung Galaxy Nexus] dr.sonic:
I need a litle help :)

I changed voltages more than it could take, so my phone is restarting over and over. What can i do?

Also, what is that SR that you talk about?
[Samsung Galaxy Nexus] rogersnm:
Yeah, SR seems to take some reference from the custom settings, so the lower you set them the lower it tries to calibrate. Which means if you have it enabled with those sorts of custom settings then it tends to crash.

---------- Post added at 03:51 PM ---------- Previous post was at 03:47 PM ----------

If you knock the max freq down to 1344 MHz it should run at a similar temp to M4/r175. The 1420 and 1536 MHz frequencies run at a higher voltage and therefore use more power and thus release more heat.

Turn the phone off, then boot turn it back on and whilst it's on the google screen hold down Volume Down and nothing else. Keep this held down until it boots into the lock screen. That'll boot your device into safe mode which disables all non system apps. Then you can uninstall Franco's app and reinstall it which will wipe the voltage settings, after that just reboot as normal and it should boot back up fine.

If you can't even reach the lockscreen and you get stuck in a boot anim loop, you probably corrupted some core files which means you'll need to restore a backup or reflash your rom. (This happened to me about an hour ago). You can also try booting into the stock rom.

If you got bootloops because you undervolted the 1420/1536 MHz freqs too much then you can get back into the OS by flashing the M4 kernel.
[Samsung Galaxy Nexus] dr.sonic:
I dont have franco app, because I can't by apps in my stupid country.

It boots to liquidsmooth rom normaly, but restarts after few seconds, and i dont have time to change voltages from rom control. Can i do that from safe mode?
[Samsung Galaxy Nexus] rogersnm:
I'm not sure about liquidsmooth, it may still apply the voltages in safe mode.
[Samsung Galaxy Nexus] metalspring:
Try flashing milestone 4 since it doesn't have the high cpu slots or try flashing a completely different kernel...either one of those should either reset the voltages or at least let you boot into the ROM
[Samsung Galaxy Nexus] dr.sonic:
I will try it now. If thats not working, i have nandroid backup from before i flashed r181.

---------- Post added at 05:18 PM ---------- Previous post was at 05:07 PM ----------

I can't boot in safe mode, phone gets stuck on android, but it's not frozen, the light is going over and over text.
[Samsung Galaxy Nexus] opethrocks:
I have the same prob, no matter what i set blx to it charges to 99, no lower or higher
[Samsung Galaxy Nexus] rogersnm:
Yep that means one of more of your core files was corrupted, you'll need to go back to a nandroid. I've had that twice now :(
[Samsung Galaxy Nexus] dr.sonic:
Nandroid here i come :)

and, it's your foult that this happend to me, i folowed your voltages :D :D :D

Can i run restore with 25% battery, or should i charge it first?

Also, what is SR? :)
[Samsung Galaxy Nexus] bioan:
Franco, why is the sun eligibility so low on your kernel compared to CM kernel? Do you know the default settings on CM so I can try them?
[Samsung Galaxy Nexus] cpom1:
I haven't had any issues.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] rogersnm:
I restored with ~16% left so you should be fine, I did say make a nandroid :p

SR is smartreflex, it's a kernel level class that attempts to calibrate the voltage levels of the CPU based off what it believes is stable. However it seems to overestimate it at low frequencies and underestimate it at high frequencies.
[Samsung Galaxy Nexus] schizophrenia:
so I used the terminal emulator and extracted the file as this

https://dl.dropbox.com/u/11834745/last_kmsg 8 jun.txt

is this good enough for you to see as a log?

I was again on min 192 max 15xx SR off, interactive, no UV on 15xx and 14xx, AOKP

within the last hour, had one reboot when using Rmap and this log was the reboot just now when I was using an app called "LINE" (instant messenger app)....

please take a look and thanks
[Samsung Galaxy Nexus] dr.sonic:
Everything is back to normal. I think maybe the problem was that I used r181 512mhz, and you are using 384mhz.

Thanks for the help.

GNex via tt
[Samsung Galaxy Nexus] CaspaTheGhost:
Auto brightness for me...

OT - What is a vident?! Is it from Latin? :confused:

Dude, we need to meet down at that 'nearest' pub so I can buy you a drink. Gotta commend your patience with these posts, along with those asking about your settings just after you've actually posted them!

Also great input into the thread, I actually read your posts rather than skim over them like so many...

Bet you have Logger turned off... Franco.app > Settings > Turn Logger off - make sure its not ticked.

It looks like it really depends on ones usage, maybe more so with Wheatley when compared with the other governors... Currently I would say I am getting worse battery life with it, used to use Interactive.

I'll try and test tomorrow and Sunday when I am able to reproduce my usual test conditions.

Two totally different things so you shouldn't be surprised, the issues are with the current build of the app and therefore have no relation to the kernel which is a standalone item. The app simply does stuff that one could do using commands

The changelog for it explained in full;

+1
[Samsung Galaxy Nexus] schizophrenia:
thanks for telling...
[Samsung Galaxy Nexus] franciscofranco:
And I appreciate all feedback. I apologize if I seems harsh sometimes, but I get so many "omg dun work, fix now" that sometimes its hard to distinguish the real ones to the ones that have a so much ****ed up rom that nothing works besides hammering down the GN with a hammer.
[Samsung Galaxy Nexus] phantasybm:
Anyone else having problems with GPS not locking since installing 181?
[Samsung Galaxy Nexus] Culex316:
GPS works fine for me
[Samsung Galaxy Nexus] W3BSurfer:
flashed 181 and the governor doesnt seem to stick after each boot, it would revert back to "wheatley". i also tried interactive then set it on boot but i get wheatley again.
[Samsung Galaxy Nexus] rogersnm:
To anyone who's on similar voltages to me, you may notice that upon boot it tends to crash. This is because SR is enabled by default and only disabled by the app after the CPU voltages are set. To get around this you can turn SR off with an init.d script so it's disabled before the voltages are applied:

Modify /system/etc/init.d/98tweaks with something like Root Explorer and add to the end:

echo "0" > /sys/kernel/debug/smartreflex/sr_mpu/autocomp

And that should give you reliable boots and still maintain the low voltages whilst your phone is on :)
[Samsung Galaxy Nexus] six_dfx:
r181 works great, didn't have a single unexpected hang or reboot running 192/1536 interactive.

I let SR calibrate voltages for every slot but 1536 (reboot as soon as I apply anything < 1350mV) and the 1420 slot is rock stable with 1210 mV.

So I was wondering if there is any chance we get the possibility to manually adjust the 1536 slot below 1350mV, or if I should just go with SR off and manually set all voltages ?
[Samsung Galaxy Nexus] rogersnm:
You can look at what SR calibrates all the voltages to and then set them to that level manually and turn SR off. Best of both worlds :)
[Samsung Galaxy Nexus] splus:
Just to say that 180 and 181 run really good for me on AOKP b38 with CPU 384/1536 and interactive governor. Phone is cool even under stress (unlike a batch of nightlies around M4 which were quite hot) and with a great battery life which is hardly any different than in previous nightlies with max CPU at 1344. Voltages are just slightly reduced from stock except 1536 which is at 1400 mV.

My phone runs so smooth now and all the apps are noticeably faster that I have now stopped thinking about getting a Galaxy S3! No need, I already have it... :)

BTW, as some have pointed, interactive runs smoother and with better battery life for me than wheatley. I understand the theory behind wheatley but in practice it somehow doesn't deliver...
[Samsung Galaxy Nexus] jhondidfool:
Switched to interactive and the phone suddenly performs better and batteryspy tells me it consumes less juice. Seems Wheatley is still not ready and needs optimizations.
[Samsung Galaxy Nexus] Moz007:
Are you sure of that ???

Please some one can help me for set uv on boot ?
[Samsung Galaxy Nexus] phantasybm:
What is the theory behind wheatley?
[Samsung Galaxy Nexus] kingoanklebreakn:
It stays at Max to complete your tasks but when done it switches to a C4 state so it saves battery.
[Samsung Galaxy Nexus] Hanny:
Hi franco, this is again something discovered on your app:

in addition to my last report about the custom power modes, i also confirm franco power modes are not responding even the mode has been circled in the menu.

Besides these, I think the CPU Core 1 online/offline statuses are not showing correctly as well. Occasionally, CPU Core 1 is shown as "offline". I thought, it might really be the core being offline. However, with no power modes (and with my regular settings in my sig), i played GTA3 heavily for some minutes, and it was silky smooth like when i played it usually. I suddenly switch to your updater app and swipe to the "settings" tab as fast as I can. at that moment, the CPU Core 1 is still shown as offline. I tried exit your app completely, force close in app info page, and heavy use the phone (still responded smoothly as duel core), and turn your app back on. CPU1 was still shown as offline.

After a reboot, both CPUs are shown as online again :). From what I believe, the two rows should display the live on/off statuses of the CPUs, and the system-managed dynamic hotplug is currently in use. Unfortunately since the introduction of two separate rows about the CPUs online/offline statuses, I hvn't seen it changed in front of me, from online to offline, even if i tried to make the phone screen on but load nearly nothing in the background. Maybe it can be revised?

Thank you franco for all your work on this app beside your major kernel development and I really understand its harsh to fix these borks while introducing new features that users are requesting. Therefore I am just here to report and I have ****loads, no, is ****loads of patience for anytime update and fixes. :) have a nice day man!
[Samsung Galaxy Nexus] Diger36:
Trying those now...looking good...
[Samsung Galaxy Nexus] Prod1702:
Those are some crazy UV's. Looking forward to seeing how those turn out. I have done some UVing myself but nothing that low yet. Most of mine are jsut 50mv to 100mv lower. I would love to see what settings you come up with so i can see if my chip will run them as well.
[Samsung Galaxy Nexus] CaspaTheGhost:
Meant to click quote but the wobbly train made me miss and click the thanks button!

It seems to be a little sketchy when trying to make that first fix after installing but then seems to work fine. Do check two things though, the server via Fasterfix and refresh GPS assistance data via GPS Status...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Nexus Project:
(r181 512) Averaging about 12 hours of battery life (3hrs Screen On time) with HEAVY use. Pretty satisfied overall w/ 181.

1228/384 Interactive. Haven't noticed any significant issues. :thumbup::cool:

Sent from my i9250 (GSM) Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
I'm happy with 192-1228 voltages, 1344 has some crashes so I gave it another 25 mV. I haven't fully test 1420 and 1536 MHz yet.

Current voltage profile:

1536 MHz: 1275 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
192 MHz: 700 mV
[Samsung Galaxy Nexus] The Gingerbread Man:
Just out of interest, this problem where a rare amount of devices can't boot, would it make any easier if the other guys who experienced it also post their own ksmg adb up?

Sent with a shake
[Samsung Galaxy Nexus] Diger36:
I just had a crash undervolting. Do you know a source of info where I can learn to read the logs etc. in order to determine which setting caused the crash? Trying to learn and understand here...
[Samsung Galaxy Nexus] rogersnm:
You can check kmesg and logcat but afaik they don't show anything useful. You can get a good idea of what caused the crash by changing the min and max frequencies and narrowing it down to the specific unstable frequency.

For instance I ran 192-1228 and it was stable, but as soon as I raised the max freq to 1344 MHz it began to crash, so therefore I know that the voltage for the 1344 MHz slot is too low and thus needs a bit more tweaking, I've added 75mV so far. It's not a fail-proof method but it works fairly well.
[Samsung Galaxy Nexus] Lambetts:
Haha, no problem at all. Thanks for the reply Franco. I appreciate it.

Update: Its funny, I think after the last update the frequencies showed up! Last night after I posted. So that's good news.

Just some weird labeling issues but now I know that settings are there and working. :)

Thanks again. ;)
[Samsung Galaxy Nexus] debasser:
i have an battery drain after update to 180+ nightly with same setting like on 175...
[Samsung Galaxy Nexus] spinkick:
not sure why you guys try to undervolt, its barely a noticeable power difference over the automatic stuff.
[Samsung Galaxy Nexus] rogersnm:
iirc the SR calibration for 1228 MHz is ~1200mV, I can run it at 775mV, which means the SR calibration uses a 55% higher voltage. Making the assumption that the electrical resistance of the CPU stays approximately the same given the same load and frequency, that means that the previous SR calibration used 55% more power. Along with the reduced temperatures and thus reduced thermal throttling under heavy load, I think the benefit of undervolting is obvious.
[Samsung Galaxy Nexus] spinkick:
You'd think, but there are tests that show otherwise. Seems like something is broken to have such a huge difference in voltages between the two.
[Samsung Galaxy Nexus] rogersnm:
Obviously there are other components to the power usage, the screen and GPU are also large power consumers - but every little helps :)

The performance under heavy load shouldn't be scoffed at either, I had a 22% increase in my quadrant scores due to the reduced CPU throttling. And yes that does translate into real life performance in both gaming and web browsing.

Curious, I can set the 192 MHz freq at 725 mV and it's fine, but if I set it to 750 mV it dies immediately :\
[Samsung Galaxy Nexus] Eckless:
First off, you have my permission to tell me I'm stupid. I can handle it. :)

I've been playing with the features of Franco's kernel (r181 over a CM9 base). I assumed that applying more overclocking would result in higher benchmarks. (Yes, I know, benchmarks prove nothing, but I figured at the very least they'd show me that something was moving more quickly!) I was trying to figure out if the "higher clocks" were worth it.

Using Antutu and Wheatley governor, here were my scores:

1036 MHz: 5763

1228 MHz: 6444

1344 MHz: 6770 (So far so good)

1420 MHz: 6449 (Whaaaa?)

1536 MHz: 6006 (Hmmm.)

Similar things happen using Quadrant.

What am I missing?

Thank you for your kind suggestions...

Eckless
[Samsung Galaxy Nexus] rogersnm:
When the CPU temp reaches more than 75C it begins to throttle back and lower the CPU freq regardless of your minimum frequency. The higher frequencies produce more heat and therefore this throttling happens faster and is more aggressive. If you let your phone cool as much as possible and then run Antutu at 1536 you should get a better score. If you want to see when it's throttling you can open adb shell and watch the kmsg log. (cat /proc/kmsg)
[Samsung Galaxy Nexus] Eckless:
Thank you for the response! Makes sense. So since life isn't about maximizing benchmarks, my takeaway from this is that my "sweet spot" is 1344. I may be able to get higher speeds at certain moments, but unless I want to install a cooling solution in my phone, it's not practical. :)

Eckless
[Samsung Galaxy Nexus] rogersnm:
See the previous posts about undervolting ;) bought my peak temp down from 94C to 79C
[Samsung Galaxy Nexus] opethrocks:
Hey rogersnm, are you undervolting your core and iva as well? If so what values are you using?
[Samsung Galaxy Nexus] rogersnm:
Nope haven't gotten that far yet, still trying to perfect the mpu values. There seems to be some instability once the 1344 MHz freq is utilized in combination with the lower frequencies.
[Samsung Galaxy Nexus] Gucci.Nexus:
can anyone please tell me how to enable interactive?

edit: found it. my scaling governor is now 'interactive'

can anyone please reccomend any other settings? i selected 'set governor control on boot' figuring that might be a good one.
[Samsung Galaxy Nexus] Theshawty:
Well, overclocking the GPU to 512 Mhz only gives you a slight performance increase most noticable in games. It also may show screen tear, artifacts and other glitches, so stick with the 384 Mhz build.

The interactive governor is selected in the app, or in the ROM's performance menu, or through the use of a CPU overclocking app. According to me, interactive is the best governor so far.
[Samsung Galaxy Nexus] The Nexus Project:
Looking for some feedback on the Wheatley gov. Gonna try it after a full charge.

Sent from my i9250 (GSM) Galaxy Nexus
[Samsung Galaxy Nexus] Gucci.Nexus:
thanks for replying. i set scaling governor to 'interactive' and selected 'set governor control on boot.'

there is another place to select 'interactive'. in settings - set a custom power mode... should i select interactive there as well?

any setting recommendations please?
[Samsung Galaxy Nexus] rogersnm:
The custom power modes are currently an alpha option and don't work particularly well, it's best just to leave them alone. Setting the Max CPU, Min CPU, Scaling Governor and checking the "Set CPU settings on boot" on the OC/UV page are the only settings you really need to worry about.

---------- Post added at 12:57 AM ---------- Previous post was at 12:54 AM ----------

Most of the feedback so far is that it seems to drain more battery than interactive and is also less responsive than interactive. I still haven't got any good all day runs yet so I have no personal view, although responsiveness does seem to be more of an issue.
[Samsung Galaxy Nexus] Theshawty:
You do not need to add a custom power mode, and if I'm not mistaken, they're a little buggy. A power mode changes the cpu freqs, choice of governor and quite possibly what CPU's are running (CPU 0 and CPU 1).

If you're satisfied with your current clock freq and governor, then you can leave the power modes. :)
[Samsung Galaxy Nexus] Gucci.Nexus:
Thanks a lot for everyone's support & sharing. If only everyone was so kind in life :)

My phone seems to be pretty smooth right now. Even typing seems to have a quicker response:)
[Samsung Galaxy Nexus] Theshawty:
You're welcome!
[Samsung Galaxy Nexus] CaspaTheGhost:
If you haven't already, you should also use colour control in Franco's app. Just follow his recommendation detailed within colour multipliers.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
Hey Francisco, having a bit of bother with your app, 5.0.

I can't set voltages.

It let's me type them in and hit save but where it says current mv doesn't change to what I set.

It says the voltages I set under saved alright but current doesn't change.

Edit: fixed. Needed a different busybox version.
[Samsung Galaxy Nexus] do0b:
hows battery life and temperature?
[Samsung Galaxy Nexus] franciscofranco:
5.0.1:

* Galaxy Nexus

- Franco Power Modes not working after setting them is now fixed

- They are also set on boot normally

- Custom Power Modes cleaned up a little bit and after hitting Save it will automatically return to the previous Settings panel for consistency

- The usual cleanup

And now I'm off to sleep, can't barely open my eyes.
[Samsung Galaxy Nexus] fatappel:
My assessment is that it's "all or nothing". When phone is in use (meaning screen on) it maximizes all processes to bring the highest performance possible. Which also means fast battery drain. However, when in standby (screen off but push mail/notifications/sync, etc. active) it sips battery juice lighter than any governor I've experienced. I'm impressed but I guess or depends on how you use your device.

As it maxes out when in use, if you don't set the max too high, the battery drain is not bad. 1536 mhz drains too fast. 1228 mhz is perfect for me. I'm a fan.
[Samsung Galaxy Nexus] superbobup:
In my (very) short test of reading XDA, interactive resulted in about 20mins with 5% loss while wheatley was 22mins with 5% loss. 1344/729 for freq. It's a short time so take it with a few tablespoons of salt.
[Samsung Galaxy Nexus] do0b:
can someone please post the default values for CPU undervolt?
[Samsung Galaxy Nexus] nikulogical:
For those having bad results mainly battery with wheatley try 384/1344. I'm getting pretty good results. Especially for heavy users and gamers.With 1500+wheatley it wasn't that great.
[Samsung Galaxy Nexus] Sveke:
Silicone is maintaining at 1536 using interactive for the last 24 hrs. I'm a happy guy.
[Samsung Galaxy Nexus] :
On M4 as it has been perfection for me. I get 4 on the screen and that's all i need. Tks for all you've done & do for Gnex!!!

Gnexus toroplus+

Milestone 4 +

Skank = flawless
[Samsung Galaxy Nexus] fatappel:
Here they are. I've never touched....
[Samsung Galaxy Nexus] do0b:
thanks so much.
[Samsung Galaxy Nexus] leos0000:
I have the best battery life with r181 384 gpu :D
[Samsung Galaxy Nexus] despard:
Have a good night bro, can't demand more from 181
[Samsung Galaxy Nexus] nodstuff:
Pretty happy with this! :D

R181 384gpu

Undervolting really helps with the the temperature throttling and in turn helps benchmarks! :thumbup:
[Samsung Galaxy Nexus] metalspring:
I can't be 100% sure but I'm pretty sure wifi tethering is broken in 181...every time I try to connect my computer says it doesn't have a valid IP configuration

USB tethering works though?

Edit: never mind, it was an odd setting on my computer (odd I don't remember changing it but oh well)
[Samsung Galaxy Nexus] sruel3216:
yes i agree great build. i ran a cycle with wheatley and i actually got good battery with music playing. i still find interactive to be smoother tho. i got a few slow downs on wheatley where i never get with interactive
[Samsung Galaxy Nexus] nodstuff:
Ya I've jumped on the interactive bandwagon too, gonna try it out for a few days, see how it goes.
[Samsung Galaxy Nexus] cpom1:
Nice score :cool:

Sent from my Nexus Prime
[Samsung Galaxy Nexus] schizophrenia:
as soon as i did the first step to UV 1344 to 1150, the phone rebooted...

SR disabled already. strange
[Samsung Galaxy Nexus] Gucci.Nexus:
do any of the backup methods, backup kernel settings?

if i updated to a new release, and then tried to restore the older release's settings, would that work?

Franco, you are a cool guy!

thanks,
[Samsung Galaxy Nexus] mazubo:
10chars
[Samsung Galaxy Nexus] bat0nas:
Far from good. Im getting restarts which is annoying. Back to max 1GHz :)

Sent from my Galaxy Nexus