yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Chad_Petree:
The gpu at 384 is supposed to have better battery life versus the 584 gpu with better performance? That's just my guessing

What's the stock frequency of the nexus gpu?
[Samsung Galaxy Nexus] jnr21:
Install this and choose cold preset.
[Samsung Galaxy Nexus] Diger36:
Hi Franco, just want to say thanks. I stayed at r154 a little to give the testing some time. Yesterday I managed to get 14,5 hrs standby, 4 hrs screen on and 16% battery left on stock 1750 battery. And fluid and smooth. For me this is awesome . So thanks again, switching to r156 now.
[Samsung Galaxy Nexus] kecinzer:
156 is first build with I experienced heating. CPU temp was realy high and battery went down realy quick. I dont have facebook app. After flesh of cm nightly again (cm kernel returned) problem went away. Btw. 384 version.
[Samsung Galaxy Nexus] Stretlow:
+1 for the heat issue being back. For the first time, i saw francos widget hit 70 degrees
[Samsung Galaxy Nexus] nklenchik:
I must be the only one without heat issues...
[Samsung Galaxy Nexus] Chad_Petree:
Whoah! In 100% brightness looks great, almost all I wanted my galaxy nexus screen to be, but in automatic/medium brightness looks too blueish :(

Guess we can't have a perfect screen :(
[Samsung Galaxy Nexus] giugiu:
Ciao Franco,

During the day I often change the kernel parameters to fit the type of use of the phone. For example:

- lazy, Hotplug on,192 min 729max when I listen to spotify

- interactive, 384 1300 max when I actually use the phone for browsing, texting

- and so on.

Would be cool to have a functionality to save kernel presets and a widget to quickly enable them.

Just a wish/suggestion based on my needs, from what I read from the previous posts people stick with mainly 1 configuration.

Ciao and thank you

Giulio

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Metallice:
No. Nobody agrees with you. Just like everyone likes Coca Cola and hates Pepsi. Also everyone knows Edward is Bella's true love not Jacob.

Subjective opinions on the relative importance of Battery vs. Performance and thus the best balance between the two are, in fact, subjective opinions.
[Samsung Galaxy Nexus] Metallice:
Nobody has heat issues. Its the result of people obsessing over stupid numbers and mob mentality.

Fun fact, when battery percentages are visible in the statusbar overall battery life magically gets worse.
[Samsung Galaxy Nexus] nklenchik:
I can't really complain about battery life. I get a full 12-16 hours on moderate use: heavy texting, heavy music minimal calls, light gaming, checking a few articles online
[Samsung Galaxy Nexus] linuxlainen:
To be honest, I didn't notice real difference in battery life between stock and frank 150.

Testing 156 now and keeping my fingers crossed :)
[Samsung Galaxy Nexus] psyren:
I reported a heat issue a number of pages back because I physically felt my phone getting quite hot when doing something that was (apparently) not very CPU intensive.

I have no obsession with battery life or whatever, since my phone use can only be described as 'fairy-like'.
[Samsung Galaxy Nexus] Puzzlegirl:
Stroppy... You're not exactly helpful are you? I've had occasions when the phone gets extremely hot. You don't need to obsess over 'stupid numbers' if you use senses you were born with, such as touch.
[Samsung Galaxy Nexus] MS.:
I'm Getting really good battery life with latest kernels (154/156). 1 day 21 hours since last charging, 2 hours 16 min screen on time and still 42% to go. And no more of weird heat that i had on M3, well done.
[Samsung Galaxy Nexus] :
Seems that we come closer to Milestone 4 :D

Taptalked by GNexus
[Samsung Galaxy Nexus] dpaine88:
THis is just what I just started testing out, so far so good!
[Samsung Galaxy Nexus] Culex316:
I have also been getting very very good battery life with this latest nightly kernel (interactive, min 192mhz max 1225 or whatever it is) This kernel + extended battery now practically gives my Galaxy Nexus battery life as good as my last Blackberry. Easily get over 3 hours screentime with a medium brightness setting.

Great job Franco!
[Samsung Galaxy Nexus] Langduscher:
r156

Rom: Bamf Paradigm 1.25

Kernel: franco.Kernel r156 (384)

Use: mostly browsing, playing light games (like Wordfeud), texting, Gtalk/ Whatsapp, a couple of short phone calls

Conditions: was on strong wifi signal for >90% of the time, extended battery (2000mAh), no inverteed browsing nor inverted themes etc, screen brightness @ ~80% (!!!)

