Related
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Apologies in advance if I'm missing any important information (I'm trying to sift through and try pick what I think are the relevant points).
Issue:
I felt my phone vibrate twice and took it out of my pocket (expecting a text). Instead I found the "Desk Clock" part of the stock "Clock" app flashing on and off the screen. When I tried to close it I came to the lock screen, unlocked it and then the desk clock opened again. It reloaded every time I attempted to close it. I tried to end it using the task manager but it didn't show up on the active applications list. I restarted the phone.
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
This solved the arrangement issue but didn't stop the desk clock popping up. I also became aware of another problem. The battery was showing 12% (down from ~35% it was showing before - when checking battery usage). I plugged it into my laptop via the USB lead I have (which I had used earlier in the day to charge it). It didn't recognise immediately that it was charging. I swapped to AC, it started charging.
It then started showing "driving mode activated" and asked me whether I wanted to complete the task with UlysseSpeedometer or Voice Talk. I didn't press anything. When I pressed back it then asked me again a few seconds later. I restarted the phone again.
This time it showed 37% battery! I switched to the USB charger to try to back the phone up. It had trouble connecting but did eventually. I left it perfectly still as it tried to back up but failed twice partway through doing so.
Recent changes:
Only real changes are installing Super Compass today, which when (re)reading reviews didn't seem suspicious. I have uninstalled just in case.
Additional information:
I updated to 2.3.5 through Kies about a month ago (the first time it was available for me after checking for updates every few weeks - I have friends with the same phone on 2.3.4 and 2.3.3). Since then the countdown timer on the clock app sometimes shows the preprogrammed 1 minute countdown even when I have a timer running. The timer alarm still goes off at about the right time (haven't tested it properly) though.
In addition to this I have customised the apps that stay at the bottom (can't think of the terminology at this time of night) by swapping the Phone for GMail. Every time I restart the phone the GMail app is removed but the Phone app doesn't replace it. On a similar note I keep getting asked to choose my default PDF reader after ticking the box to select it multiple times.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Question:
I was wondering whether anyone has any insight, has experienced similar problems, or has any other advice regarding this?
Thanks in advance for any help you can offer
Regards
T
It sounds like it might actually be a hardware fault - basically what's happening is that something on the phone (whether hardware or software related) is triggering it to think it's being connected to a dock. The desk clock is what pops up as soon as you put the phone in a Samsung desktop dock and car mode similarly pops up when you use the vehicle dock, so there may be something funny going on with your phone's connecter that leads it to think these events are happening. (The weirdly arranged home screens tie in to this, as they can be a slightly buggy result of unplugging the phone from the one of the docks while in landscape mode - the launcher tries to load the home screens in landscape and just makes a mess.)
As a bit of a bodge-job fix you can install an app from the market called 'NoDock' if you're rooted, as this stops the phone ever being triggered in to dock mode, but to be honest id say your best bet is to speak to O2 or a Samsung service centre about getting it fixed or replaced!
Anyway, I hope this helps and you manage to get it sorted - I don't know what I'd do without my Galaxy S2!
Sent from my GT-I9100 using xda premium
Hello, quite a late night here as well but I'll try to give you my insight (and then slam myself to the bed )
It seems that the widget in your device went corrupt and perhaps then some more... I recommend backing up your data and then doing a factory reset and eventually re-flashing thru kies (come to think of it, i don't really know if KIES supports full-wipe reflash ). Also, for customizing the quicklaunch bar, use GO Launcher EX (free from the market) - its customizability far surpasses that one of the TouchWiz
If a factory reset doesn't help, you can help yourself by reflashing the original firmware by yourself via ODIN (but be sure to read tutorials and know your firmware first!), you'll find all the needed information here
Hope you get your problem resolved
TUnit said:
Hey guys,
I've been reading the forums for the past few weeks and have been enjoying the discussions here, yet not having too much to add (constructively). Apologies if there is a thread on this already. I have done a couple of quick searches but nothing came up that seemed to fit the bill.
ITS a question = Q&A so well done that man for posting in the right section .
I got in this evening and took my S2 out of my pocket to find something wrong with it. I'll explain below. First of all software details:
Baseband Version:
I9100XXKI4 (up to date as far as Kies is concerned - stock ROM)
Thats the modem not the firmware .
Issue:
When I restarted it didn't seem to load properly with app icons all over the screen and the home screen numbers in the middle of the screen. I have a screenshot which I'll try to upload later. I restarted again.
My thoughts:
It appears to be a software issue to me. It's late now but tomorrow I plan to attempt to back up again (perhaps just by copying all the files on the phone using Windows Explorer if need be) and attempting to reinstall the firmware through Kies. If that doesn't work I'll do a factory reboot. After that I'll contact my carrier (O2 UK) to get some support.
Rule one is backup data and factory reset the phone then test .
Follow that with a Kies upgrade if available .
jje
Click to expand...
Click to collapse
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Hello everybody! I'm a newbie when it comes to these things, so please bear with me
I recently bought a Galaxy Grand, however, it seems to have a problem - it hangs up once every day on an average which requires a boot by holding down the power button for 5 seconds or more (sometimes even requiring a battery removal).
It seems to happen at random times, sometimes when the phone is being used, sometimes when it is just lying idle. The main problem is that when it is actually hung up, people trying to call me will hear the normal ringing tone (with which they assume my phone is ringing), but my phone neither rings, nor stores the call log on reboot!
So in effect I would not get to know if someone called me or not, which is not a good situation to be in!
I am trying to get to the bottom of this, so what I did was install CatLog to monitor the activities of the phone. As I have been made aware, Jellybean does not support logging programs fully unless rooted (and my phone is not), so it shows only basic logs. However my phone shows crazy usage (almost 70 entries per second – mainly something like this over and over (full log file attached - till a hang).
02-14 12:23:37.544 I/brcm-gr ( 6506): [gralloc_lock]: new usage 0x933
I tried the same test with an S3 (jellybean), and that showed around 1 entry in approx 10 seconds (which I assume is normal).
Can you please help me figure out what the problem is? Do you think this is a hardware or a software issue? I have attached a log file with this message, that goes all the way upto once instance where the phone had hung up.
Some other points to note:
It seems the phone hangs up more frequenty when the GPS is on
The phone does not hang up in the 1st 3-4 hours after rebooting
The phone has not yet hung up at night (coincidence, perhaps?)
Thanks a ton
DM
Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.
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