yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] dark_overload:
Heath, can you share with me your settings for voltage and clock speed? I'd like to compare and test with your settings considering your level of stability is much greater than mine. I did notice on first install the governor had an upper boundary of 23xx MHz which I thought was pretty high. First thing I did after that was restore defaults (within KTweaker) and then set the upper boundary to 1890 MHz. I have not changed any of the other settings, including voltages.

Thank you guys for brainstorming with me. Surge, I tend to agree with you about the kernel. I have a dmesg output attached to post #884 on pg. 89 if you're interested in peeking. I am optimistic, however, that the logcat will contain some sort of a hint as to what is instigating the problem. I know, it's like looking for a plastic needle in a haystack the size of Montana.

Also, I just noticed the new KT release as well. After the next crash, once I've saved the logs, I'll flash it and see what happens. I'm going on ten hours up-time now. Sitting on the edge of my seat. :fingers-crossed:
[Verizon Samsung Galaxy S 4] 318sugarhill:
I agree it's not Rom related. I've had it on baja, echo, and this. All similar experiences when the reboot happens. I didn't realize there was a new KT kernel out. I will definitely give it a shot.
[Verizon Samsung Galaxy S 4] Surge1223:
Off the top of my head,

Dial *#9900#, enable seclog and set debugging level to high, then reboot

1. dmesg

2. cat /proc/last_kmsg

3. download viewmem binary,

cd /dir-to-viewmem/

chmod 755 viewmem

viewmem 0xffe00008 0x100000 >/sdcard/seclog.txt

cat /sdcard/seclog.txt
[Verizon Samsung Galaxy S 4] bryantjopplin:
Well thank you for that, even as much as I love the hard way of doing things I found an option in ktoonz kernel app.

But will definitely do this anyways to learn it.

---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------

Also is steps 1-3 done thru the terminal?
[Verizon Samsung Galaxy S 4] dark_overload:
You sure that code is supposed to work on this ROM? I am using the built-in black international dialer, and it does nothing but call that number, lol. I want to viewmem, now that's something I haven't done yet.

EDIT: I am sure this is what you are talking about: http://xdaforums.com/showthread.php?t=2691420 And on this ROM it is disabled by default. I've enabled it and attached a seclog dump from a user-initiated reboot (not fully cold). Nothing jumps out at me though that reason code in the boot line may be useful after a hot-restart.

Thanks Surge! Let me know if you see anything I missed.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yes you have to turn on hidden menu lol, but you had already found it.

---------- Post added at 12:28 AM ---------- Previous post was at 12:20 AM ----------

OK I see what you meant. Where did you learn all this, I need to go there.
[Verizon Samsung Galaxy S 4] dark_overload:
I linked to it in my original edit. Normally I am a big Linux geek, so I knew the terminology that the search feature wanted to hear. ;)

I just updated to the new KT-SGS4-KK4.4-TW-VZW-06.09.2014 kernel. Afterwards I dumped a high verbosity seclog again and attached it to the previous post. Interestingly enough the size is the same (after trimming of course) yet the checksums differ. Differences of a constant length? I'll have to diff them later and find out. :cool:

Okay once again I have ADM linked up and listening. It's gonna happen again sooner or later. Lol.
[Verizon Samsung Galaxy S 4] heath2805:
Still running default settings as well. Haven't felt the need to change anything.
[Verizon Samsung Galaxy S 4] dark_overload:
For the first time I've done the same thing and got the same result twice. Just like yesterday I left ADM running all night watching the phone. When I woke up ADM had crashed and as soon as I "swipe unlocked" my phone it rebooted.

Same exact situation... SystemPanel shows the system process maxing out one core around 8:05 AM and this behavior continues for four hours until I pick up my phone and try to use it for the first time today. After looking through the kmsg and dmesg logs from today's system failure, I don't know if it's the kernel at all. The last line in kmsg shows the kernel does not go down in the reboot, it causes the system to restart. And after the system restarts, the system process is no longer running amok. The whole time, it seems the kernel is still up and running.

I have attached the aforementioned logs here. The length of the dmsg log is about 98.75177 seconds, plenty of time to show the behavior leading up to the crash. The kmsg log also contains something interesting: it looks like the CPU governor is being denied something. That IS kernel based, so now I am really confused.

