yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rogersnm:
There are a few people here running ~800mV mark for that frequency so I disagree with your judgement that most phones can't handle it, my phone is just a tatty second hand one off of ebay, there is nothing special about it. The SR value for 1228 MHz on my phone was 1220 mV so doing the same calc with 1220 and 800, that still means the SR value used 130% more power than 800 mV. Even weighting the power saving appropriately when compared to the other components, saying there is no real life improvement is either simply wrong, or you have a very large margin of negligibility.
[Samsung Galaxy Nexus] Lambetts:
Hey guys.

Bit of a problem with the app at the mo.... Basically every setting I set isn't sticking apart from colours.

Just reporting and not sure if its just me or not.

Thanks.
[Samsung Galaxy Nexus] despard:
****, your physics is adorable:eek:

Thanks for the lesson, I think I am gonna try how far my chips can go;)
[Samsung Galaxy Nexus] Theshawty:
Have you installed the latest app update? Try uninstalling the app and reinstall it.
[Samsung Galaxy Nexus] krex:
Mine is only empirical, but I ran one day with low voltages and SR off, and the only thing I experienced is the low temperature, no heat at all whatever I did, even if I ran benchmarks my phone stayed under 53°. :)

But the battery time and even its curve figure in Settings was identical as it is used to be by same usage. :(

Maybe I should have lowered IVA and CORE as well...
[Samsung Galaxy Nexus] rogersnm:
My consumption with core and iva also undervolted (with wifi on constantly)
[Samsung Galaxy Nexus] krex:
Yes, yours is convincing...
[Samsung Galaxy Nexus] rogersnm:
Try undervolting the other two as well, I took 200 mV off the GPU.
[Samsung Galaxy Nexus] krex:
It is the next what I will do.. thanks!
[Samsung Galaxy Nexus] ArmanUV:
You said it yourself. Yes, there are a FEW people running crazy UV but thay are a small minority. And it doesn't matter where you got your phone, it's just statistics. Only a few silicons that are shipped out can handle such low voltages. If you can, then good for you, but the principle doesn't apply to everyone.

Now regarding wether UV actually makes a difference in battery life, we can talk and talk but at the end it's all theoretical bull****. Someone did a battery study on the Nexus S and here is what they have to say about it

Considering that the gnexus has smartreflex and a bigger and more power hungry screen, there is a strong evidence that UV doesn't correlate with better battery life. It's still fun, but it's only that.
[Samsung Galaxy Nexus] rogersnm:
There are only a few people running the UV because only a few people have tried it. It's less to do with the failure rate and more to do with the willingness to give it a go. I don't use SR and your clicky lacks the complete data.

The CPU is always "on", even if it is an idle state it is still drawing power. That links states a power reduction of 13% from the CPU but I have a much more significant power reduction (as noted above). It also talks about current, rather than power, and not all the components have the same voltage and therefore will have different power draw for a given current, although I'll assume he's talking about the current out of the battery so I'll let that go.

Assuming that the screen draws a current that is a mean average of the minimum and maximum consumption is a poor assumption to make, and the actual power consumption of the screen depends much more on personal usage.

It also says that the GSM radio requires 200mA of current to run, however as above, I had my radio on for almost 12 hours and the battery is still at 86%. The battery is 1750 mAh and I used 14% which means I used 245 mAh in almost 12 hours, an average current of around 20 mA, and that went towards the screen, cpu, gpu, gsm radio and wifi radio (along with other things), far less than an averge current of 200mA just for the gsm radio.

I also undervolted the GPU and IVA whereas that article only concerns undervolting the CPU.

I fully accept that you aren't going to see huge improvements in battery life from undervolting, but I decline to accept that it will only be a 2% improvement.

This formula, however, is a useful one to have.
[Samsung Galaxy Nexus] The Gingerbread Man:
Had 3 random reboots this morning with rogersnm's settings but I had none last night, was stable. Only difference was I was charging it up via mains plug.

I bumped it all up abit and now running this table, stable so far. The phone is noticeably cooler in my hand running duel core than stock for sure. Sr off with interactive. I'll save power save mode for work

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I'll give mine a go with the mains charger. I've charged via USB+Fast Charge so far and had no problems.
[Samsung Galaxy Nexus] The Gingerbread Man:
Youl probably be OK I guess as USB fast charge is meant to force AC charging mode so should be same power or current which ever it is.

Worth noting I don't often use the supplied charger (plug with USB cable that comes off) I use a dedicated mains charger that comes with s2 (official Samsung product). I find the USB connection with supplied charging cable rather finiky personally and a good connection while holind and moving the phone just about always knocks the charger out of the port enough to stop it charging

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I use the USB charger that came with my old Xperia X1, my supplied charger didn't work from day 1 :(
[Samsung Galaxy Nexus] Bonvaz:
R181..no data drops with rascream!!!!all smooth :)
[Samsung Galaxy Nexus] The Gingerbread Man:
I only use it for PC transfer and the adb stuff we did the other day, I also come from Xperia background I had the x10 (lending it to my youngest brother) :)

