Database Info

Let's recap the new update

After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?

The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.

aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?

I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....

For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...

* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to

htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.

GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server

Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens

MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!

dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.

JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.

alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly

JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck

krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...

JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?

GPS locks on a lot faster...but still loses accuracy in middle of route.

[Q] Legend 2 ICS Edition GPS Problem for Infuse

Hey guys, so I just finished up changing my infuse over to Legend 2 ICS edition and I've been playing with it for about a week and I'm having a rather large issue. Whenever I leave the gps ability enabled so that my apps can find where I am the phone has a tendency to dump battery life like there is no tomorrow but worse than that it stops sending and accepting text messages randomly while the rest of the phone continues to operate. There are no warning signs so that I know this is happening and I have to reboot the phone to get it to work again. If I leave the gps feature off this is not an issue however, this is rather useful to have running so that my apps all work. Any idea how to fix this problem?? Thanks for your time.

I've been running legend 2 for almost a couple weeks and legend before that, my gps was buggy at first-it wouldn't lock on to my location. I did a complete wipe and reinstall, then let the phone boot up and let it settle for a while before I did anything else. Haven't had any problems since
---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1318160
http://forum.xda-developers.com/showthread.php?t=1561463
use clean wipe, I run that a few times just before I flash a rom now, haven't had any problems since I started using that.

Thanks a bunch I'll try that out and get back to you on if it works or not in the next couple of days.

Thanks
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.

Klevin2011 said:
Sorry it took me so long to get back to you, work had me pretty tied up for a while. Thanks for the help everything seems to be working fine for the most part now. I need to reboot every once and a while due to overheating but I think thats just the fact that the phone is adjusting to the new ROM. Thanks again for the help.
Click to expand...
Click to collapse
Hmmm, the phone shouldn't be overheating at all, do you do any tibu system restores? I've had an app cause an overheating problem before. One thing I've learned is when you do allot of flashing, checking out different roms or themes, its good to just do an odin or hemdall flash back to stock that has repartitioning.
It gives you a fresh start.

TiBu
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.

Klevin2011 said:
I have done TiBu on the phone however I did have to flash it back to stock with odin partway through flashing this rom the second time because I bricked the phone, I'm still at a loss because I need to restart the phone usually once a day because it stops accepting and sending text messages without warning while everything else still works. It's kinda weird, I've been chalking it up to the fact that its a new rom and the phone needed to get used to it but it doesn't seem that way anymore.
Click to expand...
Click to collapse
Have you tried the new version 3 to see if maybe that helps? This is first Ive heard anything like this. I guess it works fine using another rom?
Sent from my SAMSUNG-SGH-I897 using xda premium

I didn't even know there was a version 3. I'll have to go take a look at that and see what happens. Thanks for the help.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Still having issues
Ok so I'm still having an over heating issue and my phone refuses to send or recieve texts for periods of time. I'm going to delete a couple of apps to see if they're causing the problem. If that doesn't work any chance that I'm having a hardware issue with the phone, it wouldn't be the first time I've had issues this would be my 5th replacement due to hardware issues in the phone.

[Q] Root and ROM rookie questions

Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?

Disable Ripple Effect
CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
Try disabling the ripple effect in your lockscreen settings. That is a known issue with any lockscreen other than the stock one.

Seriously a new version of MOAR? Dang it seems like every time I downloaded the new version they're putting up a new one. Which isn't a bad thing but still. Did they say this on the thread?

CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
What kernel are you using?

airmaxx23 said:
What kernel are you using?
Click to expand...
Click to collapse
Where can I find the kernel information?
So with a couple tests, I found that the phone tends to soft reset twice if I enter the wrong swipe password, not sure why it has to freak out like that but it's annoying. That's the only time it's been resetting now. The other issue, screen turning back on after I turn it off with the power button, is still persisting but isn't happening in any discernable pattern.

Okay so I found the kernel information, it says
"3.0.31-1152558
[email protected] #1"
People in the MOAR forum (Verizon S3) have had problems on the reboots with the Blackberry lockscreen, but I'm on Rotary so that doesn't help.

Phone keeps rebooting randomly and shuts down when idle for too long (during night)

Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong (I also posted in the T-Mobile S6 Forum).
So my story, I got a refurbished unit G920T at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!

Well, if this is happening across multiple roms/software it can only really be hardware at fault I would think?
Sent from my SM-G920F using Tapatalk

jr866gooner said:
Well, if this is happening across multiple roms/software it can only really be hardware at fault I would think?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Hello!
After I posted this I ended up talking to T-Mobile and apparently the phone still is under warranty and they sent me a shipping label to return the phone and get another one from them.
Which is good but also I tripped KNOX but I don't know how much they care about that.
Fingers crossed I guess.
Thank you for replying!

Good to hear of a semi positive result! Let us know!
Sent from my SM-G920F using Tapatalk

Random reboots

My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Sent from my Pixel using Tapatalk

rosswaa said:
My pixel had decided it's going to randomly freeze and reboot itself
It does it a few times a day and doesn't seem to matter what apps are running
Is there anyway of logging the reboots without root to find the cause?
Click to expand...
Click to collapse
Same thing happening to me here too.

