yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] etche:
A couple of days ago I was running bigxie’s JB rom, with stock kernel, and tried interactive and ondemand for a couple of days each. Battery life didn’t seem to change very much, it was quite the same on both.. but with ondemand I was getting a lot of micro-stutters in all kind of places, as someone already stated. The one thing that was annoying me the most was with stock keyboard. I could see a big difference there between those two governors. With ondemand you can’t type as fast as in interactive. So I decided to keep interactive.

Now I’ll try 225 and see how well it goes.
[Samsung Galaxy Nexus] sway40:
With the volume thing, I don't think any rom has included a a volume fix yet since jb is so new, again I could be wrong.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mikeandjaimie:
Removed when we were still on ics nightlies cause it already does it by default and franco found it causing more problems then it fixed
[Samsung Galaxy Nexus] c_86:
Actually cm10 has it fixed. Volume is loud like ICS was.
[Samsung Galaxy Nexus] ntorresla:
What is "normal" deep sleep time?
[Samsung Galaxy Nexus] paratox:
i hope the 1344 or 1350MHz cpu steps will come back anytime.

this was the sweat spot for temperature / throttling / performance. 1420 is too much for my phone.
[Samsung Galaxy Nexus] LNJ:
So I've been on 225 for about 12 hours now and have to report that for some reason it's laggy especially after going back to home after closing an app or after wake.

Just microlags. Nothing major. 223 did not have this.
[Samsung Galaxy Nexus] barrist:
Did you stay on ondemand? It's the default governor in 225 (interactive was default for 223)
[Samsung Galaxy Nexus] laureanop:
Played with the phone for a couple of hours when to sleep and just woke up.excellent deep sleep numbers on 225 cm10

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] KJW979:
Volume on Droid Concepts also as was on ics, same with PE rom.
[Samsung Galaxy Nexus] muhsli:
ondemand set up like this deliver me the best performance imo.

running @ 384/1536 GPU-512
[Samsung Galaxy Nexus] MatthewYiu:
initially i had some lag, i sent on boot the below. rebooted and not it doesn't feel like it is stuttering at all. Running at 280 dpi with microbes live wallpaper too.

Running with 1536/384 min, ondemand, 729 maximum frequency for screen off, Running buttery smooth.
[Samsung Galaxy Nexus] loudaccord:
Not sure if this is related, curious if anyone else had this issue... flashed r225 and parts of my screen don't respond now. I was trying to type a message and certain letters wouldn't work. That's how I realized there were 'dead spots' on the screen. Rebooted, still there, fixed permissions, still there. Flashed 223 and everything is back to normal. I'm on Jelly Belly 3.8 if that matters.
[Samsung Galaxy Nexus] franciscofranco:
Never seen that happen with any of my devices, sure its weird.
[Samsung Galaxy Nexus] derPianist:
Exactly the same here with r225

!

via Google Galaxy Nexus
[Samsung Galaxy Nexus] zackpack:
Does anybody have suggestions for uv settings my gnex? I want to reach noon with a charge...

Inviato in Technicolor©
[Samsung Galaxy Nexus] franciscofranco:
Hmm now thats weird... I will have a look later today, I am in a semi vacation mode at the moment.
[Samsung Galaxy Nexus] TEK112:
All UV settings are different. Some that work great for others may cause your device to crash and not boot. How about sticking with this kernel for a couple of days and then start undervolting by 50 until you feel comfortable no instability is present.

DO NOT SET ON BOOT UNTIL YOU ARE SURE THE SETTINGS ARE STABLE!

---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------

Under developer options specify where your dead zones are. I have not noticed anything myself, but it is worth trending. Also, what ROMs are you both on?
[Samsung Galaxy Nexus] EvoRocker:
Nfc working for everyone using this kernel? I'm on 220 having issues, but not sure if it's kernel or what.
[Samsung Galaxy Nexus] JarGnex:
Hmm I've been texting and no problems here running 512 GPU version. I'll try 384gpu version.