All in all, this could be a dangerous problem. Look what it does what this happens: high heat, high drain. Lithium batteries can get quite angry when treated like this. Not only that, but what about extraneous wear-and-tear on the components?
[Verizon Samsung Galaxy S 4] PaintDrinkingPete:
Just switched over to this ROM after running Danvdh's GPE ROM for a few months.

Pretty happy with this ROM overall, but just had some questions that hopefully can be answered here. I searched around the thread, so my apologies of these have been answered before...

1. Phone ran great for the first day or so, but last night had pretty serious battery drain with "Android System" taking the top spot in the battery log. Is this common and if so any known causes/fixes? I've now installed wakelock detector to see if it can shed any additional light on the subject.

2. The kernel. I update the kernel to KToonsez' most recent (maybe I shouldn't have done that?), and while everything *seems* alright, are there any caveats I should know about?, any preferred settings for this ROM, or should I be using the kernel defaults?

In case it matters, I did do a FULL wipe prior to installing, and have updated the radio to the latest version "NC5" as well.
[Verizon Samsung Galaxy S 4] jds3118:
Suggest you share in kt's thread maybe he can help with the logs
[Verizon Samsung Galaxy S 4] dark_overload:
It sounds like you are having the same issue I am. For some reason the "android_system" process keeps going into an infinite loop on one CPU core.
[Verizon Samsung Galaxy S 4] dark_overload:
TIMA

I just noticed there are some errors that continuously appear in my logcat informing of a failure loading TIMA firmware.

06-10 22:28:47.266: E/QSEECOMAPI:(839): Error::Cannot open the file /firmware/image/tima_pkm.mdt
06-10 22:28:47.266: E/QSEECOMAPI:(839): Error::Loading image failed with ret = -1
06-10 22:28:47.276: W/TimaService(839): TIMA: Unknown message from TIMA APPs. Not notifying the user

I found this post describing TIMA in another thread.

Is there any specific reason that TIMA should be enabled in this ROM? Is it necessary? Anyway that file it is looking for is not there because I am using the I545VRUAMDK NON-HLOS so I just disabled it in build.prop. I don't see any more of those errors now.

I am starting to wonder if TIMA was the reason for all this crashing nonsense... Also, just above the corresponding line in build.prop is a line enabling KNOX. Same question: is this necessary? Should it be disabled on the good 'ol MDK bootloader?

On a side note I also wiped

everything

: data, cache, dalvik, SD (both internal and external) and re-flashed with VZW_NC5_AROMA_4_29_30 immediately followed by the KT-SGS4-KK4.4-TW-VZW-06.09.2014 kernel. We'll see if I still have issues with crashing and hot-reboots.
[Verizon Samsung Galaxy S 4] heath2805:
Recieved a call and screen wouldn't come on with KT 6-09...went back to KT 5-28 and works fine. Anyone else have this happen? 5-28 KT w/ default kernel settings seems flawless though.
[Verizon Samsung Galaxy S 4] dark_overload:
Just tested it. There is about a second of delay from when the ringtone starts to when the screen activates, but it does light up.
[Verizon Samsung Galaxy S 4] PaintDrinkingPete:
Well...hopefully this means I've figured out the battery drain issue...
[Verizon Samsung Galaxy S 4] lissa5168:
Never mind. I hate Tapatalk search LOL.

>^.^< Purred contentedly via Tapatalk
[Verizon Samsung Galaxy S 4] Zmnypit:
Anyone have the S5 lockscreen zip? I had a catastrophe today and had to odin back to stock and lost the zip I had. Everything I find on Google hasnt worked so far.
[Verizon Samsung Galaxy S 4] ejohn3288:
Has anyone experienced a force reboot when taking pictures in night mode?
[Verizon Samsung Galaxy S 4] dark_overload:
Actually yes. It took a few shots to happen, but it hapened. This DOES look like it could possibly kernel issue, because it was a hard-reset, bootloader and everything. I don't want to say for sure until I can get into the logs. I will try to make it happen and watch with ADM when I get to my desktop.

Interestingly enough (aside from this new issue) I may have solved the random reboot. Results seem to suggest it may have been a corrupt file on either the internal or external SD that the media scanner was choking on.
[Verizon Samsung Galaxy S 4] Velocifero:
No zip needed.

