odd freezing and permasleep? - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Hello Note 4 XDA family. My girlfriend has a note 4 completely stock. I don't use the device regularly as I have n6. She's experiencing some problems when the phone goes to sleep it never wakes back up. You have to do a battery pull in order to get it to boot back up. She is at work and dealing with it. But every time it boots back up its insanely laggy like 7-12 seconds frozen, with no force closes. Then once it comes back it works fine until she turns the screen off again. Then enormous lag and no power back on until another battery pull. I'm guessing its a problem with the device, I haven't seen anyone else with the same issues. Wondering if anyone has some input, I am going to do a hard reset tonight. Backup everything and (I don't know if Odin is still a thing but I'll figure it out) reflash the phone to factory and see if that helps. If not sprint should replace it I would imagine.

When it starts to lag. Does the device ever get really warm or instantly hot? It might be an application running in a background that's hogging insane amounts of CPU.

skuddy said:
Hello Note 4 XDA family. My girlfriend has a note 4 completely stock. I don't use the device regularly as I have n6. She's experiencing some problems when the phone goes to sleep it never wakes back up. You have to do a battery pull in order to get it to boot back up. She is at work and dealing with it. But every time it boots back up its insanely laggy like 7-12 seconds frozen, with no force closes. Then once it comes back it works fine until she turns the screen off again. Then enormous lag and no power back on until another battery pull. I'm guessing its a problem with the device, I haven't seen anyone else with the same issues. Wondering if anyone has some input, I am going to do a hard reset tonight. Backup everything and (I don't know if Odin is still a thing but I'll figure it out) reflash the phone to factory and see if that helps. If not sprint should replace it I would imagine.
Click to expand...
Click to collapse
It's a software related problem i had the similar problem in the 1st weeks i got my phone it used to freeze for a second once every 10 second
I did soft and hard reset and the problem was still there.
But the new firmware came out which is the current one, i decided to do another hard reset to take the update and since then my phone is back alive no lag.
If the hard reset doesn't fix it for you wait for lollipop and do s hard reset before taking the update
Sent from my SM-N910P using JellyBombed Tapatalk 2

