yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
Lol.

---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------

I believe so, but 'to what degree' is my question. If I spend two hours at 830 vs 730, that saves 200 something. Is that directly related to our battery level? We have what, 1750 in our battery? I don't know if those are legit numbers or not. Lol. I love math and electricity, but not when I am 95% asleep in bed on my phone. Lol. I will look into it tomor... Zzzzzz.
[Samsung Galaxy Nexus] AutomaticFailure27:
Is there a way to check what the calibrated SR voltage is, so then I could disable SR and use those calibrated voltages?

Edit: Never mind, I got to thinking, if you lower the voltages without turning SR off, then wouldn't you have a range for the voltage to be in?

Since 384 is at 830mv calibrated... and I set it to 925mv while SR is on... would that mean that the range of voltage 384 can use is between 830-925?

And reading from the previous posts, anything under 830mv is released from SR, so SR will not calibrate any lower than 830?

So again, that would give it a range of as low as 830 but as high as whatever it is set to?
[Samsung Galaxy Nexus] creeve4:
Swiping between the screens seems to trigger the input boost most of the time, but scrolling up and down results in the above behavior.

Using CPU Spy, and only swiping between home screens and within the app drawer, the CPU is about:

1228: 10%

1036: 45%

729: 15%

384: 30%

Maybe this is normal?

Bottom line, 295 is quite snappy! I'm not seeing any lag running the default settings for interactive.
[Samsung Galaxy Nexus] BigBake88:
Hey, who you calling an average user??? Lol. But....won't 192 still use less power even though the voltage is the same as 384? I remember reading this somewhere...
[Samsung Galaxy Nexus] Sik-1:
384-1228mhz with 620-770mv +50 increments, haven't tested a full day myself yet, will do in the morning, so far tho past couple hours have been sweeeeet
[Samsung Galaxy Nexus] osm0sis:
Sorry! :silly: That wasn't really directed at you, just your line of questioning got me thinking about new users and those who would rarely even check the thread. :)

One could try and argue 192MHz would potentially use more power than 384MHz at the same voltage because operations take longer to complete, and even that's unlikely because things should be ramping up, but I definitely can't see any reasoning for less power.
[Samsung Galaxy Nexus] Tarun95:
Yup under volting helps. I have noticed a difference of 30minutes screen on time. Phone also runs a little cooler.

R290 BTW

384-775mv

729-950mv

1036-1075mv

1228-1175mv

384 and 729 are used the most so if u could under volt those 2 then battery savings. Generally 729 sr calibrated runs at 1030 and 384 at 840 so yeah it works for me pretty well. And in a day 384 is used at least 3-4 times more compared to even 729 so undervolt really works by simple logic ;)

Edit: and for u guys testing 192mhz 100mv will make a big difference. I can bet on it. I tried under volt values and normal voltages thrice each to see what each gives me.
[Samsung Galaxy Nexus] BigBake88:
Haha I know just playing. :p Good point about 192 potentially using more power since it takes longer to get tasks done. Very interesting. How could we get hard data on this?
[Samsung Galaxy Nexus] drawde40599:
30 min huh
[Samsung Galaxy Nexus] Dragooon123:
Probably a stupid question, but if I undervolt and don't disable smart reflex, would they still apply?
[Samsung Galaxy Nexus] osm0sis:
Only if they go below the SR calibrated value.
[Samsung Galaxy Nexus] mike216:
I wouldn't touch the voltage. It's not worth the extremely minimal battery life you'll get. Just my opinion after a year of undervolting without seeing any difference.

Been rocking M6 for a while now. Would anyone suggest a recent nightly that would be better on battery then M6 is?

Thanks community been away in the slumps for a while so wasn't able to be as active as you pros :)

---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
[Samsung Galaxy Nexus] IAmAN00bie:
Well... *cough* P = C*(V^2)*f.....so lowering the frequency does reduce power consumption even if the two frequencies are at the same voltage. Theoretically, of course.

edit: @mike216 yes undervolting doesn't save much battery life, but it does help reduce heat which can be more pleasant for the user as his phone won't feel as hot as he/she is using it

---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------

Not really. P = CV^2*f (again!), it is clear that changing voltage makes very little difference in power consumption, because the voltages are in units of milliVolts.
[Samsung Galaxy Nexus] osm0sis:
Oh man, deja vu, how could I forget!?! :D:p:cyclops:
[Samsung Galaxy Nexus] sruel3216:
Franco mentioned ROM toolbox for adjusting the minfree values. What is the best preset values to use?
[Samsung Galaxy Nexus] shawnaye:
Guys. I tried setting uv value for 192mhz to 775mv.

