Develop Bugs

HELP! Can't answer phone while locked, wont unlock till caller hangs up

Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Running the stock ROM, and rooted with unrevoked.

michelbites said:
Sometimes when my phone rings I can't get it out of lock to answer the phone. When the caller hangs up only then I can answer. This is intermitant. I don't know what to do.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not rooted? These are things you should remember to post when you're having issues. Makes diagnostics much easier

All I have done was root it. I didn't install any rom or anything. I only rooted it to get the wifi tethering.

So screen turns on, but you are not able to press "answer" when a call is incoming?

Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App

nikon_rh50 said:
Its telling you to hang up on stock rom and go custom. Plus you have better support specially being in this community.
Just saying
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm inclined to agree. Custom ROMs definitely go waaaaay above and beyond the stock one. I use a combination of MyBackup Root and Titanium Backup free for contacts/messages and apps, respectively. Once you go custom, you never go back

What I was trying to say is that the screen is locked when the phone rings and then when I go to answer the phone it will not unlock until the phone stops ringing. But like I said in the first post this doesn't happen all the time. I would say about 25% of the time it does this. Sooo... Thats what I was trying to say.

Are you using Google Voice?
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.

I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.

reisa said:
Are you using Google Voice to direct your calls? I have 3 phones that GV directs my calls to, and I've noticed that sometimes that causes one or the other of the phones to ring "late". Sometimes the Inc, sometimes not. I don't notice an issue when someone calls my direct line to any of the phones.
Click to expand...
Click to collapse
I thought it was GV also but its not I uninstalled it and it would still do it.

Manitook said:
I am wondering what you would get if you use an app like No Lock that disables the lock screen.
I started using it when I had a roms lock screen fighting with a launcher's lock screen. I would get stacked lock screens, but only sometimes.
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
I'm not sure if I would like the no lock because I tend to put my phone in my pocket all the time and it would just turn on and pocket dial people. LoL

Manitook said:
Running without a lock screen is not for everyone, so think about how you use your phone before disabling this great security feature. For me, my phone never leaves my side, and I mean NEVER. And if a "friend" starts poking at my phone I start poking in their face or purse... They learn after awhile.
Click to expand...
Click to collapse
App protector sounds like a good app for you.
Sent from my ADR6300

SetCPU?
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.

smtom said:
Assuming screen is off when it cannot be unlocked - but...
Are you running SetCPU w/ a low screen off profile?
If not, maybe install SetCPU, and set a higher frequency in the screen off profile settings.
SetCPU is available in the market; it's also available as a free d/l for XDA members here on XDA.
Click to expand...
Click to collapse
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.

POQbum said:
Good call, I do remember when I was revving CPU way down with screen off. When it had been off for ~1-2 hours it'd be sluggish and take a bit for the CPU to rev back up. Never used it that long though because the Kernel I'm using now does this and using setCPU just chews up battery.
Click to expand...
Click to collapse
Well, there's something to try then - if the kernel is making the device slow to wake, use SetCPU to bump up the screen off profile and see if the issue persists.
Couple folk note just this issue in the kernel threads.

This is a known problem I struggle with myself. You may find that you can stroke up to deny the call but not unlock. It seems that this is some kind of grounding problem. Hearing that I tried setting the phone down and swiping while I wasn't touching it otherwise with some success. I've heard a quick cycle of the power button followed by an immediate swipe down can work. Some report pressing the screen firmly before swiping works. I usually just swipe up, call back and say "sorry about that, what's up?" After all, most people are used to drops and stuff because of Iphones.
I periodically goog "incredible can't answer" looking for the golden bullet.

[Q] Screen timeout not working?

I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?

kg1128 said:
I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?
Click to expand...
Click to collapse
Had that issue with siii, reboot fixed it, have you tried reboot?

mattsm said:
Had that issue with siii, reboot fixed it, have you tried reboot?
Click to expand...
Click to collapse
Yes rebooting always solves the issue but can i get a permanent fix? It's kinda annoying. I'm on GT-N7100 JB4.1.2 and i've never rooted.

Kinda glad i wasnt the only one having this issue. Happened to me yesterday. Kinda freaked me out as i dont want anything wrong with this phone.. reboot worked for me yesterday.
On a side note.. every once in awhile my youtube app goes to **** and it refuses to play videos.. it says network error yet i can do everything else... reboot fixes that too.
Sent from my big big BIG iphone killer.

morbiddevil82 said:
Kinda glad i wasnt the only one having this issue. Happened to me yesterday. Kinda freaked me out as i dont want anything wrong with this phone.. reboot worked for me yesterday.
On a side note.. every once in awhile my youtube app goes to **** and it refuses to play videos.. it says network error yet i can do everything else... reboot fixes that too.
Sent from my big big BIG iphone killer.
Click to expand...
Click to collapse
Yeah no kidding. I really don't want anything to go wrong with my phone. But unfortunately it has been kinda buggy from day one. A minor issue with the stock keyboard was solved after the 4.1.2 update. But the weird error with the Quick Commands thingy ain't getting sorted out, even after the update. Of course, reboots also never help.

Oh someone please tell me what's wrong with my phone The screen timeout thingy ain't working An unattended message or missed call means my display stays on till I turn it off manually A reboot would solve the issue but then it would come back again. Any permanent fix? Please help I've never rooted my phone.
Sent from my GT-N7100 using xda app-developers app

Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.

w7excursion said:
Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.
Click to expand...
Click to collapse
Lemme try doing that
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 09:48 PM ---------- Previous post was at 09:06 PM ----------
w7excursion said:
Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.
Click to expand...
Click to collapse
Went through the 124 apps that had WAKE_LOCK permission. (Used Permission Explorer). If I count out the recently installed apps before which the problem had originally started, I guess there aren't any suspicious apps. Oops Aren't there any apps that forces the display to go off? ^_^
Sent from my GT-N7100 using xda app-developers app

I'm just throwing it out there by maybe go into recovery and fix permissions? Clear the cache? Factory reset if all else fails I guess.

w7excursion said:
I'm just throwing it out there by maybe go into recovery and fix permissions? Clear the cache? Factory reset if all else fails I guess.
Click to expand...
Click to collapse
I didn't want to do a factory reset Anyways, thank you Lemme see what I can do
Sent from my GT-N7100 using xda app-developers app

kg1128 said:
I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?
Click to expand...
Click to collapse
Hi. Having the same problem... However, i believe it has to do with the feature that prevents screen from turning off if you are looking at it. Try to turn it off and on. Perhaps it will help.
If you continue to have problems, just disable that feature... it is a good adon, but having the screen turn off tose battery is more important.
Hope it helps.
Let us know if it worked out

[Q] Phone freezing after phone call ends

Wanted to see if anyone else has experienced this problem and if there is a solution. There are some other posts I found on this problem but on different phones. I can't believe I'm the only G3 owner having this problem. About half the times I receive or make a phone call, after the call ends, phone becomes completely unresponsive for about 5 to 10 seconds. Can't swipe to next screen, nothing. If the other person ends the call first then I'm stuck at the dialer interface. I can't even reboot the phone. I am rooted with IOroot and using Titanium backup and have frozen all the AT&T bloatware and some LG apps. I finally put Apex launcher on phone hoping this might solve problem. It has solved all remaining laggyness but still having the problem with freezing after phone call ends.
I have Exposed Installer and G3 Tweakbox installed. No other modules installed and this has been happening since before rooting.
I added screenshots of all the apps I froze withTB.
If anyone has some ideas on what I could do to solve this I would appreciate your help.

catatonix said:
Wanted to see if anyone else has experienced this problem and if there is a solution. There are some other posts I found on this problem but on different phones. I can't believe I'm the only G3 owner having this problem. About half the times I receive or make a phone call, after the call ends, phone becomes completely unresponsive for about 5 to 10 seconds. Can't swipe to next screen, nothing. If the other person ends the call first then I'm stuck at the dialer interface. I can't even reboot the phone. I am rooted with IOroot and using Titanium backup and have frozen all the AT&T bloatware and some LG apps. I finally put Apex launcher on phone hoping this might solve problem. It has solved all remaining laggyness but still having the problem with freezing after phone call ends.
I have Exposed Installer and G3 Tweakbox installed. No other modules installed and this has been happening since before rooting.
I added screenshots of all the apps I froze withTB.
If anyone has some ideas on what I could do to solve this I would appreciate your help.
Click to expand...
Click to collapse
I've got this problem as well. Touchscreen being unresponsive after someone hangs up on me. I have no solution tho just looking for an answer myself. Only way round it for me is a battery pull but would be nice to know how to fix it.

catatonix said:
If anyone has some ideas on what I could do to solve this I would appreciate your help.
Click to expand...
Click to collapse
Someone has told me why on Google +, well it will fix it for me. If you have disabled knock on/off and your on a certain firmware it is a known issue that the touchscreen becomes unresponsive. So hopefully you are in the same boat as me and you just need to enable knock on.

p70shooter said:
Someone has told me why on Google +, well it will fix it for me. If you have disabled knock on/off and your on a certain firmware it is a known issue that the touchscreen becomes unresponsive. So hopefully you are in the same boat as me and you just need to enable knock on.
Click to expand...
Click to collapse
Thanks p70shooter. I did disable the Knock on feature, comes on in my pocket too much. Maybe this will be addressed in a future update as well as the freezing issue. I will give this solution a try and see what happens.

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.

Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app

Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.

Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.

Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?

Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...

eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.

Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.

I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL

I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.

NVM
Screen still goes dead.
Anyone find an actual fix to this?

isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

[Q] touch key lights bug

hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?

Install a custom rom like cyanogen or something stock based.

I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk

Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.

Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk

Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!

LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.

TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?

TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.

LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?

Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su

I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.

Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.

No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...