We took it to the sprint store. She had an old class 2 SD card it it from my original galaxy s or HTC desire (don't remember which). The rep there said to take out the SD card and it will fix the problem. So she took it out. And no issues since. That seems like a really really weird bug to me. But he said its common in the note 4 with the slower class cards....? Whatever. No issues since.

Related

Official HTC EVO Random Reboot Thread

From searching, it looks like tons of people are having random reboot issues with the HTC EVO. Let's make one thread to put everything so maybe we can figure this out.
Side note, it looks like the HTC desire has the same issue:
http://forum.xda-developers.com/showthread.php?t=676402&highlight=rebooting
So post what you've tried that hasn't worked.
If you think you have a solution, share
One thing I've noticed is it seems heat related.
I've installed temperatures monitors and it seems around 32 degrees Celcius is around when it reboots. It will reboot loop usually. This can be cured by pulling the battery and waiting for it to cool down, or just put it in the freezer for 4-5 minutes.
I've tried underclocking it with the screen dimmed way down, and running it without the back cover and it still overheats.
For me, the problem came out of nowhere. I had the device for over a month with heavy usage and no problems. My current GUESS is it must be a physical problem. Not enough thermal grease or something...
It looks like the HTC Desire users may be getting replacement motherboards to fix their issue.
Does the HTC EVO and Desire share parts?
From other threads it looks like:
Root or Stock - Doesn't matter
Radio version - Doesn't matter
Rom version - Doesn't matter
GPS Fix - Doesn't matter
GPS turned off - Doesn't matter
3G data, 4G data turned off - Doesn't matter
Hard Reset - Doesn't matter
Found this on the HTC Desire reboot thread:
Latest test list for HTC Desire RR (Random Reboot) problems:
-All phones with s/n HT03 to HT07 can get this problem (Minor problem from SH09 so far)
-Starts around 1.5 to 3 months after use
-Reboots get worse over time
-Firmware and android version doesn’t matter which you have
-Force apps2sd doesn’t matter if you use it or not
-PVT1 or PVT3 or whatever doesn’t matter
-Screen type, doesn't matter if you have AMOLED or SLCD
-There seems to be an antenna/radio/simcard issue also
-Overheating causes reboots too
-Reboot is not always temp related
-SD card size doesn’t seem to matter
-Having apps on SD or not doesn’t matter
-Size of files on SD doesn’t matter
-Rooted or not doesn’t matter
-Motherboard changed after repair doesn't always fix it
-Sim locked or not doesn't matter
-Provider doesn't matter(vodafone, kpn/hi, T-mobile etc all got it)
-Most likely hardware issue, sense flashing won’t fix it, yet changing motherboard will
-Restarting doesn't fix it
-Factory resetting doesn't fix it
-Changing/buying new battery Doesn’t fix it
-Using app killers or shutting down some services yourself doesn't help
-Leaving all settings on default doesn't fix it
-Plugged into car charger in the past doesn’t matter
-Hboot version probably doesn't matter (still not fully tested)
-Having a phone cover or not doesn’t matter
Click to expand...
Click to collapse
wifes phone has been doing it very bad...one that has never been rooted...
was going to root it and try new rom but seems to be a hardware issue.
any other comments on this subject?
My stock rooted Rom just rebooted for the first time today. I really don't rememebr what I was doing st the time....but this has never happened before. I assume there's no event log to check.
Sent from my PC36100 using XDA App
I had been facing this with increasing frequency. I got the phone on launch day, and the problem started over the last month, getting worse all the time. I agree with the OP that there does not seem to be any obvious cause -- sometimes it is heat related, sometimes not. Any time I push the phone (run psx4droid, or navigation + anything else), and sometimes even with lighter usage, like on a phone call. Unrooting did nothing to stop the problem.
After extensive searching, I found three possible causes: bad battery (I tried a new one and the problem continued, but this seems a good starting place), bad memory blocks, or bad processor.
I was unable to find any solution to this problem. I took my phone to Sprint today, and they told me that their tests didn't show a problem. Then I made it happen in front of them (launch navigation to anywhere, then a couple more apps, then boom, reboot) a couple times (really, after the first time, letting it turn back on pretty much caused it to happen again).
After that, they agreed to replace it. I do have the TEP, but they assumed that the problem was hardware related so I don't know if you have to have it for them to replace it.
Strangely, they gave me a white one as a replacement.
I haven't had any problems with the new (well, re-manufactured) one, and I hope it stays that way, but I guess only time will tell.
I'm currently experiencing the problem as well, funny thing is every time it happens, the phone is NOT in use, simply sitting on table or desktop in standby. This happens about once every two days.
Currently running rooted evio2 1.3.1
Wow, I was about to start this thread, when I saw this. I guess I was like 10 minutes late. Either way, i believe something messed with the hardware. My little bro cracked my screen badly, so I am getting a new evo anyway, but will I be able to get one free bcuz of this? This is really a terrible problem. Somebody needs to de-assemble their precious evo and see if there is an obvious problem. thanks a bunch. Subscribing.
same here.
happens mostly when on the charger and i am using it at the same time. so heat related seems likely.
can anyone get a logcat of it happening?
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Sprint replaced mine for $35 [a refurb]. That's the end of that.
But now, I can only use the speaker to hear my callers. Gotta go back and get another!
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
thlinx said:
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
.jond said:
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
Click to expand...
Click to collapse
Actually I just had a reboot lol.
Sent from my PC36100 using Tapatalk
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
I bought my EVO on launch day (HW Version 002), and have not had any problems until around Oct 13.
I took the phone on a trip to Orlando, and as soon as I got off the plane and turned on the phone, the problems started happening. It has been happening ever since, even since I returned home.
I bought my phone at Best Buy, and have had their Geek Squad send it back to try to fix it. I also added the complaints about screen separation to the workorder so that they would be more likely to replace the device. Hopefully, this fixes the issue.
I also think it is heat related, but I don't know why it is just now becoming an issue. Just to make sure the folks at BB could see the issue happening, I put the phone in front of my car's heater for a few minutes, then started up Google Earth, and was able to make the phone start boot looping while I walked into the store.
I tried hard reset, soft reset, update prl, underclocking, GPS Reset, new battery, new SD Card, and none of those things worked. I wonder if the removal of the 30 fps limit in the last update caused some type of heat damage?
I just had a reboot last night while trying to look at a picture I'd just taken in the Camera app on CM6.0.0. Only the 2nd or 3rd time it's happened. Still annoying though. Hope it doesn't get worse.
.jond said:
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Click to expand...
Click to collapse
How much they charged you?
Sent from my PC36100 using XDA App
MedSchool26 said:
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
Click to expand...
Click to collapse
I reset mine back to stock. Unrooted it and everything.
Didn't fix the issue for me.
Now I did try erasing all the stuff that's erasable inside recovery and it seemed to go a few days without a reboot. Not sure if that was a fluke or not.

[Q] Did I get a bad Galaxy Nexus?

It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Try to do a clean install ... or wipe your cache and Dalvik cache
and your bone stock I would DEFINately bring it back ive installed countless roms and kernels and never pulled battery yet you didnt need to spend your money on a defective phone
irizwan said:
I believe theres a rouge app responsible .. try a clean install then don't install any apps then check
Click to expand...
Click to collapse
He just said he did this.
Anyways, try flashing a kernel and raising the minimum value slightly, saw this fix every SoD on the G2x forums. You'll need CPU Master or something similar.
I'm using CPU Master Pro, in case you were wondering.
Sent from my Galaxy Nexus using Tapatalk 2
Unroot and reroot. Problem should be solved.
Sarumiso said:
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Click to expand...
Click to collapse
Install a custom kernel and change your minimum CPU to 700mhz. Fixed my sods. Honestly though I'd go for an exchange.
Sent from my Galaxy Nexus using xda premium
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Toad858 said:
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Just get the Gnex, geesh. There's lemons with every product, not just phones.
Sent from my Galaxy Nexus using Tapatalk 2
Might be a bad Sim card
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Sarumiso said:
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Click to expand...
Click to collapse
To go to Bootloader mode requires VolUP+VoldDOWN+Power button
suggest returning defective phone
You phone seems defective.
I realize you don't want to send it back, but getting stuck with a bad phone can drive you crazy.
When I bought my Evo 3D phone a year ago, after the update, it started to reboot at random times. After talking to their support, with no solution, I insisted on a new unit.
Once I got the new phone, I had no problems ever again.
Now I have the Galaxy Nexus, and I used it a lot the first few days to make sure it wasn't defective.
I hope you can find a solution, but if you don't, consider getting a new unit. It's not worth the hassle of keeping a questionable unit.
Have u tried to unroot yet??? It fixes all the problems u could possibly have.
Use Wug's toolkit to fix this issue.

Faulty battery that wasn't faulty for 8 months?

Okay I recently wrote a thread about the random restrarts on my g3 that happened 10 times a day, but the things have gone too far. As i was having random restarts when I monstly use the camera but not only for about 5 days and some of those restarts were also shutdowns now the problem is more serious. Today i was intending to take a picture of something and as usual the phone restarted but STUCK on the startup boot "picture" that says that lifes good and then goes black screen and startup picture and black screen and so on. I wasn't able to use the phone. I pulled out the battery and tried again but it didn't worked. So as I went home i plugged the phone ot the charger and when i powered it on it started normally and tried to take pictures and there weren't any problems. So I think that this is the battery that is making this **** to happen. I highly doubt that this is software problem but from my quick examination i think that the problem is from the battery . What do You think. Tommorow i will go to my carrier and "ll try to explain them about this. But they are usually jerks who don't know anything about phones. They only know how to get your money.Anyways. Yes.
discoverymen1999 said:
Okay I recently wrote a thread about the random restrarts on my g3 that happened 10 times a day, but the things have gone too far. As i was having random restarts when I monstly use the camera but not only for about 5 days and some of those restarts were also shutdowns now the problem is more serious. Today i was intending to take a picture of something and as usual the phone restarted but STUCK on the startup boot "picture" that says that lifes good and then goes black screen and startup picture and black screen and so on. I wasn't able to use the phone. I pulled out the battery and tried again but it didn't worked. So as I went home i plugged the phone ot the charger and when i powered it on it started normally and tried to take pictures and there weren't any problems. So I think that this is the battery that is making this **** to happen. I highly doubt that this is software problem but from my quick examination i think that the problem is from the battery . What do You think. Tommorow i will go to my carrier and "ll try to explain them about this. But they are usually jerks who don't know anything about phones. They only know how to get your money.Anyways. Yes.
Click to expand...
Click to collapse
here is a gif showing what exactly is happening
discoverymen1999 said:
here is a gif showing what exactly is happening
Click to expand...
Click to collapse
Are you rooted? Did you flash anything? Did you edit any system files? Looks exactly like when I bricked my phone. There is a fix. Check out this thread and the links in it. http://forum.xda-developers.com/lg-g3/help/lg-g3-unbricking-steps-clarification-t3119844
Also can you access download mode or recovery. You might want to try them first.
No I havent rooted it or made any system modifications. This problem occurs only when my phone isnt charging. When iits charging even at 100% there isnt any problem
I've gone to my stupid carriers office and explained everything but they do not want to give me a new battery unless they bring the phone to the other end of the country for repair. This is extremely stupid. Now I can't use my phone because its totally "bricked". I xan only use it with my original dc charger if i unplug it the phone shuts off. Yesterday Ive decided to make a factory reset, but i wanted to copy my internal storage to my pc, but the phone won't turn on when its plugged to the pc. I don't know what the **** is happening with this 500 piece of pancake.
well i have finally decided to do a factory reset but after the anticipation and thinking it is a software problem it isn't apparently. Maybe i will just send it to repair and hope that i wait less than 20 days for it to come back. And i hope that they don't figure out the problem and send a new phone but i think it is the battery that is the problem. Anyways the modern technologys are the most incredible thing and the most getting you pissed of one. You pay 500 dollars+ and expect something good and there you go .
So did you do factory reset or not?
Btw, getting phone to repair center is a good decision, they'll see what's wrong.
I have been happy with my G3, only "minor" thing I don't like is the horrible backspeaker (coming from HTC One m7)

Freezes and reboots 15+ times per day.

Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
By any chance are you using the fingerprint scanner for your lockscreen? I had a similar problem until I turned it off in favor of a pattern lock screen. No problems at all ever since.
No, just the typical slide screen. My first thought was an app, but it is so sporadic, plus it has even locked up during the setup menu after one of the flashes. Very strange.
Mine started doing the same thing a few weeks ago. Freezing then rebooting. SystemUI.apk crashing.
Fresh ODIN to latest. Rebooted during setup. Eventually my phone wouldn't power on last Saturday.
I'd recommend backing up your phone and prepare for it suddenly dying. I found a few posts on Reddit saying others had similar issues.
I took it back to Sprint and they offered me a refurbished Note 4, so far so good!
AVAH0LIC said:
Up until this point I hadn't messed with this phone, it was stock all the way. About a week ago it started acting funny, slow, would freeze occasionally. Figured it was time to root and throw a custom rom on. But the probably seems to just be getting worse. The phone is practically unusable.
Recovery still works fine, still pulls up into ODIN no issues and flashes.
I've tried 100% stock flashes, I've done the OTA, I've tried the awesome Note 5 port going around, even the older ones. Have tried OK1, OB7. And now I'm flashing the MM Odin File. Like I said the flashing is going through perfectly every time. But after setup yet it just keeps freezing, and then immediately goes to reboot. Sometimes it even gets stuck in bootloop, have to pull the battery. A couple times it has went directly to Download and said "Cannot do normal boot" or something like that.
Is this phone done for? Like I said, sometimes it's unusable. For instance, I just went 4-5 hours with it performing flawless, and at this exact moment; I couldn't make a phone call if my life depended on it.
Any ideas/help is greatly appreciated. Would be happy to provide any more info.
Thanks!
Click to expand...
Click to collapse
I had the same issue. the phone kept rebooting in to download mode. sometimes I would have to pull the battery for a few hours to get the phone to even start. I Replaced the logic board to fix my phone.
Logic board? How hard is that to do? Where can i buy that part?
Ive had to replace the usb port, that wasnt too bad, im assuming its a similar task?
Lol the thing that makes me feel like such an idiot - I came here immediately when it started happening, and since I hadn't rooted this phone before I didn't do it 100% and cause Knox to trip.
The kicker? My 1 year warranty expired 4 days AFTER it started happening. So had I not screwed up and trippes knox, Samsung wouldve replaced.
My freind sold me his note 4 for $50. There are alot of videos on how to do it. It wasn't that hard. Some of the videos have links where to buy the different component's. https://youtu.be/OUDgGaFcCNY edit. The logic board is the motherboard
Sent from my SM-N910P using JellyBombed Tapatalk 2
This is insane.
After dealing with this issue for a while, I finally ponied up the cash and bought a Note 5 from eBay.
The phone was still acting ridiculous all day - I must have done soft resets at least 10 times between 6am-1:30. Excited to get home because the Note 5 was in the mailbox.
I get home, call Sprint, have them switch activation to the 5. They told me to turn them both off, they did their thing, and now service is on the 5. Just like normal.
The ONLY thing that has changed was the information in the phone regarding service/activation; and now the Note 4 is running FLAWLESSLY. I don't understand how that could cause the problems that I was having, but now I'm frustrated as I just dropped a good amount of money to buy a phone without a contract/upgrade, and now it's working perfectly. Does anybody have any ideas on how this could have changed anything???
Same here also...
My phone just started doing this out the blue about a week and a half ago. It will freeze, hang, get extremely sluggish, reboot randomly, power off randomly, there will be about a 5-7 second delay with touch responses, typing will be delayed, etc. I did all the things, rebooted, pulled the battery, unrooted, went stock, re-rooted and tried other ROMs, tried custom kernels; I got the same results. I have a Note 3 I'm going to reactivate over the weekend and see if my Note 4 suddenly performs flawlessly since it won't be activated.

Marshmallow broke my phone so I...

Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.
I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!
I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.
I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?
I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.
trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?
The LG v20 and so far so good!

Categories

Resources