yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] parkson:
Toro Xylon 10 with AK 457/intellidemand/bfq is the best combination! :thumbup:
[Samsung Galaxy Nexus] odin13:
What's not good with this kernel on PA?

I use it on PA 2.99b6 and all is good :D

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] abalam:
Best kernel in combination with Xylon. Thanks Anarkia
[Samsung Galaxy Nexus] albsat:
How about a 1036 mhz slot? Would that be saving battery life"?
[Samsung Galaxy Nexus] Nicuz95:
I've already asked for it, you can set this frequency using LiveOC :)
[Samsung Galaxy Nexus] albsat:
Sorry to ask. But how do you do that?
[Samsung Galaxy Nexus] pcphobic:
Hmm...interesting. I may follow your settings.
[Samsung Galaxy Nexus] butikofer08:
If he made a virus I'd download it....
[Samsung Galaxy Nexus] slayr76:
Just flashed Franco kernel an freezing an boot loops went away , using Franco kernel with trickster on atom v12 rom, definitely a problem with ak kernel from v80-99, no disrespect to anarkia but your kernels just don't like my gnex maybe :D
[Samsung Galaxy Nexus] cubsfan187:
There are about 1k people (if not more) that would disagree with that statement. Myself being one of them. Your phone was freezing up and looping? Which kernel version? What rom? What gov setting? Overclocked? Underclocked? Undervolted? Need more info to be able to help out.
[Samsung Galaxy Nexus] Wdustin1:
Ak kernel is the best thing that has ever happened to my gnex
[Samsung Galaxy Nexus] terminal13:
Wasn't that discussed earlier about script conflicts? Or was it a different rom?

AOSPA/AK device.
[Samsung Galaxy Nexus] DoesntPostAThing:
It was Atom. Anarkia has said multiple times that that ROM has init.d scripts that conflict with AK's scripts.
[Samsung Galaxy Nexus] noshet:
To be exact... Does anyone know which Vanir/Atom scripts/what values need to be adjusted in order to get rid of these conflicts?

Thanks in advance.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] galakanokis:
I don't doubt that there is some conflict but one would think it has to be something specific or that there are a lot of phones just sitting on an edge with this combo. Some are having issues but there are a number of us that are not having any issues. Just re-installed Atom and tried 80/83/90 and I cannot reproduce any issues whatsoever. Very strange.

Is it just Atom or are other Vanir based acting the same way?
[Samsung Galaxy Nexus] terminal13:
Never had any issue with paranoid and ak. Like pb&J. Gotta read up on the hyper governor. Pretty snappy.

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] PatimusXPrime:
OK! So this is what my settings are. I think that even if you let it default nut changed powersave_bias it would do the trick. That basically says how more the CPU tends to stay at lower freqs

Been sitting with the screen off for 2 hours and battery hasn't moved lol terrific
[Samsung Galaxy Nexus] NeverSeparate:
To be fair you cut off his statement kinda short. You left out where he said maybe they don't like his phone. That being said, more info would help indeed.

Sent from my Carbonated Gnex
[Samsung Galaxy Nexus] tomzefi:
I ran ak with vanir every time with 0 issues. Navigate to SD card and you will see a vanir script. Open it in text editor and change the first line that enables the script to 0. You will see it and it explains it better than me.
[Samsung Galaxy Nexus] cubsfan187:
Actually I didn't. He edited it AFTER I quoted him. :)
[Samsung Galaxy Nexus] terminal13:
What are your last two settings? Not on ss

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] NeverSeparate:
Well then disregard.

Sent from my Carbonated Gnex
[Samsung Galaxy Nexus] ben.nesheim:
So far 99 has been great. I was playing with abyssplug and it was stable til it seemed like it was pushed hard randomly(happened when going through chrome settings and when running Google maps when I was about. Was using a 350 min and 525 screen off max. 1200 max and only -25 uv on the lower half of freqs. I think if I were to keep messing with it but 230 - 1200 with a 350 screen off. And mostly stock settings is crazy smooth and still great on battery so far. Still with paranoid android
[Samsung Galaxy Nexus] slayr76:
Atom v12, ak 99 kernel, default kernel settings, no mods.
[Samsung Galaxy Nexus] musashihatred:
Anarkia: wifi drops are gone :).
[Samsung Galaxy Nexus] Hetalk:
As promised here's my overnight idle battery drain report with v99.

