Database Users

[Q] Navigation buttons not working after 4.4.3 update

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

Fingerprint Sensor issue

Loving my Zuk, or was. I set up the screen lock for fingerprint sensor and it was working great. Recognises my thumb first time every time. Now though I can unlock with just a normal swipe. It doesn't even demand the backup pin number. I went back into settings and it still had the fingerprint setup as the screen lock so I removed it and set it up again and hey presto i was back in action but only for about 10 minutes and it went back to no security at all.
There were 4 small OTA updates today so I am guessing one of these has messed it up. Each update didn't say what it was for
Has anybody else had this issue?

Is working well for me.
Have you added other smartlock event (wifi, location, ecc) that can interfere with the lockscreen and disable it?

bartito said:
Is working well for me.
Have you added other smartlock event (wifi, location, ecc) that can interfere with the lockscreen and disable it?
Click to expand...
Click to collapse
My MOTO 360 is in smartlock as a trusted device, don't fully understand what smartlock is to be honest. If I remove it would it affect anything?

gibmonkeys said:
My MOTO 360 is in smartlock as a trusted device, don't fully understand what smartlock is to be honest. If I remove it would it affect anything?
Click to expand...
Click to collapse
Of course!
I have also a smartwatch (LG Urbane) and the watch as a trusted device. When the smartwatch is connected to the phone the lockscreen is always DEACTIVE, even if you have configured a lock screen (PIN, pattern and or fingerprint)
Power off your watch (or set if in airplane mode) to check if lockscreen turns on in the phone

bartito said:
Of course!
I have also a smartwatch (LG Urbane) and the watch as a trusted device. When the smartwatch is connected to the phone the lockscreen is always DEACTIVE, even if you have configured a lock screen (PIN, pattern and or fingerprint)
Click to expand...
Click to collapse
I have just removed my 360 as a trusted device and the screen lock now works perfectly and so I now understand how this works. Many thanks for the advice. I can now stop worrying that I have a faulty device!

gibmonkeys said:
I have just removed my 360 as a trusted device and the screen lock now works perfectly and so I now understand how this works. Many thanks for the advice. I can now stop worrying that I have a faulty device!
Click to expand...
Click to collapse

I am facing as well to a lockscreen and fingerprint issue.
I used fingerprint to open lockscreen and pattern as secondary. After showing the ZUK to somebody I needed to modify the pattern. From that time I am unable to switch back to fingerprint. Only three opportunities what I have, and no swipe or fingerprint, due to "Disabled by administrator, encryption policy or credential storage". What accessibility service messes up the fingerprint usage? Do you guys have an idea? All of them are swiched off.
---------- Post added at 01:17 PM ---------- Previous post was at 12:22 PM ----------
My problem is solved. I needed to delete credentials in security settings.

Hi. I'm having some problems with the fingerprint sensor. Is working intermitent or not. I've asked zuk support already but no answer yet. I don't know if it's a software issue or hardware. It's any way to calibrate the sensor? Maybe it's decalibrated? Any help will be usefull. Thank you.
LE I already made a factory reset. No improvement.

Cmdragan said:
Hi. I'm having some problems with the fingerprint sensor. Is working intermitent or not. I've asked zuk support already but no answer yet. I don't know if it's a software issue or hardware. It's any way to calibrate the sensor? Maybe it's decalibrated? Any help will be usefull. Thank you.
LE I already made a factory reset. No improvement.
Click to expand...
Click to collapse
I'm using the Zuk since a month, and no problems with the fingerprint at all.
In any occasions, the fingerprint sensor don't detects the finger the first time but at second try.
Since a few days, I'm on CyanogenMod (instead of Cyanogen OS) and I think the sensor is less responsive (sometimes I need to try three times or use the lock pattern).
But if you are with issues using CyanogenOS I think is due to a hardware issue.

bartito said:
I'm using the Zuk since a month, and no problems with the fingerprint at all.
In any occasions, the fingerprint sensor don't detects the finger the first time but at second try.
Since a few days, I'm on CyanogenMod (instead of Cyanogen OS) and I think the sensor is less responsive (sometimes I need to try three times or use the lock pattern).
But if you are with issues using CyanogenOS I think is due to a hardware issue.
Click to expand...
Click to collapse
I can not use the fingerprints touch button as back button anymore. this happened after last update cynogenmod. any knowledge.
thanks.

