yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Megaflop666:
Flashed test on my current build, still no deep sleep.

Just upgraded to latest nightly and flashed latest kernel. It's currently upgrading apps so I'll let you know.

If the upgrade doesn't work, I'll do a clean install and let you know.

Edit: no dice on upgrade. Bootloop after upgrading apps.

Just did clean install using latest gapps I have from March 7. Will check back in shortly.

Edit: bootloop after clean install.

Don't know if it matters but I am on f2fs data and cache, but it hasn't been a problem until this week for upgrading. If need be I can strip it down tomorrow morning and rebuild it on ext4 if you think it'll make a difference...unless someone else has ext4 across the board and has the same problems.
[Nexus 6  Original Android Development] jiv101:
Are you on the latest play service?

There are multiple threads stating that the updated Play services at keeping devices awake... I was on banks 3/5 and also experienced no deep sleep reverted back to a gapps package from Feb now it's deep sleeping all the time
[Nexus 6  Original Android Development] bleached45:
I just turned off tap2wake and it seems I am deep sleeping again. A shame, I loved that feature on my G2. Wonder if there is anyway to make that more battery friendly. For now I guess I'll keep it off (reluctantly) and test it for longer.
[Nexus 6  Original Android Development] Megaflop666:
I'm using standard gapps 5.0.x 3-7-2015. At this point I'm thinking I'm just going to deal with it and wait for cm12.1 and hydra kernel to drop to lollipop 5.1 since cm announced they're switching and most other stuff is switching to 5.1 as well

---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------

I've never enabled that feature but I'll go check that.
[Nexus 6  Original Android Development] chipstien:
This. I wasn't sleeping on anything using a gapps from March. Reflashed using a Feb gapps and presto..... Deep sleep again.
[Nexus 6  Original Android Development] Damon13:
Hey Neo,

The issue still persists where the phone just turns itself off, This time after i was done with a phone call the phone wouldn't turn on. After a reboot things were fine, I did all you asked. I did another clean flash of an older version of hydra, and after 10 hours no issues at all.
[Nexus 6  Original Android Development] neobuddy89:
Thanks, this will be resolved in tonight's build.

Seems like issue persist with FB notifiers. :(
[Nexus 6  Original Android Development] Megaflop666:
Tried pa gapps rc3 2-1-15 and still no dice.
[Nexus 6  Original Android Development] neobuddy89:
New nightly build!

This build is for 5.0.2 and may not work with 5.1.

Hydra_v1.0-[03-14]-[00-21]

* Updates from lollipop-mr1 release. (which are compatible with 5.0.2)

* Bring back state notifiers.

DL: https://www.androidfilehost.com/?fid=95916177934541072

CM12 based ROM users if you are facing any bootloop, please follow below steps:

1. Install CM12 ROM

2. Let it boot completely.

3. Reboot to recovery and install Hydra.
[Nexus 6  Original Android Development] neobuddy89:
Using PA Gapps dated 20150301, no issues here.

Install Better Battery Stats app and check what's keeping it awake.
[Nexus 6  Original Android Development] Megaflop666:
Moot point at this time. Just did the 5.1 update.

Can't wait to see your kernel on 5.1
[Nexus 6  Original Android Development] ventu08:
neobuddy89 you can enter the mpdecision of bricked, with loads and the times for each core?

thanks :)
[Nexus 6  Original Android Development] neobuddy89:
Sorry, I don't understand your question here.
[Nexus 6  Original Android Development] ventu08:
You can insert this ?

https://www.copy.com/s/ftMaXFHXQCNVz6oA/Screenshot_2014-06-18-18-43-54.png
[Nexus 6  Original Android Development] neobuddy89:
Greetings!

Presenting preview build for 5.1 ROMs.

Before you try it, some lines of wisdom:

5.1's hyped "all cores online" is just s#it. What you really wanna achieve with that? Smoothness?

