hi,
just recenly when using aamirror with my android auto unit some strange bug seems to have happened and i still couldn't figure out how to fix the problem. let me explain:
it seems whatever i do, the bottom 0,5cm of my screen (above usb-c connection) seems not to response to any touch event within the android system (on my phone - without using android auto connection obviously)
i've tested...:
- bottom touch works fine in twrp
(makes me believe it's not a hardware issue)
- whatever the orientation (if menu is bottom, or status bar) touch will not be recognized
(in android)
- menu buttons are working fine when 180° reverse
- menu buttons work though touch simulation (scrcpy)
- i noticed it right about when having some issues with aamirror somewhat lagging my phone
so generally speaking i could only think of something intercepting the touch events.
i also tried removing both apps, rebooting, dirty flashed another update
with and without plugging it into android auto again and again.
what could be the problem??
Related
I just upgraded my Rom for the x time, this time my touch screen will no longer work in landscape. I downgraded to a ROM that used to work, and on that ROM my touchscreen also does not work in landscape mode. Is this a software thing or a result of throwing the phone against the wall to many times? i guess it's time for an 8525....
Any ideas how to get the touchscreen working again?
e.
same problem for me !
It's not switching to lanscape? While opening keys? Or just turning off?
If it's able to be switched with software way (Settings -> Screen -> Landscape), then this is a hardware problem.
Wizars has a magnetic sensor to detect keys sliding, try to check it (use an external magnet).
If screen turning off after sliding the keys, the flat cable is damaged.
Hi there,
After flashing my TD with panosha's Shine On 1.9, I experience some strange behavior:
When the TD is in standby (i.e. touchscreen off) and there is an incoming call, the display turns on but the touchscreen remains completely unresponsive, i.e. it neither responds to "Answer", "Ignore", etc., nor to "Start" in the upper left corner.
And that is while the device is definitely unlocked (I don't even use the unlock function as I switch to standby as soon as I don't need the phone).
In fact I can answer the call with the hardware button only - in that case the connection establishes, but the screen goes blank.
If the device is not in sleep mode, everything works as it should.
I have tweaked several settings with both Advanced Config and Diamond Tweak, but in my opinion none of the tweakings applied might cause such a behavior.
Thanks for your ideas .
ROM contains:
Answer Key Disabler v0.3.1
Hey, thanks so much!
It wouldn't have occured to me that that is in fact a desired feature of that ROM, therefore I didn't even consider re-reading its thread.
lol i think people need to start reading about the
stuff there putting on there phones.
Strange problem that might be a common issue. I have just gone through the process of installing Android on my TyTN II and the android system itself is working fine. Although for some reason, when the screen goes off (after screen timeout) when I push the power button to wake up (and then unlock) the device the screen just comes on as a big white screen (no image, almost as if im using the screen as a flashlight or something).
I have tried 2 different android ROMs now and it happens with both of them. Anyone got any ideas?
Zeb
This has now been fixed by changing the panel type of the display from Auto to "1" in the kernel and re-flashing.
Recently updated to 6.0.1 on my LG Urbane watch. Everything was working fine for about a day and half. Then I noticed some sort of glitch on my touchscreen. Specifically the middle area. I turned on show touches in developer option and everytime I tried touching the middle, it shows an off touch a bit to the side.
I did a factory reset. Still the same thing happens. It is also affecting some apps. In LG Pulse, I am not even able to press the start button to monitor my heart rate, unless I press it a bunch of time in and around the play button.
I tried to reflash it through adb loader but on the bootloader or recovery screen, the touch screen stopped working. I can not pressed the selection or confirm buttons at the bottom.
Does anyone know any way to fix this? Is it a software issue or is there something wrong with the touch hardware on the watch?
Hello ! I need help for a specific issue i have never heard happening on an android phone.
I have an Exynos S10e and the task/app switcher becomes partially unresponsive in specific conditions.
When the app switcher just appears, if i try to swipe somewhere (swipe to the side or swipe up to close an app) mid-way through the swipe, the screen suddenly stop recognizing my finger, i have to lift my finger and touch the screen again for it to function. Basically, i have to interact with the screen after the hardware layer updates to avoid this problem.
This issue only appears after the screen has been locked once in the session.
Basically if i reboot/shutdown my S10e, access my launcher and fiddle around with the app switcher, everything is fine. As soon as the screen locks and i unlock it, the issue reappears.
The problem exists with both the stock app switcher and the "task changer" from Good Lock. Also exists with both OneUi and Nova Launcher. I tried a lot of things and i'm up to date on the security updates, etc.
I wiped the cache partition, tried with and without the Always-On-Display, and that changed nothing.
Anyone experiencing the same thing ? Or a solution to suggest ?
(The issue also exists with my old Nexus 5 but the time window allowing the glitch to occur is extremely narrow.)