yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] devilsshadow:
Complex or not, we were told it would be fixed in 6.0. It is now 6.0.1 and still no word on what the problem even is. And it's not like it's a small problem. You lose almost half your battery life to this if you rely heavily on mobile data.

Edit: not trying to undermine your work on this. This is one of the best CM builds out there and I've ran with your build for a fair few months before CM13 and it performed amazingly. I just got fed up with no fixes anywhere in sight for the mobile radio active bug so i did the only thing that I could and I went back to a 2 year old OS.
[ONE Android Development] jgcaap:
Hehe I share you feeling. I've been already trying to find a solution, and I've read the code. I don't know where the bug is. If they know and could point it out I would try fix it.
[ONE Android Development] Purerawenergy:
I tried explaining before that I doubt we will ever get battery battery status like we did with kit Kat. The more features and options that keep getting stacked into these OS's the worse or battery life has gotten. And the iPhone? What are they selling for $99? A case with a battery pack inside. No offense but it will NEVER get much better than it is right now, just my opinion. It seems 5.5 remains the biggest that users want these days so what left to do except build a power source onto the phone somehow with something like the nexpaq.

https://www.nexpaq.com/shop/

I'm an optimist but I just don't see of getting better. ?

And I totally agree with all the all the Xposed mod being overkill as they all require juice to prevent other apps from sucking up power.

Tom-alpha
[ONE Android Development] jgcaap:
We'll... Google will fix it. Or xda Will.
[ONE Android Development] Purerawenergy:
Do you honestly believe that? Hasn't each new android version required a little more power? Is it me or hasn't the issue with battery consumption gotten progressively worse with each new climb in the alphabet?

Tom-alpha
[ONE Android Development] jgcaap:
With m battery improved. Just give it time. When there are bugs in my build I also track them right? :p
[ONE Android Development] Purerawenergy:
Absolutely and in not blaming you bro, your builds are amazing. And yes you track em,tag em and bag em. It's human nature to want "what" we want, "when" we want it. It is not your fault, but I do agree the mobile data issue IS something that needs to be solved quickly. But HOW much do we have to press cm or google to get these things fixed? You do amazing things Jorge and no one can blame you brother.

Tom-alpha
[ONE Android Development] jgcaap:
New test build is up. Need tested.
[ONE Android Development] sam_chk:
Hi Jgcaap.. I see 0105 build in test folder.. Any suggestions on what to test...i want to give a shot...

Team which supersu to use betas 2.52or 2.66?
[ONE Android Development] Purerawenergy:
Downloading, thanks.

Tom-alpha
[ONE Android Development] jgcaap:
I understood. But everyone wants this off their backs. :p until then we optimize kernel, rom to be battery friendly. When Google fixes battery issues.... Well have much better battery than normal :)
[ONE Android Development] jgcaap:
Stable build coming. With default art. In case you get tired of test build for some reason.
[ONE Android Development] Purerawenergy:
Just let me know when it's up. I love the feel of this 12.31 build but can't do anything of I'm not on WiFi, which I'm on here at home 24/7. If it goes out or if I leave I can't get to XDA(through Tapatalk) which absolutely sucks.

Tom-alpha
[ONE Android Development] jgcaap:
Rebuilding kernel 2.51 going to flash and debug this properly. Battery will be my goal for the next month.
[ONE Android Development] Bradl79:
twrp 2.8.6.1
[ONE Android Development] jgcaap:
2.51 kernel is slower, because is only for debug. Please do not flash unless requested.
[ONE Android Development] dkv2222:
So to test, I downloaded the latest build and 2.51.

Should I flash or not?
[ONE Android Development] ny15456:
20160105 privacy options?

I upgraded from 0103 to 0105 this morning (wipe dalvik+cashe, dirty upgrade, supersu 2.65, no gapps reinstall). Suddenly found that the privacy guard optionswent back to the old Allowed-Ignored-AlwaysAsk instead of the toggle options in the previous builds. Is this a new change? :confused: Would it be possible to revert to the simpler toggle option? Had to go into each app to set privacy options manually (One of the things i hated doing in cm12).

Also an app related observation - from 0103 version, user dictionary manager seems to load dictionary words successfully but then words are not saved to the dictionary. Worked fine in previous builds upto 1231.

No other problems with the Rom, extremely stable, using as daily driver.:good:
[ONE Android Development] llevin:
Use 2.8.7.0.5 it should solve the issue.

