yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] terminal13:
20-30 percent doing what over how long?

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] bensl84:
I have like five apps. Work app go daddy email lux and gmaps and g+ greenify and trickster. I feel like that's high screen on drain.

I wiped and started over one app at a time. screen off. It sips. screen on it gulps. Just wondering if I need to set something up differently in trickster or something
[Samsung Galaxy Nexus] zandander:
That's part of it! The screen sucks in much more power than any other thing. The only close competitor to the screen as far as power consumption is voice calls.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bensl84:
Checking email and texts browsing. I'm sure it's user error. Just wondering if that's a lot for just a quick glance at gmaps and texts and email and some chrome browsing
[Samsung Galaxy Nexus] szucsgf:
I get around the same screen on drain, depending on what I'm doing. Clocked at 1350 max. I used lux as well, until recently. I'm curious, do you ask because you got less screen on drain on another kernel? Or just asking in general?

My standby drain is between 0.1-0.6% per hour, depending on the day. But I'm on maguro.
[Samsung Galaxy Nexus] bensl84:
To clarify I mean 20 to 30 percent an hour....
[Samsung Galaxy Nexus] terminal13:
Stock settings?

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] bensl84:
Yea stock. I'm not smart enough to tweak anything cent changing colors lol ill wipe again and check.
[Samsung Galaxy Nexus] Az Biker:
THAT'S why they're called TEASERS!!! :eek:

Atom/Carbon ROM + AK Diamond Series = Gyrannosaurus Nex!
[Samsung Galaxy Nexus] chikimonke:
I'm all for teasers, I just hate the waiting. :D
[Samsung Galaxy Nexus] terminal13:
Sure you are!;) a little good reading will help. Check the guides in the op, i did, and in about a half hour you'll have gone through basic little tweaks to get your battery under control. Besides, I've blown out the crazy screen on times I've seen. I'm just too heavy of a user. My suggestion is sit tight, wait for the next release. Let the kernel settle in, and enjoy. But while your waiting read up, these guys know how to word things to make it easy to understand. ;):cool::beer:

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] Kewyang:
Hi I wanna ask a simple question. I'm using 207 now and if i wish to flash back to my previous kernel(Air Kernel), I have to flash ak.restore.OLD.WIFI.zip first right? So, whenever we want to flash to any kernel from AK, we have to do this step?

Besides that, If we are from other kernel to AK, we just flash the latest version of AK. Am i right?

Thank you! :)
[Samsung Galaxy Nexus] szucsgf:
Going to ak kernel: just flash kernel

Going from ak kernel: you may need to flash old wifi drivers and/or flash the reset kernel and/or dirty flash your rom and gapps, depending on the specifics. You can just dirty flash the rom and gapps to be safe; I believe that will work in all scenarios.
[Samsung Galaxy Nexus] lesp4ul:
calm down friend, i am skirt guy....

eh..

i am straight :highfive: :angel: :D
[Samsung Galaxy Nexus] Kewyang:
Thank you very much.. I have just followed ur kernel settings, seems like u got great battery life. :good:
[Samsung Galaxy Nexus] aHecticLife:
Still using diamond 70 because of battery, I get like 3-4 hours, how's the new kernel? Should I switch?
[Samsung Galaxy Nexus] musashihatred:
yes. you should. every new update presents newer patches :) and you can help us well solve problems if there is.

and 207 is really good.
[Samsung Galaxy Nexus] happymonk:
New kernel is great. But not all phone behave the same. Do switch but if it doesn't play well, you can always revert back to your desire kernel.
[Samsung Galaxy Nexus] buggerthis:
Can you explain why this is the case, please? I was using min 180 and screen on min 350 till I saw a post of yours. I've changed my min screen on to 180 now because I'll take your word for it :) but I'd like to know why.
[Samsung Galaxy Nexus] adambala:
v207 is so so so smooth and battery friendly tx ak team!!!!!
[Samsung Galaxy Nexus] sk8oldschool74:
I'm calm!!! ;) And I was just answering your joke w/ a joke!! ;):):beer:

Jokers wild!!! :D:D:D

"sk8 or die"
[Samsung Galaxy Nexus] lesp4ul:
I know hahaha just don't want others make wrong assumption. :D
[Samsung Galaxy Nexus] sk8oldschool74:
This is my friend Mark!!! Now he is here to spam your thread AK lol!!! :p:p:p AK I love you bro!!! ;):):beer:

"sk8 or die"
[Samsung Galaxy Nexus] Rimher:
Actually after a few days of testing 207 I'm back to 70 as well, and it seems to work wonderfully!