But when I go to the device monitor tab. When my phone is on 192mhz.

The voltage doesn't correspond. It's actually around 1000mv.

And when I check back my oc/uv tab. The 192mhz value current is 1000mv but saved at 775mv even after several applies and reboots.
[Samsung Galaxy Nexus] Gaku86:
Sorry to bother you yellow, but what are you guys talking about what are these combinations and where to apply them for good performance and battery
[Samsung Galaxy Nexus] trailblazerz11:
Using superSU?

I set it to 730mv and its been running fine for 4 hours so far, no lag so far with new stock governor settings, will try endurance testing.

Just seemed slightly pointless to me it was same voltage as 384 but what do I know.
[Samsung Galaxy Nexus] shawnaye:
Yep I'm using supersu

Hmm you set it to 730mv. But does that number ever show up on Francos app device monitor??
[Samsung Galaxy Nexus] The Gingerbread Man:
You need to apply the voltage change after each reboot by pressing the apply button in Francos app in oc/uc tab

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Antob125:
So 384-1228 and 729 off frequency is default and these values are default?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nighthound:
Actually, if you're going solely by that formula, changing reducing the voltage from 830mV to 730mV does make a significant difference.

The % change in V = 730/830 = 0.880.

Hence % change in P = 0.88^2 = 0.774.

In other words, the power consumption (theoretically) should be reduced by 23%, assuming the time taken remains the same.
[Samsung Galaxy Nexus] duduzinho15:
Help me franco all the time my phone crashed get reboot sometimes my phone doesnt turn on,today morning i lose the hour because my phone had crashed:mad:
[Samsung Galaxy Nexus] gialandra:
What is the best way to reset the voltage at default?
[Samsung Galaxy Nexus] PeterGuru:
No, try KK7 ...

I also have a Bell GNex, and mine is KK7 ... perhaps that's the one you want since it appears you're with Bell.

Peter
[Samsung Galaxy Nexus] 3c:
That's why I said in the title: "Why disable something that works well for many?"

You can have default UV and leave it open for others to try, that has always been the freedom we seek coming here.

In any case: stability for everyone = stock kernel.
[Samsung Galaxy Nexus] jabberwocky127:
Ok, not to be a noob, but I have been waiting for somebody to mention it for a good while and no one has; what is this app? Additionally, are those voltage values set by the app at boot or is it put into an init.d script so the app is not necessary after tweaking values?
[Samsung Galaxy Nexus] ro_explorer:
I have a bug report. The phonbe is stable in every day use, great battery also.

Today I tried to play GLWG. After about 1H of play the game suddenly frozen and the phone rebooted. I've did another clean reboot and started again the stress .. same thing only faster .. after about half hour .. game frozen, phone rebooted.

There might be 2 possible causes:

1. OC of the CPU is not so well supported while the CPU is hot.

2. same as #1 only applied to the GPU.
[Samsung Galaxy Nexus] franciscofranco:
Hmm. Tell me your full specs while playing that game please.
[Samsung Galaxy Nexus] bradm23:
Colors +

Franco,

I am alittle curious to find out how you came up with your Color adjustments? Did you mess with the colors untill you thought they looked better, or was the screen tested using calibrating equipment? Knowing the screen can be calibrated, leads me to my next question, Can these phones be fully calibrate like Plasma, LED, and LCD TV?

I know that alot of people on this site complain about the colors. I for one get all of my TV's professionally calibrated, and do not have any issues with the current colors that I see using your kernel. However, I am just curious if it is possible to calibrate their screen using some kind of calibrating device? If this is the case, do you have any info on what variables you have control over (contrast, hue, brightness, etc).

Just some food for thought,

Thanks for all of your hard work and dedication.
[Samsung Galaxy Nexus] ro_explorer:
350-1200 , conservative, 25% brightness - manual. The cpu is being recorded as staying at 1200 MHz continuous for the time of play. The battery consumption is HUGE (like I never saw before) - 30% per hour (2W). No other stuff going on behind.

I've tried playing since my last post with the phone plugged into a 750mAh charger and .. guess what .. the battery was still going down (at a slower pace but still down). I guess something is going in overdrive mode and is killing the battery.

As soon as I'll stop playing (in like 2 minutes) the phone is cool again so is definitely related to the resources involved in playing the game.

I'm trying now to limit the CPU to 920MHz to see if the situation will improve.

I'll report back in 15 minutes or so ..
[Samsung Galaxy Nexus] 3c:
The app is System Tuner (see my signature) and it can adjust voltages manually and create necessary init.d scripts.

