Incoming call issue with Greenify and Xposed - Greenify

Version: 2.9 Beta 2
Phone: Xiaomi Redmi 1s
ROM: CM13
Mode: Boost (Xposed 81), donate package
I am experiencing a weird problem. With greenify module in Xposed enabled, if I get an incoming call it wakes up the device like it should but it shows me the lock screen and i need to either enter my pin or click the 'return to call' button to pick the call. If i disable the greenify module in xposed and reboot, the problem goes away. Any ideas what could be causing it?

khdl said:
Version: 2.9 Beta 2
Phone: Xiaomi Redmi 1s
ROM: CM13
Mode: Boost (Xposed 81), donate package
I am experiencing a weird problem. With greenify module in Xposed enabled, if I get an incoming call it wakes up the device like it should but it shows me the lock screen and i need to either enter my pin or click the 'return to call' button to pick the call. If i disable the greenify module in xposed and reboot, the problem goes away. Any ideas what could be causing it?
Click to expand...
Click to collapse
u can easily see that, Version 2.9 isn't stable yet. Try v2.8, if it still occurs then mention oasisfeng please

Related

proximity sensor issue(?) on stock rom

the issue in this thread applies to the case where gravitybox xposed module is installed on stock rom. also, all the call vibration tweaks of gb are enabled.
i'm running the cwm-flashable zip rom from here. and i have gravitybox v2.5.7 installed. the "vibrate every 45th second" feature of gravitybox is erratic with the screen off (when the phone is held to the ear / proximity sensor covered). but, if the screen is 'on', it works correctly at every 45 secs. (i moved the phone away from the ear around the 40 sec mark of every minute and checked.) the call connect/waiting/end vibrations are ok.
anyone else face this issue? folks getting the "vibrate every 45th second" feature to work properly are requested to post the name of their rom and the custom build version (from settings -> about phone) here. thanks.
m0han said:
the issue in this thread applies to the case where gravitybox xposed module is installed on stock rom. also, all the call vibration tweaks of gb are enabled.
i'm running the cwm-flashable zip rom from here. and i have gravitybox v2.5.7 installed. the "vibrate every 45th second" feature of gravitybox is erratic with the screen off (when the phone is held to the ear / proximity sensor covered). but, if the screen is 'on', it works correctly at every 45 secs. (i moved the phone away from the ear around the 40 sec mark of every minute and checked.) the call connect/waiting/end vibrations are ok.
anyone else face this issue? folks getting the "vibrate every 45th second" feature to work properly are requested to post the name of their rom and the custom build version (from settings -> about phone) here. thanks.
Click to expand...
Click to collapse
hi
u can try the below rom it did solve the proximiy sensor problem for me
link : http://forum.xda-developers.com/showthread.php?t=2471648

[Xposed][MOD] CM Options - Missing CM settings [4/7/15]

