Related
Hello
My HD2 Worked well for a long time, but now everytime I press the "sleep" key it turns off for half a second then turns back on and proudly displays the lockscreen without me pressing anything. There is no way to turn the screen off and go in standby mode anymore.
Obviously the battery drains so much faster from not being able to have the screen off and this silly problem actually makes the phone unusable
I flashed a few roms using HardSPL and now HSPL2. I'm currently running Artemis 11.0, the problem appeared may days after flashing while using Artemis ROM 9.0. A hard reset seemed to fix it but the problem reappeared. Today flashing 11.0 only solved the problem at first boot.
Anyone had that before? Not sure if it's software/rom related or not anymore. HELP
As far as Ive seen, its only you an me who have had this problem so far.
Honestly, Im relieved to see someone else with this problem.
I had exactly as you described, but using Axlor roms.
It worked fine for 1/2months, then all of a suddon the screen backlight wouldnt go off, but a reset fixed it.
But it got worse and worse.
Now nothing will work...
Ive taken everything back to stock, and i mean EVERYTHING! Not a single app installed.
And I still have this problem. I've tried it all.
I think its a warrenty job....
EDIT:
I also noticed the backlight will go off fine when the phone is charging, is that the same for you?
I just sent the phone off to Tmob today, to see if they can fix/replace it.
I'll keep you informed.
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
I experienced this issue when I minimised a game called virtual pool. Closing it in task manager would then allow me to permanently make the phone sleep.
samsamuel said:
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
Click to expand...
Click to collapse
How come Ive still got the problem after reflashing several times and taking everything back to exactly as it came from the box?
flannco said:
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
Click to expand...
Click to collapse
I too have had the navi panel problem.
Im praying they fix mine under warrenty
Yes the problem is exactly what you describe, hard reset and flashing to a stock rom doesn t fix it with no programm running in the background
Navipanel seems to be on randomly sometimes so can I guess it could be related.
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Considering sending it for warranty now.
Thanks for replies! If anybody knows more let us know
Update re standby problem
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
flannco said:
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
Click to expand...
Click to collapse
I have a feeling mines going to come back from tmob in the same state i sent it in...
What other options do with have if they sent it back without fixing it?
any info? I still have not had mine back.
bump... any more infos on this?
CrocMonsieur said:
bump... any more infos on this?
Click to expand...
Click to collapse
Ive noticed allot more people getting this problem. So its not only us.
Tmob are replacing mine, so Im guessing its out of our control now.
did any of you guys try performing a task 29 in between flashing roms? it may help
Audio Oblivion said:
did any of you guys try performing a task 29 in between flashing roms? it may help
Click to expand...
Click to collapse
Actually no, I overlooked it.
Probably would have been a good idea
Prehaps thats worth a try Mr Opr
CrocMonsieur said:
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Click to expand...
Click to collapse
Thanks for this workaround. Now with the urgency gone hopefully somebody finds a lasting solution without the need of sending it in..
I have same problem guys after 4 months using. ...and my HD2 is unusable with no standby. I mean battery gets weak during 2-3 hours. Whats your guess guys is it software problem. Cause Im afraid of this is hardware prob because after reset goes my device in wrong state.
Help!
Sadly I'm running into this same error with my t-mobile hd2....getting serious power drain...can anyone confirm if the task 29 helped at all? Mine won't stay off for more than 30 seconds.
** Found out the google easy sms beta app I was running had a service which was causing the app to come out of standby...uninstalling this app cured the problem.
For me, it was a sd slot problem. When i removed the sd card, phone always waked up after 0.5 seconds, and card was detected as bad.
Now the SD slot was changed (under guarranty) and it work fine, no wake up if sd slot is empty.
Any update on this? My HD2 starting doing this today as well
And I have no usb cable at work to 'trick' it. The only option is to pull the battery which I don't want to do. This is ridiculous. Am I going to have to hard-reset the damn thing to fix it?
FYI I didn't do *ANYTHING* to my phone in a couple of weeks (no new apps, etc.) and it started doing this out of the blue.
You hit the red 'end call' button and it goes black..then comes right back on.
The odd thing is it *thinks* its plugged in because the only screen setting I can get it to acknoweldge is the 'backlight level when charging'. So somehow my phone thinks its plugged in even though my only usb cable is back home.
Grrr. No registry tweaks or temp files I can delete to reset this behavior?
Since I have got it (2 weeks ago) i have picked up my phone make a call, and on about 7-8 occasions, have noticed that the phone is turned off, and I can't get it to turn on. The only solution is to take out the battery and put it back in. Has anyone else experienced this. I have updated to JH2 firmware, but it still happens. I even got a new battery for the phone (Bell employee let me swap with another phone that was going back to samsung for gps issues), but the problem still happens once in awhile (like every 2 days, sometimes more sometimes less). Anyone have any ideas? thanks
More likely that it just "freezes" and you can't get it to react, then the solution is to take out and back in the battery - Sounds like a defective unit to me.
i think your phone was unable to wake? i have that problem previously where i can still call through my phone (using another phone) but there's no vibration / notifications of sorts.
i then realized i've been playing with SetCPU of late, long story short, i uninstalled the application, rebooted and all is fine since then.
good luck!
if it still persists, i'd do a reflash, wipe every bit of data available + formatting my SD cards. lol.
Adevem said:
i think your phone was unable to wake? i have that problem previously where i can still call through my phone (using another phone) but there's no vibration / notifications of sorts.
i then realized i've been playing with SetCPU of late, long story short, i uninstalled the application, rebooted and all is fine since then.
good luck!
if it still persists, i'd do a reflash, wipe every bit of data available + formatting my SD cards. lol.
Click to expand...
Click to collapse
So..are you saying that the phone is actually still 'on'...just the screen is not turning on?
yeee sort of. lol. but why it's unable to answer, yet able to receive calls. i have no idea. same goes for any kind of notification that wakes your screen (SMS, calls, alarm, etc.)
Next time it happens, i'll try calling the phone to see what happens...I dont wanna return it because I have a 'rare' phone that seems to have good gps and can enter recovery mode.
you should check bell to see if there working and have recovery mode i got my just recently the newer shipments are hopefully all working with recovery mode and good gps
Did you install any Lockscreen app or something similar? I´ve read about another guy who had similar problems with a not waking up device. And it was a lockscreen app that caused this.
Yeah, I agree with everyone. I had SetCPU on my device and it would shut off a bunch of times per day. After I unintalled it everything worked fine. Another trick you can try is when the phone "freezes" try to hold down the home key. You sould still get the task manager box.
My first SGS did this a lot. My second and third SGS have not done this. Conclusion: faulty.
Yep...
I'm with mine for more than three weeks now, and I've never managed to cause it to freeze/shut down. although yours considerable rare, You'd rather have a working device I presume...
TMReuffurth said:
Did you install any Lockscreen app or something similar? I´ve read about another guy who had similar problems with a not waking up device. And it was a lockscreen app that caused this.
Click to expand...
Click to collapse
No, i haven't installed any apps like that. Like i said, GPS works 'ok' on this phone and it enters recovery mode. Thats why I would hope its a software thing and can be fixed. I will go back to get an exchange today ONLY if they let me try it out 1st (recovery mode).
I've had this happen twice, both times I was charging the phone with the screen locked and the cable was accidentally violently jerked out, after that my phone wouldn't turn back on without a battery pull. It has not happened of it's own accord though.
Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
franshu said:
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
Click to expand...
Click to collapse
Mine is happening the samething, glad Im not alone. My was running fine on rooted Modaco custom rom for a few weeks then all of sudden the phone auto shut down like it has its mind. I installed Cantonese keyboard and camera mod too and some other apps. Currently Im tracking down the source. Now I have franco kernel and madaco rom on clean install running with no other app install to see if it will shut down or not. If it does Im going back to stock to see if samething happen.
I have to boot it couple times until it doesnt shut down itself anymore. Sometimes it be stable for couple hours or couple minutes or instantly.
I have the same problem, Just got my phone from google everything is stock nothing has been changed and the phone just turns it self off and then i cant turn it back on for sometime.
Does anyone know what causing this problem?
Mine also turns off multiple times a day, sometimes by itself, sometimes during a call, often when taking a picture.
Today every single time I took a picture it would shut down.
I'm f*cking pissed at waiting 5 weeks to get a useless phone... and god know how long it will take to get a replacement if I ca get one.
Hi guys, I have the same problem too
I've used my Nexus 4 for 2 weeks without any kind of problem when suddenly it turned itself off. If I try to turn it on, the phone just turns itself back off again and I haven't solved the problem even with a reset.
But I've noticed that the battery doesn't charging even with the charging cable. I think the phone detects that hasn't enough battey level and for that reason turns itself back off.
Do you think it can be an harware or software problem?
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
kalipedia said:
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Notorious544d said:
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Click to expand...
Click to collapse
You know, I'm looking at my battery history (using battery monitor) and i see the period that the phone was shut down and then when i powered it back up this morning and i notice the battery temp is extremely high so it probably has to do with the phone shutting down due to overheating, which obviously shouldn't happen. I wasn't using the oem charger, so I'll switch to that for the time being and keep an eye on temp. Hopefully it's a software bug and not a faulty battery because it should definitely be cutting off charging when it reaches 100%.
Sent from my Nexus 7 using xda premium
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Sounds like your battery is on its way out. Have you tried a new battery?
Already mentioned in post above
tiguy99 said:
Sounds like your battery is on its way out. Have you tried a new battery?
Click to expand...
Click to collapse
QCube said:
I've tried everything, bought a replacement (genuine) battery and not fixed it.
Click to expand...
Click to collapse
Earlier in the week I had an error I've not seen before. Phone restarted and went to black screen sort of looking at a recovery screen with android logo and in the centre of the screen was the message
"Kernal Panic" with some information on the top. This only has happened the one time and hasn't happened since. Took the battery out and restarted again...
Try hardreset or flash via odin
Krprem said:
Try hardreset or flash via odin
Click to expand...
Click to collapse
How do I go about doing either of these....
Still happening and it's driving me insane, It won't last me until the end of my contract (January)
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
ithehappy said:
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
Click to expand...
Click to collapse
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
phonepie said:
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
Click to expand...
Click to collapse
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
grizzylemon said:
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
Click to expand...
Click to collapse
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
While upgrading a phone, especially for major upgrades like from LP to MM, OTA method should always be avoided. You MUST do a clean flash of the ROM, otherwise you are bound to have problems. 80% of time people complain because they didn't flash the ROM cleanly, so whatever you want to do now, do it, but if it doesn't solve it (very likely it won't), then kindly flash the ROM via Odin after a full wipe. And if even that doesn't solve it then its hardware.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
phonepie said:
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
Click to expand...
Click to collapse
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
QCube said:
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
Click to expand...
Click to collapse
Are you able to wedge a folded small piece of paper between the bottom edge of the battery and the phone to make the battery fit tighter? I mean it's not good to have a loose battery. But I can't see how that would cause the screen to stay on. If anything I would think it would cause the phone to shut off or reboot.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
grizzylemon said:
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
Click to expand...
Click to collapse
why don't you reflash you device with supported PIT file and stock F.W ?
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Aside from the previously proposed wake lock solution, members in the T-Mobile Note 4 threads have experienced limited success with a downgrade to LP from MM.
From my reading, these issues seem to be common across all Snapdragon models, not to say it Exynos is excluded (I don't frequent Exynos threads).
himuslg123 said:
why don't you reflash you device with supported PIT file and stock F.W ?
Click to expand...
Click to collapse
I tried that and it didn't work for me. The only surefire solution is a replacement device, but even then there's no guarantee the device won't start acting up in the future.
pls help stuck in download mode
this is the issue I'm getting...I did a complete data wipe using twrp...now stuck on this screen...cant even push files...device not recognized in adb or fastboot mode....
what to do...??
imgur(dot)com/a/gKPaL
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
hathertonwood said:
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Click to expand...
Click to collapse
Wow, that sounds promising. I'm sending mine for replacement, and although I'm not getting a new MB installed, hopefully the incoming unit will be similar in performance to yours.
ithehappy said:
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
Click to expand...
Click to collapse
Your reasoning sounds plausible, but my phone suffered similar issues and I only flashed my unit 2-3 times in the 14 months I had it.