Related
(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.
Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me
I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel
Had that issue at the Gym the other day, not even on Bionix.
I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App
Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.
r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.
i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/
There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.
Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL
Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!
sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..
I think it's hardware.... One of the unlucky ones....
Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
HTCOmega said:
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
Click to expand...
Click to collapse
Kernel flashing doesn't always go smoothly. Repeated kernel flashing without complete system wipes in between can cause some things to start going horribly wrong.
Don't use SetCPU to set clockspeeds. Just stick with voltage control.
If you forgot to disable any lagfixes at any point along the way, that could explain alot of the problem.
Suckerpunch kernel is a great concept and is showing alot of promise, but I personally have had alot of stability issues while using it, including random freezes (YMMV, of couse).
Just my opinion, but I would just back up all your data, flash back to stock, master clear, wipe all your cache data, reflash your rom, pick a kernel and stick with it for a while. If you want pure stability and battery life, use the most recent version of either DG's Firebird kernel 2 or Hardcore's speedmod kernel. If you want stability and oc/uv enabled, stick with Glitterball's kernel. Those 3 have been the best for me personally (again, YMMV).
Hello guys ,
I had recently serviced my SGS due to a charging issue , now it's working all fine on ICS CM9 B16+Semaphore but this issue is bugging me, i can't OC my Processor beyond 1140 mark that was available in semaphore script manager & even i can't change my ARM,INT voltages in NStools.......!
Maybe they had switched the Mobo or the whole SoC chip but still all my photos and videos were untouched...
Anyways if i try to change these my phone freezes and reboots .
Any ideas ??
Can you try underclocking?
If you can't set your clock to anything but the stock speed, then there maybe some issue with rooting or some system issue.
If the issue is just a matter of not being able to get beyond 1140, it maybe a case wherein the hardware can't go beyond that. Not all processors are built equal.
just my 2 cents
have you tried changing your kernel?
icedeocampo said:
Can you try underclocking?
If you can't set your clock to anything but the stock speed, then there maybe some issue with rooting or some system issue.
If the issue is just a matter of not being able to get beyond 1140, it maybe a case wherein the hardware can't go beyond that. Not all processors are built equal.
just my 2 cents
Click to expand...
Click to collapse
yea, maybe they had snapped in a new Cpu which can't go beyond 1140Mhz..!
this is sad...
thnkya anyways..!
silviu_iliescu said:
have you tried changing your kernel?
Click to expand...
Click to collapse
Well,I'll try Glitch but if still the problem persists then it's sure that the new cpu is a crap.
Ashtrix said:
I had recently serviced my SGS due to a charging issue , now it's working all fine on ICS CM9 B16+Semaphore but this issue is bugging me, i can't OC my Processor beyond 1140 mark that was available in semaphore script manager & even i can't change my ARM,INT voltages in NStools.......!
Maybe they had switched the Mobo or the whole SoC chip but still all my photos and videos were untouched...
Anyways if i try to change these my phone freezes and reboots .
Click to expand...
Click to collapse
Hi Ashtrix,
your currently installed Rom, Kernel and Tools are not 100% compatibel.
NS-Tools didn't work for Semaphore Kernel.
Use the Semaphore 0.74 apk to optimize the kernel.
Update your Semaphore-Kernel, the newest Semaphore-Kernel support OC 1200.
But give an CNA Rom and a Semaphore-Kernel a chance.
That is IMHO the best combination for your SGS.
But .....
with an CNA-Rom and a Semaphore-Kernel there is no need to OC
Number0ne
What is the best compromise speed stability?
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
I would try reflashing back to stock. Reinstall CWM, then try installing the ROM again.
Beyond that, maybe you should PM the guy who made the rom.
brianosaurus said:
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
Click to expand...
Click to collapse
I haven't had the reboot problems since 3.12 update from 3.11 clean install. Have had lag issue a couple times..for me restarting holo launcher corrected...tried to recreate wifi issue bit is working for me. All three kernels are very similar the saver has 1.3 and 1.2 disabled and the hotplug gov tweaked
Also posting this in my thread might get you more help.. since your running thrill seeker its ok to post problems you are having in that dev thread as others may be having same issues and ill see it quicker and try to help fix it if I can.
Sent from my LG-P925 using xda premium
yeah, i'm a noob
I'll try going back to stock and then reflash the latest thrill seeker. I would have posted in the dev forum, but I don't have 10 posts yet, so I'm restricted from posting in dev. only 8 more to go
3.12 hasn't had a random reset on me, just the wifi reset, but that one "works" every time.
Thanks,
brian
found lag problem and found possible fix
lag problem on thrillseeker 3.11/3.12 appears to be the CPU somehow resetting the Max MHz to 100MHz after the phone sleeps for 10-15 mins. Having Romtoolbox installed, then adjusting the CPU sliders quickly bypasses this issue. Although a true fix is in the coding, this workaround appears to be permanent once preformed. At least we now know it is not a flaw in the Rom as far as an overload or hang-up problem. I have not experienced the Wifi issue yet. If I can get a heads-up on how to induce it, I can look into it. Great work on the Rom!
problems im having
The rom itself is near perfect to me...I give thanks to all that put the hours and hardwork into this
I am a complete noob so any help or answers I will greatly appreciate. The only trouble I have from rom so far is if I'm using the browser while its plugged in.. might be a bad install after all. I really jumbled a few things like not making a nandriod. So I'm kinda stuck with with out a return to stock option...I have been trying to work through this but im a bit unsure how to get a stock Back on here. ..????? Any help....... back to rom I love thrillseeker 3.1....I been testing what I need in a rom and well I couldn't be happier that this rom seems to to do the job and then some....everything works perfect ....like I said the only thingthat seems fuzzy is when I plug in to wall charger and then it gets glichy.....
cpu
I adjusted sliders as well the second one seems to revert back to 100mhz often so its not a permanent fix. It does help....
Yeah. Funny thing. My phone broke (cracked screen), so I did an exchange at best buy and this rom works just fine on the new one. I guess my old one was kind of janky on the inside.
Sent from my LG-P925 using xda app-developers app
I installed minicm 4.0.2 with naa-jb-03. Things are working fine, but there is a problem with wifi. it is connecting well, but after a small amount of data traffic, the phone restarts. i can load 1-2 webpages and then reboot. the same when i use market or other internet applications. what am I doing wrong?
I am pretty sure that's a RAM issue. No problem with WiFi.
I think you were right. i turned off the zRam setting and it worked for a few hours. but now doesn't matter what i do, when wifi is on, the phone get bootloop, just a full wipe/reset solves the problem. maybe this rom doesn't like me :/
Have you overclocked your cellphone? If you did so, then it's highly likely that that's the problem. try lower down a little the max value, and set the lower value a little higher...
default max value is 600 mhz.
On a side note, I experience reboots every 5 hours aprox... they are not that often, but still annoying.
I don't recommend overclocking; it's unnecessary, almost.
I didn't use overclock. i tried to install other rom with other kernel, but after the flashing the phone got bootloop at the kernel part :S
so i installed the stock kernel and 2.1. after that flashed naa kernel and minicm, and now it seems to work.
i also got wifi problem..how new update nightly fix the wifi
Sent from my E15i using xda app-developers app
I think i figured ot my problem. I tried also minicm9, and the same problem appeared. I found posts in the topic, that other people experienced the same on eduroam networks. I'm also trying on an eduroam network at my university, so the main problem is with wifi. Is there maybe a solution to fix this thing?