I've got a problem with my I9000, several times throughout the day it will randomly restart itself. It will be quite happily sat idle in my pocket not doing anything, and then suddenly I hear the boot-up sound from my pocket. It's just started doing this since Thursday or Friday I think it was, had nearly 700 hours uptime on it (699 hours ) and then I noticed from my SeePU notification that something was hammering the processor, running it at >90% for more than 10 minutes. Couldn't see any programs running in the background so decided to restart the phone. This is one my problem started.
It's running stock JPY with Voodoo Advance kernal, it was overclocked to 1.2GHz and had some undervolting from 800MHz down, this had been stable for all of those 699 hours, but I disabled the OC and UV yesterday to see if it was that causing the trouble, but even with it disabled the phone's still been restarting.
What would be really great is if there is some kind of crash log for Android (something similar to the Windows Event Viewer) so I can see what's causing this. Does anyone know if such a thing exists, and if it does how I might go about accessing it?
Failing that, anyone know why my phone would suddenly start restarting itself now?
had pretty much the same issue, different kernal and rom... but had an OV/UV that for the most part was stable...
then today was continually restarting.....
solution?
changed CPU scheduler to noop
changed CPU Governor to conservative (Galaxy S cpu default configuration)
Now not restarting at all... and that's with a 1.3GHz overclock... running several benchmarks and no undervolting at all.
I'll let you know if it starts acting up... but interesting that this at least fixed it for me.
Stupid thing has restarted itself twice this morning. This is ridiculous.
I've just set the schedular to noop, can't see an option to set the governor though. Will see if that sorts it.
Would really appreciate knowing if there's a log file or something though
If it was a PC you would say its overheating .
jje
Found an app on the market called OS Monitor that shows all the running processes and what load they're putting on the CPU, it also shows the dmesg and logcat log files.
Thankfully my phone hasn't restarted itself since changing the schedular, but if it does I should hopefully now be able to find out why
quick answer. Reflash the phone .
I guess reflashing and removing some dangerous apps will be good for you phone.
Hmm, well looks like it's given up on restarting itself and is just plain turning itself off now.
Looks like I'm going to have to reflash the stock kernal and see if that fixes it
So i've installed sammy kernel and as soon as i was done, the problem started. First, i booted back into the OS and i got a message telling me my SD card was damaged, i tried to take it out, reboot, nothing, it obliges me to format it. Then i've tested out a few combinations of governors and frequencies qith SetCPU and for some reason i barely get a 2000 score in vellamo when on stock i was getting between 2350 and 2400 almost every time. I'm not sure why, but i went through a few pages of the thread about the kernel and everybody found goos improvement and no problem.
Anybody knows how to troubleshoot this?
give little bit more info, dude.
such as?
when I flashed out of Sammy back to stock Kernel exactly one day later my SD card crapped out - unrecoverable data. I had to format it and go from there - now all is fine.
To be expected with new development. Hindsight is always 20/20.
does anybody else have similar issues?
Seems after switching back to CFQ, I havnt had a reboot yet, 64hours up time, when on SIO couldnt get more than 14-16, and would always reboot on a call. Hope that helps someone...
edit: sorry everyone, but it may actually be " allow purging of assets" I may have jumped the gun for the solution to the issue, ill keep testing...
Edit: Seems my issue with reboots was being caused by the option "allow purging of assets", just thought I should give an update
Follow me on...
Youtube http://bit.ly/To93d6
Google+ http://bit.ly/RqyYPa
Facebook http://on.fb.me/RFIADb
Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
SO... in regards to the KT-SGS4 KitKat 4.4 TouchWiz kernel, the vast majority of users seem to have no problems with it, but there ARE KNOWN issues that appear to be caused by this kernel for some users, with varying degrees of rarity. WHY certain users have these issues when others do not is not currently known, but it would be great if we could figure this out. I am HOPING this thread (and it will only be a THREAD with input from others) will help us find cures for the issues we face with this kernel.
KNOWN ISSUES:
#1. Sound skipping - This seems to be the most common issue experienced with the kernel and I actually would not call it rare. Some possible fixes for this are to: A) increase the Media/Music Min Mhz and Bluetooth Profile Mhz to around 702 Mhz or so, B) try using a different I/O Scheduler and try adjusting the Internal and External Read Ahead Buffers, C) change disable_hotplug_media from a 0 to 1.
#2. Phone freezes/locks up while charging
#3. Screen flickers when a window is open over the desktop
#4. Mobile connection/data (and possibly also GPS) loss a while after booting phone - this may be the rarest issue, but it is OBVIOUSLY the most serious. I have suffered from it personally. I contacted Ktoonsez regarding this and he denies it being a known issue since many thousands of users use his kernels and don't have this issue... I have confirmed multiple other users who DO have this issue and the only thing I see we have in common is the KT-SGS4 kernel. It appears that this issue MAY be fixable by using the "right" choice of governor and settings. The problem is that what the "right" choice of governor and settings are MAY be determined by your ROM. On stock rooted NAE with MF9 bootloader, using largely the kernel default settings, including the interactive governor, APPEARS to have cured this issue for me (as well as the freeze while charging), while using the ktoonserativeq governor or the pegasuq governor appear to have caused this issue (I am still in the process of investigating this...).
This is not meant to be in any way negative towards Ktoonsez and I certainly appreciate all the work he does to provide us kernels, but there ARE issues that some of experience and I hope this thread can help us work TOGETHER to solve them! If there are any other issue that you believe should be listed, please post them. If you have any possible cures, please post them. If you need any help, please ask. If you have any input, please post! :highfive:
I can't get his kernel to run on my phone for the life of me so I stuck with Negalite NAE Stock Kernel, but I use his kernel religiously on my wife's s3. Even using basically the same setup I still get skipping on music, phone goes unresponsive after charging a few hours. And a few others.
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)? I think the governor and adjustments are also critical in solving this problem. I've been using ondemand and somebody said interactive is also helpful. The other thing here is that it could be an issue of I/o scheduler. I've been using sio. I'm getting minimal skipping at this point. You're right that ktoonservativeq caused MAJOR skipping, even with tons of governor tweaks.
After switching to ondemand, my phone hasn't locked up while charging, but it has randomly locked up at other times. Weird.
On issue #4, I've lost data less with ondemand but it hasn't completely solved the problem. Sometimes I can toggle Airplane Mode on and off and get going again, but mostly that toggle won't even work and I have to reboot.
JesseAaronSafir said:
Is music skipping only for users who are also trying to do ViPER4Android (probably with Convolver turned on)?
Click to expand...
Click to collapse
That is an interesting question, now that you mention it. I had been using ViPER4Android, probably while I was having the skipping issue, but I stopped using it in the long process of attempting to cure my mobile connection issue (I read something that made me think it could be related) and I'm actually not sure if I ever had the skipping issue without it.
Of all the issues though, this one is very common in the KT-SGS4 kernel thread, so I DOUBT (but don't know) that everyone experiencing it is using
ViPER4Android.
(Also, I THINK it skipped for me without Convolver turned on).
I haven't used v4a since I was on Negalites
elwood said:
I haven't used v4a since I was on Negalites
Click to expand...
Click to collapse
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
rsngfrce said:
Yeah, I think the skipping has to do with the kernel generally allowing the governor in default settings to throttle down too low when music is playing...
Click to expand...
Click to collapse
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
arikdahn said:
Don't forget the issue where the phone will not power up while charging if it's charging while off.
I don't. Mine even skips while the screen is on and I don't use V4A and have tried other than stock music players as well. I have no such problems with Nega but I've tried different modem firmwares too. These don't seem to affect this problem.
If anybody wants, though, they could chime in on my Wifi tethering problem. Nobody seems to wanna tackle it.
http://forum.xda-developers.com/galaxy-s4-sprint/help/wifi-tether-disappeared-t2877341
Click to expand...
Click to collapse
I didn't forget it, it is issue #2!
#2. Phone freezes/locks up while charging
In my experience, the phone does NOT have to be off while it is charging to have this issue, it would happen to me when I was charging my phone with it on. Fortunately, on NAE stock rooted with MF9 bootloader, using the mostly default kernel settings with the interactive governor seems to have fixed this issue for me, as well as the mobile connection/GPS issue (knock on wood still...). I mainly just adjusted the I/0 Sceduler to noop and the Media/Music and Bluetooth Min Mhz to 702 Mhz from the stock settings. The only issue I am personally left with now is the screen flicker.
I don't think the screen being on or off relates THAT much to the music skipping issue, it skipped for me too with the screen on. Definitely I would say, using the ktoonservativeq governor with Ktoonsez' settings WILL result in music skipping... BUT, IMO, this MUST BE TAKEN INTO ACCOUNT, Ktoonsez DOES NOT HAVE OUR PHONE... how can his settings POSSIBLY be OPTIMAL for our phone? Think about that!
As far as your WiFi tethering issue, I am well aware of it personally, having read your other posts, but I don't know much about this (don't use it myself) and in another thread I was going to direct you to a link you are already aware of that didn't help. If anyone can help arikdahn with this, please jump in! :good:
I definitely had more problems with music skipping when the screen would turn off. Using ondemand or interactive with sio and 2048 read ahead caches seems to have almost completely resolved the issue for me. I'm still not sure which I/o scheduler is best.
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
rsngfrce said:
I would think that the governor throttles down MORE when the screen is off, which is why I consider the Media/Music and Bluetooth Min Mhz settings important to be set above the default, which I believe is Min and should override that throtte down when music playing (ay the expense of battery time, but the battery is meant to be USED when needed) and I can't see how that CAN'T cause skipping in most setups. But it does occur for some even with the screen on.
Click to expand...
Click to collapse
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
arikdahn said:
Well, all I have to go off of is my own expertise with MY equipment only. My thoughts based on this is that it's not a limited-resources type issue, like if the CPU's throttling down or not buffering ahead enough or whatever. I had skipping problems all the time and I tried it with uTorrent running in the background, items downloading/moving, and these processes didn't slow down or cause any problems themselves. That's why I think what I think. Anyway, what this means to me is that I do not believe that in my situation, anything I can do with the kernel's configurable options will change anything. Then again, i think my phone's possessed anyway. It won't run the dialer on AOSP/CM roms and might just be one of the most finnicky high tech devices I've ever owned.
Click to expand...
Click to collapse
Hey, I'm not in any way disputing what you are saying, the point of this thread is to figure these things out! I'm certainly not presenting myself as the expert on these issues! I'm just a lucky one who seems to have mostly resolved the issues on MY phone. (BUT... I AM NO ANDROID EXPERT EITHER and will never claim to be, but I am not saying it is a limited-resources issues, what I am saying is that I believe the default settings will allow the governor to throttle down to below the level necessary to play music without skipping... I could be wrong, but that it what it looks like to me.)
Because SO MANY people APPARENTLY don't have MOST of the issues mentioned, I personally think this is highly related to which ROM you are using... though I don't know what ROM those other people are using...
Hi everyone,
Thanks for reading this . As specified above, my phone has a rather serious problem of overheating. To try and reslove the issue I tried modifying the CPU frequency, to set it low enough. And a very bizarre thing just happend.
Opening Kernel Adiutor, I saw that 4 out of my 8 cores (the 2.5 ones) were running normally. No overclock, stock settings, stock governor and so on. The issue seems to be in the other 4 (the 2.3 ones). Both the minimum and highest frequency allowed is set up to the same parameter (1556 mHz), forcing it to stay at maximum clock all the time. I tried modyfing via Kernel Adiutor the settings, lowering the minimum frequency allowed to stock one (which should be around 300 or something), but it had no effects: it immediatly comes back to 1556 and just won't come down.
All of this started happening after i removed Franco Kernel from my system, flashing another ROM (Chroma) with a different kernel altogether. I'm currently on Cataclysm ROM and after doing a clean install, formatting internal storage as well as every other partition, i couldn't resolve the issue. Moreover, Kernel Adiutor sometimes won't even show my CPU settings, stuck on an infinite loading. If anyone could help me, it would be much appreciated. It's really important. I'm by no means Android expert but i do have a rather basic understanding of ADB and so on.
Thanks a lot for your time.
-LVBNR5
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
ml11ML said:
I used to own a n7 and that allowed me to set min and max freq. with apps fine but i am also seeing this on my 6p, i don't notice any "overheating" although it may be due to me being used to it always running hot since i run a lot of heavier programs and also you know... SD810 but i guess it does the frequency thing as a way that frequency is actually controlled on this platform or something, because it sticks fine to the limits you set while flashing a kernel but no app can get it to stick. Then again this is just me sharing my experience with it as it is my first phone with this platform, so maybe someone who knows more about this could offer some help.
Click to expand...
Click to collapse
Thanks anyway, i really appreciate it!