Atm this is my sweet spot (with Az biker settings, already thanked his post ;) )
[Samsung Galaxy Nexus] paarthdesai:
using diamond 207

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] oubeichen:
i flashed CODEX rom today,and it's great with ak kernel!

but boot time is almost 2 minutes long,i don't know what's going wrong.......

clean flash.
[Samsung Galaxy Nexus] zandander:
I'm running codex as well. I've also noticed longer than usual boot times, but it's all worth it to me! And I would highly recommend a clean flash every time you install a rom, even if you're just updating your current one. That way if you have a bug from dirty flashing you're going to have to clean flash anyways. I play on the safer side of flashing!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shanp7780:
Boot time has always for whatever reason been lengthy with DT builds but they're worth it he builds killer roms.

agree always do clean flash only reason I dirty flashed he dropped 2 more one after another once got around to flashing see little glitch here and there but next release defiantly clean next go around.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Kewyang:
I'm using the same setting except power saving core 2& colour settings as szucsgf(http://xdaforums.com/showpost.php?p=40404414&postcount=25326). My battery has nt drained even 1% per hour during standby. I was full charge since 5 hours ago, and i took a nap about 2 hours, i made some calls in between.. My battery at 96% now...

XenonHd + Ak 207!
[Samsung Galaxy Nexus] Hetalk:
It is quite normal with AK kernels. Even the battery bows down to AK kernels.:D
[Samsung Galaxy Nexus] itasoulas:
@ Khizar

hey dude. You asked about my color settings a few posts back. Have messed with settings on trickster and I find the following setup to work really nice, at least for my screen. I also have "Content Adaptive Brightness" set to

OFF

.
[Samsung Galaxy Nexus] odavans:
looks awesome
[Samsung Galaxy Nexus] szucsgf:
I can't explain it but I can give some evidence.

1. Anarkia has said hotplug feature only works when min =min screen on.

http://xdaforums.com/showthread.php?p=40566069

Multicore power savings lowers the frequency of one cpu core when possible instead of turning off one cpu core, but maybe it's similar in terms of min screen = min screen on.

2. An experiment: set governor to interactive, multicore power savings to 2 and min =min screen on =180. Go to trickster's "info" tab. At the bottom you'll see "device status" which shows the frequency of each core. Just watch that for a little while. Every now and then you'll see one core go to 180 while the other is higher. That's multi core power savings.

Now keep min =180 and change min screen on to 230 or 350. Go back to "device status". You'll see the two cores always run at the same frequency.
[Samsung Galaxy Nexus] Kewyang:
Ermm. before the setting, my battery drain quite fast.. 1 sleeping night with wifi off, 7-8% gone.... anyway it is much better now :D
[Samsung Galaxy Nexus] ciprianruse88:
That isn't normal...you may have a rogoue app.When i installed first time 207 I got 3% battery drain from 8h of idle.Check for wakelocks

Sent from my Shining Nexus using AK DIAMOND ED.
[Samsung Galaxy Nexus] ak:
you are my best friend sk8 .... no problem.
[Samsung Galaxy Nexus] xxSAKISxx:
way of topic but i just open app store and i see the new one. is official out?

Send from my awesome-superb-f.... ng incredible Galaxy Nexus
[Samsung Galaxy Nexus] butikofer08:
I'm going to try without this setting enabled due to what I just noticed. Maybe someone can verify...with this option set to 2 my frequencies are always bouncing around and very rarely stay on the lowest frequency for long and never settle down.

However, when I switch it to off or zero my frequencies are bouncing around far less and it actually settles on my min. Freq for much longer periods. If this is true multi core power savings

would actually result in less battery, no?

I remember his comment but think it applied to the HP governors only. Multi core power saving doesn't actually disable/turn off a core like hot plugging does. I only say this because with my min screen on and min frequency different I still do see one occasionally stay at 180 while the other goes up. Sorry of this is wrong.... Just my thoughts....:beer:

Looking closer at your link in Stefano's comment he is referencing the HP governors only. Their hard to see but they are in black text at the top of his post.
[Samsung Galaxy Nexus] kaluoshi:
new rubik r24

hey bro please update op :D
[Samsung Galaxy Nexus] butikofer08:
So your wondering if the updated play store Google pushed to your phone is official?:what:

I'm confused
[Samsung Galaxy Nexus] xxSAKISxx:
well i. am not suppose to get a notification to update app store? o don't get nothing. just open app store and see the new one. that's all

