yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] wrongway213:
Actually I don't think it's just since AnyKernel, no. I believe I had noted this in the past at one point and forgotten all about it to be honest. Is interactive based on stock interactive, interactivex (wondering as lk is baked in, thought at one point it was just interactivex for some reason to be honest) or based on another interactive governor? I might have to try that, intelliactive scales strangely I think just because I don't know how to set it up without intelliplug, so maybe interactive would be a better fit for me.. tbh I'm not a fan of the stock interactive governor though, and since you based most of your other governors on particular kernels, I'm curious about what interactive comes with the kernel. Also, I find it odd it seems scaling is less aggressive att 110 - 700 and 35 - 2880 then 300 - 605, 300 - 2649.. not sure if your kernel is just set up to play nice with your extreme freqs as they are after all part of your kernel, or if it's just conservative being super aggressive in scaling still. Appreciate the feedback and suggestions, definitely not a bug or issue in the kernel, just performance I'm noticing I'd like to tweak.
[Nexus 6 Android Development] Xileforce:
What your min and max is should affect how it scales afaik. Interaxtivex is stock interactive with off screen frequency tweaks. That's all. I use interactive with Franco's tweaks. Which is just stock interactive with lots of CAF patches and some improvements done by Franco.
[Nexus 6 Android Development] wrongway213:
Lol I know it should affect scaling bro.. I would not belong in a kernel development thread if I didn't I do not think :p I mean it as in: it seems to scale less aggressively when tuned to extreme freqs, both high and low, on both gpu and cpu, then using a higher/closer to stock min and a stock max. I find this behavior surprising, given I would think 2880 and 700 would cause very aggressive scaling - why I wondered if your governors or hotplugs had been optimized/fine tuned to these extreme freqs as they are default in the kernel (other than CPU OC), or if it was simply noticeable in your kernel that scaling works this way because your kernel offers all these variety of CPU/GPU UV/OC combinations.
[Nexus 6 Android Development] Xileforce:
Woops I meant to say shouldn't xD I agree with you. It shouldn't scale more aggressively based on ur frequencies. I'm not sure why it would tbh. I haven't tuned them to my stuff.
[Nexus 6 Android Development] wrongway213:
This... makes sense actually as counter-intuitive as it is to think that OC would be beneficial to battery life.

Ohhh haha, I thought you were thinking I was reaaaaal stupid for a minute and literally didn't understand why setting my freqs affected scaling lmao. I was like uhhhh... but yeah, I think bencozzy here might just have explained it to us.
[Nexus 6 Android Development] Aerigon64:
That however ignores the impact voltage has on power consumption. After all, voltage is squared when calculating power and since voltage increases as you go up, over clocking isn't actually better for your battery.
[Nexus 6 Android Development] wrongway213:
How do you factor in scaling though? Like, say I'm idle 83% of the time, using my phone 10 min/hr. Whether I'm scaling aggressively or calmly is gonna influence my battery consumption WAY more than it would for someone who is using their phone twice that much. If this math really meant anything, would it not have to take this into account? Or did I miss something? That's why I have never put any stock into that voltage equation, I leave the math up to the devs generally and just set a config that gives me performance and numbers I like, for the most part.
[Nexus 6 Android Development] Xileforce:
I think what he meant to say is that even though running at 2.88 for a shorter period of time may allow it to race to idle faster you are going to drain noticeably more battery at those frequencies which obviously can't be avoided. The question is weather or not the tradeoff is worth it. This was the main argument for ppl who said we should only use performance governor.
[Nexus 6 Android Development] wrongway213:
I see. So basically the equation is just a good way to point out that line of logic, that equation is still as flawed as it ever has been.. hmm. So many variables man
[Nexus 6 Android Development] Aerigon64:
I remember it being explained somewhere but I couldn't find the post. Basically if a tasks completion time is directly proportional to the frequency, then increasing the frequency should allow the device to finish quicker and go to idle, saving power. However, when the frequency is increased, then voltage also increases to maintain stability. That results in more power draw.

Even if you idle 83%, most of the power drain is from that 17%, so reducing the power used then even at the expense of idle time is worth it.

Ex task with 1ghz @ 1v (just examples)

Takes 1 minute meaning 1unit power draw (ignoring other factors since they are fairly linear/constant)

Ex task with 2ghz @ 1.15v

Takes 30 seconds but with 1.3 power draw