Really, really liking r156 (384) so far (only really been on wifi), absolutely no issues

r156 (384) settings:

192/ 1036

interactive gov (input_boost ON)

SR ON/ SQLite ON/Generic hotlplug ON

OMAP4 Gamma @ 1.2

Result :eek:

Total time on charge was ~9hrs (so fairly heavy usage)

And no temp probs here, temp always hovering around 40C

Could EASILY go over 6h screen-on if I used auto brightness, but the screen just looks too good :D

Going to change radio (I am now on XXLA2), to see if I can get more out of the screen on time when on data. Im mostly have poor reception at my whereabout. Usually I get 3 to 3.5hrs screen on time when on data.
[Samsung Galaxy Nexus] wilwilwel:
I'm using the R156 with AOKP M5 release.

I've done a full wipe.

When i try to activate the hotplug with "echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled" command. Which was run as SU. Im getting an error "cannot create ... no such file or directory"

cannot see whats going wrong
[Samsung Galaxy Nexus] relax24:
/sys/module/omap2plus_cpufreq/parameters/generic_hotplug
[Samsung Galaxy Nexus] wbknox:
franco

can you increase voltage to wifi in your next nightly(512)?
[Samsung Galaxy Nexus] eezdva:
When the screen is off the wifi ain't working. Don't get any notifications.

The Fugumod kernel works. Not sure what you did different . But heard many good things about this kernel. So would love to try it but can't :(
[Samsung Galaxy Nexus] Sveke:
Franco,

I just wanted to say that I have no problems whatsoever.

No wifi issues, no heat issues, nothing.

I'm going with user error 100%	of the time.

Well done. Keep it up. Thanks.
[Samsung Galaxy Nexus] sing1gnis:
Wifi has been crapping out on me with the screen off too. Doesn't happen every time though. I use gtalk a lot and I won't get a new message until the screen comes back on.
[Samsung Galaxy Nexus] eezdva:
Have it always so makes the kernel unusable for me sadly
[Samsung Galaxy Nexus] Langduscher:
So, which version (384 vs 512) and what settings do you guys use? I'm experiencing 0 problems.

(Have to admit my Gnex accepts anything Francisco throws at it :D)
[Samsung Galaxy Nexus] Akik:
Is it better to use the latest nightly or the stable version (milestone 3 I guess)??
[Samsung Galaxy Nexus] Langduscher:
Try for yourself mate. Not 2 Gnex's are the same and not 2 people use it the same way either. Flash both and stick with what works best for ya :)
[Samsung Galaxy Nexus] sing1gnis:
I'm using the 512 version. I really didn't have an issue until 156.
[Samsung Galaxy Nexus] eezdva:
Milestone 3
[Samsung Galaxy Nexus] Langduscher:
With M3 you should be good on wifi :confused:

and yeah from r156 Fransico lowered wifi voltage. So your phone may just not like that.

What settings do you use in the kernel app?

And what Rom?
[Samsung Galaxy Nexus] eezdva:
Not using the kernel app ;)

But I'm on AOKP Maguro
[Samsung Galaxy Nexus] The Nexus Project:
156 is running smoothly so far

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] drawde40599:
Or EVERY SINGLE phone is different and u have no clue what ur talking about " user error" out of the bajillion comments I've seen that was the smartest o_O!!
[Samsung Galaxy Nexus] jcmm11:
To all the people having wifi problems only when screen is off - do you have wifi-pm turned on? Franco's app or an init.d script

-----

# wifi fast to allow wifi to maintain fast connect when screen off

if [ -e /sys/module/bcmdhd/parameters/wifi_pm ]; then

echo 1 > /sys/module/bcmdhd/parameters/wifi_pm

fi

-----

Franco already said he'll boost the voltage again in the next nightly in case this doesn't solve the issue.
[Samsung Galaxy Nexus] KingDavid63:
How's everybody liking nightly 156?
[Samsung Galaxy Nexus] nodstuff:
+1

On another note, why does the 512 version work with my phone now? o.O

Went to America for a month, got home and my phone now likes 512.

What have I missed??

What sorcery is this, Francisco???
[Samsung Galaxy Nexus] drawde40599:
Then please explain y my phone slows down to a crawl making it unusable?? , and says 70°c++?? Coming from fresh unlocked bootloader?So "hot " I can feel it threw my jeans???

