U-touch reseting actions byitself and screen rotation stops working etc... - Lenovo ZUK Z2 (Plus) Questions & Answers

I have run into a strange behaviour with my Z2.
I've now tried 2 cleanly flashed ROMs (AICP and RR) and with both I get the exact same issues:
Every now and then U-touch functions seem to reset to some predefined actions without the settings itself being changed nor is the keylayout file changed:
Tap is back, press does nothing, double press opens camera, swipe left does nothing, swipe right opens menu. Screen rotation stops working as well and advanced reboot options are gone as well. There might be other issues as well but when ever I run into the previously mentioned issues I just restart the phone and all settings are back to normal.
What could be causing this? It does not seem to be a hardware issue per se, as I would imagine the touch button would to stop responding altogether. Now it just resets to some weird predefined actions.
Could this be about the baseband ppl seem to be mentioning everynow and then?
I've attached screenshot of my baseband.

This has something to do with the "system profiles". I have been using them once I understood how handy they are.
I just got the bug again when my profile changed from "default" to "home". I changed back to default and disabled the whole profile system and my screen started to rotate and u-touch actions returned to those that I have set.
Is this "system profiles" thingy a CM/LOS feature? Where should I nag about this?

This is indeed a LOS14 issue.
Faster workaround than rebooting is to switch wifi off ( or what ever is the trigger u got) and lock and unlock the phone one time normally and then activate wifi to enable "home" profile again.

Related

[Q] Problems with 5.1.1

My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.

Home button continues pressing?

I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
the only explanations i can come up with are:
-accidental touching the area in some way (unlikely)
-getting some substance stuck on the screen in that area (unlikely)
-a faulty touch panel (unlikely and very specific defect)
-a hickup in the software (again unlikely)
then again, if the OS (for whatever reason) thinks the home button is pressed, on default it should not only pull you back to the homescreen, but continue and send you right through to google. the conclusion of which would be, that this UI area is triggered repeatedly rather than continuously.
keep an eye out for what could have triggered it in case it occurs again.
check your settings what build exactly you are running (settings -> about phone -> build number).
ans lastly, if it happens again, you should still be able to hold your power button to hard-reboot it (no further interaction with the UI required).
RockinAmigo14 said:
I've had this issue before on my LG Power (Straight Talk branded LG Leon), running on Lollipop 5.0. No matter what I look for I can't find anyone who's experienced similar issues.
It just happened last night on my 5-day old Nexus. I could not open any of my folders to access apps. As soon as a touched a folder, it briefly showed the animation to open it, and it immediately closed. Whenever I selected a widget or the app drawer, they would immediately close as well. When I attempted to swipe down the notification/quick settings shade, they immediately closed themselves. Turning off the screen resulted in the screen immediately turning back on, albeit locked. I was even having trouble turning the device off because the 'Power Off' menu would disappear right after it popped up. Eventually I was able to time it right and was able to power off. Since I restarted I have not have any issues.
Any idea what gives? I'm unrooted, locked bootloader, everything 100% stock, running MM 6.0.1.
Click to expand...
Click to collapse
Try to clean your screen also with a towel
That is extremely weird. It really sounds like a faulty digitizer, but you'd be the first... Maybe it's a rogue app, but unlikely.
Were you doing something before this starts to happen?
I haven't noticed any consistent apps or behaviors when this would occur. This most recent time, I was low on battery (10%) and I had just flipped on my data.
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
dpj52190 said:
fyi. you could also just press and hold the power button, for 10 secs, for a reboot ( might come in handy when the screen isn't working properly).
Click to expand...
Click to collapse
appreciate the tip! I'll keep this in mind if it happens again.
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
RockinAmigo14 said:
Finally was able to capture a video. The issue occurred after I was playing around with Open Camera and it crashed. Holding down the power button didn't work when this glitch is happening.
https://youtu.be/4n5vzXlUPqM
Click to expand...
Click to collapse
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What's the icon on the lock screen, top right in the status bar? That behavior is unusual if it's not a screen defect. Are you using any apps that monitor battery, a task killer, or maybe a security monitor app?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
The icon is a picture for my user profile on the phone.
I don't use anything like that. I had Clean Master installed briefly but it's been uninstalled for a couple of days now.
so it seems like this issue pops up whenever the camera crashes. happens occasionally when using the camera shortcut (double power tap) or in an app that uses the camera.
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
exninja said:
It's got to be software IMO. It didn't happen when you went to Google Now and your Recent Apps. I'd try uninstalling the Open Camera app first. Do you have Face Unlock active by chance? After that I'd FDR...
Click to expand...
Click to collapse
right, that's what's confusing me. i did a factory reset last week, set up the phone as a new device. haven't installed a new camera app, just the stock google camera. the issue occurred again last night when using an app called Shopkick, which accesses the camera but crashed.

Screen lock

Hi,
Under screen lock I marked swipe.
It stopped working.
When I press the lock button, the screen just appeared like the none option is marked although the swipe is marked.
I have tried the following:
Restart
Shut down
Change user to guest
Clear credentials
Change to password and change back
After changing to password go to smart lock and make sure there are not trusted places
After changing to swipe the smart lock option is grey like it is set to None.
Any ideas?
Thanks
I recently updated to the latest ElementalX kernel (1.15) and am experiencing the same issue, lock button doesn't lock or wake up screen, gestures work fine though.
Edit: After hard resetting the lock & wake functionality is back to normal!

Tilt-to-wake broken in recent update

Recently (last week or two) tilt-to-wake has stopped working, and the option to enable it no longer exists on the on-watch settings menu.
The toggle for tilt-to-wake is still present in the Wear OS phone app (under Advanced settings) but even when on, the tilt-to-wake functionality no longer worked. The only way to wake the watch is to tap the screen or press the side-button.
Anyone else noticed this? It is driving me mental!
Cheers
Uhh... scratch that. After rebooting watch, new Google App was installed and it is back to working as normal! Should have tried that first.

Question Lockscreen not always showing

The problem:
I will hit the power button to sleep the device. I have fingerptint/pin set as my lockscreen. My lockscreen wallpaper and home wallpaper are different, so the issue is easy to see. I sleep the device, then anywhere from 1-30 seconds later I hit the button again to wake it. Instead of showing the fingerprint scanner and my lockscreen wallpaper, it shows my home wallpaper, with the small gesture bar at the bottom. There are two ways to get past this, swipe down from the top for the quick tiles and then swipe them back up and the lockscreen wallpeper and fingerprint scanner shows. Or I can hit power to sleep and then power to wake again and my lockscreen is there.
I thought the issue was with the kernel at first because I hadn't noticed it outside of installing it. After flashing to stock kernel I noticed it happening again. It happens once every 5-10 wakes. It's not super annoying, but still annoying.
I have tried backing up and restoring everything from Google One, then rooting, then with and without a custom kernel, still the same issue.
I have also tried backing up and restoring all my data through SwiftBackup. For apps I backup all user app data parts: APKs, Data, Ext. data, Expansion, and Media. (Not sure if I even need to but certain games etc I don't want to lose data). After I restore I use the same Magisk 24000 to patch and flash the boot.img.
No matter what I've tried, the issue still seems to persist. If it helps, I am on Android SP2A.220405.004
If anyone might know what is causing this or how I can fix it, that would be great. Thanks!

Categories

Resources