Related
I can't remember if this happened with the build I was using before (month 2) -- I think perhaps one or two times, but I'm not 100% sure. However, more recently it has been happening quite a lot. Sometimes the phone will just simply not turn the screen on. There's not even any backlighting (or in this case in other words the black level is below the minimum that it seems to be when the screen is on since it's LED.) Most of the time I don't think it's responding at all, but this latest time I did get haptic feedback from what should be the lock screen, so I'm not entirely sure if I was maybe just missing the lock before. I think the issue has been happening more frequently now than before though (well, it has only been since the 14th or so I guess, but I'm pretty sure the issue wasn't happening much at first) I'm wondering if it's more likely something I've changed. Also, this last time I did notice later that day that the battery was shockingly low for such a short trip out. I think it was in the 70-80 range -- normally it's around 92+ after that length of time.
To be honest, I do keep a lot of things from running in the background and freeze a lot of apps. I try not to get anything essential, but sometimes it's hard to tell what truly is. I've mostly frozen obviously useless things like the live wallpaper stuff though. The only thing even remotely related that I could think of is the face unlock which I froze since it was running even though I don't use it (I have the plain slide to unlock set and do not want face unlock.) I can't think of anything else I might have messed with that even remotely could have to do with this though... My Nexus 7 also running CM 10 stable doesn't seem to have this issue.
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version
Well this really sucks. I've been telling people for a long time that my G5 has been the best phone I've ever had...a true powerhouse. Then came the Nougat update. Since then it's been nothing but problems. I called Verizon, LG (useless), and Google. All said 'try a factory data reset, that should fix everything'. Yeah, right. So after the Ohhhhhhh-so-painful FDR, I still have all the same problems. When plugging in the oem or third party fast chargers (I have two of each), the notifications will simultaneously say "slow charging" and either "charging" or "fast charging" at the same time. Unplugging and reconnecting will fix it every time. Also, I'm getting ghost images when changing screens...I can still see a shadow of the previous screen which eventually fades away. These are both just minor annoyances, but still weren't there before. But also, my NAV appears to have a hard time keeping track of where I am. More annoying. But the biggie is that I can no longer use any of my many Bluetooth headsets for phone calls. You just can't have a Bluetooth conversation anymore. Streaming audio is fine. But calls aren't doable. That's a problem. Since I already tried an FDR to no avail, Verizon is going to send me a new phone. All I can say is if it comes with Marshmallow, I'm leaving it that way. Any benefits that Nougat brought are far outweighed by the problems. I'll wait until they fix it, maybe then. Anybody else been so plagued by this update?
D Dave
I have the same problem.. I have to charge and re-start the phone to make the phone "charging" otherwise it is intermittently connected and disconnected.. I've done factory reset and didn't work out also.. I guess getting a new replacement from T-mobile is the option here.
I got the new phone that Verizon overnighted to me and got it all set up. It thankfully came loaded with marshmallow and is working fine, but keeps prompting me to install Nougat. I'm going to keep postponing the update for now to give them a chance to work the bugs out. Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
I have the charging issue as well and it started with 7.0.
You should report it. They won't fix something if only a couple people report the problem. They sent me a new phone and I've managed to defer the 7.0 update for over a week now. It prompts me everyday, but I just say later! I'll wait awhile to see if they fix it. The unbearable Bluetooth call quality was just totally unacceptable.
Nougat?
My G5 is still on Marshmallow, and does not see that there is any update to Nougat available. So what are you all talking about?
What carrier are you with? I'm on Verizon, so maybe not all carriers have it yet. Or maybe you're one of the lucky ones who wasn't randomly chosen to be a guinea pig and find all the bugs and glitches. ☺
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Dangerous Dave said:
Is there anybody out there who has installed the update on their Verizon G5 without any problems after?
Click to expand...
Click to collapse
Me, totally problem free. No problems of any kind but it did fix one bug, I had an app that wouldn't run in Marshmallow and it's back working normally again with Nougat, who knows why?
jpradley said:
I'm on Verizon.
This is a Verizon LG G5 forum. Are those posting here WRT Nougat posting in the wrong place?
Click to expand...
Click to collapse
Try to keep up.
I have the G5 on Verizon and am fully updated. The only problem I've had is with storage space. 85% full and I'm lagging frequently. I've deleted as much as I can, to no avail. I can't seem to get anything successfully moved to the SD card, so I'm not sure of its purpose.
I´ve got exactly the same problems and more.... What did you do to fix them in the meantime?
To add another problem, my fingerscanner isn't working 9 out of 10 times.
It became an annoying piece of ****! Please help to get my awesome phone back.
Greetz from the Netherlands
I've had other bluetooth issues... I have to restart bluetooth nearly every day to get it to connect to my devices, it's as if the bluetooth apk is hanging up in the background.
That said... My phone updated to 27A this morning, so I guess I'll find out in the next few days if I have the same problem, lol
Well the 27A update must literally be ONLY the security patch. It didn't fix the bluetooth issues...
Seriously this update has been the worst. I too am experiencing the power cable issue. I'd say 7 out of 10 times it tells me it's slow charging. Simply reseating the cable fixes it every time. The most frustrating part for me is Facebook and Twitter. With the first Nougat update the Facebook app began to bug out. At least once a day it randomly crashes, even when i'm not actively on it, and begins a crash loop that won't stop until I restart the phone. that usually fixes it. I'd say every other week I've had to straight up re-install the FB app to fix the crash loop. and now after the recent update that was pushed the twitter app keeps failing to load some images. Most tweeted images show up fine but profile/banner images will not. Again fixed with a restart. This is really quite frustrating. I don't understand what they did to break Nougat so badly. My friends Pixel hasn't had any of these issues. I'm getting so fed up with my G5. I love it but it just so damn locked down and now this. It really makes me wary of getting another LG phone
Well, it's been over three months since I started this thread. The problems after the Nougat update were just unacceptable, so Verizon sent me a new phone loaded with Marshmallow. I've been deferring the update every day for three months. Last night I accidentally tapped the wrong spot on my screen and it installed the damn Nougat update. I've had the update less than 24 hours now, so haven't tried everything. But I can tell you they haven't fixed the problem with the slow charge/fast charge, as it came back IMMEDIATELY after the update. I called Verizon today to ask why the hell LG couldn't fix that issue in three months time! Verizon called LG for me and inquired if there was a fix. LG said if I send the phone back to them, they'll fix the corrupted files and send it back to me. Really?!? Both my G5s experienced the same problem immediately after the update and they couldn't fix the issue in the download in three months time? Douchebags. Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Dangerous Dave said:
Now I have to decide which is a bigger pain in the a$$, having to unplug and replug my phone every time I want to charge it...you know...until I get a new phone, or format it, send it back to them for however many weeks it takes them to (theoretically) fix it, and rebuild it when I get it back. Why, oh why, wouldn't they implement the fix they already have, instead of pushing out flawed software, then making me send my phone in to them to fix. Grrrrrrrr!
Click to expand...
Click to collapse
Unfortunately don't have anything helpful for you, other than to say, you're not alone, and I similarly got sufficiently pissed with this bug today to see if there was a solution yet.
Pretty sure you answered your own question though: they don't actually have a fix because LG has likely stopped developing new releases for the G5 in anticipation of the G6 release. They want you to send it back to them for the "fix" because it's a pain in the ass and transfers the opportunity cost onto you, which hopefully (in their eyes) means they can do absolutely nothing.
I'm just.... beyond frustrated with this ****ing phone. I really wish that I would have limped by on my old HTC M8 until the V20 came out, even with its barely-chargeable battery. At this rate, I would have been better off with a pixel or internal-battery phone for that matter. There is just seemingly no end of software and hardware issues with this phone, and LG's piss-poor customer service gives you almost no recourse for any of them
Hi. G5 VS987 Owner here with a build date of 10/2016 so I've managed to survive the bootloop issues that plagued a great number of us thus far.
My theory is: LG has no clue on how to push an OTA update.
My question(s) are: How many of you updated with the OTA?
And how many updated via LG Bridge or some other flashable method?
I'm wondering what if any difference knowing this makes because while this phone has honestly been the best/fastest/bug free phone I've ever used...the update nagscreen has me wanting to choke the [email protected]!%# out of it. It just won't go away.
I really wanted the Note 7 before they blew up...What to do guys?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Another thing...is there a way to flash back to MM if this update really goes south?
I updated to Nougat OTA with no problems except the power cord which I fixed.
Here's how I did it:
DISCLAIMER! I KNOW this has nothing to do with the problem and cannot possibly fix it but... it did fix it for me so give it a try, OK?
1. When you get the slow charging message look at the power cord, turn it around and plug it in the other way, see if that helps. Once you've determined that plugging the power cord in one way reduces the frequency of the error just keep on doing it that way and in a couple of days the problem will be gone!
I know, I know, but try it, what can it hurt?
Well, interesting update here. Verizon said I could send it back to LG to have corrupt files replaced. I decided that neither option, living with the problem or shipping the phone back to LG, was acceptable. I called Verizon back and told them so, asking for a replacement and hoping it would come with MM. They just sent me a replacement, and it came with Nougat already on board. But would you believe this phone works perfectly! I mean, it rocks! I have NONE Of the problems I had with the last two phones after the OTA update. So maybe the OTA really is a piece of crap. But I gotta say, it's nice to love my phone again.
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes not. If you restart the phone, it temporary fix the problem and after few minutes/hours my mic doesn't respond again. I tried to flash different official rom released from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works. I'm now looking to root my phone and flash a custom rom, maybe they fixed the issue in their end.
I installed Sound Meter and Mic Tester to check once in while (you should too) if my mic is working. When I found that the mic don't respond the way it should, that's the time I restart my phone.
* Flashed different versions of: Nougat, Oreo, P (preview) ... but the issue is still there.
Can we list the Custom ROMs that fixes this annoying problem (is there any)?
Sound Meter(if mic is working)
https://photos.app.goo.gl/kcU0APX2pNPYjoG12
Sound Meter(No Response)
https://photos.app.goo.gl/a1lqNeyogTtuHRkE3
Mic Tester (if mic is working)
https://photos.app.goo.gl/K7oZYvSQDS2ndJHc2
Mic Tester (Flat)
https://photos.app.goo.gl/6BPoSryI3ECNJxwu1
chrizcrozz said:
As we all know Pixels have this dreaded microphone issue. Sometimes it works, sometimes are not. I tried to flash different official release from https://developers.google.com/android/images but the issue is still there. I believe it's software issue because the hardware works.
Can we list the Custom ROMs that fixes this annoying problem?
Click to expand...
Click to collapse
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
chrizcrozz said:
Did you try to install Sound Meter and Mic Tester? If yes, is it stable (referring to mic Issue)?
Click to expand...
Click to collapse
No, I would just lose microphone functionality for a minute at a time, sometimes longer. It happened in phone calls a lot. I just thought my mic was going out but I'm glad I tried a few other roms before buying a new phone. I feel like my issue was far different from your current problems
If this was a software issue, everyone running android 8.1 would have this issue. This sounds like the audio codec manufacturing defect. Unless you have an app that is interfering with something, probably not software
That's weird,. I haven't encountered that issue not on stock but I never stayed on stock for long though as I flashed custom rom a couple of days after receiving my phone. Bought it new in March. I'm running Dirty Unicorns rom though, can be found from the link to Discord on my signature.
I'm definitely interested if you find anything. Installed the April update over the weekend and bam, no mic and random reboots. Factory reset didn't help. I would think it's firmware related since it happened immediately after the update, but idk. Both Sound Meter and Mic Tester show no response.
UPDATE:
I tried to load a custom ROM - Resurrection Remix 6
So far so good. I haven't experience the problem this day.
Usually, I restart my phone 6-8(or more) times a day just to temporary fix the microphone issue.
I will observe in a few days and update this asap.
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
I installed Resurrection Remix 6 and I still have the same microphone issue. Can someone please confirm if by downgrading the problem will be fixed? Thank you.
chrizcrozz said:
UPDATE
Resurrection Remix 6.0 works great! I didn't have any problems! It seems fixes that microphone bug.
I have uptime of 36 hours and counting with out restarting my phone. I had few voice calls and few net calls (FB and Skype).
Super big thanks to all who's involved in making that project.
https://photos.app.goo.gl/60ABq4dUFnKNKAcE2
Click to expand...
Click to collapse
Do I need to downgrade before flashing Resurrection Remix 6.0?
I'm on 8.1.
jacobas92 said:
I had the problem in all oreo roms, but not in nougat or P. Been running the P preview since it was available and haven't had the issue once
Click to expand...
Click to collapse
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
zeth717 said:
Man, you can comfirm that you got no audio and microphone problems on android P?
If so, I will cry. :,)
Click to expand...
Click to collapse
problem persisting in Android P too..... i upgraded last night and works well for few hours, then today, starts again........
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon ?
Does anyone else have any more tips for dealing with this?
mattyyey said:
Thanks for the tip. Ever since I got the June 18 update (D1 android 8.1) I've had random reboots, mic and the odd speaker issue.
I rooted stock with twrp n magick no difference. Even b4 restoring apps. So this week have installed pixel dust. Such a great time BUT mic n speaker problems persist, and the random reboots have become complete crashes. Where I think my phone is bricked, but if you hold power long enough it reboots. That's where I'm at now. Barely got any apps installed, dealing with it. I think I'll give ressurection ROM a ago tomorrow. Thanks for the tip. I know easily when it's happening, because I use ok Google and voice typing ALOT.
I can't believe that only last month I was totally ignorant to this issue and loved my pixel a bit too much. Now it's like dancing with a dragon
Does anyone else have any more tips for dealing with this?
Click to expand...
Click to collapse
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
If you’ll recall, Google’s 2016 Pixel devices, the Pixel and Pixel XL, faced microphones issues not too long after launch. As Google explained in early 2017, this issue was attributed to “a hairline crack in the solder connection on the audio codec,” with a warranty replacement being the only reliable fix. Later on in the manufacturing process, Google refined this part of the device to reduce the chances of this problem occurring.
Obviously, that was a frustrating issue for Pixel users, as it essentially disabled all three microphones on the device. What made the problem worse, though, was that holding the device in a different way or even a change in temperature could make the problem come back after it had seemingly gone away.
Click to expand...
Click to collapse
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Google is providing free motherboard replacements, but only to those encountering bootloops due to microphone-related issues (lawsuit affect?). Some one who claims to be working for uBreakiFix have recently confirmed this on a Reddit thread discussing the matter.
Click to expand...
Click to collapse
abemore said:
I was also pleasantly oblivious a week ago. And I've been running on the March 2018 security patch since...well...March. So I can confirm this issue isn't caused by the June (or April, as another hypothesized) security patch. I haven't updated because I've been using Magisk for root since day 1 (opted not to install twrp), and the one time I system-updated to March, it don't go smoothly with magisk.
My repeating symptoms:
Mic failure some number of hours after boot.
And yesterday (not sure if it's repeating):
Could not receive income phone calls
so I received a Hangouts call instead, and phone did not stop vibrating until the Hangouts call was finished.
Around the time these symptoms started I had:
1 never-before-seen phone brick while I wasn't looking at it. Picked up phone, black screen, no response. Held power button for ~10 seconds to reboot.
1 never-before-seen instance of super laggy scrolling. Freezing for a second before it would scroll. Rebooted to fix.
Claimed fixes:
some say uninstalling apps solved it
some say upgrading to P
some say replacing the motherboard
The frustrating part is not having any way to know what the problem is or what the solution is. And people are experiencing different symptoms, so we can't even be sure we are having the same problem.
This article https://9to5google.com/2018/02/08/google-lawsuit-pixel-defective-microphone/ explains the cause:
Free Motherboard replacements are being offered http://piunikaweb.com/2018/05/03/untangling-google-og-pixel-motherboard-replacement-mess/ by UBreakIFix:
Click to expand...
Click to collapse
I never had bootloops but the mic and audio issue, with stockROM, pixel dust and CrDroid. Then I heard about the ubreakifix possibility and when to the next store and they changed the MB without hesitation. Since then it works like a charm. Just go there, they are very helpful. That's a hardware issue not a software one.
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
mattyyey said:
Long story short - the update triggers the behavior(s), but its actually a manufacturing fault. You can replace part or your full motherboard to fix it. I personally just flashed stock and took it back to EE and they replaced it no cost. I remembering reading its a common problem with a certain early batch of Pixels. I've lost the link but you can use your serial number to check if its an early version thats effected. Apparently its only effects less than 3% of phones but the problem looks bigger when i was searching lmfao.
Anyway software fixes might help, but ultimately its a hardware issue. Get it replaced. Yeah they sent me a new one with a locked bootloader so i have to start from scratch but thats better than living with the error.
Click to expand...
Click to collapse
You're right. I ended up getting a free repair from uBreakifix. The guy said he wasn't allowed to tell me what he did to fix it. I noticed he had downgraded me from Android 9 to 7.1.2. I hoped that wasn't the secret fix. On closer examination, I noticed the serial number had changed, which means they replaced my motherboard...for free...on an out of warranty Pixel that I bought second hand. :good:
Since Android 10 dropped, if anyone notices any bugs or issues I figured it would be good to make a thread about them. Been using Android 10 since it dropped, and one issue that I have noticed is my signal is more sloppy and inconsistent which may be a radio issue. I am using Sprint, but the signal has been more spotty and the reception overall has declined.
Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.
omky_b4u said:
Biggest issue, battery drained so fast after update. Standby mode eat up more juice compare to Android 9. 9 was giving me 6-7 hrs SOT now it's just about 3-4 hrs SOT. Few apps which were using battery percentage half of it's usage time now using double battery.look like apps are not yet optimized for Android 10.
Click to expand...
Click to collapse
I've had that too, but it's not too significant, and i wouldn't worry about it for the first few days while things optimize but i also noticed slight battery drain.
Been trying to update the signals. The radio is definitely having issues for my carrier.
Pixel 3 in the Call Application, my screen goes black after call in connected and I can't seem to get the screen to become active again until call is over and I hit the power button twice. This just started after an OTA update to 10...
I updated to 10 OTA and since updating my wifi calling isn't working. Whenever I try to toggle it, it just says that it's unavailable and to try again later. I haven't performed a factory reset because it's always such a pain to do that (especially with all the accounts I have using 2FA w/ Google Authenticator).
My cell/data reception has also been significantly decreased, according to my little indicator in the notifications.
Anybody else having these issues?
My reception has always been poor with this phone so I cannot confirm our deny that it's worse on Android 10 stable.
However I ota updated from final beta to stable 10 and my phone randomly goes home while I'm using it. Really annoying when having an app open to have the home screen constantly appear.
Personally I'm having between 2 and 3 hours of SOT, and always had those stats on Android 9 too, for very basic using (no calls, no gaming, no videos, slight browsing, few SMS, etc). Hope battery will be much better for the Pixel 4...
I forgot about this. My phone initially also got stuck on the boot screen. I was like oh great here we go. Apparently it's an issue. Android 10 appears to still be in beta mode despite being released as stable.
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/amp/
Unbeliavable, how google tries to force you towards its search engine!! I could probably get used to thr new gestures, but not to that notorious search bar!! There is no reason to block all Launchers from working with gestures. I hope somebody will soon hack that!
you are furthering probably biggest bug of Q (not affecting everyone though, but many people)
https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
As I said in another thread, I have not been able to flash the factory image of either the .019 or .020 firmware. I've been doing the method of running the flash.bat file minus "-w" to prevent it from wiping my phone, using the latest SDK Platform Tools and after trying both they both cause a bootloop. My phone will attempt to boot up 2 different times and fail (assuming once for each partition, A & B?) then go back to fastboot mode.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.
Toronadian said:
.
Considering this other major bug with the sensors now not working, I guess holding off may actually a good thing for me for now.
Click to expand...
Click to collapse
i would definitively if i were you. not everyone is affected but some are so...
Sensors bug fixed thanks to great teamwork of many members in this forum! Solution available in sensors bug thread!!
Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader
mikeprius said:
Had no issue with sensors but am stock unrooted since the phone was purchased. From that link it appears it may be a rooting issue. I'm surprised that that it didn't go away though after wiping and reflashing stock images and relocking the bootloader
Click to expand...
Click to collapse
still nobody knows what caused it but according to some users it seems it happened also for people who never modified their phones (people with not unlockable bl)
It's weird, this sensor bug everyone is having i never once had sth like that, flashed the official q factory image from beta 6 via the tool-all-in-one app. What i was thinking is, does the phone have different hardware revisions ? I am with the initial rev and can't tell
Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?
Hello.
I have the freeze too. Random freezing from the notification. Freezing with the recent app. Sometime black wallpaper with Nova Launcher.
The Q is with bug who don't have the beta or Android 9....
mikeprius said:
Gotten at least 3 random reboots since taking. Anyone else getting periodic recent app switching freezing or random reboots?
Click to expand...
Click to collapse
Yes, I've had a few random reboots since updating. It's been happening randomly in Google maps, YouTube, etc. I don't really want to factory reset unless I have to though.
Hey guys here is an android 10 bug on my Verizon pixel 3, when I goto the recent apps and try to clear them they will all get cleared and then when I go back to it they are all still there. Anyone else having this problem?
Im using google Launcher, and when I change the gestures sometime they all clear for good but sometimes they still won't until I restart the phone.