We already got that with touch boost aka project butter. (Apologies if your stockish kernel didn't gave it.)

So, do not fall for false claims.

You *must* use 5.1's bootloader and modem. You can find flashable version HERE in case if you don't have.

If you don't use these on 5.1 then you will get random dead screen. It's Moto's black magic.

Hydra base is not rebased for new release instead we have adapted all required updates for 5.1 so as you can enjoy all features including hotplug, limiter, etc with Synapse.

This is preview build. We will switch to nightlies once CM12.1 starts rolling out.

* Hydra 2.0 is ONLY for 5.1 based ROMs. *

DL: https://www.androidfilehost.com/?fid=95916177934541617

So far, so good. Tested with Stephen's ROM here since it is only build that has fixed phone call issue as of yet.

Feedback welcome! Cheers... :highfive:
[Nexus 6  Original Android Development] hellsgod:
Yep, I also don't see the point leaving all 4 cores on by default. Dunno why google left it that way.

hells
[Nexus 6  Original Android Development] Megaflop666:
Been craving this the past two days. Flashing now
[Nexus 6  Original Android Development] Megaflop666:
Well damn. I flash it and after reboot my phone tells me my system is partition is almost full and Google app keeps fc'ing. Running stock 5.1
[Nexus 6  Original Android Development] neobuddy89:
This doesn't seem to be kernel issue.

Were you on some other kernel before? If yes, reflash ROM and then kernel.
[Nexus 6  Original Android Development] Megaflop666:
Ya. Was on elemental x. Flashed stock unencrypted kernel and got the same result. Grrrr... I've been sticking with the stock image until cm updates but I'll go find a flashable stock 5.1 rom to dirty flash so I don't have to redo everything.
[Nexus 6  Original Android Development] hellsgod:
Flash the system.img via fastboot should do the trick, without losing any data.

hells
[Nexus 6  Original Android Development] Megaflop666:
I'll give it a shot. Thanks
[Nexus 6  Original Android Development] bleached45:
I was wondering if you would weigh in on this a bit more. From what I read a little, it sounds like Google prevented cores from getting unplugged and instead keep them all on until they go into suspend. Supposedly this removes the hot plugging overhead and boosts. And this is supposed to save battery and increase smoothness? Franco seems to like this idea (based on his initial g+ post about it). But you do not.

And Google is now utilizing the C states the SoC is able to go into? I have all those on with Hydra anyways, so I guess that isn't too great here.

Do you think keeping all cores online just consumes too much power, especially with yours and other non-stock kernels optimizing past what Google did?

Thanks. Just trying to educate myself on this change. I'm still running 5.0.2 haha.
[Nexus 6  Original Android Development] purian23:
Horrible Kernel name really :/​
[Nexus 6  Original Android Development] neobuddy89:
What google/moto did is introduced redundancy or bug.

Consider your screen is on. All cores get online. Why?

Each core is able to go 2.6 GHz which means one core can perform 260000 tasks within one clock cycle or second.

So that means keeping all cores on all the time is redundant.

Checking lockscreen for notification => makes all cores go online.

Listening music, watching a video => all cores go online.

and so.

Multicore ability is useful for heavy computation like playing games or running CPU intensive tasks.

So, the best way to decide when a core is hotplug should depend on load of previous CPU.

Qualcomm's CPU boost driver boosts min freq to input boost frequency. i.e. 1.4 GHz whenever you touch screen.

This touch boost is perfect.

Google's mpdecision and powerhal introduces non-configurable complete 3-10 seconds of min freq boost and that too on all cores.

If CPU cores will go online and boosted all the time, surely there will be more power consumption comparatively. (even if one says power consumption is less)

My and other devs idea of keeping this mess in control is simple.

Let CPU boost do all the frequency boost. Let hotplug driver do hotplugging as and when required.

(instead of single mpdecision messing up things)

In Hydra kernel, MSM and Intelli hotplug drivers features touch-boost CPU cores. This feature ensures that atleast boosted_cpus remain online when you touch screen.

Additionally, CPU boost driver has hotplug boost which means when your core goes online from offline state, its min freq will be boosted.

The drivers and mpdecision binary of Hydra kernel will ensure device gets enough boost and no. of online CPUs as required for smoothness and performance without redundancy.

Hotplugging overhead is bearable considering device will be used for variable scale of loads and in most cases for low load.
[Nexus 6  Original Android Development] neobuddy89:
What's there in name? Lol.

Suggest one, I might make up my mind to change. :p
[Nexus 6  Original Android Development] rignfool:
Because...

At least in my testing on both this and leankernel... I got better battery life... Like 6 or 7 hours screen on time...

It seems that the phone uses more power than it saves off and on lining cores...

Also... With all 4 cores on... My phone (unless playing a game) NEVER gets above 2 GHz CPU speed....
[Nexus 6  Original Android Development] Megaflop666:
Didn't work. Got the same result. Did a wipe and clean install and the kernel was working great. Unfortunately I don't have time today to deal with setting up my accounts and other bs involved with a fresh build so I had to restore my nandroid.... Hopefully cm catches up to 5.1 soon do I can get back to cm and hydra, perfect combination.

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

Love the name!
[Nexus 6  Original Android Development] neobuddy89:
That's fine. However, 5.1 brings overall good battery life.

You can anyhow configure that on custom kernels using "Min Cpus Online" = 4.
[Nexus 6  Original Android Development] hellsgod:
Depends on usage in my opinion. If you're mostly reading on the device, its pointless to have all 4 cores online when the device is mostly idling, don't you think? My phone also gets barely over 2ghz without all 4 cores online all the time. I've read from a few people, which got horrible battery life with 4 cores online all the time. As soon as they switched back to 5.0.x hotplug routine, their battery life got better again. So no, 4 cores online all the time is not a battery saver for all.

hells
[Nexus 6  Original Android Development] wrongway213:
I idle for long periods of time (hours sometimes) and then will sporadically use my phone for like 40+ minutes SOT at a time, then put it down. A user like me would almost assuredly get better battery from hotplugging than 5.1's four cours online all the time, would I not? (I know you can't know my device usage, just based on what I have given you + no tethering, mostly Chrome, XDA, phone calls or music). I feel like you have a very good understanding of this based on your posts so I decided to direct this your way, I hope you do not mind me asking.
[Nexus 6  Original Android Development] hellsgod:
I don't know how mpdecision handles the core management on screen off. I doubt mpdecision leaves all cores online in suspend. So if you listen to music or make phone calls, it shouldn't affect you that much. I've used the stock rom and the stock kernel for a while to test the behavior. I noticed more heat and more drain with my usage. Mostly tapatalk, hangouts, browsing and so on. With my normal usage and my tuning I lose around 2% in 10mins, with the google behavior it was 3% or more. In the end you've to test it for yourself. Run 4 cores for a day or two and run "the old behavior" for 1 or two days and decide for yourself what suits you better :)