Sent with a shake
[Samsung Galaxy Nexus] The Gingerbread Man:
This rascream rom interests me, I can't find much info about it around though, I looked on the euroskank site and doesnt say much. Is there somewhere with more info?

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I looked around and apparently rascream's unofficial home is the trinity kernel thread here: http://xdaforums.com/showthread.php?t=1455874

This FAQ post may be useful: http://xdaforums.com/showpost.php?p=26998659&postcount=7125

Seems like it's largely a minimal build of AOSP with some speed tweaks.
[Samsung Galaxy Nexus] The Gingerbread Man:
The only thing I'd really miss about the paranoid rom is the tablet mode nav bar with the clock and notifications at the bottom. I hope it has that

Sent with a shake
[Samsung Galaxy Nexus] 1cewolf:
Performance is great with n181 on AOKP B38, but for the past couple of days I've been getting a kernel wakelock from suspend_backoff.
[Samsung Galaxy Nexus] endymion2k5:
Could somebody please give some insight or information on what i am (most likely) doing wrong with the following setup.

The thing im trying to do is undervolt the CPU from an init.d script (i know the risks, no questions there). So far i tried a few methods but it always comes out the same. If i set the voltages with the franco kernel updater, it works. Just not from the init.d script.

init.d script:

First use ">" to clear the previous file and add the first line. Then use ">>" to append to the file. (My instinct says it goes wrong at that point)

/sys/class/misc/customvoltage/mpu_voltages outcome:

What would be a valid way of writing to the file, with multiple lines, from an init.d script? Is it even possible to set it with an init.d script?

Thanks in advance
[Samsung Galaxy Nexus] rogersnm:
Curious, try:

echo "1536mhz: 1400 mV\n1420mhz: 1350 mV\n1344mhz: 1325 mV\n1228mhz: 775 mV\n1036mhz: 750 mV\n729mhz: 750 mV\n384mhz: 725 mV\n192mhz: 700 mV\n" > /sys/class/misc/customvoltage/mpu_voltages

It looks like something (either franco's app or the kernel) is overwriting your 192-1344 MHz values anyway, but I haven't got a clue what's going on with the 1536 and 1420 MHz values :\. If you're quick you can adb onto your phone during the boot cycle and run "cat /sys/class/misc/customvoltage/mpu_voltages" a few times and see what the output is. You can adb on just after second vibration, just as the screen brightness is applied. If you're quick enough you can do it before the apps start up. You could also try booting in safe mode (stops non-system apps from running) and see what the applied voltages are.
[Samsung Galaxy Nexus] endymion2k5:
Thanks ill give it a try and report the findings.

-- Update

Gave adb a try, the first results im getting right after adb is functioning, are already 'wrong':

C:\Users\XXXXXXXX>adb shell cat /sys/class/misc/customvoltage/mpu_voltages

1536mhz: 192 mV

1420mhz: 700 mV

1344mhz: 1325 mV

1228mhz: 1300 mV

1036mhz: 1317 mV

729mhz: 1203 mV

384mhz: 1025 mV

192mhz: 900 mV
[Samsung Galaxy Nexus] ascariz:
you need to update your wiki http://xdaforums.com/wiki/Samsung_Galaxy_Nexus/GT-I9250/ROMs/FrancoKernel#App_Changelog
[Samsung Galaxy Nexus] rogersnm:
Might be something to do with it being overwritten immediately as the lines go in. So possibly the last thing it sees is 192mhz: 700 mV which it then parses to 192 700 and uses that for the first two voltage levels. Try just doing echo "1400 1350 1325 775 750 750 725 700", that will probably sort out the first 2 but I wouldn't mind betting the rest which still default back. Change the saved values in franco's app as well as doing this and it *should* work.
[Samsung Galaxy Nexus] Lambetts:
Hey,

Thanks for your response man.

Unfortunately yeah, tried that. Not sure what's happening. Getting weird battery drain now too....
[Samsung Galaxy Nexus] Lambetts:
Quick one, just a quick one. :)

