Related
Read on... before you just see the post and start flaming.
Been having a helluva trouble with my Galaxy Note II since a month now.
It all started a day in April when I was on a weekend break and my charger just stopped working. Not the charger, but the charger port. I even tried a few other chargers and none of them worked, whereas my charger worked on other phones.
So after the weekend without a phone I come back home and read some posts on XDA about moisture in the USB port. I blow dry the port with the hair dryer and things start working again. After a couple of days of flawless working, again the problem comes up. But it is nothing that a few 'frustrating' 20 minutes of fidgeting will not solve and so goes life.
There have been a few days where it has gotten so annoying that the phone simply wont charge no matter what I do and which angle I place the phone (yoga for phones, anyone?). The phone has even switched off completely at times. Yesterday was one of those days when it simply wouldn't charge.
So again I spend a lot of time on XDA and Google and what makes consensus is that there is moisture in the USB port, or there is something wrong (loose connection) with the USB port and it needs repair.
Few facts before we get to that, and my point about this being a software problem.
1. The charger, when it works, works flawlessly irrespective of whether it is on the table or hanging by the charger from the power outlet. I expect that in case there is a loose connection, the position becomes very delicate.
2. The charger, when it works after moving the wire around for a while, keeps disconnecting occasionally even though it has been placed on a stable table surface and no one is disturbing the table. After some seconds, it connects back automatically and begins charging.
2. The phone works without any problem whatsoever when I plug it into the Samsung car charger - never once do I remember it not working
Now here are my findings from yesterday after I almost broke the phone in frustration.
1. On a whim, I decided to do a factory reset of my device. After fidgeting with the phone for 4-5 hours and it not charging, it magically started charging after the factory reset.
2. After the reset and a 1 hour charge, I updated all the default software on the phone - including 1 samsung update, 1 allshare update, and 1 push service update. Within a few minutes of this update, the charger started showing the 'loose connection' problems again. I also noticed that at times the phone screen would switch on for no reason - for only 2-3 seconds.
3. Again I reset the phone, and force stopped some samsung services and disabled as many samsung services as I could and I could notice consistent charging.
I subsequently installed some apps (not going full out as I want to observe the behaviour) and occasionally the charging stops. I then go into the application manager and shut down some samsung services and more often than not the charging starts working.
After all this circus, I believe there is something wrong with the Samsung services, the phone device drivers, or the MTP service. It does something when it detects a cable being inserted and causes a malfunction of the phone. This is what it looks like to me.
In fact the same problem happens when I plug in the phone to the PC too. The connection keeps breaking and the phone is just not usable from the PC. However the interesting thing is that when the USB / MTP breaks, the charge is still working and the orange light is glowing.
So, finally the XDA relevant question. Can you guys help me find out if it really is a software problem or just some strange co-incidence? Are there any traces that I can pull out to see which app/service is causing the problem? There are many apps/services that I would like to disable, but they are greyed out - is there anything that I can do about them?
Mind you that my phone is not rooted - so all the usually available apps might not work for me. I use the phone as a corporate device and I can't violate rules by rooting the phone.
Any tips, suggestions, ideas, flames?
Hi I'm having the exact same symptoms as you I wondering if you got to the bottom of the problem? Many thanks
Sent from my GT-N7105 using xda premium
My wife has same problem with her note 2 since yesterday. I'll test and share the result.
Sent from my GT-N7100 using XDA Premium HD app
Are you sure it's not the cable? Because many stock cables tend to be crappy, just try another one if you haven't. It doesn't have to be just loose connection.
Works here fine without issues, so doubt it's software. I rooted mine almost immediately, so can't say much about that though.
Ive tried 3 different cables and every time I plug one in s voice launches lol
Sent from my GT-N7105 using xda premium
Could be a problem with newer Samsung phones and their construction. I have a friend who has a Galaxy S3 (not Note 2) who's gone through FOUR phones so far -- all of them with the same problem of the charging port dying after a while. T-Mobile's insurance company is starting to give him dirty looks, poor guy ...
He gets intermittent charging before the phone stops charging completely. Now his phone is hooked up to the charger constantly while he's at home because of battery issues, so it's possible he's putting excessive strain on the charging port. My thinking is that it's a hardware issue rather than software, but who knows with these things.
mudge
my friend's note 2 having quite similar problem, every time plug in the cable, the phone start charging after some minutes. not the problem of cable, i tested the cable and charger with my phone. Plan to send it to service center.
Sent from my GT-N7100 using xda app-developers app
Exact same problem for N7100 (international version)
I have been facing the exact problem described above. The service center has blamed water logging to be the issue. But seriously doubt it since the port seems to be working fine when it really functions. Also i noticed that when i restart my phone few times it starts to work fine(without me touching the charger cable or the charger itself). I guess its a lot to do with the software than the hardware
note 2 Gt-n7105 bootloops, with charger doesnt boot loop
Hi,
My note 2 seems to work perfectly fine when i connect my charger. But when I disconnect the charger when its full charge it turns off.
When I turn the phone on without the charger it comes on the screen where it shows the "samsung galaxy note 2 gt-n7105" its begins to boot loop.
Can someone please give me some solutions.
Has anyone ever solve this? I have the same on my S4....
I too have the exact problem of phone getting connected and then disconnected automatically in few minutes.
I fixed mine with the same issue
Power usage
Hi,
I first saw this when I was using my sat nav app in the car, I turned off the Performance optimised when plugged in option in favour of a lower power option and the problem went away. As I get more applications on my phone I see this more and more.
Could this be the power usage of the phone? The charge will supply 500ma, if the phone is already using a good portion of that the battery will not charge, so the phone shows the charge intermittently as the phone uses slightly more and slightly less power when the cpu, etc wakes and sleeps. More apps running uses more time on the cpu so more power. And of course as the battery gets older this would display itself more.
Just an idea based on what I've seen...
My Note 5 just started doing this, and only on the car charger using the Adaptive Fast Charge port. Charges for 2 seconds, off for 2 seconds, charges for 2 seconds. Using the normal port it charges fine, just slower. I have the Adaptive Fast Charge adapter at home and in the car, it works fine at home.
usb A3 usb issues
for mine it is intermittently not being recognised in file manager and also charging and then not charging round and round making beeping noises. This started when I dropped it partially in a bowl of oxtail soup. At the time it wouldn't recognise any cable at all. After I cleaned it with a cotton wool bud it was working again for ages but every now and then it wouldn't be explorable in windows. Now its acting up again, very difficult to get it to detect in windows, it starts charging when I plug in the cable but not in file explorer.
It's a real pain because its a samsung a3 which is difficult to open. I think really I will have to get it repaired - opened up and cleaned inside properly or have the usb port replaced.
I've watched many videos about mtp drivers and cleaning and bending the usb port a bit etc etc for many of you I think cleaning the port and/or bending the usb tab a bit would help, good luck.
Stop posting your damn problems so some one can answer it. Jesus look at the posts and see if there is an answer.l cuz you asking makes no difference because u have to scroll to the bottom to see an answer any ways. So just w8. Also ya it's software thing.... Samsung kinda sucks but what the hay I love them anyway even tho thay, including the expencive ones, are crap
In the past week, my wife's 1 yr old Tab 3 10" has become flaky to charge and as of last night we can't get it to charge at all.
Tried several cables and different chargers around the house, no luck. The port is very loose so at first i thought maybe it was just worn out and wasn't getting a connection. Tried the freshest tightest cable i have in the house and couldn't get even a moment of charging so i've ruled that out.(or it's more worn out than i can imagine)
Saw a suggestion about the 7" model to disconnect the battery for a bit to resolve a similar issue. Gave that a shot but no dice.
After that I noticed something interesting.. one of my chargers stopped working when i plugged her tablet into it. until i unplugged it from the wall for about a minute, it wouldn't charge anything else. 3 times it played out just like that - charger works, plug in her tablet, charger doesn't work.
Then I plugged the tablet into my Macbook Pro and things got really fun.. it shut down instantly and won't power back up at all(i'll deal with that later on).
So,.. my assumption now is that there's a short in the micro USB port.. does this sound logical to anyone? Or could an issue like this be caused by something else that's not as fixable?
This is really disappointing because we've been generally happy with samsung products.. but this just seems too soon to have an issue like this. At least it's easy to take apart.
Sorry if this is a common issue that's been covered.. couldn't find any info relating to the 10" model. Thanks in advance!
esmoger said:
In the past week, my wife's 1 yr old Tab 3 10" has become flaky to charge and as of last night we can't get it to charge at all.
Tried several cables and different chargers around the house, no luck. The port is very loose so at first i thought maybe it was just worn out and wasn't getting a connection. Tried the freshest tightest cable i have in the house and couldn't get even a moment of charging so i've ruled that out.(or it's more worn out than i can imagine)
Saw a suggestion about the 7" model to disconnect the battery for a bit to resolve a similar issue. Gave that a shot but no dice.
After that I noticed something interesting.. one of my chargers stopped working when i plugged her tablet into it. until i unplugged it from the wall for about a minute, it wouldn't charge anything else. 3 times it played out just like that - charger works, plug in her tablet, charger doesn't work.
Then I plugged the tablet into my Macbook Pro and things got really fun.. it shut down instantly and won't power back up at all(i'll deal with that later on).
So,.. my assumption now is that there's a short in the micro USB port.. does this sound logical to anyone? Or could an issue like this be caused by something else that's not as fixable?
This is really disappointing because we've been generally happy with samsung products.. but this just seems too soon to have an issue like this. At least it's easy to take apart.
Sorry if this is a common issue that's been covered.. couldn't find any info relating to the 10" model. Thanks in advance!
Click to expand...
Click to collapse
well, if according to my understanding of your description, that is what happening to me now.
You can try my method which is working for me.
If you didn't mess your boot partition up. you can leave it drain for like hours to days *I have tried to leave it for 7 to 9 days... * and charge it again, keep charging about 30 minute to an hour when you see charging sign, then proceed to Section B if you brick your device. If you don't, just start it up normally and let it charge up to 100% before you discharge.
>Drain the battery by leaving it uncharged for hours to days
>Charge it on, you will see charging sign
>Leave it charge for hours
>DONE!
OR
You can replace your battery
http://www.ebay.com/itm/T4500C-T450...765?pt=LH_DefaultDomain_0&hash=item5669e27b05
And I guess maybe you have a p52xx (Tab 3 10.1 from samsung and not fom tmobile etc.) , remember to use 2.1 A x 5 v charger. Do Not use Laptop Power to charge your device . It may be a bug or hardware issue for this problem.
you can pick up something useful for your situation here, http://forum.xda-developers.com/gal...p52xx-soft-t3051604/post59361000#post59361000
forget about the bricking...
Jacker31 said:
well, if according to my understanding of your description, that is what happening to me now.
You can try my method which is working for me.
If you didn't mess your boot partition up. you can leave it drain for like hours to days *I have tried to leave it for 7 to 9 days... * and charge it again, keep charging about 30 minute to an hour when you see charging sign, then proceed to Section B if you brick your device. If you don't, just start it up normally and let it charge up to 100% before you discharge.
>Drain the battery by leaving it uncharged for hours to days
>Charge it on, you will see charging sign
>Leave it charge for hours
>DONE!
OR
You can replace your battery
http://www.ebay.com/itm/T4500C-T450...765?pt=LH_DefaultDomain_0&hash=item5669e27b05
And I guess maybe you have a p52xx (Tab 3 10.1 from samsung and not fom tmobile etc.) , remember to use 2.1 A x 5 v charger. Do Not use Laptop Power to charge your device . It may be a bug or hardware issue for this problem.
you can pick up something useful for your situation here, http://forum.xda-developers.com/gal...p52xx-soft-t3051604/post59361000#post59361000
forget about the bricking...
Click to expand...
Click to collapse
Thanks for the response.. I'll keep it in mind for the future. For now, this did end up being a bad usb port.. i ordered the part same-day on Amazon and had it swapped in 10 minutes. as soon as it was back together it was charging normally again. kudos to samsung for not soldering the usb port to the mainboard!
esmoger said:
Thanks for the response.. I'll keep it in mind for the future. For now, this did end up being a bad usb port.. i ordered the part same-day on Amazon and had it swapped in 10 minutes. as soon as it was back together it was charging normally again. kudos to samsung for not soldering the usb port to the mainboard!
Click to expand...
Click to collapse
alright then, congratz for you got ur device back alive again
First it stopped fast charging. I then later it would only charge sometimes and then accidentally dropped it and now it wont charge at all. I don't know what to do. I tried another note 4 charger and it won't charge on that either. I just got the phone last Feb and it broke already? Is there anything to try before I take it somewhere to be fixed?
Phone won't charge on a note 4 fast charger
Tried 2 note 4 fast chargers.
When the phone is off it sits on the screen with the battery and the thunderbolt but never charges or shows a charge %.
Please help. The phone is in a pelican case. It doesn't look damaged from the outside but I don't know about the inside.
Edit: As soon as I posted this I tried again and it charged with fast charger. I don't understand what is going on.
Maybe the charging port is loose...You can try using wireless charging thought that will require a new back cover/ insert and a qi charger
Warranty. Go to AT&T Device Service Center
The battery could be defective as well. Try another battery or take it to ATT and tell them its not charging, they should have an extra battery to test with as well.
When you tried the other chargers, did you use their cable or the power block with your cable. My son had a similar issue with his Note 2 and did what you did but used his cable. Turns out the cable had a short in it. Replaced the cable and it charges fine ever since.
herox said:
first it stopped fast charging. I then later it would only charge sometimes and then accidentally dropped it and now it wont charge at all. I don't know what to do. I tried another note 4 charger and it won't charge on that either. I just got the phone last feb and it broke already? Is there anything to try before i take it somewhere to be fixed?
Phone won't charge on a note 4 fast charger
tried 2 note 4 fast chargers.
When the phone is off it sits on the screen with the battery and the thunderbolt but never charges or shows a charge %.
Please help. The phone is in a pelican case. It doesn't look damaged from the outside but i don't know about the inside.
Hi did you fix it ?
Edit: As soon as i posted this i tried again and it charged with fast charger. I don't understand what is going on.
Click to expand...
Click to collapse
hi did you fix it ?
Yep. Was a bad wire. Not sure why others were not working at the time but eventually one started working and then they all started working again. I have no idea what was the problem.
Need some help XDA family.
Not sure if the Oreo update is responsible for my issue or not. But everytime I try and charge my phone in my car, and the ambient temperature and device temp are around 75 degrees, the device will shut down as soon as I plug it in, but it will charge the phone. The device is in no way hot. And if I try and turn it back on from this state, it will bootloop. Until I've hit it with some air conditioning. It never did this because I got the phone and updated it to Oreo in the winter time. And I always charged it in my car with an official Samsung fast car charger. It's like a security guard that gets triggered way too early.
Has anyone else had this problem?
Any ideas?
Kinda worried that it won't work when I need it. And I never had these problems with my Note5 or any other phone to be honest.
Thanks.
same issue with my verizon note 8
I'm having the same issue, not just with my car charger but also with multiple wall chargers. if I wait to charge it till it is less than 50%, it will charge for a few moments then shut down and keep charging. if I leave it alone till its at 70-80% it will normally boot up ok, if I try to reboot it right away I get into the same boot loop (clearing cache and safe mode do not consistently get it to boot correctly). This has been happening for a few months off and on but is getting much more consistent the last few weeks. I've even tried wireless charging rather than wired but that didn't seem to help. i'm thinking it is a battery issue. did you ever get a fix?
thanks,
James
Jjavitable22 said:
Need some help XDA family.
Not sure if the Oreo update is responsible for my issue or not. But everytime I try and charge my phone in my car, and the ambient temperature and device temp are around 75 degrees, the device will shut down as soon as I plug it in, but it will charge the phone. The device is in no way hot. And if I try and turn it back on from this state, it will bootloop. Until I've hit it with some air conditioning. It never did this because I got the phone and updated it to Oreo in the winter time. And I always charged it in my car with an official Samsung fast car charger. It's like a security guard that gets triggered way too early.
Has anyone else had this problem?
Any ideas?
Kinda worried that it won't work when I need it. And I never had these problems with my Note5 or any other phone to be honest.
Thanks.
Click to expand...
Click to collapse
Yesterday morning My Pixel 3 XL suddenly died while in a call. It would not restart.
My day had just started, Pixel 3 XL 128gb fully charged over night, was in a call for about 20 minutes while going down the highway. The phone was in the wireless charger. All of a sudden My Bluetooth switched back to radio I looked down The phone was dead, my call was dropped.
I had about 45 minutes more to travel so while going down the road I attempted to restart; holding power button, holding power and volume down. The phone was not hot, after a while I plugged directly into my rapid charger. The phone wouldn't show any indication of life. No vibration, charge indicator, nothing. Left it on the rapid charger the remainder of the trip.
I let it sit on/off the charger, switched to factory charger. Several hours later attempted to hook to computer, no drivers loaded, no fast boot, no ADB...
Contacted Google, and went through all the troubleshooting steps again. The Google CSR got a replacement on it's way, no hassles. It will arrive in about 2 days.
I'm persistent, and continued troubleshooting last night after is sat for about 4 hours. Finally, I put the phone in it's box, it sat there for about 24 hours.
Tonight I pulled it out and pushed the power button and it started right up normally! Battery was at 23%, so Something must have hung for the entire day. I looked at the phone log and the 20 minute call was missing, the call prior to that was logged.
I Pulled all my precious photos, docs, and pulled out a logcat. Nothing was logged from yesterday. Gonna wipe it, and send it back with a note.
Edit:
About to go to bed, put Pixel3xl in google charger stand, it went black and restarted, now it bootlooped a few times, starts with clock at 12:00, get's NTP and changes to correct time. Gonna try to get some logcats again.
My failure was triggered by attaching the charger; Google Stand and google usb c charger now causing reboot, and bootloops until removed from charger.
radionerd said:
Yesterday morning My Pixel 3 XL suddenly died while in a call. It would not restart.
My day had just started, Pixel 3 XL 128gb fully charged over night, was in a call for about 20 minutes while going down the highway. The phone was in the wireless charger. All of a sudden My Bluetooth switched back to radio I looked down The phone was dead, my call was dropped.
I had about 45 minutes more to travel so while going down the road I attempted to restart; holding power button, holding power and volume down. The phone was not hot, after a while I plugged directly into my rapid charger. The phone wouldn't show any indication of life. No vibration, charge indicator, nothing. Left it on the rapid charger the remainder of the trip.
I let it sit on/off the charger, switched to factory charger. Several hours later attempted to hook to computer, no drivers loaded, no fast boot, no ADB...
Contacted Google, and went through all the troubleshooting steps again. The Google CSR got a replacement on it's way, no hassles. It will arrive in about 2 days.
I'm persistent, and continued troubleshooting last night after is sat for about 4 hours. Finally, I put the phone in it's box, it sat there for about 24 hours.
Tonight I pulled it out and pushed the power button and it started right up normally! Battery was at 23%, so Something must have hung for the entire day. I looked at the phone log and the 20 minute call was missing, the call prior to that was logged.
I Pulled all my precious photos, docs, and pulled out a logcat. Nothing was logged from yesterday. Gonna wipe it, and send it back with a note.
Click to expand...
Click to collapse
I am confused. Sounds like you said you were driving and on a call while the phone was on the wireless charger?
sliding_billy said:
I am confused. Sounds like you said you were driving and on a call while the phone was on the wireless charger?
Click to expand...
Click to collapse
Yup,
It was in a wireless charger cradle.
It's a hardware problem, just reset to default and its bootlooping while plugged in. Runs for a few minutes with charger unplugged. I got all my stuffs out of it, and it's wiped, so it's going back to google.
radionerd said:
Yup,
It was in a wireless charger cradle.
It's a hardware problem, just reset to default and its bootlooping while plugged in. Runs for a few minutes with charger unplugged. I got all my stuffs out of it, and it's wiped, so it's going back to google.
Click to expand...
Click to collapse
Gotcha. I was having this image of a Pixel stand sitting on the passenger seat with power coming from an auto>AC adapter. LOL! Seriously though, it does seem coincidental that while numerous complaints are showing up about the Pixel 3 series having issues running apps while charging (especially wireless charging) this happens to you while using a 3rd party wireless charger. I know you said it wasn't hot and you are getting a replacement. I just fear that your issue might repeat itself under the same usage pattern.
radionerd said:
Yup, It was in a wireless charger cradle. It's a hardware problem, just reset to default and its bootlooping while plugged in. Runs for a few minutes with charger unplugged. I got all my stuffs out of it, and it's wiped, so it's going back to google.
Click to expand...
Click to collapse
What type/model wireless charging cradle?
I'm curious. You said your day was just starting and it was fully charged. Why on earth is it in a charging cradle if it's already fully charged? Just wondering because I have yet to run he battery down to zero unless I don't charge overnight and try and stretch out my screen times. I have been getting over 7 hours SOT along with music playback while I commute. That on top of phone and text.
FWIW I exchanged a Pixel 2 XL about 2 months ago because it was having odd/random reboots. I had purchased a P2XL from Google on launch, ended up replacing it through VZW insurance after the screen cracked (didn't have the Pixel protection). Had that one for about 3 months and I would often take it out of my pocket to a freshly rebooted phone, or it would reboot as I removed it from my pocket.
Was annoyed and started removing apps thinking that was the issue. One day I was in a meeting at work and mindlessly spinning my phone on the table while and it rebooted. Spun it again and it eventually rebooted again. There was a mild click/rattle when I shook it that I had attributed to the OIS but every time I shook it, especially when inverted (charging port facing up). I contacted the insurance company and they sent a replacement. A few weeks later my P3XL arrived and I sent the P2XL in as a trade. I can only assume something was loose inside the device. Could be the same with yours. Glad they got it replaced for you.
v12xke said:
What type/model wireless charging cradle?
Click to expand...
Click to collapse
It was in an iOttie Qi Cradle/wireless charger. I found out after purchasing several of these chargers that the Qi standard won't fast charge Pixel3's. They charge at a about .5 amps.
Bubba said:
I'm curious. You said your day was just starting and it was fully charged. Why on earth is it in a charging cradle if it's already fully charged? Just wondering because I have yet to run he battery down to zero unless I don't charge overnight and try and stretch out my screen times. I have been getting over 7 hours SOT along with music playback while I commute. That on top of phone and text.
Click to expand...
Click to collapse
I put it in the cradle when mobile.
Battery life has been the best of any device I've owned.
fury683 said:
FWIW I exchanged a Pixel 2 XL about 2 months ago because it was having odd/random reboots. I had purchased a P2XL from Google on launch, ended up replacing it through VZW insurance after the screen cracked (didn't have the Pixel protection). Had that one for about 3 months and I would often take it out of my pocket to a freshly rebooted phone, or it would reboot as I removed it from my pocket.
Was annoyed and started removing apps thinking that was the issue. One day I was in a meeting at work and mindlessly spinning my phone on the table while and it rebooted. Spun it again and it eventually rebooted again. There was a mild click/rattle when I shook it that I had attributed to the OIS but every time I shook it, especially when inverted (charging port facing up). I contacted the insurance company and they sent a replacement. A few weeks later my P3XL arrived and I sent the P2XL in as a trade. I can only assume something was loose inside the device. Could be the same with yours. Glad they got it replaced for you.
Click to expand...
Click to collapse
This device has rebooted several times over night. In fact That fateful morning when I turned off the alarm it had obviously rebooted since I had to enter the pin, and finger print.
This same thing happened to me today. I dont know if mine is going to start working again, but I did get a replacement ordered from Google. There is a common factor between yours and mine, I too was using an iOttie Qi Cradle. Looks like that might be a problem. Im wondering if I should continue to use it or not. Are you going to still use yours?
What Google number did you call for help? Yup, Mine died watching Youtube while using a Samsung wireless charger. I have the Pixel Stand just not one in every room.
MIne just died as well. Was sitting in a Samsung wireless charger also. Wtf people?
Mine also died today but I was using the Pixel Stand, replacement is on its way. I did manage to turn it back on after about an hour and a half of holding the power button down. The phone allows me to use it for about 30 seconds before it boot loops and if I plug a charger back into it or place it on the Pixel Stand it will go back in to the dead state.
This can't be good! Too many reports here with same issue. Does Google know what's going on?
I had exactly same issue. I've been using an iOytie wireless charger. Mine just shut down. So I powered up and in 30 secs, it would shut down again. Eventually it wouldn't even power up, so I RMA'd it.
New one seems ok...so far!!
On my fourth pixel 3 XL now!
Is there any support for multi-window mode?
Kite'la said:
Is there any support for multi-window mode?
Click to expand...
Click to collapse
Not if it dies suddenly.
I had my phone crash once too while in my car wireless charger. It has not happened again in over 2 weeks.
FYI - this isn't just a cradle issue. I actually had this problem on my FIRST 3 XL, and managed to get Verizon to exchange it in store a few weeks ago (got it on Black Friday for a great price, though the forced monthly payments to retain the deal are obnoxious). Full charge, and just stopped working. Actually got it going after a half hour, but only as far as the hard reset key function - and it froze halfway through the reset. That's when I went to Verizon and had some words.
So, here we are, new one... THIS hasn't happened yet, but I've now had three instances where it wouldn't charge. I bought the cradle, and avoided that intermittent issue - but now it often thinks it's connected to USB when I de-cradle it, and I've had several repeats of the "won't charge" event. This occurs on both OEM and non-OEM chargers, and I found that rebooting the phone fixes the problem. That to me screams OS or drivers.
Anyone heard any news on their problem? (FWIW - I left an OG Pixel XL for this... and have had more problems with this in the first three months than I did with the OG in two years, running beta releases.)
J