If you idle for 4 minutes after task 1 and 4:30 after task with 2ghz (that's assuming this is like your setup with ~ 80% idle)

Then idle would take 35mhz *.625v^2 or 0.01367 power per minute. That means that total, your power draw is 1.05 for 1ghz and 1.36 for 2ghz both with 5 minutes on time. That means that increasing frequency and the race to idle is not a power saving measure but a performance measure.
[Nexus 6 Android Development] Xileforce:
This is good explanation. Though you need to keep in mind that the CPU at idle doesn't necessarily mean 35mhz. Idle typically is used to refer to the CPU not processing anything which could also happen at 2.7ghz. When the processor is idle it can go into one of many C or sleep states. It depends on your processor for how many you will have. This basically means that the processor goes uses significantly less power than it would even just sitting at 35mhz but it cannot process anything and in order to process something it has to wake up first. There's multiple sleep states because there are different "deepnesses" of sleep. For instance it can go into a retention state for a light sleep but a very quick wakeup. Or Into a total power collapse sleep which saves more power but at the cost of a higher wake up latency. There's actually a pretty complex driver that decides when and how to sleep your cores. It essentially tries to predict how long a CPU will be idle and put it into the correct sleep state. Sleep states are a big part of why we can run without hot plugging and not completely eat battery. Because most of the time the cores are in some sort of sleep state. Whew...sorry for the long post. Was just trying to explain it clearly. Hope it helps.

Edit:

One last thing. You will actually lose more power even at idle if you are at higher frequencies. For instance if we lock freq to 2.7ghz. That uses a significantly higher voltage. And even if only 1 core is processing something and the others are sleeping but stuck up at 2.7ghz we will get a little bit of voltage leakage which is pure waste. At least I read about that somewhere.
[Nexus 6 Android Development] Aerigon64:
Thanks for adding that. BTW what is total power collapse?

As in what does it change
[Nexus 6 Android Development] Xileforce:
It is the name of the deepest sleep state on the nexus 6. I believe it goes retention, stand alone power collapse, and then power collapse from lightest to deepest sleep. There may be one in the middle that I'm missing though. Total power collapse probably just refers to the deepest sleep.
[Nexus 6 Android Development] Aerigon64:
Do you know what the sleep States do to the CPU exactly?
[Nexus 6 Android Development] Xileforce:
Here's a great read up on it. Its not exactly arm/krait specific because we only have like 3-4 sleep states but it should help you understand.

http://www.hardwaresecrets.com/arti...About-the-CPU-C-States-Power-Saving-Modes/611
[Nexus 6 Android Development] Aerigon64:
That's a great article. Thanks
[Nexus 6 Android Development] Xileforce:
Any time. This thread is supposed to be for learning!
[Nexus 6 Android Development] USA-RedDragon:
No. This thread is meant to F*** S*** up!!!!!
[Nexus 6 Android Development] simms22:
:o
[Nexus 6 Android Development] Xileforce:
That's because I was more worthy of your thanks than jamcswain.
[Nexus 6 Android Development] LunaticSerenade:
So, I cannot find any wakelocks, but my phone is stuck awake. Can that be caused by the mobile radio being held active?
[Nexus 6 Android Development] Xileforce:
I don't think so but I could be wrong. It could also be the google play services wake lock which I don't believe shoes up in all apps
[Nexus 6 Android Development] Macusercom:
Does anyone know what the msm_serial_hs_dma and the msm_serial_hs_rx wakelocks are? Each one has kept my device awake for 30 minutes. Moreover, Android OS and Kernel keep my device for an hour awake. Somehow I got 5h awake while I can see only 3h with apps + kernel. Weird :S

Gesendet von iPad mit Tapatalk
[Nexus 6 Android Development] LunaticSerenade:
But would it show up in BBS or WLD?
[Nexus 6 Android Development] simms22:
its google play services most likely. use disable services and disable systemupdateservices in google play services.
[Nexus 6 Android Development] USA-RedDragon:
And google services framework. Or it won't always sleep

---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------

If your ROM has privacy guard built in, that'll work even better than [MENTION=1811927]simms22[/MENTION] method
[Nexus 6 Android Development] LunaticSerenade:
I'm running stock 5.1.1, so it's not built in.

I will give what [MENTION=1811927]simms22[/MENTION] said a shot.

On that note, does anyone have any ideas on how to kill the wakelock that happens when using a wireless charger? When I take my phone off the charger, I have to reboot or it just stays awake forever.
[Nexus 6 Android Development] wrongway213:
That's smb135x wakelock, believe you can disable it in the kernel via Synapse, if not you can in lkconfig last I checked (althought lkconfig not available if on AnyKernel, yet anyway)
[Nexus 6 Android Development] Xileforce:
Yup it can be disabled in lkconfig. Also I'll try to have an m compatible kernel out in the next few days. Been busy lately.
[Nexus 6 Android Development] LunaticSerenade:
So, fun fact: BBS shows 83% asleep, the built in battery stats shows 100% awake.

O.o

I give up. Battery life is awesome, occasionally I need to reboot, I am done chasing this ****. At least for now. [emoji14]
[Nexus 6 Android Development] Macusercom:
[MENTION=4517211]Xileforce[/MENTION] I've found out that I get SODs when having MSM Hotplug enabled. Mako does not work (even with UKM.zip) nor does MPDecision.

So every boot only MSM and Zen are available. MSM gives me SODs and Zen does not hotplug, but leaves 1 core online all the time :(

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
Mako should be enabled by default unless you manually disabled it. You will have to wipe synapse data and reboot to enable jy again. Zen decision will put the cores on if you turn screen on and off.
[Nexus 6 Android Development] Macusercom:
True, but when I enable set on boot it is not enabled anymore :(

EDIT: After a reboot I mean of course.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
I'll probably just remove the toggle :/ its half working
[Nexus 6 Android Development] Macusercom:
Would be nice. I want to modify some settings in Synapse without needing to apply them manually every reboot. And Mako is still the best, you could do a "special" UKM flash zip for people who don't want Mako and enable it by default with the removed toggle :)
[Nexus 6 Android Development] mwebb34:
It OK to flash this if I'm running Cyonide 5.1.1
[Nexus 6 Android Development] Xileforce:
Should be. If it doesn't boot make sure to have a working kernel on hand or nandroid before flashing.
[Nexus 6 Android Development] mwebb34:
It wouldn't boot, I got system UI FCs. I'm on a permissive ROM also. I also tried some other kernels which yielded same results.
[Nexus 6 Android Development] Xileforce:
In that case use this build.

https://docs.google.com/file/d/0B6n0VW96A9MoNU9fWHJhQWhNNGc/edit?usp=docslist_api
[Nexus 6 Android Development] wrongway213:
So now that Temasek's is cleaned up I can see what issues are in this kernel and what were in the ROM... most were the bugged build. However, mako hotplug not working as it won't stick on reboot and the toggle doesn't work is the main issue.. other than that, type on "bbedwara" and things are awesome. Seems the messed up ramdisk was causing most of my issues indeed. Now to see if I get random reboots on MSM as other user reported, if so I'll shoot you kmsg/dmesg... other than that this thing is running amazing for your first AnyKernel. It runs just as good as always, crossing my fingers mako can be fixed up and the next AnyKernel release should be awesome for sure. I was getting to the point of almost wanting to give up on one of my favorite ROMs (Temasek's) and thus CyanogenMod in general because it just broke every kernel I liked to use.. this kernel has really opened my options back up. You can't imagine how frustrating it is to try to use a highly optimized ROM with full O3 and stock CM kernel.. horrid man. Thanks for ending that awfulness. I can't wait til the next AnyKernel release.. definitely glad I stayed with Vindi for the ride.
[Nexus 6 Android Development] wrongway213:
Everyone dead? :p I think I found a lovely little combo to use given the current state of mako toggle: Conservative with MSM! Stock values for both are perfect. Man, this is nice, never would have thought it would mesh so well. 300 - 2649 cpu 240 - 605 gpu. Scales perfectly but it's fast and super good idle.. really kinda glad you broke/didn't fix the mako toggle because it caused me to find this odd little gem. Benching 50k with 40+% freq spent at 300mhz >>>>>>>>>>>>>> Everyone would be quiet when I have this kernel doing backflips an stuff, haha
[Nexus 6 Android Development] Xileforce:
Lol! Glad to hear u found a good combo! I never ran msm but it sounds like a good balance of battery and power!
[Nexus 6 Android Development] cm0002:
Should i use this build if im on stock 5.1.1?
[Nexus 6 Android Development] wrongway213:
Bro, try it out with conservative and your stock values sometime if you are bored.. it's a beastly combination for exactly that. It does not lag at all, but it is SO efficient and just sips battery. I'll be curious to see if you fix mako, do away with it and focus on MSM and Zen, or add something in its place.. definitely some interesting options available with this kernel man. Loving updating my ROM though, AnyKernel >>>>>>>
[Nexus 6 Android Development] Aerigon64:
How does msm compare to Zen for battery life?
[Nexus 6 Android Development] wrongway213:
MSM is way more focused on battery life whereas Zen is performance oriented. MSM and conservative is a great combo in that it has power but is very good on battery, though - my opinion anyway.
[Nexus 6 Android Development] Aerigon64:
Thanks I'll try it out.
[Nexus 6 Android Development] PatimusXPrime:
Xile, we don't have a fully official any kernel build do we?
[Nexus 6 Android Development] Xileforce:
Negative. The one I posted a bit back should work fine aside from a few quirks. I'm not entirely sure why the ramdisk would cause them though O_o
[Nexus 6 Android Development] Macusercom:
[MENTION=4517211]Xileforce[/MENTION] Will you remove the toggle soon or make it work? I'd like to continue using Synapse but the Mako option is hard to keep active lol :o

EDIT: So after digging a bit into Synapse settings and Vindicator I just did it myself. I've attached a flashable UKM zip file. It is based on the modded flashable zip from [MENTION=4517211]Xileforce[/MENTION] and just has no "Enable" settings for Mako hotplug. So with this Mako is always standard when booting and you can use "Apply On Boot" without the risk of the Mako hotplug checkbox getting disabled. Keep in mind that you cannot properly disable Mako hotplug with this and I'm not responsible for anything. I'm not even a developer lol

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Aerigon64:
Do you have an s6 kernel available?
[Nexus 6 Android Development] Tylog:
That's why it called Any Kernel :) the sense behind is that the Kernel works with CM and Aosp Roms.

Btw. The Any Kernel is fine with latest CM Nightly.
[Nexus 6 Android Development] wrongway213:
[MENTION=4517211]Xileforce[/MENTION] just got a random reboot on AnyKernel running Temasek's CM12 secondary in MultiROM. Wondering if kernel or ROM related. No mods but V4A. Using your modded UKM, not the mako one just posted. Ramoops: http://hastebin.com/eqibarevol.vhdl
[Nexus 6 Android Development] hellsgod:
Unfortunately Its a log from multirom. Did you recieve a call and it rebooted?

hells
[Nexus 6 Android Development] wrongway213:
Nope, sent a text and it rebooted about 30 seconds after I sent it. If it is relevant, the person I texted apparently was out of service area and did not get it until about 20 minutes later (issue on her end, presuming it's not related to my reboot as she had voicemails from non-root users as well when she called me back). May I ask why you thought it would be related to a call, i.e. is something in my log indicating that or is that a known MultiROM issue or something? Assuming you mean MultiROM error when you say MultiROM log (please do correct me if that's not what you meant so I am not just bugging devs with useless logs), I suppose I shall forward this to Tasssadar over in his thread. Thanks for stepping in and taking a look at this- I knew there were a handful of devs this could be meant for when I submitted it but you are surely not one of them, so I appreciate you giving it a look anyway man. Very nice of you.
[Nexus 6 Android Development] Xileforce:
The logs you've posted recently are weird. They aren't normal console ramoops... :/ normally its a super long file and it will clearly say the error and where it occurred. I've not seen one like this.
[Nexus 6 Android Development] wrongway213:
Have you gotten logs from others using your kernel as a secondary in MultiROM before? I can't think of anything else I do differently than the average user (in terms of my phone usage anyway :p) And I'm not even forcing them in Synapse.. these are right in pstore when I boot up.. :/ indeed man
[Nexus 6 Android Development] hellsgod:
Its a known issue on some roms that the device reboots on a call if you use anykernel. And the funny part is, its mostly a problem on cm based roms, which are one of the main reason for using anykernel lol

Yeah it seems to be a log from the multirom bootup (BUG: scheduling while atomic: kexec/253/0x00000002 - 3.10.79-unicornblood-kernel-shamu-lp-g3e206f9-00837-g3de685d #1) and its not the first time I see this type of log after a reboot. But I'm sorry, I can't say much about the bug it states in the log. Maybe a good idea to forward it to Tasssadar :)

hells
[Nexus 6 Android Development] wrongway213:
Excellent, thanks so much for going out of your way to help out with something that had nothing to do with anything you developed. I always really appreciate when I see developers do that for others - definitely appreciate it even more when the courtesy is being extended to me in particular. Glad you caught on what I was getting at on that last part - felt like i had bothered enough people with this log already unless there was something pertinent for him to check out. Thanks again man.
[Nexus 6 Android Development] psychomaniac189:
One thing i noticed running the anykernel version is that the phone has difficulties switching from wifi to mobile data. i just get the bars with the ! mark. if i turn data off then on, BAM, I have data again. i think if i leave it alone it eventually switches correctly. i say that because I didn't have this problem wednesday but I didn't look at my phone the whole time i drove to work and when i finally looked at my phone at work I had data.

Can this kernel be built from source and can you change the ram disk to cm12's ram disk or what is another rom that is AOSP that has all the features that cm12 has? im getting sick of cm's incompatibility issues with things like kernels and now xposed.
[Nexus 6 Android Development] B@RRY78:
Will it work on fusion ROM

Thanx in advance
[Nexus 6 Android Development] e29:
Fusion should run fine on anykernel
[Nexus 6 Android Development] Xileforce:
Yup!
[Nexus 6 Android Development] B@RRY78:
Can u please put OTG in this great kernel
[Nexus 6 Android Development] Xileforce:
Don't we have that already? I never removed it :/
[Nexus 6 Android Development] Megaflop666:
It's already there. If you go into recovery it works perfect so the device sees and recognizes it. If your ROM doesn't recognize the device, go download stick mount.
[Nexus 6 Android Development] Xileforce:
Bout time you said something useful!
[Nexus 6 Android Development] wrongway213:
He's from Ohio... :p
[Nexus 6 Android Development] Xileforce:
Yea...freaking cavs fans...
[Nexus 6 Android Development] Волк:
Well, I am not sure it's ROM or kernel, but I otg isn't working for me either. Seems that it should be enabled in ROM, but stockmount isn't mounting it either. I have had it work previously on other versions of the ROM. ROM is Cyanide. I will see if I can get a log when I get home.
[Nexus 6 Android Development] Xileforce:
If it worked on previous versions of the ROM, then its the ROM.
[Nexus 6 Android Development] ProStreetCamaro:
I must be doing something wrong. Running euphoria and tried 2.4 and 2.3 and getting no LTE. Just an H next to the signal strength. Any ideas?

Scratch that took a while but now showing ltelte.
[Nexus 6 Android Development] Xileforce:
Check your apns and network settings. Make sure its on lte preferred and that your apn is correct.
[Nexus 6 Android Development] Megaflop666:
You can spot the haters wishing they were in Ohio. ;). [MENTION=2632235]bbedward[/MENTION] - help me rally the troops, we need to take over in here.
[Nexus 6 Android Development] bbedward:
Cavs in 6
[Nexus 6 Android Development] Xileforce:
You two are trouble makers. Mainly megaflop. Hes just a terrible person. And we all know the warriors are gonna win. Even when they suck they win or tie the cavs. As demonstrated on thursday, when they are just partially on they smoke em :)
[Nexus 6 Android Development] bbedward:
The cavs were the off team Thursday :p our backcourt didn't make anything. Won't happen again though ;)
[Nexus 6 Android Development] Megaflop666:
I may be horrible, but you wouldn't know what to do without me at this point.

And don't worry, Lebron won't be showing his junk on national TV tonight, so we won't have that jinx hanging over our heads.
[Nexus 6 Android Development] wrongway213:
Cleveland! [MENTION=5867243]Megaflop666[/MENTION] [MENTION=2632235]bbedward[/MENTION] [MENTION=4517211]Xileforce[/MENTION] making trouble and being a terrible person >>>>>
[Nexus 6 Android Development] quaman:
Where can I find the link for 2.5 I really want to try it
[Nexus 6 Android Development] LunaticSerenade:
Ohioans out number you here [MENTION=4517211]Xileforce[/MENTION] [emoji14]
[Nexus 6 Android Development] Xileforce:
Gah! Am I going to have to add a no Ohioans allowed rule to the OP? I swear u guys just come from nowhere. Is everyone on xda from Ohio?!? Its like every time I get rid of one Ohioan another takes his place! But I think megaflop is actually a traitorous warriors fan. Just throwing that out there...
[Nexus 6 Android Development] wrongway213:
Actually, I'm gonna go out on a limb and say that Megaflop and me being cool on the forums is purely coincidental with us being Ohioans, believe he recommended this great kernel to me long ago so we both end up here together. Then you decide to go BFS and we all know BFS is based out of Cleveland anymore.., so there's bbedward, so yeah man, you invite Megaflop here, you rebase on Zen, you make me happy by finally releasing an AnyKernel.. you've done this to yourself :p