This started earlier in the week. I think I loaded the Free Monopoly, Contract killer and Text Plus in the morning when it started. I'm thinking this was Tuesday or Wednesday morning after Christmas.
At the Time I immediately killed and uninstalled all three of the recent app additions. This did not appear to resolve the issue.
Symptoms
Screen would not remain off for more than a few minutes without turning itself back on again. Full screen wakes.
Occasionally and without warning the phone would completely turn itself off, requiring the very long power button press to turn on again (was a full power-down).
Since this has started I decided to upgrade to the latest unamed rom.
This does not appear to have helped anything, although the frequency may have been reduced. I don't think this is related to the ROM since the issue survived the factory reset / wipe / rom change.
Questions
Are there any internal logs that may help to point me in the right direction?
If so, where / how can I view them?
I'm seeing a RILJ dialer something under Partial wakelocks in BBS.
I see this as [p]_RILJ under Kernal wakelocks as well. Any Idea what this is?
I admit, I was getting a bit silly with the quantity of Apps I had loaded and still running well at the time. Amazed the phone was still going very strong with no issues at all. I'm trimming this back on the new rom.
Any help would be greatly appreciated.
Random Illumination Wakes and sleep crashes.
Still trying to nail this down.
Additional observations.
Timing appears to be random.
When I say the screen wakes up, I'm mean illuminating.
The wakes appear almost as often as the power off freeze. What I mean is the quantity of complete power off's is similar to the screen wakes.
It's very possible that the same event may be causing both the screen wake and the hard starts. Neither issue occured prior to this the starting of both events.
I have occasionally seen the "Driving Mode" steering wheel icon pop-up, while unplugged. I've not connected this phone to any kind driving interface as of yet, so this is a surpriseds.
Today I had additional issues with extremely heavy battery drain in a short period of time. I had incorrectly added 2650mA under battery capacity beneath Calibration tab of "Battery Monitor Widget Pro".
Still looking for help finding and viewing any error logs on the device.
Does anyone know of some basic error log files on the device?
Again, all help is greatly appreciated.
Under Recent unamed ROM but I do not believe the ROM is the issue.
iqak said:
Still trying to nail this down.
Additional observations.
Timing appears to be random.
When I say the screen wakes up, I'm mean illuminating.
The wakes appear almost as often as the power off freeze. What I mean is the quantity of complete power off's is similar to the screen wakes.
It's very possible that the same event may be causing both the screen wake and the hard starts. Neither issue occured prior to this the starting of both events.
I have occasionally seen the "Driving Mode" steering wheel icon pop-up, while unplugged. I've not connected this phone to any kind driving interface as of yet, so this is a surpriseds.
Today I had additional issues with extremely heavy battery drain in a short period of time. I had incorrectly added 2650mA under battery capacity beneath Calibration tab of "Battery Monitor Widget Pro".
Still looking for help finding and viewing any error logs on the device.
Does anyone know of some basic error log files on the device?
Again, all help is greatly appreciated.
Under Recent unamed ROM but I do not believe the ROM is the issue.
Click to expand...
Click to collapse
These random screen wakes, particularly with the car mode activations, are what I was seeing when my usb port on the device failed. there are several threads in the general and QA forums regarding usb failures, you might want to dig around in there to see if other behavior is similar. I think one poster mentioned cleaning out the USB port with alcohol and a small paint brush. I had tried doing the same with canned air, but that did not help me. I ended up with a warranty replacement device.
Sent from my SGH-I777 using XDA App
I think you may be onto something.
Since the event I am also having issues connecting up to my Win7 Pc.
On the morning of the event, I remember a brief weirdness to the charging indication. I think it said it was charging when it wasn't or vice versa.
So now the question becomes.
What do I need to do before an exchange?
Purchased from Best Buy on US Launch day without extended warranty.
Do I still have a warranty?
Can I go to the AT&T store in Sacramento?
I think you may be onto something.
Since the event I am also having issues connecting up to my Win7 Pc.
On the morning of the event, I remember a brief weirdness to the charging indication. I think it said it was charging when it wasn't or vice versa.
So now the question becomes.
What do I need to do before an exchange?
Purchased from Best Buy on US Launch day without extended warranty.
Do I still have a warranty?
Can I go to the AT&T store in Sacramento?
Your phone has a 1 year hardware warranty. Talk to Best Buy, and force them to give you a replacement. I did that with AT&T, not putting it on the phone insurance, but the phone's warranty that came with it, for free.
Backup your apps using a tool like ROM Toolbox from the market (it's my favorite). When you restore your phone, all apps that AREN'T sideloaded will come back with the last Google Sync you made, so sync now. If you're sure, 100% that it's hardware and not software, make a backup via CWM and ignore all previous instructions, but if you're like me, you'll want a fresh restart with the ability to axe all the apps you don't use on a clean ROM.
When backing up all non-sideloaded apps, Google does it for you, use a backup program from the market to ONLY backup your sideloaded apps.
HUGE ADDENDUM:
READ THIS. Alright, before taking it back to Best Buy, flash Entropy's "Back To Stock" ROM and kernel. If you don't, you're done. Warranty voided. If they are intelligent and check the flashcounter, and see you tripped it, but you're on a stock ROM, you can talk your way outta it. Try thinking of something before you go in. The excuse I will use if ever needed is I was clueless about why my phone was ****ing up, so my friend who said he could fix it took my phone for a day and temporarily fixed it, and it worked alright for a couple days before the issue came back. So you can claim ignorance IF NEEDED, but most of the time they don't check. Just be sure to have an answer for if they do.
Sent from my SAMSUNG-SGH-I777 using xda premium
I do have a jig and I do not have the Exclamation Icon.
However my boot animation is no longer stock and I have not been able to read the flash counter. The Power-off, Hold volumes and plug USB thing is not working for me.
To date, I have not caught anything in software to cause this.
Getting myself ready, Thanks a million.
iqak said:
I do have a jig and I do not have the Exclamation Icon.
However my boot animation is no longer stock and I have not been able to read the flash counter. The Power-off, Hold volumes and plug USB thing is not working for me.
To date, I have not caught anything in software to cause this.
Getting myself ready, Thanks a million.
Click to expand...
Click to collapse
As long as you used a root method that should not have increased the counter, I think you can mobile Odin back to stock unrooted to prep for warranty return.
Sent from my SGH-I777 using XDA App
Shot back to this ROM
Kernel + cache + rooted UCKK6 system package: http://www.multiupload.com/NYL3XT51Y0
Feels like olden times.....Naked in front of the Gym class.
Beyond Best Buys 30 Days so had to go to the AT&T Service center.
They grilled me, checked, wiped, reflashed, yada-yada-yada.
Gave me the could be an app shpeel, did you use a car charger questions etc.
Long story short....
They want to try a new battery 1st.
So, news years eve overnight, maybe by Monday.
I admit this could be a possibility because I have had the battery lose a large amount of capacity in a short amount of time one the order of Full to Dead in 2-3 hours. This has occurred to me on maybe three or four occasions since launch day. Phone got warm to hot at the same time. This usually included a hard kill power off. Nice big gap / drop in battery stats.
Is there any way the phone would get a charging indication yet not charge?
Like if the USB port got wonked or crossed with something?
Additional Weirdness:
I have had the phone freeze up on me, picture turn weird as it gradually whitened to full white screen only.
No response from the keys or screen with the exception of a long power button press to recover. This occurred a few times since the original event (maybe 3) with the last one happening while plugging it back in for some juice for the return today.
Keeping this up to date in case others run across the same funkyness.
iqak said:
Shot back to this ROM
Kernel + cache + rooted UCKK6 system package: http://www.multiupload.com/NYL3XT51Y0
Feels like olden times.....Naked in front of the Gym class.
Beyond Best Buys 30 Days so had to go to the AT&T Service center.
They grilled me, checked, wiped, reflashed, yada-yada-yada.
Gave me the could be an app shpeel, did you use a car charger questions etc.
Long story short....
They want to try a new battery 1st.
So, news years eve overnight, maybe by Monday.
I admit this could be a possibility because I have had the battery lose a large amount of capacity in a short amount of time one the order of Full to Dead in 2-3 hours. This has occurred to me on maybe three or four occasions since launch day. Phone got warm to hot at the same time. This usually included a hard kill power off. Nice big gap / drop in battery stats.
Is there any way the phone would get a charging indication yet not charge?
Like if the USB port got wonked or crossed with something?
Additional Weirdness:
I have had the phone freeze up on me, picture turn weird as it gradually whitened to full white screen only.
No response from the keys or screen with the exception of a long power button press to recover. This occurred a few times since the original event (maybe 3) with the last one happening while plugging it back in for some juice for the return today.
Keeping this up to date in case others run across the same funkyness.
Click to expand...
Click to collapse
I got the "try a different battery" story too. Conveniently my wife also has the I777 as well, so tried hers. No joy for me. After that, rma was approved. Good luck!
Sent from my SGH-I777 using XDA App
It ain't the battery man. The symptoms you described fit perfectly with a fried micro usb port.
If you haven't set the flashcounter off, and your phone has the AT&T boot logo, then you're good to go as far as exchanging it goes. DO IT UNDER WARRANTY AND NOT INSURANCE. This is the **** quality of the usb connecter, not user caused.
Sent from my SAMSUNG-SGH-I777 using xda premium
I doubt it too, since the original event involved the AM unplugging from the charger. I always check the Next Amazon app, 1st thing.
I can honestly say that:
The phone has absolutely never been dropped.
The USB cable nor port has never been stressed, tweaked nor twisted.
Never used the phone with the cable attached.
Neither the phone nor the Taurus gunmetal case have a single scratch.
The phone has never been close to water, save for the obligatory post shower, AM, moist towel screen wipe (ok.... too much info).
I think I had 137 apps on this thing until the 1st event last week. In those original two months I've had maybe 5 force closes or other events. The force is definitely strong in this one!
I hope they forget the "new" battery when the time comes for the full swap?
As always, thanks for everyones help. I'll post this through beyond conclusion for the rest of us.
Definitely the USB port is screwed. I'm on my third phone cuz of this issue. First guy at best buy said it was probably because I wasn't using stock launcher. Whatever. Second replacement was easier, just a young girl who never even looked at my phone, and just gave me a new one. I did go to a different best buy second time to avoid possibly getting another phone from a bad batch. I've posted on other threads on this issue about the fact that this problem might be caused by the lack of a cover over the USB port. Maybe i'm wrong, but it seems to easy for junk to get in there. If you can't flash back to stock via computer, you can try mobile Odin, however I ended up soft bricking my phone trying to run the stock Odin one click via drop box through mobile Odin. Don't know if file didn't completely DL through drop box, but I couldn't fix soft brick since I couldn't connect phone to comp using the USB port. Long story short, my advice, flash stock while you still can, and keep it that way cuz the problem most likely won't go away.
Sent from my SAMSUNG-SGH-I777 using XDA App
Additional info:
I performed a factory data reset (from the settings screen) prior to re-loading the unbrick/return to stock ROM. Also wiped all three memory areas prior to the rom.
Last night the Driving mode Icon and V-Lingo kept popping back up as if I were connected to a car adapter. I have no use for either as I have no car adapter yet (was at home). No cable was attached at the time and the phone was sleeping. This occurred a half dozen times or so.
I also randomly receive the USB connected icon despite having nothing connected to the phone. Says MTP-Initialization.
Odin 3 worked yesterday without any issue. Droid explorer also appears to work but Kies has refused to connect since the event, even with the New years update. The Win7 pc randomly recognizes the phone. Sometimes it's ok, but mostly it does not show up at all with the pc saying "USB device not recognized...".
With USB Debugging turned on, Kies says:
"Reconnect the device in Samsung Kies (PC Studio) mode.Current mode not supported by Kies."
I switched USB debugging off 1st thing this morning and it looks like Kies USB is working ok now.
Kies Air works like a champ.
Still think the USB Port is dorked. Probably the USB controller chip as I don't think I have any physical looseness. I really wish USB connectors were longer and deeper with screwed attachments to the motherboard in addition to the soldering.
Correct me if I am wrong here, but I thought that the "Driving / V-Lingo Mode" is Hardware triggered and it is not possible to trigger this mode with any software. At least that is the impression I got by reading the car cable connection cable discussions.
More fuel for the bad USB port fire?
Since the multiple wipes and return to stock, I do not think I've had an event from sleeping to hard crash / reboot required.
Still having wake-ups and spurious driving mode activation's both plugged in and unplugged. This may or may not be accompanied by the V-Lingo, terms prompt.
Prior to going back when the replacement battery fails to improve things....
Can I kill / Delete everything on the phones internal SD memory?
Not thinking,.. I still had the Titanium Backup directory along with Clockwork Mod etc. still on the phone when I brought the phone to the service center. Had they checked the phone directory, I could have lost warranty, etc.
Any other directories I should look for?
Just Realized I had not stated my Hardware Level.
Model: SAMSUNG-SGH-I777
Android Version: 2.3.6
Baseband Version: I777UCKK6
Kernel: 2.6.35.7
Build No. GINGERBREAD.UCKK6
Still getting spurious wakes with the USB port thinking:
It's connected to a PC.
It's connected to the car
or V-Lingo launches thinking I'm about to take a trip.
All of these occur with nothing connected at all, and typically the phone is sleeping. Still have not had a repeat Hard crash since the wipes and return to stock.
Do we have enough of a known hardware history here to know / avoid certain builds?
No. Not much effort has been put into figuring the faulty USB port out. Entropy and I even hashed it out in Q&A, both of us thinking it might have been the software. Truth is, you'll probably find more info in the international SGS II community than here, as more were sold, and our SGH I777 was discontinued only a month or two after being brought to the market.
Because it hasn't been reported on much, no one has thought to start observing the hardware for faults. You should consider doing so - I can tell you some information on my phone model later, after I remove the battery and such. Maybe shoot GTX or Entropy a PM to ask them for tips on identifying different hardware models and state why you're interested. As I said, I'll post my info on my new replacement, and observe it to see if the same problem occurs as it did in the last one.
Sent from my SAMSUNG-SGH-I777 using xda premium
Here's a link to the thread I started when mine went tango uniform:
http://forum.xda-developers.com/showthread.php?t=1369647
I mentioned at one point about looking at device serial numbers to attempt to track bad hardware, but I'm not sure if that info is safe to post online when not coupled with device imei. I would think it is safe, but not sure.
Unfortunately I don't know if I can track down the info on my defective phone now, since it has been gone for several weeks.
Also: I was under the impression that the i777 had in fact NOT been discontinued, only not stocked in COR stores in LTE markets. I'd be interested in documentation on the discontinuation if you can provide it...
Sent from my SGH-I777 using XDA App
Wow, your thread has quite a few similarities.
With the exception of the ROM selections, the device responses appear to mimic my own dead on. I was on "update-unnamed-v1.0.4-full" when the issue reared its head. Jumped to v2.0.1 to see if it helped, but again, I seriously doubt this issue is ROM related.
I'm still waiting for the "overnight-ed" battery.
I expect it will arrive tomorrow. With any luck I can grab it from home at lunch and charge it at the office. Put an effort into trying it at least.
That pushes my eventual return out till Wednesday evening / Thursday morning. I'll be sure to get the serial number data from it before it goes back.
Would it be insecure of me to post the old serial number data after the exchange?
I'm wondering if charging device, cable or PC could have had something to do with the failure. Pretty sure the cable was stock, but the plug may have been a logitech. This arrangement had been used nightly since launch date, so I doubt it.
Electronic chips can do some funny things. I'm fairly certain the port itself is still firmly attached.
As always, thanks for everybody's help.
Ok so this morning I had a little bit of a frustrating time getting out the door and I'm wondering if anyone has good info to help me and others. Specifically, I'd like to hear from those that actually understand what is going on under the hood so that I can have a morning routine with my phone that gets me out the door with minimal frustration...
First off, I know that the easiest solution is to revert back to an ICS rom. I know that until source drops the JB roms are experimental and that issues are to be expected. We are so lucky to have the devs that support our phone. They have brought us this far and we should show appreciation through the "thanks" button and, as means allow, through donations. Don't get me started on the ridiculous lament of some that can't afford it - Guys if you can afford a phone plan (or a cup of coffee), kick the dev a fiver (not much, but if everyone did it would add up)- side rant off
Back on topic - my two issues are my paranoia over the deep sleep issue when pulling phone off charge and losing in call volume. For me the two issues are related. Like many, I need my phone to maximize it's battery potential. I can't afford to pick up my phone in the afternoon to place a call only to find that it has been draining battery because it was not properly sleeping because of how it was pulled off the charger. I have no rogue apps running and I am not entirely convinced that unlocking it before removal from the charger fixes the deep sleep issue. I am further convinced that nobody, not Samsung nor our amazing devs can fix this issue. It must be a hardware problem as Samsung had to be aware of it before the ICS update and were not able to fix it. My solution currently is to reboot my phone every morning after I take it off the cradle.
This leads to my second issue. After I reboot my phone, I immediately dial my home phone number to verify that I have in call volume. In most instance I know immediately if I hear the phone ringing through my note's ear speaker even before my home phone starts ringing. If I hear this, I am good to go - as long as my phone does not randomly crash throughout the day I am sure that if someone calls me, I will be able to hear them or if I need to place a call the phone will act as a phone.
Through the work of our devs, we have some very stable roms and random crashes are minimal. I am going into my third day on Manelscout4life's eclipse rom and have yet to experience a random reboot! My problem this morning was that I lost in call volume after my voluntary reboot and had a hell of a time trying to get it back. For those, who understand what exactly is happening, I would ask - how is the quickest way to get up and running so that I can get out the door?
-I know that the issue has been linked to rebooting while connected via wifi so I toggle it off before rebooting
-I know that sometimes a simple reboot fixes it so I try that -however today three simple reboots served only to waste valuable morning time and drain 3% of precious battery life.
-clear app data and force stopping phone and related apps before rebooting sometime works - no dice this morning
-clearing caches and fixing permissions in recovery sometimes works- this was the kicker today, but only on second try...
I know that the in call volume issue will more than likely be fixed once JB source is dropped by Samsung. It is a known issue that affects all JB roms currently out and I know the devs are working hard to fix it without Samsung's help. But I think if someone can give me a sure fire morning routine (preferably under 5 minutes). I would be good to go with the present state of JB stability....
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Do you remember when were the times when the screen was unresponsive?
I've read somewhere that sometimes when the screen is woken up and is under some pressure this will happen, and the only way is to do what you did. It's not uncommon in touchscreen phones though, so I wouldn't worry about it.
The verge app was broken until the most recent app update. Also, the s5 seems to refuse allowing Dashlane's accessibility service from working properly. So no more auto filling passwords for me. Ugh. I hoped rooting might help but it didn't. Now I really can't wait for custom ROMs to start appearing. Samsung, you make great hardware (like amoled displays) but your software sucks. Even the software on my Samsung TV is stupid.
Yes on two out of three!
finotti said:
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Click to expand...
Click to collapse
The unresponsive screen is more than a little issue, it is being reported all over the web, and get's more severe over time. I'm thinking that it is a bad proximity sensor defect, either firmware, hardware or software. Some people are reporting along with myself that sometimes for no apparent reason, the screen will not turn on even though the phone is completely operational! This has happened to me four times now and I am stock with very few apps on my phone, five total games and Pandora. I do use a substitute launcher that I've used for years but I don't believe that would be the issue since others report the same issue with stock launcher.
The pop or skipping you speak of in sound happens to many of us who stream music in our automobiles. It even happens on the note3. The fix is simple for that one though! Turn the screen on. I was told that with many of the streaming software music programs that the phones CPU goes to sleep and does not offer enough processing power to the music program. I stream all day via bluetooth to my Auto's sound system and it will usually start to skip, click or whatever after the phone has been untouched for about twenty minutes. The second I turn the screen on the problem alleviates itself. You can find even more information by googling that one, in fact both of those! The heat one I have not had, both with stock battery and zero lemon high capacity battery. The phone very rarely get's warm. However, when I was using wireless charging it would get warm even after charging was complete but I believe that is a normal event with QI type tech.
Well, I tried searching for this answer, but couldn't find it, so I apologize if it's somewhere out there. I'm VERY new to all this smart phone technology, so please bear with me. I bought this phone because it looked very similar to a tablet I currently use and figured it couldn't be THAT hard to figure out. I have figured out about 90% of it, but there are some issues that I just can't find an answer to; i.e. how to answer the phone using the swipe option. Sometimes it will work very simply an other times I can swipe til I turn blue in the face and nothing happens. VERY frustrating and I end up missing the call. Is there an alternate way to answer? Next question is what apps can I safely stopped that came factory installed? My battery is draining BIG time, as in, the phone can sit on the counter and be 100% charged and I can pick it up 2 hours later and it's at 80%. I stopped the daydream application and turned off the location option, as well, but I simply don't know what else I can turn off. I have installed a 16 mb external SD card so that I can have my photos sent to it instead of internal storage in the hopes that that conserves battery power, and have only two or three applications installed on the phone, as I mainly want it as a PHONE not as a game playing tablet, which I already have. When I click on "battery" it states that it's collecting data on usage and to please wait. After 10 minutes of waiting and nothing happening, I gave up on that option. And not to throw a dozen questions at you, but the phone also seems to be slower in changing screens. I also had it plugged into my car charger on the way to work and a call came through, but the phone didn't light up so I missed the call b/c nothing I did would make the answer screen appear! I have closed all running applications after using them to conserve battery power (by holding the button between the back button and the menu option button) and I'm at a loss for what else to do or what may be the problem. I don't know what rooting the phone is, or if that will even help. I don't know what mobile data storage is, but mine is turned on. The phone is only a couple of weeks old, so I find it hard to believe the battery itself could be the problem. ANY help would be GREATLY appreciated! Sorry if I sound like a moron, but up to this point, I was using a Samsung slide with no games/internet/etc., so this is kind of like culture shock to me!
I need a cell phone and I thoroughly enjoy taking photos with my phone. The Sony Xperia 5 II, and other Experia with Photo Pro, are unique in the world of camera phones. Yesterday, around 2 o'clock, my Xperia 5 II bricked. It wouldn't turn on. Connected to a charger the red LED light didn't come on and the phone didn't charge. I panicked at the thought of no cell phone and started thinking of alternatives. They're all pretty much the same for me until we get to the camera.
I don't do social media, I've never zoomed, I don't play games but Calendar, Keep, Maps, Photos, GMail, and messages are used by me every single day. My phone tells me when your birthday is, when my phone bill is due to be paid, and when it's time to take my pills. First thing in the morning I read the headlines on my phone. Depressing.
All cell phones do all these thing pretty much the same.
But, the cameras are different. I am hooked on the shutter button on my Xperia 5 II and the volume button used to do digital zoom. I love Photo Pro which moves the operation to something other than excellent point-and-shoot. I've had Pixels and Xiaomi and Huawei but I'm hooked on Sony Xperia with Photo Pro.
I don't know why my Sony Xperia 5 II bricked and I don't know why it came back to life. I've been checking frequently to see if an app or an update is draining the battery and that's negative. So, life goes on. I'm hoping the Xperia 5 III comes out soon enough that my sister can bring me one.
What OS version?
Any other odd behavior?
Version 92.0.4515.157 (Official Build) (64-bit)
No other oddities. I've been checking frequently to see if something is draining the battery and so far it's not.
Wait, wrong version.
Android 11
Build Number 58.1.A.5.280
Any chance it could have got infected by a rootkit?
If so factory reset.
Otherwise probably hardware.
The reset will sort it out more than likely if not hardware.
Regardless backup all critical data redundantly to at least 2 hdds now... while you still can.
Okay, my guess now that the panic has passed. My normal routine is to charge my phone to 80% before bed and then to power down. In the morning, I turn on the phone. Perhaps once a month I forget my routine. If I forgot and the phone had power it could have downloaded an update that somehow drained the battery. That would have made the battery drain to zero around mid-morning.
I downloaded and read the manual for the 5 II and it said that if the battery drains to zero, plugging it in will not do anything for around ten minutes. That would explain the LED not lighting up when I plugged in the phone. Then, when it sat idle for the next night the battery percolated a bit and got enough power to show the "Battery Zero" icon when I picked it up and pressed the power button. But, as the manual said, the LED didn't come on for a while.
Whatever it was, everyone is working fine now. I wish all hysterical panics could be solved so easily.
Yay!
Consider disabling auto updates before it does toast your phone...
I will when I read the manual again and find out where that is. I did a search in "settings" for "auto" and got nothing that gives an option of auto-update or manual.
patrickt said:
I will when I read the manual again and find out where that is. I did a search in "settings" for "auto" and got nothing that gives an option of auto-update or manual.
Click to expand...
Click to collapse
I use Package Disabler. Carrier phones don't give you that options. It can be killed with a adb edit but it's a pain to reenable then if you want it.
Package Disabler lets you easily disable apks on the fly. Useful for troubleshooting too. It will also completely clear apk data leaving no null marks unlike doing it in settings.
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com