Today i was simply typing a email and after finishing it i clicked back button to hide the keyboard. Wooha it is not working !
I thought
"Okey no problem i was on Android L and may be it is a framework issue lets flash ROM again"
Entered into my recovery and my heart skipped a beat.! Yep navigation keys not working in recovery too
Flashed Mahdi still no luck. Tested my touch screen with an app found in play store and it is not recognizing touch on that portion. But when i type something with keyboard all the bottom portion keys are working perfectly!
What is this issue ? Is it an hardware related thing ?
Wipe everything and do a clean flash. Always do a clean flash...
It is been last 3 months am using this beast as it is. Thanks to LMT. Thinking about replacing display.
Related
When i play games with latest update 3.0 sense and 2.3.5 when u press 1 button like
walk forward then u press turn left, it all stops. only 1 thing works at the time.
sorry 4 unclear english but multi touch used to be 4 fingers. now its 3 fingers?
what happened?
WHAT TO DO?
multi touch aint working properly!?
UPDATE: Rebooting device fixed this problem! well it did not fix the cirkle locker thing but..games are good now...
UPDATE: The Bug is back! Wtf is going on? rebooting fixes it fow little while but is strikes back very fast! and agains 3 multitocuh on antutu tester.?
Fixed: Hard reset fixed this issue, Now all is fine!
If your still interested it was probably a custom lock screen. Like go locker or lockbot.
I am having this exact same issue (also reported at androidforums.com/desire-hd-support-troubleshooting/470923-issues-following-update-2-3-5-a.html) - and I don't have any custom lock screen installed
hard reset fixes all issues.
hello fellow xda-ers
I recently updated to the latest and stable CM10.1 (after using M2,M3, RC3 and RC5) and noticed that my home button stops working after a while. I'm not sure when it started but I think it was with the RC.
I did a search but it didn't yield anything particularly relevant. Is that a known problem?
I just reinstalled everything after resetting all data and it still happening.
thanks in advance for your input,
n
edit: before someone mentions it, I read this thread:http://forum.xda-developers.com/showthread.php?t=2340170 where the user indicates that re-flashing everything and restoring his apps using TB fixed the problem. That's exactly what I did but the problem persists unfortunately.
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
same thing is happening to me. i was running cm since i bought the phone in February. Decided to flask Franco and now I'm getting this weird touch screen problems. The bottom row where the home button is located will become unresponsive. I decided to go into developer settings and enable "show touches". My phone is sometimes touches without my physical input.
Not sure if kernel related or if my touchscreen coincidentally has given out. I'm gonna try flashing stock kernel and see if that fixes things
nks2105 said:
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
Click to expand...
Click to collapse
I have the same problem on
Franco M3 and CM10.1 stable, just I'm not sure if it started when I flashed CM stable or Franco M3. Home button doesn't work with app draw open and also it doesn't swap from one homescreen to the default.
However if I got to settings>Launcher>Homescreen>Default screen and change it to another screen then back again the home button works properly but after a few days it stops again.
edit: its as if it just forgets what screen is supposed to be default
Has anyone faced similar issue? Here's bit of background. I was using Liquidsmooth custom ROM with navigation bar disabled and pie controls enabled for navigation. I used to to enable pie control to swipe from bottom border.
So, the day I got system update available notification (for 4.4.3), my pie control stopped working from bottom border. Just a coincidence I think. It was still working from other trigger positions though. I also had this incredible urge to see new update of Kitkat. So, I just got Google factory image of 4.4.3 & flashed it. Everything done, I got to home screen only to find out my navigation buttons are not working. That area is completely dead. Those buttons will randomly start working for some time. Only for a minute or so.
So I went back to the latest version of Liquid Smooth ROM. Pie control from bottom border & navigation bar is not working. Tried going back to stock 4.4.2 & take a 4.4.3 OTA. Still no go.
And to me, it seems a software issue since navigation buttons work in landscape mode. And the area where navigation buttons are in portrait mode also works fine for everything else. So, it's not as of that part of touch screen is dead.
So, to cut long story short, please help me out here guys!!! :crying::crying::crying:
Regards,
Mrugesh.
Did you find a solution to this? I know of a Nexus that also started having this problem and no clue how to fix.
Sent from my SM-T320 using Tapatalk
No clue dude... No resolution... I'm just using my Nexus with pie controls whichever way I can.... Thank God it's a Nexus. Else I'd have been screwed by now buddy.... But surprising to see no resolutions from XDA.
Sent from my Nexus 4 using XDA Free mobile app
Spoke to google support and they told me to return it for another device.
Sent from my SM-T320 using Tapatalk
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.
Hi,
I've a moto g5 plus which is not accepting any touch to the navbar area. Even when I enable the one nav button feature, the navbar keys hide but I cannot touch or register response to that. I don't think it's a hardware issue but if it is, how should I check it?! I'm currently using fluid navbar guesture app to navigate.?
The problem appeared suddenly when I was on Android 7.0, I thought ota will fix this problem. So I updated device to 8.1. But problem did not solved. So I tried hard reset, but no luck. If somebody know what exactly the problem is, I'd be glad. The device is not rooted nor the bootloader is unlocked.
How do I install stock oreo rom? I think this should fix it but I'm not sure.
Please help.
If you have your warranty you should get the device checked, that sounds hardware unless you rooted (you didn't) and touched something
What was the last thing you remember doing before this trouble started?
Does the screen touch works at the bottom? Does the navbar register the touch but it doesn't do anything? Can you see your lockscreen?
M1810 said:
If you have your warranty you should get the device checked, that sounds hardware unless you rooted (you didn't) and touched something
What was the last thing you remember doing before this trouble started?
Does the screen touch works at the bottom? Does the navbar register the touch but it doesn't do anything? Can you see your lockscreen?
Click to expand...
Click to collapse
Hi M1810, thanks for replying.
I've been told it's hardware issue by service centre but they not even touched my phone, that's another story perhaps. I don't think it's a hardware issue as I'm doubtful about how only the navbar portion of my screen became unresponsive only and not other part of screen?!!!
Last thing I remember doing is switching between one nav guesture feature toggling on and back. But it was working fine then for some time. It just suddenly stopped working. (This is the reason I think this is a software issue. With the moto nav bar feature.)
I've enabled the show touches from developer option. The taps not even getting registered on the bottom portion. Other than that, there is no problem. I can see lock screen but cannot touch the bottom three icons, the camera and google mic thing.
uXDay said:
Hi M1810, thanks for replying.
I've been told it's hardware issue by service centre but they not even touched my phone, that's another story perhaps. I don't think it's a hardware issue as I'm doubtful about how only the navbar portion of my screen became unresponsive only and not other part of screen?!!!
Last thing I remember doing is switching between one nav guesture feature toggling on and back. But it was working fine then for some time. It just suddenly stopped working. (This is the reason I think this is a software issue. With the moto nav bar feature.)
I've enabled the show touches from developer option. The taps not even getting registered on the bottom portion. Other than that, there is no problem. I can see lock screen but cannot touch the bottom three icons, the camera and google mic thing.
Click to expand...
Click to collapse
If not even the lockscreen lower part reponds then it's hardware.. if updating/reseting did not solve it
M1810 said:
If not even the lockscreen lower part reponds then it's hardware.. if updating/reseting did not solve it
Click to expand...
Click to collapse
Last question.... Can I install stock 7.0 rom by using this guide (https://forum.xda-developers.com/g5...e-npn25-137-67-5-fastboot-t3694738/amp/) )?! I'm currently on updated oreo 8.1. or should I flash the oreo based pixel experience rom?!
uXDay said:
Last question.... Can I install stock 7.0 rom by using this guide (https://forum.xda-developers.com/g5...e-npn25-137-67-5-fastboot-t3694738/amp/) )?! I'm currently on updated oreo 8.1. or should I flash the oreo based pixel experience rom?!
Click to expand...
Click to collapse
I don't know for sure, i recommend you to ask in that thread, ehat i know is that it is not recommended to install custom ROM's if you're currently on 8.1 stock