Edit: I'm on MinCo ver1
[Samsung Galaxy Nexus] franciscofranco:
Yes it helps knowing which roms are you guys using.
[Samsung Galaxy Nexus] zackpack:
I bought the official extended battery but i'm not so satisfied..

So,do you suggest to undervolt by 50 every field? IVA or CORE? Smartreflex enabled? ty

ok I won't.
[Samsung Galaxy Nexus] TEK112:
I would not undervolt with smartreflex. Undervolt only MPU, all slots. However, I don't personally believe all of the hype in undervolting. It is already undervolted a bit and with smartreflex, even more. Those extra mv people try to squueze out of it don't seem worth it with all of the headaches it causes.

The number one culprit of bad battery life is signal. Even above screen brightness, if your signal is iffy or constantly flips between 3G and 4G, your battery life will suck out loud.

I do the following:

Autobrightness

Max - 1228

Min - 384

Governor - On Demand for testing (per Franco), but I usually used Interactive

CDMA mode, unless I have something large to get, then flip to 4G.

These simple steps with francos awesome kernel have netted be 3 times the battery life I got in the beginning.

Also, make sure your device is deep sleeping (CPUSpy - free from market).
[Samsung Galaxy Nexus] zackpack:
During work the signal is not so good. In my it's ok,but when I move in other areas of the company I have problems (even roaming). 2 signal bars active,maximum 3. At midday usually I have 94% (5h of data active-3G)

what is CDMA mode? we don't have 4g in Italy :silly:

test already done,deep sleep is ok.
[Samsung Galaxy Nexus] loudaccord:
I'm on Jelly Belly v3.8 ASOP Rom... I have the Verizon CDMA Nexus.
[Samsung Galaxy Nexus] derPianist:
I am on Paranoid Android 1.9.1

With r223 everything was fine. Will take a look at it and try to Screenshot it.

via Google Galaxy Nexus
[Samsung Galaxy Nexus] iferlive:
Guys I have resist myself to post something but this time I really need help, I'm runnin MIUI 2.7.20 and used to have franco kernel milestone4 and decided to try the JB version for ICS (r200), after flashing it I started to play whit the rom and seeing the performance, then I rebooted the phone and it got stuck ok bootanimation, after a while my pc detect it in adb so I have access to recovery and other stuff, I have tried reflashing milestone4, cleaning cache, dalvik cache but seems that it wont boot, Do you have any idea of how can I fix it without reflashing the whole rom? this is because I have already tried that but once i restore data from a backup it gets stuck again in bootanimation.

Thanks in advance and sorry if I postef it in the wrong section
[Samsung Galaxy Nexus] sleepsus:
I purchased the franco.Kernel Updater for my GNex on rooted Stock JB 4.1.1, I tried to use it to download and auto flash the latest franco Kernel but it is just stuck at 100%

"Downloading and flashing franco.Kernel-nightly-r225"

What am I doing wrong? :confused:
[Samsung Galaxy Nexus] TEK112:
Sorry about that. I have no knowledge of how overseas cellular networks work. Do you have a hand off between networks. If you goto settings-more-mobile networks-network mode, what do you see?
[Samsung Galaxy Nexus] JarGnex:
Just wait for it to finish downloading after a min or so your device will restart with francos kernel.
[Samsung Galaxy Nexus] TEK112:
Nothing, start with a cache wipe. If that doesn't work, clear app data (you will lose all settings for the app) and try again. Or, you could always download and flash it yourself.
[Samsung Galaxy Nexus] zackpack:
There isn't network mode option... The only similar option is "use only 2g" but this means "roaming" for me because I'm with H3G (uses only 3g network)

Inviato in Technicolor©
[Samsung Galaxy Nexus] Paragon_X:
r225 running on jelly belly awesomebeats... running great like every other kernel, honestly don't know how it just stays so good but i'm not complaining
[Samsung Galaxy Nexus] TEK112:
Sorry then. It looks like your constant poor signal is killing your battery. Perhaps you can purchase a network extender?
[Samsung Galaxy Nexus] hexinn:
Try to check ur superuser or supersu. may help.
[Samsung Galaxy Nexus] zackpack:
I don't know what it is at all, sorry..

