My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
The softkeys are enabled within the framework.
Sent from my Nexus 4 using Tapatalk 4
Help
manojsap said:
My Nexus 4 has Stock ROM Android 4.3 & the Navigation bar at the bottom does not respond to touch in Portrait position but works in Landscape position for applications where I can use the Landscape mode. In the Landscape mode the screen rotates the position of the Navigation bar.
I have through the developer option selected the Show Touches option which shows me the exact touch position on screen as a blob. In the portrait position I can see the touch points on the Navigation bar the home screen works for Google Now but the back & task do not work however I can see from the Show touch it registers the touch but no execution of the command happens. The same Navigation bar in Landscape mode works perfectly as required. These developments are after the OTA 4.3 upgrade. Can someone help me to either remove the navigation bar in the Stock ROM Android 4.3 as now I have an application from Google store called Button Saviour (Non Root) working perfectly. I have also observed that the due to the Show Touch option activation it generates sometimes on the navigation bar area on the extreme left a clear Show touch blob where as there is no one touching the screen. This Show touch blob sometimes rapidly oscillates horizontally in the Navigation bar area & which ever icons it crosses it automatically triggers them as well randomly. On touching the screen in the Navigation Bar at that time does not make the back or task button work but without touching I can the Show touch blob while oscillating managing to make it work while crossing over the respective button icons.
So the hardware does not seem to be the issue but some bug in the new 4.3 which is triggering this weird behaviour. I use the Nexus 4 mostly in Portrait mode hence it is frustrating to now suddenly not have the Navigation bar functional the way it was suppose to work. Can some one help & guide me on what to do to resolve this problem.
Click to expand...
Click to collapse
same issue here even i try a factory reset
I flash the stock rom again and no clue of what to do
The exact same issue here, started behaving quirky since 4.3 and went bat**** crazy after the update second 4.3 ota (1.8mb patch google released recently). i used developer options to show the on screen touch blobs as well and it registers touches in the nav bar area, it just will not work in portriat (or rather that section of the screen) It is extremely frustrating.
I even went as far as to use adb and fastboot to restore my phone to stock 4.3 which would remove all files and place a stock 4.3 directly from dev.google but still It doesn't work.
The same issue
Im having this exact issue just a few days after i install a new update i hope that its a software issue :crying: and if is not warranty will cover it?
Navigation Bar issue
Same problem here , wont respond on portrait mode.
I did try to downgrade my android version to 4.2.2 (from 4.3) after the factory reset did not work, that did not work either.
Any ideas? could use some help
I have the same problem, I tried to restore the 4.3, the 4.2, but the problem remains, I also tried the cyanogenmod and 4.4, but it still does not work the navbar in portrait mode ..
No one knows a solution to the problem? You may have a hardware problem? Who takes care of the navbar?
Having the same issue here. Works in Landscape but not portrait. It went spastic this morning randomnly opening the clock and pullin the bar down itself. Show touches showed it registering touches all around the nav bar then suddenly it stopped. I cant use the bar now at all in portrait but the random touches are gone. I downloaded a touch detector and it shows all the way up to where the nav bar would be then deadzone, but fine in landscape again
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
sorschumi said:
anyone know a solution to the problem? I tried to put the last KRT16S factory image, but the problem is always the same ...
Click to expand...
Click to collapse
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Same issue here
Tried lot of things still not working .........
pls someone find the solution.......
skycoresaunish said:
Tried lot of things still not working .........
pls someone find the solution.......
Click to expand...
Click to collapse
I think it's a hardware problem. Mine just went bad as well.
I have this problem now, too. Google now NAVRING still works to open Google Now from the middle nav button, which is why I do not understand why they nav bars do not work at seemingly the bottom of the screen. It just seems like that part of the screen has died, though some times it randomly works....... what the hell is this?
Huawei ascend mate navbar problem
I have same problem. And not only that my landscape control also got messed up After factory reset.
Also when I try to scroll down the web page in landscape mode it dosent work on the same area. So does this mean screen is screen is not registering my touch.
Some times the middle button start acting funny. It operates by itself even the internet is off. Like virus or some thing I did checked with antivirus nothing found. After activating show touch option it is shows Google shortcut is always pressed.
Dont know how to fix. Dont know the reason pls. Help. Xda.
Do you use dt2w? For me, after enabling that feature this would happen after a while. The borders of the screen would become unresponsive. I disabled dt2w, rebooted and it was fine again.
Sent from my Nexus 4 using XDA Free mobile app
Hi to everyone!
I have the same problem since some days with the nav bar on stock 4.4.2. Factory reset + rom flash via fastboot + CM 11 innstallation did not help at all. I'll bring my Nexus 4 today back to the retailer for reparation / replacing.
I'll inform you guys about the report of service center but it can take up to 45 days.
Thanks. This works for me
haris0032 said:
Before update to 4.4, I installed purity rom, and in purity system settings there was option to change navigation bar height. Default height is 48dp, but you can change to 52dp and the buttons working. Not ideal solution, sometimes you must to hit button few times, but it's working!
But, after I update my N4 to 4.4 kitkat, and install purity rom for 4.4, there is no option to set button height to 52dp (max heigth is 48dp-default height) I hope so that purity rom will be updated and return option to set to 52dp.
Click to expand...
Click to collapse
Hi, I was facing the same issue on my mako. It just started without any notice. Being a flashaholic I thought it could be due to something I installed. Tried a lot of differnt ROMS including stock but no luck. Read somewhere about the "Show touch" function in the developer options and found that almost 7.5mm of the bottom of screen was not responding to touch. I then installed the stock 4.4.3 ROM, rooted it and installed gravity box. In Gravity I changed the navigation bar height to 120% and selected "keep at bottom" for landscape. I am now able to use the phone. I wish some custom ROMS start implementing 52dp height option so we could use these directly. I tried using gravity with Mahdi ROM but there is some conflict and I cant see the recents button. Also, the NB reverts to original and it needs to be enabled again manually
But thanks anyways. I dont want to buy a new phone for the next 6 months and this will work well for me.
Cheers
Related
Hello there, Im having a weird issue with PIE, whether it's SLIMpie, PA's PIE or even LMT Launcher's PIE controls - I usually set my PIE trigger area at the Bottom, when triggering it it doesn't really work perfectly unless I trigger it from the very left side of the bottom of my screen, it doesn't really work well at the center and right bottom of it - Unless I set the trigger area as MAXIMUM.
If I set the default settings but on the Right or Left area, it works perfectly, is it a problem with my screen ?
And NO, I dont like the area to be maximumly triggered since it conflicts a little bit with the Launcher's dock, where it becomes a little slacky
Ensifolk said:
Hello there, Im having a weird issue with PIE, whether it's SLIMpie, PA's PIE or even LMT Launcher's PIE controls - I usually set my PIE trigger area at the Bottom, when triggering it it doesn't really work perfectly unless I trigger it from the very left side of the bottom of my screen, it doesn't really work well at the center and right bottom of it - Unless I set the trigger area as MAXIMUM.
If I set the default settings but on the Right or Left area, it works perfectly, is it a problem with my screen ?
And NO, I dont like the area to be maximumly triggered since it conflicts a little bit with the Launcher's dock, where it becomes a little slacky
Click to expand...
Click to collapse
Just because bottom part screen has the GOOGLE SEARCH. I mean when you slide your finger upwards from bottom of the screen the GOOGLE SEARCH ring appears..
Also check this. I am on Slim ROM,
the trigger gravity should be 75%
trigger thickness should be 40%
This settings is what I use and all working fine here.
Rohit02 said:
Just because bottom part screen has the GOOGLE SEARCH. I mean when you slide your finger upwards from bottom of the screen the GOOGLE SEARCH ring appears..
Also check this. I am on Slim ROM,
the trigger gravity should be 75%
trigger thickness should be 40%
This settings is what I use and all working fine here.
Click to expand...
Click to collapse
But the navigation bar is not even there i have totally disables it...pie works fine id i trigger deom left bottom...but if i try from center or right bottom...it doesnt show...unless i set trigger area to maximum...weirdest **** ever !
Sent from my Nexus 4 using xda app-developers app
Works fine for me.
It could be an issue with the digitizer on your touch screen.
Test:
Load the app "dev tools" and click on pointer location
Note that if activating pie it doesn't show the pointer tail so start in the center of the screen.
Drag from the center down to the bottom and drag it across the bottom end of the screen to make sure that you are actually getting touch detection at the bottom.
Sent from my Nexus 4 using xda app-developers app
I flashed PAC onto my Galaxy Note 10.1 just a few days ago when I ran across the PIE section in the settings, as I started toying with it I fell in love with how the nav bar was no longer hanging around the bottom all of the time, and I certainly liked PIE's interface better. However, ever since I started using the bottom 1/2 inch (interestingly about the size of the nav bar) hasn't been responsive to any touch input other than PIE. For example, if I was typing something, only the top of the spacebar would recognize a touch as a space, but the other, bottommost part would still operate if I swiped up to reveal PIE.
Is anyone aware of a fix to this problem, or is it just a tradeoff of having PIE, and this is just the way it is?
--John Galt from my GT-N8013
You can disable pie from the settings menu. You should also consider upgrading to 4.4 as JB is no longer receiving updates.
Well I know that I can disable PIE, but I want to know if the bottom of the screen not being functional is just something I have to deal with or if there is something that I can do about it.
I'm not aware of a 4.4 update for PAC for my device. I'm willing to try a nightly release, but I'm not sure how to tell what version a ROM is from the name of the .zip.
For example, what version is: pac_n8013-nightly-20140122.zip ? I can't anything except for "pac", "n8013" (my model no.), "nightly", and "2014".
The "0122" I'm not sure of.
Galt42 said:
Well I know that I can disable PIE, but I want to know if the bottom of the screen not being functional is just something I have to deal with or if there is something that I can do about it.
I'm not aware of a 4.4 update for PAC for my device. I'm willing to try a nightly release, but I'm not sure how to tell what version a ROM is from the name of the .zip.
For example, what version is: pac_n8013-nightly-20140122.zip ? I can't anything except for "pac", "n8013" (my model no.), "nightly", and "2014".
The "0122" I'm not sure of.
Click to expand...
Click to collapse
You can move the pie trigger to the side of the screen to see if you get the full touch screen back...
0122 is the date of the nightly build. Up to 0128 is 4.3 and from 0303 will be PAC-4.4
Sent from my ST18i using Tapatalk
Thank you for the clarification. I could be missing something, but there are no ROMs that have any release after 0128 (which I have now) for my device.
Seems like I'll have to wait for an update to roll around, but until then I'll keep playing with the settings and see if perhaps I have something not set properly.
Sent from my GT-N8013
Hybrid Properties
As I was thinking about the correlation between this problem and the nav bar, I realized that the nav bar was likely still active, but not visible because I clicked on the PIE fullscreen button in the quick settings. So I went to Hybrid Properties, clicked on interface, and set the "Nav. bar" slider to 0%, and clicked Apply. When that didn't work, I went back to that screen and found that the Nav. bar slider was all the way back at 100%. I've tried several times to get this to work, including adjusting the "Size" slider, clicking "Tablet UI" in the Launch screen and applying that, but nothing has stopped that slider from returning to it's default setting. Anyone know why this might be?
Need help as my phone became barely usable aftaer OTA update.
The top end of the screen (about 1 cm top to down) is not responding to touch. I cant tap any input in common use cases like using google search box widget, answering a call while in app using the new call feature, tap Send when composing an email and so on...
The only case this part of screen is active is when pulling down the notification bar, tapping objects like the clock (time display) Setting icon etc'. So I beleave this is not a hardware issue.
I did wipe the catch with no help and reset to factory setting with no help as well.
Did anyone experiance the same issue?
Any idea how can I overcome this except down grading back to 4.4.2?
Any easy trick for some one who is not a developer or deeply technical?
THANKS!
Hello all. Just yesterday my XT1575 started acting up, the navigation buttons - all three, Back, Home, Recents - are not working anymore. Initially, I thought it was a minor thing that could be sorted out with a reboot. I rebooted yet no show, still not working. I went to the extreme and did a factory reset, still no show. I fastbooted a fresh install, no show. I installed custom recovery and flashed a ROM, no show. But I made one discovery - in TWRP recovery the navigation buttons work just fine, and they are almost at the same location the main ones are on the phone screen when booted. This made me more skeptic if it was a hardware issue. As it is now I'm thinking of getting another screen to replace this one, but want to be sure this will fix the issue before shelling out more than $50 for a replacement screen.
Please all suggestions and advice is very welcome. I need to fix this. I love this phone. Thanks all.
maybe try to go to settings, enable dev options and then enable show touches
iks8 said:
maybe try to go to settings, enable dev options and then enable show touches
Click to expand...
Click to collapse
I also agree. Doing this will allow you to see if any key presses being registered when pressed in the affected spot.
Fix(?)...
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.
ezeuba said:
OK. I stumbled on a fix, maybe a permanent fix, maybe not... I rooted with BETA-SuperSU-v2.62-3-20151211162651.zip directly flashed in TWRP recovery, no need messing with extracting anything and all those long steps in a related rooting thread. Flashed Xposed (xposed-v86-sdk23-arm64.zip), installed XposedInstaller_3.1.1.apk and after all this, installed Gravity module for Marshmallow. Go to Navigation bar tweaks in Gravity, activate master switch, enable navigation bar and scroll down and then increase the height and width of horizontal navigation bar to 124 or more (124 is the minimum for things to work again). And, voila... The navigation buttons work again. I hope this helps someone with this issue.
Click to expand...
Click to collapse
Hi im having the same issue. How did yours happen? Mine happened after dropping my phone. Also I enabled Show Touches in Dev Options and the pointer would only go to the top of the nav bar and not on it even though my finger is on the nav bar.
I had this exact same issue with my Moto X Style. I was not willing to spend anything on this 3 year old device. Looked around for solutions but none worked. Finally settled for a 3rd party app which floats on screen, but very annoying. Found a commnet on a Youtube video who asked to change the display setting and it worked.
Settings -> Display -> Display Size. Change it from Default to large, larger or largest. It worked for me when I set Large. Just wanted to share it here, so it might help someone desparate.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!
jaboto said:
Hello,
I am suffering from a really annoying problem for the last month and I cannot find a solution. I have tried to flash several firmwares but the EPD navigation bar seems to become somehow irresponsibe making the phone quite unusable.
With LP EU (5.0.0-EU1.1.87a and 5.0.0-EU1.1.124b) the navigation bar on the EPD seems to be working on the YotaHub without problems, I can navigate and I can unlock the screen by either double tapping or sliding. However, when I enable the YotaMirror the screen is mirrored but the Navigation bar becomes somehow disabled so I cannot exit the application that is running. The only way is turning on the normal screen so the EPD goes back to the YotaHub (quite annoying).
With LP RU (5.0.0-RU1.1.124 and 134 sideload) the YotaHub works fine but when I enable the YotaMirror a message saying "YotaMirror mode is enabled" with a help message explaining how it works and two buttons "Skip" and "Continue" which do not respond to any action; making it impossible to leave that screen. The only way to get rid of this is going to the normal screen and opening the YotaHub settings. This error seems to be already reported by another user: https://forum.xda-developers.com/yo...phone-201-stuck-androis-5-0-ru-1-124-t3571739
In MM (EU and RU) the area of the Navigation bar, no matter if YotaHub or YottaMirror seems irresponsible to any actions; so I cannot move across the panels in YotaHub nor exit an application opened in YotaMirror.
I thought this could be a hardware issue but I have discarded the option knowing that in LP it works and in both LP and MM the double tap unlocking feature (once enabled) unlocks the screen even being tap on that area.
I will continue flashing firmwares and eventually come back to the version of LP that was working fine (I cannot recall which one was it so I am downloading and trying most of them). But any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Can you unlock the back display without doubletap? So by using the power button when the epd display is facing up. IE, does it still correctly sense which display is facing up?
Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...
jaboto said:
Hi @tomgaga Thanks for your response.
I can unlock the screen with in every mode: double tap, swipe and power.
I can fully confirm that this is not a hardware issue, meaning that the screen gets the touches as I have just captured the events with adb and saw how the screen gets the input event on the area of the screen "YotaMirror is enabled" that allows me to "Continue" or "Skip". So the taps are registered but it seems that this notification doesn't seems to work.
Anyone knows how to avoid this notification? I think this could solve the issue...
Click to expand...
Click to collapse
I had this problem when using gravitybox from xposed and made an adjustment to the navigation bar. You got any mods installed?
@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!
jaboto said:
@tomgaga , I didn't install xposed until now, I also tried to increase the size of the navbar with a mod but it seems to not doing the trick (I have the impression that the nav bar on the EPD doesn't get affected by this). When you had this issue did it go away by just removing the mod? Or you increased the size? However, I believe that after a full reset this should be gone...
Danke!
Click to expand...
Click to collapse
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.
tomgaga said:
Yeah if you reinstalled the system images and reset the data, then any mod should be gone, but not if you just did a factory reset.
And the problem went away after I removed the mod yes.
Click to expand...
Click to collapse
Hi again @tomgaga. The thing is that I reinstalled the ROM many times and I did full factory reset every time, so for me it seems there is an issue coming from somewhere else... Thanks anyway for your comments.