Does the kernel support 2 way recording? Or is there something I can change in the init or something to get it working? Just a passing question.

Thanks guys.
[Samsung Galaxy Nexus] endymion2k5:
Thats what im guessing aswell. Something goes wrong with the echo and it is not parsing it right. I did try your echo line, which has better results but still is not entirely right. It does match your theory however:

Tested the last echo line, kind of weird that it works. I have not changed the voltages from the franco kernel app, yet they seem to stick. (i always believed the files should be echoed to the way they are now, which seems is not always the case):

Many thanks for helping with this issue. Hope more users can enjoy the echo line ;)
[Samsung Galaxy Nexus] rogersnm:
The app does seem to lock the voltage files (mpu, iva and core), it's best to change them in there first and then set them on boot with an init.d script (alternatively the GLADoS control app has set on boot functionality and doesn't seem to have any compatibility issues with franco's kernel)
[Samsung Galaxy Nexus] endymion2k5:
The voltages im using within the init.d are already set within the franco app, i only had to press 'apply'. Thats how i tested it prior to making it stick on boot. I did not want to risk bootloops prior to knowing that the set voltages are actually stable. The tests i have done on these voltages looked promising, but it has many factors in which it could become unstable (cpu temperature, cold/warm/hot day, governor type (wheatley at the moment), etc). Time to test the stability over the next few days...
[Samsung Galaxy Nexus] franciscofranco:
A small advice: low core voltages WILL cause data drops, and low IVA voltages will cause a strange sound tick. Better leave those voltages alone. I have to separate the disable of MPU, IVA and Core smartreflex in the app rather than doing it all together.
[Samsung Galaxy Nexus] rogersnm:
Cheers, seperate SR options would be very useful. I haven't had any data drops or sound issues yet *touch wood*
[Samsung Galaxy Nexus] franciscofranco:
Your silicon is a beast. Mine is pretty good, but I cant run your UV settings.
[Samsung Galaxy Nexus] nodstuff:
Hey Francisco, I know you have 6 kernels to maintain as it is but do you have any plans on getting a gs3??
[Samsung Galaxy Nexus] SeauxCrazy:
Maybe someone can help me out here. I've been running Franco nightlies when they drop, but for some reason I cannot install 180 or 181. The app is up to date, but I cannot get the phone to boot on either. It gets stuck at the google screen, with small green lines around the lettering. I've tried manually installing the .zip and through the app, but with no luck.

AOKP Milesone5, been running Franco 175 with no issues.
[Samsung Galaxy Nexus] endymion2k5:
Thanks for the advice, i will keep a close watch on the data connection. But to be honest, i did not understand the fuzz about the data drops earlier because i had never experienced one on any of your kernels. I never go for milestones but only nightlies. Quite frankly, my nexus accepts anything you seem to trow at it. Im quite amazed that the voltages that rogersnm posted work for my nexus, or at least for now ;)
[Samsung Galaxy Nexus] drawde40599:
I'm going to get yelled at and some 1 going to get fancy and try convince me I'm wrong but, I've tested this and ever other kernel out there, stock settings for 3-7 days at a time then screwing around with OC, UV and everything else u can do and UV got me maybe 2-5% more and thats being nice,and by then your looking for a charger anyway so ....... its not worth it unless ur bored maybe, I've tried little UV I've tried major UV and everything in-between its a waste of time, unless u have a hot running phone then yes it helps there . I see guys on here UV like crazy but i don't see the comparison to stock ( maybe I missed it?? ) IMO run Franco settings with a governor u like and leave it alone; ) personally I run 1300/ 700 ( ya I no ) interactive gov everything else stock I get 3.5 hours screen on, data on, gps on, sync on brightness 75% with 100% Franco settings I avg 4 hours screen on same setup . And BTW if u search this 2000 page thread; ) Franco himself said UV don't do much
[Samsung Galaxy Nexus] rogersnm:
I've yet to see any rigorously collected data to persuade anyone one way or another. It generally seems to just be opinions based off rough empirical evidence. Given the effort involved in collecting any statistically significant evidence it's unlikely that that will ever change, however the theory, to some extent, backs up undervolting. My phone's been on for the past 18 hours without any faults or data drops so I see no downside to undervolting.
[Samsung Galaxy Nexus] schizophrenia:
just had another soft reboot while I was using Map.. (most of the time the phone rebooted when I was using map related stuff with GPS on)

