yashsingh1/xdaforums huggingface dataset:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
I've encountered the same issue here, with stock EPG2 and also the dev-base 6.0.1 build flashed with TWRP. Seems like it's happening to a lot of folks.

Thing is, the other day I downgraded to DOK2 and installed Mega's PopRocks5V4XxXZ build of 5.1.1 and while the problem isn't as bad as any 6.0.1 ROM, I'm still experiencing long lags and occasional reboots.

I have not experimented going without root. I'm not seeing any battery issues. I don't use Xposed.

I'm thinking that it's time to try repartitioning with the PIT file. I really don't want to give up root -- I hate seeing all the bloat in stock ROMs and I need root to make the junk go away :)
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
The battery just seemed normal charging to 80s and then I kept checking my phone and noticing it hadn't really gone anywhere. I just took a 3-hour nap and woke up and it was on 100%. So although slow (not sure how slow), it did reach 100 finally, so that's good.

My issues are still nonexistent with stock. I'm going to cf-autoroot here in a while and keep testing. Then add Xposed and test again to see what may be causing the issues. Perhaps I'll try a CM ROM as well, since the two ROMs I mentioned above are from the same base. Maybe I'll downgrade too. I was a big fan of Mega's ROMs on LP and KK.

I agree, a repartition would confirm it's probably a software issue. Haven't seen the mmc_read message in a while now.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
My mmc_read errors have also disappeared.

I just noticed something -- in "About Device," my baseband is DOK2. Which is, in fact, the baseband and bootloader I flashed. However, Mega's ROM shows DOG1. I wonder if I should flash that baseband and bootloader?

I'm also kinda curious if EPE3 exhibits the same problems that EPG2 has.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Hmm, yeah if you're still having issues, I'd say matching them up is a good place to start.

