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.
Related
{
"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"
}
That happens to me from time to time. Sometimes I'm doing something and it suddenly happens, sometimes it's happened while the screen's been turned off and no programs have been running in background.
So is this a normal TF3D feature, or should I contact warranty services?
The graphics everywhere else are normal, it just seems to affect the TF3D.
Have you tried a hard reset? No that is definitely not normal... try a hard reset. If that doesnt solve it you should probably contact warrenty services.
Mine does it too. It also produces an effect that looks a bit like a 'broken screen', AND sometimes, just for fun, it pretends it's an old analogue TV that someone unplugged the aerial from (ie snow). All have been covered elsewhere on XDA. Mine has been doing it since day one (along with GPS lag about as long as a Nimitz class carrier) and three months later it still keeps on plodding along, annoying the hell out of me, making me wish I haden't wasted £479.99 on it....
On a more practical note, it looks like you have altered your Touch Flo a bit, mine has problems with the bog standard ROM and with customisations to the Manila.
*EDIT* Actually, it looks like your Touch Flo is bog standard so i'll shut up. Ahem.
Hehe yeh, it's the standard TF3D, and yes I've tried hard reset, no help. Sent the phone to the shop I bought it from, let's see if they can do anything about it.
Unfortunately the place I bought mine from doesn't take returns after 28 days. I have funally badgered HTC support into offering a repair, but I have a bad feeling that the will simply send it back and say it's okay (then give me a bill, LOL ; )
I'm actively considering flashing another ROM but can't make up my mind.... Hope the shop you bought it from replaces it : )
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?
As title says, the backlight started shining through on my U11+.
{
"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"
}
It happend today, i was on my phone. i put i down to go get something to eat and when i came back the bleed came. it's around the entire screen.
i haven't contacted HTC yet because i wanted to ask you guys and get your opinions first.
i haven't dropped it, i haven't thrown it after somebody. i've been looking after it.
Sorry for the unacceptable quality on the picture, it's taken with my work phone.
That's not good. RMA it if you can.
Did you get yours repaired? My u11 plus just did the same thing today. I am wondering if too much squeezing the edge sense warpped the screen.
jaylo2003 said:
Did you get yours repaired? My u11 plus just did the same thing today. I am wondering if too much squeezing the edge sense warpped the screen.
Click to expand...
Click to collapse
No i Didn't. It "fixed" it self. it's actualy done it a couple of times now and i have never used the squeez fuction.
HrBorggreen said:
No i Didn't. It "fixed" it self. it's actualy done it a couple of times now and i have never used the squeez fuction.
Click to expand...
Click to collapse
It happened to me too: I was watching a film, checked phone and it presented the same symptom, but in always on display. Rebooted and same problem. After a little time (just 10 minutes or down there).
I am using edge function and it is no longer happened .
DHD22800 said:
It happened to me too: I was watching a film, checked phone and it presented the same symptom, but in always on display. Rebooted and same problem. After a little time (just 10 minutes or down there).
I am using edge function and it is no longer happened .
Click to expand...
Click to collapse
I think the last time it happened to me was in January.
It's a bit bizzar that it comes and goes like that, I still haven't figured it out what's causing it.
But it doesn't seem to be a problem any more so I'm not worried.
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?
Hey guys,
Reporting a shocking incident and service feedback from Google support outsourced to B2X in India.
A week back I encountered a display flickering issue all of sudden while I was trying to click few photos on my Pixel 3 XL. I assumed it was a glitch and I reset my phone, but the issue remained same and I immediately called Google support for further help, they assigned a field engineer for further checks (Ticket - GL0068474)
{
"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"
}
The field engineer arrived next day and he examined phone and informed that this is a display issue and the same will be replaced since there is no physical damage and Phone is in good condition (he mentioned the same in the Job sheet & a copy was also given to me)
After 4-5 days I receive a shocking mail from B2X team telling I need to pay Rs. 19637/- (approx 285$) as repair charges since my phone has severe damage. (which is nothing but a lie as my phone never had any physical damage which also confirmed by the B2X engineer, I even have video proofs that my phone never had any damages).
I was completely shocked to receive such response from Google/B2X and I immediately reached out toe Google support team to get this escalated, they accepted the escalation and it has been 2 days now and I have not received any further updates from either Google or B2X
I am now worried that Google will ignore this and send the phone back to me unpaired
How do I take this forward
Mark this details to Google Twitter and Google support email with all proofs including the video
Sent from my Pixel 3 using Tapatalk
have done all that, patiently awaiting their positive response now but I am not hopeful
never ever thought a Company like Google would provide after sales service in this manner, this is where Apple wins hands down.
In all fairness, most companies would just give a new phone and deny the problem.
If there's anything I've learned from my time in the military... Be annoying about it until the issue gets resolved, be extremely persistent.
is there anyway that I can get mail IDs of Google heads in India or even mr Pichai ?