Inviato in Technicolor©
[Samsung Galaxy Nexus] crixley:
Just reflash the kernel that was working originally

edited: sorry I missed the part where you already tried that
[Samsung Galaxy Nexus] thuynh022:
Lots of lag for me on 225/on-demand. Was going through my battery a lot faster too.
[Samsung Galaxy Nexus] garu12:
I'm lagging pretty hard too on ondemand. Running Jellybro
[Samsung Galaxy Nexus] TyroneLT:
I've had next to no lag on r225-512gpu. I've been using ondemand since r217 and its been generally good for me and gotten better with each nightly update. Battery life has been fairly good as well, averaging just over 4 hours screen time.

Today I've been testing usage with the OC up to 1.5 gHz and it's held up pretty good so far nearly no lag. Got 70% of my battery left with just over an hour of screen time used.
[Samsung Galaxy Nexus] Coffeebeans:
Ondemand is a bit laggier for me as well on stock JB 4.1.1, r225-384, battery life seems to be similar.
[Samsung Galaxy Nexus] nic85:
jb kernel have smartflex active?

some1 can tell me the voltages that franco choose for this kernel?

384gpu verion.
[Samsung Galaxy Nexus] The Gingerbread Man:
Perhaps try changing your radio if your running jellybean and your bootloader, I think these will help if you havent updated since ICS

Yes smart reflex is working fine, tbh I am finding it works just fine. If you don't know about undervolting yet then really I suggest leave your phone to it until you think you know what's best.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dascjb:
Any chance of adding lower cpu freq slots? Like 180 or 220 to try to get better battery
[Samsung Galaxy Nexus] Razer(x):
I'm experiencing much better battery while in standby with latest kernel on CM10
[Samsung Galaxy Nexus] dandyqb:
r223 is better than r225 when it comes to battery life even on interactive governor, i lost 3% overnight on idle, whereas r223 managed to lost only 1% for 8 hours overnight on idle. :)
[Samsung Galaxy Nexus] motorator:
Similar battery savings when phone is idle.

Used to drop about 15% overnight on R220, but seems to have gone down to about 5% with R225 + Bigxie V2. :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] derPianist:
Can anyone confirm that?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] garu12:
I found 223 better as well. Cant judge battery but performance for sure. Also settings stopped sticking again on 225. Reverts back to 1200 on screen off. Jellybro Cm10
[Samsung Galaxy Nexus] barrist:
225 on interactive feels the same as 223 as far as i can tell.

settings stick on reboot as well for me
[Samsung Galaxy Nexus] sway40:
Settings stick for me, and performance is the same.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sway40:
No that guy is retarded, the kernel is way to new to judge battery, especially last night when it just came out. You gotta give a new kernel a few days of charges to judge battery.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] saadi03:
I was wondering what your setup was to get 3% drain only in 8h mind sharing?
[Samsung Galaxy Nexus] dandyqb:
2g, no wifi, 1.3ghz384 smartreflex on
[Samsung Galaxy Nexus] saadi03:
oh makes sense thats not to surprising. thanks for the help
[Samsung Galaxy Nexus] GeekMcLeod:
How much damage to my battery health would having the battery life extender at 100 do? I don't like how it doesn't reach 100 and that seems to be the only way besides shutting it off for a bit every time to get to 100 which is annoying.
[Samsung Galaxy Nexus] franciscofranco:
Your battery will be just fine, don't worry.
[Samsung Galaxy Nexus] IAmAN00bie:
You know, I always see people saying this, but I wonder why this is/what proof you have for this claim.
[Samsung Galaxy Nexus] mariachi202:
The battery stats. Think of it as installing new brake discs in your car. They're new to the rest of the vehicle's mechanics, so a period of adaptation must be considered.
[Samsung Galaxy Nexus] EvoRocker:
PGM Nexus work with 223 or 225?
[Samsung Galaxy Nexus] JarGnex:
Yes
[Samsung Galaxy Nexus] derPianist:
Both