What I would do is start from scratch, install factory image, don't install any apps, use for a day to test, then install your apps one by one to find the culprit.
If still rebooting without any apps installed, it might be time for a rma
Sent from my Pixel using XDA-Developers mobile app

I used that Google support and came down to putting the phone I to safe mode for 24 hours to see but some days it does it a few times and other days it's fine
Sent from my Pixel using Tapatalk

Has there been any resolution to this? My Pixel has been randomly rebooting, too. Already tried troubleshooting with Google tech support, tried Safe Mode (did it there, too), and factory reset and cache wipe.
It still happens. And when I say random, I mean random. Sometimes it reboots overnight, sometimes in my pocket, sometimes as I'm using the phone (it'll freeze in some cases too before it reboots). There's no obvious indication of what's causing it.
Has there been any light shed on this problem? Any clue as to whether it's software or hardware related?

Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk

rosswaa said:
Some days it doesn't, others it'll do it 5times. I've not had any luck fixing it which is annoying because it awesome except for that
Google aren't very helpful either, they refused to help because I got my phone through carphonewarehouse lol
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yeah, there really is no rhyme or reason to the way it reboots, making it even harder to diagnose.

Rebooted again while it was just sitting on my table. No rhyme or reason to this bug.

I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.

UnusualSuspect said:
I've had my 5" Pixel since launch. Google Store device, 32GB, never unlocked the boot loader.
I had a few random reboots, but never actually saw it happen. I'd go to use my phone and see the pattern unlock screen you get on first use after restart.
I have not had it occur since the January OTA.
Click to expand...
Click to collapse
Same here. Sometimes I'll go to my phone wanting to use it, try my finger to unlock, and it'll prompt me to input my pattern because it's required after a reboot. Clearly, rebooting by itself.
It's frustrating because there's no rhyme or reason to it. Sometimes it'll happen multiple times a day, sometimes it won't happen for a couple of days.
At first, I thought the Jan update fixed it too because it didn't occur for a while after the update, but then it reared its ugly head again. I've already tested it in Safe Mode, did a factory reset, and the rebooting still persisted.
If you simply research this on the web, many others are having this issue. And it's even been reported a few times by Android sites/blogs. Google needs to get on top of this. At the very least, they should confirm it's a software issue and not a hardware issue.
---------- Post added at 10:08 PM ---------- Previous post was at 09:09 PM ----------
Just a few links of people online reporting this problem:
https://productforums.google.com/forum/#!topic/phone-by-google/QHp96fk4Ygw
https://productforums.google.com/fo...vS_XxvBh8;context-place=forum/phone-by-google
https://www.reddit.com/r/GooglePixel/comments/59i9e5/pixel_xl_random_restarts/#bottom-comments

Happens at random but only when I'm using Chrome or when my Pixel has been sitting on my nightstand charging.

I've had the phone since launch with no issues. My random reboots just started yesterday and it's happened 5 times in the past 12 hours. Glad I'm not the only one with the problem.
Sent from my Pixel XL using Tapatalk

im thinking this is a hardware issue, im pretty annoyed if it is! i get it like 6 times a day or nothing for a while, makes no difference what im doing or apps being used

Going to try and get a replacement this is a joke, fully wiped and flashed and still does it
Sent from my Pixel using Tapatalk

Mine hasn't really been "rebooting"... It's actually just been suddenly shutting completely off for no reason. It will be fine for a few days, then the next fee days it will simply abruptly shut off for no reason... Battery levels don't seem to make a difference.. Weird.
Sent from my Pixel XL using Tapatalk

For me it seems that the reason lies in Bluetooth or just in the BT stack. If I deactivate bluetooth it works fine through the day. But I need bluetooth so I started BT again and the Pixel XL 128GB crashes sometimes 10 Times a day, but as I checked BT was automaticly deactivated after these first reboots. I seemed. The Pixel stopped rebooting as I activated BT and deactivated it myself.
And now? How long do we have to wait. I don´t think it´s a hardware issue.

So, I have this issue but it became (very) apparent only after the OTA Oreo. First two weeks were fine (and subsequently first two weeks after a factory reset I've done), but then it slowly starts doing this after those 2 weeks. Freezes then reboots. At first it's 1-2 a day, now it's like 12-20. Ridiculous. There's a buganiser thread for this issue and Google is aware of it. Most of the bug reports have this in them:
Code:
Sense Key : Hardware Error [current]
which Google rep says is a hardware issue. I also have an access to a Google's internal buganiser thread on this issue (i'm a vendor) and they refer to this being a Toshiba's memory issue. Not sure though why this started happening only after the Oreo update. Also people who flash Nougat report no issues as well. Another funny thing is that there's at least two users with Pixel (XL) 2 who suffer from it. Anyway, I'll be giving it back to my carrier over the weekend (glad we have 2 year warrant here in UK) even though I'm pretty sure I'll get a refurb with a similar problem after two wasted weeks of wait.

Flash nougat rom and see does this problem occur or not? If not then us nougat for a while then again update to oreo