hells
[Nexus 6  Original Android Development] dany20mh:
[MENTION=3795148]neobuddy89[/MENTION]

Bug report:

So I flashed the 2.0 version but the KCAL setting won't work and they won't stick.

When you apply them and hitting the check mark on the synapse app, they will change and you can see the color change in the app but when you go outside of the app, nothing changed and if you come back inside the app, the setting is trying to back to the default value.
[Nexus 6  Original Android Development] neobuddy89:
Issue confirmed. Will be fixed. Ready for second preview build? ;)
[Nexus 6  Original Android Development] dany20mh:
Yes, bring it on.

Also waiting for the Intelliplug 4 and other goodies you promise too :)
[Nexus 6  Original Android Development] purian23:
Yeah my bad lol. Alcohol fueled last night. The name that comes from the movie and what it means was bothering me with probably over thinking it as you seem really cool!

That said Hybrid SERIES would be cool lol
[Nexus 6  Original Android Development] neobuddy89:
Moving forward, it's difficult to publish kernel for different android version.

Last Hydra nightly is stable release for Android 5.0.2 ROMs. It will be soon moved to stable folder and linked in OP.

Hydra 2.0 nightlies begin today and it will *only* support Android 5.1 ROMs.

CM12.1 support will be eventually added.

If you want all cores online when not suspended, use Synapse and change "Min CPUs Online" to 4.

You *must* have android 5.1 bootloader and baseband for stable experience of Hydra 2.0 nightlies.

Hydra_v2.0-[03-16]-[02-30]

* Complete update from lollipop-mr1 release

* MMC driver updates and performance optimizations from CAF

* Added SIO I/O Scheduler

* Updated Intelli Hotplug

* KCal driver update

* Fixed preview build issue with Synapse

* Added underclock/overclock frequencies. Still device will boot and operate within stock frequencies range unless you change from Synapse!

* Misc updates for performance

DL: https://www.androidfilehost.com/?fid=95916177934542149

Cheers!! :cool:
[Nexus 6  Original Android Development] chipstien:
3-14 Hydra bootloops on 3-15 Blissrom. The ROM is still based off 5.0.2. Just a heads up.
[Nexus 6  Original Android Development] jiv101:
I'm running it just fine
[Nexus 6  Original Android Development] chipstien:
Really? I've tried 3 times and it just sits there on the boot animation. Are you using 3-15 build of Bliss?
[Nexus 6  Original Android Development] otisman:
Just asking but [MENTION=4213212]chipstien[/MENTION] you using the build for 5.0 and not the build for 5.1. [MENTION=3795148]neobuddy89[/MENTION] tried latest 5.1 build with euphoria and get system ui fc with rasta pop and chorma no issue at all kernel is spot on!
[Nexus 6  Original Android Development] wrongway213:
Theme chooser in Euphoria, no custom kernels compatible with Euphoria 5.1 right now likely dsmitty said due to SEPolicy.
[Nexus 6  Original Android Development] otisman:
Much alohas wrongway213
[Nexus 6  Original Android Development] dany20mh:
[MENTION=3795148]neobuddy89[/MENTION]

