yashsingh1/xdaforums huggingface dataset:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
I'm loving this interaction/problem solving. If you guys get your issues fixed and want to help a nearly desperate woman, I could be your new problem.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Might be able to help out!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Been thinking about your case issue for a while and had a random epiphany. To open, I've been having snags again. Remember, they never occurred on stock EPG2. I was smooth sailing. Installed OvrDriVE's ROM w/ root, SuperSU, Xposed, and all my usual apps... I got all happy and resumed my normal life. Now I get hangs, occasional freezes. Two things I do run are Greenify and Amplify (Xposed modules). Greenify more-or-less acts like the SmartManager app in stock EPG2. Just kills apps that you haven't used for a certain amount of time. Amplify, in case you've never dabbled with it, is much more aggressive. It stops alarms, wakelocks, processes, all sorts of stuff that's beyond my level of understanding. I use it because it claims to improve battery life. Many concur. But what if it's TOO aggressive?

It makes sense because I mentioned that I wake up in the morning, turn on my phone, open Facebook, scroll my feed really fast (since no one there's very interesting) and I get a hang. Why would a cold phone, coming out of a deep sleep, hang? Must have something to do with it having been in a deep sleep and not ready to 'handle' the data/processes/CPU load, et al. This also happens when I pull my phone out of my pocket after not messing with it for 10-15 minutes. First app I run... hang.

I still can't explain the random reboots or boots into ODIN with mmc_read failed... but I just have a feeling that you and I have the same issue caused by different culprits. I'll observe and report.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Interesting observations. I agree that we're experiencing similar problems. Finding the cause, though, is driving me insane.

My earlier statement about thinking the problem had to do with the cover is incorrect. I'm now experiencing lags and hangs even with the normal back.

During our conversation the past few days, I've flashed and reflashed half a dozen times. And it's always the same: the phone behaves fine for the couple hours I spend setting everything back up. But then once it goes to sleep, it hangs. And thus begins yet another series of hang-while-sleeping and mmc_read errors when I boot. And I can never actually power off/on the phone normally; it always requires a battery pull to get things moving again.

Like you, I stopped using Greenify, thinking it might be the culprit. Nope. I've also tried a few things to keep the phone from deep sleeping. That logcat I mentioned previously is one; another is using the Wake Lock app from the store. Neither one really helps. Eventually, after half a day or so, the phone becomes completely unresponsive.

I'm resigning myself to the only thing that makes sense: a hardware failure of some kind. I'm half tempted to buy another battery, given the behavior difference I'm seeing in the two that I already have. Maybe, just maybe, I can rescue this thing with a $40 fix. If not, it's apparently time for me to shell out hundreds for another phone, long before I actually want to.

I'm headed down to Australia for a few days -- speaking at a conference. I'm currently using an old Nexus 5 that I found in my technology gadget junk drawer. Boarding the plane in a couple hours. I'll continue to check here to see what reports you have.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Safe travels, man! Completely jealous of you as I have so many friends in Australia and haven't yet been.

I'm considering another battery right now. Mine hits a certain point then trickle charges. It hit 82%. I tested this theory. Turned the phone completely off and plugged it into the wall. 15 minutes later, still on 82%. I think the battery is definitely shot. Kinda strange that it happened all of a sudden like this. I'm still thinking deep sleep is the issue. Testing one portion of this at a time. It'll be time-consuming, but hopefully i'll be able to pinpoint exactly when the phone hangs and under what circumstances. Check and make sure you don't have SmartManager or another app built into Android that's also killing apps after a certain amount of time.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Hello from 28,000 feet...blows my mind that I can write to you from over the friggin" Pacific Ocean!

When I saw where that supposedly "Smart"manager came from, I disabled it immediately. Samsung kicks ass with hardware but really sucks ass with software, ya know?

Anyway. I don't have anything to add here at the moment, just wanted to gush on some oceanic wifi, lol.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] DaKillaz98:
Hey, I don't mean to jack your guy's convo', but I have also had similar speculation to you guys about the Note 4 issues.

I would like to start with the battery issues. I bought a new OEM battery from Amazon and placed it in my Note 4, but it continued with the same issues. But, I have absolutely NO issues on EPG2 Stock, at all. It is only when I try other TouchWiz ROM's, I even tried CyanogenMod Verizon builds that were verified working on the T-Mobile Note 4, and I still had no reboot issues. As soon as I try other TouchWiz ROM's, BAM!, my phone flips everywhere and will reboot.

I believe the TW ROM's I tried though were on the EPE2 Base which caused the issues. So far from my testing, the issues come from either mismatching BL and Rom images or maybe (Voltage). I say voltage because these problems generally happen when the phone has been able to enter deep sleep mode, meaning, maybe the CPU has an issue ramping up, or the stock voltages aren't right for the chip and need to be raised/lowered. That is just my speculation and I thought it might interest you.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Suzano-Sho:
This isn't an isolated problem either...

It seems to be happening for everyone using a custom ROM based on the MM update here. Some are attributing the problem to the kernel but any other kernel seems to produce the same problems (occasional lag, frequent random reboots, frequent overheating)...I had just come here to wonder why the issue wasn't being discussed a little more in-depth...
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
This is my story of woe. Note 4, T-mobile N910 T. Bought used, no problems, was rooted, but no custom rom. When lollipop came out, I realized I wasn't going to get the upgrade without unrooting. I was able to go back to stock and got the lollipop update, no problems. I never did bother to root again, and was ok with regular. Then MM came out. Suddenly all kinds of issues, lag, freezes, reboots for no reason. So I thought, ok, let me root it and put on a custom rom. I used Odin and tried to get TWRP but couldn't get that far, I almost had the phone bricked. I managed to get the stock t mobile MM rom back on (I tried to get back to lollipop and was having errors, then realized it wouldn't let me downgrade. So now I have it running stock, same problems and I have tried clearing everything, not putting any programs on besides what are there. I have 2 batteries, same thing happen with either. I also have the s view case, so I had some hope that was it, but I see that has been determined not to be the issue. Every time I think it is going to be ok and try to get it set up, it just randomly shuts off. sometimes it goes back into the screen that says downloading do not turn off target (even though it isn't plugged into anything). I am so bummed. I have actually seen a few note 4's on sale on ebay being sold 'as is' with the same problems being described. 'random restarts, lag, slow'. It seems to be several of us. I am willing to try just about anything. If someone has a link to downgrade to lollipop, I would be willing to let my phone be the guinea pig. :(
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] DaKillaz98:
Legit, the same exact thing happened to me. I purchased my phone used off of Swappa listed as fully functional. I never really got an opportunity to see how the stock rom performed however as I jumped on the twrp train immediately and was off on custom roms. That is when the weird stuff happened. Although, from what it seems with being unable to downgrade, you must have taken the EPG2 update which modifies security policies only allowing downgrades as low as DOK2. I would also like to state that if anyone has an experimental fix that may worry for bricking, my phone can be a guinea pig as well, getting a new one soon. Just hoped it wouldn't be THIS quick that I had to replace this phone.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Wow, some very interesting testimonials now. I appreciate all of you chiming in. Although my issues are less now, they are still existent, mainly right after I turn on my screen and open an app really quickly. I think that today I'll go back stock EPG2 for a couple days and use my phone very heavily just to confirm that it's the problem. My battery still won't charge beyond about 82%, even letting it sit on AC for two hours. I was going to purchase a couple Anker batteries this week, hoping that would fix it, but after reading a couple of these posts, I will hold off and test the software side of things first.