I like this kernel, have since 1st build but once in a while it gets really hot, i wouldnt call being on internet for 5-10 min excessive use either! Ive used other kernels and this dose not happen, ( then go use one of them u say; ) I am but rather use this one, if Franco don't want feedback he wouldn't put out a new build every few days, maybe u don't mind ur phone doubling as Hand warmer but its not normal and that's ur choice ....
[Samsung Galaxy Nexus] Sveke:
Maybe the air up there is to thin and you should come back down to the lower 48 before you say more stupid ****.

If your having issues, self diagnose and figure it out. Oh yeah there's this thing called Google too, very useful.
[Samsung Galaxy Nexus] drawde40599:
That's what u came up with??? Its cute! I don't have time for u . OK by!!
[Samsung Galaxy Nexus] franciscofranco:
Enough.
[Samsung Galaxy Nexus] psyren:
Would like to report more heat issues. This time, I was doing a crossword (Shortyz), and the CPU was stuck at max freq the whole time (1228). Temp was capping at 75c. Android's battery stats say the program only used about 40s of CPU time. Just rebooted and did a cache/dalvik wipe, phone is still very hot, and lagging very badly while I'm typing out this message.
[Samsung Galaxy Nexus] nodstuff:
Every phone is different, ergo, some people will experience problems others don't. Not necessarily "user error"

You aren't as smart as you think you are, in fact, you may need to self diagnose. My money is on narcissist.

Snide remarks aside, stop being condescending.
[Samsung Galaxy Nexus] rmcsc:
Wow, what a snotty, racist bastard you seem to be. :screwy:

Franco: after a day of usage of M3, I gotta say I'm liking it very much. I'm gonna get your app soon to be able to use the kernel to its max potential. :thumbup:
[Samsung Galaxy Nexus] nklenchik:
I know we've probably been over this but, artifacts...solution? I'm on the - 512 gpu on 156
[Samsung Galaxy Nexus] Metallice:
Two possible solutions. Raise voltage / Use 384 instead. Well or raise regulator voltages but I doubt that's it unless it continues with 384.
[Samsung Galaxy Nexus] Gahh Its Lee:
I figured out I can use 512 if I turn off smart reflex but I'd love a solution to keep it on and use 512
[Samsung Galaxy Nexus] moe6:
watercool your gnex
[Samsung Galaxy Nexus] Gahh Its Lee:
Heats not the issue lol. I'm almost surprised I haven't seen one yet I've seen everything else watercooled
[Samsung Galaxy Nexus] dpaine88:
Those of you with issues on 512 GPU, which issues are you having? I'm running it but so far no noticible issues playing games and such.
[Samsung Galaxy Nexus] Metallice:
You're better off not running it then. Smart reflex gives way too much voltage as is with 512mhz. Like 200mV more than I need to run it. If your phone can't handle it unless its using even more than that... I would just stick with 384...

Sorry its not the solution you were looking for.
[Samsung Galaxy Nexus] ra990:
I am running AOKP milestone 5 with Franco nightly 156 (384 GPU). No issues so far, here are some screenshots of the excellent battery life:

BTW, franco - it would be cool if your kernel app had an option to reset all kernel settings back to stock. I frequently play around with it and would be nice if I could easily undo all my changes if something messes up without editing any files or doing a system restore.
[Samsung Galaxy Nexus] BrUhNiGGs:
Hey Franco are you ever going to make it so you can set the voltage values for CPU, GPU, and IVA on boot on future updates of your app? And where is the file located that changes values so I can make an init.d script
[Samsung Galaxy Nexus] jnr21:
+1

Older 512 gpu nightlys doesn't work for me but r156 512 version works without any issues.
[Samsung Galaxy Nexus] drawde40599:
Manage apps/ Franco app / clear data . Or Titanium backup /Franco app / clear data, u can use for now no need for wipe /restore
[Samsung Galaxy Nexus] digweed4me:
I am using r156 with 512 gpu it tends to get get little hot when I watch you tube video around 59c . I am loving it those hd YouTube looks amazing .
[Samsung Galaxy Nexus] rubino90:
My expirence with franco 156 (384gpu) and foxhound 0.6 ondemand no gen hotplug little undervolt (see image) brightness 25% and set up threesold 90 no lag no issue in games or graphics and all with stock battery!!!! Thanks franco
[Samsung Galaxy Nexus] yyz71:
loving 156 http://img.tapatalk.com/.. I'm using 192 min, interactive, hotplug enabled and this is from constant usage,I'm happy with these results. Thank you Franco :)

Sent from M5
[Samsung Galaxy Nexus] krex:
Please, does anybody explain me how BLX works here?