Send from my awesome-superb-f.... ng incredible Galaxy Nexus
[Samsung Galaxy Nexus] Kewyang:
U mean even the default setting by Ak 207???
[Samsung Galaxy Nexus] manolone:
hello

I'm on 28 march paranoid android+ak 207 ..and PGM doesn't work for me!!

any ideas how to solve this?

thx

EDIT updated to PGM 1.16H and it works fine
[Samsung Galaxy Nexus] szucsgf:
Your first comment about frequencies bouncing about more when MCP is set above 0: Interesting, I never noticed that before. I tried it now and I saw the same thing as you.

Your second comment about hotplug governors: I used the wrong phrase. I said MCP turns off one CPU core, but that's incorrect. It seems to lower the frequency of one CPU core.

I understand that anarkia's comment applied to hotplug governors, but I mentioned it because I thought that behaviour applies also to the MCP feature. And it seems to, since unless min=min screen on the two cores always run at the same frequency.
[Samsung Galaxy Nexus] ak:
Multicore power save is a type of scheduler.

Group operation for try to use first core more than second.

That is.
[Samsung Galaxy Nexus] ablor:
Uninstall your pirate version of pgm and buy it
[Samsung Galaxy Nexus] lesp4ul:
Flash previous kernel that worked for you. Done!
[Samsung Galaxy Nexus] butikofer08:
Have you noticed how much these frequencies bounce around and don't settle when MCP is set at 2?:beer:
[Samsung Galaxy Nexus] jjhiza:
You'll never get an indication that the Play Store needs to be updated...it updates automatically.
[Samsung Galaxy Nexus] B@je:
This is true i noticed that the when the multi core saving are above 0 the frequencies bounce all over the place and i think that made the hotplug governors unstable and cause my phone to heat up and freeze like in 5 to 10 mins. I now have MCP set at zero and all is well:D

Don't force it get a bigger hammer
[Samsung Galaxy Nexus] buggerthis:
I tried this experiment- very briefly - like 2 minutes with min and min screen on the same and 2 minutes with them different and I noticed that even with min screen on set to a different freq one core does shoot up higher than the other, but it happens much less often than with them set to the same freq.
[Samsung Galaxy Nexus] ak:
http://xdaforums.com/showthread.php?p=40695187
[Samsung Galaxy Nexus] PatimusXPrime:
Hey guys out of curiosity why add governors or i/o schedulers such as userspace or vr that aren't really useful for our phones? By no means am i trying to be a ****, I'm really just curious
[Samsung Galaxy Nexus] terminal13:
user option/ much like women, each device has different silly needs:eek::silly:
[Samsung Galaxy Nexus] buggerthis:
I noticed this too. Freqs do bounce around an awful lot with mcps set to 2. To find out how much it affects battery life, someone would have to test both settings for a whole cycle each. I would, but I'm on holiday and I'm really not using my phone that much- my last cycle was 1 day 14 hrs with 1.5 of screen on
[Samsung Galaxy Nexus] PatimusXPrime:
Lol but userspace! :P yeah I suppose..
[Samsung Galaxy Nexus] B1nny:
Hmmm very interesting! Just changed it in my build.prop and did a reboot, let's see if I notice any difference. :)
[Samsung Galaxy Nexus] lesp4ul:
Rubik v6 is online everyone!!! :)
[Samsung Galaxy Nexus] ak:
At this point.

Why people use hotplug governors?
[Samsung Galaxy Nexus] Wh1t3Rose:
I'm actually doing this now. I have the same usage patterns every single day except Sundays. I'll post results tonight or early tomorrow morning. I already did a cycle with it set to 2. Now doing a cycle with it set to 0.

Toro | Xylon | AK SKL

---------- Post added at 10:50 AM ---------- Previous post was at 10:46 AM ----------

Off Topic:

I have the ultimate Anti-Theft security system combined with Avast, Tasker, and Foldersync setup. Its amazing. This weekend I think I'll post a how-to in the general section. I hope to get people interested.

Toro | Xylon | AK SKL
[Samsung Galaxy Nexus] PatimusXPrime:
I've found that with my device anyway, hotplug isn't worth it.. The extra lag and slowdown isn't worth the tiny battery boost.. Plus then it takes longer for the CPU to process one task and stays active longer.. Ill never know!
[Samsung Galaxy Nexus] Wh1t3Rose:
just use hyper with powersave bias. Best of both worlds :p