http://xdaforums.com/showthread.php?p=52212366&highlight=lockscreen#post52212366
[Verizon Samsung Galaxy S 4] Zmnypit:
Thanks but this has no sound. The zip had working sound.
[Verizon Samsung Galaxy S 4] Velocifero:
Ah I see. I never appreciated unlock sounds anyway so this was ideal for me. Best of luck in your search. The Galaxy Locker app mimics the S5's lockscreen pretty damn well, to include the sound, and most recently, the camera icon unlock on the right corner. You can even hide the status bar. Only bad part about that app is I dont think you can change the clock widget. Whether on purpose or not, I think they made it TOO accurate in that sense since you can't change the lockscreen widget on the S5 either hahah
[Verizon Samsung Galaxy S 4] dark_overload:
Night Mode Camera Crash

I am not exactly sure what is causing this to happen. Taking pictures with night-mode crashes hard about 90% of the time. I have attached a logcat starting from when I touch the shutter button up until the phone reboots. Hopefully someone else can make more sense of it than me.

On a side note, I'm now quite sure I've solved the battery draining runaway system process. If anyone is still having this issue, try re-flashing the system after a full wipe (including internal and external SD cards, after a backup of course). You can piece-meal things back on to them later. I still haven't found what caused it, I just know doing that fixed it.
[Verizon Samsung Galaxy S 4] Beakhole:
Dumb question:

My brother is running stock rooted 4.2.2, build MDK. If I do this for him, will this eliminate root or is root access still included in this ROM? I'm referring to the VZW_NC5_AROMA_4_29_30.zip.

Please let me know as soon as you can.
[Verizon Samsung Galaxy S 4] dark_overload:
That is the build I came from. This build is pre - rooted. Just remember to wipe all storage as per my previous post to avoid the possibility of random reboots and battery drain.
[Verizon Samsung Galaxy S 4] Beakhole:
Would it be advisable to remove the sdcard before doing all of the wiping? And if this gets screwed up, will it be easy to restore from a NANDROID recovery backup made with CWM?
[Verizon Samsung Galaxy S 4] dark_overload:
You could do that. But you still have to wipe the internal (mounts and storage, iirc) because it is non - removable.

NAND backups are always a good idea. That's a given. I rolled back once and it worked fine.
[Verizon Samsung Galaxy S 4] Beakhole:
Thanks. Can you tell me if this page's last set of instructions would be sufficient for a CWM on his phone and whether or not it'd be compatible with this ROM?
[Verizon Samsung Galaxy S 4] dark_overload:
That looks like how I did it last year. As long as he hasn't taken any OTA updates that should still work.

Also: even if you remove the external SD during install, you should still backup/wipe it before re - inserting it.
[Verizon Samsung Galaxy S 4] Beakhole:
When you say backup/wipe, are you referring to the SDcard? And if so, why does the SDcard need to be wiped, have the stuff put back on it, and then reinserted back into the phone?
[Verizon Samsung Galaxy S 4] dark_overload:
Read the last few pages of this thread. There is a common issue with system instability.
[Verizon Samsung Galaxy S 4] Beakhole:
Alright, well thanks for your help. :D
[Verizon Samsung Galaxy S 4] dark_overload:
No problem. If you have the random instability issue please let me know.
[Verizon Samsung Galaxy S 4] mochamoo:
Seems like overkill to me. I've never seen it recommended to wipe all storage before installing this rom. Is there a link somewhere? All I usually do is wipe cache/dalvik cache/app data but not sdcard or extsdcard. NC5 ran fine for me except for the occasional SOD and random reboot that is present even on stock kitkat s4s. Currently running NE5 with the AEL kernel with no problems at all. (I hate to admit it, but I even dirty flashed that one over this one...but was prepared with a nandroid just in case.)
[Verizon Samsung Galaxy S 4] dark_overload:
The "standard operating procedure" is what I followed on my first flash. Something on either the internal or external stayed behind and jammed up the media scanner process causing it to go into an infinite loop. By backing up and clearing those storage medium, I was able to stop the "random reboot."

I am still slowly moving things back on to their respective storage medium but as of yet I have not re-introduced the problem file.