So, I still have this issue that causing my device to freeze at the boot. (SinLess ROM 3.0, Android 5.1, Hydra 3/16)

Everything on the device is clean and there is no other kernel app except synapse.

And if I don't activate the setting (by opening the app and hitting the X mark) it cause device to freeze (no matter screen be on or off - completely freeze)

I don't know what should I do to fix it.
[Nexus 6  Original Android Development] neobuddy89:
I will download Sinless and check. Tested with Stephen 5.1 and Chroma 5.1... It's working fine.

Also, have you updated your bootloader?
[Nexus 6  Original Android Development] neobuddy89:
Euphoria 5.1 got theme chooser? We will update tonight then. :)
[Nexus 6  Original Android Development] otisman:
Much alohas neobuddy89
[Nexus 6  Original Android Development] jiv101:
Sorry I fell asleep while upgrading and woke up to my phone bootlooping. I was off in my blisspop version when I read your post
[Nexus 6  Original Android Development] chipstien:
So you are bootlooping on 3-15 Blisspop then?
[Nexus 6  Original Android Development] jiv101:
Yep
[Nexus 6  Original Android Development] Greedy242:
Had the same problem as [MENTION=955548]neob[/MENTION]uddy
[Nexus 6  Original Android Development] dany20mh:
I installed factory image and wiped everything and then I installed SinLess ROM and your kernel.
[Nexus 6  Original Android Development] freebee269:
Running the 3-16 kernel on stock 5.1 system with 5.1 bootloader and radio and have zero problems. Doing an awesome job with the updates.
[Nexus 6  Original Android Development] jiv101:
Has anybody gotten Hydra to work on blisspop's latest rom update
[Nexus 6  Original Android Development] neobuddy89:
New build uploaded for more ROM support.

Hydra_v2.0-[03-17]-[00-30]

* Support for theme-supported and CM superuser ROMs.

* Init.d support for 5.1 based ROMs.

DL: https://www.androidfilehost.com/?fid=95916177934542564

Tested only with Euphoria ROM; running short of time.

Have to download blisspop now to check.. :rolleyes:

Please report your ROM and kernel status if you tried above build.

Cheeers! :good:

EDIT:

Hydra 2.0 is only for 5.1 ROMs.

You will also require to update bootloader and baseband to latest.
[Nexus 6  Original Android Development] adio201:
Will v.2 work on 5.0.2
[Nexus 6  Original Android Development] neobuddy89:
No.
[Nexus 6  Original Android Development] jiv101:
Yeah 3-14 Hydra doesn't with blisspop 3-15, just bootloops
[Nexus 6  Original Android Development] adio201:
OK. My phone won't go in to deep sleep I'm on pac-rom hydra v1.0 build date 3-10
[Nexus 6  Original Android Development] wrongway213:
No need yet, Bliss is still 5.02
[Nexus 6  Original Android Development] jiv101:
Exactly, still hoping to get that last update. Hopefully bliss comes soon
[Nexus 6  Original Android Development] neobuddy89:
Please use last nightly build of Hydra 1.0 on 5.0.2 ROMs - Hydra_v1.0-[03-14]-[00-21]

That will resolve sleep issue.
[Nexus 6  Original Android Development] adio201:
But if I use that build it brakes camera
[Nexus 6  Original Android Development] daleski75:
Very bizarre issue when playing back music on nokia mix radio beta 2.2 there is no sound and after about 3 or 4 seconds it skips to the next track and this happens for all tracks.

