yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] splus:
Ok, I just tested my good old favorite r241 to make sure I wasn't wrong about what I'm about to write, and I can say that scrolling is definitely smoother than on r275 and last few releases where GPU frequencies changed. I'm talking about 512 GPU kernel build.

From what I understood is Franco changed GPU frequencies for 512 GPU version of kernel from 153 - 307 - 512 MHz to 153 - 384 - 512 MHz. In theory this looks better and more logical (I was happy to see that change log) but somehow in practice it behaves less smooth and with more scrolling stutters.

It looks like GPU simply scales up to 512 MHz much less often than it did before, and therefore gives poorer graphic performance than it did on older pre r27x kernel releases.

It's almost as if kernel often thinks GPU speed of 153 or 384 MHz is good enough and doesn't scale it up to 512 MHz, where in reality that is needed. Or it doesn't scale it up fast enough as it used to do before.

I'm of an opinion that Apple aren't stupid for making their phones with super beefy GPU but with just an average CPU - fast GPU has much more to do with GUI smoothness than fast CPU.

Franco, here's a suggestion - is it possible to revert the GPU changes in last few nightlies to pre r27x frequencies for 512 build?

And also introduce (if this is possible at all?) a Min and Max GPU frequencies settings in your kernel app? Or at least have the configurable Min GPU frequency?

Still have two kernel versions, 384 and 512 GPU, but just have a little better control of at least the minimum GPU frequency. I know I'd keep my GPU always at min 512 MHz, I prefer perfect smoothness over little bit of less battery life...
[Samsung Galaxy Nexus] The Gingerbread Man:
Scrolling for me is almost perfect, I get the odd little stutter on xda app and that's more to do with the slider thing on the right side changing size. Perhaps try changing to a slightly higher or maybe lower CPU speed and change governor, interactive and lazy are best. Also in governor control if you put 1036800 hispeed_freq it gives you a nice boost as you touch the screen. Are you manually undrvolting? Perhaps too little juice will cause bad performance.

Edit

Enable force GPU 2d rendering stops xda minor stuttering

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] venividivici87:
I'm using Milestone5 with original JB rom. Setted governor LAZY, scheduler DEADLINE, undervolted 230mhz-875mV, 384-975, 729-1100, 1036-1200, 1228-1250.

Result: 5h4min screen on at 3% of battery, wifi always ON

undervolt is so stable... that i'm thinking to low down it further!
[Samsung Galaxy Nexus] T-Loop:
I was on a testing spring and tested several other kernels. After coming back to franco's 275 I was royally surprised. This is a winner and works so much better than earlier versions I tried. It's fantastic to see development after some time. Congrats franco, fine build.
[Samsung Galaxy Nexus] Pkt_Lnt:
The r275 changes affect all governors for me.

Galaxy Nexus / Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Not sure what to tell you, I'm just going by what franco said here:

http://xdaforums.com/showpost.php?p=32016922&postcount=27805
[Samsung Galaxy Nexus] Pkt_Lnt:
Yes, I saw that as well, and in the changelog in the FK app. Something in my phone does not like r275. Display artifacts, hangs, lags, restarts a couple times. I always run the 384 GPS and usually 1035/384, 384 max screen off and lazy or wheatley governors (I need battery life more than speed). Every other kernel has been fine till now, so I am back to r273 and no issues. (shrug)
[Samsung Galaxy Nexus] Blackcrx:
are you guys using nstools to set your hispeed freq? when i use nstools it will not let me do specific numbers like 1036800but instead just 1000000

I have to manually go in with root explorer and hammer down the folders to make the change

