Hello,
My spice android one mobile having marshmallow was working smooth... and all of sudden On-screen soft keys (navigation keys) home - back - overview stopped working...
But there is no damage to the screen - touch screen is working fine - when i rotate the phone and soft-keys move to different side then it works - but not in vertical mode...
Not finding any solution for it...
Please help anyone....
Related
im trying to find out if this problem is software or hardware related. it seems the issue only appeared at wm6.1 and wm6.5.. it works fine in android, and works fine when you hold your finger on the screen while you slide the phone open.
does anyone else have this problem with wm6.1/6.5?
No problems using the touch screen with my Touch Dual, 20 key, with the slider open or closed.
weird
maybe it is hardware then
hello XDAexpertes
I have one of this Chinese phones that looks like want to go holidays forever, specifically a Star A3 (Mtk6575)
things is, for few days, soft keys start intermittently stop working, it did got funny because as I take out the back cover they work again, also, the screen protector was little dirty, so I took it off ...
but things have become worst, and up to the point to do not respond at all, but only soft keys, touch screen works perfectly. More over, and this is happening more and more, ghost strokes of the soft keys have start to appear
so I guess, touch screen has got wet(?), fail(?), nuts(?). Anything I could be doing to repair it ?
But my main question is:
- is any way to disable the soft keys (to prevent the ghost strokes) and enable some app to emulate the menu and options soft key (maybe shaking the mobile)
I just need it to make it works for sometime, so I am not without mobile up to purchase a new one.
It is funny, as the soft keys seems to be part of the screen it self, and not separate buttons or anything else. and the touch screen works, while the soft keys do not ...
Hi all,
New here, just want to find an application (or an Xposed module) that "down" by some pixels the touch trigger for my notifications panel, as the top of my touchscreen is unresponsive (a top row of about 2 pixels ,the screen is perfect) and i can't pull down the notification bar, it seems to be a problem with the digitizer (this is strange as the problem appears just after my update to 6.0..) i read many forums and this seems to be a commun issue with many users, note that the notification panel is accessible when phone is in portrait mode, will be
Thanks in advance for your help .
Device : LG G3 D855 (rooted)
ROM : 6.0 Stock
My phone fell down before 2 days and from that time onwards the hadware navigation keys are not working. Everything else is working fine in the display. I tried flashing official MIUI global or developer rom, still it is not working. Currently I am using on-screen navigation keys. Any solution guys?
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
robjg63 said:
I have been running my Tablet Z (pollux_windy) on the latest Oreo release (15.1) . Have installed a few nightly updates - but the problem below keeps occurring.
It generally runs really well - but I have discovered something that seems to be causing issues for me and wondered if anyone else has the same issue.
I like to use the full real estate of the screen, so found the Settings/Display/Expanded desktop setting that lets you hide the top status bar and the lower navigation keys go into autohide mode (you swipe up from the bottom of the screen to see them).
First time I enabled them all seemed great - Then I left the tab and the screen timed out.
I tried to wake it up (using the power button or double tap on the screen) - Nothing.
Tried this quite a few times over a few minutes.
Did a Hard power off.
Restarted eventually. Seemed ok until the screen blanked out - then the same as above.
I did eventually get the screen to wake back up without a reboot by trying the double tap and quick press of the power key. But it took quite a few attempts.
Finally I turned the full screen mode off (ie brings back the status bar and nav controls) and everything was back to normal behaviour - ie always wakes back up when required.
I have tried changing the expanded desktop mode several times and it always locks things up after the screen times out so have now given up on it.
Anyone else finding that setting this mode causes lockups?
Click to expand...
Click to collapse
Hello!
Please write your problem to an official bugreport https://wiki.lineageos.org/bugreport-howto.html to let the LOS developers team about the encountered issue.
Thanks. Signed up to add the fault and found someone witha different device reporting the same bug around a week ago.
Added my confirmation of the problem with different hardware.
Fingers crossed someone may have a look at it when time allows.