Database Users

Note 4 freezes while charging after lollipop

I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.

ks-man said:
I tried posting this in the Sprint thread but haven't gotten any answers yet so perhaps I'll have better luck here. I pasted both posts to show the initial problem and what I did (essentially I factory reset). I'm still having the same problem where my phone will freeze while I'm charging it (about 2-3 times/week) requiring a battery pull. Anybody else seeing this problem or have suggestions on what I should try? Thanks.
-----------------------------------------------------------------
Twice this week my alarm didn't go off (luckily I set a backup today) because sometime throughout the night something happened. When I woke up the phone was frozen on the yellow Sprint Spark startup screen. I needed to pull the battery and everything started up fine. I updated to Lollipop about 2 weeks ago which is where I'm guessing the issues stem from.
Is there anything I should try other than restoring to factory and starting over? I'd prefer to not have to wipe everything from my phone but these issues are becoming problematic. I am not rooted.
Thanks.
--------------------------------------------------------------------
So I ended up doing a factory reset and while the phone certainly started running faster with better battery performance after the reset I'm still having this issue. I would say it occurs 2-3 times a week. It has only occurred overnight which is typically when I charge my phone so I'm pretty sure it is related to being left connected to the charger. The majority of the times I will wake up with a dim yellow Sprint screen and everything else frozen though occasionally the screen will be black with the led notification light red. In both situations the screen will not respond to any button pushes or holds and I need to pull the battery and then everything will start up fine.
Does anybody have any suggestions here on what I should do? I guess I can try and restore one more time and see but I don't really know why it would be different and it is certainly a pain to keep restoring the phone and losing all my settings. I definitely don't want to root now since I believe that voids the warranty and if I can't figure anything out with this I'll certainly be requesting a new phone from Sprint. Before I start dealing with Sprint though I thought I would check here first. Through all my searches on the internet I haven't seen anyone else complaining about this problem.
Thanks.
Click to expand...
Click to collapse
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late

jbkmin said:
Hi there. I have a Canadian Note 4 (W8) with Bell, and I am having identical issues.
While charging over night, I find my phone stuck on "Samsung" logo, with the bubble animal still running. Holding down the power button does nothing and the only work around is the battery pull. I noticed that it also gets warm (assuming from the screen on time?)
First tried cache wipe - no fix
Factory reset - no fix
Cache wipe again - no fix
Aaaand today I came into work late
Click to expand...
Click to collapse
Did your issues first start after you upgraded to lollipop?

ks-man said:
Did your issues first start after you upgraded to lollipop?
Click to expand...
Click to collapse
Definitely after the upgrade.
While on KitKat, it never happened (1 month ownership). But after upgrading to lollipop, it has happened 4 times (6 nights since lollipop).

Have you figured anything out with your situation? Woke up this morning to my backup alarm and the Yellow Sprint screen on my phone.
I guess I'll have to try another factory reset and if it still happens try and get a replacement. It just doesn't seem widespread enough of an issue to be a software bug with 5.0.1.

Very frustrated. I did another factory reset but the issue still plagues my device. It still only occurs once or twice a week but when I hear my old clock radio alarm in the morning I know when I look over I'll see the yellow frozen Sprint Spark screen. I am completely out of ideas and guess I will need to have it replaced under warranty. I'm hoping Sprint won't give me a hard time as this will be very hard to demonstrate.
It definitely appears to be a software issue as it never happened before I upgraded to Lollipop but there must be more to it or others would be complaining.
If anybody has ideas please let me know. Thanks.

Response to Note 4 Freeezing while charging
I have found that after turning the quick charge feature off the problem is not happening. Hopefully this is fixed in 5.1

I'm having the same issue even after turning quick charge off..def a lollipop bug, never experienced this on kk.

I know its not the BEST option, but after taking the update to lollipop, sometimes left over kitkat files can make the system poop out. Sometimes a factory reset will take care of the leftovers. But of course, then you have to set your phone up again
If you've tried this or plan to to, let us know the results.
(When i first took the update, my heartrate monitor sensor was always on, so i did a factory reset and it fixed my problem).

Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.

same problem here
Ive tried turning off fast charging option on the powersaving mode
And also tried the option on developer mode, the "keep device awake while charging"
And even flashing dofferent firmwares from sammobile through ODIN and installed custom roms. These options doesnt resolve the issues on freezing while charging..
I think turnong off your device while charging is the only option..
Im using note4 N910C..

