I'm not sure if it's a software problem or a hardware problem that's not the motherboard.
This is my phone's original stats, as I have written down.
N7105
ROM: DN3 v3.2
kernal: AGNi v3.9
bootloader: 4.1.2
Recovery: Philz 6.07.9
The problem is that the phone just randomly stopped waking from sleep. Not all the time, but it just started one day and slowly increased in frequency. I eventually figured out that the phone was simply not waking up, causing the phone to (presumably) freak out, because if the freeze happened hours ago, then the phone would be very warm when I picked it up and, after forcibly rebooting via the power button, the battery would be way down.
I noticed IndexServices was using a lot of battery power, and google tells me that it freaks out at files over 200mb in size, but best I can tell, I have no such files. I can't recall anything that would change this when the freezes started happening. It may not be relevant at all.
I could live with the forced reboot for a while, but having my battery capacity killed for no reason sucked.
Screw this, I thought, I have a spare motherboard, I'll figure out the problem later or never.
Nope.
My phone's current stats.
SGH-t889
ROM: DN3 5v2 final slim
kernal: default
bootloader: 4.1.2
Recovery: TWRP 2.8.0.0
I swapped the motherboard in and used Titanium to restore my most-used apps and their data. Unfortunately, the problem seemed to have followed the change, although in a different way. The phone just freezes and doesn't accept any kind of input- no touch, no buttons, nothing. I have to pull the battery to reboot. It doesn't just happen when asleep. I've had the phone literally just stop responding as I was scrolling through a webpage. It seems to happen mostly at night and early morning, which is no bueno. I can't use it as an alarm anymore. But it's still better than leaving it alone only to find the battery down 40%.
It also occasionally reboots on its own. I haven't found a pattern to any of these problems.
I played with this motherboard when installing the ROM and such and never had the above problems, so it may or may not be related to the problem I had with the other motherboard.
It's not my SD card. I pulled it when I still had the N7105 motherboard in. It didn't make much of a difference.
I installed SysLog and got a bunch of logs from the N7105 motherboard right after one freeze/reboot. But I'm not entirely sure what I'm looking at nor what to look for. It's been a while since I've fiddled with my phones, so I'm not very enthused at the idea of reflashing my phone.
What can I do to better pin down the root of the problem, short of reflashing everything and hoping the problem goes away?
I would flash stock rom and kernel without apps restoring just to see if it's hardware or software issue.
there is service menu where you can test sensors *#0*#
you can try to overclock cpu, I remember that some time ago it helped to similiar problems with waking up
Yeah, I think I'll probably have to reflash at some point, just to make sure. But I'm going to avoid it for now, since I have other concerns.
I forgot about the service menu! That's a good idea, thanks!
I've never overclocked a CPU, computer or phone, so I'll read up on that. Not sure it'll help with the t889 motherboard, but it might work for the N7105 motherboard.
Thanks again for the suggestions!
For what it's worth, I have the same problem. It started a few weeks ago. I was using Dr. Ketan's rom and thinking that it might be a rom problem, flashed Resurrection Remix 5.1.1. CM 12.1. For a week there was no problem, but now it's back again.
If the phone is left untouched for a while, it won't wake up and is warm to the touch. And yes, the battery is greatly reduced...
I'll be interested in anything that is discovered....
Thanks.
Well, this is mildly frustrating and not at all helpful, but the weird freezes on the t889 motherboard seem to have stopped by themselves. I didn't do anything beyond poking around the service menu. Everything looked ok there. The freezes continued a while longer, and yesterday I noticed that it had been over a day since I had to pull the battery to force a reboot.
My best guess is that an app update caused a minor hardware incompatibility, and some update this past weekend resolved that incompatibility. I'm going to give it another couple of days before swapping the N7105 motherboard back in and seeing if some app update fixes that problem.
Update: I swapped the N7105 motherboard back in and ran all my app updates. No go; the problem showed up again while I was charging the phone. On the other hand, I was able to confirm without a doubt that it's a problem with this motherboard and not the headphone port that causing the lack of sound output with headphones in. The phone acknowledges the headphones when I plug them in. It just doesn't play anything through it.
Indexservice is still using up far more battery than it should. It might be higher than normal due to all the app updates, but it really shouldn't be as high as it is, so I'm tentatively declaring it related or the cause. Since it's not a file size problem, it may be a corrupted file, which means a reflash in my future, if I want to keep using the N7105 motherboard.
It's possible that all these problems mean that the motherboard is failing. It's two years old. It might just be its time.
Hopefully, reflashing everything will fix the problems. If not, at least I had another motherboard to fall back on.
I'm still having the same problem and haven't found a solution. It often won't awaken and needs a long push on the power button to boot. After booting, if we use it a lot it seems to be fine, but if we leave it alone for a while, it won't wake up.
Is that what you are getting? My wife wants another phone!
We always leave in on the charger all night long (as I have done with all my phones). Can that have damaged something?
I could try flashing a stock rom, but fear this may be a hardware problem. I don't see many participants in this thread...
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
---------- Post added at 06:45 PM ---------- Previous post was at 06:22 PM ----------
That service menu that you quoted above doesn't work on my phone. Could it be misspelled?
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Yes, that is exactly it. As long as I'm actively using the phone, it's fine. It's only when I leave it for a while that it won't wake and I have to press the power button to force reboot.
I also leave my phone on a charger all night, but I hardly think we're the only ones to do this. It might be related, but I kind of think it's not.
You could swap out the motherboard like I did. I imagine they're much cheaper now then they were when I bought mine ages ago. The Note 2 is very easy to take apart.
The service menu as written above works for me. Not sure why it won't work for you.
Did the new motherboard solve the problem completely? I see replacement motherboards for $45 online. They offer both 7100 and 7105. What is the 7105? I now have a 7100 European model.
I downloaded the EMMC check program. My phone does not have the "Insane Chip" that causes the Sudden Death Syndrome, but it has eMMC chip VTU00M -for what that's worth.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Phenomenal. I'm going to order a 7105 motherboard. It will take a while to arrive and my wife will grumpy until it is installed.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Selofain said:
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Click to expand...
Click to collapse
When you installed the new motherboard, did you have to do anything with your imei number?
In reading above it sounds like you changed motherboards several times and during that time the problem went away, but was it really the different motherboard? There are motherboards for sale in China, but I don't see any indication that they are Samsung manufacture. They are compatible, may be used actually, and although they cost 45€, shipping will be 38€ more unless I want to wait 2 months for the free shipping by mail.
Did you try reflashing a stock rom? I am tempted to try that first.....
Regards
I only have two motherboards, and I only swapped them out a couple of times. I had minor problems with the t889 motherboard at first, but the problem went away on its own after a week or so. It had actually been nearly three weeks before I swapped the N7105 motherboard back in, and I didn't leave it in for long, just long enough to determine that the problem was still there. I'm back to using the t889 motherboard now, and haven't had any problems with refusing to wake from sleep.
I haven't flashed a stock rom yet. I found that I couldn't restore the data of one of my apps to the new motherboard, and the data was something I spent hours inputting, so until I find a way to save that data, I won't be reflashing.
I didn't do anything with the imei when I installed the new motherboard, but I was prepared to transfer the imei if necessary. I backed up my old one and would have restored it to the new motherboard if necessary, but it wasn't necessary, so I didn't do anything. I bought my motherboard on ebay, which has both advantages and pitfalls. I'd say definitely try reflashing first, since that won't cost you anything but time.
My girlfriend has had the same issues for around one week (exactly the same symptoms_freezes when left untouched, especially at night, and she has to reboot). She has been on revolution HD 31 rom for months without problem ; she hasn't installed anything lately either... an update is probably the cause. I flashed ditto N4 (after factory reset) but the issue has shown up again... It's a european n7100.
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Weird thing, I got that insane chip but my note doesn't seem to randomly reboots overtime.. I experienced some reboots using some rooms, though, mainly with 5.1.1 releases. Is there any trusty app that really informs me the right chip? Thanks.
Enviado do banheiro
Oh, great! It's good to know that it was a software error rather than a hardware error. Let us know if you figure out which app is causing it. It can't be too common an app, or we'd see more people here in this thread.
So far, the phone is behaving perfectly. My wife is thrilled because she is used to the look and feel of Samsung roms. She didn't like AOSP which is considerably more buggy. Yes, with CM12 roms, random reboots are common. Little by little, we are adding essential apps. We don't even have the phone rooted and may not ever do that since my wife likes to keep it simple.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
quijote1 said:
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Click to expand...
Click to collapse
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
oliwek said:
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
Click to expand...
Click to collapse
I used the latest TWRP recovery because the AOSP roms seem to like that better. Otherwise I have always preferred Philz. I always froze hangouts but our whole family are heavy WhatsApp users. I have now frozen most of the Samsung and Google bloatware and the phone is very happy. Today root and more apps. Oh, I also use Greenify and it's working fine.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Related
Have you ever had intermittent reboot problems on your Incredible?
Did you do a warranty exchange or were you able to fix the problem?
This is regardless of what ROM you use, it could even happen when completely stock. If it is happening when completely stock and/or you were never able to fix the issue, it is most likely a hardware defect (failing/overheating 3G radio?). I'd like to see the prevalence of this problem and if it pertains to one version of the Incredible in particular.
I hesitate to vote "never", because CM was initially pretty shaky, but you asked regardless of ROM. The stock ROM was fine for me, and CM has been great since the RIL update.
Yes
Random reboots on multiple ROMs. Haven't been back to stock because from what I've read, the problem won't go away.
Unlike many others I've read about, my reboots are completely random and are just as likely to happen while idle as while doing heavy processing.
AMOLED screen, Build Number FRG83
CUViper said:
I hesitate to vote "never", because CM was initially pretty shaky, but you asked regardless of ROM. The stock ROM was fine for me, and CM has been great since the RIL update.
Click to expand...
Click to collapse
Yeah if yours was fixed after the RIL update and if the stock ROM was fine, you're definitely not having the hardware problem. In your case, it is just from CM.
Yes and No
My first DINC went back due to reboots which were based on overheating which was, in turn, based on a bad hardware radio (present in many first batch DINC's).
My current DINC has rebooted only a small handful of times, and always when the signal is super poor.
So my 2 cents is ... check you temperature ... if its high and you reboot RMA; if its low and you reboot, check your signal.
That must be what happened to me too. I pre-ordered the DINC and had an early AMOLED version obviously. I do agree that it was because of an overheating/faulty 3G radio, that's the best explanation I've come to so far.
My first Incredible was great for the first 6 months but then it got a spot on the screen that wouldn't register touch inputs anymore so I got a replacement. The replacement from the day one has had rebooting issues. It's happens when I use 3G. I think the phone is overheating and reboots. It doesn't happen very often when I'm on wifi though. The replacement was stock ROM.
Blacklight17 said:
My first Incredible was great for the first 6 months but then it got a spot on the screen that wouldn't register touch inputs anymore so I got a replacement. The replacement from the day one has had rebooting issues. It's happens when I use 3G. I think the phone is overheating and reboots. It doesn't happen very often when I'm on wifi though. The replacement was stock ROM.
Click to expand...
Click to collapse
I would get a replacement for that one as well. It is most likely the 3G overheating issue.
Here's my story:
I had an original AMOLED version back when they first came out, it was rock solid until whenever I made this thread. This was after rooting, custom ROMs, etc. The phone would reboot whenever it wanted to.
I asked for a replacement, and they gave me a refurbished AMOLED. This one was even worse, as soon as I took it out of the box (completely stock) it would start rebooting when I tried to turn it on.
Finally, I got another replacement, and so far I have been happy with it.
Of course, all 3 were AMOLED versions, they always give you a replacement of the version that you already own.
I had this problem for two months ... I tried everything. I changed ROMs, I changed kernels, i changed batteries, i *228, I performed a ruu... nothing worked.
I went from a 1 to 4 reboots a day to now none! I have no idea why. It actually stopped when I started using Athena but I think its just coincidence.
I've been reboot free a month.
Sent from my ADR6300
The reboots seem to be pretty random even when using completely stock incredibles. Without even a history of rooting it is possible to have a reboot issue. The problem is the phone/hardware itself and not user error.
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
ccarr313 said:
Ok here is my question - Two times i have installed CM11 roms, the newest nightlies, after wiping data / cache, using CWM for recovery, and rumrunner to achieve s-off / unlock. The first time my phone functioned fine for a few days, then began over heating and the top speaker quit working, started issuing static after certain apps turned on, or when the phone booted up. Also - battery was draining faster than i could charge it. Would jump multiple % points at a time.
I "BELIEVE" that my charger has gone bad, and that is the culprit for destroying the phone. Even after flashing back to stock, removing s-off and relocking the bootloader, it drained the battery(even when powered off battery continued to drain and phone was hot to touch).
After this happened to my first htc one, i returned it to stock, and got a replacement under warranty. Then i proceeded to root / s-off / unlock my new htc one, and drop CM11 m7vzw onto it. It functioned fine.......until i plugged it into the charger that i think is the culprit. After hitting 100% power, the phone started to heat up and the top speaker quit functioning. I instantly upon noticing this, used CWM to restore a backup of the stock software. Which did nothing to fix the problem, phone continued to over heat and drain the battery, only one speaker worked. I managed to flash it back to the stock oem RUU software and relock the bootloader, attain s-on before it died completely(so i could turn it in for warranty with no issues AGAIN).
My question - is this a bad charger you think, that is killing my phones? Or could it possibly be something inside of CM11 and PA gapps(4.4) killing my phones? I do not have a meter on hand to test my charger, so i am going on logic that it must be the charger. Since i can't imagine that cm11 is killing every m7vzw it is installed one, and it seemed to function fine until i plugged into that charger.
I love custom roms, and seriously hate all the bloatware that comes attached to verizon phones, so looking for some advice from people mor familiar with this subject then i am. I have only recently started customizing my phone. My back ground is in computers not phones, but seeing as how i am not tweaking the cpu or gpu at all, i am thinking it MUST be this charger. Please let me know what you think, if you have experience with this on a m7vzw. I get another phone tomorrow, and do not plan on using the same charger again, but i am somewhat wary as to upgrading the rom after all this crap ive been through. ANY advice is appreciated. Much thanks!
Click to expand...
Click to collapse
Are you using the stock charger?
Try a different charger on the next phone. Many people have flashed CM11 and don't have those issues so it appears to be your charger that's killing the phones.
Don't think it's the charger. I am seeing more and more threads of people running cm11 a d getting this overheat issues then phone dying. I think it's best that people leaves cm11 alone until it can be fixed. As I have never seen any other Rom act like this.
Sent from my HTC6500LVW using Tapatalk
The only thing i can think of, after resting on it, is that i turned on the DSP manager EQ shortly before it happened each time. Not going to customize the one I am getting today. Just thankful I know enough that I managed to get them both back to s-on / locked / stock RUU before sending them back.....so my warranty will cover them.
And yes, i was using the stock HTC charger that came with the device. Wish i had a meter.
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
peteschlabar said:
This is odd. I have been using CM 11 for close to a week now, and haven't experienced any issues like this yet, and hopefully won't. The battery life isn't great (and I will probably return to using BoneStock from @andybones ), but no overheating or speaker issues. I don't normally listen to a lot of music, and I have not messed with DSP manager much, but I have used it, and music/videos seem to work fine. I would recommend trying a different charger to rule that out. Also, if you are getting a warranty replacement, try leaving the phone s-on and stock for a few days and see how it acts with your charger - that will help narrow down the real cause.
Click to expand...
Click to collapse
Both phones are dead. Will not charge, will not turn on. They only worked for a few hours after the over heating issue started. Battery continued to drain even after being turned off, and after it was drained it would not charge at all. It was lucky i could even get them back to s-on / locked / stock. And the issue continued after going back to stock. Hardware damaged for sure. So no more testing on those. lol
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Fu5ion said:
On the next one, wait a week before installing a ROM, and see if the phone functions fine. If not, then its the charger or something else you've been doing with it. If it is fine, try installing cm11 again and see if it returns. If it returns at THAT point, then it might be the ROM, though I doubt that's the issue. You'll never know if its cm11 or something else causing the issue if you immediately flash it after getting it.
Click to expand...
Click to collapse
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
ccarr313 said:
That is my plan, and i have other chargers. I don't plan on using the HTC one. Going to use a stock samsung charger until i get my replacement charger in the mail. I am hoping it was the charger. It just seemed odd that the issue happened both times after turning on DSP, then using the phone to either watch netflix, or listen to music on the speakers. Also, I figure if no one on these forums has the same issue.....then it must be the charger. In the meantime - I am just going to root / s-off and use stock software till next week or so.
I'm just getting paranoid as to how many times verizon will let me get a warranty replacement, even though i am sending them back in full stock format. lmao
Click to expand...
Click to collapse
They'll let you send as many as you want as long as its under warranty haha. I remember I had to send in the droid bionic 4 times and the droid RAZR twice, both times without any hassle from them. I just had awful luck with those phones, mostly screen-lifting.
Haha. Good to hear. Because I have 10 months of warranty left, and I am a computer modder at heart.....and that has turned me into a custom rom loving phone crazy person. :laugh:
Yeah you've got nothing to worry about there. Just make sure its back to stock. They honestly probably wouldn't say anything if it weren't, but we don't want to give them even more reasons to lock us down more.
I'm having the same issues. I'm on my 4th phone now.
This happened to me on several ROMs. SlimBean 4.3, SlimKat 4.4 now.. and I flashed back to stock while I had a phone that wasn't dead yet.. but it's still happening.
I'm not sure what the deal is. Just happens without rhyme or reason out of the blue one day.
Can anyone recommend flashing anything that might help?
What's responsible for the battery management even if there's no ROM installed? HBoot? Should I re-flash an HBoot to attempt to fix? It's not the ROM, I don't think. If it is, it's something that permanently screws up the phone. I've completely wiped my phone and went to stock. Same issue.
I got my new phone, and s-off'ed / unlocked / flashed cwm recovery, then updated it to 4.3 ota, no issues so far. Scared to put any custom rom after what happened to the last two. But having no issues yet with it, with only a custom recovery and s-off. Have rom manager loaded also, and made a back up since it seems to be running fine now. If anyone isolates this problem and can get a fix going, would make me very happy.
I've noticed that trickster and some of the other CPU performance apps are locking the min CPU speed at the max speed so the phone always stays at top speed. If it stays like that for an extended period of time it will damage the phone. The heat can cause the battery to drain really fast and damage the CPU. If you are on any ROM with a custom kernel I would be on the lookout for this.
Sent from my HTC6500LVW using Tapatalk
I was running CM11 on my nexus Galaxy and I thought my battery was bad. My phone would die after a few hours. I got a new battery and it did the same. I installed slim ROM and now I am getting 10+ hours no problem. Also my phone does not feel like it is going to melt.
I have rooted sm n910p with freeza's kernel.
Last week my device sometimes locked it's screen up by itself.
I am using fingerprint to unlock it.
So why does this happen and how to avoid this?
Sent from my SM-N910P using Tapatalk
Try a different kernel if you think its that.
Sent from my 0x1 Note 4...... I love tep
Mine was rooted but I never rooted it again since upgrading to 5.1.1 and suddenly the last few days my phone locks up really bad and has even began power cycling on lock-ups. I've factory reset twice and it does it even without apps installed yet.
I think it's a memory issue. Thankfully it's still under warranty and is going back to Samsung. Hoping they find out whatever's wrong and repair or replace it.
Your issue might be related to root but I think it's coincidental that we both began to see similar lock-ups around the same time.
When did you buy yours? I bought mine October 2014 so I'm at a year now.
touch_rules said:
Mine was rooted but I never rooted it again since upgrading to 5.1.1 and suddenly the last few days my phone locks up really bad and has even began power cycling on lock-ups. I've factory reset twice and it does it even without apps installed yet.
I think it's a memory issue. Thankfully it's still under warranty and is going back to Samsung. Hoping they find out whatever's wrong and repair or replace it.
Your issue might be related to root but I think it's coincidental that we both began to see similar lock-ups around the same time.
When did you buy yours? I bought mine October 2014 so I'm at a year now.
Click to expand...
Click to collapse
Could be battery or shameful ItsOn service tasking resources. I believe you can see if ItsOn is running by viewing the ##DATA# options. Mine is not there anymore to say where it's at.
Maybe OP didn't disable ItsOn? It may not be an issue with the kernels required to have root on OG5; not sure if kernel alone keeps ItsOn from running or trying to run?
True, the memory management can be too aggressive for some vital services while ignoring some that shouldn't run all the time. But that shouldn't be causing lockups or power cycling. Too late to fix Lollipop; I hope they get Marshmallow right.
If OP's lockups are black screen or wake issues, may help that in build.prop with this line added (if it's not there already):
ro.HOME_APP_ADJ=1
You may find reasons to root again, depending on what you find. Best wishes.
Sent from my SM-N910P using Tapatalk
Phone was sold as is, it turned on but the battery was drained completely and died soon after reaching home screen. I took a plunge since price was $50 tempting Washingtons :laugh: I was 100% sure something is wrong with this device but **** it i did it. Bought a charger and USB cable on the way home and so far it's charging just fine.
Phone is mostly erased at least manually I think, because somebody left his google account as I can see email in the plays store menu and some apps, or maybe this is all the carrier pre-installed junk I'm looking at ? LOL
I don't have much experience with Samsung devices but it's a SM-N900T model with N900TUVUCNB4 4.4.2. from February 2014 according to this site http://www.galaxynote3update.com/galaxy-note-3-odin-factory-stock-firmware-usa-canada/
My question is do I stay on this Android or do I jump to Lolipop ? Wasn't there some memory issues with 5.0 ? Or maybe Custom builds ?
Your first move is to sell it to me for $5
If I was OP, I would fully charge the phone, do full factory reset and run it few days as is to test if everything works,. Once you start updating, especially custom ROM, things can break and you'll never know if it's software or hardware. If everything works fine, then you could decide for yourself what to do next. My biggest worry would be the phone is blacklisted, since Note 3 in good shape sells for $200-$300.
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
If you're planning on keeping it, you'd be better spending the extra $ on one of these mate: http://www.amazon.com/Zerolemon-Zer...d=1453047493&sr=1-1&keywords=ZeroLemon+Note+3
I'm getting 6 days on a full charge outta mine, compared to 1 day with stock battery (course I'm running a custom rom, but when I was back on stock with my ZeroLemon, I was getting 3 days outta it)
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
Actually you can root the phone easily, even without tripping knox on kitkat, once rooted you could freeze or kill on start up most apps that bother you, that's what I do and problem solved, phone runs like a dream.
pete4k said:
If I was OP, I would fully charge the phone, do full factory reset and run it few days as is to test if everything works,. Once you start updating, especially custom ROM, things can break and you'll never know if it's software or hardware. If everything works fine, then you could decide for yourself what to do next. My biggest worry would be the phone is blacklisted, since Note 3 in good shape sells for $200-$300.
Click to expand...
Click to collapse
There is actually an easy way to not worry about the blacklisted issue before you ever buy a phone from someone. You can go to www.swappa.com/esn and check the status of the phone by entering it's IMEI. We buy and resell phones a lot and this is how we check them. You can check up to 10 phones free every 24 hours on the site.
4xxxxL said:
OK
Phone charged fully I booted it up and after short amount of time it would freeze constantly when bringing up the keyboard (Samsung or google), can't recall which one was first now because I was changing them in settings and nothing helped. Either way it was freezing after typing couple of letters or appear then crash/disappear. All this combined with some crashes from app called Lookout. Google told me to do Volume UP+HOME+POWER and do a factory reset, after that everything works fine now. Changed my sim card and I can place calls with no issues also data works fine but damn there is tons of f***ing poopy preloaded apps in here from Samsung and other garbagio . I think whoever was using this device had no idea what to do with those errors and just stopped using it somewhere around Feb. 2014 because since then basically nothing was updated on it. I'm gonna let it sit for couple of days then probably will upgrade to 5.0 via KIES and maybe replace the battery either way with OEM or maybe something like this ? http://www.amazon.com/Anker-T-Mobile-Compatibility-18-Month-Warranty/dp/B00FF54C8Q/
Click to expand...
Click to collapse
Sounds like you did get lucky and come across someone who wasn't tech savvy at all, and had no idea how simple it was to fix. But hey... that's their lose and your gain.
If you do decide to root it at some point and want to run a custom ROM, click on the top banner in my signature and check it out. I think you might just like it.
kevp75 said:
If you're planning on keeping it, you'd be better spending the extra $ on one of these mate: http://www.amazon.com/Zerolemon-Zer...d=1453047493&sr=1-1&keywords=ZeroLemon+Note+3
I'm getting 6 days on a full charge outta mine, compared to 1 day with stock battery (course I'm running a custom rom, but when I was back on stock with my ZeroLemon, I was getting 3 days outta it)
Click to expand...
Click to collapse
Yeah man, there is an awesome custom ROM out for this phone. I can't remember the name right off hand, but I'm sure you've heard of it. Haha
pete4k said:
Actually you can root the phone easily, even without tripping knox on kitkat, once rooted you could freeze or kill on start up most apps that bother you, that's what I do and problem solved, phone runs like a dream.
Click to expand...
Click to collapse
You can freeze them, but in my opinion if you've gone to the trouble of rooting it, you might as well completely remove the bloatware. If all you do is freeze the apps, they are still there needlessly taking up the internal storage. There are a few lists on here that tells what is safe to remove without fear of messing the phone up.
problem with deleting "bloatware" is two fold: some programs are interdependent and deleting one you don't want may break another you need. Also, I don't know about others, but I changed my mind in the past and reactivated some applications I never thought I'll be using before.
As far as space goes, the whole system uses 4 GB maybe, so you could save 1 GB, if you're aggressive deleting files, probably couple min of 4k video worth. I got 128 GB sd card, problem solved. Maybe different story with Note 5, but that's one of main reasons I never upgraded.
Either way I strongly suggest at least freezing apps and testing before deleting it.
TimboMachimbo said:
Your first move is to sell it to me for $5
Click to expand...
Click to collapse
Lmao
Still been using the device to watch stuff on wifi @ home and **** Can't use it as my daily driver it's just to big :0 anyway the other hidden issue that I found out about it is that the charging port is kinda beaten up especially on the left side. Sometimes you can plug the cable in and it won't charge until you apply little pressure on the connectors left side it's time to do this http://www.amazon.com/Charging-Ribbon-Connector-Samsung-T-Mobile/dp/B00H3DZRXC/
Alliance Rom
4xxxxL said:
Phone was sold as is, it turned on but the battery was drained completely and died soon after reaching home screen. I took a plunge since price was $50 tempting Washingtons :laugh: I was 100% sure something is wrong with this device but **** it i did it. Bought a charger and USB cable on the way home and so far it's charging just fine.
Phone is mostly erased at least manually I think, because somebody left his google account as I can see email in the plays store menu and some apps, or maybe this is all the carrier pre-installed junk I'm looking at ? LOL
I don't have much experience with Samsung devices but it's a SM-N900T model with N900TUVUCNB4 4.4.2. from February 2014 according to this site http://www.galaxynote3update.com/galaxy-note-3-odin-factory-stock-firmware-usa-canada/
My question is do I stay on this Android or do I jump to Lolipop ? Wasn't there some memory issues with 5.0 ? Or maybe Custom builds ?
Click to expand...
Click to collapse
Flash Alliance 5.0 Lollipop ...best rom for note 3
http://forum.xda-developers.com/not...-alliancerom-n900t-uvufob6-v1-online-t3055309
Replaced the charging port with the $5 one I bought via Amazon... charging worked great but the voice recording and mic in general sounded garbled had to put the broken one back lol :S
Okay, so I have no idea what is wrong with my att note 4.This thing has always been kept in an otterrbox.It has been kept in perfect condition until an ota forced its self upon the phone. After that it started acting weird. Reboots, freezes, black screens, and sometimes something would get corrupted and the phone wouldn't boot at all. Sometimes the phone would make a constant buzzer or it would go straight to recovery but say sbl1 partition doesn't exist. Flashing stock worked for a while, but the problems would come back shortly and have gotten much worse.I just bought a brand new battery fully charged it and flashed stock 5.0, 5.1, 6.0. It doesn't matter i have tried it with the pit, without the pit same things happen. I have tried both batteries, fresh wipes, different firmware's, and now I can't even get it to boot at all no matter what I Try.
What do you guys think my problem could be i have no idea what it could be
I WOULD APPRECIATE ANY HELP
Same Issue
Hello,
After the marshmallow update I am facing the same. but i kept it running by downloading wakelock app from playstore . It somehow helps I am not sure the reason. Please select PARTIAL_WAKE_LOCK option once you download.
Try to not to shut down the phone because of any reason.
I hope this helps! and do let me know if it does.
my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone
jammer8 said:
my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone
Click to expand...
Click to collapse
I have read many sources available online. These updates sometime is not compatible with our phones. In case of note 4, certain model's CPU faces shutdown trouble due to update the moment we lock the screen or in standby mode. To keep them running there are apps like wakelock. Download that and select option Partial_wake_lock. This will help a bit hopefully. Worked for me. But this isn't a permanent solution.
Apologies in advance if my terminologies aren't correct or the solution doesn't work.