No, please don't point to search. I've already read Ezekeel's thread about it when I had Nexus S anno though I didn't use it, and today I've done again because now I want to.

My problem is that whatever value I set for BLX, my phone charges up to 99%...

Thanks!
[Samsung Galaxy Nexus] nikulogical:
Did some tests and min CPU of 192 had zero impact on battery life vs 700. (Used interactive Max 1350 for both) but it did bring some lag so I think a min 700 is still ideal or most usage patterns.
[Samsung Galaxy Nexus] Metallice:
Displayed 99% = BLX% of actual capacity.
[Samsung Galaxy Nexus] Metallice:
Well I find that 192mhz - 1500mhz Lazy is better for battery. Obviously one of us must be wrong because we can't both be right. RIGHT? Its not like people disagree on things or have differing opinions or have different phones, or have different usage patterns that we both consider normal because to us our usage seems normal right? :)

View attachment 1045177
[Samsung Galaxy Nexus] nikulogical:
Did you add the 1500mhz step yourself?
[Samsung Galaxy Nexus] franciscofranco:
Yes he did. Im still thinking of the best way to add 1,5ghz to make it work for everyone without ****ing the other half of users that dont want to use it. We have DCC, trim and still smartreflex. All of those need to be harmonized.

Last time I added higher frequencies we were able to go to 1,65ghz but it was causing some major issues like heat, instability and worse battery life for half the users. I cant afford that again so until I figure out a way to harmonize the settings the high freqs are a no go for public nightlies.
[Samsung Galaxy Nexus] :
Is the latest nightly running fine ? 1,5HGz sounds great if it doesnt harm my cpu..but you should know it

Taptalked by GNexus
[Samsung Galaxy Nexus] nklenchik:
On some kernels I can't go past 1.4, or I can and it's slow as ****. Then I put my max back down and I'm good to go.
[Samsung Galaxy Nexus] nikulogical:
My device is able to handle every over clock I've thrown at it ( this kernel and lean kernal no trim exp builds) but I've never seen any advantage to over locking CPU. Even with the 1350 step I just use because.. why not. Doesn't affect battery life for me.
[Samsung Galaxy Nexus] franciscofranco:
Yes that happens because of the DCC. We're getting in a VERY VERY good place for battery life and stability, so this is going to be my primary target for this week.
[Samsung Galaxy Nexus] Flukester69:
is there some forced option in the nightly kernels that cuts mobile and wireless? I've noticed recently when my phone unlocks when its been sitting for some time that both my mobile and wireless are grey... just wondering...
[Samsung Galaxy Nexus] Flukester69:
Totally agree..700 is my min.
[Samsung Galaxy Nexus] nklenchik:
Cool beans man, keep it up. Just a heads up with more feedback today (no logs though)

These were my settings: r156 (384gpu), ondemand 192/1228, smartflex on, no hotplug

- When playing PowerAMP I'd get a stutter in the music when turning on my screen (I figure this could be because I'm at such a low frequency

- Had a random reboot later after that

I rebooted my phone this morning (first time since I installed r156) to get rid of any rogue apps/whatever.
[Samsung Galaxy Nexus] thien.n1:
For all who are having problems with slowdowns in GTA:

I recently bought GTA III and had horrible slowdowns with MS3 on my Sam Galaxy Nexus. So I just tried a new Kernel (r156 - 384 mhz gpu) and now it's runnung like hell.

Could it have something to do with the reinitialization of the kernel, when updating?

Thanks a lot for this great piece of work!
[Samsung Galaxy Nexus] nodstuff:
Its because of the faster gpu. 384mhz compared to M3's stock gpu @ 307mhz.
[Samsung Galaxy Nexus] jboy15:
Getting only 5 hours of this rom with r156-384mhz kernel. Is there something im doing wrong? Im just doing messaging.
[Samsung Galaxy Nexus] jboy15:
I edited build.prop tthats why it says nexus s. Lol
[Samsung Galaxy Nexus] SupWiz17:
You have done a great job with nightly 156. Actually such a great job with battery life on this release that my battery continued to charge itself after I unplugged it today lol. I gave my phone a quick charge to finish out the day and I unplugged it at 57% charge then about 15 minutes later I turned my screen on to check the time and noticed my phone was up to 64% while it was off the charger. I have never seen my phone do this before and thought it was pretty cool. You can see on the graph that it keeps climbing even after the charger was unplugged.

