yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DroidOnRoids:
I know the Galaxy Nexus is known for its poor battery performance, but I am scratching my head as to why after 2 days on this kernel I can't get more than 90 minutes on screen time with BeastlyBattery Power mode enabled. I have to charge 3 to 4 times a day.

I'll give a little background though. I purchased the Toro on Swappa from a guy who used it for a year, so my guess is I need to purchase a new 1750 mah battery to fix the atrocious battery life? I think the phone likes Franco's kernel, I just don't think I'm getting what I should out of it.
[Samsung Galaxy Nexus] kuyam:
Monitor your phone with the app 'wakelock detector' to start with. Also if you have bad reception it will hurt your battery, so a different radio can help too

I believe there is a thread about the battery in the gnex general forum.
[Samsung Galaxy Nexus] Edward Stanbury:
Ahh yes our phones are purring like a kitty with these new voltages ! amazing performance, low heat and great battery. Couldn't ask for much more :P but i really hope we can sort out the higher IVA frequencies
[Samsung Galaxy Nexus] The Gingerbread Man:
So far I haven't had a great deal of time to properly test any undervolt to the limit. I have a border line voltage at one frequency either 1.0 or 1.2 GHz I go -100 across all freqs. -75 has been stable for 10 hours
[Samsung Galaxy Nexus] KostasR:
Lagfix isn't working. Is this a kernel issue?

Sent with my thumbs using Tapatalk 2
[Samsung Galaxy Nexus] The Gingerbread Man:
That is because there is no lag to fix ;)
[Samsung Galaxy Nexus] büscher:
Try to clear data of lagfix (not just cache) and reboot.
[Samsung Galaxy Nexus] KostasR:
That was my first guess. :silly: But the seq write speeds have decreased to 6MB/s :p

Already done that. Didn't work :cowboy:

Edit: Second time was a charm I guess :P Did it again and seems to be working now :)
[Samsung Galaxy Nexus] Edward Stanbury:
you are lucky :P i can only do -100mv or more on all frequencies below 1.2ghz and can just push maybe 80mv for 1.2+ if im lucky
[Samsung Galaxy Nexus] cmstlist:
I'm having a 100% reproducible issue:

Immediately after booting/rebooting the phone, if I allow the screen to sleep, within one minute it reboots to the Google logo and starts all over again. However if I wake the screen and keep it awake long enough for the Franco app to kick in and apply colour settings, there is no reboot after it sleeps.

Last_kmsg link: https://dl.dropboxusercontent.com/u/11887975/last_kmsg6

Final lines:

So it doesn't seem to be a kernel panic - but - the last thing it does before the random reboot is always setting the colour controls. And if it's awake for that, no reboot happens. Any thoughts?

Running stock 4.2.2 yakju with latest nightly.
[Samsung Galaxy Nexus] The Gingerbread Man:
I think you have the rare bug when you have to leave content adaptive brightness enabled, try that.
[Samsung Galaxy Nexus] cmstlist:
Hmm and why is the bug rare? Are most people at large not experiencing the same bug with CAB?

I disabled CAB because at my current colour settings in low light, it gives web pages severe banding that looks awful.

Trying it now - removed the disable CAB checkbox and rebooted. Allowed screen to sleep and waited 60 secs. And the result is... yep, no hang, no reboot.

Damn, well I hope it gets fixed soon.
[Samsung Galaxy Nexus] The Gingerbread Man:
I think it only applies to certain screen types I think i read there's about 6 different ones each with their own different levels of colour temperature and hue. I guess one of them doesn't like CAB and the but is rare as it works fine for most people, it a lottery of luck which screen you get.
[Samsung Galaxy Nexus] osm0sis:
Try setting it via init.d; that was recently suggested as a workaround. :)
[Samsung Galaxy Nexus] RNZart:
wandered around to find out how to do this init.d thing... works like a charm, CAB disabled with no double reboots!! thanks mate.. :thumbup:

"I see..I read..I don't get it..I flash anyway!!" ~ Maguro Daily
[Samsung Galaxy Nexus] gummie:
Since I have added the new 4 Tweaks for BFQ I haven't used other I/O since then. I really like the Deadline before but now I am a sucker for BFQ. Didn't know just by 4 lines tweaked it could make the difference what if BFQ has been fully tweaked.
[Samsung Galaxy Nexus] bunnahabhain:
can u share the values?
[Samsung Galaxy Nexus] Ci@cKi:
I've just applied the same values for test, let's see how it works!

http://xdaforums.com/showthread.php?p=42686461&highlight=bfq+tweak#post42686461
[Samsung Galaxy Nexus] The Gingerbread Man:
Either something isn't right here or my phone is a ****ing trooper. Undervolting 1036mhz at 825 just should not be possible? Main & Max speed set to 1036, disabled mpu smart reflex, set voltage at 825 and begin stability test, been running for over 15 mins and no crash! Previously I crashed 1228mhz at 1100 then raised 1125 so I know it works but this is mental!

Edit

It crashed when I changed the min CPU speed back down to 192. Back to testing from 1000

Edit 2

Yup 1025 is the closest -25 I can get to without instant freezing
[Samsung Galaxy Nexus] AndyGnex:
Exactly how i felt. Before this all i ever used was the tweaked cfq.. Now, it would take something really spectacular to convince me away from bfq
[Samsung Galaxy Nexus] Edward Stanbury:
thats some pretty sweet results bro ! dont you just love undervolting :D i might revisit my voltages again and see if i can get any lower !
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah its not too bad haha So far my results are (will edit this as I go along)

Speed Orig Tuned Saved

1228 1225 1125 100

1036 1150 1050 100

729 1050 925 125

537 900 850 50

384 850 750 100

192 800 725 75
[Samsung Galaxy Nexus] osm0sis:
Just so you know, Stability test app doesn't really seem to do anything for voltage testing as far as I can tell.. I had known borderline voltages and it didn't trip them, but 15 min normal usage and Stock browser did.

Looks like your voltages are coming out close to mine and pkgnex's. :) 729MHz@900mV was borderline for me, had to bump it to 925.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yup stability test isn't the greatest of things to test with and results differ in real world cases but it was the only app I could think of at the time to maintain 100% load on CPU. When I get my chart more complete I'll test for a few days before hitting the dredded set on boot. I'm quite pleased with my results so far. Also I think system monitor by Chris Göllner is wrong, it reads 537 as 538 :p
[Samsung Galaxy Nexus] Edward Stanbury:
and im super lucky with 729@875mV :P haha but thats its absolute lowest with stability

Edit: oh jokes looks like my device lied to me ;)

1228mhz: 1125 mV

1036mhz: 1005 mV

729mhz: 865 mV

537mhz: 800 mV

384mhz: 730 mV

192mhz: 700 mV

but i dont think they will hold under real stress :\
[Samsung Galaxy Nexus] pkgnex:
Yeah, BFQ still works, and tests, really well for me, too.

I ran some benchmark testing yesterday on all the schedulers out of curiosity, and in certain tests it came out on top both for maximum average throughput, minimum latency, and lowest overall variability, which was impressive. All of the schedulers can be good for certain uses, but BFQ is definitely a good overall daily driver with the "quick tweaks".

And the "quick tweaks" really weren't that quick - it took me a solid day or two of testing and some minor statistical analysis. BUT, the data was just on my device (Tuna/Toro, not Grouper) with very little input from the other Dev Team members other than a final confirmation check that it seemed to run well for them, too. I really don't think a "full tuning effort" could squeeze much more out of BFQ, and there are so many variables that coordinating a full tuning like we did on CFQ and Deadline would probably take the rest of our lives.

I'd still love it if Franco could find a way to get v6 to be stable, but I don't think that is a priority on his radar anytime soon!
[Samsung Galaxy Nexus] Midomad:
I have added the bfq tweaks with fku but after reboot it's back to default!

