Hey all,
My Pixel 3 standard started freaking out today. I have initiated an exchange, yet thought perhaps someone may have had/fixed similar issues. I was in the middle of playing a game and my screen kept shutting off. I closed the application and found that SystemUI was crashing at random intervals, which is what was causing the screen to blank. The phone was also very slow at this time and wouldn't respond to several inputs. I also had a few instances where the phone opened random apps on its own. I tried going into safe mode and I don't seem to experience the issue. I am presently unrooted and on the latest November OTA. I've also tried removing any apps that updated today as that's when the issues started.
I've started the exchange process, yet it's five days out for a replacement and it's going to be painful to be without a fully functional phone for that amount of time.
Any ideas of what to try? I thought perhaps crash logs, yet I'm not sure which to parse...
Thanks!
I too started seeing System UI isn't responding message. Tapping to wake the phone or pressing hardware buttons had a delay in both normal mode and safe mode. I tried reapplying an OTA image from December and same result. So I tried Factory image vs OTA image, same result. Turned off always on display to see if that improved. Same result. Removed any case and screen protector to see if that was contributing, but same result.
I'm having a harder time getting google to initiate the exchange as I bought my device off swappa and can't access the original owner's email or order id. Never thought that was needed - until now. Buyer beware. I bought pixel 1 and 2 straight from google, but went secondhand with the pixel 3. My mistake.
blueline-pq1a.181205.006-factory-af1829a6.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you factory restored?
I have tried to factory reset my phone and I'm still having this problem.
It happens at random when getting an incoming call, I can't see the caller screen, the UI is frozen, can't silence it pressing the buttons, can't wake up the screen until the phone decides to let me use it.
It's so annoying.
I am stuck with this issue during this lockdown, can somebody help? Or tell me what worked for them?
Related
Hey Guys,
I have a peculiar problem with my girlfriend's phone. I've been stumped for almost a week now trying to unbrick her phone without making an attempt to root to try other things, but here's the scenario:
Phone is completely stock.
One day she came home and her phone was stuck at the Verizon screen.
I'm not sure what version was her Rom prior to the brick, but the phone recently told her there was an update about a month ago. She installed the other updates prior to this one.
I ultimately ended up performing a factory reset, and a cache wipe from the recovery, and it still wouldn't get past the Verizon Splash Screen.
I then used the Verizon Repair Assistant as suggested by many members on the forum, and it looked good for a second. It started updating all the apps, and survived past the splash screen, and into the welcome screen to get started. I started the activation process and boom, the phone reboots itself. I noticed something strange about the boot screen though. It started to look like it's glitching out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This one is like VZW's version of the Nyan Cat! Ha.
I then tried the Odin route, Installing VZW-I535VRUCNC1-20140430102617 onto the phone. Same result.
The last thing i tried while writing this thread was removing the AIM, and attempting the no activation WiFi, which it ultimately did take me back into the phone...
I moved fast enough where I was taken back into the UI, but I would see errors like
"Unfortunately Samsung Keyboard has Stopped"
I was able to swipe around on the screen for a bit before it froze, but the weird thing is when i press on the softkeys, I could still hear the water drop sounds. Then it would either go back through it's boot looping, or it would shut down. Pressing the power button won't work here, and only a battery pull would allow it to go through the boot cycle again.
I feel like a noob still, even after being able to successfully root 3 generations of the Samsung Galaxy Phones, (Epic, S3, and S5.) but I'm totally stumped on this one.
Seems like something is locking it up,
Any help would be appreciated, and if you are local (Silicon Valley, Bay Area), I'll buy you a coffee, or a beer. hah. :fingers-crossed:
Thanks in advance!
Anyone?
Received the phone yesterday afternoon and everything was great for the first three hours. After updating to the latest version and reinstalling apps from Play, the screen flickered and started ghosting a line of pixels stretched vertically over the bottom third of the screen (images and video below). It doesn't appears to be a hardware issue as the ghosting moves with animations, but it does appear during boot as well. I've factory reset without any difference, and have flashed the current firmware images (cm-11.0-XNPH33R-bacon-signed-fastboot) without any luck.
Booting
Notification drawer
App drawer
Video
Any ideas?
EDIT: I didn't have my brightness all the way up; the issue persists during transistions.
Sorry about that, you can try RMA. If it's also in Fastboot mode, you have two options: a) Write OnePlusOne and ask for repair(tooks long!!) b) Buy another phone.
You should try a custom kernel. As the stock kernel for 33r doesn't have the display commits that custom kernels have. I recommend Franco kernel. If the problem persists, then I'm afraid you'll have to RMA.
It is surely hardware.
Sent from my Oneplus One
mine too.....
Got mine 5 days ago and was in the middle of a game last night and the exact same thing is happening..... I put in a request for an RMA already but the whole process takes about a month from what i have read.... Didn't see a similar issue in a search of their forums but it is interesting that our phones came from the same batch likely and have the same issue....grrr
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, same thing exactly. Rolling the dice on RMA. :/
any progress?
peterochford said:
Yep, same thing exactly. Rolling the dice on RMA. :/
Click to expand...
Click to collapse
So I am debating filing a paypal claim. Reading the reports of the RMA process on their forum I am wondering if I will get a functioning device within the paypal buyer's protection timeframe. After several emails and pointless software fix attempts back and forth I finally got their support person to say they would forward me to an RMA specialist... but who knows how long that will take and given time frames I think it is very likely the 45 days will run out on 10/5/14 before I receive a replacement device. Any luck on your end?
At first I thought glitches I saw caused by the app (inbox) itself. Then I keep seeing it happens on other apps as well.
It is like some elements (ie, action bar) of apps flashing or the whole screen flickers. It usually happens only a second or two at most; too quick to make a screenshot of it.
Though, this problem is not happen regularly, it is frequent enough to get noticed.
Here are some apps that I remembered glitches happened, it happens in other apps too but usually very quick and random.
In FX File Explorer, sometimes glitches occur during transition animation between folders.
When adding a new Google account in Settings, the big top blue part of the screen flickers.
In Inbox app, sometimes tips bar just keep flashing for almost 2 seconds when I closed it.
And, in A Better Camera app, this can happen sometime:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm considering reverting back to 23.4.A.0.546.
Even though the old firmware has stagefright bugs, it's very unlikely that someone would use it on me, and I don't use MMS anyway.
for me both cameras are better in .232
and yeah I have these screen problem
and did you notice that the speakers are noticeably lower in music ?? now they are like Z3+ !!!!
I had some screen tearing when I first installed .232, but none since then.
Speakers seem just as loud as before.
I do have the same problem.
Made myself a prerooted fw using PRF, downgraded, rooted and upgraded using the prerooted firmware i made.
Also made a factory reset. Now i'm getting screen tearing while scrolling, video glitches and stutterings.
I saw that at first but not anymore (maybe I haven't noticed them).
Strange thing is that 232 version should be Stagefright free, however, I've runned a test and I'm still vulnerable to one of the flaws.
My two month old POCO X3 NFC 128GB appears to be randomly exhibiting a graphics fault. Occasionally upon screen wake up, this sort of graphics corruption occurs (see first image below)
The first two times this happened, the corruption was blue, the one in the image is red, it looks like a low resolution, low colour mode, and the only way to get the screen to go back to normal is to reboot. I have not managed to intentionally cause the error to appear.
Screenshotting while the error is occurring shows a normal screen without the issue.
Has anyone seen anything like this or have any idea what is causing it? This is my first Xiaomi phone after reluctantly switching to them from three previous Huawei mobiles. Very disappointing and annoying to have an intermittent error two months into owning this phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have indian variant, have exactly this issue.
After updating to 12.0.9 once a while display acts like this.
You don't need to reboot simply go in settings/ display/colorscheme and click standard Display will be back to normal, it's a software glitch which came with new update
darshan9222 said:
I have indian variant, have exactly this issue.
After updating to 12.0.9 once a while display acts like this.
You don't need to reboot simply go in settings/ display/colorscheme and click standard Display will be back to normal, it's a software glitch which came with new update
Click to expand...
Click to collapse
Thank you for your message, this very interesting to hear as I have not seen anyone else talking about this and I was beginning to wonder if it was a hardware issue as the fault looks very much like graphics chip corruption. The next time this happens I will try your fix without rebooting to see if it helps, thanks again.
Hello everyone. It's been a minute since I've posted anything on this site. In January this year I decided to upgrade from my aging Blackberry Priv to one of these phones. I've been using it without any issues until early this morning when I tried to look at my notifications and the screen wouldn't light up. It was working fine all throughout the day, and I don't recall the battery being below 50%. It is unresponsive when I plug it into the wall adapter or my PC, however the PC seems to pick it up as a device called "QUSB__BULK."
The phone is running stock Android, and I only charge it with the wall adapter it came with and occasionally my PC. I only have a few social media and email apps on it. I had the Open Camera app on it, and I'm a little sus of it since there have been times where I would wake the phone up and the camera would just randomly open. It seems like it would bog the phone down a bit when this would happen. I installed the app because I didn't like the way the stock app processed audio while recording videos. The app gave me the ability to record raw audio which worked fine aside from slightly lower volume.
Does anyone have any ideas on what could have caused this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figured I'd bump this for an update. I contacted the company shortly after I made this post about the phone. The phone was covered under warranty, and they told me to ship it to them for repairs. I shipped it in June and have contacted them a few times since. I'm suspecting that there was some kind of defect in the motherboard since I'm apparently not the only one who has had this issue. I found a post on another forum dating back to last year from someone with the same experience as me where their phone just randomly said "ight, Imma head out." It's been quite a while since I sent it off, which adds to my suspicion that it was a board issue given the whole chip shortage we're going through. I'll update this post if anything comes up in the future. I miss that phone. Been using an iPhone since I sent it off. It's okay I guess, but man do I miss that keyboard.
Update on the phone - I was contacted by F(X) Tec about four days ago. My phone has been repaired and shipped to the US. I should be getting it back by Wednesday. They did not specify what actually caused the issue with it. Hopefully, once I get it back it won't have any further issues.