Clasimodo said:
Solved with workaround!!!
I faced this "sleep of death" too after updating to Lollipop. I had to pull out the battery almost every time after charging. Very annoying! I noticed though that my phone never froze in my car while charging. Thinking about the difference I realised that I keep my phone awake in the car while charging using Macrodroid (which I love anyway to automise all kinds of things). I made a simple macro which keeps my phone awake while charging and another one that returns the phone to normal while on battery.
While charging: Trigger: Power Connected; Actions: Keep Device Awake enabled & Screen Off, Constraints: None
On Battery: Trigger: Power Disconnected; Actions: Keep Device Awake disabled & Screen Off, Constraints: None
Off course there are alternatives available to Macrodroid that should be able to do the same.
My problems are solved, with and without fast charging. I hope this will help some of you as well.
Click to expand...
Click to collapse
Thanks a lot, Mate. I'm trying your workaround now. Will report later if it works on my phone. BTW, so, are you sure it is a just a system issue? Definitely, isn't a hardware problem? Did you fix it, after your post -a month ago-, installing, for example, lollipop 5.1.1 or Cyanogenmod 12.1? I'm on 5.0.1, SimpleRom V4. Of course, mi device, N910C, is rooted.
Thanks again.

With lollipop 5.1.1 the problem is solved for me, even without this workaround.
Sent from my SM-N910F using XDA Forums PRO

I'm having similar issues as you guys. I found out that my phone will only perform normally when I charge it with my laptop USB port which I think is around 0.5amps. Anything above that, even a 1amp charger would cause the phone to freeze, reboot and turn off and not turn back on. The phone has been in repair 4 times and the problem is still there. Now every night I'm forced to charge my phone with my laptop which takes an age instead of the fast charger that came out of the box.
Currently my phone is still freezing and rebooting when I'm out and about and the only way I can get it to perform normally is when I plug it into my laptop. This normal functioning would only last whilst the phone is plugged in.

Random shut down

Today I picked up my phone up to send a text and it was no longer powered up. It had randomly shut down.
When I switched it on again I noticed it has lost its battery stats so looks like they were reset or lost. There were no user apps installed on the phone either.
Have you had a similar experience?

You could try to reset it or take it back. Could be defective!!!

Was it somewhere it was hot? Maybe the phone got too warm and hit the shutdown temp?
Honestly hard (read impossible) to tell you what happened. Have any more info / logs?
I haven't had any issues with heat or shutdowns at all. I get 6+ hours SoT every single day at 75% brightness. 100% stock and unrooted. I use my N5 for all the modding aspects like V4A, Xposed, etc. I want this one for Android pay.
Anyways my uptime has been running since I unboxed it on 11/9/15. No issues.

I actually had it reboot in my pocket yesterday on the first day i had it but I already installed a custom ROM so no testing it out now.

RoyJ said:
Was it somewhere it was hot? Maybe the phone got too warm and hit the shutdown temp?
Honestly hard (read impossible) to tell you what happened. Have any more info / logs?
I haven't had any issues with heat or shutdowns at all. I get 6+ hours SoT every single day at 75% brightness. 100% stock and unrooted. I use my N5 for all the modding aspects like V4A, Xposed, etc. I want this one for Android pay.
Anyways my uptime has been running since I unboxed it on 11/9/15. No issues.
Click to expand...
Click to collapse
It was only room temperature. Here in England at 18cc so not too hot, but good point.
I read about the same thing happening with a N5 and it turned out to be a defective mother board.
Guess I should return today then... Bummer

If you just got it, might want to see if it happens again. I had one random reboot the first day and its been fine since.

My phone has started doing the same thing. Twice in 3 hours.

Same here...... 3 times reboot..... And now 2 times shutdowns.

I started having random reboots after I installed greenify. I tried several settings but had the same problem. It rebooted 5 or 6 times a day. I uninstalled it and haven't had any more problems.

I had my phone shut off yesterday and wouldn't boot until I plugged it in (it was at 80% battery). I then noticed that once it booted, it had deleted all of my paired Bluetooth devices.
Sent from my Nexus 6P using Tapatalk

murphyjasonc said:
I started having random reboots after I installed greenify. I tried several settings but had the same problem. It rebooted 5 or 6 times a day. I uninstalled it and haven't had any more problems.
Click to expand...
Click to collapse
Was just having the same problem but it was happening every 30 seconds to a few minutes. Deactivated greenify's device admin ability and now it's gone. Hopefully it stays that way, though if it comes to uninstalling it, that's fine since there don't seem to be as many background apps running on the 6P compared to my verizon LG G4.
Nevermind had to uninstall it.

Shut down, and a little warm
My nexus 6p shut down nearly every day, I just picked it up and it was shut down, I looked under battery and I could see it has been shut down for hours.. hope somebody knows anything about this problem.. I don't think a hard reset will help, because when I got the phone I installed all the update to Android 6.01 (MMB29M) and then I did a hard reset to make sure the phone was as good as it could be..
But maybe I'll try one more hard reset, just to be 110% sure
..
Lars
Danmark.