via Google Galaxy Nexus
[Samsung Galaxy Nexus] AzzaD:
I'm back on 223 - there was some lag in 225 that didn't change no matter what settings I changed, not sure what it was from
[Samsung Galaxy Nexus] 15israellai:
Lol that's almost like airplane mode.

Blazing on my Nexus Prime
[Samsung Galaxy Nexus] dandyqb:
i dont need wifi during sleep,haha...
[Samsung Galaxy Nexus] Rikusaki:
I also went back to 223.

I felt that On Demand was a step backwards. Didn't Google talk about CPU scaling during Google IO and how governors like On Demand caused lagginess? :confused:

I dunno. It just didn't feel as smooth. Keep up the great work, though. I am loving this kernel. :3
[Samsung Galaxy Nexus] RcrdBrt:
Interactive is a more aggressive ondemand

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Rikusaki:
I see. So was that what Google was talking about at Google IO?

Here's a link to the moment where he talks about CPU scaling. http://www.youtube.com/watch?v=VuC0i4xTyrI#t=07m28s
[Samsung Galaxy Nexus] laureanop:
Probably the worst analogy I've read in a long time! Does that mean that until they adapt to the vehicles mechanics you have to brake your car like Freddie Flintstone? :D

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] dandyqb:
:laugh::laugh:
[Samsung Galaxy Nexus] budakmaran:
hi im on JB 4.1.1??

which one should i use??

"Milestone 4" or "Jelly Bean kernel for 4.1/4.1.1 only" ?
[Samsung Galaxy Nexus] nic85:
I know how to undervolt i did it many times...225 have a bit battery drain in idle

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] :
Milestone 4 is an ics kernel. 4.1.1--is JB

CM10 Skank/Trinity Alpha 35-1344-384
[Samsung Galaxy Nexus] dandyqb:
milestone 4 is for ICS, so take the Jelly Bean kernel :good:
[Samsung Galaxy Nexus] budakmaran:
Thanks..
[Samsung Galaxy Nexus] tixed:
Bump. It persists on 225. Using stock frequencies, no undervolt, ondemand, fsync on.

And confirmed that downloading from any other app triggers the same problem. Only with video files, though. Maybe the problem is with video codecs?
[Samsung Galaxy Nexus] budakmaran:
one more question..

what is differences between 512GPU and 384GPU??

thanks
[Samsung Galaxy Nexus] danielvc:
It has a ramped up GPU. For some people this improves graphics, for some not (get glitches/artifacs). It also eats more battery, although I don't really notice the difference with JB.
[Samsung Galaxy Nexus] dandyqb:
obviously it is the 2 speeds of our GPU, 512 is a lil bit faster than 384. :cowboy:

assuming your gnex can handle the higher clock speed,...
[Samsung Galaxy Nexus] kompressorgpl:
Now that is what I call a good answer!!!! Thank´s!
[Samsung Galaxy Nexus] The Gingerbread Man:
A little feed back from 225, on demand does indeed seem to help improve battery and not really facing any of the micro lags. Don't really know what else to say other than great job as usual

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] andrew53517:
Is anyone else's settings not sticking in the app? ... Not just on reboot but in addition to exiting it too.

Color control, cpu, min screen off cpu, etc keep changing.
[Samsung Galaxy Nexus] The Gingerbread Man:
Just supersu instead of super user. Failing that clear Francos app data, uninstall, reinstall and set it back up and should be OK. Unless your using cm 9 / 10 and you can blame them if you are

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] andrew53517:
See, it's odd because I am using superuser too. I'll try the app wipe I guess.. Oh how fun haha. Thanks.
[Samsung Galaxy Nexus] Puzzlegirl:
Yes, I agree. Can't understand what people are on about, saying they need to go back to 223! Give it a chance. Idle speed is definitely improved on 225 ondemand as well.
[Samsung Galaxy Nexus] mohdameer:
strange problem. cannot use usb debugging. have to restart the phone while keeping it connected to the pc. otherwise it does not work. any ideas?
[Samsung Galaxy Nexus] TyroneLT:
+1
[Samsung Galaxy Nexus] dmbfan36_23:
I too would like to see a 220-250 slot...
[Samsung Galaxy Nexus] Michealtbh:
Turn off USB fast charge
[Samsung Galaxy Nexus] mohdameer:
did that, still didnt work, but do i need to restart?
[Samsung Galaxy Nexus] daggerxXxsin:
After disabling fast charge, unplug and replug the usb cable.
[Samsung Galaxy Nexus] dmbfan36_23:
It seems like 225 keeps turning off CPU core 1, even without any power modes set... The only way to get it back is to flash the kernel again... Anyone else see this?