It just makes no sense why everyone else in the thread of the ROM that I use... uses the same phone, same base(s), same kernel(s), but their devices seem to be running fine. There must be a difference somewhere.

ODIN'd stock EPE3. Strangely, every time I do this, I get a random reboot when initially going through setup. Then when it's restoring all my apps, I get another random reboot. This causes my phone to go completely dark. Only way to get it back is to do a battery pull. Then I boot and things are fine on stock MM. My battery has easily charged back to 100% now.

I spoke too soon. Occasional random reboots on stock EPE3... and also hangs/freezes, sometimes it hangs for 20-30 seconds, goes dark... then all of a sudden it's back. It always seems to happen right after I turn the screen back on. I'm going to leave the screen always on, low brightness, and see if it still occurs. I don't want to drop $35 on new batteries just to still have issues that I haven't yet been able to narrow down...
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
Okay guys, from reading other threads where someone recommended downloading the app wake lock and setting it to partial wake. I did it because...well, why not? and I have not had any freezes or reboots since. So..if this is truly working and so far so good, why??? What would this app be affecting and how?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
It's much in line with what SteveRiley and I have been discussing concerning his phone case and my Amplify app possibly triggering a deep sleep and the phone having a difficult time "waking up" from it. These freezes/reboots/episodes of instability usually happen when 1) I have just turned my screen on (hang/hang-reboot), or 2) when the phone screen is off and the device starts to do something, like download an app (random reboot).

As far as how... that's a bit over my head so I'm not sure. I still suspect battery issues, maybe not supplying enough voltage when it suddenly needs to. Thanks for the tip. If (when) it happens again, I will try that app to see what difference it makes for me.

