I am encountering strange touchscreen locks. They occured first with Google Navigation amd always after approx. 20-30 minutes of permanent display usage.
It looks like I would tap on the screen (I see the maginification buttons clicked in the lower right corner), but I cannot go back, because the screen does not react anymore. I have to use the power button twice to get it back to work, sometimes even that does not help. Imagine you want to stop the Navigation software (which is still talking) but you cannot...
This happens also with Navdroid, but the software seems not to be hindered as much as Googles Navigation. In any case, the screen does not react to touch anymore.
I also found this to happen after a longer telephone call, the screen does simply not react anymore, but still shows everything.
I had this effect with Megatron, Void, Prime, Miks CM7 and Andys Gingerbread ROMs, so is this then a hardware or a software (driver) issue? I cannot remember having that with the stock ROM, but that's a long time ago
With the Gingerbread ports there seems to be a problem with the screen after calls but am not too sure if thats the reason for ur problem as u had the same with Froyo.
I am on stock rom and i dont have any such problem. And i have never heard anyone else having the same problem. You could try wiping everything and then flashing a froyo rom again. If that doesn't work, it might be a hardware problem.
In case you do need to send it in to LG, you will have to revert it back to stock condition. When you do that, check if this happens then too.
Sorry if posting in the wrong forum, I cannot find a forum dedicated to the Desire VC but I think it is quite similar in any case.
My girlfriend's phone is exhibiting an extremely frustrating problem wherein the keyboard doesn't respond to presses. Occasionally it starts working again for a short time then simply stops again in the middle of typing a message. The problem is present across multiple applications, including "People", "Messages", "WhatsApp" etc - I presume anywhere where the keyboard is used.
Closing and restarting the app doesn't work. Sometimes just waiting for a few minutes will see the keyboard working again. More often than not the problem persists even overnight, but then will just suddenly "go away" and the keyboard suddenly works again.
Everything else works but is slow.
It seems the problems started after an update about a week ago.
The software is Android version 4.0.3 and HTC 4
Any suggestions?
Keyboard
Same problem I was facing a month back. Changed the phone.
First i noticed that whenever i chat with someone over messenger, it starts calling them randomly while i type.
I thought it's about messenger and i cleared the cache and reinstalled it. Problem is still occurring.
Later, i noticed in one game that screen does that touch again - on the very same spot as in messenger - somewhere in the top right corner (where's the call button in messenger).
I turned off the phone, waited 2-3 minutes and then turned it on. Problem is still occurring.
I started service "thing" (found on the internet what to type in the dial to activate it) and tested the touch screen, everything seems to be okay. So from my experience it seems it's not hardware problem. Do you have any suggestion or experience with this kind of problem? I wish i could fix my phone
And one more thing, it happens only when i'm touching the screen too, it wont do that when i leave it alone and just watch the display.
Hello,
So it's 6am here in the UK, and I went to check my phone as I'm waking up to find that the screen is acting up! It's been unplugged all night, and the night before I was searching google before just locking it and going to sleep. Before locking the phone, one of the web pages (atleast what I believe) was acting up, causing *their* page to make this weird grey, green and red lines over a chart I was looking at. I took no notice, went to sleep.
Turns out it's not the web page: scrolling in google, and most other apps now (including the settings) causes this weird glitching to occur.
Pretty much any UX and UI scrolling causes this, with the only solution being to close the app - it locks up the phone while the glitching animation occurs.
Any screen shots I get now are completely grey - really odd!
Thank god I am still in my 14 days - going to send it back.
What do you guys think? Return the device and get a different handset all together, or try again with the Mate 20 Pro? Happy to experiment with this if any of you want to know more.
Videos:
Scrolling through google: streamable.com/wnjq8 (Big problem)
Scrolling through reddit: streamable.com/hdh3u (fineish)
Scrolling through settings: streamable.com/1oyhl (Oh dear...)
*****EDIT******
So my phone specs are as follows:
Mate 20 Pro 128gb 6gb edition /w a 128gb nano sd card
Model: LYA-L29
Device: HWLYA
Some settings I had enabled when this first occurred:
I had the screen set to WQHD+ instead of the Smart resolution: since turning this back on, I have noticed the bug to occur less, but still occurs.
I usually have the notch set to default, as I quite like it, but since this has occurred, I have got 'hide notch' enabled
I do have the on screen display setting so I can see the clock when its locked.
I have restarted the device many times, sometimes I restart, I notice the gluegate issue, but it never occurred while using the phone, only while shutting down (green edges)
Chrome seems to be one of the main apps this occurs on, particularly when scrolling - It can even crash chrome too. Oddly, reddit seems fine.
When closing apps via the bottom right corner and swiping up, this bug has never occured.
FYI I've only had the device for about 2 weeks, (just under thankfully) so I'm hoping the new handset doesn't do this!
So I closed all the tabs on the phone, and also enabled 'eye comfort' mode (should have really done this one at a time) and it seems to have cleared up the issue in everywhere but chrome. It's nowhere near as bad, but not something i'd settle for. The current isse now is that chrome sort of stutters-ish. I'll post some more experiments in a minute.
Kimpton said:
So I closed all the tabs on the phone, and also enabled 'eye comfort' mode (should have really done this one at a time) and it seems to have cleared up the issue in everywhere but chrome. It's nowhere near as bad, but not something i'd settle for. The current isse now is that chrome sort of stutters-ish. I'll post some more experiments in a minute.
Click to expand...
Click to collapse
Have you tried restarting the phone?
chris_fuller said:
Have you tried restarting the phone?
Click to expand...
Click to collapse
Yes many times - sadly didn't help much.
The issue came back, so I'm currently talking to three to send out a replacement
So my new handset arrives on Monday: so I got the weekend to experiment with this handset. Hopefully possibly help some people in the future. I'll post some specs and models later along with some other videos.
Has your new unit solved these issues as I have the same also where the screen locks up and shows the image or something like a hundred times. In addition to the grey screen
Wazzup.
Over at the Pixel 6 Pro fair, we have quite the number of people having problems with random reboots. We are trying to narrow it in - Android12? Pixel 6? Software? Hardware?
So - anyone here with the same set of problems? Or does the Pixel 6 not have that kind of issue?
For reference: https://forum.xda-developers.com/t/random-reboots.4353231/
I have gotten several random reboots as well. 256gb seafoam pixel 6. In particular, I was using "Frep" automation app (unrooted, used pc to start server) to do repetitive image searches in a game. Also the phone was sitting on a wireless charger while doing this. I noticed my phone felt pretty warm, wonder if it could be overheating?
Could be a naughty 3rd party app. Have you tried safe mode?
I posted this here:
P6 Bluetooth Problems
My p6 will see most some of my Bluetooth devices (laptop, tablet, TV, earbuds) . It pairs with the earbuds, but everything else it will try and pair, usually does not. If and when hen it does pair, that pairing is dropped dropped within 5 secs...
forum.xda-developers.com
My random reboots (or crashes that forced me to reboot) almost entirely stem from the wifi+bluetooth implementation. I found a sure-fire way to crash it during setup. Without word vomiting here, connecting the P6 with and to other devices has proved more difficult than any previous Pixel (for me).
mruno said:
Could be a naughty 3rd party app. Have you tried safe mode?
Click to expand...
Click to collapse
Not yet. It's also hard to "force" it (the reboots, I am not able to replicate it manually). Yesterday it just randomly happened whilst the phone laid idle next to me, thrice at the morning, about one time through late afternoon, then one time evening. I just notice the screen lighting up, then the Google logo comes, meaning the phone restarted.
I'm also pretty sure that Bluetooth/Wifi settings differed when the reboots happened, ergo at some times bluetooth was on, then when it rebooted, bluetooth was off. At no time when the reboots happened had I a bluetooth device connected. WiFi was online though, all the time.
What all the reboots have in commong though (at least the ones where I am concerned), is that the phone is just laying next to me, or somewhere, being in idle - doing as far as I know, nothing. It never happened when I used the phone or put it under load, so my P6 never "crapped" out under me. That's why I am not that concerned about this as of now, but it's certainly a nuisance to unlock the phone every time with my darn pin.
(Concerning 3rd party app) - I'd say that's unlikely. I copied my files over from my Pixel 4 XL and have not yet added one singular other app to my P6 Pro, so it should have gone naughty before my transfer over.
Hi! I experienced a big crash on the pixel 6. When I was configuring telegram, the app crashed and then the screen got black. After a minute it rebooted to the Google logo with a loading bar underneath. It was blocked in that state, but I could reboot it with volume up + power button.
I was pretty scared as the usual button down + power button didn't do anything lol
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
dirtyissa62 said:
12 (SD1A.210817.036) on my pixel 6, occurred randomly when opening camera app. Happend 7-10 times.
Click to expand...
Click to collapse
Odd. I never had a problem whilst using the phone, my phone only rebooted when laying idle (even though today I had no reboots at all, alas I didn't use the phone much, maybe 2h SoT without any heavy lifting).
Something in android 12 is bugging around, maybe we have to open support tickets.
dirtyissa62 said:
Something in android 12 is bugging around, maybe we have to open support tickets.
Click to expand...
Click to collapse
I just talked for a while with a Google rep and he said that they are not aware of any reboot problems, no people over at Google Forums have reported such a thing. "We do not monitor Reddit or XDA" - so he said he opened a support ticket to the responsible team and they would look into it, he also asked that I / we report/feedback this under -> Settings -> Tips & Support -> Feedback.
We also talked about a lens flare problem, that at least the Pixel 6 Pro has. If you shot some photos where the sun is directly shining into the camera, you might want to re-check them. Most of mine have either some sort of big circular green dot in them, or a big beam of light like in a phone with a very bad HDR processing. It seems to be some sort of software glitch, he also reported that.
So hopefully those things can get fixed.
This was the follow-up email:
Thank you for contacting Google support.
This email is regarding the chat conversation we had earlier today, I'm sorry we weren't able to complete it. Hence I wanted to follow up via email to ensure all your queries have been answered.
Please re-launch the camera app and check if the issue is fixed.
Please be assured our developer team is working on this to fix it as soon as possible. We would really appreciate your kind understanding as we work on this to fix it for you.
If there is anything apart from this that needs clarification, please feel free to reply back to this email. I'll be more than happy to assist you.
Thanks!
Nova
The Google Support Team
I'm having similar restarts while phone is sitting on a table doing nothing. Tried a factory reset and was fine until overnight on charge and it happened again.
Also have had a few times where wifi has stopped working for some reason. Not sure if related.
Not had any reboots but quiet a few app crashes in especially FB will be scrolling away and bang just closes also Amazon app ,
Well that was interesting.. When it rebooted that time, it gave me an error screen saying it could not load and may be corrupt. I had two options, try again and factory reset. Try again got me back running, but I'm wondering do I got as defective device now.. or if it's software related.
So after a lot of messing around, I think I have narrowed down what may be causing my reboots. It only seems to happen when I am using "Frep" to play macros on a game while charging my phone.. the phone gets pretty hot, and reboots when I tap the screen or try to swipe home or recent apps. Maybe its overheating, or maybe its "Frep" playing naughty.. but Frep did work perfectly fine on my old $200 used Nord N10 5g. Will update if it reboots while not doing this.
no reboots or crashes so far, not doing any gaming - but using phone for email, surfing, whatsapp etc and also a work profile for MS outlook and teams.
I have/had similar issues with my Pixel 6 (128GB - europe unlocked).
I was transferring old data via cable from my old (Xiaomi Mi A1) to the Pixel 6. This resulted in sluggish performance, crashes every 15 minutes. The crashes would randomly occur and behave mostly like this:
Try to unlock phone with fingerprint sensor
Fingerprint sensor lights up, nothing happens, no haptic response
Swiping up to the PIN entry. Enter PIN and hit enter. Nothing happens. Now freeze.
Screen turns black and it takes phone to reboot on average ~7minutes
Factory Reset; Installed apps manually (standard messaging apps, no games etc), better performance, problem persists
Factory reset; boot into safemode. It now took way longer to provoke the issue. But it still happened.
After this I contacted the customer service and they will provide me with a replacement. But now after a night of idle, the phone was working for 3-4 hours without any issue at all with most of my apps installed. It just now went into a random reboot (could only notice because it asked for PIN because of the reboot). But not the 8 minute blank black screen type of reboot.
I am really unsure what is the issue at hand here. But have to say that experience is less than ideal.
Mine just happened last night, not charging or running anything 3rd party apps (all from App Store). I tried to use the camera after eating dinner and noticed that double clicking power button doesn't open the camera anymore. After unlocking the phone it appears that the phone has restarted.
Is anyone running Private DNS on their system like Adguard DNS or NextDNS? I did some searching and people reported some private DNS were causing Android to crash. It was suppose to be fixed in previous Android versions but it could be back again.
I haven't noticed any random reboots (and the lock screen will require a pin to be entered after reboot and says this on the screen, so you should know the phone rebooted). I've had the P6 since the official release date. In fact, I haven't restarted the phone in days.
I run a wide variety of apps. Some from the Play store and some sideloaded. I think that any reboot issues are probably app related. Remember that A12 is very new and the are surely still some compatibility issues that app developers haven't found/fixed yet.