Hyper governor.

Close to nephilim's settings.

Hyper is now my personal favorite. :thumbup:

Woah. Message sent. I need not say no more.
[Samsung Galaxy Nexus] MДЯCЦSДИT:
Anarkia, you should add a sysfs entry to turn off cpu1 with screen off regardless of the governor (in the same spot where the screen off max freq is).

Here is an example, but you probably want to make it toggle-able via sysfs so you can enable and disable it in trickstermod: https://github.com/marcusant/Xi/commit/9096fd26917c0cdefacead8033ab4aefcd89dddf

I've been working on making it have a sysfs toggle myself and would submit a pull request, but I haven't had time to set up a build environment lately.
[Samsung Galaxy Nexus] PatimusXPrime:
i didnt change them, theyre whatever the default was. let me know what you think! i think i notice a slight difference? im not sure if its just a tad laggier with no battery impact? im gonna try and figure that out and if thats the case ill just put it back to stock and deal lol..

either way this is awesome!

---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------

eh i dunno dude, my phone sometimes has problems with hotplugging.. especially when im playing music, i have a mod installed that adds a CRAZY amount of eargasm at the cost of cpu power. totally worth it lol
[Samsung Galaxy Nexus] MДЯCЦSДИT:
That is why I suggested a sysfs toggle for it.
[Samsung Galaxy Nexus] chrissurra:
westwood
[Samsung Galaxy Nexus] slayr76:
Actually i didn't edit my post, why is when people have a problem but others may not you just want to crucify them rather than help or try to understand, trust me i always thought this was a great kernel but i can't use it after what it does with my phone at the moment, you just take any issue with something as an attack, anyone would think i was an apple fanboy the way you talk rather than a fellow gnex user with a kernel issue, hitting the thanks button on people who flame others with problems makes no sense either, check the atom an also the trickster mod thread if you still think there's no problem with ak kernel for others :rolleyes:
[Samsung Galaxy Nexus] nikulogical:
also confirming SODs with hyper
[Samsung Galaxy Nexus] DoesntPostAThing:
Really? Hyper's been behaving fine so far on Rubik v4.
[Samsung Galaxy Nexus] slayr76:
Just because it works fine with you doesn't mean it does for everyone else dude, get over yourself seriously.
[Samsung Galaxy Nexus] jeffcavicchi:
Can someone please explain to me exactly how to revert to the old wifi drivers so that I can flash a different kernel? I have tried flashing both the zip and running the script from script manager - neither work. When I flash the latest franco kernel I can't even turn wifi on.

I am trying to troubleshoot the problem I am having with AK and Trickster/Atom, so any help would be appreciated.
[Samsung Galaxy Nexus] Hetalk:
No sods since release.

My settings

Running cubic row hyper 180-920

Mpu undervolted by 50

Kindly share your settings. :)

Woah. Message sent. I need not say no more.

---------- Post added at 08:59 AM ---------- Previous post was at 08:57 AM ----------

Thread op has a zip file and instructions on how to revert to old WiFi drivers.

See if they help you. All the best.

Woah. Message sent. I need not say no more.
[Samsung Galaxy Nexus] jeffcavicchi:
Umm...I just said that I followed the instructions in the OP and it didn't work - neither the script manager version of the zip worked.
[Samsung Galaxy Nexus] terminal13:
Patimus, just a teeny bit of lag initially, then it set in and seems to be settling down. The battery is holding great. Nice slow trickle with nice performance and no sods.:thumbup:

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] galakanokis:
easiest way is to dirty flash your ROM and then flash a different kernel.