This is my first ever Xposed module which consists of several CM options / settings that are otherwise missing, but I find useful. This module has been tested on my personal device (Google Nexus 5) running the latest CM nightlies (hammerheadcaf - 4/3/2015).
The options within the module include:
Enable call recorder - Allows option in overflow menu to turn on call recording for the current call
Hide volume boost - Hides/displays the volume boost button
Automatic proximity speaker - Turns on speakerphone automatically when in a call and proximity sensor detects you have taken phone away from your ear
Proximity speaker delay - Sets a delay (ms) before turning on/off automatic speakerphone
Only while in call - Only turns on spearkerphone after recipient has answered the call
Hide superuser icon - Hides/displays the # superuser session active icon in the statusbar
Debug logging - Turns on basic Xposed module logging for this module
Changelog:
4/2/2015 - Initial release
4/3/2015 - Updated CM call recording code to force resource loading and set audio source
4/7/2015 - Redid CM call recording to force it on if enabled, small UI config tweaks and logging
Installation:
Download / Install attached APK
Enable module in Xposed Installer
Turn on settings you want
Reboot
Do I have to have CM for this to work? Or can anyone use it?
terrorist96 said:
Do I have to have CM for this to work? Or can anyone use it?
Click to expand...
Click to collapse
maybe its only for cm
works in lollipop??
Hi
Looks like does not work on CM12.
Call recording isn't showing up here, with the Xposed Module "EnableCMCallRecording" it works fine however. CM12 20150402 nightly.
terrorist96 said:
Do I have to have CM for this to work? Or can anyone use it?
Click to expand...
Click to collapse
No sorry unfortunately it only works for CM12 based ROMS.
jayaraj.chinna said:
works in lollipop??
Click to expand...
Click to collapse
Yes, I have geared the API version of the module so that it will only run with minimum Android API version 21 (Android 5.0)
Publiuss said:
Hi
Looks like does not work on CM12.
Click to expand...
Click to collapse
You have turned on/off the settings you want, and nothing happens? What particular function does not seem to work?
XlAfbk said:
Call recording isn't showing up here, with the Xposed Module "EnableCMCallRecording" it works fine however. CM12 20150402 nightly.
Click to expand...
Click to collapse
My approach to to enable call recording simply was to attach to the recording service "isEnabled" method and override the return to be always true, if enabled in the settings. I will push an update to attempt to override the resource loading on the boolean flag, which is based on country / region values. But it seems like overkill to me. I will also explicitly attach the current voice call as the audio source. Please let me know if this works.
Nice, can do you add „Navbar height“ Settings?
art.montesinos said:
You have turned on/off the settings you want, and nothing happens? What particular function does not seem to work?
Click to expand...
Click to collapse
Well i set call recording, no button appears, I tried speakerphone when phone is far from the ear, it does not activates...
When I was on a CM11 nether "cm call recording" module worked (button appeared but no working registration).
I own a Sgs2 plus and resurrection remix 5.0.2 ROM.
Can you add advanced reboot menu? By the way nice module there!
FantasticalX said:
Can you add advanced reboot menu? By the way nice module there!
Click to expand...
Click to collapse
CM already has an advanced reboot feature. You do not need Xposed for that.
Publiuss said:
Well i set call recording, no button appears, I tried speakerphone when phone is far from the ear, it does not activates...
When I was on a CM11 nether "cm call recording" module worked (button appeared but no working registration).
I own a Sgs2 plus and resurrection remix 5.0.2 ROM.
Click to expand...
Click to collapse
As for the call recording the UI is different in CM12 vs CM11. When enabled in CM12 you have to click the overflow menu (3 dots ...) And you should see a menu item to record the current call.
For the speakerphone issue I am at a bit of a loss. Could you try to get me a logcat of what if any errors are occurring? Is resurrection remix CM12 based?
RevUnix said:
Nice, can do you add „Navbar height“ Settings?
Click to expand...
Click to collapse
I can try this week to add some new features. Modifying the navbar might require hooking into resource methods which gets a bit tricky. I am just learning this as I go. But I will definitely give it a shot. It would be nice if CM12 did have more Navbar options.
Is there any way to enable call recording without using Xposed?
which xposed framework are you using guys? the one I have is not working properly, I have many faulty modules which are supposed to work on lollipop.
dafank said:
which xposed framework are you using guys? the one I have is not working properly, I have many faulty modules which are supposed to work on lollipop.
Click to expand...
Click to collapse
I am using Xposed framework alpha2, version 3.0 for lollipop.
harpin14789 said:
I am using Xposed framework alpha2, version 3.0 for lollipop.
Click to expand...
Click to collapse
I guess you mean this one http://forum.xda-developers.com/showthread.php?t=3034811 which is the one I'm using
have you tried cputemp or cpufreq in status bar modules?

[MOD][XPOSED] Call Screen Sleep Fix

