(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.
I saw that they have SetCPU working with the Hummingbird in the Nexus S; I was wondering if this means there is a possibility that SetCPU overclock support may be coming for the Captivate as well?
it must be supported by kernel...
It already works?? But most of us use voltage control and you have to flash the right kernel
Sent from my SGH-I897 using XDA App
All the OC-supporting kernels I saw said not to use SetCPU...
Thread moved to Q&A.
Only person that would know that answer for sure would be supercurio as he's doing the kernel for both the i9000 and the Captivate.
I'd suggest going to his i9000 thread or checking his twitter to find out.
set cpu works but is not recomended with i9000 kernels though i dont know why. on the threads for unhelpfuls kernels there was talk about it messing up the interneal clock causing the time on texts to be off but that happened to me with the stock kernel and no use of set cpu when using set cpu the problem was no better or worse, therewas also non specific talk of it not playing nice with our phones.
i havent tried it on an i9000 kernel because there is no use for it. the voltage control app is capable of setting the max clock speed. set cpu could still be used for profiles i guess but i never saw the need for a profile, if you are running such a fine line that stability is effected by heat and charging status you might want a little less overclock. over/under clocking has very little effect on battery life do to cpu scaling. under clocking just makes it take longer to get tasks done keeping the cpu from sleeping, really not as big an effect on battery life as you'd expect. so that leaves you with the governor settings which our kernels dont support very well, you can try different kernels with different governor settings built in. perhaps the aosp kernels do better. i dont know becasue there are too many problems with cyanogen mod and the gingerbread port right now.
As mentioned it has worked for some time. But we've been recommended not to use it. I'd love to know why just out of curiousity.
Hi,
I've been recently playing some Dungeon Defenders on my SGS and well it is still sort of choppy when under stress. What bugs me is the fact that some people (with the same phone) claim to be having a clear lag-less game experience.
I've tried to switch ROMs and went from 2.1 stock eclair, trough 2.2.1 stock EU to latest Darkys 8.0 (with voodoo enabled). I have to say that there was some improvment, but it still has a long way to go.
Now, as Im looking for better gaming experience, I would like to ask if there is better ROM (not that I wouldn't be satisfied with this one though ) gaming-wise.
I also noticed, when running Quadrant Advanced (now getting 1350-1650 which is wierd. I mean 300 difference between two runs ??) that my CPU was, at the time, running at 400MHz with minimum frequency set as low as 100MHz, which seems ridiculous to me. I mean I know that CPU frequency changes in accordance with how much stress are we putting on it, but isn't it possible that even under stress my CPU runs "slower" ?
I would love to somehow improve my phone but as I already have voodoo in place, the only way to do so would be to overclock CPU right ? Or am I missing some other way to improve my phone ?
If Im not, than how safe is the overclocking ?
what would you suggest ?
Thanks everyone for your answers !!!
btw, Im sorry if I misplaced this message !
Uhmm, I can't advice you about the lag. I don't find it choppy playing Dungeon Defenders. Everything is smooth sailing. But it is safe to overclock. There might or might not be stability issues with your phone. Every phone varies. Like mine, I could get max OC to 1.3GHZ and then the phone freezes but I have friends who can OC to 1.6GHZ.
I don't recommend you to overclock though, I have some freezes in game (gameloft games especially) when OCed to 1.2GHZ.
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.
So i download a kernel off of the kernel manager from the market, I think its called thiamets? But anyways it has the option to go up to 1228Mhz and i think even 1256Mhz but my phone always freezes up at 1228Mhz. Is there anyway to get this stable or is that asking for to much. I just want to do it keep in mind I usually run my phone underclocked except when playing games...
It was noted many times that most Nexus Ones will exhibit instability over 1150 MHz. You can find warnings in most kernel threads.
Try the phone stability mod here: http://forum.xda-developers.com/showthread.php?t=1059423
I haven't tried it myself, but it could work.
Why do you want to overclock your phone that much?