I just went to flash TWRP (for some reason, I guess it didn't take on the first go) and got the mmc_read. Rebooted back into download mode and it was fine. Flashed SuperSU and now EPG2 is still running great. Figuring out what else to do from here.

EPG2 was reportedly just a security update to EPE3 so, I'm not sure. EPG2 is really smooth for me now, still, with root... but one of the devs noticed quite a few issues once he based his ROM on it, so he went back to EPE3.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
In my experiences, the lagginess and reboots didn't occur immediately. I could get through my usual routine of going through settings, installing my apps, and deleting the bloat all with extreme smoothness. The problems would begin appearing after I put down the phone for an hour or so.

In all my years of messing around with Android (started with a G1 in 2009), I've never seen anything like this. Makes me suspicious of Samsung.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Suspicious is right because none of this software chaos began to happen until the official Marshmallow firmware was released. It seems mmc_read has been around for almost 2 years though.

I keep swiping like crazy, opening apps as fast as I can, trying to put a load on the CPU to see if it will give me any issues... but, nothing. If no issues by the end of the night, I'm going to flash a random CM ROM and see what happens inside that environment.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Have you tried a lot of data traffic, like more Facebook?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Sure have. That's what always triggered the hangs/freezes on OvrDriVE's EPG2 and EPE3-based ROMs. Now, no problem at all. Instagram pulls even more data than Facebook and even that's smooth. I've been scrolling both apps really fast and not one problem.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
I just noticed this from your post #5.

So you're rooted this time, and everything's behaving normally? What's different from the previous time when you were getting all the lags and reboots then?

EDIT: Nevermind. The difference is you Odin'd stock, whereas before you were on OvrDriVE's ROM. See, I've had these strange problems even when I Odin'd stock.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Rooted and all is well in the world. The difference is that I'm running a straight stock EPG2 firmware. I've been running OvrDriVE's Marshmallow ROMs and have also tried Note4UXEdge ROM. Again, I believe they are created from the same base. That's when the issues were happening. I kept blaming the kernel... but I switched from BeastMode to Xceed, same problems. Haven't tried AEL or Emotion though.

The next test will be to flash a ROM that I know isn't affiliated or related to either of the above 2. I'll see if I get the issues... then I'll know it's likely ROM or kernel related. However, others in OvrDriVE's thread aren't getting these issues... so it's really frustrating because he can't help. There's no hard evidence that it's the ROM's fault...
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Which version of Odin are you using?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
3.09 ... but prior to that, I was using 3.11.1, the newest release. I've never understood why some people use (and recommend) older versions of ODIN. Seems like they function differently or something?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Take a look at this:

http://xdaforums.com/note-4-tmobile/help/csc-folder-stock-mm-t3437091

First time I tried flashing stock MM, I used 3.09. You'll note that my result was a missing /system/csc folder and was experiencing several flash failures. The lack of a /system/csc folder meant that some T-Mobile specific functionality was missing. Another XDA member suggested that Odin 3.09 wasn't aware of the file cache.img.ext4 and suggested I try 3.11.1 Also had some flash failures, but this time cache.img.ext4 flashed fine and I had the /system/csc folder.

Do you have this folder on your phone?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I do have /system/csc ... I see customer.xml and sales_code.dat in there so I assume it's definitely related to something T-Mo specific.

This stock ROM was flashed with 3.09... so maybe I should try flashing a clean copy of OvrDrive's ROM with a different version of Odin. He recommends 3.11.1 on his ROM OP though. I'm just not sure what I used previously... might end up being trial and error here.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Now that's a real mystery! Why were you getting a /system/csc with 3.09, and I wasn't?????
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Not sure. With this stock ROM, I didn't wipe internal storage but I definitely wiped data and system x5, so if any CSC folder existed prior to, it should have been gone before the ROM installed.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Well, I'm gonna take the plunge and try 3.09. I always wipe internal storage. Nothing there I need to keep -- music and photos are on an SD card.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I'll keep you updated. I'll flash the ROM on a couple different versions of ODIN and see if that's the culprit. I'll also try another ROM. Just doesn't make sense why this stock ROM is so smooth, but I guess that's a good sign.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Have you debloated anything yet? I use SD Maid (or sometimes Titanium Backup) and remove some stuff:

Google and Youtube and Amazon and Dropbox and others I can download from the store (they just clutter the ROM when they get updated anyway)

the Facebook apps (I don't use it)

Milk

non-English fonts

Allshare and nearby devices bits
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I haven't yet. I use to use BloatFree but now I just use ROMs that come debloated out of the box, so I never have to worry about it. I just disable Hangouts, Google App, and the other stuff I'll never use.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I was just thinking... in my case, ODIN version shouldn't matter. I ODIN the stock ROM to update the BB and BL. Then I boot TWRP and wipe clean x3. Then I flash the ROM from extSD... so I actually don't use ODIN through any of the process of installing the ROM. Either my phone doesn't like the ROM or the kernel, it seems. About to try OvrDriVE's ROM again right now.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Hm, then that's why you've been getting the /system/csc directory.

So I just finished flashing the full EPE3 stock ROM using Odin 3.09 -- and, this time, it looks like Odin read the cache.img.ext4 file. Setting up the ROM now. When I install a file manager, I'll check for that directory. I'm not going to root just yet.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I mean, nothing has changed from my previous reply though. I was running stock Samsung EPG2 firmware, which I ODIN'd with 3.09... and I had the /system/csc at that point. Whether I have it with a modified stock ROM, I'm not sure yet.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Nope, no /system/csc. I'm gonna try Odin 3.10.7. I feel like I'm just shooting in the dark.

Also had an mmc_fail message once when I tried to boot into download mode. I'm wondering if my phone is dying.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
But are you sure that /system/csc directory is related to the issue? Every time I install a ROM, I'll keep an eye out and see when I do/don't have it.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
If I set up the phone without that directory, then I'm missing the things that CSC does when it sets up the phone. Obvious examples include no alternate symbols on the keyboard (a CSC enables that) and the presence of Bluetooth tethering (some other CSC setting disables that, I think it's a T-Mobile thing).

When I didn't realize this was missing after my first attempt at flashing MM a few days ago, the phone was performing abysmally -- it would stutter and lag every 5 seconds or so. When I learned that I needed to use a newer version of Odin to get that directory, the phone's performance was better -- but not trouble-free.

Great -- the flash just failed again. There's a "write error" on the phone's screen. I think my phone is toast, or slowly becoming toast.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Yeah, maybe try that PIT re-partition? Also if you're running ODIN, make sure your USB cable is a good one, change ports as well. I've had flashes fail due to a USB that was cheap or too lengthy.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Uh, so I just saw something new.

Every single time I've flashed, I've followed this procedure:

1. Boot TWRP. Wipe everything except external SD card

2. Boot download mode. Start Odin. Uncheck the auto-reboot option. Flash the complete stock ROM

3. Pull battery to exit download mode

4. Boot download mode. Start Odin. Flash TWRP

5. Boot normally

But this most recent time, I forgot to do what I put in italics in step 2. When the ROM finished flashing, the phone rebooted. I just let it go to see what happened. The little Android dude appeared with a message indicating that it's installing an update. I've never seen this before! Aaaaand... I have a /system/csc directory now.

I'm going to make a supposition here. You apparently need to actually let the phone reboot after flashing the complete stock ROM before doing anything else, because it's this process that creates the /system/csc folder. I bet if I would have done this with Odin 3.09, I'd have seen the same behavior. I'm not actually going to test that, though -- I'm getting tired of messing around with this stuff.

I'm going to proceed with setting up my apps to see how the phone performs.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Very interesting. I always have auto-reboot checked and always see the little Android with the gear spinning and "Installing System Update" as you indicated. I always let it completely boot (and usually rest for a few) before I restart and ODIN TWRP, change kernel, install any fixes, etc.

Restoring my 80 apps now on OvrDriVE's 6.0.1 ROM and after it calms down, I'm going to start swiping like a madman to see if it hangs/freezes.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
So I think this extra step I accidentally performed is actually pretty important. Not only do I see all CSC-related stuff, but I could actually enable private mode this time. It always worked with 5.x ROMs, but never worked with any kind of 6.x ROM previously.

I'm going to flash TWRP then root the thing. I gotta get rid of all that bloat, lol.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
So how's it going with you? Everything is looking really good here for me. I can't believe I've pissed away so many hours over that dumb little misunderstanding I had about not auto-rebooting!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
While we're on the subject of misunderstandings and wasted hours of our lives... check this out. In mega's LP and KK ROMs, I always had a habit of disabling Google apps I don't use. G+, Hangouts, Books, Newsstand, Music, etc. Every time I installed OvrDriVE's MM ROM (from the beginning), I only saw Hangouts. None of the others.. not even G+. I didn't think anything of it. Who cares, right? Maybe those system apps just weren't included?

So I re-downloaded the entire ROM. (He hasn't changed anything on it.) I wiped clean x3, flashed it from extSD. All of a sudden, I see the GAPPS. All of them as I'm used to seeing. Everything works fine. When I was restoring the 80 apps from Play Store, my phone did randomly turn off. Short vibration, screen off. Couldn't do anything. I unplugged from AC and the LED indicator stayed on... totally frozen. Had to do a battery pull. It went into download mode and gave me mmc_read failed. But I rebooted again, it continued the restore... and everything has been fine. Not a lag, hang, freeze, or blip yet. His ROM is running as it's supposed to on BeastMode kernel even.

Absolutely strange. I may ask OvrDriVE if he has any insight as to what happened. It's almost as if I've been installing this "incomplete" or corrupted base ROM that just happened to only be missing GAPPS... or it's corrupt on the androidfilehost server I downloaded it from. To be fair, I don't check my MD5 checksums... and perhaps I should start. I'm not out of the woods yet with this mmc_read error... but as for now, the ROM is nice and smooth!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
This has not only been a therapeutic conversation with you but an educational one as well, for both of us! We each learned something new.

Now about that mmc_read error -- do you happen to have another Note 4 battery lying around? I have two of them. I've noticed this evening (probably might have noticed before, but really didn't give much thought) that I see memory-related errors with one of my batteries but not the other. Read errors, write errors, "can't read partition" errors, even one ultra-scary error saying a partition didn't exist!

Hard to believe that a friggin' battery would be the cause of that, but it seems to be a pattern here.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Indeed, always easier to get new ideas without being in a thread full of 100 people spouting off myriad questions while a dev pulls his hair out trying to answer them all and fend off the dumb ones.

I don't have another battery but I think it's about time to get one. I've needed a spare for a while and since this one is almost 2 years old, it can't hurt. I'll see if this error recurs again during normal usage and then once I replace the battery, I'll see if it goes away for good. Thanks for the tip! Glad we're both up and running smoothly.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
This is what I have: https://www.amazon.com/dp/B00NQG2XNC. The charger case is pretty convenient. I keep one battery in there and plugged in so that it's always topped up, ready to go.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
I'm rarely away from a charger for long periods of time but for concerts and stuff, something like this should be good. Also been looking at ZeroLemon. A lot of people seem to enjoy them as well. If power is cutting out or not supplying adequate voltage or anything like that, I expect that the hardware could throw such an error. It can be temperamental to power changes just like a PC. Maybe all those people who sent their Notes back just needed a new battery. Interesting notion.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Had some issues trying to flash Magisk and Xposed so I ended up re-flashing the ROM again last night. Still, nice smooth setup. Just ONE "blackout" (again) whilst it was restoring. Had to do a battery pull. Then it booted to mmc_read again. Something is causing that when the ROM is setting up and I can't put my finger on it.

At any rate, forget all the business about GAPPS. I think what happened is that... during my time talking to you, I was using a stock EPG2 ROM long enough for it to sync with my Google account. the stock rom comes bloated with all those GAPPS I mentioned. So when I installed this new ROM, Google Play automatically redownloaded them. OvrDriVE's ROM doesn't ship bloated with them. Haha... for now, I'll just chalk this up to a bad download of the ROM.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Sounds like you've made progress, cool. Wish I could say the same. More freezes and reboots today. I'm flummoxed!
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Which ROM did you ODIN exactly? and is it stock?
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
The stock .tar image DeeXii posted:

http://xdaforums.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018

Thing is, sitting here at home with the phone connected to a USB port and running logcat, I can't seem to cause the malfunction. But I've had periodic lag issues all day and pulled the battery like four times.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Maybe try a re-download of the other firmware? Either PE3 or PG2, whichever you haven't tried? Could be your issue kinda like it was mine. I'd start from scratch and re-partition then ODIN the firmware... just as brand new and clean as possible. If you still have issues pure stock, you know it's a hardware malfunction...
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Yeah, sounds like it's time to bring in the nukes. Never done a repartition, will research. And I'll try EPE3 this time, let's see what the difference is.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
GRRRRRRRRR! I want to break something! You'll never believe what I found out.

So last night I tried once more, as thoroughly as I could imagine:

1. Booted recovery mode, wiped every.last.bit except external SD

2. Booted download mode, Odin'd the PIT file and the .tar factory PG2 image

3. The automatic reboot after flash went back to recovery mode and the Android robot updated the system

4. The automatic reboot after the update failed to start the phone, so I pulled the battery

4. Started phone, and recovery mode came back up -- eh?

That was weird. I was expecting normal. So I:

5. Booted download mode, Odin'd TWRP

6. Rebooted (had to pull battery again)

Now the phone started normally. Huh -- there must have been some flag stuck somewhere that got cleared when I Odin'd TWRP. Onward:

7. Went through my normal setup routine

8. Did not root the phone this time

9. Installed my handful of normal apps

Then I closed the S-View cover on my phone and set it aside for a couple minutes. I opened the cover -- and the phone didn't turn on. This has been one of the consistently weird things I've observed ever since I started my horrible MM update journey last week.

I discovered that if I kept some kind of process running, this problem would disappear. I started a terminal emulator, ran

logcat *:E >/sdcard/logcat.txt

then went to the home screen. I could close the phone cover, wait a while, reopen the cover, and the phone would come alive. But something's definitely not right -- shouldn't have to manufacture a background process to keep the phone from sleeping to death.

I remembered that this sleep of death wouldn't occur when I had the phone out of its cover. So I put the S-View aside and attached the LED flip cover. Same problem -- sleep of death after the cover is closed for a couple minutes. WTF!

So this morning, I pulled that cover off and attached the original back. And voila -- I've gone all day without any issues at all.

There's definitely some sort of power management problem that my phone experiences when an electrified cover is attached. I can't imagine that it would be the cause of the other problems I've seen -- lags and reboots.

I do miss having root -- think I'll flash SuperSU tonight.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Wow, so you narrowed the problem all the way to an accessory. Well I think that's still good news though. At least you identified a major issue. Might be time to research what the electrified cover actually does when it puts it to sleep. I have one on my Tab S, never had any issues, but I have no idea how the thing actually works.

As far as I can recall, you're not supposed to have Auto-Reboot checked when flashing with a PIT file. Just Repartition and F. Reset Time. May want to look into that as well. Doesn't sound like you got a solid install of the OS with all those battery pulls and such... which I would definitely make sure to do so you know that it took. Rooting shouldn't affect anything negatively.

All is well with mine, I have gotten a couple random freezes and restarts when I'm pulling a lot of data (Wifi).. Facebook, Instagram scrolling fast... just locks up. Only about once a day though. Still much better performance than what I was getting before. I flashed Xceed kernel this morning after the crash so I'll see if that makes a difference over BeastMode.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] SteveRiley:
Couldn't wait -- already flashed SuperSU. No issues.

I followed this procedure for flashing the PIT, which says you can do the PIT and the OS image all at once. And in the Odin log file, it was evident. First came the PIT and repartitioning, then came the various OS image files. Followed by the reboot.

http://xdaforums.com/note-4/orig-development/note-4-pit-files-repartiton-f-g-c-t-w8-t3282641

I left a step off -- after I Odin'd TWRP, I did a cache wipe/factory reset. Somewhere in the back of my brain I recall reading about other people have weird lag/reboot issues if they didn't do the wipe/reset after flashing a new ROM.

I'll keep going with what I have. It's the solidest (that a word?) install I've had so far. My suspicion is that the battery pulls had something to do with the stuck recovery flag.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] forbidinjustice:
Yeah you're right. I think leaving Auto-Reboot unchecked is for when you flash the PIT file alone and then reset ODIN and flash the firmware separately. If all is running smooth now, I guess it's hard to ask for too much more than that. Hopefully it'll stay that way.

If I'm flashing a new ROM or an update to a ROM, I always reset cache and dalvik... I also do it prior to flashing a new kernel. Takes a while to rebuild the cache but I think it does help. Sometimes a quick cache wipe can fix a lot of problems too.