Experimental Module
This Xposed Module will prevent Phone Screen to sleep(lock) during phone call.
Proximity sensor will work as it is i.e. Display will go off when proximity sensor is covered but screen won't sleep
Especially useful when loudspeaker is on and "Power key ends call" Accessibility feature is turned on.
display wont go off thus accidental call termination can be avoided.
Note: First Xposed Module
to test this module set sleep time(in phone Settings -> Display) to 15 seconds or so and place a call, if screen doesn't sleep after defined seconds it worked
Download at Xposed Module Repository. repo.xposed.info / module / pkg.x7491.xposed.callscreenfix
Tested on various devices. if it does/doesn't work for you post your ROM and Device Details
bitcoin: 1EyW96mf9uqVWYDW7npFbL1iWDhm2MoS2
I was literally about to make this for myself
But I don't see a DL lol
Emmanuel U said:
I was literally about to make this for myself
But I don't see a DL lol
Click to expand...
Click to collapse
am new user external link not allowed. Available at Xposed Module Repository
For now 100% working cm12.1
Thanks its very useful module
sent from my G7102 CM12.1 using Tapatalk
Very useful module.
Added to my list thanks!
works well on samsung device people is going to underestimate this module which i hope not
Unfortunately this module doesn't work on my Sony Xperia Z3 compact. Android 5.0.2
I feel like I'm really going to like this module !! But just a little thing : would it be possible to make it also force the screen to wake up when you receive a call ? Because (and I'm sure there is no option for this) whenever I receive a call, I must first push the power button in order to answer it (weird huh ?)...
Testing this on Samsung Kitkat
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Christoph_NL said:
Unfortunately this module doesn't work on my Sony Xperia Z3 compact. Android 5.0.2
Click to expand...
Click to collapse
on Android 5 you dont need this module
As far as i know if you have power key ends call feature enabled on Android 5 and screen sleeps, then when you first press power key it wakes up screen and second press ends call.
Frazew said:
.....would it be possible to make it also force the screen to wake up when you receive a call ? Because (and I'm sure there is no option for this) whenever I receive a call, I must first push the power button in order to answer it (weird huh ?)...
Click to expand...
Click to collapse
Strange never faced this issue on any of my device. Android automatically wakes screen when call is received. may be you are using a screen guard that may be covering proximity sensor
Frazew said:
I feel like I'm really going to like this module !! But just a little thing : would it be possible to make it also force the screen to wake up when you receive a call ? Because (and I'm sure there is no option for this) whenever I receive a call, I must first push the power button in order to answer it (weird huh ?)...
Click to expand...
Click to collapse
Yes nice idea, will this be possible ? I too sometimes have to push the power button then answer the call.
I'm not sure if this module aim to solve this problem
I receive a phone call, the phone call ends and my screen locks with pin number.
Why would it do that?
Anyway I read your description, it seems it solves another problem I never noticed.
I have a Samsung Galaxy S3 neo with kitkat 4.4.2
It is not keeping my screen on using Android 5.1.1. Still goes black when on call, supposed to stay on correct?
Sent from my One M8 using Tapatalk
x7491 said:
on Android 5 you dont need this module
As far as i know if you have power key ends call feature enabled on Android 5 and screen sleeps, then when you first press power key it wakes up screen and second press ends call.
Click to expand...
Click to collapse
This module prevent normally your screen goes to sleep when you make a call with speaker. But with this module my screen goes off anyway when I make a call. And yes with pressing the powerkey you can turn on the screen again. That also worked on Android 4.3.
Did not work on my ZTE Kis 3
Hello:
Thanks for the effort but this did not work on my ZTE Kis 3 working on android 4.4.2. Should I do anything to make it work, any thong on definitions?
Rui
sk1887 said:
I'm not sure if this module aim to solve this problem
I receive a phone call, the phone call ends and my screen locks with pin number.
Why would it do that?
Click to expand...
Click to collapse
I also noticed this weird behaviour on my S4, 4.4.2. It would be very nice if this module could fix this "issue". Not sure either whether it's the case yet.
useful module...confirmed works on Lenovo A3000 with AOSP 4.2.2
Please if you have some time, try to make it compatible with MIUI.
Frazew said:
I feel like I'm really going to like this module !! But just a little thing : would it be possible to make it also force the screen to wake up when you receive a call ? Because (and I'm sure there is no option for this) whenever I receive a call, I must first push the power button in order to answer it (weird huh ?)...
Click to expand...
Click to collapse
I have noticed that when my phone is on battery save mode, my screen does not turn on when a phone call comes in.
Sent from my Nexus 6 using XDA Free mobile app

[BETA] Greenify 2.9.5 beta 3 (Sep. 21, 2016)

