Related
Im having some issues with my vibrant and since today, everytime I lock the screen, then i try to unlock it, it stays black and nothing comes up or anything i just can seem to unlock it without holding the power button which causes the vibrant to restart. is anyone having this problem? Any solution to it other than formating maybe? Its rooted and I have a lag fix on it.
I'm assuming you've rebooted?
no i didnt. i didnt try to do that because i didnt want to lose everything. i was hoping its some app and i tried uninstalling some apps but still got the same problem. It keeps happing to me everytime since earlier today. you think that would work?
s15274n said:
I'm assuming you've rebooted?
Click to expand...
Click to collapse
I thought the same thing.
Ok. Something must be in the air. Exact same thing happening to me today.
Each time the screen times out the phone becomes unresponsive. Blank screen, soft keys don't light up. If I hold the power button too long it just reboots.
Rooted
Flashed lag fix
Clockwork recovery
Set CPU
Ya know what, as soon as I posted the details on my phones configuration it dawned on me that it could be a setcpu problem... Looking into it.
Set CPU was my problem. When I looked at the min/max they were both set at 19 out something ridiculously low like that. NO MORE SET ON BOOT!
I bought SetCPU but have not installed it on the Galaxy... I really don't see the point right now unless you want to underclock, and yes, it has been reported (perhaps fixed now?) that set on boot could cause issues.
I would just uninstall till we have a kernel we can OC.
OP, what would you lose by rebooting? Yes... I do believe that would work (and uninstalling SetCPU if you have it or change the aforementioned)
Set CPU profiles cause the phone to reboot and or freeze. See this thread forum.xda-developerscom/showthread.php?p=7808723#post 7808723
lagginess
Just to clear the setcpu is useless without a proper kernel i had it everything bogged down badly like reported went down to 19 from 10000. I would just take off the setcpu and wait for a kernel my phone def sped up after but thats my own experience.
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
I have some trouble transferring big files ~2GB+ from my SD card to my computer using a USB cable. I'm using BFQ or CFQ scheduler, don't remember exactly what one right now..
Transfer just freeze completely for like 20 seconds over and over again until it's done.. Take so much time and it's really annoying.
I think this have to do with a bad I/O scheduler, anyone know anything about this?
What is recommended for my activities? I don't want any freezing, some jumpy speeds is okay as long as things don't freeze up.
I don't have time to test like 20 schedulers that’s why I ask for help, mod please don't remove this thread. Thanks.
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...
Nexus 6P freezes after filling up ram and swap. I can reproduce it in the way that after restart I load like 30-40 apps and then the phone gets frozen. having an eye on vmstat I can see that once all mem and swap is filled up the system completely freezes, if i free up memory by killing some processes from adb shell (which is also slowed down) system regains responsiveness until memory is filled up again. Do you have similar issues? (from a non technical perspective you shall just experience random freezes 4-5 times a day where only a reboot helps)
I have DP4 with SuperSu 2.74. coming from DP3 where everything works fine.
I already posted a bugreport here, please star it (and don't comment) if you are interested
I have this exact same issue. It happens when on elementalx and stock. Unecrypted. I cant tell you how happy i am to find out someone else is having this issue.
Now, any ideas or leads on how we can work to fix it till the new Preview is released?
my nexus 6p froze a lot too
it's crazy
i don't know what to do
dev options Background processes 3 at most. Or kill all....
Dp4 was too buggy for me so I went back to pa which is working great and maxes daily usage out at 3% with 6 hours screen on time using eclipse profile and elemental x 1.18 using themes and atmos viper mod
i42o said:
dev options Background processes 3 at most. Or kill all....
Dp4 was too buggy for me so I went back to pa which is working great and maxes daily usage out at 3% with 6 hours screen on time using eclipse profile and elemental x 1.18 using themes and atmos viper mod
Click to expand...
Click to collapse
Im okay with this fix haha.
I'm getting this too. Surprised this was the only thread I can find about it after several days of release. Stock and EX kernel as well, while the phone is encrypted. Switching back to DP3.
Edit: Reinstalled DP4 but kept the kernel/boot.img from DP3 and is working fine so far.
I am now on DP 3, but android guys need a bugreport about the issue, could you please send them one?
fir the record I tried the following:
- DP4 with DP3 radio (because I had a lot of QC QMI errors in log): freezes
- DP4 with elementalx kernel 3.02 (meant for DP3): freezes
- DP4 with only SuperSu 2.74: freezes
@divadkha please let us know if you are fine with DP3 boot.img. the usual pattern how i can always reproduce the issue is to just load up a lot of different applications and i can make it freeze in 10 minutes after boot.
Exactly same issue I have since dp3, after few weeks, here's what I did
temporary workaround, set limit process to 4(3,2 1 should also work) in dev option.
if you want keep standard limit, try disable zRam and KSM in the ex kernel Memory option, see if that works.
my one (DP4) suddenly out of this issue, Available Memory won't <500m, it will automatically kill some process when memory down below around 500m
I don't know what I exactly did, just suspect it may related to zRam or KSM.
guys, please keep update.
jiajialing said:
Exactly same issue I have since dp3, after few weeks, here's what I did
temporary workaround, set limit process to 4(3,2 1 should also work) in dev option.
if you want keep standard limit, try disable zRam and KSM in the ex kernel Memory option, see if that works.
my one (DP4) suddenly out of this issue, Available Memory won't <500m, it will automatically kill some process when memory down below around 500m
I don't know what I exactly did, just suspect it may related to zRam or KSM.
guys, please keep update.
Click to expand...
Click to collapse
I've set to 4 and opened every app I've got and seems to be working had no problems so this looks like a fix thanks
jaythenut said:
I've set to 4 and opened every app I've got and seems to be working had no problems so this looks like a fix thanks
Click to expand...
Click to collapse
ye, that works, but we need figure out why it doesn't work under standard process limit.
maybe google's bug?
perhaps, please fill your findings and possibly a bug report to the android bugtracker so they can resolve it, thanks
Glad (sorta) I'm not the only one suffering on DP4. I didn't think twice flashing it because of how stable DP3 was. I haven't tested the app limit but in regular use a crash becomes more likely the longer I'm using it. It happens a lot using Chrome for example. I also experience it with the camera though. Launched snapchat - freeze/crash/reboot, launched 2nd time, crashed again, launched 3rd time... success! Will try a 4 process limit for awhile.
stock DP4 with root
jiajialing said:
Exactly same issue I have since dp3, after few weeks, here's what I did
temporary workaround, set limit process to 4(3,2 1 should also work) in dev option.
if you want keep standard limit, try disable zRam and KSM in the ex kernel Memory option, see if that works.
my one (DP4) suddenly out of this issue, Available Memory won't <500m, it will automatically kill some process when memory down below around 500m
I don't know what I exactly did, just suspect it may related to zRam or KSM.
guys, please keep update.
Click to expand...
Click to collapse
EDIT: Nevermind there's no franco kernel for N, I had a brain fart there for a second. Still not sure why people are having the freezing issue. I'm running stock with no issues.
bouchigo said:
It's most likely zRam. I'm running franco kernel, and I know his kernel has modified zRam settings and I get no freezes anywhere.
Click to expand...
Click to collapse
Which one did you flash can't see one for n
I uninstalled Superuser 2.74 by reflashing the stock system and boot images and no longer have the problem.
bouchigo said:
It's most likely zRam. I'm running franco kernel, and I know his kernel has modified zRam settings and I get no freezes anywhere.
Click to expand...
Click to collapse
I have tried ElementalX 3.02 with disabled zRam and it did not help.
do you guys with this issue use AdAway? maybe it is the culprit. can someone confirm if it gets resolved by removing the host file changes or has the freezes even without it?
jaythenut said:
Which one did you flash can't see one for n
Click to expand...
Click to collapse
I edited my previous post, check it out again...lol
usaff22 said:
I uninstalled Superuser 2.74 by reflashing the stock system and boot images and no longer have the problem.
Click to expand...
Click to collapse
in this case a bugreport shall be sent to @Chainfire too
As strange as it sounds raising minfree values did make freezes stop for me. Try it and report back please.
You can use AutoKiller or any other minfree tweaker to test it.
The funny thing is I only tried it now... Lolz