Have people with issues with the AK/Atom combo tried deleting the init.d scripts?
[Samsung Galaxy Nexus] Hetalk:
Did you flash reset to stock kernel zip file for 4.2.2?

If yes, and if it still didn't work, wait for someone more informed than me to reply. :D

Edit: I don't see a scriptmanager version to revert to stock kernel. Are you sure you're not using the bug report script by mistake.:p

Woah. Message sent. I need not say no more.
[Samsung Galaxy Nexus] jeffcavicchi:
Just tried that, and so far everything seems to be working better - no reboots anyway. We'll see.

Thanks!
[Samsung Galaxy Nexus] terminal13:
Also pulled the power save bias back to 100.

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] Hetalk:
I think I read anarkia1976 saying that atom's init.d scripts may play foul with ak kernels. Didn't read more into it as I wasn't on atom. See if you can find it.

Chill, buddy. One guy is confirming sods and other's confirming no sods. Both posts are equal in being helpful, if u know what I mean.:D

Woah. Message sent. I need not say no more.
[Samsung Galaxy Nexus] zandander:
I think hyper is the best, bar none, governor I have ever used. The way I have my kernel set up now has never been this smooth battery friendly and snappy. Using 180-920 undervolted 50 across the board.

I personally believe this is the best you've put out yet Stefano. Even better than cylon 801!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hetalk:
Agree. Did I mention that its super snappy as well even with UC and UV? :thumbup:

Woah. Message sent. I need not say no more.
[Samsung Galaxy Nexus] galakanokis:
Guys with issues, what is content adaptive brightness set to? There were/are reports over in Franco's thread about people having issues with freezes and reboots and being told to change this setting. Sounds strange but some said it worked. Might be a bug in there some where.

Couldn't hurt.
[Samsung Galaxy Nexus] zandander:
I believe you did lol

I'm using some settings you posted I believe.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ak:
idle

I have tested, the idle drain for Hyper and Interactive is the same " 0.2 % - 0.3 % " hours.

This is correct because the deep sleep status of the core is kernel dependency.
[Samsung Galaxy Nexus] ak:
I want to say that the problem of Wifi drops was not a problem of ATOM or others roms.

I have resolved after a lot of days of debug with a collaboration with TheMysteriousOne.

These are the changes, not all rom affected:

CONFIG_CFG80211_DEFAULT_PS is not set

"This option enables powersave mode by default."
[Samsung Galaxy Nexus] ranasrule:
this is just amazing....Hyper governor is snappy as hell....just when I thought my GNex couldn't get any faster AK proves me wrong
[Samsung Galaxy Nexus] ak:
This behaviour, was present for Interactive and Conservative, with implementation of the Early suspend core 1 off when screen on/off.

I have reverted this for the intereractive and left only for consevative, because a presence of lag during late resume.

Thanks a lot for collaboration.
[Samsung Galaxy Nexus] galakanokis:
Yes, I know. Was just pointing out an easy way for the guy to switch kernels with out boot loops. The second line was in reference to the others that are having issues with freezes and SOD's with atom and your kernel. I didn't word the post very well at all, sorry for that. Trying to watch the hockey game, get the kids to bed and read your thread, just too much for one dude to do...
[Samsung Galaxy Nexus] szucsgf:
I had the reboot issue that was mentioned in relation to Atom, though I'm on Vanir. That is, if I did not interact with my phone while it was in the process of booting it would reboot itself. I had CAB turned on. I turned CAB off and I haven't had this issue since. I've rebooted 3 times.
[Samsung Galaxy Nexus] ak:
Can you send me your best setting for Hyper?
[Samsung Galaxy Nexus] n0ve:
Alternative method to those running any vanir based rom if you don't want to modify vanir.cfg to AK values and comment out the inappropriate values, just open terminal and type vanir disable.also to play safe ; Su -> zram disable
[Samsung Galaxy Nexus] madhavs:
I have flashed V99 yesterday on latest carbon nightly dated 15th APR and the idle drain over night was astonishing 0.2% With all default kernel (generally i don't want to experiment more coz i believe stefano pre optimized it with performance and power) settings. This so far the best battery performance on my phone since i bought 5 months ago

Out of excitement i didn't took screens of it I will post on next cycle

Thanks a lot anarkia for such a wonderful work :good: and the others who helped in creating such a wonderful work :)
[Samsung Galaxy Nexus] ak:
Thanks a lot.