Toro | Xylon | AK SKL
[Samsung Galaxy Nexus] mono28aug:
Using 207 with jbsourcery... And trust me guys its so awesome... Performance plus battery life and m taking about ots...Coz stand by is not even an issue.... It has become my dd.... Thanks [MENTION=1106390]anarkia[/MENTION]
[Samsung Galaxy Nexus] sebby d:
Sorry if this has been mentioned. What is power save bias for hyper? Any suggestions? I have been using interactive for the longest time. Thanks.
[Samsung Galaxy Nexus] mono28aug:
Search this forum... Ur question have been discussed
[Samsung Galaxy Nexus] szucsgf:
"powersave_bias - Default value is 0. Setting a higher value will bias the governor towards lower frequency steps. Use this if you want CPU to spend less time on higher frequencies. A better alternative would be to underclock to a lower frequency than using powersave bias."

That's from here:

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] Droid-21:
I've noticed that this kernel is the culprit mobile warming.

Franco kernel and kernel STOCK not heated.

Temperatures rise when flaseha this kernel at 35 and 38 ° c.

Franco kernel, kernel lean and STOCK KERNEL, remains at 25, 28 and 30 ° c
[Samsung Galaxy Nexus] Sveke:
Its because AK is hot like fire.
[Samsung Galaxy Nexus] frenchy714:
Try a different AK version or Rubik, there's plenty to choose from, and I'm sure you'll find one that your phone likes. If not, just use a different kernel.
[Samsung Galaxy Nexus] njiki11:
Who has the best the battery settings because the last one I tried the battery life was horrible...
[Samsung Galaxy Nexus] Wh1t3Rose:
What version were you on? Go to Nephilim's Sig to see the best settings in my opinion fur this kernel

Toro | Xylon | AK SKL
[Samsung Galaxy Nexus] natsuke:
Just some insight from my experience.

I have test the mcp a while back then and I saw the the difference of freq between cpu is not that much. that is even before the min screen on is put into the setting.

however, by using perfmon or system monitor, i watched over the load of each cpu and i see the differences

For Mcp = 0; cpu0 and cpu 1 has almost the same load. if cpu0 is 50%, cpu1 will almost at the same load (40-50%). sometimes, cpu1 will has higher load, depends on which process finish first. This is due to no task grouping.

For mcp=1; cpu0 will almost always has higher load than cpu1. Let say the load of cpu0 is 80%, cpu1 load is just around 20%

long task is grouped and processed in cpu0, letting cpu1 to be less load. although the freqs are the same, but the load is different. power is used more on 1st cpu while 2nd cpu is let to half-idle.

For mcp=2; almost similar to mcp1. i couldn't see much different. but since it is for more power saving, i assume that it is more aggressive than mcp1

p/s: Sorry if everyone has known this. I'm not really reading xda much lately.
[Samsung Galaxy Nexus] irminsul:
At the Franco thread people are experimenting with tweaking the VM values in the build.prop ( https://code.google.com/p/android/issues/detail?id=40961)

The point is changing build.prop so that:

dalvik.vm.heapgrowthlimit=64m

dalvik.vm.heapsize=384m

In stead of 96/256.

I changed it on vanilla rasbean and the 4.2 'systemui' lags are gone and things are noticeable smoother.

Anyone interested in testing?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] szucsgf:
There's a whole conversation about this going on in this thread:

http://xdaforums.com/showthread.php?t=2178962&page=54

starting on page 54. Perhaps we can test and share results there.
[Samsung Galaxy Nexus] chikimonke:
Made the change myself, not sure if things are better, or if it's just a placebo like many of these things end up being. As long as it doesn't make things worse though, why not give it a try.
[Samsung Galaxy Nexus] Phazmos:
if you look at build.prop from different roms, you'll see these settings have been in use for a while now on some roms. unfortunately, I can't say 1 that used it was better or less laggy than one that didn't
[Samsung Galaxy Nexus] sarkar1990:
I use these. Nice battery life. OST of 3 hours with everything on.

http://xdaforums.com/showpost.php?p=40404414&postcount=25326
[Samsung Galaxy Nexus] bunnahabhain:
Vanir uses:

I get terrible lag on vanir... I am trying these values out on Purity now.
[Samsung Galaxy Nexus] aosp:
More is not better with these ;)
[Samsung Galaxy Nexus] adambala:
i try to change kernel to test lean but i cant pass the google logo...i flash stock 4.2.2 and boot ok thrn l flash the old wifi drivers and try lean again but still nothing..any help??
[Samsung Galaxy Nexus] sajty:
Try AK cure.
[Samsung Galaxy Nexus] adambala:
i am on ak v207 but i want to try lean...
[Samsung Galaxy Nexus] szucsgf:
Dirty flash your ROM and Gapps, then flash lean.
[Samsung Galaxy Nexus] zandander:
^this

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] terminal13:
Hey SV, have you seen the logs i posted on a 214 issue i was having involving computer connection?
[Samsung Galaxy Nexus] ToMeRv32:
What do you mean by WEP don't work with new drivers?
[Samsung Galaxy Nexus] galakanokis:
He means WEP won't work with the drivers.
[Samsung Galaxy Nexus] PatimusXPrime:
To those of you using FIOPS i/o scheduler, try out these settings and tell me what you think. Seems to be a LOT better for my device at any rate:

async_scale = 10

read_scale = 8

sync_scale = 8

write_scale = 12

Seems much more stable for me than stock FIOPS settings. From what I've read this should work pretty well? Please correct me if I'm wrong
[Samsung Galaxy Nexus] ak:
testing now!
[Samsung Galaxy Nexus] chikimonke:
Just loaded them up. What are some quick "real world" tests to test out IO tweaks in general? Also, do you happen to have an explanation of what those 4 parameters do? I've been looking, but haven't had much luck, as FIOPS is my IO of choice. Paired with Ondemandplus, I've been having what I feel to be great success.
[Samsung Galaxy Nexus] ToMeRv32:
My home wifi is wep secured.

It's working in everything but whatsapp..
[Samsung Galaxy Nexus] PatimusXPrime:
Well I usually go by AnTuTu bench, downloading some apps from the store, pasting files to and from SD card via explorer or computer.. ect.. who knows if this is good? Thats what go by, usually I get some lag when downloading/installing/updating apps from play store but it went away with these settings.

Sure let me find the explanation, i'm on a school laptop and dont have the pages i Looked at earlier when i found it. Give me a moment to find em! :)
[Samsung Galaxy Nexus] chikimonke:
And for those interested, THIS is the page I used to tune Ondemandplus. My settings are currently

General:

TCP: Westwood

RAB 256

IO FIOPS

Min 180

Max 1060

Max Screen Off 525

Min Screen On 180

Governor Ondemandplus

Scheduler Control (after discussing with PatimusXPrime, stock may very well be the best for these currently.)

Governor Control

down_differential 35

inter_hifreq 810

inter_lofreq 525

inter_staycycles 3

staycycles_resetfreq 450

timer_rate 20000

up_threshold 85

I also made the VM.heap mods from earlier as well. I don't have battery results or benchmarks to show, but so far I've been very happy with real world performance and battery drain. For me, as long as I can make it through a normal day and not feel like my phone is struggling and I don't have to plug in to make it until I go to bed, I'm happy.
[Samsung Galaxy Nexus] PatimusXPrime:
async_scale: Asynchronous I/O processing is basically just saying that the I/O can process more than one request at the same time instead of synchronous i/o which is "work until the process is complete." So from what i've read, if we have a higher async_scale it will process more than one task at a time which would in theory slow down the individual task but it would be much smoother when you're doing something else on the phone?

sync_scale: Sort of explained above, so I think by keeping this less than async_scale it will still retain performance but create a slight improvement when multitasking.

read_scale & write_scale: Basically this number is there to bias the I/O scheduler to task reads or writes ahead of the other, depending on which has the higher number. So because our device has a significantly better read speed than write, i have write_scale higher than read. So by my understanding, the I/O will give more priority to writes. I've tested lower numbers, write = 8 and read = 4 and on AnTuTu i got ~10 less write speed on 5 trials so I just went with these values.

http://en.wikipedia.org/wiki/Asynchronous_I/O

and

https://groups.google.com/forum/?fromgroups=#!topic/linux.kernel/-I3KYN1HPy8

were two of my references. PLEASE correct me if I'm wrong, especially with the async and sync because i know FIOPS doesn't exactly treat the I/O tasks as CFQ does so PERHAPS sync and async have no real impact on this?

---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------

Dude this is a great post, i read through the link you posted and it definitely clarifies a lot of those tunables. I'm on hyper which is based off ondemand so a lot of those settings applies here. Thank you for that :D
[Samsung Galaxy Nexus] chikimonke:
Thanks. That all said though, what do the numbers themselves represent? What are their units? As I'm understanding what you have written, it only seems that the numbers determine the bias's of async v sync and read v write. Being that they are "scales" maybe it's the percent difference between the 2? So if Read is 1 and Write is 2, the bias to Write is 100% higher than Read, but with Read 8 and Write 12, Write is only 50% more biased than Read? And if that's the case, would Read 2 and Write 3 be the same as the 8 and 12? Sorry, I'm rambling and thinking outloud here.