384GPU, 384 min / 1228 max, 729 max screen off, ondemand

EDIT: using AOKP JB preview 4

EDIT 2: ok, a reboot brought it back this time, don't understand why it shut off though, I tried playing a game and watching some full screen YouTube videos to increase load thinking the kernel would turn it back on for more power and it didn't....
[Samsung Galaxy Nexus] sway40:
All good here, no problems at all with this kernel.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mohdameer:
thanks man. it works.
[Samsung Galaxy Nexus] kashix:
The USB fast charge thingy is like a historical lesson for all of us, every now and then something will pop up about it. Anyway, seems to be a lot of debates over the governor, so which is better? Interactive? Ondemand?
[Samsung Galaxy Nexus] franciscofranco:
I don't even answer those posts anymore.

They are different. Interactive is much more aggressive performance and battery wise while Ondemand is more balanced.
[Samsung Galaxy Nexus] kashix:
Hahaha, can't believe the magnitude of frustration you face when you see them repetitively and I'm glad you're still answering mine :) thanks Franco! Looking forward to more of your good work being implemented in future!
[Samsung Galaxy Nexus] asicman:
Possible earpiece volume bug in JB r225. After unplugging my headphones to make a phone call, the volume on the earpiece was very low. Tried to make another call 2-3 mins later and the volume is back to normal. I'm on bigxie 4.1.1.
[Samsung Galaxy Nexus] franciscofranco:
Thats a known bug on Sound Control interface. I tried to fix it but I wasn't very successful - I also bugged Ezekeel to fix it, but I think he's busy with something else.
[Samsung Galaxy Nexus] s_o_r_e_n:
Just leave the option in "increase maximum sound volumie" at 0 and it will help:)

Wysyłane z mojego Galaxy Nexus za pomocą Tapatalk 2
[Samsung Galaxy Nexus] creeve4:
I'm running r225-JB and have purchased your Kernel Updater app. I changed the governor to wheatley, but after each reboot it switches back to ondemend. I have checked Set CPU settings on boot.

Running JRO03C stock firmware (rooted of course).
[Samsung Galaxy Nexus] asicman:
Is the short term solution simply to retry the call or is there another way (I want to make use of the volume boost @ 3)?

Thanks, but I want to make use of the additional gain that sound control provides. Bizarre as it may sound, I like customer kernels not because of the awesome OC/UV features, but rather for sound and color! OC/UV is an added bonus for me.
[Samsung Galaxy Nexus] kashix:
are you using superuser? use superSU instead
[Samsung Galaxy Nexus] Degrated Shadow:
question

hey bro.. u got my phone flying smoothly...:p

I have a question though.. as u see our phone gets 695 user available ram.. bt devices like galaxy note n7000, galaxy s 2 i9100 hav got about 800 mb user available ram.. how's that? i mean our kernels are lighter than galaxy note's. arent they?
[Samsung Galaxy Nexus] jazzaddict:
I'm getting audio stutter on poweramp when turning screen off or while I'm multi-tasking. What could be the cause of this issue? I have already set audio buffer to max.
[Samsung Galaxy Nexus] Degrated Shadow:
i suppose power amp has some problems with custom kernels or roms.. i experienced same issue on my galaxy s bt not on this device... meanwhile try playerpro

maybe change the screen off max frequency to 729mhz and keep it as it is.. i havn ried though cuz i switched to playerpro.. thats has some problems too bt not as bad power amp
[Samsung Galaxy Nexus] GeekMcLeod:
If you have the max sound boost in his app set to 3 that could be causing it. I noticed problems occur with sound when that option is 3. 2 works great though!
[Samsung Galaxy Nexus] LNJ:
Yeah my I9100 had 835mb available.