I'm having this problem too. It happens a couple times a day, and I think it always happens right after I pull it out of my pocket and try to unlock it. I'll feel the vibration from the Nexus Imprint fingerprint sensor, but then the screen doesn't turn on. So I try the power button, and nothing happens because the device is suddenly off. So then I hold down the power button to turn it on, and it boots normally.
Someone mentioned this happening with stock software, which makes me think it's a hardware problem, so we'll need replacement devices. However, I do have Xposed and GravityBox installed, so I need to rule those out first by removing them for a while.

I've had the phone for two weeks now and so far this happened twice.
The only two things that come to mind:
- enabling SRGB in the dev settings
- using a bluetooth headset
Has anybody pinpointed whether this is a HW or SW issue!?
How common is this ... I've seen ppl complaining in this thread and in Reddit also on random reboots as well
Thx

Still happening...
I am having the same issue. Did the reset to factory with no help. Phone was not hot, was sitting on my desk with 81% charged battery. This is the 3rd or 4th time in a week it just shuts itself off for no reason. Has anyone found anything??

I'm having this problem too, now on DVP 3 it's even worse. But I notice today that alarm clock works, but the screen won't. So I think is a SW related, the screen won't wake up, and after a while if you press the buttons the phone reboots. Anyone have e ideas how to fix this?
Enviado de meu Nexus 6P usando Tapatalk

facing this problem since may security update, on purenexus , dirty unicorn and rr rom. dont know if it hw or sw or simply power button getting pressed accidently.

I think I need to reopen this post, coz' I've been facing thif problems for so many times this week so I google around and come to this post.
Has anyone come to a workaround or point out if it is software or hardware related yet...? If it's hardware then I think I'm gonna go for a replacement then!!!

If you haven't done so already, go vote in the "early shutdown" poll

Note4 boots into download mode.

So, here is my problem. I've got an almost four years old Note4. I flashed some custom ROM's after i bought it but then I found an old X-note 4.4.4 based custom ROM and i was using that for more than 2 years. Yesterday around noon i noticed that if I try to use Viber, it takes seconds till it opens, and lags badly. (Before that the phone was working perfectly for years). I deleted it, reinstalled, but the problem stayed the same. After a few hours all the other apps started to do the same, the phone became really laggy. As time went by it got worse and worse, around 8pm it started to freeze, reboot, became almost completely useless. I thought maybe a factory reset and a new flash would help. I did a factory reset, and flashed a completely stock ROM on it. It started well, was working good for an hour or so, and then the same problems occured again. Lag, freeze, reboot.... And then nothing. Did not even restart. I can switch it on every now and then, (like in every 20 minutes), but it boots into odin mode. I thought maybe the battery, but that is less then 2 months old. Anyone any idea what happened? I mean the phone is almost 4 years old, so I'm not really pissed off, the only reason why I wanna keep using the Note4 cuz it's removable battery. I don't like phones with built-in battery, this is why i did not upgrade to Note8 for instance. Any help would be much appreciated. By the way, my device is an SM-N910F.

Well, things got even weirder later. I found my old battery which i replaced 2 months ago, still had some juice in it, i put it in, and the phone started!!! Worked perfectly, for about an hour and a bit, then the same problems occured again, lag freeze reboot, and now it boots itself into recovery if i can start it up at all... All the same story. Anyway, i threw it in the drawer and bought a new phone.

nexus 4 randomally shuts off?

have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.

probably battery issue
Gibson295 said:
have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.
Click to expand...
Click to collapse
It's probably battery. Does the phone shut down on charge?

I have same issue and I don't think that it's something wrong with the battery, because I already changed the battery and nexus 4 still freezes sometimes. And it's looks like freeze, not regular shuted down phone, because it's hard to wake up after that happens.
I read somewhere that this may be issue with internal memory, but I'm not sure about it.

Gibson295 said:
have an old nexus 4 i wanted to try fixing a few issues with so i could keep using it as a backup phone.
It likes to sometimes not wake up from stand by. i'll go to use it and the screen won't wake up and it is hard to get to reboot but eventually does then works fine for a bit then repeat. Sometimes even when the battery is fully charged i could go to sleep one night wake up in the morning and it's like it just randomally shut down and is sometimes hard to start other times not, but always has to fresh boot.
not sure what the issue is.
i have re flashed OEM roms in the past to try and fix the issue, and ofc it just updates to 5.1.1
>< all help appreciated.
Click to expand...
Click to collapse
Had same issue running on stock 5.1.1 or something like this. Shut downs, reboot, frozen screen, don´t wake up, start problems, networking complete breakdowns.......installed Lineage 15.1 official and no such issues so far.
So it might be Android related.
So best thing, unlock bootloader by Nexustoolkit, flash latest custom recovery TWRP (you have to flash an older version first, if not having TWRP allready) and then install Lineage 15.1 official. Use instructions provided by XDA. It might be dropped, but it runs great.