I was on r181 min 192 max 1344 ondemand with some UV and on AOKP

these are the logs please take a look and thanks

https://dl.dropbox.com/u/11834745/kmsg10june.txt

https://dl.dropbox.com/u/11834745/dmesg10june.txt.txt
[Samsung Galaxy Nexus] rogersnm:
It looks like that is due to undervolting instabilities.
[Samsung Galaxy Nexus] The Gingerbread Man:
Welcome to my world. Your about the 7th or 8th person iv read here with the same issue as me.

I did post a adb kmsg a few days back and Francisco said he can't see where the problem is, well rather how to fix it. The system is complaining about some kind of boot thing which only effects a few of us.

Also just for extra information weather thus helps or not I don't know but its definatly a device specific issue as I'm running rascream now and it still won't boot with 181 so its not a rom thing.

I'm wondering if its to do with hardware version which can be found at boot loader menu, mine is 9.

Sent with a shake
[Samsung Galaxy Nexus] The Gingerbread Man:
There was a discussion regarding the benefits of under volt a few pages back

Sent with a shake
[Samsung Galaxy Nexus] endymion2k5:
Just checked the bootloader. My HW revision is 9 aswell. Currently running franco 181 with 384 mhz gpu on CM9 (compiled a few hours ago by myself)

Radio:XXLA2

I dont think thats the problem, but im no developer.
[Samsung Galaxy Nexus] SeauxCrazy:
I'm HW Version 14.