Trinity has less available memory compared to Franco by about 15mb or so.

Maybe more can be freed up from video allocation?
[Samsung Galaxy Nexus] mrcool007:
Hmm. I'm also experiencing wifi drop.. never happened before

I don't know if it is rom related (AOKP b13 ) or ... not. I'm using the latest radio XXKK6.
[Samsung Galaxy Nexus] Redflea:
Are we maybe seeing a pattern here around AOKP?
[Samsung Galaxy Nexus] franciscofranco:
This is what I changed network wise in the ramdisk

write /proc/sys/net/ipv4/tcp_timestamps 0

write /proc/sys/net/ipv4/tcp_tw_reuse 1

write /proc/sys/net/ipv4/tcp_sack 1

write /proc/sys/net/ipv4/tcp_tw_recycle 1

write /proc/sys/net/ipv4/tcp_window_scaling 1

write /proc/sys/net/ipv4/tcp_keepalive_probe 5

write /proc/sys/net/ipv4/tcp_keepalive_intvl 30

write /proc/sys/net/ipv4/tcp_fin_timeout 30

write /proc/sys/net/core/wmem_max 404480

write /proc/sys/net/core/rmem_max 404480

write /proc/sys/net/core/rmem_default 256960

write /proc/sys/net/core/wmem_def 256960

write /proc/sys/net/ipv4/tcp_wmem 4096,16384,404480

write /proc/sys/net/ipv4/tcp_rmem 4096,16384,404480

Play with the values and see if it fixes anything, I don't have time to double check everything.
[Samsung Galaxy Nexus] ChongoDroid:
9.1 fixed the wake lag for me. Will report after some battery tests.

So far performance feels great!

Sent from my Google phone
[Samsung Galaxy Nexus] jan-willem3:
https://github.com/drod2169/KangBang-OMAP/commit/7a8e16a85a3ff1d0ce687584211b30649dbe1c51

Maybe something useful for you guys. I actually do not own a galaxy nexus yet but I am gonna order one in the next few days.:D
[Samsung Galaxy Nexus] Vangelis13:
+ 1 & same set up. Not necessarily a drop but it turned grey (all syncs on however)

I just however flashed 9.1 and it seems to be gone? #clueless
[Samsung Galaxy Nexus] Grims:
It does... after awhile but it seems doing anything pegs at back up to 1350 for an undetermined amount of time
[Samsung Galaxy Nexus] chikimonke:
Not sure if this is meant for me, but I honestly wouldn't even know where to begin or what any of the numbers mean. But seeing that other folks on AOKP are having the issue, maybe it's ROM related.
[Samsung Galaxy Nexus] Dr_Ownage:
Not that i actually use the internet a whole heap on my phone but i havent experienced any data drops or anything...

Everything is working great for me and im running the latest franco + latest AOKP
[Samsung Galaxy Nexus] chikimonke:
It's not a full on data drop, just a google server drop. The icons still stay gray and I can browse the internet, but anything that syncs with google is SOL until the connection comes back. Sometimes I have to force it by going into and out of airplane mode to get it to reconnect. I also imagine that you are using the GSM version and not the LTE/CDMA version of the phone. Not sure if that would affect things, but it is something that's different.
[Samsung Galaxy Nexus] Dr_Ownage:
well maybe i am experiencing this issue. i noticed twice on my phone when i went to send a text that my reception was grey (not in sync) however i put it down to the ****ty reception in my office....
[Samsung Galaxy Nexus] chikimonke:
I thought it was a reception issue as well, but I'm on my wireless network sitting 3 feet from my router, so reception really shouldn't be an issue. I just don't know enough about this stuff to fix it myself.
[Samsung Galaxy Nexus] Dr_Ownage:
hmmm i might leave mine for the day as i told myself i would. actually wanna test the battery....

problem is when your in front of a computer all day reading forums all you wanna do is flash and change stuff :P