I have Set on boot ticked!

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] Efrenjr15:
as far as the BFQ tweaks, what are yalls Interactive tweaks or set up? (screen shots maybe :p ) and if not interactive what is another good govener to go with BFQ?
[Samsung Galaxy Nexus] osm0sis:
Did you try the usual yet? Clear f.Ku app data+cache? Disable/remove init.d? Or you could flash my Emergency Reset Zip and let it do all that for you.
[Samsung Galaxy Nexus] pkgnex:
Interactive using default kernel governor parameters should run great. No special governor tweaks are required due to changing the i/o scheduler to BFQ.
[Samsung Galaxy Nexus] Efrenjr15:
might call me crazy but i set max cpu to 1.5 and hig freq on Interactive to 1.5 as well.

not really going for battery here since its going to drain regardless and my job and commute to home sucks when it comes to signal so regardless i get raped on battery even underclocked or even stock settings.

even at 1.5 i get really good battery life at home both on wifi and 4g.

Franco FTW!
[Samsung Galaxy Nexus] büscher:
This is what I do. I want a phone that is fast. I have so many opportinities to plug in my phone during the day if i need to. But even if I dont, my battery lasts the whole day almost every day...
[Samsung Galaxy Nexus] whitedragonz83:
I found hi speed freq of 1GHz with top freq of 1.5 is very smooth too, when I am not as worried about battery. Really, the hi speed freq of 1GHz might be most of it for my overall interactions with the phone.
[Samsung Galaxy Nexus] Jerreth:
BFQ tweeks reverting

I have flashed the franco reset tool and then added the tweeks in franco app for bfq and set them on boot however they don't seem to stick. I found some lines to add to the 950iosettings but that seems to not be working as well any ideas?
[Samsung Galaxy Nexus] njiki11:
Maybe I'm confused, but everyone's talking about these new bfq values. But what are they...?
[Samsung Galaxy Nexus] Jerreth:
BFQ - will work with v5 (current franco) and v6 (some other kernels):

back_seek_penalty=1

slice_idle=0 (really, really, important)

raising_max_time=0 BFQ will then auto-tune this value higher and smooth out)

raising_max_softrt_rate=2000 (most report improvement, if you have issues, revert this to 7000 and post in franco.kernel thread)

from a post a few pages back
[Samsung Galaxy Nexus] bigknowz:
BFQ

# bfq tweaks

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty

echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle

echo 0 > /sys/block/mmcblk0/queue/iosched/raising_max_time

echo 2000 > /sys/block/mmcblk0/queue/iosched/raising_max_softrt_rate

# raising_max_softrt_rate is 7000 default, in case there are issues
[Samsung Galaxy Nexus] Midomad:
I just copied the tweaks to iosettings and set permissions and stil Not working!!

EDIT: you need to add this line:

elif [ $scheduler == "bfq" ]; then

EDIT2:raising_max_time always back to defaut 256!

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] gummie:
Thats exactly how it works ong BFQ. It populates its values for a certain time rate. You set it to zero and let it automatically set values over time.
[Samsung Galaxy Nexus] alfiemenace:
Why can't I trim my data and cache using Lagfix when using franco.kernel, it says not supported :(
[Samsung Galaxy Nexus] blackode:
Does anyone else notice lag when typing and opening/closing apps?
[Samsung Galaxy Nexus] Edward Stanbury:
nope sorry, its all silky smooth here ! :P
[Samsung Galaxy Nexus] Efrenjr15:
Just curious what kernel are y'all on?
[Samsung Galaxy Nexus] Ci@cKi:
Funny, to me happens that i can trim data and cache but not system (not supported) on latest PA... Someone else?
[Samsung Galaxy Nexus] DonXoB:
Try reset app data of lagfix

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] bluerez79:
Worked for me
[Samsung Galaxy Nexus] psyren:
Tried out the BFQ tweaks, and I think it killed my phone. Had to restore an image to get it working again. It had a BSoD, then wouldn't boot.
[Samsung Galaxy Nexus] Ci@cKi:
Yesterday i've tried to clean app's data and nothing happened, but today worked! Another proof that computer science is not a deterministic science! :D
[Samsung Galaxy Nexus] Khrushy:
/glances at thread name.