This would suck if its a hardware thing, I'd hate to be topped out at 175 in regards to Franco Kernels because I'm guessing every kernel is built off of the latest version. :(
[Samsung Galaxy Nexus] nodstuff:
I have HW version 9 and have never had any problem.

Its not the hardware version that is causing the problem.

There must be something else.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well I guess it can't be hw version then. Radio version maybe but unlikely, mine xxla2

Sent with a shake
[Samsung Galaxy Nexus] rogersnm:
I've got xxla2 as well :o
[Samsung Galaxy Nexus] nodstuff:
I'm using XXKL1 now but I've used XXLA2, XXKK6, ugla4 and UGLC1 as well and haven't had any problems.

Its strange how people on the same radio, kernel, os veraion and hardware version have different experiences.

I mean we're all in western Europe and using the same frequencies for GSM etc. and you have drops and I don't.

Its a mystery
[Samsung Galaxy Nexus] The Gingerbread Man:
I haven't had a drop in a while now. I really don't know what the solution to this is, would it help if I were try and get another kmsg from adb now I'm running a different rom?

Sent with a shake
[Samsung Galaxy Nexus] drawde40599:
Ya i read it . But I've been using and reading this kernel / thread since page one ( b4 Franco had phone ) and I've seen and read so much, (most is nonsense), but I have 2 GN and from personal experience with both controlling heat is only noticeable difference for ME when UV. And its funny that alot of people here install the kernel and "tweak " the hell out of it before even using stock setup for least 24 hours o_O so they don't no if helping or not, but hey if one thinks there phone running better, great!! its ur phone do.what u want; )
[Samsung Galaxy Nexus] SeauxCrazy:
CDMA Sprint version here in US and I'm having the 180/181 issues :(

I'm sure there has to be some commonality to cause us to not be able to boot it.
[Samsung Galaxy Nexus] CaspaTheGhost:
+1

My own experience is very similar as is my setup. I think reducing temp would be the reason for me to disable SR and UV manually.

And that would be due to seeing the results of your comprehensive testing showing a real impact in that area.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
Ignore
[Samsung Galaxy Nexus] Diger36:
Heat is my main driver to UV. If battery is empty: I charge. But with the new slots my phone gets hot a lot. This way it just FEELS nicer. (I know, it's just a feeling).
[Samsung Galaxy Nexus] dracon6ai:
Looks like these are my stables for now.

CPU -

1536 - 1275 mV

1420 - 1250 mV

1344 - 1200 mV

1228 - 900 mV

1036 - 875 mV

729 - 875 mV

384 - 825 mV

192 - 800mV

IVA -

266 - 900 mV

133 - 825 mV

Core -

512/384 - 775 mV

307 - 700 mV

153 - 675 mV

SR off of course and just posting this to get more data out there. Any lower on IVA and I get sound popping so I believe that's as low as I can go on that. Still messing with core, had a wifi switching to 4g issue this morning so bumped it up.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] CaspaTheGhost:
:confused: I may be British, but that wasn't dry wit or an intentional deadpan delivery!

Battery life factors vary so much that the improvements from UV are subjective as you pointed out earlier, whereas CPU heat output is objectively measurable.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jhondidfool:
Thanks! Your core voltages now power my machine, and it still goes smooth. ---- not so smooth. now it crashes. I'll play a bit with it...
[Samsung Galaxy Nexus] ro_explorer:
Hi Franco ...

I did not had the time to play around with my phone and give you feedback in the last couple of months ... but I was always up to date with your Milestone releases and also with your App.

I no longer experienced signal loss since M4 but yesterday evening I lost the whole network connectivity ("no network" was displayed on the status). A reboot fixed it. I do not think this is necessarily related to your kernel (might be as well the rom or some application gone berserk) but in case I will get again this weird network loss I'll report it since it is a stability issue.

On the bright side, today I did a battery full discharge cycle (by playing with the phone all day).

The result is above expectations (I've obtained the best screen on time ever with Your M4 running on AOKP M5 rom):

Setup:

Frequency range: 384 - 1030

Stock voltages

Governor: Interactive

Both CPUs online

OEM extended battery

Thank you for the great work you're doing!
[Samsung Galaxy Nexus] nodstuff:
The thread has been quiet for a while so off topic bump:

COME ON IRELAND!!!! :D
[Samsung Galaxy Nexus] MS.:
Bump!
[Samsung Galaxy Nexus] nodstuff:
Linesman should have gone to specsavers.
[Samsung Galaxy Nexus] Exostenza:
Hey guys I asked this a couple of days ago and it must have just been missed as this thread is quite active.

I have been using Lean Kernel for a while now I have been missing the amazing battery life of franco.kernel, but have been waiting for M4 to come out. When it came out I flashed it and right after that I get about maybe 1 in 5 calls which have excessively low volume. Does anyone else have this issue? It seems to be kernel specific as on Lean Kernel this does not happen.
[Samsung Galaxy Nexus] leelaa:
So franco, 181 running great, any new nightly soon?
[Samsung Galaxy Nexus] AdrianE46:
Since 180 and 181 i keep experiencing random shutdowns. It just turns itself off in my pocket for no apparent reason.
[Samsung Galaxy Nexus] ChosSimbaOne:
Hi is there a specific step size one must UV with? Thought i read 25 mV, but not sure, is that CPU specific?
[Samsung Galaxy Nexus] rogersnm:
You can use 1 mV increments, it's just the app's slider bar that uses 25 mV increments.

---------- Post added at 10:17 PM ---------- Previous post was at 10:16 PM ----------

Grab /proc/last_kmsg and upload it. (After a random shut down)
[Samsung Galaxy Nexus] irizwan:
:D Hello

I've installed N-181 works great no reboots or anything just wanted to ask a small question .. about undervolting

I've UV'd -50 on all CPU states seems stable i wanted to ask is it Safe to undervolt the hardware decoder and GPU .. i have UV'd it round -25 on both of 'em just askin' there woun't b any side effects

Thanks =]
[Samsung Galaxy Nexus] drawde40599:
Yep!! And if u have one of the phones that just run hotter, then UV would cause better battery cause phone running cooler ... but mine runs cool no matter what I do never gets over 57°c ( Franco app ) and in MY testing I get no benefit with MY phone . I'm still interested in every1's before and after testing, something u really never c posted here ....; )
[Samsung Galaxy Nexus] The Gingerbread Man:
You might be able to go much much lower than that, you should turn off smart reflex via Franco app before changing your settings as it causes errors and instabilities.

There's been several if us posting under volt tables over the last 10 pages maybe less so have a look and use them for reference and see what works well for you.

Sent with a shake
[Samsung Galaxy Nexus] irizwan:
Ola yea ive been browsing but i don't wanna undervolt too much that my device can't handle i wanna start with small increments n find what is stable for me

and yes smart reflex is off =D

edit: small question ive noticed that after a restart the voltages go up again and u have to hit "Apply vales" again is that normal ?