https://www.androidfilehost.com/?fid=24269982087010524

---------- Post added at 09:43 ---------- Previous post was at 09:42 ----------

Just like any recovery - Use fastboot mode.

fastboot install recovery <filename>
[ONE Android Development] TorchaOne:
You can install IMG in twrp too. From install there should be a change possibility from zip to IMG
[ONE Android Development] llevin:
Your screenshots show about 5 hours on time, with 3:20 sot - That's not abysmal at all. Normal smartphone usage profiles that are used by OEMs while designing our devices, are assuming maybe 20% screen on time. You are at ~66%. In an average usage pattern you would reach over 20 hours on a full charge.

No optimization (greenify, etc.) will help much when screen is on and CPU is working hard. CPU, screen and radios just take a lot of juice when they are active. There is no way around it. You can use under voltage and under clocking to keep the CPU from overheating and over-consuming, but the physics remains ever true - active devices need power. (an iPhone would not last longer on such intensive use).

Most of the optimization you specified are intended to optimize nap time - reduce the wakelocks and background activity and get the CPU to wake less. They have little to none effect on a fully awake CPU.

Frankly, I suspect having 5 battery optimizers working simultaneously probably creates more problems and uses more power than having none.

---------- Post added at 10:07 ---------- Previous post was at 10:01 ----------

I was not aware of that. Good to know.

Thanks!
[ONE Android Development] sam_chk:
Hi.. I flashed today 0105 from test folder and found rom stable, fast and in last 3 hours or so battery life seems to be good.

I do see small enhancement required for indian users. Based on OP FIRMWARE signal strength for me was bad.,so i flashed c7-00013 firmware for bacon from teamsek page. Seems to be just a change in modem to 13 and signal at 3g is back to normal. Hope ot might help someone. Rest exploring as i m not a power user.
[ONE Android Development] jgcaap:
No :p
[ONE Android Development] :
It goes without saying that I - and many other people - appreciate the work you're putting into this to find a solution and optimize your ROM further.

Okay, I'm currently running the 01/02 nightly, with the stock CM kernel you asked me to use. That's the only variable I've changed, because I want to compare whether the kernel is, in fact, the issue.

If this doesn't work, I'll try a clean flash with no power-saving apps installed. This included Greenify, Amplify, Naptime, Servicely, and PowerNap. After that, I'll test with no Xposed, because I've become quite dependent on certain modules that I would like to not disable, but perhaps that is the culprit, though I doubt it.

With regard to the latest test builds, other people will have to test; I'm currently keeping the 01/02 nightly to keep things as consistent as I can.

A bug I'd like to report, however: the "Enable by Default" option in CM Privacy Guard hasn't been working on this ROM, can you look into that if it's not too much work?

Also, granted I haven't used the new kernel much, but it doesn't seem to have any difference in terms of smoothness as compared to your kernel.
[ONE Android Development] TorchaOne:
I agree, I even think they just make phone worse, much worse. They consume battery too :) Anyway, I don't ever use any of those and with official+boeffla+zzmoove battery plus I got 0.8-1%/h sleep consumption, with this jgcaaps 0401 I got 0.6-0.7%/h and I have Facebook + chat running, hangouts etc running at background. I tried those sw during 12.1 time when I got 2-4% idle consumption and either I dont know how they work but I saved 1% but phone came slower and annoying to use.

Thats why for now, jgcaap is a keeper for sure :)
[ONE Android Development] Nicolas_g134:
I had the same obsession you have, if I may call it that, I too had installed all these power saving apps with their xposed modules. But when I threw all these apps overboard, my battery life became a lot better and my user experience a whole lot better. My phone even sleeps better now.... So I suggest you try this too :) I don't have the facebook app installed, but I do have Chrome and FB Messenger and I had more than 6 hrs SOT yesterday with this ROM, sometimes on wifi and sometimes on mobile data :) good luck!
[ONE Android Development] :
I disagree. I believe 3:20 is a horrible time, seeing as this phone has a battery that was touted as the best for 2014. But that's not much as a frame of reference, so if we talk numbers, 3000mAh is a LARGE battery, no way to slice it. This battery is capable of much more, the processor doesn't have any overheating issues, and is a very good chip in terms of power management. Heck, it's only a generation or so old. The fact is that the battery should not be draining as much under regular, low-power usage, much less gaming use. And as I mentioned earlier, my sleep is a contributing factor to the drain, but not a significant one; the main issue lies with usage while the screen is on. With regards to how OEMs design power profiles - we at XDA know they aren't always optimized. They announce such conservative results to err on the side of caution, whereas we at xda know there's much more to that.