Probably the Franco kernel.

Also, totally loving 382 with the current(ish) memory-leak-less build of AOKP. I just hit a casual 270 hours of uptime without even thinking about it - my phone just hasn't done anything recently to suggest it needs a reboot. Insane!
[Samsung Galaxy Nexus] Efrenjr15:
Lol!!!!!!! I ment ROM ooops
[Samsung Galaxy Nexus] pkgnex:
That's really weird.

If you still have the stomach for it, you could try all the tweaks EXCEPT raising_max_softrt_rate=2000 (leave it at the default 7000).

If you do this, please report how it works.

Also, just to make sure... you're on Franco's r382 kernel, correct?
[Samsung Galaxy Nexus] psyren:
Black screen, not blue screen.

Yes, I was, running the latest AK47 ROM.

Will do a reflash back to it (my restore took me back to an old uXylon version) and test it again.

Any idea what might have caused it? I would get you a logcat, but logging had been disabled (via FKU) anyway, and I needed my phone working so I did a restore.

EDIT: just thought I should mention that I also tried the emergency kernel reset zip after my device wouldn't boot. Still no luck.
[Samsung Galaxy Nexus] psycho693:
Hey guys. I am running 4.1.2 because its faster and I just like it more. But could any of you tell me what r300 and lower kernel was best to use or the milestone even thanks!
[Samsung Galaxy Nexus] L-ViZ:
r300 is in my opinion the best kernel for 4.1.2. performed well+great batterylife. 3-4h screentime always possible with this kernel.
[Samsung Galaxy Nexus] mpokwsths:
I hear by many people that 4.1.2 was faster than 4.2.2.

These claims are simply ridiculous.

I went back to CM10 the other day to examine these allegations.

Well ... CM10 was slower and had worse memory management than 4.2.2 (stock CM10.1). More launcher and app redraws. Also, the transition animations were choppy and the general feel was soooo much worse than 4.2.2.

Now, if we take under consideration that the newer 4.2.2 roms are compiled with Linaro/Bionic optimizations using much more advanced Toolchains the gap is increased. There is a huge difference between a good linaro/Bionic rom and the best 4.1.2 rom. Huge.
[Samsung Galaxy Nexus] Seraz007:
+1

i dunno where they get this kinda stuff

4.2.2 and neva going back :rolleyes: :D
[Samsung Galaxy Nexus] The Gingerbread Man:
OK so here's how my under volt went, only applied to GPU and CPU. I only under volted CPU 192 MHz - 1.2 GHz as I don't over clock. Been 100% stable for 2/3 days now after a few tweaks to a couple of border line ones. These are just for reference, it won't work on everyone's phone.
[Samsung Galaxy Nexus] rofik_gitara:
agree..

if 4.1.2 more faster than 4.2.2

so for what google build 4.2.2?
[Samsung Galaxy Nexus] Rimher:
What kernel is the AK experimental with Vanir ramdisk that you have in your signature??
[Samsung Galaxy Nexus] psycho693:
Oh man .... That is in vanirs thread I will take a look and find it and let you know
[Samsung Galaxy Nexus] yoncy:
From what i remember 300 was the best option for 4.1.2. You can remain on that.
[Samsung Galaxy Nexus] psycho693:
Here is the download link from the thread I would only recommend this kernel if your running vanirs ROM.

https://www.dropbox.com/s/bvm37kumjju0j33/AK.EXP40.zip
[Samsung Galaxy Nexus] L-ViZ:
also went back to 4.1.2.

the system ui lag was in every rom with every kernel. made me sick. now back to 4.1.2 and i can tell u it's just a different feeling to 4.2.2.

4.1.2 offers u stability over time, 4.2.2 is noticable faster especially when opening apps. but after 2h running, i always had the system ui lag... now it's a bit slower (not the ui) but i got the same perfomance over time. but i hope to switch to android 4.3 soon :)
[Samsung Galaxy Nexus] bigknowz:
Timer Slack