also for some reason when i loaded the kernel it had 729000 as the stock hispeed freq
[Samsung Galaxy Nexus] osm0sis:
729 is the default. Why don't you just use Franco's app? Couldn't be simpler.
[Samsung Galaxy Nexus] franciscofranco:
After all I made a little confusion and that CPUSpy app bug that is caused by r275 is not related to the thread priority boost, but by another derp from me. I had no idea until now since I merged this changes to the N7 and CPUSpy was just fine.
[Samsung Galaxy Nexus] ectodroid:
Changed back to interactive from dyn interactive and stuttering in Tapatalk stopped.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TheMan0790:
Anyone find that, while on WiFi, the phone is constantly trying to pull in data? Is this a known issue?
[Samsung Galaxy Nexus] franciscofranco:
If you have an app requesting for data then Wi-Fi will be pulling that data. Otherwise it won't pull anything.
[Samsung Galaxy Nexus] andQlimax:
I would say this?

https://github.com/franciscofranco/Tuna_JB_pre1/commit/e11f0a75dffe53fd716bfb16a60eedb7dfe1a2f0

It say omap_getspeed(), and since cpusy is not able to get speed usage, it seem reasonable for me
[Samsung Galaxy Nexus] franciscofranco:
Just pushed r276 fixing the bug in CPUSpy.
[Samsung Galaxy Nexus] Blackcrx:
good point, i just purchased the app. haha
[Samsung Galaxy Nexus] yyz71:
Man franco your a machine :good:
[Samsung Galaxy Nexus] splus:
Thanks, but that's all "workarounds" for something that shouldn't be a problem.

Yes, xda has always stuttered, but now it stutters more. I'm talking about micro stutters that many others have reported some pages back since r272, not just in xda but elsewhere as well. It's not all the time but it skips a frame here and there, even in simple tasks. This was never happening before, on 384 and especially on 512 GPU.

Btw, CPU works great with r275, I'm just talking about GPU, where something is glitchy since r272. Maybe it's not easy to notice for most users since it's more like micro lags, but scrolling and swiping are definitely less smooth than pre r272 releases.

Dyinteractive is great on battery but way too choppy comparing to interactive, which I use. And yes, I've been using 1037000 in hispeed_freq since beginning, with max CPU 1536 MHz.

No undervolting, SR does its job perfectly.
[Samsung Galaxy Nexus] ralphcolumna:
Is r276 ready for download?
[Samsung Galaxy Nexus] TheMan0790:
Makes sense, but I don't have any apps pulling in data. It just keeps trying to do this while on idle, actually. Thoughts?
[Samsung Galaxy Nexus] Mayday_XL:
Thanks for the update.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] chugger93:
R276 confirmed good with cpuspy. Nice!
[Samsung Galaxy Nexus] franciscofranco:
Try to up the Core voltages, I messed with them since r272.
[Samsung Galaxy Nexus] The Gingerbread Man:
276 = m6?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
I hope so, lets give it a few days without a release to see how it works for everyone.
[Samsung Galaxy Nexus] Culex316:
What were the CORE voltage settings before you lowered them to 1125mv (for 384 GPU)?
[Samsung Galaxy Nexus] The Gingerbread Man:
You deserve a good rest with all these releases recently!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
LOL I really enjoy this, if I didn't I wouldn't release a single **** ;)
[Samsung Galaxy Nexus] franciscofranco:
#define OMAP4460_VDD_CORE_OPP50_UV 962000 -> first nominal Core entry

#define OMAP4460_VDD_CORE_OPP100_UV 1127000 -> second nominal Core entry

#define OMAP4460_VDD_CORE_OPP100_OV_UV 1250000 -> third nominal Core entry

Thats before the changes. Smartreflex would come in and calibrate all of those.

Now:

#define OMAP4460_VDD_CORE_OPP50_UV 950000

Smartreflex won't calibrate that, it will be pure 950mV.
[Samsung Galaxy Nexus] kyokeun1234:
Lol I wish I could learn making kernels :p
[Samsung Galaxy Nexus] silverhunk:
What does kernel stable version have that nightlies version does not have?