I do agree, however, that those power saving apps have no effect when the screen is on, with the exception of Greenify. Greenify puts apps in hibernation and doesn't necessarily wake them up when you begin using your phone - only if it wakes itself up, or if you explicitly launch it. But with the rest, I do agree. Which is why we're trying to optimize the kernel to suck less juice, while maintaining - or improving - stability and smoothness.

Without using these apps I was having massive wakelocks not only from Facebook - which I'd rather not uninstall but will if this is the main culprit, but, disappointingly, Google Play Services. Turning Location to Device Only is not a solution, because apart from it yielding no discernible difference to my battery life, prevents Google Now from functioning properly. IMO, I should not have to turn down features I use to get a phone that lasts longer: that is not a solution, but a stubbornness to admit there is a problem. At least with Apple, their own App Store or whatever services they have that make the phone run don't have issues like these.
[ONE Android Development] xdavidc:
Latest recommendation is 2.52 but ROM as been flashing it lately so there's no need now. I have flashed 2.66 once and the apps I use had no problems.
[ONE Android Development] :
This is the next step. I'm trying out the stock CM kernel today, and if that doesn't help, I'm trying a clean flash of the current ROM without these apps installed. The problem I have had with that is that it works one day, but the next, the battery drain will be back.
[ONE Android Development] jgcaap:
How it improved with 2.51? There are things I still want to try revert.

2.51 is currently on debug mode. Activated alot debug options to see info.

I see the phone sleeping very well. I'm currently trying to find when the phone is stuck at a frequency.

My focus this month is battery. :)
[ONE Android Development] :
It seems as though battery life has improved with 3.51, but it's too early to tell. 100-80 always lasts quite long for me. What has made a difference, however, is that it sleeps better. When it's supposed to be sleeping, it does, actually, sleep.

Edit: I read something about SuperSU 2.66 solving sleep issues on MM or something? Have you seen that?
[ONE Android Development] jgcaap:
Let it become stable and I'll update. :) no need to run. When something works, don't change.
[ONE Android Development] :
True, there is that. Don't fix it if it ain't broke. :D
[ONE Android Development] jgcaap:
And remember. This will need patience.

I try to keep the structure most stock like for two Reasons, one is stability. Two, to not blow the kernel structure.

Slowly we'll find and improve battery.

There are still some tests I wish to run. If you have the patience will be cool :) I'm currently on 2.51 with you, the difference is that I enabled debugging options.
[ONE Android Development] :
Tbh this Marshmallow ROM has worked the best for me, battery life included. Since the next iteration of Google's OS isn't due until the end of this year, it looks like I'm here to stay, at least for now.

For purposes of brevity, this is my standardized setup:

02/01 nightly

Slim GApps 12/25

Xposed framework v78

V4A 2.3.4.0 on Super Quality, no convolver

Facebook v58.0.0.28.70, Messenger v52.0.0.19.66, Amplify v3.3.4, PowerNap v0.7, Greenify v2.7.1 with Donation Package (and most aggressive settings applied, those for Xposed included), GPlay Store v5.12.10, GPlay Services v8.4.89.

Current changes:

Kernel upgraded (?) to v3.51.
[ONE Android Development] Zombie Dude:
Flashed TWRP 2.8.7.0 and now I get a message that says "Error 7" I'm really confused as to why I'm having trouble flashing all of the sudden.
[ONE Android Development] jgcaap:
The secret for battery is not xposed. In the past yes. But things have changed for a while. I usually get between 6 and 8 hours SOT. Since cortex and 2 other commits I have in mind battery worsted. So we are going to slowly test and see which one actually makes a difference.
[ONE Android Development] nosphor:
Don't forget to update to the v79 of xposed ;)
[ONE Android Development] jgcaap:
After 1 cycle, with Ukm turn off arch power. And keep testing.

