Back and Recents Buttons Disappeared / Not Working? - HTC U Ultra Questions & Answers

I have noticed that my back and recents buttons seem to have stopped working. I had them set so that they were always lit up but they've disappeared.
Has this happened to anyone else and did you manage to fix it? I've looked through the settings and can't see that I've changed anything.
Currently running Action Launcher.
I have noticed that if I touch the Home button briefly, when using the Sense launcher, two small symbols appear briefly - a "b" and something else... Have I accidentally engaged some accessibility feature unwittingly?
ETA: I properly switched it off and restarted it, and the buttons reappeared, lit up as expected. It was a bit of a worry though. Hopefully this will not reoccur.

Related

Odd rotation behaviour

OK I've had this happen to me for at least three days now and it's finally to the point where I'm posting to see if anyone else has experienced it. I use the Vega in landscape virtually all the time and because of that I lock it in that orientation. However, once or twice an hour the screen will briefly flip to portrait (power button would be on the left in that orientation) then back to landscape. It's very brief and as I said it flips back just as quickly but it's very annoying. It has happened while watching videos too which is more annoying as it takes longer than a browser to change orientation while playing.
I've tried recalibrating it, rebooting the tablet and everything short of reflashing the ROM. I'm really hoping to avoid reflashing to test it as I've finally got the screen calibrated to an almost perfect level thanks to the other calibration app on the MoDaCo forums. Has anyone else had this behaviour before? If so, have you found a fix?
I do not have your exact problem but something similar. Just now I picked mine up and screen was upside down (when the device was right side up i.e. buttons at top and right). I checked the rotation button and it was not locked. When I rotate the device it will not switch rotation at all - when I go into settings and turn off auto-rotation it flips right-side up. It seems like the accelerometer is knackered but it would seem to be working in order to flip it when auto-rotation is switched off. The daft thing is that in various screens it flips to being right side up. It boots up the right way round and the lock screen is the right way round but as soon as unlocked it flips upside down. I too have tried rebooting and all sorts - thinking of flashing it as a last resort.
I seem to have fixed this now. I use quickboot and on a whim rather using my reboot shortcut I used power off. I then used the power button to start up with the rotation lock switched on - when I turned it off once booted it was back to normal. I suspect the rotation switch bit was a red herring - I reckon the shutdown/restart fixed it.
settngs>g sensor>games mode can cause some accelerometer antics try turning on and off
What does the gsensor mode do when activated, as I haven't seen any difference?

[Q] Home button stops responding

Beginning with 2.3.4 Launcher Pro, with sporadic frequency, ceases catching the home button presses.
Pressing it during this phase just causes the screen to flicker black.
This has been evident in any ROM I use (Currently Home Base) and this is even the second device I have owned to display this symptom.
If I do a little dance and any combination of resetting its settings, clearing data, clearing defaults, reboots and changing launchers around it will begin to work.
It doesn't usually start during an on state when it's functioning correctly, it begins at boot.
Anyone else experience this?
[Edit] Using an "Extended Controls" widget that includes the auto lock toggle is the cause of that behavior. Toggling on/off the auto lock causes the behavior to cease.

4.2.2 notification bar problem

OK. To start with, my OTA didn't show up so I force stopped and cleared data of one of Google's services responsible for holding the OTA information. After that everything went smoothly. However, I noticed that my notification bar behaves just bizzare. When I'm trying to pull it down, it sometimes goes down, and sometimes just goes up (this only occurs when pulling down with 2 fingers). Now, it just stopped scrolling down at all... No response, totally. The screen is all fine, testes that in touch localization in menu. OK, after restarting the phone, it works again. With being pulled with only 1 finger everything is fine, but with 2 fingers it still glitches somehow. I wish I could go back to 4.2.1 now...
PS. Am I the only one that noticed there is no voice calls and ringtone volume control in lockscreen?
I'm on 4.2.2 (ota update). No major problems with the notification bar but it just doesn't feel as smooth as it was on 4.2.1. A bit jerky at times.
i noticed that too, but if i pull it down slowly it gets stuck right up to the part that shows the date, if i pull it down like i normally do, it's just as fast.
is this the issue that you're seeing or is it something else, try pulling it down quickly with your thumb
hope this helps
I had this issue when I flashed one of the versions posted in the Development section. I just flashed the official stock image and no longer have this issue.
Sent from my iPad using Tapatalk HD
im not on official rom on PA but the volume controls dont work in lock screen unless your playing music which is only for music volume,
thanks for the 2 finger pull down, i didnt know it toggles the shortcuts pane.