What is the difference between them?
[Samsung Galaxy Nexus] Kurre:
It's just the opposite..nightlies have so much more than the latest stable version (milestone 5). There's a link to changelog somewhere (in OP probably? :p) just go for the latest nightly..so far it's stable and fast :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] silverhunk:
Is antutu benchmark reliable? Because stable milestone 5 has more score than the nightlies. Thats why im on milestone 5 :)
[Samsung Galaxy Nexus] kyokeun1234:
I dunno how milestone compared to nightly since I've never used milestone, but benchmarks are never reliable. Take them as grain of salt

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] nicholaschan24:
Franco, loving the kernel! Phone flies! Any chance of joining in with Googles 25billion app celebration and discounting your app? :p
[Samsung Galaxy Nexus] kyokeun1234:
I personally would disagree with this sale personally since less money we pay means less money he gets. That means we're supporting him less :p

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] ÜBER™:
Not necessarily if he would have it discounted and crap ton of people bought.. just like a crap ton of people use his kernel.. he'd make bank thats the whole scheme behind discounting numerous apps.
[Samsung Galaxy Nexus] goTouch:
I don't know if Google promotes an app that needs root.
[Samsung Galaxy Nexus] Blackcrx:
agreed. i used to benchmark all kernels to compare but after a while you will realize that benchmarks could and will be biased. I just started going with user feel and experience.

flash a kernel, use it for a couple days, flash a new kernel and compare.

some kernels you can tell the difference right away
[Samsung Galaxy Nexus] wyattn:
Has anyone else seen any odd drains during airplane mode? The 24x series seemed to be doing better (losing 2% instead of 25 over an 8hr period) that the 27x. Battery stats isn't showing any odd outliers. Is there something I should be looking for?
[Samsung Galaxy Nexus] Astug:
275 is so good! 16 hours idle (data enabled), 30min of screen on, still 80% left!
[Samsung Galaxy Nexus] tobitronics:
What are your kernel settings? I just keep failing to get a good image of my battery life cause every day im flashing something new because of an update xD. However i think my battery life is a bit off on this one.

Beamed from my Paranoid Google Nexus 7
[Samsung Galaxy Nexus] TheMan0790:
So...does anyone have any reason why my wifi is showing that it is pulling down data when in idle, even though I have no apps attempting to pull down data?
[Samsung Galaxy Nexus] The Gingerbread Man:
Nope but if you turn data off it will stop

Sent from my Galaxy Nexus

---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------

Try leaving things to settle, takes a couple of cycles. My battery is lower today for the time of day than normal because of these updates.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Dunno how that works, I think its Google that chooses what apps they want to discount or not, we, developers, have 0 power over that.
[Samsung Galaxy Nexus] zephiK:
Wouldn't make sense for it to be a $0.25 app, majority of the Android community wouldnt understand the purpose of the app and it has limitations due to it only working for some phones and not all.
[Samsung Galaxy Nexus] haxor:
i don't know what's going on my nexus after flash kernel my phone don't allow me to install apk file and it is not allow me to select any right hand side option like yes :( i am on stock jelly bean ! when i am trying to backup my all install apk and data through toolkit then my on screen option Back Up My Data not has been select except Do Not Back Up
[Samsung Galaxy Nexus] Hungry Man:
With the latest 512mhz kernel I can't undervolt anywhere close to before. For example I could undervolt the CORE 512mhz frequency to 950mV (turning SR on/off didn't effect it). Now I've just crashed at 1100. Actually it just seems to be the 512mhz frequency that's not undervolting like before.

edit: The crash may have been caused by something else. Testing more.
[Samsung Galaxy Nexus] ssCISengineer:
I love how so many of you speak FOR the developer, and even defend him. Let the man speak for himself and just listen instead of always trying to TELL somebody something. And no I don't care at all if you like or dislike this post. I just read instead of preaching all the time. Can't ban me from doing that.

please remember to thank me for e-peen points!

