Related
i saw a post about ringer delay for AT&T user and they just need to disable the dialer and the problem solve but what about us sprint users? Here is the original post about that http://forum.xda-developers.com/showthread.php?t=449417
i tried to disable the dialer on registry but still get 2-3 second delay before my Touch Pro actually ring.
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
convert your ringer to .wav file
temperamentalman said:
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
Click to expand...
Click to collapse
The ringer delay that this changes is the pause between when the ringtone ends and it repeats. Not the delay from when the LED starts flashing (because a call arrived) till the phone actually starts ringing.
If you wish to turn off the HTC dialer and use the WM Dialer, simply goto the following registry entry,
[HKEY_LOCAL_MACHINE/Security/Phone/Skin]
"Enabled" = dword:1​change the Enabled value from 1 to 0 which will disable the HTC dialer.
I vote for converting to WAV files as well.
If you would like to complain to Sprint about it, the following is the thread I started on Sprint's forum regarding this very subject.
http://forums.buzzaboutwireless.com/baw/board/message?board.id=SmartPhones&thread.id=5304
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
temperamentalman said:
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
Click to expand...
Click to collapse
Depends on what you may have done (adding programs, etc..) to your phone. By default, our devices will turn the screen off to conserve battery while a call is in session. However, if you have added one of the S2A dialer GSM versions which was taken from the Touch HD, that feature was disabled because of the InCall curtain. The CDMA versions (my signature and others) were taken from the Sprint Diamond ROM that was released and still contains the necessary code to turn off the screen display while the call is in progress.
Smotrs...just HR'd and installing now. I haven't tried that one, and actually think I ended up with the GSM version I WAS using.
I'll let you know how it works.
Thanks...
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
temperamentalman said:
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
Click to expand...
Click to collapse
It should Dim after about 10 seconds (or whatever you have in the backlight Advanced setting under Battery). After about 40 seconds or so (same location) it should turn off the screen.
At least that's what mine does, just verified it again. Sounds like maybe your values are too high. After a HR they usually are by default.
Somehow it was at 30 (dim) and 1 min (off). That is a little high. Changed it to 10 / 40. We'll see what that does.
Thanks for the tip. I'll keep you posted.
Seems to now be working the way you explained!!! Thank you for the help!
Is there anything else out there, other than S2U2 that allow FULL SCREEN Caller ID pictures??? I don't want to reinstall that because the dialer is actually working right. I just miss full screen caller ID.
Thanks again.
That I don't know, sorry.
Eh...it's ok. I'd much rather have a dialer that works than a full screen picture of my ignorant brother.
you can also change the Slot Cycle Index in the epst settings... you'll need your MSL though
it's under "Modem Settings"
What is slot cycle and where are these settings? How do I find my MSL? I don't see "Modem Settings".
not trying to be an ass, but i suggest you do some searching. there is plenty of info on the subject
check out this thread - http://forum.ppcgeeks.com/showthread.php?t=48775&highlight=epst+poll
or here - http://forum.ppcgeeks.com/showpost.php?p=625185&postcount=14
and here - http://forum.ppcgeeks.com/showthread.php?t=42730&highlight=epst+poll
I don't think you are an ass...I'm thinking thanks for the threads!
I know search is my friend LOL
lol, no prob man...
Changed the SCI to 1. We'll see if that helps. There is always "0"!
I'm also seeing mixed reports/opinions on ACCOLC - Access Overload Class. Mine was defaulted at 8 on Sprint. People say leave it alone. People say set it lower. Others say set it higher.
i found that setting SCI to 1 is good enough, i'm able to catch my calls and haven't noticed decreased battery life from it so that's where mine stays.
on the sensor firmware blunt, the screen turns off it is not possible to disable the incoming call, is sent in direct sunlight, or bright light from the lamp sensor works.
on V20c 2.3.3 proximity sensor is not working officially release
on version 2.2.1 v10g sensor works correctly)
on version 2.3.4 CM7, Void forever works
you tube test my
http://www.youtube.com/watch?v=2jAmMgh0uY8
how fix it? disable?
up 22.07.2011
in v20e Proximity sensor is working but randomly, random screen fades out, then turn on, turn off during a call.
And why did you have to post in this section?
I have similar problem - with v20c proximity sensor during the call is switching screen on and off randomly (even when phone is on the desk). But in hidden menu test everything is ok. I don't have this problem in any froyo roms, or cm7.
Unfortunately, LG f*ck*d update to Gingerbread, many users have problems and are waiting for a good custom roms.
To end calls turn on ending with power button - settings > accessibility > power button ends call
http://www.youtube.com/watch?v=rH17cYeaXX4
I have exactly the same. Perhaps phone application is poorly calibrated with sensor. Like everything in this official update.
I'm not having this issue on v20g. However, I have the following added to my build.prop (thanks to Noejn)
ro.lge.proximity.delay=20
mot.proximity.delay=25
Click to expand...
Click to collapse
edit - I am having the same issue even with the edits though it's not quite as bad as the youtube vid.
Any news about the fix for this issue? I just flashed GingerLOL 1.5 ROM and faced this issue. It's based on V20c.
stolenmoments said:
Any news about the fix for this issue? I just flashed GingerLOL 1.5 ROM and faced this issue. It's based on V20c.
Click to expand...
Click to collapse
no fix it
but
To end calls turn on ending with power button - settings > accessibility > power button ends call
proximity sensor
The V20H version resolve this Bug !!!!
http://forum.xda-developers.com/showthread.php?t=1300421
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
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
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.