I'll be testing something else.
[ONE Android Development] xdavidc:
You should use 2.8.6.0 official, the one in OP or 2.8.7.0.5 https://www.androidfilehost.com/?fid=24269982087010524
[ONE Android Development] Zombie Dude:
I was recommend to flash the last one which the file did read as 2.8.7.0.5 but shows up in the TWRP app without the .5 at the end.
[ONE Android Development] Bobbi lim:
The recommended 2.8.7.0.5 is actually materialized TWRP. A quick google search will lead you to the correct thread...
[ONE Android Development] lampshade90:
Hey jgcaap,

im following this thread for a while and have seen your progress. But i mentioned that you didn't post a changelog some builds ago, of course you're still testing, but as some people say the 31/12 build fits them best im curious what is changed till than. I can understand if its too much work to sum up every build and at least only a few people are interested. But i just wanted to point out that there are maybe some people beside me, who would like to know what changes are made and find their best combination.

I know that youre saying what is changed somewhere in this thread, but maybe its better to have an overview...

Maybe you would benefit from this too, as people could say exactly what changes made an impact on performance and battery, also they could change some parts on their own.

Just my 2 cents, if its too much work, or youre just not interested, im totally fine
[ONE Android Development] Zombie Dude:
That appears to be the one I have downloaded.
[ONE Android Development] jgcaap:
Go to about and changelog.

I'll post the extras compared to cm later. :)
[ONE Android Development] TorchaOne:
error 7 means you are trying to install wrong ROM, incompatible to your device. Scary. I cant test it now, and I trust so much 2.8.6.0.6. I would use new version only in encrypted device.
[ONE Android Development] :
Is UKM+Synapse supported on this kernel?

Currently my testing process is just changing the kernel to 3.51. After that, I'll clean-flash and install everything except for the power-saving apps I have. After that, I'll try without Xposed. After that, I'll give arch power off a shot. It's going to be a long week.
[ONE Android Development] superiscch:
Am I looking wrong or is 'double tap to sleep on lockscreen' not available?

I read a lot of you are happy with the 0501 build, but are you using the normal build or test build? :)

[MENTION=2040569]jgcaap[/MENTION]: may I ask why you don't include your custom kernel in you own rom? :)
[ONE Android Development] TorchaOne:
I see it in display settings but it do not seem to work atm. and not available through synapse.

---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------

yeps, OP has link to special version for newkernel (newkernel thread) https://basketbuild.com/filedl/devs?dev=jgcaap&dl=jgcaap/UKM_v3.8.1.2_Special_Ed.zip
[ONE Android Development] jgcaap:
Yes. i'll start improving UKM also. We need to start having serious control of the kernel :)
[ONE Android Development] superiscch:
I guess this is on the newer build, going to update this afternoon
[ONE Android Development] :
That's interesting. All things considered, if UKM+Synapse works on this, I wonder how optimized kernel profiles will work on your kernel?

I'm currently testing quite a few different stock setups, can someone test out Stylo King's profile on [MENTION=2040569]jgcaap[/MENTION]'s kernel and see if it works?
[ONE Android Development] BigMacca:
Just for info [MENTION=2040569]jgcaap[/MENTION]

I've been running the 04/01 test build and feels as good as the late December build to me.

Cheers

Macca
[ONE Android Development] jgcaap:
New UKM is up : http://download.jgcaap.xyz/files/kernel/UKM-NewKernel.zip

Have Fun
[ONE Android Development] TorchaOne:
Flash over old one or uninstall first and flash?
[ONE Android Development] tacohell:
I have been a bit behind as I have been swamped with work and not paying too much attention to this thread.

Is this (CM13/6.0.1) version now ready for daily driver (I am still on 12.1 - last one of Dec. builds and it is super stable and ultimate battery life)?

Thanks
[ONE Android Development] jgcaap:
Battery..
[ONE Android Development] jgcaap:
And already done 3 reboots to flash stuff...
[ONE Android Development] redesign93:
noob question

i am on 31st dec

going to clean flash 5.1.16

what is UKM ?

do i flash kernel and then flash UKM ??
[ONE Android Development] akash7071:
where can i find the cm12.1 version of this rom?
[ONE Android Development] superiscch:
I only see double tap status to sleep bar which works fine, but no double tap to sleep on lockscreen.
[ONE Android Development] Purerawenergy:
There's an app in the Play Store called TWRP(root) that will allow you to flash any version of TWRP's recoveries directly from within the app. I know for most flashing a recovery from an "app" goes against the grain, but with all the issues successfully flashing firmware over the past several months, this will make it much easier because it has every version listed inside the app, hopefully making this process a bit easier. Here's some screenshots.