This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
v2.95 beta 3
Aggressive Doze now works in non-root mode on Android 7. (Manual privilege granting via USB required)
Improved GCM Wake-up (Xposed) for some misbehaving apps. (e.g. WeChat)
Improved the stability of accessibility service.
Fixed Wake-up Cut-off on Android 6+.
Fixed Shallow Hibernation (Android 6+) in boost mode (Xposed).
Fixed alarm analysis on Android 6+.
Fixed the false "Root privilege not granted" notification.
Fixed the verification failure in a short time after donation package is installed.
v2.95 beta 2
Wake-up cut-off now works on Android 7.0 (root).
Improved the overall stability and smoothness of non-root auto-hibernation.
v2.95 beta 1
Auto-hibernation in non-root mode is now compatible with secured key-guard. No more compromise for device security!
Screen-off by Greenify no longer invalidates fingerprint unlock and Smart Lock. Be sure to enable "Alternative Screen Off" in settings.
Aggressive Doze and doze notification is now compatible with Android 7.0 in root and boost mode. (support for non-root mode on the way)
Tasker plug-ins for toggling Auto-Hibernation and Aggressive Doze.
Improved app state detection on Android 6.0+.
Click to expand...
Click to collapse
Known issues
Doze on the Go is not yet compatible with Android 7.0 in non-root mode. We are seeking for a proper solution.
Get beta versions
Opt-in to beta channel or download the apk file.
oasisfeng said:
This thread is served as a general discussion and feedback for recent beta versions. It will be updated with newest version in title and change log in the first post.
Changelog:
Known issues
None.
Get beta versions
Opt-in to beta channel or download the apk file.
Click to expand...
Click to collapse
Works on my Nexus 6! awesome stuff!
italia0101 said:
Tried the aggressive doze on my Nexus 6 ,,
Had it plugged into my PC with a logcat running . i used the " battery unplug " command .
I can see it go into Doze on screen off . a new notification says " entered doze mode" , but with a bit of shaking a movement it wakes up , so on the Nexus 6 at least it still gets awoken with motion
Click to expand...
Click to collapse
Have you granted the DUMP permission manually?
oasisfeng said:
Have you granted the DUMP permission manually?
Click to expand...
Click to collapse
No i have root, but with your suggestion from the other thread it seems to work! so thanks for that, i've edited my post above
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
naudmick said:
Problem with galaxy S6 G920f Android 5.1.1 xposed and rooted.
Problem in open setting, FC App in bêta 9.1
Click to expand...
Click to collapse
Sorry, I messed up with Android 4.x & 5.x in beta 1, a fix is pushing out.
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Pupet_Master said:
I have a concept to offer for a new beta build.
Is it possible to make a hybrid engine, where we can choose per app the ones we want to be hibernated with the normal mode and what apps we want to use shallow hibernation?
So for example i can set whatsapp for shallow hibernation and fb messenger to normal hibernation mode
Click to expand...
Click to collapse
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
oasisfeng said:
Ye, that's the plan in the next major version (3.0 probably), which needs a completely redesign of the UI.
Click to expand...
Click to collapse
Thanks, i can't wait for it
draggehn said:
@oasisfeng Just curious if you have any idea how to fix this problem: one of the recent updates of Greenify made my fingerprint sensor during sleep no longer work; I have to wake up my device (turn the screen on) for it to respond again. Any ideas? (I am fairly certain it is Greenify as 1) nothing recently has changed, 2) somebody on the Nexus 5X subreddit also had this problem)
Click to expand...
Click to collapse
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
oasisfeng said:
I've never had this issue on my daily Nexus 5X. Do you use nav-bar gesture to hibernate apps and turn off the screen?
Please try disabling some of the features (Aggressive Doze, Shallow Hibernation for example) in Greenify and try again to narrow down the cause.
Click to expand...
Click to collapse
Disabling aggressive doze right now, I'll report back.
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
arunkafley said:
I updated from 2.9 Beta 1 to Beta 2 and now doze seems to be gone. Doze was working in Beta 1. My phone is rooted.
Click to expand...
Click to collapse
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
lusto170859 said:
It's a Dream. 3 percent in 8 hours. Calls and WhatsApp messages arrive anyway. I don't need more.
Click to expand...
Click to collapse
It's usually inaccurate for the first a few percentages from 100% downwards.
I'm going to prepare for and celebrate the Chinese New Year in the following two weeks. The next beta release is probably not going to be released soon.
I'll check and reply to posts here occasionally during the holiday.
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
even if i have root ?
thanks for the hard work
oasisfeng said:
Is your device running Android 6.x? Be sure to grant the DUMP permission manually as suggested in the first post.
Click to expand...
Click to collapse
Yeah I did that. But before without granting the DUMP permission it was working fine
oasisfeng said:
It's usually inaccurate for the first a few percentages from 100% downwards.
Click to expand...
Click to collapse
Yes I know. But without Aggressive Doze I lost 12% in this period. Normal Doze does not work with my device. (Samsung Galaxy S2plus CM13)

Problem: Greenifing during CALL

I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
Have you greenified anything related to phone calls? Can you post a screenshot of what all you have greenified? Do you also use Amplify?
This is not the normal behaviour unless you greenified or limited something which you ought not have.
Nothing related to Call or Phone or other system realated apps are in Greenify list (178 apps).
Normal behaviour of Greenify is to start hibertatiing apps when screen goes off.
(In root or boost (xposed) mode this operation is very fast, it closes many apps at once.)
But in NON-root mode it use standart automated [Force close] dialog or every app, so it takes a second or two per app to close it.
When I make (or receive) a call, I put the phone near to my ear, the proximity sensor turns off the display.
After a while, Greenify starts hibernation process.
There is no problem with the CALL itself, it is not interrupted or disturbed and qualiry is excellent.
The problem is when I take off my phone from my head, proximity sensor "realesed" and display have to goes on (rise) again but this NOT happens.
At this moment Greenify closes apps one by one and screen is OFF.
Call conversation remains active and I can NOT hang up (close) my call.
No reaction if I press [Home] or [Power] buttons.
By pressing many times (5+) [Power] button I'm able to interupt the Greenify hibernation process, display goes on and I see the force close app's dialog.
Now I use drop down menu and press (red earphone icon) to hang up (close) my active call.
That's why I think that settings option in Greenify for "temporary disable of hibernation" during an active call will be very useful especialy for "non-root mode" users.
Do you think it is worth to add such option?
@ChoSmile
When you are on a call, it will hold a wakelock so that the screen going off doesn't affect it. The proximity sensor senses your face near it and switches off the screen. When the phone is held away from the face, the proximity sensor should sense it and switch on the screen. This is the normal behavior.
Greenify starting to hibernate the apps should not affect the proximity sensor sensing. Check the functioning of your proximity sensor because no one else seems to have reported this problem, as far as I know.
I don't think that Greenify hibernates apps during a call ie. while the screen is off during a call. Atleast for me, it doesn't.
ChoSmile said:
I use Greenify for a long time with donation package, beta tester also.
At the moment I'm using it on a non-rooted Samsung Note 5
I add most of the programs be "greenified" except a few important for me.
The BIG PROBLEM is that in most of the times when there is an ACTIVE CALL, Greenify strart "working" and I can not do aniting. The phone is "black" and I can not even close/finish the call, just waiting Greenify to "hibernate" a.k.a. "force stop" all apps.
Sometime with 5 to 10 "power button" presses I'm able to interupt "hibernation" and to close my call.
Please, add an option to DISSABLE hiberation during a CALL!!!
Somebody else having this problem?
Best regards to all developers!
Click to expand...
Click to collapse
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
kenboyles72 said:
By any chance do you have aggressive doze enabled in greenify? I started having about the same issue, i would receive a call and screen would never wake up. I had done a lot of tweaks and wasn't sure what exactly what was causing this. So I did a fresh install and started a little bit at a time doing my tweaks and never got to install greenify yet. So far, phone has been working properly. So maybe this had something to do with aggressive doze or the fact that I had two apps setting aggressive doze, greenify and force doze.
Click to expand...
Click to collapse
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
ChoSmile said:
I disable Aggressive Doze (experimental) but issue happens again, might be no so offen like before I disabled it.
@tnsmani
Do you use Greenify on NON rooted device?
Because on rooted devices, you probably use it "Root" or "Boost" working mode where hiberanating is "at once" for many apps.
Click to expand...
Click to collapse
Normally I use Greenify in root/boost mode since my phone is rooted.
But to investigate your issue, I ran it in non-root mode (phone is still rooted). Still my screen behaves normally.
I have the same issues exactly non root greenify kicks in during calls and everything goes south. Any solution to disable greenify during calls
Sent from my ONE A2003 using Tapatalk
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Sent from my ONE A2003 using Tapatalk
ofird said:
Guys. Anyine found a solution here? This is a real issue for me. I am using non root and everytime a call starts, screen goes dark, greenify starts and doesn't capture the right screens probably but rather initiates clicks on the task bar on the top. This way I see the WiFi starting or Hotspot being disabled or data being turned off.
All I need is for greenify to not work during calls!
Click to expand...
Click to collapse
Seems to be a persistent, unresolved issue on some non-rooted devices with stock ROMs. You'll probably have to abandon Greenify.
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Sent from my ONE A2003 using Tapatalk
ofird said:
My worst issues with battery drain is when the phone is on and not off. Maube screen brightness. I don't know but it drains like crazy
Click to expand...
Click to collapse
Your ROMs built in battery stats may (likely will) provide clues to that type of drain. For a more comprehensive assessment try GSAM which is a available in the Play Store. BBS can also help but it's a little more difficult to interpret IMHO. Good luck.

Categories

Resources