Anyone look into [MENTION=4615478]boype[/MENTION]'s timer slack feature? If so, any thoughts?
[Samsung Galaxy Nexus] mpokwsths:
And Boype's tweaked RAM timings, which have obvious impact in performance and are stable at the same time.
[Samsung Galaxy Nexus] osm0sis:
Link? :)
[Samsung Galaxy Nexus] Gimic26:
http://xdaforums.com/showpost.php?p=42895372&postcount=2674
[Samsung Galaxy Nexus] boype:
Github links:

cgroups timer slack

not "my" work. Kirill A. Shutemov wrote it (worked for Nokia)

LPDDR RAM timing tweaks

Would be happy to contribute to others too, so go ahead and propose / pick :)
[Samsung Galaxy Nexus] osm0sis:
Nice! Thank you boype and the Fancy Kernel crowd for continuing to push and tweak the GN to perfection. It's impossible not to love all the great work you've been doing. :D

Hopefully [MENTION=3292224]franciscofranco[/MENTION] can see his way to including this!
[Samsung Galaxy Nexus] psycho693:
Exactly what I noticed I'm glad I wasn't the only one lol
[Samsung Galaxy Nexus] lightingcloud:
What internet browser do you guys use? Seems like Chrome Beta has problems with Deadline... And I tried Dolphin but it's terrible.
[Samsung Galaxy Nexus] sym_m:
Boat Browser

https://play.google.com/store/apps/details?id=com.boatbrowser.free&hl=en
[Samsung Galaxy Nexus] osm0sis:
Stock browser has always met all my needs. Lightning Browser, which I saw Francisco recommend awhile back, seems pretty nice and lightweight too.
[Samsung Galaxy Nexus] bunnahabhain:
NEXT Browser, there's no way out ;)

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] namtombout:
Thanks for sharing. Im sure it took many reboots and time. I personally had to raise all the mpu voltages by 50 except for 537. GPU voltages are stable for me.

I wonder, why you didn't play with the iva voltages? In the past I tried tinkering with the iva voltages but I noticed it borked my media playback. Same for you or do you have other reasons?

U.O.E.N.O
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah it took a **** ton of reboots and a fair bit of testing then real world usage to get it right. The GPU was quite fun to under volt seeing funny artifacts and also measuring fps with nemamark 2 to find the best one. Iva I didn't touch simply because we can't choose to isolate any frequency (setting min / Max) so I just let smart reflex take care of that one for me and as much as I love using my phone for music play back and stuff I don't use media functions as much as CPU and GPU so iva isn't so important compared to those.
[Samsung Galaxy Nexus] lightingcloud:
Thanks a lot, I think I'll go back to stock now and then will try something new when I'll have the time
[Samsung Galaxy Nexus] The Gingerbread Man:
Chrome beta all the way for me, love the speed of the beta and sync between PC tablet and phone
[Samsung Galaxy Nexus] lightingcloud:
My choice for that, but sometimes it just hangs my phone even for a minute or two. I read that it has a problem with swiftkey, too, but since I switched to deadline things got a lot worse.

Stock syncs favourites, though, so it's better than I thought (and almost everything I need).
[Samsung Galaxy Nexus] osm0sis:
SR is hardcoded disabled though, so those IVA voltages are what you get. You can definitely undervolt the lowest one with ease using the audio in Nenamark 2 to evaluate, it's just the other 3 we can't seem to jump to, let alone isolate.

But hey, if we can't get it to go any higher then the bottom is also where your savings may matter. :)

Edit: Just looked at Next Browser. Pretty cool video on the Play Store. Nice looking browser! :good:
[Samsung Galaxy Nexus] malaroth:
Damn but I miss y'all... there's plenty I'd like to do with the s4 but it's a whole new beast. Anyway here's a peek at my underclocked s4 at 387/1482 with -50 undervolt across the board. Funny. Higher mHz on here take the same or less voltage than the gnex
[Samsung Galaxy Nexus] osm0sis:
Hey! Good to see you again bro! We miss you around here! :)