Sent from a Galaxy Nexus between here and there.
[Samsung Galaxy Nexus] Hungry Man:
He's already stated that developers aren't the ones who decide it's Google. IDK why it's still being talked about.
[Samsung Galaxy Nexus] CADude:
Because cheap assholes are trying to pay a quarter instead of paying a few bucks more.
[Samsung Galaxy Nexus] Hungry Man:
@Franco,

Would it be possible for us to set our own SR values? For example I can undervolt my 512mhz (as of this latest kernel) to 1010mv. I would assume that under very little load I could undervolt another 10mv or however much (maybe more). It would be a really cool feature if it's possible.
[Samsung Galaxy Nexus] ChazzMatt:
Agreed.

If you can afford $350 + tax + shipping for this excellent phone, you can afford a few more dollars for the kernel/app (and help the developer) that makes it run like a speed machine.

_____________

Galaxy Nexus GT-i9250 | xda premium
[Samsung Galaxy Nexus] creeve4:
Running r276 with CPU 384 min, 1305 max with these governor settings for interactive:

The CPU never goes above the hi speed frequency, 1036 MHz, even when fully stressed (e.g. StabilityTest)

With these same settings on r275 I was seeing 5 to 10% of the CPU use at higher frequencies under normal use.

My phone feels a bit slower is some scenarios.
[Samsung Galaxy Nexus] koax88:
change it to any other governor, then change it back to interactive solve issue for me
[Samsung Galaxy Nexus] creeve4:
Switched to several other governors for a few minutes each, then back to interactive. Still capped at hispeed_freq.
[Samsung Galaxy Nexus] THE_KINGDOM:
Wondering if it's normal that most times I open the Franco app it needs to 're-request root permissions..?

Does this happen for others here?

Doesn't this mean the app may not have sufficient privileges to control various kernel settings..?
[Samsung Galaxy Nexus] billykxda:
A few pages back, a poster asked about settings for best performance and settings for best battery life. The first response was:

For ultimate I would recommend:

Min: 729

Max: 1305

Max Screen Off: 729

Hispeed_freq: 1305

For battery I would recommend:

Min: 729

Max: 1036

Max Screen Off: 729

Hispeed_freq: 1036

Then, on-going discussions and posts corrected/modified these values back/forth - it was a bit confusing. Will someone please provide the final answer?

Also, are these settings one person's opinion, or the general consensus here?

Thanks!!
[Samsung Galaxy Nexus] creeve4:
A reboot seems to have fixed it, but if I change the max frequency, the CPU is again capped at 1036 MHz until I reboot.

Definitely related to hispeed_freq. Whatever it is set to, the CPU is capped at the closest lower frequency.

Edit:

It was going higher for a minute or two after the reboot, but now it is stuck at 1036 again.
[Samsung Galaxy Nexus] osm0sis:
They are only opinions, there is no final answer since everyone's phone is different (due to variability in the manufacturing process), and differences in personal usage. The only definite answer is what works best for you, so we encourage you to experiment.

I can tell you that I value performance, and with my device, settings and usage I still got 2h 55m screen on, and 22h on battery with r275. Pretty good numbers for the 1750 mAh standard GSM battery.
[Samsung Galaxy Nexus] kyokeun1234:
That's pretty good for overclocked gnex! Is this wifi only or 3g too? Thanks

Swyped on my Galaxy Nexus running AOKP with Franco Kernel
[Samsung Galaxy Nexus] billykxda:
Thanks osmOsis.

