Database Users

[Q] Nexus 4 Portraite Navigation bar not responding

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.

[DISCUSSION] Problems & Bugs on stock CM11S

I created this thread in order to share the problems which I am facing on my 1+1. Hope can get resolved by CM soon... As well as others can discuss about the problem and solution (if available) that we are facing. State method if others can try reporduce the problem to confirm will the problem affect all other 1+1 device, if have screenshot the better.
Firstly, please state:
ROM version (Root Y/N, Other than CM11s don't discuss here, Nightly, Color OS etc.):
ROM mod (State which app will affect system files, from your opinion):
Custom kernel (Y/N, If yes please state kernel you've used):
Model & storage (CN/INT ver, 16/64G):
Recovery (Apparently has nothing to do with ROM I think, just state better)
Problem/bugs:
Okay, start with me...
ROM version: CM11s Rooted, XNPH25R - latest at the moment
ROM mod: AdAway, BusyBox 1.22.1, Xposed Framework 2.6
Custom kernel: NO
Model & storage: CN ver 16G
Recovery: PhilZ Touch 6.49
Problem/bugs:
USB OTG will be not functional when plug in while the screen is OFF, if screen is ON then no such problem, even if you insert USB OTG while screen off and reinsert back after waking the phone, the USB OTG still not working (suspect deep sleep cut off USB OTG power) - Temporary solution: Reboot the phone
MX Player crashes more often while playing with H/W decoder, however S/W decoder works flawlessly. Format Played - 480p FLV.S/W uses more battery consumption so I don't like it, I confirm the same type of video played on other phone doesn't have such MX Player FC problem (If it crashes too many times it will stop working at some point, you can't even play MP4 files with H/W decoder and or stock Gallery app - Temporary solution: Reboot the phone
GPS sometimes takes forever to lock - Temporary solution: Reboot the phone
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
As you can see all these problems can be fixed by rebooting the phone, so I guess it's ROM related problem.

ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.

oneplusonepwns said:
ROM version: CM11s running XNPH25R
ROM mod: None, running stock and unrooted for now
Custom kernel: NO
Model & storage: 64gb sandstone black
Recovery: None
Problem/bugs:
Torch gesture not working 80% of the time, and crashes the phone - This has been confirmed will be fixed on next OTA
Same issue with torch. I ended up disabling torch and music gestures.
Haven't had any other issues per se, but my battery hasn't been nearly as impressive as others have stated. I am going to continue monitoring it and will report back once I have solid information on battery usage.
I have the yellow hue at the bottem 25% of screen but its faint and not too noticeable. I am hoping its just temporary.
Click to expand...
Click to collapse
At battery stats see any other apps are draining your battery. In my case, sometimes Android OS/System, Google Play Service and Media Server are keeping awake draining the battery while screen is off, in that case, enable privacy guard deny them from keeping awake, or reboot your phone.

ROM version: CM11s running XNPH25R
ROM mod: Rooted with xposed framework, AdAway.
Custom kernel: Franco Kernel
Model & storage: 64gb sandstone black
Recovery: Stock
Firstly: I always like to disable the backlight illumination of the hardware buttons. This works perfect but it doesn't stick. After reboot, its back to lit up.
Secondly: Notification sounds can't be set on per app basis. For eg, Hangouts has its own notification tones and I like gmail and other email app to have different notification tone from the system wide one, however it doesn't happen. All apps use the system wide notification tone regardless of what I set separately on them. I guess this has something to do with the theme engine coz I chose tones from it.
Thirdly: when rotation is locked, camera interface doesn't rotate. I thought camera interface is meant to auto rotate regardless of the "rotate setting on or off"
Sent from my One using Tapatalk

ROM version: CM11s XNPH25R rooted
ROM mod: Why mess with a good thing?
Custom kernel: N
Model & storage: INT 64G
Recovery: PhilZ CWM
Lock screen delay doesn't work on built-in custom lock screen. Works fine otherwise.

ROM version: CM11S XNPH25R, not rooted
ROM mod: None
Custom kernel: N
Model & storage: INT 64G
Recovery: Stock
[ ] 2 Google Play Services force closes while setting up phone
[ ] Ringtone and default notification sound were reset to default once randomly
[ ] Double-tap to wake setting becomes checked again randomly after turning it off, but the feature is not re-enabled
[ ] Google Now keeps showing "Good morning / evening! Here are your current cards" and "Google Now is always working for you" cards even after swiping them away many times
[ ] In-call speaker volume is too low, MUCH lower than volume for everything else
[ ] Some ringtones and notification sounds are duplicated with different names
[ ] The screen seems to miss touches occasionally
[ ] "Ok Google" and Google voice searches only work if I speak VERY loudly
[ ] The phone occasionally sticks in landscape orientation and I have to shake it to get it to rotate back to portrait
[ ] Scrolling is not as smooth as my stock Nexus 5 (more dropped frames) in not all, but some apps. This could just be poor optimization, but I'm calling it a bug because really this phone should always perform better than a Nexus 5 because it has an 801 and 3GB of RAM.

Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Does this have anything to do with it's multi touch issues?
Sent from my One using Tapatalk

ROM version: Stock CM11S XNPH25R, rooted
ROM mod: Busybox,Xposed
Custom kernel: No
Model & storage: CH 64G
Recovery: Philz
Problem:
Screen not wake when press power button,navigation light is on, but screen not wake. my solution for now is need to force restart.
Sent from my One using XDA Premium 4 mobile app

SleemLDJ said:
Is there anyone who types fast on the OnePlus One?
Do you find it that it misses some keys sometimes and generally makes it hell to type on...
Click to expand...
Click to collapse
Yes, I believe I have experienced this and quite often too.
Apart from the missed keystrokes, my phone reboots randomly every 30 mins or so. I haven't gotten around to root causing it.. Maybe due to ART (?)
ROM version: Stock CM11S XNPH25R, rooted
ROM mod: None
Custom kernel: No
Model & storage: INT 64G
Recovery: Stock

I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app

Maybe I'm just lucky I haven't come across any problems yet.
CM Version 11.0-XNPH25R
Completely Stock.

magnum73 said:
I have also issues with the touchscreen; some parts of the screen doesn't react on touch or swipe...For example when I touch the letter 'b' on the standard keyboard, its always the letter before or behind. In landscape modus it works well. Also games like candy crush and 2048 where you have to swipe alot on the screen and difficult to; sometimes it doesn't react on parts of the screen or it does something else ( to the right instead going down,...)
I 'm waiting since Friday for an answer...because I'm afraid its hardware failure
https://www.youtube.com/watch?v=SSmpYQYofOc
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Oh god that looks terrible.

i haven't seen this mentioned yet, but sometimes when i open the Google keyboard in landscape mode, it will only show 1 line of keys. i fix it by force stopping the keyboard

Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app

cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
You are most likely missing a couple lib files, like hotword detection for Google now..
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One of the moderators on the OP forums replied to my comment about the hotword detection and stated it is a known bug with CM and has been addressed and will be resolved in the next OTA.

cas8180 said:
Main ones for me are the speaker phone volume and incompatibility with the Google launcher "OK Google" feature.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
The speakerphone problem has been addressed in one of the recent nightlies. Call volume is good now. It is scheduled for the upcoming ota.

M9 just came out. Only in a matter of time we get the ota for the next update

jarjar124 said:
M9 just came out. Only in a matter of time we get the ota for the next update
Click to expand...
Click to collapse
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app

cas8180 said:
Where are you guys seeing these updates. I went to cm's website but didn't see our device on there. Also tried googling it and didn't see it. Maybe I am just blind.
Edit:
Just found it nevermind...
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Where
Sent from my One using XDA Free mobile app

Navbar stop working

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.

Bottom Navigation bar not working

So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?

I had a similar issue just recently. Using the developer options I was able to see that the presses under a certain line are not registered anymore. Strangely enough, after charging the phone over night, the issue is gone. I am now dreading its return and start to search for a new phone as it seems from your comments that this is a hardware defect and not a software issue...

troin said:
So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?
Click to expand...
Click to collapse
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve

Spencervb256 said:
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve
Click to expand...
Click to collapse
that's pretty muth the only thing left I can do.

The bottom part of the screen no longer works for me.it was weird because it worked for a starter but then it just stopped working. the first half inch more or less of my screen is senseless

so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.

viggyv said:
so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.
Click to expand...
Click to collapse
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..

Spencervb256 said:
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..
Click to expand...
Click to collapse
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA

IftekharAziz said:
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA
Click to expand...
Click to collapse
Some of my friends had this problem too. They had to replace a new battery and some even a new lcd. Battery caused this problem.

https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049

Moto G5 plus: Navbar not accepting touch, even woth one nav button feature.

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