Galaxy S5 with Lineage OS stuck in a bootloop

Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Might Be A Malicious OTA Uptade , My Advice For You , Install Stock Rom

Try installing a different rom and if that works, retry installing LOS. Two years ago i became unable to update/install LOS. RR was an instant success and i kept using that till becoming somewhat instable one year ago, so back to LOS, w/o difficulties(probably a clean install of RR would have solved the problems i had, but i didn' t want to do this two times, if really RR and only that was the culprit).
Of course you can start by reinstalling stock rom in Download Mode, as this will be the last attempt if all previous measures may fail. Then re-root, re-install TWRP etc.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
I Heard That The Last Uptade For Lineage Doesn't Work So Download A New ROM In Your Computer And Put It On A SD-CARD And Boot To Recovery And Clean-Flash It
Oh If You Want To Know My ROM I'm Using : Resurrection Remix.

XxXPhantomXxX said:
Hello everyone,
I rooted my Galaxy S5 (SM-G900T) about 6 months ago. I also installed Lineage OS. All of it has worked fine until recently, I downloaded a new update for Lineage. I tried to open the Google Play Store after the update but it kept crashing. So I waited about 15-20 minutes and tried again. I rebooted as well. It was still crashing. So I thought I'd try installing an older version of the Play Store to see if that would fix it. My S5 rebooted, and hasn't loaded since. I am stuck in a boot-loop. I have tried an Advanced wipe and tried to re-install Lineage OS and GAPPS. Still won't boot up. Will I even be able to get my S5 out of a boot-loop? Am I doing this the wrong way? What are some other options for getting rid of a boot-loop?
Click to expand...
Click to collapse
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.

yerrag said:
Since it's old, possibly hardwqre related.
Recently, I had that with my stock s5 s906s.
I reloaded stock firmware but to no avail.
Occasionally it boots up but I noticed it would go past the boot loop after I gave up and gave it a rest for a few days. Then I realized it was a temperature thing. When it's hot and I put the batt in, it would automatically start and go into a boot loop.
But then, it does not always boot well even after giving it a long rest.
I then reached out for my Qi wireless receiver, slapped it on top of the battery, pressed the 3 pins onto the connectors on the phone, and pressed the power button. And the phone booted well right after.
So, something in the old phone has made it sensitive to internal heat. Cool it down by turning it off, even if you have to remove the battery. Leave the battery out. If you have to recharge it with a charger or with another s5, do that.
Then, once cool, put the battery back into the phone with the qi receiver strapped onto it, and make the 3 contacts in the wireless receiver touch with the 3 connectors in the phone as you slide the battery in. Then press the power button. Somehow, this makes up for the old phone's faulty circuitry's tendency to start by itself when the battery's put in.
It is a quirk in my old phone, but other than that I have loaded it with an RR rom and it is running now like a champ. Just expect it to go into a bootloop each timeI I restart as there is heat already from its operation. When that happens, remove the battery and let the phone cool off before putting in back in to start.
Click to expand...
Click to collapse
Well, this worked for a while. Then, bootloop became more stubborn.
By then, I had already bought a phone to replace it, so I was in no hurry to fix this issue but still, I hate to see a good phone go. Still has a screen that stood the test of time, and at high res, and I love the size of the phone.
So, another Hail Mary. And it worked!
I put the phone, worked in tissue paper, then enclosed in bubble wrap, in the freezer overnight, surrounded by grains of rice in a plastic container, that had been vacuumed by a FoodSaver machine.
The following morning, removed the phone from the freezer and laid it bare, separating the battery from it, and wiped it clear of moisture, and let it sit to evaporate any more moisture from the temperature gradient.
Then started the phone, and the bootloop once again gone.
So, phone saved. But since it's no longer that reliable due to the recurring bootloop problem, it would be my phone to watch streaming movies from Amazon Prime or Netflix, but not my phone for receiving calls and text messages, or for Waze and all.
The lesson I got from this is that with this phone, the circuitry inside has become finicky. To open it up and fix it would be too bothersome, especially with the circuitry being composed of embedded modules. Probably somewhere inside there is a capacitor that has reached its reliable end of life, but still breathing and needing an occasional handholding. So, I just gotta learn to live with this quirk, and this quirk is tolerable for the use I have it for.
So, if you run across this problem, I hope I gave you a workaround for you to remain loyal to a workhorse that served you long enough.