|
Post by fards on Jan 15, 2017 12:37:08 GMT
View AttachmentHere is my simple test... fully charged 2-Apollo-Lite phones to 100%, put both phones - screen-off on the shelf for 12 hours, took pictures of battery use.: LEFT = MAD ASOP 7.1.1 ROM - as of 12-Jan-2017 RIGHT = FARDS 6.0 ROM-11Dec16C - as of 24-Dec-2016 You can judge based on your own priorities. * FYI, had some charging issues with MAD ROM (12-Jan-2017), when phone shut down will not charge and battery gets really hot and phone charge LED does not light up. With phone on it charges and LED indicator works as normal. I still want to work out what's happening with "phone idle" it's bugging me that one..
|
|
|
Post by No1VIPER on Jan 15, 2017 12:40:41 GMT
View AttachmentHere is my simple test... fully charged 2-Apollo-Lite phones to 100%, put both phones - screen-off on the shelf for 12 hours, took pictures of battery use.: LEFT = MAD ASOP 7.1.1 ROM - as of 12-Jan-2017 RIGHT = FARDS 6.0 ROM-11Dec16C - as of 24-Dec-2016 You can judge based on your own priorities. * FYI, had some charging issues with MAD ROM (12-Jan-2017), when phone shut down will not charge and battery gets really hot and phone charge LED does not light up. With phone on it charges and LED indicator works as normal. I still want to work out what's happening with "phone idle" it's bugging me that one.. Do you mean on your ROM, or the MAD one?
|
|
|
Post by bl3nto on Jan 15, 2017 13:47:03 GMT
The screen what chucker posted, Phone Idle section still uses a lot of battery, the problem on M.A.D.'s ROM is that there is additional section Android OS uses the same amount of battery like Phone Idle. So essentially Phone Idle is sucking a lot of battery on both rooms. And on M.A.D's ROM it's doubled. EDIT: question for fards, is it possible to pack your ROM to be flashable ZIP, I know I'm being a PITA but it's a lot easier just to transfer the ZIP file to your phone and then flash the new ROM than having to deal with right version of SPFlash Tool and also installing MTK drivers that work with X20 chipset.
|
|
|
Post by MLC on Jan 16, 2017 8:05:56 GMT
Hi, I’m currently on fards ROM (Latest Build: 11Dec16C) coming from Stock ROM (OTA 4), + TWRP & Rooted & XPOSED. On both ROM’s the Telephony volume is very low when over Bluetooth and Speaker, nearly inaudibly. I tried already ViPER4Android FX_2.3.3.0 & Busibox and latest drivers (didn’t work for me at all neither on Stock nor on fards ROM). Also installed DOLBY ATMOS, which works very good for MUSIC over Bluetooth & Speaker, but Telephony doesn’t work, ATMOS won’t even notice any source of sound. I allready upped on Engineer Mode Hardware Testing ->Audio->Volume->Audio Playback the System and the Bluetooth_sco to 152 on Headset & Speaker. Nothing has really increased the Telephony Volume. I would appreciate any suggestions/solution how to up the Volume for Telephony over Bluetooth and Speaker? Thx in advance
|
|
|
Post by chucker on Jan 17, 2017 5:50:46 GMT
Yes, battery consumption moderation is better with FARDS 6.0 (Build: 11Dec16C) than MAD 7.1.1 based on the objective tests I have run on my phones at the time of this writing.
|
|
|
Post by bl3nto on Jan 17, 2017 6:49:04 GMT
chucker, that is definitely true, and clearly visible from the screenshot you posted, but still, there is a battery drain and 15%-20% is still significant... I haven't tested fards' ROM or Verevkas' CM13, but for me Verevka's AICP had lowest idle battery consumption (always less than 20% during 8 hours), then it was stock with 20-25% battery drain over 8 hours and M.A.D.'s ROM goes well above 30%+ over 8 hours of being idle. But I think M.A.D's ROM would be similar to stock or Verevka's if they fix that "Andorid OS" section that is using the battery (this section does not show up on other ROM's, at least not this much, more that 20% of battery usage on M.A.D.'s ROM in addition to "Phone Idle" section). Considering that all my previous phones had at max a couple of percent of battery drain during the night (my regular 8 hours of sleep), Apollo's ~20% over night is huge battery drain for me...
|
|
|
Post by SvejkM on Jan 17, 2017 17:08:45 GMT
You guys do something wrong. Try stop WiFi, data and apps on background. Check my screenshots, I using last fards rom and with stock it was about the same. See attachments (I hope it will insert attachments as picture ). Battery drain is about 8% for 50 hours and it's seems pretty good for me. Attachments:
|
|
|
Post by bl3nto on Jan 17, 2017 18:31:46 GMT
It's not apps, it's not WiFi and it's not data. Tried already All wakelock detectors list Android kernel as battery drain, and list hundreds of processes that run under Android kernel, which tells me absolutely nothing...
|
|
|
Post by fards on Jan 17, 2017 19:05:41 GMT
I still want to work out what's happening with "phone idle" it's bugging me that one.. Do you mean on your ROM, or the MAD one? Mine.(i really don't like calling it mine. I'm just playing with the stock source). Can't say i care about that lots stuff tbh.
|
|
|
Post by No1VIPER on Jan 18, 2017 2:49:49 GMT
fards would you be able to make a flashable zip file that's compatible with TWRP for your ROM? Or is that not possible?
|
|
|
Post by bl3nto on Jan 18, 2017 13:25:58 GMT
Is there any other way of troubleshooting this battery drain, except wakelock apps and battery monitor apps because they don't tell me much?
|
|
|
Post by fards on Jan 18, 2017 19:21:25 GMT
I've already said no to a flashable zip. The spflash is pretty damn foolproof. As has been shown twrp can cause issues.
The otapackages I've built don't flash with twrp, only stock recovery so there's no advantage.
|
|
|
Post by miiick3y on Jan 19, 2017 18:09:47 GMT
I'm using your rom since 2 days and I can tell that i have exactly the same battery life as on stock rom
|
|
|
Post by No1VIPER on Jan 19, 2017 18:20:07 GMT
There's one main advantage to TWRP... It doesn't require a computer to flash.
I didn't realise you already answered that question before. Sorry mate.
|
|
|
Post by bl3nto on Jan 20, 2017 8:17:21 GMT
Yep, It look like my fears are coming true, this damn battery drain could be the end for this phone...
|
|