I'll check your settings.
[Samsung Galaxy Nexus] christophicer:
276 I had multiple heat issues with my phone running everything the exact same from 262, phone was running at 45 degrees and didn't change a thing. Rolled back to 262 and heat issues disappeared.
[Samsung Galaxy Nexus] Hungry Man:
I think the app has a CPU hanging issue or something. I was clocking up to 1.7ghz for like over 30 seconds. I killed the app and it all went back down to normal.
[Samsung Galaxy Nexus] franciscofranco:
45ºC is not heat, thats a normal temperature for the CPU.
[Samsung Galaxy Nexus] klobkelosh:
I've had a bunch of Wi-Fi data drops on 276 running on stock toro jb. Have to do the old airplane mode trick to get out working again. Thought it might be kernel related - haven't added new apps or changed system at all and i know you tweaked something to help prevent data drops. Let me know if any logs would be of assistance.
[Samsung Galaxy Nexus] yellowdie:
Those were my recommendations, and they were the accurate numbers, but yes, just my opinion. :) Like osm0sis, I value performance. I normally get 2.5-3 hours of screen on time and about 24-32 hours of total life. Stock battery. Wifi on 100% og the time. Brightness is either 50% or 100%. =)
[Samsung Galaxy Nexus] momomok:
Google has released new binary for JRO03R, which contains binary of Wifi & bluetooth

Is that newer than the one in the latest kernel? Or is the binary for something else?
[Samsung Galaxy Nexus] franciscofranco:
Binaries = userspace. Kernel = kernelspace.
[Samsung Galaxy Nexus] momomok:
Lesson learnt. Thanks for the clarification :)
[Samsung Galaxy Nexus] J-Hop2o6:
Franco. I flashed r276 earlier today, got artifacts ("sparkles") when playing a 3D game (Asphalt 7) using Interactive & OnDemand. Rebooted the phone and still got the artifacts. Flashed back to r268, all is good, no artifacts :good:

As for the others guys that value performance like me (1.5GHz+512GPU & 50-100% brightness), you guys have some low screen on battery life. I normally get around 4 hours, and i'm using the stock 1750mAh battery.

---------- Post added at 09:21 PM ---------- Previous post was at 09:20 PM ----------

I learn something new Android related every week. Thx Franco!
[Samsung Galaxy Nexus] doomed151:
Just wondering, since 512 MHz GPU is too high for some phones, is it possible to add one more step? I'm thinking 448 MHz.
[Samsung Galaxy Nexus] franciscofranco:
Been there, done that, not viable.

People stating artifacts and the likes, try to increase Core voltage plz.
[Samsung Galaxy Nexus] Hungry Man:
Is setting our own SR values possible?
[Samsung Galaxy Nexus] w04g005:
Random_Reboots

Hey guys,

since i've installed latest Kernel r276 and CNA 3.6.0 i get a lot of random reboots. I don't know if it's kernel related. Attached is the last_kmsg

It would be nice if someone who knows a little bit more about it could have a look on it.

I searched for "error" and found some "omapdss DISPC error: SYNC_LOST, disabling LCD" i think that could be the reason for the reboots.

Thanks in advance

Matthias
[Samsung Galaxy Nexus] viscocesco:
I've the same configuration,no issue,try to flash CNA with full wipe and than Franco Kernel.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] mrfleetwood:
Same rom & kernel here, absolutely zero abnormal reboots.
[Samsung Galaxy Nexus] w04g005:
Thanks. I made a full wipe before installing CNA. Maybe it is undervolt related!

My Preferences are:

1228 Mhz - 1200 mV

1036 Mhz - 1100 mV

729 Mhz - 925 mV

384 Mhz - 775 mV

230 Mhz - 775 mV

Governer is interactive

greetings
[Samsung Galaxy Nexus] Kappa Lamda:
Definitely the UV may be the main reason... I used to undervolt and never got under 820 for 384MHz without reboots... If you aggressivly undervolt then reboots may appear!

Why dont you give SR a chance... For me it does a great job. No need to undervolt and mess with these things!
[Samsung Galaxy Nexus] haasgo:
Thx franco! Just purchased the pro version and here are my results. I AM USING THE STANDARD BATTERY BTW :thumbup:
[Samsung Galaxy Nexus] kyokeun1234:
baked?
[Samsung Galaxy Nexus] haasgo:
Nah u holdin?
[Samsung Galaxy Nexus] tobitronics:
GIVE.....ME......SETTINGS......NEED.....TO......HAVE......MORE JUICE :D :D :D

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] billykxda:
Thanks!

-bk

