weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
I think I have the same issue as you, but in case I don't I will post what I am seeing on my device.
In about the same frequency, say once in every 15 unlocks from phone sleeping, the screen will come on but will be completely unresponsive. Doesn't matter if it is swipe unlock or pin code etc, there is no response to touch input on the screen. In fact, I think the screen is just frozen or the operating system is causing the lock screen to hang.
If the lock screen is hanging, pressing power will:
(a) sometimes make the phone sleep again
(b) make the phone screen kind of glitch/blip and then it takes input again
(c) does nothing and the screen remains on and hung/frozen
Occasionally mashing both the volume key and power key will help fix it, but usually if it is completely stuck I have to do a hard reset (holding HOME+VOL UP+POWER and then selecting reboot from the menu).
Now - I think this could be an app, but not sure.
When I first got the phone, set it up with my Google account etc, it went ahead and downloaded ALL the apps I had installed on my previous phone (HTC Sensation running Android ICS). So if it is an app, it is having issues with this phone, not the OS, imo.
I uninstalled all those automatically downloaded apps, and used the phone for a bit without my normal stuff installed. Then started installing apps singularly.
I think it is either Facebook or Alarm Clock Xtreme. The latter makes more sense given it would be polling the system to find out when to go off, so it is doing more in the background I would expect than Facebook or any other non-system app.
Other apps I have installed/running:
Swiftkey X
3G watchdog
Dolphin Browser HD
ES File Explorer
Winamp (locks without this running or running at all in lock screen mode, so that is not the issue)
Real Calc
Google Drive
Facebook
Alarm Clock Xtreme
It is quite frustrating for a brand new phone to have these issues. Not sure if it is hardware related, and if it is, I want to find out soon so I can take it back to carrier within their 28day device swap RMA period.
Thoughts?
So others may try to help or identify the possible cause / fix .......
What is your firmware version?
Are you rooted, custom ROMs or Mods etc?
Stock ROM,Baseband : XXLE8. Build No :XXALE9.
But my screen responds after i press wake button again. You are right seems to be issue with the app. i will just compare your apps and below are the ones which are common between us.
Facebook
3G watchdog
Dolphin Browser HD --i never use
Google Drive
a fix that worked for me
Steps to the solution that worked for me (so far) were to uninstall:
1. Alarm Clock Extreme (no noticeable result but I wasn't needing that application anyway)
2. I had WIFI Fixer installed because of the problems I experienced with the WIFI connectivity on my Galaxy S3.
I disabled that application and problems seemed to go away for a time, but every so in a while they resurfaced. Much less often than before, though.
I was still stuck with my WIFI problem anyway, so I looked into solutions for that problem and since I could not find a workable solution I uninstalled Wifi Fixer and started tweaking my WIFI settings.
While doing that I noticed that disabling "Network Notification" under the Settings -> WIFI -> Advanced tab fixed both my problems.
Now I can't be 100% sure this solution works for all, but I am pretty sure the application that created the problem was "WIFI Fixer".
It's been more than 4 hours now without the "disabled unlock screen from hell", and I’m very happy.
LOOOL
Actually...
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
This is not a solution, this is a work-around....
It will remove the standby wifi.... My phone was at 0% battery in one night... But actually yes, the phone doesn't hang up when unlocking.
Someone who had replaced the phone could tell me if the problem is solved with a new one ?
calint said:
My WIFI problem was not solved.... but I found a solution on another forum , which you can read below:
I dialed *#0011# then pressed menu button, then selected WIFI, and pressed the button to turn off the "WIFI power save mode". Hit back until I was back in the homescreen. WIFI has worked to my satisfaction ever since.
Click to expand...
Click to collapse
Sadly having the same issue! and only sing LG6 and LG8 of the UK firmware was release.. out the box was LG4 if I am not mistaken... have been putting off custom roms due to the fact stock one is so far good..
This fix seems to be working..Thanks! will live with battery drain as data is expensive in SA!
khan.dharvesh said:
weird and terribly disappointing. Once in atleast 15 unlocks, when I press the power/wake button, screen just doesnt respond. I try to swipe, but no response. But when I press wake button to turn off screen and press it again, theres no issues. This happens only during unlocking screen. Did anyone face this issue?
rest all is good..no lag..once unlocked phone works perfectly...no lag..no getting stuck..again, let me tell u this issue happens once in 15-20 lock/unlocks.
Click to expand...
Click to collapse
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
It worked!!
douglasurbano said:
This looks like a bug from wifi, i had the same problem and i found a fix:
On the dialer type: *#0011#
Then press menu -> wifi, there is a button ON ( power saving or something ), change it to OFF.
let me know if it solves ur problem
Click to expand...
Click to collapse
This worked for me!!! Thank you!! I was about to take a hammer to this phone! :good:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
RhavoX said:
I seem to have another problem. When unlocking the phone the screen turns on in a quite ok amount of time, but then when I touch it immediatelly after it turns on it doesn't react to touch. This moment when touch is not working is getting longer and longer depending on how long the system is running, anybody else sees this?
Click to expand...
Click to collapse
Not sure what ROM and kernel you are using, but at a big guess, try reflash another kernel or with less aggressive settings.
Sent from my GT-I9300 using xda premium
hey guys. I have a problem with my s3's lock screen similar to the described. whenever I press the power button to unlock, it takes 2 second for the screen to turn on. Anyone got any ideas on that?
Related
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
p1ceus said:
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
Click to expand...
Click to collapse
Can you check under settings -> applications -> Background tasks?
It more looks like plenty of apps are trying to sync up or use the resources. I might be wrong, but this did happen to me even at about 55% battery. But not as bad as 10 taps. I just felt the app launching was a lil slower than normal when I had ample background tasks.
Didn't know about "Background tasks", thanks
Currently I have only "HTC Hub" there. I will go and check this setting next time when I occur this problem.
But anyway, shouldn't reboot kill all background apps?
p1ceus said:
Didn't know about "Background tasks", thanks
Currently I have only "HTC Hub" there. I will go and check this setting next time when I occur this problem.
But anyway, shouldn't reboot kill all background apps?
Click to expand...
Click to collapse
Reboot surely will kill all background apps. But these background apps are different to other OS. They are those that will 'start on boot'. So after reboot just in few seconds, they will get to their business as usual.
I love this 'background' task feature! No other OS does it so efficiently as Windows.
The good thing is if you check that place often, you will know what apps are 'going to run'. It doesn't mean they are running all the time. It tends to indicate the capability of them to run.
So as you said you just have HTC Hub, which is same on mine. However, when you to go 'advanced' option on that same page, you will see a list of greyed out apps that are going to run in background and you can't kill them. Reason being these apps need to be told about not running in background by entering them individually.
See if that greyed out list has some huge apps. I downloaded this gMaps thing from market and although I just looked for maps once (a day ago) since then, it's been running. It's because it kept on looking for my GPS co-ordinates. Now that dint freeze my phone (1.5 Ghz, I know!) but it drained battery quicker. Changing attributes within the app, removed it from greyed list and happy days!
In a nutshell, very intelligent task management. You can choose what can run and can't run while your screen is off! + you get benefit of battery saver option if you use that so you can choose who can connect to 3g network and who can't while you are not looking at your screen!
PS: whole point of that long post was : Most likely it's not a background task that's hogging your processor, but it's worth looking under advanced and you might know what app was it.
Hey, that was a long post Thanks for clarifying. I just checked Advanced tab and there are only HTC hub and some Media something (I have it in Czech so don't know the exact name in english)
Anyway I will keep my eye on that menu and in case of any issue I will check it and we will see
OK guys, here is the update. It's still happening :/ Everytime battery drops under 10% phone cannot be almost used. I have to tap everything 10 times to get it done. Checking background task was not helpfull, only HTC Hub is running (even if I kill it its the same).
So...I don't know...maybe its a bug (some power-saving feature thats is not configured properly?). I was used to behaviour when my mobile works even with no battery left like fully charged. No change in behaviour...
p1ceus said:
OK guys, here is the update. It's still happening :/ Everytime battery drops under 10% phone cannot be almost used. I have to tap everything 10 times to get it done. Checking background task was not helpfull, only HTC Hub is running (even if I kill it its the same).
So...I don't know...maybe its a bug (some power-saving feature thats is not configured properly?). I was used to behaviour when my mobile works even with no battery left like fully charged. No change in behaviour...
Click to expand...
Click to collapse
As a last resort - try a hard reset. I've got many issues fixed that way.
However, can I ask how closer to the release did you get this phone? Here in the UK there seems to be two separate batches dispatched. One which was at the release - which is buggy batch. I got my new phone sorted from someone I knew at the store and so far not a single problem from the earlier handset is seen. Battery is drastically better too (it was better on earlier one already, but this is very pleasing!)
Try hard reset, if that doesn't solve it, I would recommend to swap it if you can.
Hello everyone,
I am facing the exact same issue on my HTC Titan - when battery is low (battery saver turns on), touchscreen becomes unresponsive. This is very annoying since it usually happens when i get an incoming call and i cannot answer it.
Did anybody try hard-resetting the phone in order to solve this issue?
Thanks for the answers!
Regards
Hello there... I have the same problems too. I don't try to do hard rest for my titan. It is very annoying for me. Also some time my touchscreen becomes unresponsive even the battery charging is more than 50%...
Yeah, I get this issue too, it makes the phone unusable until you get to a charger. I find that it comes in stages, it sometimes is really bad then works for a few seconds, then stops again.
I have checked all my background tasks and nothing is really running.
I have this issue too. I got this phone only yesterday, and when my battery reached 10%, touchscreen became unresponsible.
Guys I think I've mentioned this in the FAQs thread, but ..
Everyone with this issue - please tick the box under battery saver, where it says 'automatically start.... '
If you phone goes below 25% without battery saver ON, it will lag/freeze - the screen response.
However with battery saver on, you will be able to use it till you go below 5% or even 3% when it gives you the 'critical battery' warning.
This is HTC screwing with us!
mine has the completely opposite problem!! when the phone is charging, the screen becomes very unusable, in ex. i press the phone tile, the screen registers my tap, but it understands that i pressed the tile below or next to the one i really pressed. or i happen to scroll down or up, the phone hesitates for a second and then scrolls but it is very jumpy and jittery, unlike normal use. some times it doesn't even register my taps 2 or maybe 3 times in a row!!
the only workaround i've found is not to use the phone when charging
is this happening because of a faulty charger, maybe the phone is experiencing a short circuiting situation??
(i forgot to mention that i have the phone only for a week!!)
thanks
drupad2drupad said:
Guys I think I've mentioned this in the FAQs thread, but ..
Everyone with this issue - please tick the box under battery saver, where it says 'automatically start.... '
If you phone goes below 25% without battery saver ON, it will lag/freeze - the screen response.
However with battery saver on, you will be able to use it till you go below 5% or even 3% when it gives you the 'critical battery' warning.
This is HTC screwing with us!
Click to expand...
Click to collapse
I have battery saver enabled and even with the heart icon in the info bar at the top, the screen is still unresponsive.
Same here! i thought it was just my device that was dead or something, even since it's only 2 months old!
I did a hard reset and it solved the problem, it must have been something messing it up.
Nope...I have tried Hard Rests...ROM Changes etc...but its still the same problem..
Does anyone here think its a hardware problem ? or something else?
Any geek suggestion would be helpful
Send it back to htc, let them repair it?
Sent from my HTC using Board Express
Hi, I also have a problem with non-responsive screens but only in specific areas and doesn't have to be 10% percent or lower.
Ex: It happens only when the keyboard is up and the buttons on the bottom are very difficult to press!
I'll provide pictures soon
------------
Phone: HTC Titan X310e
Custom rom: Dynamics 2.0b full unlock 7.10.8862 (ultrashot)
p1ceus said:
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
Click to expand...
Click to collapse
That happened to me today. Then I did a hard reset and now my phone won't go past the carrier logo (the one after the HTC logo, and before the windows Phone logo)
I've had this problem with both a rooted tablet with an extra launcher ontop of the B&N one, and now that I've put CM7 Final on it. Basically, it'll go to sleep after not being used for a few minutes, and then when I try to get it back on, it won't come back. The N button, or the power button, neither works, and I have to hard reboot it (hold the power button a while) to get back into it.
It doesn't happen every time, there doesn't even seem to be any rhyme or reason towards why it happens. Sometimes it'll just be sitting on the desktop when it happens, other times I'll have had a book open when it happens. Other times, it will come right back as soon as I push a button.
It's getting really frustrating, honestly. Is there any way to prevent this?
There's been some discussion of this (SOD = Sleep of Death) in the CM7 threads. You should look there for more info. I think searching for "wakelock" will find you what you need... I think that's what it's called. It's an interim fix.
I have been seeing this same thing. I originally thought it was something I loaded so completely unrooted it and let it run for a bit and rerooted it to find it is now doing it again. will look into what CRE mentioned
Only real thing I can find doing a lot of searching and reading is this ...
http://forum.xda-developers.com/showpost.php?p=23410167&postcount=103
Wake Lock app
Yeah, im having the same problem! It happens for me everytime. Im going to install that Wake Lock App tonight, see if it helps... my only concern is that will it drain battery life?
cheers steve
Weird as hell. Mine has not done this for a few days now. I do notice it happens when my WiFi is acting up.
last time it happened to me I had it sitting on the charger while I slept and I had left the wifi enabled.
I wonder if this is something to to do with the wifi sleep policy. I know on my android phone there is an advanced settings to access this.
any more issues with this? I have since been making sure to keep my wifi off when not in use, but I did have this happen once again when the battery was below 30% and sitting idle for a while.
I've had a similar issue where I need to hit the power button two or three times to get it to boot up on my CM7 Final internal build and I can't change the "go to sleep" settiing.
Posted from Spaceball One
apart from finding that Wake Lock app... Has anyone found a more permanent fix for the SOD issue?
I tried this and it seems to have worked as I haven't had the problem since I made this change.
Go to: Settings>Wireless & networks>Wi-Fi Settings. When you are in the Wi-Fi Settings screen, touch the Menu button in the status bar. It will bring up a dialog box. Select "Advanced" and on the Advanced screen touch Wi-Fi Sleep policy. That will pop up another dialog box and you select the "Never" radio button.
Hello everybody.
I have a rooted 4.0.4 XXLFB Galaxy S3 and have noticed a problem.
Whenever I'm on a call using my blueooth headset, the screen turns on once every 30 seconds, give or take.
It's a problem because if I have the phone in my pocket, sometimes I mute the call, other times I turn off the headset...
Does anybody know how to solve this?
Thanks in advance.
Posting to add a "me too" to the list. Trying a ton of different things, almost to the point of clean device.
Hit the button and the screen turns off, about 2-5 seconds later, screen turns back on. Does not matter what I do. Seems to do it with speakerphone option too. If neither Bluetooth nor speakerphone are used, and you put the phone to your ear, backlight stays off. Otherwise, it automatically turns back on by itself. Tried with wifi on/off, speaker with bt on/off, different headsets, etc. My Wife's does not have this issue, so I gotta look into what is different. There has gotta be a setting or app installed that is doing this. I've even tried apps such as screebl and others. Some even had a thing to say lock it off till press button, and it still comes back on after 2-5 seconds. I've muted and hung up on many people when the phone was in my pocket because of this issue.
I've not used a BT headset but i'm thinking that maybe because the phone isn't against your head the screen comes on. possibly to give you information about the caller.
I'm not saying you should put the phone to your head even though your using bluetooth either.
thanks, but, don't help, tried that too. Had entire top half of phone covered during most tests. Screen does not turn off unless I press button, then comes back on automatically after 2-5 seconds. I did find one app today that seemed to work, but not sure if it works too well "Smart Screen Off".
Sounds silly but have you tried locking the handset?
That's what I meant by pressing the button. Button on right side that if I am not on a call, turns off screen and locks it.
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
agree with the above. if you leave call status up while connected via BT headset, screen remains active (comes in and out). if you exit active call status (ie press home) then the screen timeout works. if you are talking on the phone without headset, no problem.
so yes, that's the prob. any solid fix yet?
please and thanks....
visegrip72 said:
Ok - narrowed it down a ton. If I leave the in-call status screen up, the screen turns back on after being turned off via power button. If I hit home or have any other screen active, it remains off. So dialer related, but I can deal with an extra button press.
Click to expand...
Click to collapse
Thanks a lot, visegrip. It was really frustating having to redial every other call because i hang up without noticing.
Any solution to this problem? Hitting a home button and locking the phone is not an option when I keep my phone in a leather holster on my belt. That's a main reason for having bluetooth as hands free.
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
Almazick,
It would be great if you can send me the fix!
ital1981 said:
Almazick,
It would be great if you can send me the fix!
Click to expand...
Click to collapse
Here is the fix for a screen that I created. Let me know if it works or not for you.
http://www.mediafire.com/download.php?1ikj7d4wnjs9hx5
Almazick said:
Problem solved by using Tasker. If anyone need APK patch file to fix a problem, let me know and I'll post it here
Click to expand...
Click to collapse
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Inane65 said:
You know, I use tasker and have been trying to figure this out for a while. I've also been trying Secure settings and Locale Using multiple settings and plug-ins. I have not been able to create anything yet that seems completely reliable.
Not trying to be rude or anything, but I am and always have been a little leary of installing APK files unless I know the source. However, if you would be so kind to post the contexts and tasks so that I may enter them myself manually, it would be greatly appreciated. Thank you in advance.
Click to expand...
Click to collapse
Well, It's pretty easy.
Profile -> Phone Offhook
Task:
Wait 20 seconds
App-> Go Home
Display -> System Lock
In case if you'll have any problems just use my apk file which is exactly the same.
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Hmmmmm... OK. Thank you. I'll have to try that and see how it works. I was looking, hoping and working on trying to get something that would keep the screen off. Dialing, talking and ending the call. I've got something that seems to work for the most part, (I still get quick flashes, which is fine) but still have some more work to do on it.
Sent from my ADR6425LVW using xda premium
visegrip72 said:
Good news! I just took the Jelly Bean update from sprint & this problem is FIXED!
I tried calling and turned off the screen and it stayed off!
I also called and didn't touch the screen and after the timeout, it turned itself off!
Click to expand...
Click to collapse
It's not fixed. I'm getting crazy about this master bug.
After my phone is running for awhile the screen won't time out, a reboot will fix it but after some time the screen won't timeout again. Also if Quick glance is activated, while the issue is present, the screen will turn on, start to dim and then the lock screen will show and stay until I shut it down. Maybe an app is running in the background and keeping it from shutting down? This is when the phone is not charging so it's not the Stay awake setting. I've also turned various settings on and off as well as changing the screen timeout, which is now set to 15 secs, and the problem still persists.
Anyone with this issue?
I've seen some (Issue 37974) with the GS3 posting about the same issue but never saw a resolution.
Any help or insight would be appreciated.
I've noticed this but it usually was an app that kept it running.
From the Homescreen, try holding down the Home "Verzion" button for a few seconds. Click "Remove All" and then see if it times out. If that doesn't work, try clicking "Task Manager" instead and closing all Active Applications.
If either of these do work, then when you notice it again, be more selective in which apps you close until you find the offending app. I have a few Sound Engineering apps that use the microphone and one of them forces my screen to stay on. I'm assuming to access the mic hardware. It seems to run in the background even when I "close" the app.
I've done the remove all and nada but I'm adsuming it is and app too...
Thanks for the reply...
It must be Stay Awake in developer options that is causing this bug. As stated a reboot fixes the issue temporarily, after the reboot the Stay Awake option gets turned off on its own, If I turn it on again the issue appears again shortly after. So somehow the Stay Awake option must be getting messed up and keeping the screen on even when not charging.
My workaround is turn off Stay Awake and Use Tasker to keep the phone awake while charging. Not what I'd like, I'd prefer the system work correctly, but it works for now.
Thanks
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
thenuke1 said:
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
Click to expand...
Click to collapse
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
kimdoocheol said:
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
Click to expand...
Click to collapse
interesting...
just my 2 cents. When i switched to swift from samsung key i just rebooted and it corrected the issue. Im sure theres a permanent fix but works as a temp one imo
I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.