I was expected you waited for somebody to ask about UV interface ;) I did but no one asked.
[Samsung Galaxy Nexus] ro_explorer:
Me again .. with 920MHz as max the game is still very fluid, the phone still gets VERY hot and it still rebooted (1 min. ago). I'm inclined to suspect the GPU as being overkilled.

I'm setting up 700MHz as max frequency and test again.
[Samsung Galaxy Nexus] nuggahund:
Great kernel, works very well!

I do though have some questions.

What is the original frequency of the GPU?

How comes the browser is very smooth when scrolling, like an iPhone, when it was quite choppy on the stock ROM? I mean, do you really know more about creating a smooth browser than Google do? Well it might be the ROM I'm running and not the kernel? Flashed them at the same time, so I can't tell.

And btw i really recommend the updater app.

Martin
[Samsung Galaxy Nexus] ro_explorer:
Quoting myself :) ... same result with 700MHz.

It appears that if I'm not letting the phone to cool down it will reboot in about 5-10 minutes after starting the GPU stress again.

I'm beginning to be worried about the GPU possible failure under the current conditions.
[Samsung Galaxy Nexus] sishgupta:
True enough
[Samsung Galaxy Nexus] franciscofranco:
Hmm very nice report. Thank you.
[Samsung Galaxy Nexus] fenerbuuh:
Good work and kernel, but please open uv settings.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mfish123:
Where did you get this "System tweaks" app?

EDIT - NEVERMIND - already answered in a previous post
[Samsung Galaxy Nexus] lynxboy:
Your browser joy is down to the 4.0.3 ROM which increases the performance of the 2D UI in general, be it the browser or in 3rd party apps. I found it to be a massive improvement over 4.0.1/2.

This kernel obviously helps with the overall performance though. There is simply no other (custom) kernel on the GN worth flashing right now, it's that good.

Regards.
[Samsung Galaxy Nexus] mfish123:
Inconsistent mA during sleep

I'm hoping my question is kernel related as I've had similar behavior on both Axiom 2.4 and AOKP build 15. It probably is something I'm not doing correctly as Franco's kernel rocks.

In the screen shots below. I was on wifi the whole time, in the same location in my office (consistent signal strength). BT and GPS were off. Sync was on. I've disabled auto rotate, disabled location services and open and close the camera everytime I reboot. I've also disabled these apps: Google maps, Google+, and Google Talk. I'm running convervative governor with hotplug enabled. For the screen shots I ran 350mhz to 1350mhz but I see the same behavior from 700mhz - 1350 mhz.

Sometimes my phone sleeps with 2 mA and other times its significantly higher. I know my Android OS is a high percentage of battery drain but can't really figure out why and/or if that's the primary cause of the inconsistent drain.

Attached is a battery monitor widget log, cpu spy screen shot, betterybatterystats screenshot, and android stock battery stats screen shots.

If anyone can help me track down what is causing these inconsistencies I'd be very appreciative.
[Samsung Galaxy Nexus] minooch:
Hey Formel,

I remember you from N1 days (your MIUI ROM), so I know that you've attempted searching - The reason 700 min is recommended is because:

When the phone is idling, the power consumption is lower than 350

Less frequencies means faster movement between idle & full (& Vice Versa)

The end result is a little better battery life & better performance

There is of course an exception to this - If your using your phone to play music (or something similar) you will benefit from using 350 as a min (for a battery life)

OMG! Read a little - There is a reason why custom UV controls are NOT provided!
[Samsung Galaxy Nexus] Shaquiel Harris:
Just because of the PURE popularity of your kernel (seems like literally everyone is running your kernel) i'm about to flash and see whats all the fuss about :cool:.
[Samsung Galaxy Nexus] NEtik:
very interested in that! I have exactly the same problem.. I killed maps.. open/close camera.. location.. rebooting.. etc.. looking for the problem and i dont know what's happening
[Samsung Galaxy Nexus] DonXoB:
It would be helpful, if you post some more details. What rom do you use, what kernel version, which settings?
[Samsung Galaxy Nexus] duduzinho15:
I use aokp build 5, using config 350 to 1350, milestone 6
[Samsung Galaxy Nexus] supernova_00:
Why do you guys keep saying 384 and 192 use the same voltage? My defaults show 384 using 1025mV and 192 using 1000mV. Also, where'd you get the 830mV from?
[Samsung Galaxy Nexus] Sik-1:
The 830mv is the SR calibrated voltage
[Samsung Galaxy Nexus] yellowdie:
Check out this post . And the best thing is the r295 defaults. :)

Yep. :D How does it feel?