Moto X Style On Screen buttons not working

Some basic info before i begin:
Phone: Moto X Style/Pure on android 5.1.1 (XT1572)
It is rooted, but no custom roms are installed.
So basically what happened was I dropped by phone, then all of a sudden the on screen (Home, Back and Multitasking) buttons started to become unresponsive and started ghosting. I have restarted so many times just to exit an app. After several restarts, my on screen (home, back and multitask) buttons have stopped working.
Firstly my basic and short term solution was to install a 3rd party on screen button app from the play store, this would put a second set of on screen buttons above the stock on screen buttons. But before this I noticed that the on screen buttons actually worked when rotated so that instead of being on the bottom of the screen they would be on top. The on screen buttons also work when i boot into recovery mode, my custom recovery is TWRP. I also wiped dalvik cache and reinstalled my apps through the recovery setup.
I dont know whats going on, I even made it so that when my on screen buttons moved to the top of the screen, i would click on apps from the bottom of the screen and it would work. It doesnt seem to be a hardware issue as i have confirmed it to be working through TWRP and tapping on apps from the bottom of the screen, confirming that my touch screen is working perfectly. The on screen buttons also work and it being detected when TalkBack is enabled.
Help me plez.
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
valest said:
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
Click to expand...
Click to collapse
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Houndz said:
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Click to expand...
Click to collapse
The touch screen issue of this device is hardware related, born with such flaw, you will have it even you didn't drop it.
No sure how it happened, but it helps if you can take it apart and clean the connector a bit and make sure you reconnect it firmly, if that doesn't work, you will have to replace the touch screen part or the whole screen and touch screen and rear frame and stuff, but do notice: it's likely to happen again.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049

Some parts of the system lost their functions

Hello,
There is this weird problem that came out of nowhere. I usually sleep listening to music and sometimes I weak up with the phone battery completely drained so I have to charge it. Today after charging the phone some parts of the system lost their functions. These are the problems I discovered so far;
-The home(LeEco) and the multitask buttons are not doing their main functions even though the phone registers the touch inputs from the buttons and they light up. The home button can even lock the phone on long press but won't take me to the home screen.
-I have the swipe shortcuts button enabled but it won't take me to home screen or multitask screen. The "go back" option, however, is still working along with the back button. I can go to the home screen by swiping or exiting apps with "go back" button.
-I can't download apps from google play store even on wifi with auto-update enabled. it's stuck on download pending.
-I can't open the notifications management from notifications.
-Connecting the phone to my PC does not show connection options.
-Screenshot doesn't appear in the notifications. The notification area remains empty.
So far these are the ones I discovered. Do you have any idea what causes that and how to fix it? I didn't do a factory reset yet as I can't transfer the data to my PC. Eui 5.9.026S I haven't had any of these problems up until this morning.
Thanks in advance.
Backed up data using an app and factory reset solved the problem.
The actual problem seemed to be:
1-The multitask screen virtually opens but it appears behind the background aka it doesn't actually appear. I think because whatever app that is responsible for it does not have the draw over other apps permission(?).
2-The notifications are there but does not appear in the notifications bar menu. I made sure by using the a notification history app. So it might be notification access permission problem(?).

Categories

Resources