I expect this to be the case on stock phones suffering from this issue as well, as the media scanner is part of the android system.
[Verizon Samsung Galaxy S 4] mochamoo:
Gotcha, but I still wouldn't wipe all storage except as a last resort. External sdcards can go bad and can cause system weirdness. Did you try a different kernel? I would currently refer you to talexop or AEL. I like ktoonez' kernels but just haven't much luck with them on TW kitkat roms.
[Verizon Samsung Galaxy S 4] ejohn3288:
Would you happen to have a link to these kernels for the Verizon galaxy s4. I545?
[Verizon Samsung Galaxy S 4] dark_overload:
Read the last few pages, lol. It kinda was a last resort for me. I am not new to debugging procedures and so I had tried a lot of things to make it stop beforehand. Besides that, the random reboot I was suffering from was not kernel related.

http://xdaforums.com/showthread.php?t=2294083
[Verizon Samsung Galaxy S 4] mochamoo:
I understand that your issues were severe enough that you wanted to go the extra mile and take the shotgun approach. I just don't recommend it for everyone as it is often unnecessary.

My recommendation? Run this instead...

http://xdaforums.com/showthread.php?t=2552605

With this kernel.

http://xdaforums.com/showthread.php?t=2711416
[Verizon Samsung Galaxy S 4] dark_overload:
Lol. Hey once I find that problem file I can give people rifle rounds instead of birdshot. Until then, anyone wishing to stop the reboots bad enough has an option to try.

I did not come to that conclusion blindly either, mind you. I studied very closely what the system was doing.

Now I only have this one device with which to test so if anybody has solved their random reboot problem here I want to hear about it. Maybe someone else has already narrowed it down. I don't know about you my friend, but I have a LOT of files...

I'd like to see if someone with a non - root stock I545 has solved the random reboot with a shotgun wipe. But this is probably not the forum board to look in. ;)

---------- Post added at 01:59 AM ---------- Previous post was at 01:55 AM ----------

That is for the I9505. He has an I545.
[Verizon Samsung Galaxy S 4] Redflea:
+1

That's my combo.
[Verizon Samsung Galaxy S 4] dark_overload:
Back to this issue. I posted previously a logcat excerpt from when this happens. I just made it happen again while following kmsg. It kind of looks like the CPU just halts execution.
[Verizon Samsung Galaxy S 4] mochamoo:
My buddy has one but I think that he would seriously hurt me if I tried anything with his phone. He doesn't even have an external sd card in it. He doesn't have the random reboot issue but he does get SODs from time to time since the kitkat update. If it starts to rebooting too much for him then *maybe* I can convince him to be a guinea pig.

---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------

I learn from the best :)

Have been on this combo for a week now. No SODs, no reboots. *like*
[Verizon Samsung Galaxy S 4] mochamoo:
It runs perfectly fine on my i545. You can run either the AEL or talexop international kernels on the i545 as long as you flash loki doki zip immediately after flashing the kernel and before you leave recovery. See post #482 in this thread. Either one of those kernels works better on this rom than ktoonez. Reduced the SOD/reboots that I was having quite a bit.
[Verizon Samsung Galaxy S 4] dark_overload:
I thought the hardware in the I9505 differed slightly from the I545. It may work, but is it meant to? Would it be worth creating lokified zips for people to flash on their I545s? It's not hard at all, there must be a reason the creators of those kernels have not done so.

Remember: if the round hole is large enough, a square peg WILL fit.

When you say reduced, you don't mean completely gone? Have you tried the shotgun wipe? I don't have any reboots at all anymore. :cool:
[Verizon Samsung Galaxy S 4] mochamoo:
The creators haven't done it likely because they have no interest in doing so but couldn't say for sure. Others would know better.

They didn't completely go away, but they were greatly reduced. Still annoying. After going back to an old 4.3 nandroid for a while I switched to the ne5 rom that jkruse built instead (ne5 is international kitkat version) with an aroma installer for the i545. Loaded the AEL kernel. Link in earlier post. Much less time consuming than the shotgun approach :)
[Verizon Samsung Galaxy S 4] dark_overload:
Considering that anyone preparing for a flash should have already backed up all of their files (even on internal/external SD) and the fact that formatting takes only seconds, I can't see why you'd think it's more time consuming. It may be, but it's not worth debating. ;)

The way I see it, it all boils down to a choice that everyone preparing for a flash is going to have to make. Do they want to take the time to wipe all storage in return for the highest level of stability? Or do they decide to skip that step and roll with the punches.