sadrettin said:
I can not use the fingerprints touch button as back button anymore. this happened after last update cynogenmod. any knowledge.
thanks.
Click to expand...
Click to collapse
Fingerprint actions has been removed by CM a few OTA updates ago.
I hope a kernel developer will add soon, but ZUK has not too much developers

Modded kernel for COS can be found in the other topic about this issue.
The OnePlus 2 sources happen to have a compatible finger print driver with capacitive button support which is currently being checked out for porting to the Chroma kernel.
So don't fret.. The feature can be restored.

iam not able to use my fingerprint lock, it was working well before but now suddenly it is not showing the option in CHOSE LOCK SCREEN- the SWIPE an d FINGER PRINT OPTION IS DISABLED.
how to enable it

Thanks ... I had the same issue & delete credentials in security settings.

I bought zuk z1 3days ago
Why We cannot use fingerprint sensor to lock and unlock the device for both purposes

Having an issue with the fingerprint sensor.....
Works fine but when push notifications(any notifications**) show up on the lock screen ..the sensor gets non responsive...mind u almost impossible to unlock
Have no choice other than security pin
And I Definitely think this is result of All IN ONE Issue
Say like.....1)fingerprint sensor integrated into hone Button, 2)Faulty software patching, 3) Me, adding two or more fingerprints
Any Suggestions from u guys Feels helpful
BTW....Bought the product via Amazon.in

Is there a provision in the ZUK Z1 which let's you interact with the device by simply tapping on the fingerprint sensor except on the lock screen?
If the device is locked and the screen is off too, simply placing my hand on the fingerprint sensor doesn't work. I always have to press on the button to wake the screen first.
Any help?

May sb tell me the modell of the finger print reader of the ZUK Z1? Pls. use AIDA64.
Gesendet von meinem Aquaris X5 Plus mit Tapatalk

@infistuff said:
Is there a provision in the ZUK Z1 which let's you interact with the device by simply tapping on the fingerprint sensor except on the lock screen?
If the device is locked and the screen is off too, simply placing my hand on the fingerprint sensor doesn't work. I always have to press on the button to wake the screen first.
Any help?
Click to expand...
Click to collapse
That's part the of custom roms. Fingerprint as home button can be activated by flashing something, you need root. But in the play store you can try https://play.google.com/store/apps/details?id=com.ztc1997.fingerprint2sleep
But it's not that what you need. Without root and a kernel where its implemented its not possible.

Hey my fingerprint was working fine till one day it just started vibrating when I tried to scan it. I tried deleting the saved fingerprints and registered new. I'm not even Able to register new fingerprints. What do I do?

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

Screen rotation lock doesn't work on MI A1

After I rotate the phone and then toggle OFF the rotation button , the screen automatically rotate back to normal position, instead of remaining locked in horizontal position, and yes- I keep the phone physically rotated on its side the entire time
The phone is rooted with magisk, if it matters
What could cause this problem? I already tried to reset and disable developer options, which btw, would it make an issue booting the device if OEM unlocking won't be ON ?
-to make it clear - the screen rotation functions well when rotation mode is on, I just can't keep it in horizontal position
Thanks in advance

That's not a common error.
On both mine and my GF's A1 that setting works.
EDIT:
I just can't keep it in horizontal position
Click to expand...
Click to collapse
That's correct: You can't 'lock' screen to horisontal position!
Both untouched Android 8.0.0 April patch.

I thought this was normal behaviour for stock android? I understood only certain manufacturers allowed rotation lock in their ROM's like LG?
FYI: My stock A1 on April 8.0 returns to Portrait when rotation is turned off.

That's not an error. It's just how Android is designed to be.

DetmL said:
That's not an error. It's just how Android is designed to be.
Click to expand...
Click to collapse
kudos1uk said:
I thought this was normal behaviour for stock android? I understood only certain manufacturers allowed rotation lock in their ROM's like LG?
FYI: My stock A1 on April 8.0 returns to Portrait when rotation is turned off.
Click to expand...
Click to collapse
JockeSve said:
That's not a common error.
On both mine and my GF's A1 that setting works.
EDIT:
That's correct: You can't 'lock' screen to horisontal position!
Both untouched Android 8.0.0 April patch.
Click to expand...
Click to collapse
On other android phones it's not the case, you can lock it on Samsung S8(oreo), Samsung S1 (stock) and on S1 with CM mod
Perhaps it was possible with the MI A1 before some of the latest updates too,I'm don't really remember, anyway, Xiaomi should return this function because it's useful and already exists in older and newer android phones WITH stock versions