v99 + Carbon 15th:

View attachment 1887319

I remember some time ago v467 + aokp with the same performance .... im very happy after a lot of work for fix a lot of bug.
[Samsung Galaxy Nexus] nikulogical:
Calm down he's just sharing his experience.

Stock settings with just the governor changed and tcp algorithm I think.
[Samsung Galaxy Nexus] tomzefi:
Hey are you running the extended battery? I ask kuz I was having same issues and i thought it was the kernels. My extended battery, or any battery for that matter was not holding the voltage changes that would occur when there was a jump in frequency. I had it tested and it was confirmed. Put a new battery in and all was solved. Just throwing it out there for ya. Some kernels that are more aggressive can initiate this more often than others. Hope it helped. All the best.
[Samsung Galaxy Nexus] Az Biker:
Not to sound condescending, but have you tried a full wipe, reflash Atom, gapps, Ak, let it settle for a bit, reboot and set up trickster following my, Nephilim's or themysteriousone's kernel settings?

The reason I ask is; a factory reset & system wipe with the above instructions has helped a few folks resolve similar issues.

Again, I ask with all respect and sincerity trying to help you solve your issue, so you too can enjoy Atom and AK together! :D
[Samsung Galaxy Nexus] irminsul:
Nope still have them at home.

At work I had them only once or twice yesterday. Gonna try at home again with WiFi opt unchecked.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] DoesntPostAThing:
Is it possible for a CM theme to cause lags and slow transitions? I was using HoloGlass, and apps would delay for a second before opening. Switched to system theme, and apps now open instantly. I thought it was kernel/ROM issue before, but guess not!
[Samsung Galaxy Nexus] bmg1001:
Yes, especially a theme like HoloGlass in which many applications are transparent.

System theme was always the fastest for me too.
[Samsung Galaxy Nexus] shanp7780:
I concur with AZ atom v12 is fine with AK's latest was on atom all weekend just have to play with settings some here and there running liquid atm w/99 blazing along all day Hyper, FIOPS, slightly UC'd.

Anarkia sir you are starting to reach a mythical level with your kernels you continually raise the bar and make the G-Nex perform above and beyond it's abilities.:thumbup::thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ak:
Theme sometimes can create also problem with trickster settings stick at boot :thumbup:
[Samsung Galaxy Nexus] ChazzMatt:
cubsfan187, if he edited AFTER you quoted him, his post would show an EDIT stamp. It doesn't. See the edit stamp on this post? :)

Just say you are sorry for getting caught. ;)
[Samsung Galaxy Nexus] Frank_9.5:
+1

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] DoesntPostAThing:
Wasn't just me then.

Thanks for the tip, will keep in mind if set on boot ever doesn't work for me (always did)

Sent from my Paranoid Galaxy Nexus powered by AK Dummy Kernel
[Samsung Galaxy Nexus] ak:
I have a lot of confirm that wifi never happen anymore ..... :fingers-crossed:
[Samsung Galaxy Nexus] mrdevil_25:
question:

i am using trickster mod to monitor the voltages:

i have SR on but lowered MPU to 760mV.

What i have noticed is that both 230 and 350 runs at 790mV.

if this is the case, would it not make sense to run at 230 since it is using the same amount of power?

just wondering. thanks for input.
[Samsung Galaxy Nexus] ak:
have you lowered MPU min?
[Samsung Galaxy Nexus] sajty:
Guys,i need your help (opinion,experience).I know,its a little bit of topic,not related to kernel,but...Is normal,that system UI takes 9% of battery?I think,that its tooooo much.
[Samsung Galaxy Nexus] ak:
restart

You can use this script for kill ... for my point of view isn't normal.

All thanks to Lioux:

Remove .txt:

View attachment 1887570
[Samsung Galaxy Nexus] mrdevil_25:
yup, i have lowered the MPU min to 760.

I have even tried to lower min to 700 but it still runs at 790.
[Samsung Galaxy Nexus] ak:
Probably is the min for SR .. try to disable It. but NB: Its dangerous! :fingers-crossed:
[Samsung Galaxy Nexus] qu4nd:
Is it "normal" that i get less deep sleep using hyper compared to interactive?
[Samsung Galaxy Nexus] ak:
For me is the same 0.2 0.3!
[Samsung Galaxy Nexus] sajty:
Thanks.Restarting systemUI helped.Usage of processor by systemUI is now lower too.
[Samsung Galaxy Nexus] mrdevil_25:
hahahaha its ok i'll stick to the safe thing here haha.

i'll just stay with 350 min to 1200 max

since its showing the same voltage for both 230 and 350 I dont see a point for me to lower it to save power.
[Samsung Galaxy Nexus] kekko986:
Wi fi direct issue with ak kernel

Here the kernel dump for wifi direct issue, see attachment
[Samsung Galaxy Nexus] ketann:
For me its showing same voltage for 230-250-525 which is 820mV. So it won't make any difference in battery if I set min freq to 512?
[Samsung Galaxy Nexus] buggerthis:
I'm pretty sure power drawn by the CPU is related to both the voltage and the frequency, so it would make some difference to battery life, I couldn't say how much though
[Samsung Galaxy Nexus] terminal13:
Are your .2/.3 drains with hyper and is it stock or patimusx' tweak?

I let hyper sit overnight with the tweaked set up and went from 28% -14% from 11:15 p to 6:15 a. Stock battery. Must have something out of line......

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] qu4nd:
I'm also having trouble using hyper. Wasn't able to figure out why yet.
[Samsung Galaxy Nexus] szucsgf:
http://xdaforums.com/showthread.php?t=2175147

It will make a difference in battery. Power = Capacitance * (Voltage^2) * frequency. % Changes in voltage have a larger effect on power usage since power changes by voltage squared, but higher frequency at the same voltage will still use more power.
[Samsung Galaxy Nexus] BlackMaster1991:
Is there a paper about the governor options? I want to know more about the different options like hyper or interactive, and of course about the options like sio, fiops and the others. I'm quite new to this topic.
[Samsung Galaxy Nexus] ak:
bb

The problem Is not Hyper ... if you change the idle governor certainly drain persists.

I dont have problem with carbon and basic apps.

You can check with BBattery if you have wakelock or other rogue app.
[Samsung Galaxy Nexus] ak:
Into OP some links ... otherwise you can use google and search "XDA GOVERNORS" or "XDA SCHEDULERS" :highfive:
[Samsung Galaxy Nexus] BlackMaster1991:
Thanks for info, didn't see this,
[Samsung Galaxy Nexus] terminal13:
Hyper is fantastic. Just trying to get the most out of it..

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] sambaeallegria:
Today with 230mhz minfreq (screen off) I had 2 reboots. Seems that hyper governor doesn't like frequencies under 350mhz while with interactive I sticked at 180mhz (same MPU voltages). It's weird that reboots happened after 14h of 230mhz minfreq and one consequently to the other, both when my screen was off but it stayed off all night long,also for a long time in the morning, and no reboots happened.
[Samsung Galaxy Nexus] ciprianruse88:
Mine works fine with min 230 mhz. on it since 18 h ago and no reboots. You can post last_kmsg to track the problem ;) oh and btw...I don't use pgm :)
[Samsung Galaxy Nexus] szucsgf:
http://xdaforums.com/showthread.php?t=2194044

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

http://xdaforums.com/showthread.php?t=1369817

https://github.com/android/kernel_c...d2057edd/Documentation/cpu-freq/governors.txt

These have lots of info about governors etc. The first two are more general. I haven't been able to find much on hyper specifically.
[Samsung Galaxy Nexus] cubsfan187:
On topic: V99 is running great for me. UC'd @920 and using hyper gov. besides color changes, the only other setting I changed from stock was the power saving cores. I have it at 2. Very nicely done AK!