Shame your GN bit the dust.. Don't suppose you've tried out the Dev Team scripts on the S4? ;)
[Samsung Galaxy Nexus] malaroth:
Lmao as if I could stop myself from it! Of course though I soft bricked my phone and just got it set back up today. Just put in the init.d scripts but modded your color script to my preferred settings
[Samsung Galaxy Nexus] osm0sis:
That's awesome! So cool that our stuff works on so many other devices. I've been sort of following the picked commits from Franco's github and it's all over the place now and we have you to thank for a large part of that. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Are you running the 4.3 gpe rom? Nice to see you again :)
[Samsung Galaxy Nexus] malaroth:
No I'm currently on beanstown106's jellybean beta 4 with ktoonsez Loki'd touchwiz 06/23 build. But the benchmarks I posted were running all the scripts all of y'all worked so hard to finalize and I wasn't even capped at stock CPU speed. This phone is a beast and I miss my gnex but getting over 4 hours screen on with stock battery...yeah I like.
[Samsung Galaxy Nexus] The Gingerbread Man:
Awsome! I'm a bit jealous of some of the nexus 4 users sot some achieving over 5 hours, I look forward a to the next nexus phone as I'll be upgrading to it. I'm surprised your not running the leak though, if I had an s4 I'd flash it to be a gpe one
[Samsung Galaxy Nexus] Manya3084:
I was giving it 1/2 hour before I passed judgment but 14.1 is working fine. no boot loops or freezing.
[Samsung Galaxy Nexus] maximum error:
So what's with the loss of signal? Flash this kernal n then I can't even send a txt. Switching aeroplane mode on then off fixed it but then locking and unlocking broke it again.
[Samsung Galaxy Nexus] Felixpau86:
Running bigxie 9.2... boot looped with 14... went back to 13.1, then flashed 14.1. So far so good no signal drops yet
[Samsung Galaxy Nexus] franciscofranco:
The kernel have nothing to do with signal.
[Samsung Galaxy Nexus] dwang:
could it be related to undervolting? with 14.0 when the screen is off, I lose my 3g mobile signal, once my screen is on, the signal comes back.

Flashing back to 13.1 and no issues.

14.1 doesn't have that problem either.
[Samsung Galaxy Nexus] franciscofranco:
Ahah thats awesome. I had to leave home for a second to lend my NS to a friend for a couple of days, I'll explain what I changed to make it work when I get back home, and it wasnt voltage stuff ;)
[Samsung Galaxy Nexus] Br0wNb0y:
It was working for about an hour and then all of a sudden it went into a bootloop. I'll go back to r13 for now.
[Samsung Galaxy Nexus] dwang:
whatever you fixed, you should probably tell morfic since his kernels have the same issue.
[Samsung Galaxy Nexus] jan-willem3:
Netfilter stuff can do a lot with singal I know this for sure because when I owned an hd2 we had some kernels who had way more bumpy singal or ones that switched more often to edge. Or on someroms you couldnt get a singal at all.

Ofcourse the radio didnt change.

For me personally the changes in v13 give me sometimes one bar where I normally got always 2 bars with v12. I saw a few other posts wich confirm this.
[Samsung Galaxy Nexus] rob151515:
Yep, I'm also getting unknown symbol trying to load the cifs module. :(
[Samsung Galaxy Nexus] LionAR10:
Thank you for this (and other stability related items) ... I'd rather use a little more battery than get reboots/sod/data off mysteriously.

You kernels have been good, app purchased while on 13.1 ..

Thanks again.
[Samsung Galaxy Nexus] rabhw:
Hey Franco,

I'm unable to test right now, would you be able to confirm whether this kernel supports the wireless ADB that was just added to bixie's apex rom?

According to his thread:

Thanks!
[Samsung Galaxy Nexus] taney:
anyone here running CM9 (codeworkx/fits)?