My phone randomly began charging to 100% yesterday and have had no issues in the last 18 hours or so. Haven't really changed anything except restored my ROM. Seems hit-or-miss with these problems.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
Yes, so far still haven't had an issue. Try it if you start having issues and we can worry about the "why" later.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
After I just had a hang/reboot, I downloaded the app and started it on the wakelock level 2, FULL_WIFI. I'll increase the aggressiveness if/as I have further issues. Strangely enough, right after I started the wakelock on the app, I put my phone on the charger, came back a few minutes later, and the 77% had become 100%. Not sure what happened.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Update. When I returned home yesterday I installed the wake lock app. It's been running in partial_wake_lock for about 36 hours and I haven't had a single lag or reboot. A CPU monitor shows that the phone idles at 300 MHz and never deep sleeps. Battery life is certainly lower, of course.

I'm still thinking there's an underlying hardware problem.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Agree. Have had MUCH better results, albeit shorter battery life, with the Wake Lock app. Rarely any freezes. However, last night laying in bed playing on my phone... the screen blips and phone shuts off. Probably the scariest one I've experienced. Pulled the case, pulled the battery, nothing. I seriously thought my phone was a brick. Kept the battery out for about 30-45 sec and put it back in... finally got it to power back on. All has been fine since then.

Definitely a hardware issue somewhere.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] andyr1982:
Finally............got it fixed!!!

i thought it was hardware issue/problem too.... and it seem so many people have the same problem with us.... after they upgrade their android os from 5.11 to 6.0.1 (stock or custom rom/custom kernel)

follow this thread to fix your phone( all credit is for him) dont forget to thanks him if you fixed yours

http://xdaforums.com/showpost.php?p=66879466&postcount=10
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
So yours is good to go after following this guide? And also, are you able to upgrade back to MM? Or do you have to stay on 5.1.1 with DOK2 forever?

Thanks for the guide, I will try this later today. :good:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] TheROMGuy:
I changed out my battery for a new one and haven't had the problem since. still testing, but I've loaded the phone down and it stil performs well. May not be in all cases but in mine changing the battery worked.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] andyr1982:
Yess....everything is back to normal now. (no more: pull battery,emmc errorl,random reboot,freeze,etc at lease not yet) after you boot up LP stock rom and connected to internet it will automatically downloaded MM stock rom and ask you to upgrade it. but i will stay with LP for now... i want to make sure this is sofware related issue not hardware. beside i see alot of people having issue after upgrading to MM.

good luck everybody......hope you guys fix it tooo :good::good::good:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I still can't shake the suspicion of a bad battery. I've been thinking this for a while. The Wake Lock app to keep the CPU running is working, so I didn't order Anker batteries this week like I planned, because I figured it was some internal issue. However, the phone is only accepting than 500mA on a standard wall charger, only getting 6-700 when I plug into my car charger (which is rated 2.1a and always has given me a lightning fast charge.)

I'm going to try the DOK2 guide tonight, just because... but I'll keep a TWRP backup just in case. If I have any blips after that, I'll go for new batteries. Cheers
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Attempted to use the guide, but the process stopped before it started. Failed. Getting the "SECURE CHECK FAIL : PIT" message on my phone in download mode and it won't go any further. I'm not sure if it has to do with the fact that I"m trying to downgrade from EPG2 to DOK2 ... (which I didn't think was easily done...) but I've tried several times on a couple versions of ODIN and no luck so far. Researched the issue a bit but no solution to this error yet.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] andyr1982:
Try again...but skip the pit part...so just load the rom in pda
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Such a mess. Now I'm getting "flash write failure" in download mode and I can't ODIN any firmware... tried DOK2, I even tried installing TWRP then going in and wiping everything, then flashing EPG2 again... same flash write failure. Absolutely nothing will take.

By the way... the DOK2 passed the first time... I rebooted as instructed. It did the system update, and then restarted itself... and went to the green Android screen (again) and the gear just kept spinning. Never did anything, never booted up.

UPDATE: Alright, DOK2 worked fine, used the guide. All is well with that. However, I rebooted into download mode and the first thing I see is "mmc_read failed" so clearly that issue was not fixed. But to be fair, I didn't re-partition (since I kept getting ODIN failure while doing that). But the downgrade to DOK2 was successful. I'm going to go back to MM and see if the issues recur. If so, back to DOK2 it is and I guess I'll stay there.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Wow. Sounds serious. So...will you buy another Samsung device?

My phone remains almoat trouble-free so long as I keep that wake lock app running. But whenever I power the phone down, it'll take multiple restart attempts (with a battery pull) to get past an mmc_read fail. My spidey sense says we're all experiencing intermittent hardware issues with a thermal aspect. As if when components heat up, electrical contacts get flaky.

I've seen some other threads with more drastic suggestions. Enabling the "NAND wipe all" when flashing a .pit file is one. Another is booting off an SD card and flashing from there. I might try these for the hell of it.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Yeah this issue seems to happen a lot with Note 3 and Note 4. I'm sure I'll stick with Samsung though. Going to talk to T-Mo to see if they're willing to do anything for me. Sprint helps out even after warranty is over so T-Mo might do the same. They told me I have to call tho.