Off topic quickly. MBQ, what happened with Project M? Haven't seen it for Toro lately.
[Samsung Galaxy Nexus] butikofer08:
Interactive rock solid as usual. Going to try hyper today. Was going to apply the governor tunables I have screenshots saved of but I notice hyper tunables are totally different. Not even a HSF frequency.

Any one work out any sweet spots for hyper tunables and care to share screenshot?

Found one a couple pages back but others reported issues.

:beer:
[Samsung Galaxy Nexus] ak:
Im using hyper with:

180 min

350 screen off

230 min on

1200 max

mpu undevolt -25

all rest default

No problem at all .... 2 hr idle = 0.1% drain = Fantastic!
[Samsung Galaxy Nexus] Charmacas:
Two questions about your setup:

1. Why don't you use 1350 instead of 1200 or otherwise why do you prefer using 1200?

When I think about it and look at the voltages I decided to use 1350 but maybe I am wrong!? ::confused: The voltage of 1350 is only a bit higher but we got 150 Mhz more power to come back to lower frequencies.

2. When you're undervolt MPU by -25 do you deactivate SmartReflex? And so... isn't it better to let SmartReflex do the job and configure Min voltage to (as I do) 700 for example?

Just a few questions to get your opinion and maybe others opinions. :)
[Samsung Galaxy Nexus] musashihatred:
I'll try this. :)

sorry Captain, limited to 8 thanks already -_-
[Samsung Galaxy Nexus] logi43:
Thanks again for your great work, Ak 0.99 and the new settings in init.d osmosis make this kernel "pure butter"

My settings: Carbón nightly 16/04 /

TCP / Cubic /

row / interactive / / -75 UV. / /180/1200 / minimum / maximum

Screen off 350.

Scrip color init.d settings:))

contrast / 9 /

Ajust gamma 0 /

Red / 0 /

Green / 0 /

Blue / 0 /

Múltiplers /

Red / 240 /

Green / 240 /

Blue / 325
[Samsung Galaxy Nexus] shawnaye:
Hey AK, you mentioned you isolated the WiFi dropping issue. Is the fix already implemented into Diamond v99?
[Samsung Galaxy Nexus] ak:
Yes ... :fingers-crossed:
[Samsung Galaxy Nexus] terminal13:
Do i have to reflash the kernel to default the hyper settings?

Lurking on my AOSPA/AK device.
[Samsung Galaxy Nexus] ak:
Untick trickster set on boot .... go to data/app clear cache and data.

Reboot.
[Samsung Galaxy Nexus] dominatore22:
Where i can find hyper governor? O.o i dont have it on governor list o.o
[Samsung Galaxy Nexus] PatimusXPrime:
You using v99?
[Samsung Galaxy Nexus] ak:
Hyperspace!
[Samsung Galaxy Nexus] PatimusXPrime:
Yeah dude even if you just uncheck "set at boot" and reboot it'll work

Also guys, i figured out that default + powersave_bias = 125-250 is really sexy :D
[Samsung Galaxy Nexus] xxSAKISxx:
if you run v99 that's impossible. Everybody that run v99 have it. Try to look carefully.

Send from my awesome-superb-f.... ng incredible Galaxy Nexus
[Samsung Galaxy Nexus] dominatore22:
Yes o.o but i dont have it o.o
[Samsung Galaxy Nexus] ak:
Do you use trickster ? O_0

Uninstall recovery wipe cache and dalvik reboot install ... :fingers-crossed:
[Samsung Galaxy Nexus] szucsgf:
Hyper is a governor not a scheduler.

Scroll a bit further down in trickster.
[Samsung Galaxy Nexus] relax24:
180 min

350 min screen off

230 min screen on

Am I not understanding properly? Should min and Min screen on be the same, because it's the same thing??
[Samsung Galaxy Nexus] dominatore22:
Oh god >___< sorry all, :Facepalm