---------- Post added at 08:30 AM ---------- Previous post was at 08:26 AM ----------

Ditto!

Would be great to see what you are up to!
[Samsung Galaxy Nexus] GrenW:
Get that myself. Although not all the time. I flash a new rom/kernel every 2-3 days so I lose track though...
[Samsung Galaxy Nexus] andQlimax:
EVERYTHING depends ONLY in the way u use ur phone and ur apps...i have default settings and i usually get 4 / 4.30 screen on time every day
[Samsung Galaxy Nexus] venividivici87:
My configuration and Battery performance

Governor Lazy, scheduler deadline

GNex Tapatalk 2
[Samsung Galaxy Nexus] billykxda:
I agree, to a degree. I use my phone in a very consistent manner from day-to-day. I've seen differences in battery life between kernels - for sure - with my use being held consistent over time. I've switched back to certain kernels and have observed repeatable outcomes regarding battery savings and performance.

Trying someone else's settings is not going to guarantee that you will get the same result - understood - b/c then we are introducing differences in use, specific hardware, and software environment - too many variables to predict a specific outcome. But it is interesting (at least to me!) to see what other users are doing to coax extra battery life and performance out of their phones.
[Samsung Galaxy Nexus] djjonastybe:
You shouldn't worry about CPU or GPU overclocking. This freaking amoled screen is drawing everything.

I found that undervolting the LCD panel by 200mv was still very stable. Didn't notice much difference in battery life.

I am still working on CyanogenMod working out some stuff to save battery more easily. I was thinking about adding a multiplier for the brightness. But I think it's best to put this into the framework of a ROM. This way we don't have to mess with each brightness level individually, and all you have to do is adjust brightness multiplier.

I found out that undervolting the GPU is very dangerous. The GPU seems too damn sensitive. Even a marginal decrease in voltage is enough to crash :/

IVA is easy to undervolt, just undervolt until you hear cracking sounds, then move it back up one or two notches.

To make a stable undervolt, make sure you add a 50mv safety margin. This is the ripple or noise value for the MPU.

The phone has overall a great battery life. I get 4 days easily if I don't play games or browse the internet
[Samsung Galaxy Nexus] bradm23:
How are you undervolting the display? Is that an option in Franco app or elsewhere?
[Samsung Galaxy Nexus] pphi:
Location via Wi-Fi seems to be broken on the latest nightly for jelly bean.
[Samsung Galaxy Nexus] mohaimed:
what is your maximum and minimum cpu speed? are u facing any lags?is it on stock battery?
[Samsung Galaxy Nexus] franciscofranco:
Its done on the kernel source and its not avaliable anywhere in the userspace. No I wont add it, been there, done that = 0 impovements = more instability.
[Samsung Galaxy Nexus] bradm23:
kernel wakelocks

Seems like I get a lot of modem_USB_gpio_wake and modem_USB_suspend_block wake locks respectively. I get these a lot with different ROMs I try. Anything I can do to reduce these? I have about 3 hours up time and there is about 5 min of wake time for gpio and 4 min of suspend.

Funny thing is that sometimes a reboot fixes it where the wake time stops and idle life becomes great again, however sometimes a reboot doesn't do anything.
[Samsung Galaxy Nexus] zenzip:
goog setting, but i prefer a little more blue, and a little more dark... for the rest your setting are close to perfect :D

awesome!
[Samsung Galaxy Nexus] yyz71:
Damn that's sweet :D
[Samsung Galaxy Nexus] zenzip:
really battery friendly but performance are bad with lazy governor....i'm using intercativ with franco default setting and performance are really smooth, maybe fastest of ever! min 384-1420...batterylife is around 20h, and 2,30h of screen on.
[Samsung Galaxy Nexus] yellowdie:
Try mine: r200, g150, b250 - Gamma: 5/10/15 - Trinity: 15 - OMAP: 1.2 (I like 1.0, but 1.2 will give you the darker look) :laugh: