Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
chrriiiss said:
Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
Click to expand...
Click to collapse
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Addicted2xda said:
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Click to expand...
Click to collapse
Well I first experienced the issue running CM 10.1.
Since then I've relocked it and loaded the stock RUU where things got REALLY weird. The navigation keys still didn't work and soon nothing was really responsive. I can't even get past the unlock screen. The ring bounces when I touch it but it won't drag and unlock. So it's still detecting something, but it's not really responding at all. I can't even turn the thing off now as holding the power button down restarts the phone. what is this i don't even....
bump!
I need help with this and after extensive searching, I haven't found anyone else with this sort of problem.
I'm trying to install a ROM via TWRP but my capacitive and on screen navigation buttons don't do anything, so I'm stuck without a ROM at the moment.
Related
Hello XDA Community
I recently started having some strange capacative button problems. This did not occur while I was running a no-sense script on top of ARHD.
Almost as soon as I started running bulletproof by xboarder, this problem occurred. I don't really see anyone else running his ROM with this problem.
Occasionally, these buttons work fine as they should and are super responsive. However, when they don't work, I can leave my finger over it for three minutes and nothing would happen. A work-around that only works around 60% of the time is by either
1. locking and unlocking the scree
2. pulling down the notification bar
3. locking and switching to the phone application
4. continually press it and pray to god that it works.
Are my buttons broken or is it just software issues? I'm really concerned because I've been looking VERY forward to ICS. I don't want to get it and still have these problems occurring. Please help?
Hello friends.
I just got my Motorolla Atrix 4G and im not abble to unlock it on the unlock screen, the touch just dont works at all there, even the capacitive buttons below not responding. The first day I managed to unlock it somehow after removing the battery, after that the unlock screen was working fine even when I lock the phone so I tough the problem was over and stated to install some basic apps. Like 2 days later the problem was back and now not even removing battery was working, sometimes I get to unlock it but now thats less and less posible. I read that installing an optional unlock screen could do the trick so I installed "Widget Locker" and worked some hours, then the same thing even the Widget Locker unlock screen dosnt respond. Its weird because once I manage to unlock it the touch works perfectly at all so that makes me think its a software/system problem.
Currently I cant unlock it at all, not even removing battery or anything.
The phone its used, I was thinking to bring it to a tech center on here and try root and installing a custom rom?
Thanks in advance for your help guys.
Bump...
Just to add... tried hard reset and didnt worked =/
¿Any sugestion? ¿Should I try an screen change?
Thanks.
BlazeHN said:
Hello friends.
I just got my Motorolla Atrix 4G and im not abble to unlock it on the unlock screen, the touch just dont works at all there, even the capacitive buttons below not responding. The first day I managed to unlock it somehow after removing the battery, after that the unlock screen was working fine even when I lock the phone so I tough the problem was over and stated to install some basic apps. Like 2 days later the problem was back and now not even removing battery was working, sometimes I get to unlock it but now thats less and less posible. I read that installing an optional unlock screen could do the trick so I installed "Widget Locker" and worked some hours, then the same thing even the Widget Locker unlock screen dosnt respond. Its weird because once I manage to unlock it the touch works perfectly at all so that makes me think its a software/system problem.
The phone its used, I dont have access to warranty or anything =/ I was thinking to bring it to a tech center on here and try root and installing a custom rom?
Thanks in advance for your help guys.
Click to expand...
Click to collapse
Does the problem occur when you move the phone into a vertical position (moving the lock screen)?
Try turning the screen off/on by using the power button (but don't turn the phone off) ... does this help?
When you installed a custom rom did you do a full system wipe? (goto 'mounts/storage' and format pre-install, data, system, osh, cache) before
installing rom.
Hello barry, thanks for the answer.
Yes, the problem occours in both horizontal and vertical positions.
If I press the power button the power off dialog appears on screen and im unable to touch the options, holding the power button dont turn the phone off so im forced to remove the battery to turn it off.
I havent installed a custom rom yet. Thats the next step ill be covering. I toke the phone to a tech center place and asked them to install a custom rom (since I cant persoanlly do the root and flash rom proces) They just told me that it didnt fixed it, but when i turn it on i saw the same Moto Blur interface wich make me think they didnt changed the rom at all...
Sadly when puting a SIM and starting the phone the Motorolla interface screen appeared, but... touch wasnt working there neither wich now starts to make me think it is a hardware problem after all... Im not sure anymore and dont know what to do now
Sorry for the long answer and the bad english.
sounds like your digitizer might need replaced, based off of what I read. just out of curiousity, what android version is it?
Stock Android Gingerbread 2.3 with Moto Blur UI
Digitizer? Not Screen then?
EDIT: Ohh nvm, Digitizer = Touchscreen right?
BlazeHN said:
Digitizer? Not Screen then?
EDIT: Ohh nvm, Digitizer = Touchscreen right?
Click to expand...
Click to collapse
Yes. Don't confuse the two, the screen has nothing to do with the digitizer, other than one being on top of the other physically.
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
Hello I have a 9100 international version, and this is not your usual 1-2 seconds lag on wake. My phone (well, my friend's) takes around 10 seconds to wake. Not exactly wake but for the display to show, because when I press the home key or power key, the soft keys light up and the phone vibrates to the touch, the screen is also responsive to touch while the screen is off.
All this started after I flashed paranoid android into it, but after trying multiple roms, the issue is exactly the same. I also flashed a pit file to repartition the phone to have more storage for apps and it worked. I mean the phone works flawlessly except for this particular issue of the screen not turning on fast enough, even though the touchscreen seems to be responsive.
Ill flash stock back to it and give it a try. In the meanwhile, any one else have had this issue?
Try Neatrom 6.4 is a stock based with more feautures and battery friendly. Yeah i faced this issue one time, in neatrom 6.4 i never have this issue.
I've rooted my phone and flashed it back to stock 4.4.2 (TWRP recovery) because I wanted more freedom than 5.01 gave me. Everything workeds fine until it did an OTA upgrade back to 5.01.
At this point the back button stopped responding (menu button was fine). When I pressed the menu button both of them lit up, but the back button still did not respond.
I put it back to 4.4.2 again and the buttons worked just as they should, but again after an OTA upgrade the back button stopped responding. Getting tired of this, I flashed various other ROMs from Stock 5.1 to CM12.1 and whichever one I choose the same problem occurs. Only when I put it back to 4.4.2 does everything work normally.
I know I'm not the only one who has experienced this and I'm told that Samsung is aware of it happening in a very few cases, but no cure has appeared and it is getting really frustrating. Today I flashed a really great-looking ROM, which is a port from the S6 for the S4. There are one or two little issues with it, but guess what? Yes, the back button is disabled again. I have switched on the accessibility menu option, which puts a floating icon on the screen which when pressed has a few options, one of which is to go back, but this is only a workaround kludge not a solution to the problem.
Is there an expert out there that can tell me what all the later ROMs have in common which disables the back key? There is nothing intrinsically wrong with the key mechanism, such as it is, because it works perfectly under 4.4.2. I have the feeling that since this only affects a relatively few S4's the problem will not be progressed.
Does anyone out there know what is going on and can anyone help me, please?
KC