If I flash another kernel such as franco's it works 100%
[Nexus 6  Original Android Development] otisman:
Hey [MENTION=3795148]neobuddy89[/MENTION] is f2fs in your 5.1 kernel tried to convert but wouldn't boot never had issue with your builds so maybe rom? Maybe recovery needs update cause of 5.1 much alohas
[Nexus 6  Original Android Development] neobuddy89:
where to find this app? I don't see this app on play store.
[Nexus 6  Original Android Development] daleski75:
Uploaded it to the thread so you can download the apk to test it.
[Nexus 6  Original Android Development] Lazy79:
Ehm indeed. Have the same with this app and the kernel. I thought it's the app due to beta phase. Didn't try any other kernel because well I like this one :)
[Nexus 6  Original Android Development] freebee269:
This same kind of issue is happening for me with slacker radio. The song starts to play but doesn't have any sound and the timer for the song moves slower than a normal second moves. If I restart the issue goes away but it eventually comes back. I also had this same issue with aol radio. I am on stock 5.1 images with the latest hydra kernel. I'm going to fastboot flash back to stock kernel for a few hours to see if this still happens.
[Nexus 6  Original Android Development] neobuddy89:
Issue confirmed. Will be fixed in next build.
[Nexus 6  Original Android Development] neobuddy89:
New nightly build!

Hydra_v2.0-[03-20]-[03-26]

* Fix kernel issue with compressed audio streams on 5.1 ROMs.

* Linux 3.10.72 update.

* Misc performance and stability updates.

* Added toggle under Misc tab in Synapse to switch between FB notifiers and State notifiers.

DL: https://www.androidfilehost.com/?fid=95916177934543831

Enjoy! :fingers-crossed:
[Nexus 6  Original Android Development] dany20mh:
[MENTION=3795148]neobuddy89[/MENTION]

Just a feedback for FB Notifiers

So last night I install this latest version and head to the MISC setting and enabled FB Notifiers and went to sleep.

During the night I got a few notification, hangout, my work schedule (Hotschedule app), ...

Around the morning I wake up (so 12 to 6) and checked my phone (I saw the notification light on it) and clear the notifications and back to sleep and wake up around 9 and when I checked the battery status I saw during the first time that my left to sleep (12 to 6) it was awake (awake section in the battery status was like solid bar) and the rest was device were in deep sleep (after I clear the notification)

So I'm not sure why is that but this way it won't save any battery for me and cause me more drain, I just wanted to let you know about my experience.

I'm on the Euphoria 1.1 ROM (it's Android 5.1), I have Ambient Display Enabled and I also have Notification Light too.

Thanks again for your work.
[Nexus 6  Original Android Development] neobuddy89:
Its not FB notifiers but Ambient Display keeping awake, I believe. (on some ROMs?)

However,there is no crazy drain even with that on. :)

FB notifiers are for those who use AD.
[Nexus 6  Original Android Development] freebee269:
[MENTION=3795148]neobuddy89[/MENTION]

Great job on the streaming audio fix. I installed the newest kernel last night and went to bed at 100% battery. I woke up 7 hours later at 98% battery. The deep sleep is amazing. I didn't change any notifiers. It's on whatever it selects on first install. Thanks for the fixes. This kernel is now perfect for me.
[Nexus 6  Original Android Development] neobuddy89:
I was waiting for this review. Thanks. :o
[Nexus 6  Original Android Development] Frozt:
Not using this kernel atm. Its very nice though.

Just wanted to stop in and say:

HAIL HYDRA!

For anyone that gets that reference +1
[Nexus 6  Original Android Development] saramon:
Well, I love your work and would really like to use this, but I can't get viper4android to install the driver, it just hangs, on permissive, so I'm not sure what else I can do. It works properly on any other kernel I've tried.
[Nexus 6  Original Android Development] wrongway213:
This is an issue for me too. I know leanKernel implemented this commit to the RAMdisk to make Viper play nice (it works with SELinux enforcing) https://github.com/imoseyon/leanKernel-shamu/commit/31939ce9df31e49215b742ac5d54dc00de600043 - I wonder if something like this would be needed for this kernel to make Viper work normally. It installs, but it takes about 90 seconds of hanging for some reason first.
[Nexus 6  Original Android Development] freebee269:
Have you changed the kernel to permissive?

Never mind I think I read that wrong.
[Nexus 6  Original Android Development] neobuddy89:
V4A link? Will fix in next build if any issue.
[Nexus 6  Original Android Development] wrongway213:
http://xdaforums.com/showthread.php?t=2191223

http://www.mediafire.com/?cnqqdme51qy9ft4

https://github.com/vipersaudio/viper4android_fx
[Nexus 6  Original Android Development] SeVIIn:
I've actually not had any issues with V4A after the kernel is set to permissive on my setup anyway, but I use a zip to install it http://xdaforums.com/nexus-6/themes-apps/viper4android-t2952137