Related
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
The issue is real and Google have confirmed it. They've been working on a fix and the official word was an OTA update was going to be released this week:
Just a heads up that our initial tests look good and that we are expecting to send out an OTA within one to two weeks that will resolve the issue. Thanks for your continued patience!
Click to expand...
Click to collapse
code.google.com/p/android/issues/detail?id=13674
silfer said:
It always seems to pop up in the forums but it has never happened to me. I've had mine for almost a month now and it all seems to be perfect. No defects with screens or buttons or reboots. Maybe im just lucky...or people with complaints are just louder than ones who are satisfied.
Click to expand...
Click to collapse
Argh. I did not have this problem until yesterday (had the phone since January). Now my phone will reboot right after a call.
apreichner said:
I keep hearing about this unfixed Nexus S reboot bug. I'm curious... is it really so widespread? Or is it only something a few people experience, like the luck of the draw?
I apologize if this question has been asked before. I'm considering buying the phone but can't decide if I should wait.
Click to expand...
Click to collapse
I've had three Nexus S so far. The first one I picked up on dec 16th and didn't get a single reboot on - but the oleophobic coating on the screen was coming off in spots so I swapped it for another unit.
The second unit had issues rebooting. I saw it immediately - it rebooted while sitting on my desk. I could constantly recreate this by streaming audio over BT in my car - every 10-15 minutes it would reboot.
I picked up a mt4g for a few weeks to see if they could sort whether this was a hardware of sw issue (that thing is a brick to hold) and eventually picked up a third Nexus S once they identified it as a SW issue. This device has not rebooted a single time in the 27 days I've had it. I can stream audio and make long calls without an issue.
All three devices have operated with identical configurations. Based on this I'd say that some units are worse than others.
Maybe it's issue with the hardware tolerances and some hardware that falls within the accepted tolerance is not operating as expected and causing kernel panics as a result. This would explain why some have this issue constantly and others rarely or never see it. Perhaps it's something seemingly unrelated that everyone experiencing the reboots has in common. It would be nice if Google weren't so tight lipped about this. Supposedly the OTA will address these issues and moving forward it should be irrelevant.
I get this issue at least 60% of my calls (not that i call much). i have made 4 calls today, and 3 of them my phone rebooted during the proccess.
I am returning this to CW tommorrow for a replacment unit, i love the phone dearly but do not want to be robbed for £429 but not being able to take it back if they do not resolve.
It could be a batch issue, or something i guess, but that's not my job to find that out, that's for the people i paid for the hardware/software
I hope i get another unit, and if not problem free at least i can rely on a warranty, hopefully making sure if google slack on fixing this i can get my money back.
If it fixes soon or the new handsets ok, i can keep this lil beauty of a phone
I've had my SNS since launch. My phones has rebooted on me twice. It was right after playing a 3D game. Right after i exited the game the phone rebooted. Funny though, it hasn't happened again.
I've gone back to using my Desire until Google sort this out. For me, any call above 5 minutes has a 50% chance of rebooting the handset.
The handset (running stock 2.3.2 and un-rooted) will on occasion spontaneously reboot as well. Not good.
It is a bug that seems to be very limited in scope but is very serious for those affected. Personally, I've never had it happen to me or my wife.
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
apreichner said:
Thank you for your replies, they were very helpful. I was keeping up with the OTA Bugfix promised by Google for the Nexus S. Although, that was promised almost 3 weeks ago and still no word from Google since. That's one of the reasons why I came here to ask for advice before I bought the phone. Although I'm curious to see if 2.3.3 resolved the issue. I know the 2.3.3 just lists API changed, but I wouldn't expect them to list bugfixes on a list of API changes.
I think I'm ready to buy the phone and hope for the best. I'll probably just get Best Buy insurance just to be safe.
Click to expand...
Click to collapse
Getting the insurance is definitely the right choice. I hope you enjoy your phone and your stay here!
I get periodic reboots on both my phones.
It is not that noticeable, since it often happens when I am not using the phone and unless I glance at it and see the start animation, I may be unaware of it.
But it has happened during a call as well (couple of times on each phone) and then it is definitely noticeable.
I have this bug... not during phone calls but random reboots. 2-3 a day. I hate it but its tolerable.
Weird, I don't have this bug
If flashing a custom rom, the problem will be solved? Since i am considering if i should get Nexus s later on.
Thanks
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 of Saturday, my Pixel refuses to make or take phone calls. It seems to work flawlessly in all other regards.
If I get a phone call it takes a long time to acknowledge that I've selected to answer the call. I can then neither hear the other person, nor can they hear me (no line noise, complete silence). If I choose to hang up, the Phone app ceases to work, and within a few minutes the whole phone reboots. Making call doesn't even get that far, as as soon as I initiate the call the phone app ceases, and again, within a few minutes the phone reboots.
I chatted with Google Pixel Help twice yesterday. They checked a bunch of things with me, then suggested a factory reset when those didn't work. Yesterday, the issue only seemed to occur after the phone had sat idle from a reboot for a while. So initially after the factory reset things were working. When I got home, however, the problem persisted, and was now occurring every single time the Phone app was used. It's now 100% reproducible:
https://youtu.be/5YSJpLVBR1A
https://youtu.be/sENelMnE4eI
I've tried using 3rd party dialers, but they all seem to throw over to the stock phone app as soon as the call is made. I have no idea what happened.
Google hasn't been helpful, as their support person said I'm out of warranty (purchased in late-Oct. 2016), and thus have to deal with Telus. I have I feeling I know how that's going to go (ie: not well).
Anyone else ever experienced anything like this?
Happend to me too.
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
saltorio said:
I just got an email back from the Google Store Support manager. She just reiterated that the phone is out of warranty and suggested that I visit UBreakIFix to see about getting it repaired.
Overall, I'm quite unimpressed with Google's support on this. If I have to replace the phone, I'm seriously going to consider something other than Google.
Click to expand...
Click to collapse
Well I mean if the phone is out of warranty they are following the same guidelines literally any other manufacturer would. Their response is kind of a non-problem and your reaction is kinda poor. Anyways for now try rolling back to the factory image before current and then updating back to current, might do something.
Edit: preferably keeping the -w intact but you can try dirty flashing it first
I can't recall when this first started happening, I'll say about a few months back. I have a Google Pixel 1 phone, and at times when I get a call, the phone app would freeze and I can't hear anything, and when I go to make a call, I don't hear the ringing sound or anything. I also noticed if I try to play apps with sound such as snapchat, youtube..the audio will not play. The video plays just fine but there is no audio. I've tried factory resetting the phone and that didn't do much really, because sometimes it'll work, and other times it'll just freeze out of random and start rebooting. I am on a 2 year contract with verizon, I got the phone November 2016 and most of it is paid off, but I don't have insurance. I called Google and they said my warranty expired November 2017. So I'm just wondering what I can do. I want to downgrade back to Nougat because I did some research and people say ever since updating to Oreo is when these problems started to happen. I don't know if that's the case with mine because I really like the pixel and want to use it, but I just don't know what else to do.
solidwing68 said:
I can't recall when this first started happening, I'll say about a few months back. I have a Google Pixel 1 phone, and at times when I get a call, the phone app would freeze and I can't hear anything, and when I go to make a call, I don't hear the ringing sound or anything. I also noticed if I try to play apps with sound such as snapchat, youtube..the audio will not play. The video plays just fine but there is no audio. I've tried factory resetting the phone and that didn't do much really, because sometimes it'll work, and other times it'll just freeze out of random and start rebooting. I am on a 2 year contract with verizon, I got the phone November 2016 and most of it is paid off, but I don't have insurance. I called Google and they said my warranty expired November 2017. So I'm just wondering what I can do. I want to downgrade back to Nougat because I did some research and people say ever since updating to Oreo is when these problems started to happen. I don't know if that's the case with mine because I really like the pixel and want to use it, but I just don't know what else to do.
Click to expand...
Click to collapse
It sounds like you have audio codec defect. Downgrading back to nougat probably will do no good (I'd still try it though because why not). Its a common problem that effects the Pixel and Pixel XL manufactured before around January 2017. I have had this happen to 2 pixels
**** man, yea my problem looks like alotta other people have the same or similar issue. So far though my phone's been good for a day now so cross my fingers it stays good
I know there are memory management issues with this phone; what I'm not sure though is if the behavior I'm experiencing is just a manifestation of this well-known problem or another issue.
Since I got the phone a month ago, after some period of use after rebooting, simple actions like switching between two apps can cause the phone to hang for a long time - usually 20 or 30 seconds. The phone isn't completely hung - I can still go back to the home screen, and do some things, but whatever app I tried to switch to will be non-responsive for this whole time. Eventually, it will just start working again.
Other times, typing using the google keyboard will get stuck - that is, I can still type, but nothing shows up in the field where the text should appear. After a while it will suddenly "catch up" and everything I typed appears.
These two issues both seem to start happening around the same time, so it seems memory use related, but the amount of time involved seems very excessive for swapping.
I can fix this just by rebooting, but it always comes back after a while. I suspect it's related to how many different apps I've loaded and not just time of use, though, since sometimes it won't happen for a day or two, but it always happens again at some point.
I removed a bunch of apps that were migrated from my old phone (a Motorola Z Force), too, to try to eliminate a badly-behaving app, but I never had any issues like this on that phone, and it didn't make any difference.
Is anyone else experiencing this? Or does it sound like a possible hardware problem? I don't want to swap the phone unless it's clear this is abnormal behavior. Thanks.
It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?
samnada said:
It's abnormal behavior. My first thought is it might be related to a balky network or intermittent connection. Just a wild guess. Do you see the same issue in airplane mode? Also, if you check battery or cpu usage is anything hogging resources?
Click to expand...
Click to collapse
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.
jamtre said:
I've used the phone in exactly the same circumstances as my prior phone (and other devices) so I don't think it has to do with network connectivity; but next time it happens I'll try switching to airplane mode just to be sure. There's no visual indication of a network drop (e.g. wifi status icon). I haven't checked for anything hogging resources during these events, and generally I'm not having any battery life or performance problems. It's just switching apps that brings everything to a standstill for a while, and then it works fine again.
Click to expand...
Click to collapse
Maybe check the temp when it's stalling. This app might show something: https://play.google.com/store/apps/details?id=com.glgjing.stark&hl=en_US
I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.
mrchuckfl said:
I have the exact same issue as OP describes.
Had a 64gb Pixel 3 when it was first released and it manifested the issue with the random hangs and freezes. I decided it was too buggy and returned it.
A month later got a 128gb Pixel 3 on the gift card promo and it is exhibiting the same issue as the OP and my original 64gb unit.
Doubtful it is a hardware issue since this is my second one with the same issue.
I have tried factory reset and removing any un-necessary programs on both, but the condition still persists.
Both phones were on Fi.
If the January patch does not fix the issue it will be time to switch back to iPhone.
Click to expand...
Click to collapse
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?
jamtre said:
Mine's 128gb (Verizon). The January patch looks trivial so not expecting any change here...
Not going to switch to iPhone but troubling that you have had this with two different phones. At the same time, pp seemed to think this is not typical behavior, and if it's a common OS issue then wouldn't a lot of people be talking about it? I'm not a crazy power user or anything, I never play games, pretty much use Waze, whatsapp, camera, facebook (lite), spotify, etc... really pretty standard apps.
I wonder if there's something unique to us that could be involved here? I'm not using any apps I wasn't using on my old phone, but I also had Oreo before and not Pie, so not a direct comparison. When I first set up my phone, though, all my old apps were migrated, including some Verizon bloatware I couldn't delete from the old phone. Is it possible that apps that were automatically migrated (but later deleted) could have left something behind that's causing issues with PIe?
Click to expand...
Click to collapse
I have have been on Google phones since Nexus 4 and upgrading like a good consumer every year.
Like yourself I am not doing anything crazy and have the run of the mill stuff like FB, Snap, kik, Whatsapp and IG. The only thing out of the ordinary I have on the phone is Cerberus and BlackBerry email.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.
mrchuckfl said:
I have the exact same issue as OP describes.
Apps don't get migrated so that is not the issue. When you setup a new phone or transfer, some of the data is moved, but the app is re-downloaded from the app store.
Click to expand...
Click to collapse
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.
jamtre said:
Right - but it installed -everything- I had on my old phone including some Motorola & Verizon apps, which I then uninstalled (but maybe even missed some). Just thinking it might be possible that something hardware-specific to my old phone got installed on the pixel. In theory shouldn't matter but there seem to be so many nuances to Android, particularly across major releases, that I wondered if this could have been involved in the problem.
Anecdotally, it seems like it's been happening less often over time. I haven't had it happen in a few days, though I installed the update yesterday so I'm within 24 hrs of a clean boot now.
Click to expand...
Click to collapse
I've been having exactly the same issues for the last couple of days. Have just done a factory reset but the problem persists. The biggest issue is that when the phone is locked it seems to freeze as well and takes about 15-20 secs to unlock. Also if you phone it while its locked (and frozen) the incoming call isn't acknowledged (no ringing !) until after its unfrozen. Looks like I may have to return it and get a different phone !
Mike
More than a few people have been having issues with their Pixel 3, but I've yet to experience a single issue with memory management or slowdowns. In fact, I've found the Pixel 3 to be a far smoother UI than the iPhone X on the newest versions of iOS. Maybe I got lucky, but I'm more inclined to think it's about use. Just like my desktop operating system, I start from scratch every time I do a reformat, reset, or upgrade of a device. I can see there being issues with migrating old data. I'm also a fairly light app user; I've got around 100 apps in my drawer, most of which are Google apps or banking apps. Are the people experiencing these slowdowns installing a lot of things or running more resource intensive apps like Facebook? Not to say you shouldn't be able to do that with your phone, but I'm curious how behavior differs in our situations.
Feb update?
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!
jamtre said:
OP here, so more than a week since the February update landed and I have not had this happen since then. I'm kind of shocked, honestly, and keep waiting for the other shoe to drop, but so far it looks like something they did fixed this.
The only other significant change I made was to uninstall the Facebook Lite app, a few days ago, but I've used that long before I had a Pixel 3 so doubt it's related. So... :fingers-crossed:!!
Click to expand...
Click to collapse
Maybe I should give Pixel 3 a try. Tried P3 twice since October and it was a phenomenal laggy mess specially under load ... My Pixel 2 had its ups and downs, specially with the Pie release. Took them 3-4 months to 'get it right' so I'd expect Pixel 3 to be no different.
I was experiencing some lag and short freeze (2 to 7/8 seconds) with my pixel after the latest update.
I tried a factory reset with little hope but it seems it did the trick for me. No issues ever since.