Nice. :D So my question is if I use the 192MHz slot for two hours throughout the day, how much does a 23% saving actually increase screen on time?
[Samsung Galaxy Nexus] Antob125:
Feels good so far. Any recommendations to tweak to make it faster but still safe? :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
The best thing to keep in mind is this:

So if you want "more performance" then you can try turning the first two numbers down, but 6/7 is really what we found to be the best sweet spot. If you didn't care about battery and wanted it to spent most of the time at high clockspeeds, you could try 5/5/9/3. But again that's not gonna be battery friendly. :) Enjoy! Let us know if you try stuff and what you think about them.
[Samsung Galaxy Nexus] franciscofranco:
r295 is so fast and so smooth that Im using 192Mhz undervolted to 750mV, so I believe the current settings are the most balanced while getting awesome performance. Not a single ****ing lag in this device = SGS3 back to the drawer.
[Samsung Galaxy Nexus] Sik-1:
Never had this going this strong b4, Franco you are a kernel god
[Samsung Galaxy Nexus] BigBake88:
Franco.kernel FTW!!!
[Samsung Galaxy Nexus] yellowdie:
haha. I was really wanting a GS3, but now I'm super glad I went with the Nexus instead! :D
[Samsung Galaxy Nexus] franciscofranco:
Wtf 75% left with almost 2h screen on time, nice sorcery.

Yes Im still wondering why I bought the SGS3, nothing beats pure Android.
[Samsung Galaxy Nexus] rickbosch:
Wow, am I glad I decided to give r295 a try. This is ridiculous.

Thanks Franco.
[Samsung Galaxy Nexus] sruel3216:
I'm just curious. Shouldn't I have more available with a gig of ram? Or does this not show the memory used by system. My n7 shows I have much more free
[Samsung Galaxy Nexus] jltorrente:
Okay... I come to you today , humble and defeated... I have tried lots of tricks on this thread (changing interactive values, undervolting, lowering freq speeds) and my screen time can't get over 2.5 hours and 15 hours of battery life...

My current configuration is CNA 3.8 and franco milestone 6, I can't find a way to keep my BBS stats to survive a charge
[Samsung Galaxy Nexus] mpokwsths:
Ridiculous screenshots :laugh: . Flat line and 76% for the screen means that you just had on purpose the screen turned on the whole time (probably at the lowest possible brightness and on a black background). This way you should have gotten 2:30 hours screen time for the 25% of the charge lost. Please don't post such obviously ridiculous screenshots...
[Samsung Galaxy Nexus] mariachi202:
To be honest, I was fairly disappointed by the looks of the S3. Piano f***ing glossy finish in 2012? The Nexus is a class or two above the S3 in build terms, and frankly, having used both, I couldn't notice any improvement in terms of speed in everyday normal usage. (browsing, net, Angry Birds)

Back on topic:

Franco, thank you!
[Samsung Galaxy Nexus] trailblazerz11:
r295 is really a sweet spot, no lag and smooth and getting great battery.

What surprises me most if how much time it has spent in 192mhz and no lag, touch input works brilliantly. (Granted I've only been messaging and social media)

The only small issue is music stutters with 192mhz, have to set min to 348.

Heh I almost got a SGS3 but knew I would go AOSP roms anyways so got nexus for half the price, staying with nexus now.

Btw new evleaks pic of nexus 4, cant fathom if franco on it :eek:
[Samsung Galaxy Nexus] ÜBER™:
The N7 has no phone parts to it. So my guess is alot less ram is partitioned. Just a guess. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] venividivici87:
What's default scheduler in r295? about 2 gpu freq versions, have you noticed reasonable performance improvements or only an higher unjustified battery drain?
[Samsung Galaxy Nexus] yellowdie:
Deadline is default. And 384gpu is fast enough for me. I really have zero need for 512 anymore. :D

---------- Post added at 10:30 AM ---------- Previous post was at 10:24 AM ----------

Hey, Franco, you ready to tackle a new beast? :D

These are from Imoseyon:

http://www.imoseyon.com/2011/01/sysctl-tweaking-for-faster-longer.html

http://www.imoseyon.com/2011/02/sysctl-and-minfree-tweaks-revisited.html

http://androidforums.com/esteem-all-things-root/532317-tweak-wip-sysctl-conf-tweaking.html
[Samsung Galaxy Nexus] Sik-1:
Lmfao would be a **** wouldn't you, unfortunately for you I have been using my phone in the same pattern I use everyday, ppl lie numbers don't, step your game up and have some fun playing around with the kernel