Anyway, yeah but I believe in cause and effect... and these issues didn't start to happen until I upgraded to a Marshmallow ROM at the beginning of July. Before that, all was well. The battery thing is still possible too... going to replace them if I keep having issues with MM. Worth a shot.

Been working on this for the past few hours. Still no luck getting the PIT file in ODIN to work, so only ROM flashing.

--DOK2 is hit-or-miss with the PASS or FAIL in ODIN. I got it to work again. Installing OvrDriVE's DOK2 ROM since I'm on that BB/BL anyway... and I'm experiencing the next symptom that I've read about... and that's normal restarts not working. They all seem to lead to mmc_read failed ... or it hangs on the initial Samsung screen and then goes black after a minute and I have to do a long battery pull to get it to boot.

So all in all, my issues with booting are much worse, but so far, this DOK2 ROM is snappy, no issues within Android. I'll see how it goes today.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
I'll keep an eye on this thread trying to find out how you progress. No problems with the wake lock, but in the interim I had ordered a used Nexus 6. So, I am trying it out, but missing my note 4. If I hadn't ordered this other one, I would not have even tried to change after the wake lock app, but...when I ordered it off ebay, I hadn't been able to find any solution and had to pull the battery several times a day. Do you think note 4 will get Nougat and if so, is there hope this would fix this issue for us? :(
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I honestly doubt Note 4 will ever see a Samsung stock Nougat firmware. It took us 18 months just to get Marshmallow. Surely we'll see some ROMs pop up with the Nougat features but they'll probably be on a MM base.

Again, I believe in cause an effect so I'm having a really difficult time trying to admit a hardware failure. This didn't happen until I installed a ROM that was EPE3 or EPG2 base. On 5.1.1, up until early July when I switched, everything was fine. No reason that a hardware failure would suddenly happen.

I'm thinking battery, again. Going to order Anker batteries this week. Still, within Android, OvrDriVE's DOK2 5.1.1 ROM is snappy and smooth, minor issues but nothing like before. Deep sleep works just fine. But sometimes I get random reboots, especially after I've just rebooted. Earlier I had to fight just to get it past the Android screen. Just seems like a power problem to me. At least after I try a new battery, I'll be able to narrow it down to something internal. The only thing software-related I haven't done yet is re-partition.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
I wanted to experiment whether my SIM card might be a contributor. I disabled the wake lock app autostart and powered down the phone, removed the card, and then tried to power up the phone. I experienced two mmc_read failed errors, and then on the third try the phone booted into TWRP. Eh? I told TWRP to reboot system and it said there was no operating system installed. Double eh? But surely there must be, because I can mount /system and see its contents. I booted into download mode and Odin'd just the bootloader and modem files. I let the phone boot, which happened without incident, and also re-attached the S View cover. So far, I've just let the phone sit for about 24 minutes. 20 of those minutes the phone has been sleeping! Now I will exercise it as much as I can, over wi-fi of course.

Could bad SIM cards cause these kinds of weird behaviors we've all been seeing?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Interesting experiment. I highly doubt it's SIM-related though; it would be way too coincidental in my case since the issues only happened when I upgraded to Android 6.x -- To me, it makes sense to have mmc_read failed errors... then it booted itself into TWRP. No mmc_read on that one, but "No OS"... perhaps it wasn't detecting the files needed to boot the OS so it just booted itself into TWRP (software error rather than hardware.) I'm just spitballing here... Windows does the same thing. Can't boot the OS so it halts at BIOS.

Glad you got it booted though. We'll see what happens. 10½ hours of uptime for me, no restarts. Again, it seems like the random restarts happen *right* after I boot Android... but once I'm in, smooth sailing. Haven't used my phone a ton today, but I'll exercise it, as you said. Just ordered my 2 Anker batteries so on Tuesday, I'll definitely have a yea or nay on whether a new battery offers a fix.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
After letting the phone sit for another half hour, it became quite laggy and eventually rebooted. So yeah, not a SIM card issue.

Curiously, the lockscreen reverted to the default wallpaper (but only the lockscreen). I also noticed that a number of settings reverted to their defaults. Not all, just some.

This thing is a real mystery!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] grizzylemon:
There are too many of us who had this happen after the new updates. I have two different batteries, one newer than the other, but would be interested to see if the anker battery removes/reduces the problem. When I went to Tmobile to get the sim card changed for size, I asked the guy if he had a lot of complaints on the note 4 after the update, of course, he said "no" and then he said, well, he has had to do a lot of replacements for phones still under warranty. Double talk, as usual.