[ROM] [COMMUNITY][MM 6.0.1] OctOS (Z00A) - Updated September 15, 2016
Another build, compiled from source. But before I get too far...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, this is a build of OctOS, using the device tree, kernel and advice from @jrior001 and @crpalmer.
NOTICE:
Final build for the LP bootloader is here.
As work with Nougat begins, I will need to switch over to the MM bootloader. I won't be going back (downgrading) to check builds using the old bootloader. For OctOS, as that is MM anyway, I can begin special builds (reliant on the MM bootloader) once I become established. For Carbon LP, it means the end of the road.
The September Android Security Bulletin arrived for MM a few days ago. I have cranked out the final build, tested, and posted it. Device-identity-wise, the only difference between this build and the one previous is the fix to the "off-path TCP" exploit. The ASB had other fixes, but to the ROM instead. Plus, there were sweet enhancements to the OctOS UI since the last build.
Thank you for all the support, and if it applies to you yet, check out the MM build using the latest bootloader. Cheers.
WHAT WORKS:
Powers on
Phone calls tested (SIM 1)
Mobile data
Torch
Camera
MTP (Linux users be sure you are using libmtp version 1.1.10 - or greater)
Charges
Play Store
WHAT DOES NOT WORK:
M-Bootloader edition(s) do not come with SuperSU, due to (I suppose) the BL's expectations of a signed boot image (that the SuperSU install otherwise screws up).
GPS and NFC still to test.
As this ROM shares the same device tree as CM, (and a lot of projects) this will share the same flaws. Otherwise, please tell me.
DOWNLOAD:
via AndroidFileHost
For the L Bootloader (if your stock remains 5.0)
For the M Bootloader (if you took the 6.0 upgrade)
GAPPS:
OpenGApps
INSTRUCTIONS:
Prerequisites: An unlocked boot loader and TWRP 3.x installed
Download ROM above, and a GApps package
Save/push files to your (External) SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional, but highly recommended)
Wipe cache and data/factory reset (unless updating from previous OctOS version)
Install ROM and GApps
Wipe Dalvik cache
Reboot
Enjoy!
CREDITS:
jrior001
crpalmer
CyanogenMod
OctOS (incl. Don Kaczmarek)
XDA:DevDB Information
[ROM] [COMMUNITY][MM 6.0.1] OctOS (Z00A), ROM for the Asus ZenFone 2
Contributors
OfficerJimLahey
Source Code: https://github.com/carbon-z00a
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Beta Release Date: 2016-06-11
Created 2016-06-11
Last Updated 2016-09-15
Other Info...
For those following along....
Project GitHub: https://github.com/carbon-z00a
Branches for L Boot Loader:
oct-mm (Device Tree)
cm-13.0 (All other identity projects)
Branches for M Boot Loader:
oct-mm-M (Device Tree)
cm-13.0-M (All other identity projects)
LOCAL MANIFEST:
Currently a part of the Community builds section of OctOS...no local manifest required!
CHERRY PICK(S):
Code:
None at this time.
Make a new folder for and then initialize the build tree:
Code:
mkdir octos-mm
cd octos-mm
repo init -u https://github.com/Team-OctOS/platform_manifest.git -b oct-mm && repo sync
Complete all the normal steps (". build/envsetup.sh && brunch") at this point.
CHANGE LOG:
Besides the project git hub...
CyanogenMod upstream
ZF2-BringUp-Related Commits
AOSP upstream
Good job.Build for Z008?
WELCOME BACK!
Sent from my ASUS_Z00A using XDA Labs
Thanks Reserved
Russiamen said:
Good job.Build for Z008?
Click to expand...
Click to collapse
Thanks.
I don't have a Z008, so not comfortable with building that one.
Thank you and welcome back
This ROM is not affected by the network bug?
Inviato dal mio ASUS_Z00A utilizzando Tapatalk
Nice. So what features does this rom have? Can't find a list on their site.
Sent from my ASUS_Z00A using Tapatalk
salvoza96 said:
This ROM is not affected by the network bug?
Click to expand...
Click to collapse
Mean like Wi-Fi dropping (and hesitant - although it gets there - to reconnect)? I saw that happen a little bit, but it does that for another device of mine as well (across a couple 6.0 ROMs), so I figure it is an AOSP thing waiting to be squashed.
kenbo111 said:
Nice. So what features does this rom have? Can't find a list on their site.
Click to expand...
Click to collapse
Quoted from the Moto G 2015 OctOS thread:
FEATURES
Android 6.0.1
Optimized for the best efficiency (battery and performance)
Smooth as hell!!
Live Display
Ambient Display
Separate customization menu, which can be hidden
Omniswitch
Clear-all recents
Immersive recents
Status bar clock/date customization (format, colour, etc)
Battery icon customization
Status Bar Header Image
QS Tiles customization
App Circle Bar
Buttons customization
Volume Steps
Gesture Anywhere
Kernel Auditor
Lock Screen customization
Toast Icon
Power menu customization
SuperSU
Privacy Guard
Status Bar Greeting
Battery Bar
Traffic Indicator
Theme Engine
More to come!
Click to expand...
Click to collapse
Hope this helps.
So the battery life on this will be good you reckon? I am really just looking for a ROM to handle my all day 4G use and just whatsapp in general. Do you reckon i can get about maybe 3/4 hours of SOT while having 4G on?
aosp based?
abner albuquerque said:
aosp based?
Click to expand...
Click to collapse
Yes, but it runs CyanogenMod 13's Fig API.
great, big thanx
EdgeVibration said:
So the battery life on this will be good you reckon? I am really just looking for a ROM to handle my all day 4G use and just whatsapp in general. Do you reckon i can get about maybe 3/4 hours of SOT while having 4G on?
Click to expand...
Click to collapse
As with all things, your mileage may vary. With that out the way...
Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.
Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.
Hope this helps.
OfficerJimLahey said:
As with all things, your mileage may vary. With that out the way...
Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.
Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.
Hope this helps.
Click to expand...
Click to collapse
Hey thanks a lot for that. I have been using the ROM and I have to say it really is amazing. I don't really have any bugs to report, everything is working nice and smooth. Battery does last quite long, maybe gets me through the day with moderate use. I even use FlareM 17.6 and I have optimized it. I get around 4 hours while on heavy use + 4G so yeah, great ROM.
OfficerJimLahey said:
As with all things, your mileage may vary. With that out the way...
Just booted from a fully charged state (without SIM), and let it drop to 99% (since booting puts a little more load, and untracked SOT in the test). I then timed, with screen on (brightness around 60%), how long it would take to go from 99% to 98%. Took a little over three minutes, by then the phone estimated I had five hours of battery life left (as a result of having the screen always on). Three minutes for a percent also works out to five hours for 100% of battery life. Toss in 4G in a good service area, some idle (screen off) time, and a day's use for 4 hour SOT sounds about right.
Why I mentioned earlier YMMV: My ZF2 has been used as a daily driver (light to moderate daily usage), until very recently, for almost a year (I believe it was this day last year that I purchased it). For the first 8 months, aside from being plugged in for adb/fastboot purposes (or a charge after a lot of work done in TWRP), I would charge it every second day. For the last 4 months, I needed to charge it at least some amount on a daily basis. So my battery is starting to show some wear after 240 to 250 (or more) charges (it is noted on third party battery packaging that the product will show their wear after 300 charges - I imagine the real deal is not all that different). Contrast this to my new ZF2 Laser which on 5.0.2 stock gives me two days (Saturday morning to Sunday evening) from 100% to 56% (so I could have squeezed another day out of it) though I did not check the SOT.
Hope this helps.
Click to expand...
Click to collapse
i wish my analytical recall was this good. i guess it's one thing if you always meant to keep track and had it in your head to keep of your charging schedule but it sounds like you were just considering it in real time given the question, haha.
my life would likely be very different if i could track reach a year back and consider with clarity my actions
Sent from my ASUS_Z00A using XDA Labs
Nice ROM. Just want to let you know that GPS works great on my end (so no need to test it). Not sure about NFC however as I don't use it myself.
Everything working for me, calls, 4G,Wifi,SOT is 4hrs with my usage,GPS working, ALARM(thank goodness) is working. Thanks for the effort. I wonder if this Zenfone 2 can break anymore battery barriers compared to using other ROMs. Nonethless great job. Will be using this as daily driver
P.S: Previously used RR, CM Nightly, AOKP, BeanStalk(recently changed to OctOS).
Not using GApps, stock kernel
ROM works great. GPS works!
One issue: when looking at photos or a pdf the screen occasionally goes black. This lasts for 3-8 seconds before it comes back and I can interact.
Disabling hardware overlays in Developer Options seems to fix the problem, but it eats more battery.
Any better ideas?
Related
Ok...this is going to sound completely outrageous! It seems outrageous to me even I have never had this good of battery consumption ever! The phone was purchased 16/08/10 and has retained the standard battery all this time and had various Samsung ROMs on it. Mostly DarkyROMs that have improved battery quite considerably. It currently has its first stable ROM of ICS since I started flashing ICS from just prior to RC1. The ROM is a bit of a mix-matched frankenstein build of a ROM by me originated from MyICS and OneCosmis RC3.1. I have recently experienced allot of issues (including very poor battery drain) prior to this last flash and so have many of my users...actually most jumping **** (and I don't blame them).
My last ROM flash seemed to stable and go through perfectly, I was running with my own 2.0.1 and was about to release this ROM (that I'm currently on from a system dump) as a 2.2.0 version update for everyone else.....however I have held back because of the announcement of RC4.....so any of the improvements I haven't released. The install procedure backs up battery stats so as not to need re-calibration and has done so for the last 3 or 4 install. I am running the latest platypus kernel made for RC4 though
Anyway the last time I had my phone on any decent charge 22hours ago. It's currently 10.40pm EST and phone went on charge about 12.30pm lastnight. Since then I have had data left on (something I wouldn't normally do...I was used to renaming APN prior to ICS) and wifi on* (granted I have latest Juice defender ultimate)
*set to trained locations to auto-on within 250m of known wifi access point and disable 3G when wifi connected
I have gone the whole day today, with a small amount of internet (damn genie widget gets me every time with cool interesting things flashing up on the screen lol) and moderate phone usage; texting and a hand full of 10-15min phone calls....nothing out of the ordinary.
I plugged the phone to USB to transfer some things from work and it was plugged in for approximately 15-20seconds. I use multi-mount SD card app (I have included the lite version in my ROM) and allows for fast transactions and also to be able to use the phone whilst connected etc (read up about it). And I did the same here at home to transfer the things off again. It has remained sitting beside my PC untouched (unusual cause I like to fiddle) for the last 3 hours...and decided to pick it up and glaced at the battery 90%. Ok so I waited another hour and glanced again and STILL 90%.
Is there something weird going on here that I should know about? My phone has never been this good even if I left it completely on standby and in flight mode it would have eaten more than that! It seems almost stupidly impossible.
Fill me in on your take of this situation? Happy to do a complete system dump to try figure this sh!t out cause I made so many mods last ROM update I wouldn't know which one is contributing or if all or none?
edit: included more information
It's now 2:20am I am going to bed. My phone is 86%
A drop of only 4% in nearly 4hours. 1% per hour is not too bad
How do you handle synchronization, and why kind of tweaks do you perform with juicedefender?
heh i know what you mean
Im using as well icssgs rc4 (pulled) for 3 days, and right now i have 10% left after 29 hours of using my phone as wifi, downloading, sync, calls, sms and some music, all i can say is that rc4 +platypus kernel is the beast for the battery. my phone never lasted for such a long time, even on rc3.1 it used to die after 18 hours of being idle.
Reporting
7am 77%
10am 62%
10.55am - poor signal and market prompted to download an update for LinkedIn battery has plumited to 23%
36hours use and still 23% battery is pretty good. At least the resil
I will be making a deodexed version of RC4 sometime soon with a few extra bonuses ....however it won't be all that special as I have been giving away my secrets everywhere on the forum to help others on any ROM (not just my own) so anything included in my next release will be old news lol
Juice defender? Tweaks? I am not sure what you mean? You mean what are my settings?
Ok...wtf? Battery is climbing back up again now? That is something that has never happened before! Im on 26% again
realy ? ))
Offfical time of death 4.34pm EST. approximately 40hours after full charge. I am stoked with that.
Edit: I will be making a donation to Platypus Kernel right now
Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.
dimon28 said:
Can you tell which rom you had before flashing rc4 and another question are you experiencing any other problems with the rom like sd problems because im considering to go rc4 too.
Click to expand...
Click to collapse
I am still running RC3.1, I am just using the RC4 kernel
I am in the process of developing my own RC4 ROM based off this RC3.1 (my own version of it anyway) that is the first ROM I have that is stable. All versions of my ROMs prior to this have been very unstable. ROM is still odexed so that will be my first point of call and then repackage and get it up and running.
I am in the process of compiling some java code for wifi calling on vibrant though so I am too busy to even start on my ROM
Q&A for [ROM] [Unofficial] | AOSPA 4+ | Weekly Update
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Unofficial] | AOSPA 4+ | Weekly Update. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery charging very slowly
I really appreciate the developer of this thread for giving us weekly updates on AOSPA :good:
The only problem i have apart from random reboots is that the battery charges very slowly and discharges real quick. :crying:
As I have observed in comparison to miui v6 is that in miui v6 the battery would charge up to 5% in just 5:30 to 6 mins, instead in this AOSPA ROM the battery takes over 10 mins to charge up to 3%. I don't know if this can be resolved or not but if it is possible to fix this in the coming updates it would be really appreciated.
PS: I am running the latest build of AOSPA i.e, pa_cancro-4.6-BETA5-20141102
Thanking the Developer for providing this awesome ROM
MAC Address Changes On Reboot?
Every time I reboot my MAC address changes, this is very annoying for me and happens on every custom rom that I have tried on the mi3(cancro), this is quite tiresome as my dad uses MAC address filtering and it is impossible to connect to wi-fi without constantly having to change the accepted MAC addresses. If you can fix this or at least give me a tip I would be extremely grateful!! Thanks for reading, Stas Domanski.
akshayAXE said:
I really appreciate the developer of this thread for giving us weekly updates on AOSPA :good:
The only problem i have apart from random reboots is that the battery charges very slowly and discharges real quick. :crying:
As I have observed in comparison to miui v6 is that in miui v6 the battery would charge up to 5% in just 5:30 to 6 mins, instead in this AOSPA ROM the battery takes over 10 mins to charge up to 3%. I don't know if this can be resolved or not but if it is possible to fix this in the coming updates it would be really appreciated.
PS: I am running the latest build of AOSPA i.e, pa_cancro-4.6-BETA5-20141102
Thanking the Developer for providing this awesome ROM
Click to expand...
Click to collapse
Didn't notice this as I always charge at night. About battery draining need wakelock stats for that. Average my phone can last day with no deep sleep, 4hrs SOT.
universalfox said:
Every time I reboot my MAC address changes, this is very annoying for me and happens on every custom rom that I have tried on the mi3(cancro), this is quite tiresome as my dad uses MAC address filtering and it is impossible to connect to wi-fi without constantly having to change the accepted MAC addresses. If you can fix this or at least give me a tip I would be extremely grateful!! Thanks for reading, Stas Domanski.
Click to expand...
Click to collapse
I'll take a fix from Armani device if it can be use with ours. Will post a new build when ready. Hope you can report back if it work.
audahadi said:
Didn't notice this as I always charge at night. About battery draining need wakelock stats for that. Average my phone can last day with no deep sleep, 4hrs SOT.
I'll take a fix from Armani device if it can be use with ours. Will post a new build when ready. Hope you can report back if it work.
Click to expand...
Click to collapse
I really appreciate if you can fix the Wifi MAC address bug, Thanks for the continued development
audahadi said:
Didn't notice this as I always charge at night. About battery draining need wakelock stats for that. Average my phone can last day with no deep sleep, 4hrs SOT.
My battery drains quick as i have disabled device deep sleep, because of the random reboot problem.
Is there any way you can resolve the slow charging issue?
Click to expand...
Click to collapse
Don't know for sure..regularly my phone full charge 3-4 hrs..even on MIUI..is it right? There a lot changes I'm doing locally in my build to test stuff.
audahadi said:
Don't know for sure..regularly my phone full charge 3-4 hrs..even on MIUI..is it right? There a lot changes I'm doing locally in my build to test stuff.
Click to expand...
Click to collapse
in MIUI in could achieve a complete charge from 0 to 100 in less than 2hrs.
But in AOSPA it takes almost 6hrs for complete charge, so instead of putting it to charge while the os is booted, I tend to turn off the device and then charge my battery and then the charging rate matches to that in MIUI v6
This is not a hassle free process as I am unable to use my device when I put it to charge. I have to compromise between keeping my device on and faster charging rate.
akshayAXE said:
in MIUI in could achieve a complete charge from 0 to 100 in less than 2hrs.
But in AOSPA it takes almost 6hrs for complete charge, so instead of putting it to charge while the os is booted, I tend to turn off the device and then charge my battery and then the charging rate matches to that in MIUI v6
This is not a hassle free process as I am unable to use my device when I put it to charge. I have to compromise between keeping my device on and faster charging rate.
Click to expand...
Click to collapse
This mean fastcharge thingy didn't work properly..hmmm...
audahadi said:
This mean fastcharge thingy didn't work properly..hmmm...
Click to expand...
Click to collapse
Sorry, @audahadi I didn't get by what you meant in your reply and you did not even mention weather or not you could solve this issue.
Also i can confirm that Mac address changes every time the phone reboots.
Fastcharge seem not working..
audahadi said:
Fastcharge seem not working..
Click to expand...
Click to collapse
@audahadi What is meant by Fastcharge??
akshayAXE said:
@audahadi What is meant by Fastcharge??
Click to expand...
Click to collapse
Most new QUALCOMM base chipset/board has this (if I'm not wrong). Simple say...quick charging like OPPO Find7 has..but not as fast as that. More quickly than conventional charging.
audahadi said:
Most new QUALCOMM base chipset/board has this (if I'm not wrong). Simple say...quick charging like OPPO Find7 has..but not as fast as that. More quickly than conventional charging.
Click to expand...
Click to collapse
Thank you for the explanation. So can it be corrected in AOSPA?
akshayAXE said:
Thank you for the explanation. So can it be corrected in AOSPA?
Click to expand...
Click to collapse
Don't know...we'll see...[emoji13]
universalfox said:
Every time I reboot my MAC address changes, this is very annoying for me and happens on every custom rom that I have tried on the mi3(cancro), this is quite tiresome as my dad uses MAC address filtering and it is impossible to connect to wi-fi without constantly having to change the accepted MAC addresses. If you can fix this or at least give me a tip I would be extremely grateful!! Thanks for reading, Stas Domanski.
Click to expand...
Click to collapse
Uploading new build..approx ~1hrs...please confirm if MAC address stick after boot.
Screen flickering
The screen flickers when you hold the status bar midway and during the recent app switcher. It looks ugly.
El-Chupacake said:
The screen flickers when you hold the status bar midway and during the recent app switcher. It looks ugly.
Click to expand...
Click to collapse
Can't do much..PA stop on kitkat development..move on to lolipop know..seem no more bugfix from PA.
Thank you sooooooo much, just dirty flashed from AOSP and the Wi-Fi works with no problems!!
Sent from my MI 3W
audahadi said:
Can't do much..PA stop on kitkat development..move on to lolipop know..seem no more bugfix from PA.
Click to expand...
Click to collapse
Carbon Build 4 has fixed it. I love your rom and hence I want you to do the same.
Is the battery life on the Android P Beta 2 bad, even for a Dev Preview version? I tried it but even after two days I could literally watch the battery percentage drop down rapidly as I used the phone.
Which is a shame because the beta ROM felt smooth when compared to the stock 8.1.0 ROM.
If you use the ADB command in the P thread battery life is bloody excellent, I've been running it for abiut 5 days now after reverting back first time and my battery life is possibly even better.
This is from the other thread.
K3DAR7 posted.
i can confirm, that me previous problem (first post, more info) with battery drain have sure fixed by "adb shell pm clear com.evenwell.powersaving.g3"
after this, during two days, phone is not warm when no use(an also not if used(i not gaming)) and no cpu eating, battery life: 2d2h from charge, SoT ~6.5h, remained 15% (all time enabled Wifi(mostly on range/connected), 2xSIM, BT(not used, only pair with SBC for SmartLock), GPS)
also i must mentioned, that DP2rev2 is really stable, fast, smooth and (for me) working all apps i use before with Oreo, camera now have option of 2x zoom, bluetooth headset work (for music and for (gsm)phone call) and is (for me) usable as daily driver...
BigD18t said:
If you use the ADB command in the P thread battery life is bloody excellent, I've been running it for abiut 5 days now after reverting back first time and my battery life is possibly even better.
This is from the other thread.
K3DAR7 posted.
i can confirm, that me previous problem (first post, more info) with battery drain have sure fixed by "adb shell pm clear com.evenwell.powersaving.g3"
after this, during two days, phone is not warm when no use(an also not if used(i not gaming)) and no cpu eating, battery life: 2d2h from charge, SoT ~6.5h, remained 15% (all time enabled Wifi(mostly on range/connected), 2xSIM, BT(not used, only pair with SBC for SmartLock), GPS)
also i must mentioned, that DP2rev2 is really stable, fast, smooth and (for me) working all apps i use before with Oreo, camera now have option of 2x zoom, bluetooth headset work (for music and for (gsm)phone call) and is (for me) usable as daily driver...
Click to expand...
Click to collapse
Thanks for the response. I'm gonna try your solution and will report later.
After a use of about 2 weeks, the battery life has come back to normal like oreo now. Getting more than 24hours of standby time with around 7 hours SOT. I just did the adb trick mentioned above and also switched off the background apps manager and battery manager.
I've had my T713 for about 18 months. It does what I need it to do but the security patch is now 9 months old so I am considering a new ROM. And I don't like being two Android versions behind
Just can't decide which way to go. Any opinions are appreciated. Thanks.
lmacmil said:
I've had my T713 for about 18 months. It does what I need it to do but the security patch is now 9 months old so I am considering a new ROM. And I don't like being two Android versions behind
Just can't decide which way to go. Any opinions are appreciated. Thanks.
Click to expand...
Click to collapse
If you want all the hardware to work normally, then stay with stock. If you don't care about microphone, tethering and hotspot, etc, then you can go to either 15.1 or 16. I used 15.1 for months and it was extremely stable. 16 now is pretty stable, but going to be changing and updating. 15.1 is official, and if you wait, you can upgrade to 16 when official.
As it happens, I have two 713s (long story). One of them is stock, rooted, with a few Xposed modules (GravityBox, XSSID). The other has the "unofficial" Lineage 16 (https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-16-0-t3829963).
LuK1337 has done a *fantastic* job of getting LineageOS 16 out quickly with minimum problems, and I intend to keep updating that system as new builds come out, HOWEVER, the "stock" Nougat system is my daily driver. At this point it has better battery life, fewer occasional "hiccups", and a better keyboard (with actual cursor keys!). The only drawback (for me) is the lack of adoptable storage for the microSD card.
I just changed from stock to 15.1, as I thought that move has to be made sooner or later anyways if I want to keep up to date with security patches. At least the version that I have (Sept 10th 2018) surprised me very negatively with battery drain when idle: I often don't use the tablet for a couple of days, and on stock the battery level would only go down minimally. On Lineage, however, it goes don't >10% per day, even though I don't use it. Yes, I manually did the change to have wifi turn off when screen is off.
On my Galaxy Tab A with Lineage 15.1 this doesn't happen, so it seems to be about this implementation here.
gorthon said:
I just changed from stock to 15.1, as I thought that move has to be made sooner or later anyways if I want to keep up to date with security patches. At least the version that I have (Sept 10th 2018) surprised me very negatively with battery drain when idle: I often don't use the tablet for a couple of days, and on stock the battery level would only go down minimally. On Lineage, however, it goes don't >10% per day, even though I don't use it. Yes, I manually did the change to have wifi turn off when screen is off.
On my Galaxy Tab A with Lineage 15.1 this doesn't happen, so it seems to be about this implementation here.
Click to expand...
Click to collapse
I flashed the 15.1 10/02 build 2 days ago. AccuBattery is reporting that the tablet is in deep sleep for 91% of screen off time. Where is the setting to turn off wifi when the screen is off? I can't find it.
gorthon said:
I just changed from stock to 15.1, as I thought that move has to be made sooner or later anyways if I want to keep up to date with security patches. At least the version that I have (Sept 10th 2018) surprised me very negatively with battery drain when idle: I often don't use the tablet for a couple of days, and on stock the battery level would only go down minimally. On Lineage, however, it goes don't >10% per day, even though I don't use it. Yes, I manually did the change to have wifi turn off when screen is off.
On my Galaxy Tab A with Lineage 15.1 this doesn't happen, so it seems to be about this implementation here.
Click to expand...
Click to collapse
I went back to to the Debloated Stock Rom, because of the idle battery drain on Lineage, tried both 15.1 and 16. I just want to be able to pick up the tablet and use it without charging it for a couple days.
lmacmil said:
I flashed the 15.1 10/02 build 2 days ago. AccuBattery is reporting that the tablet is in deep sleep for 91% of screen off time. Where is the setting to turn off wifi when the screen is off? I can't find it.
Click to expand...
Click to collapse
That deep sleep in AccuBattery apparently doesn't mean anything. I just did the test and let the tablet for the last 23 hours idle:
Battery dropped from 52% to 33%, AccuBattery says 98% deep sleep (22h26m).
The option to configure wifi during sleep is gone from the settings in Oreo (very annoying for tablet users), but you can set it manually, see here
tjupille said:
HOWEVER, the "stock" Nougat system is my daily driver. At this point it has better battery life, fewer occasional "hiccups", and a better keyboard (with actual cursor keys!). The only drawback (for me) is the lack of adoptable storage for the microSD card.
Click to expand...
Click to collapse
Had the first hiccup today when Chrome crashed. Never happened under stock but I can live with an occasional hiccup like that. Second hiccup with Weatherbug when the screen showed multiple overlaid on one another. This was app-related because closing the app made it go away.
Battery discharge data on 15.1
Here is some battery/discharge data from the AccuBattery app under LineageOS 15.1. I turned wifi off when I wasn't using the tablet because there is no longer an option in settings to do this and I'm not sure wifi is off during sleep. I don't have this type of data from stock Nougat but my impression is that this is not significantly worse since it projects to almost 5 hours screen on time and almost 4 days uptime.
Time: 24:15
discharge: from 86% to 60%
screen on: 1:17
deep sleep: 22:17
largest drain was from Chrome
Hello
Yesterday i had the phone around 65% at 01h00, in the next morning (around 7h20) i wake up to find the phone at 1%, no wifi/4G/bluetooth/GPS...etc was active, even the battery saver was ON. As you can see in the screenshots, android system drain battery around 400% !!! what's up with this behavior ? happened the 1st time last week (49% drained in 8 hours) the problem seems gone after i fully charge and than reboot, but still today happened.
The phone is almost 1 month old.
The 1st few days, i disconnected the phone from charging at 100% and went to sleep, after 6 hours battery is drained by 6% without doing nothing. is this normal ??? screenshot
ROM : crDroid 8, latest magisk installed+microg+magiskhide props config and fdroid/aurora modules installed.
Thanks
which rom are u using now? stock or custom?
sheikfahad said:
which rom are u using now? stock or custom?
Click to expand...
Click to collapse
Read the post. They are using crdroid8
Arealhooman said:
Read the post. They are using crdroid8ok
Click to expand...
Click to collapse
Arealhooman said:
Read the post. They are using crdroid8
Click to expand...
Click to collapse
ok... is there any heating issues?
Oi69qEZ said:
Hello
Yesterday i had the phone around 65% at 01h00, in the next morning (around 7h20) i wake up to find the phone at 1%, no wifi/4G/bluetooth/GPS...etc was active, even the battery saver was ON. As you can see in the screenshots, android system drain battery around 400% !!! what's up with this behavior ? happened the 1st time last week (49% drained in 8 hours) the problem seems gone after i fully charge and than reboot, but still today happened.
The phone is almost 1 month old.
The 1st few days, i disconnected the phone from charging at 100% and went to sleep, after 6 hours battery is drained by 6% without doing nothing. is this normal ??? screenshot
ROM : crDroid 8, latest magisk installed+microg+magiskhide props config and fdroid/aurora modules installed.
Thanks
Click to expand...
Click to collapse
clearly something is going wrong, I would suggest factory resetting, and optionally reinstalling your custom rom.
Oi69qEZ said:
Hello
Yesterday i had the phone around 65% at 01h00, in the next morning (around 7h20) i wake up to find the phone at 1%, no wifi/4G/bluetooth/GPS...etc was active, even the battery saver was ON. As you can see in the screenshots, android system drain battery around 400% !!! what's up with this behavior ? happened the 1st time last week (49% drained in 8 hours) the problem seems gone after i fully charge and than reboot, but still today happened.
The phone is almost 1 month old.
The 1st few days, i disconnected the phone from charging at 100% and went to sleep, after 6 hours battery is drained by 6% without doing nothing. is this normal ??? screenshot
ROM : crDroid 8, latest magisk installed+microg+magiskhide props config and fdroid/aurora modules installed.
Thanks
Click to expand...
Click to collapse
well, that must a bug related to optimiztion of the rom, report it to the rom mantainer
Exactly what happened to me same ROM same phone but I didn't root it. it drained from 54% to 6% during the night, next day I switched the ambient display off and the battery became better but so far I am also looking for solutions to make it similar to miui
I feel the battery is draining so much fast when I start using the apps unlike miui but the room is also great and fast , with my light use it gave me 1 day of use and remaining of 10% with 120 fps (3.3%/hr screen on and 0.6%/h screen off )
today I will test it with 60fps
sheikfahad said:
ok... is there any heating issues?
Click to expand...
Click to collapse
No, only when charging of course (around 40°)
Arealhooman said:
clearly something is going wrong, I would suggest factory resetting, and optionally reinstalling your custom rom.
Click to expand...
Click to collapse
I'll wait and see if this bug happens again as right now i need the phone for the rest of the week, if happens again i might switch rom altogether on the weekend.
tutibreaker said:
well, that must a bug related to optimiztion of the rom, report it to the rom mantainer
Click to expand...
Click to collapse
yeah i'll do that. ty
Johnton said:
Exactly what happened to me same ROM same phone but I didn't root it. it drained from 54% to 6% during the night, next day I switched the ambient display off and the battery became better but so far I am also looking for solutions to make it similar to miui
I feel the battery is draining so much fast when I start using the apps unlike miui but the room is also great and fast , with my light use it gave me 1 day of use and remaining of 10% with 120 fps (3.3%/hr screen on and 0.6%/h screen off )
today I will test it with 60fps
Click to expand...
Click to collapse
Wow, 3.3%/hr is seriously impressive for active drain, especially for 120hz. Can I ask you if you did anything special / your exact setup? I installed Ricedroid 8.0 + Sleepy kernel and applied the GMS Doze module + Naptime (as suggested by a kind poster on here), and this allowed my idle drain to go down to 0.2%/hr, but my active drain is still struggling a bit.
Linkoh said:
Wow, 3.3%/hr is seriously impressive for active drain, especially for 120hz. Can I ask you if you did anything special / your exact setup? I installed Ricedroid 8.0 + Sleepy kernel and applied the GMS Doze module + Naptime (as suggested by a kind poster on here), and this allowed my idle drain to go down to 0.2%/hr, but my active drain is still struggling a bit.
Click to expand...
Click to collapse
to be honest I am not sure if I report it correctly I have used accubattry app but I will post few screenshots from the app and you can see , I didn't do anything except disable the ambient display maybe my usage is light in default I don't know I also formatted the phone like 20 times during my testing for different ROMs. I found Cr-droid to be the best so far or miui
Johnton said:
to be honest I am not sure if I report it correctly I have used accubattry app but I will post few screenshots from the app and you can see , I didn't do anything except disable the ambient display maybe my usage is light in default I don't know I also formatted the phone like 20 times during my testing for different ROMs. I found Cr-droid to be the best so far or miui
Click to expand...
Click to collapse
Ohh the 3.3%/hr is combined use, which takes account of both active drain and idle drain (through what I guess is some weighted average). But honestly, 6.7%/hr (or even 7.8%/hr tbh) is still pretty damn impressive, so I'll thank you for letting me know! Now I wanna flash crDroid haha.
Linkoh said:
Ohh the 3.3%/hr is combined use, which takes account of both active drain and idle drain (through what I guess is some weighted average). But honestly, 6.7%/hr (or even 7.8%/hr tbh) is still pretty damn impressive, so I'll thank you for letting me know! Now I wanna flash crDroid haha.
Click to expand...
Click to collapse
I spent 1 day and half trying all custom roms in this forum because for long time I was on miui and didn't know how custom ROMs are now , after trying I found that all custom ROMs either are pixel flavored or very basic without any customization and I settled with Cr-droid because it offers best of both worlds less google and good customization options.
now regarding the battery after few days of using on 60 fps I have combined use 2.4%/hr and 0.8% screen off but I still feel that it drains fast during my usage compared to Miui , I have only used naptime for optimization do you advise me to add anything else for non-rooted device ?
Johnton said:
I spent 1 day and half trying all custom roms in this forum because for long time I was on miui and didn't know how custom ROMs are now , after trying I found that all custom ROMs either are pixel flavored or very basic without any customization and I settled with Cr-droid because it offers best of both worlds less google and good customization options.
now regarding the battery after few days of using on 60 fps I have combined use 2.4%/hr and 0.8% screen off but I still feel that it drains fast during my usage compared to Miui , I have only used naptime for optimization do you advise me to add anything else for non-rooted device ?
Click to expand...
Click to collapse
MIUI very often switches off alarm (not clock alarm) and wakeups -- it's known for long. Your notifications often comes late when using MIUI. In real life situation, however you might never notice it, but it's there. It also sets higher priorities to known messaging, social media apps to receive notification/action faster than any apps that are outside "the list".
It's a good trade off for battery life compares to stock AOSP or lineage which put every apps on generic list of "optimized battery" based on your pattern. It will took a long before the pattern is useable.
Johnton said:
I spent 1 day and half trying all custom roms in this forum because for long time I was on miui and didn't know how custom ROMs are now , after trying I found that all custom ROMs either are pixel flavored or very basic without any customization and I settled with Cr-droid because it offers best of both worlds less google and good customization options.
now regarding the battery after few days of using on 60 fps I have combined use 2.4%/hr and 0.8% screen off but I still feel that it drains fast during my usage compared to Miui , I have only used naptime for optimization do you advise me to add anything else for non-rooted device ?
Click to expand...
Click to collapse
I'm not sure about your possibilities on a non-rooted device honestly. I think Naptime can work on a non-rooted device, if you grant a few permissions through ADB first (if I remember correctly, the app itself will guide you through the process). Be mindful of which apps you're restricting though, as Naptime will likely cause delays in the arrival of notifications. You can whitelist apps through Android's battery restriction screen.
Linkoh said:
I'm not sure about your possibilities on a non-rooted device honestly. I think Naptime can work on a non-rooted device, if you grant a few permissions through ADB first (if I remember correctly, the app itself will guide you through the process). Be mindful of which apps you're restricting though, as Naptime will likely cause delays in the arrival of notifications. You can whitelist apps through Android's battery restriction screen.
Click to expand...
Click to collapse
yes I am it currently after activation via ADB it made some improvement I felt , so far the highest consuming system apps are : Android OS [19%] screen [9%] and System UI [6%] can I do something about them ?
Johnton said:
yes I am it currently after activation via ADB it made some improvement I felt , so far the highest consuming system apps are : Android OS [19%] screen [9%] and System UI [6%] can I do something about them ?
Click to expand...
Click to collapse
Hmm I don't have any further tips honestly, not about these specific things. In my case, using Naptime already improves battery life by a ton over the course of a day (not wasting entire %s in hours of idle time is already huge).
Try and see if greenify or its replacements helps.