Then maybe you can achieve something close lol
[Samsung Galaxy Nexus] Kurre:
And no extended battery either? It seems quite common that people "forgot" to mention it..just to brag with screenshots :rolleyes: but I ain't saying that you do that :) batterylife erg this kernel is awesome :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Sik-1:
Stock battery, no need to brag tho, if u check a couple pages back you would see I'm using extremely low voltages and they have been working like a dream
[Samsung Galaxy Nexus] shawnaye:
Praying that franco will get a LG nexus and start developing as soon as the sources are out :D
[Samsung Galaxy Nexus] franciscofranco:
Been there a lot of times but quite never found an optimal pattern. I will think and post some values when Im confident enough they are a good starting point.
[Samsung Galaxy Nexus] franciscofranco:
Yes I will get buy one as soon as its available.
[Samsung Galaxy Nexus] kmjo29:
Anyone know why my max cpu keeps setting itself back to 1200 mhz? Crazy thing is this kernel doesn't have 1200 to choose from. I'm running Are you jellin 4.1.2 with 295 512
[Samsung Galaxy Nexus] lupor0x:
i'm on cyano10 (22/10) with franco milestone 6 kernel... some little lag but the battery life is good :)

thanks franco
[Samsung Galaxy Nexus] yellowdie:
Install r295! DO IT!!!!! :D :D :D
[Samsung Galaxy Nexus] venividivici87:
.. In doubt... I flashed r295-512 :D

With Rom Vanir AOSP v3 seems to fly... But after some battery cycle I'll give feedback

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Hans QC:
I'm on r295 with 512GPU and scrolling is stuttering a lot in Tapatalk and G+. This is with stock settings. Any suggestions?

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] yellowdie:
Franco, I approve! :victory:

4 hours of screen on time with the stock battery. Mostly just testing lag and speed throughout the phone, some web browsing, some gaming, and lots of XDA :p. But that also include multiple reboots (some SODs thanks to UVing) and autoflashing r295 as well. So the second battery cycle will be even better! Wifi was on the whole time.

I have 192MHz UVed to 730mV. The only other thing I've changed from the stock r295 is my max CPU is 1036, and both my input_boost_freq and hispeed_freq are at 729. I really like the CPU Spy stats. Most of that was overnight, so there's a lot of deep sleep, but I am really liking the ratio of the actual speeds:

14% @ 192

2% @ 384

3% @ 729

1% @ 1036

My phone is FAST!!!!! Boss Man, you blow my mind. Thanks! :):D:laugh::good:
[Samsung Galaxy Nexus] gm007:
I remember the time when i used my x10 http://xdaforums.com/showthread.php?t=934486&page=16

And there is an app in playstore to configure those settings

https://play.google.com/store/apps/...utm_medium=organic&utm_term=sysctl+play+store
[Samsung Galaxy Nexus] duduzinho15:
Nobody will help me?? :(
[Samsung Galaxy Nexus] yellowdie:
Reflash it. There shouldn't be shuddering. :D

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

Yeah, I've used the app, but personally, I like manually editing the files in ES File Explorer. :) But I also have it all set up in my custom init.d scripts.
[Samsung Galaxy Nexus] TEK112:
That is too random. Wipe both caches and reflash the kernel. If it persists consider a full wipe and start fresh. I do that every time I flash a new ROM and it avoids problems like this.
[Samsung Galaxy Nexus] yellowdie:
Sorry, don't want you to feel like your getting ignored. What were you asking? I saw you say something about crashes, but I thought Franco answered you.
[Samsung Galaxy Nexus] TEK112:
Have you tried running a 512GPU kernel before? Some phones can't handle it and do exactly what you described.
[Samsung Galaxy Nexus] kmjo29:
My max cpu was set to 1536. It keeps jumping back to 1200mhz. Why is this happening?

Also was TCP taken out of the Franco app?
[Samsung Galaxy Nexus] Stigy:
Running r295 on CNA 3.8 with 1305/384 (max off 729) and interactive with 6/7/5/3 and this is absolutely amazing.

Thanks for ALL the hard work everyone!
[Samsung Galaxy Nexus] yellowdie:
Franco said to do another autoflash.

And nope, mine is still there. Again sounds like a borked flash of some type. Try it again. :)

---------- Post added at 11:56 AM ---------- Previous post was at 11:54 AM ----------

Out of curiosity, what made you manually change min_sample_time from 60000 to 50000?
[Samsung Galaxy Nexus] Stigy:
Did some reading back a few pages and read that going down to 30000 was good for battery, but saw some lag so I tried going down to 50000 to see how it performed and so far so good. Honestly might try to go down to 40000 unless these values are not recommended.