I urge everyone to weigh all options and decide for yourselves. But please come back and tell us what you did, why, and how it turned out.
[Verizon Samsung Galaxy S 4] mochamoo:
Which is why I still follow this thread...still interested in seeing what others discover because you never know. My belief is that there is something basically wrong with the 4.4.2 firmware and that it won't be completely resolved until 4.4.3 (hopefully). I kinda like the line in this article that says "fix for random reboot". One reason why I don't spend too much time on any one rom. There's always a newer one to play with instead. This one is almost 2 months old now!!! :) I am already on the prowl for the next one to load on my s4. I might leave touchwiz altogether.

http://bgr.com/2014/03/31/android-4-4-3-kitkat-update-changelog/
[Verizon Samsung Galaxy S 4] dark_overload:
You are right about it being a bug with the 4.4.2 system itself. Like I said in a previous post, it is indeed a fault in the Android system. The media scanner process has a bug that causes it to go into an infinite loop when it runs across a bit of data that it cannot handle. This process is part of the Android system itself, and as such, it is common to all Android ROMs.

As a matter of fact, the behavior of this issue seems to suggest it could possibly be exploited to run arbitrary code. :angel:
[Verizon Samsung Galaxy S 4] bryantjopplin:
I truly wish I could see what problems you quys have. Being on mdk and wiping everything besides the SD cards, I literally have had only one random reboot. No wifi, Bluetooth, battery, smoothness issues or anything weird. Are you guys mdk? I have flashed almost all s4 kitkat roms with almost all with zero issues. I have always used ktoonz and kept everything stock settings and updated everything.
[Verizon Samsung Galaxy S 4] jds3118:
It's the i9500 that has different cpu I believe.

is it really that hard to hit the thanks button ? lol
[Verizon Samsung Galaxy S 4] stang5litre:
I am in the Jkruze Build as well aroma installed with exposed frame work. KToonz Kernel with no issues what so ever. No reboots, No Camera Problems , battery life is excellent. I would have to agree if your going to install any rom you always wipe data, cache, and delvik. Other wise if you have issues your it will be a lot harder to track down as a lot of your old files are now combined with a different rom. I am on MDK build. Are you using SS? Don't see why people are having any problems with the Rom. I am looking at your log as well. See if there is another work around. I know you have removed the file that you narrowed down to.

---------- Post added at 09:10 PM ---------- Previous post was at 09:04 PM ----------

Same here no issues what so ever. Aroma installed with exposed KToonz Kernel. I have been on a ton of s4 ROMs and KitKat builds as well. And what problems you have? I have none everything works. Only thing I need to do is see if someone made a work around for being on a call and using the camera while on the call. I believe I found the thread a while ago I just forgot about it. If not I'll make a work around and post a flashable zip if anyone needs.
[Verizon Samsung Galaxy S 4] bryantjopplin:
No issues for as I said earlier but are you trying to do this, camera plus call?
[Verizon Samsung Galaxy S 4] dark_overload:
It's not strange to me why not all of you are having the random reboot. You may not have any files with "bad mojo." Lol. But until I find out what was on one of my cards that caused it I can't tell you why it happens. Non printable characters in the ID3 tags maybe? Who knows. Whatever it is 4.2 handled it well and 4.4 does not.
[Verizon Samsung Galaxy S 4] stang5litre:
Yep, the camera and call. I know I saw it somewhere . My Google camera works with calling (tested that ), does your Samsung camera work while in call as well? If so then that is what I am looking for ☺ (I use both cameras depending on what I am taking a picture of).

I must have miss read your previous post as I thought it said you barely have any issues. My mistake ☺

---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------

I'm sure you have done this but figured I would ask since this problem Stemed from your sdcard. Have you re flashed with a different sd card? That way any files that are haunted could be replaced. (Sure you have but had to ask anyways). The log is definitely interesting.
[Verizon Samsung Galaxy S 4] dark_overload:
In a sense, that is exactly what I did by formatting them, plus the fact that it works now also rules out bad NAND cells as the cause. I always confirm when I can though so I ran some low level tests on the SD card using Kali Linux and the SD is in tip top shape. I have not tested the internal (emulated) SD though as that is actually part of the NAND on the main board itself. I hate problems like this; they are so hard to debug.