Tom-alpha
[ONE Android Development] xdavidc:
Is it today's build?
[ONE Android Development] TorchaOne:
There is new ukm but just apply from settings/display and it works, did not know u have to 2click upper bar or what that is...

---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------

Kernel manager and u need application like synapse then to check and modify attributes. Rom + gapps + ukm.
[ONE Android Development] superiscch:
Double tap on status bar works, double tap on lockscreen isn't available here... Nor in Settings/display nor in Synapse
[ONE Android Development] dkv2222:
Kernel 3.51?
[ONE Android Development] :
[MENTION=2040569]jgcaap[/MENTION]

Attached is the usage data for today, from 100%-50%.

Observations: SOT is 2 hours for loss of 50% battery. Total usage including standby time is about 8 hours. Extrapolated, that would yield 4 hours SOT over 16 hours. The slight difference in SOT as compared to yesterday's results is likely due to me not using Chrome throughout the duration of the test.

Verdict: Cortex A15 code modifications (or lack thereof) yields virtually no difference. Testing continues.

For my next test (tomorrow), my phone will be set up as follows:

02/01 nightly (clean flash)

Stock kernel provided with ROM

Slim GApps 12/25

Xposed framework v78

V4A 2.3.4.0 on Super Quality, no convolver

AC Display Off, DT2W On.

Facebook v58.0.0.28.70, Messenger v52.0.0.19.66, Amplify v3.3.4, PowerNap v0.7, Greenify v2.7.1 with Donation Package (and most aggressive settings applied, those for Xposed included), GPlay Store v5.12.10, GPlay Services v8.4.89.

Variables changed with respect to control conditions:

Amplify, PowerNap, Greenify, and Naptime disabled
[ONE Android Development] jgcaap:
building 3.51 kernel without logs for users to try.

It seems Cortex A15 optimizations create battery drains for us. Disabled.

Lets see if improves kernel use on battery. Cheers. :)
[ONE Android Development] jgcaap:
Change of test. You'll redownload 2.51 beta which has debugging mode on and see if improves battery for you might be odd but i've been studying the kernel, and there are some debugging options which are not related to messages but to formulas, which problably might be needed on other parts. If battery imrproves let me know and i'll correct my mistake. I actually found an improved level of battery with this option on.
[ONE Android Development] dkv2222:
Would love to test :D
[ONE Android Development] jgcaap:
i'm going to test 3.52-beta, please do not download that one. :)
[ONE Android Development] :
2.51? Don't you mean 3.51?

Also, debugging mode improves battery life? From what I know of app dev, debugging usually taxes the processor and battery.
[ONE Android Development] TorchaOne:
My bad, never even seen such feature :) blind as a bat. Did boeffla has it in his manager? Or somewhere... I always disable all double tap to sleep etc cos I use flip cover, no need.
[ONE Android Development] Blac Caesar:
[MENTION=2040569]jgcaap[/MENTION] ...been running 04/01 beta 3.51 kernel; I know it's only been a short while, but I can say that battery seems to have improved over 01/01 v3.50. Oh, I'm on 05/01 test build as well btw. I'll try UKM-Synapse in like a day to give the latest flash time to chill out so I can see how it really acts lol. Definitely glad to see a dev that's devoted to improving his builds and kernel work for the community. Keep up the awesome work! :victory:
[ONE Android Development] jgcaap:
yes :P sorry
[ONE Android Development] jgcaap:
yes. but if the code has verifiers of the messages in order to work ... can create battery drains. :) So yes... We take a step back in order to take 2 forward later. I didn't study on detail each option, as you can imagine 1GB of kernel code is very hard for me to study it in a day, specially when i'm on exams. Since this is harmless we'll do test, as is faster to take conclusions.

I'm exploring android kernel MSM, and I've been doing already many discoveries. But is possible to have messed up when i turned off all debugging. Possibly we need to keep some of it on. So in order to find that quickly since I've tested 2.51-beta and found an improved battery, you'l test the one I've been using today.

While I test again debugging mode + cortex A15 again.

The rest will test without cortex in order to compare.

If I find battery had improved and you too. Then the answer to our battery issues is inside of some debug code which has to be included on kernel.

After we find out... :) We'll have a good balance of battery+performance.
[ONE Android Development] :
Alright, that makes sense. What's the link to the one you want me to test? There's a lot of different kernels in your kernels folder.