I think that the performance and battery life is great with this kernel and really like having the 192mhz as an option.
[Samsung Galaxy Nexus] fatappel:
Can't believe the response you got from morfic over there at that other thread Franco. Your kernel's better anyway in my opinion and I don't think I'd use his work after the way he talked to a fellow kernel developer no matter how good, just out of principal. Can't we all just get along?

While I'm saying hello, I'm using your kernel with aokp M5 and it's made a great build about as good as could be imagined. Thanks for your work.
[Samsung Galaxy Nexus] nikulogical:
Yeah that was uncalled for.
[Samsung Galaxy Nexus] nodstuff:
Where would I find said remarks?

Edit: Nvm, found em. What a ****.

I guess jealousy does that to people, what with trinity not being popular for gnex and all and Franco.kernel is doing all the business.

He had an attitude in his NS thread too. Some people get caught up in their works popularity and actually believe they are someone important, its sad coz all they are are people using pseudonyms on an internet forum.

Its not hard to be nice.

Francisco you're a decent guy which makes it a pleasure to use your kernel and post in your thread and we all appreciate your work, which is without doubt the best kernel here.

Haters gonna hate.
[Samsung Galaxy Nexus] andrew53517:
Yeah never using Trinity after seeing that crap. Franco FTW!

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] jnr21:
Min 729 is best for me too. I think that phone can go to deep sleep much faster with 729mhz than 384 or 192, so it gives better battery life. And i'm not saying that it's same for everyone, it's just my opinion.
[Samsung Galaxy Nexus] jnr21:
Where is that other thread?
[Samsung Galaxy Nexus] nodstuff:
Go back about 4 or 5 pages in morfics thread.
[Samsung Galaxy Nexus] zimphishmonger:
Ok, Franco threw in a comment, Morfic got a lil heated as he already knew that and didnt feel he needed the input, end of story. Ive been using the guys stuff for a while, talked with him quite a bit.....he like kernels a certain way, no jealousy, just his preference. I can tell you he does NOT care about his kernels popularity. Theres no one kernel to rule them all and theres No need to rehash drama. Flash whoever you like.....:cool:

Personally, Im enjoying the work for all the different devs....Faux, Morfic, Ezekeel, Franco.
[Samsung Galaxy Nexus] nodstuff:
Well he did the same in this thread and was even a smartass about it and Francisco didn't throw the toys outta the pram, he took the advice as one dev to another. As it should be done. It's not expensive to have a good attitude.

That kind of behaviour belongs in kindergarten.

Nobody wants trouble but everyone deserves respect.
[Samsung Galaxy Nexus] Metallice:
Talking with imoseyon and having people test my builds via pm has shown that the big issue is with smartreflex. Working with imoseyon we got SR working with higher freqs by assigning unique fuse opps to these slots, however for about half of his users and people who've tried my builds smartreflex is too aggressive and calibrates 1.5/1.65ghz to voltages their phones can't handle and they instantly reboot.

Although its not a perfect relationship, for the most part it seems like people with hardware revision 10 can run SR1.5 with 1.5/1.65 while the voltages are too low for those with r9.

If anyone wants to try these freqs on 156 pm me, but let me know what hw revision you have and if it works for you or not. Also never bring my build up in this thread period. Pm only.
[Samsung Galaxy Nexus] jnr21:
Where to check hw rev?
[Samsung Galaxy Nexus] Gahh Its Lee:
Go to fastboot mode power off hold vol+ and vol- then hit power.
[Samsung Galaxy Nexus] Metallice:
You can also just go to settings > about phone> baseband version > i515.9 or i515.10

Edit: if you are on Cdma that is...
[Samsung Galaxy Nexus] nodstuff:
Only on cdma version.

GSM version has to be checked via the bootloader.
[Samsung Galaxy Nexus] Gahh Its Lee:
Wasn't sure what to put since this is the GSM thread lol. Hopefully we can all figure something out.
[Samsung Galaxy Nexus] franciscofranco:
Yes, I think the UV is still not working like it should...still waiting for coolbho's fix on that one.

Low frequencies have an huge problem: the race to idle is ****ed up. We want the device to enter idle as soon as possible, and having such a low frequency slows down that race because the device is running on a very low frequency, so it is awake for longer periods while it finishes its tasks, while with an higher frequency it would be ready so much faster.
[Samsung Galaxy Nexus] ro_explorer:
But when the device is not racing to idle and you do not have heavy stuff running you may want/need a lower frequency. In other words, the awake state should allow low freq.

// sent from my green robot //