Database Develop

JAC kernel bug: using audio randomly kills phone

(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.

Droid 1 + MIUI Overclock Kernel

Hey all,
I just helped a friend load up MIUI onto his Droid 1 after he saw my Inc running MIUI and was impressed. I noticed that the with Droid 1 it comes with a kernel overclockable to 800 mhz, but I was wondering if there were any other good kernels that you guys recommend using for this?
Thanks!

Try this: http://forum.cyanogenmod.com/topic/4434-froyo-kernels-by-slayher/
I'm using Slayher 1100 Mhz v1.6, and it's pretty stable and smooth.
I had an wifi issue though - turningn on wifi would make
the system crash and put into a loop of force shut off, reboot and crash.
But I used both wifi driver and wifi fix on the same URL,
and that solved the problem.
I love my D1 + MIUI v1.7.8 + Slayher v1.6 combination.

Can't OC beyond 1140Mhz..!

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?

2.6.35.7 vs 2.6.32.9 kernel

Okay here's the thing,
my last most stable ROM I was running on was CacingKalung's MIUI. And that had a wakelock issue too. I'm pretty sick of it, so I decided to try Edowar's CM7 and maybe even Bumblebee rom.
when I flashed to Edo's CM7, all was good, no wakelocks, apn thing I had it fixed by using yashwant's APN fix.. until I ran Temple Run. The frames were skipping really bad, in the store part the Back button couldnt even been seen until scrolled up. The vines kept disappearing, and the gameplay was even worse, laggy. Mind you I updated the game already.
I never had this issue when I was on 2.6.32.9. So tell me, with me switching back to .6.32.9 now, what do I have to lose? Please share your thoughts and opinion!
PS: Thinking of going back to Maclite rom, least it's stable.

Bro its too early to comment on difference between these two kernel.
for .32.9 kernel various custom kernel are available while for .35.7 only TJ's custom version is available and I think it need more support from kernel developer.
till now if we think for .32.9 kernel, mOCk is best for gamer.

I have found that the best gaming combo is maclite with bumblebee kernel for mortals(non devs like me) and newer gpu drivers as far as benchmarks go. It also gives a superfast rom. What I have found so far is that eventhough there is a scarcity of custom kernels for .35 the situation will not improve any better than the performance of tj with a score of 27.9. I have already achieved 27.7 at 1.4 GHz with the. 32 kernel and 27.2 with stock speed in nenamark 2.2. Still this is just my opinion and it is very likely that your device may hit tjs score.
Sent from my MacLite-FB0 using XDA

Between .35 and .32... seem that .35 hasn't been hacked with wakelock trick while wifi is on. This hack is needed to prevent our device to meet Sleep of Death when it goes to sleep while wifi is on.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk

CacingKalung said:
Between .35 and .32... seem that .35 hasn't been hacked with wakelock trick while wifi is on. This hack is needed to prevent our device to meet Sleep of Death when it goes to sleep while wifi is on.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk
Click to expand...
Click to collapse
oh i thought the SoD had nothing to do with kernel.. lol well thank God im back to. 32..
am still getting pretty bad wakelocks every now and then x.x
but honestly i tried STOCK sharp rom to play temple run and even on that the frames were choppy, graphics n sum sprites were missing. ugh.
anyone with good batt life on either roms can u guys share your rom,kernel n config? my phone lasts about 8-10 hrs a day only if heavily used non stop.

cheezzzz said:
Okay here's the thing,
my last most stable ROM I was running on was CacingKalung's MIUI. And that had a wakelock issue too. I'm pretty sick of it, so I decided to try Edowar's CM7 and maybe even Bumblebee rom.
when I flashed to Edo's CM7, all was good, no wakelocks, apn thing I had it fixed by using yashwant's APN fix.. until I ran Temple Run. The frames were skipping really bad, in the store part the Back button couldnt even been seen until scrolled up. The vines kept disappearing, and the gameplay was even worse, laggy. Mind you I updated the game already.
I never had this issue when I was on 2.6.32.9. So tell me, with me switching back to .6.32.9 now, what do I have to lose? Please share your thoughts and opinion!
PS: Thinking of going back to Maclite rom, least it's stable.
Click to expand...
Click to collapse
I'm on latest edowar's CM7, got lag issue when playing Temple run on 35.7 kernel, but then after I set the I/O governer to Deadline, and CPU gorvener to smartassv2 or interactive X, it seems better.
From my experience with this rom, the gpu lib is not very good to play HD games (got so much lag when playing Asphalt 6, but not dungeon defender 3), or very much like fast moving graphic game like temple run. I've test to install the older gpu lib from 32.9 kernel (just the gpu lib, not the kernel itself), it gave me back low nenamark2 value, but the lag is gone like 32.9 kernel cm7, however, it seems making the fast locking gps not to be that fast anymore (wonder why, still need to play2 around again).
About the wifi, it really piss me off as it will brings the phone to sleep of death each time it goes to sleep although I set the wifi sleep policy to 'never'. however, the workaround would be to install Advanced Wifi Lock from the market for now.

Originally Posted by CacingKalung
Between .35 and .32... seem that .35 hasn't been hacked with wakelock trick while wifi is on. This hack is needed to prevent our device to meet Sleep of Death when it goes to sleep while wifi is on.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk
Click to expand...
Click to collapse
oh i thought the SoD had nothing to do with kernel.. lol well thank God im back to. 32..
am still getting pretty bad wakelocks every now and then x.x
Click to expand...
Click to collapse
Because of the wakelock hack, when wifi is on, our device will never go to sleep. So it's very recomended to turn on wifi only when we need it and turn off if we've done. so our device will able to enter sleep mode when in idle to save power.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk

CacingKalung said:
Because of the wakelock hack, when wifi is on, our device will never go to sleep. So it's very recomended to turn on wifi only when we need it and turn off if we've done. so our device will able to enter sleep mode when in idle to save power.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk
Click to expand...
Click to collapse
CK bro, Mokee v0.3 still has the SOD issue though it uses mock kernel(0.32). Any ideas on how to fix this?

whyzee said:
CK bro, Mokee v0.3 still has the SOD issue though it uses mock kernel(0.32). Any ideas on how to fix this?
Click to expand...
Click to collapse
Are you sure? While wifi was on?
As far as I know, mOCk and SD and also last TJ's miui kernel have been patched with wakelock if wifi is on.
Or maybe you can use wifi library and driver from miui just to make sure.
If still remain then I don't have an idea for that problem.
Sent from my CSL-MI410 @CKMIUI 2.4.13 using Tapatalk

thanks for the info bro. I am certain that it happened. I'll try again and see.
EDIT
I can't replicate the problem. Though the lockscreen turns on, I'm able to get back without any problems. So I think may be its gone now. thanks anyway.....
UPDATE
fixed sod after using different wifi lib files

natsuke said:
I'm on latest edowar's CM7, got lag issue when playing Temple run on 35.7 kernel, but then after I set the I/O governer to Deadline, and CPU gorvener to smartassv2 or interactive X, it seems better.
From my experience with this rom, the gpu lib is not very good to play HD games (got so much lag when playing Asphalt 6, but not dungeon defender 3), or very much like fast moving graphic game like temple run. I've test to install the older gpu lib from 32.9 kernel (just the gpu lib, not the kernel itself), it gave me back low nenamark2 value, but the lag is gone like 32.9 kernel cm7, however, it seems making the fast locking gps not to be that fast anymore (wonder why, still need to play2 around again).
About the wifi, it really piss me off as it will brings the phone to sleep of death each time it goes to sleep although I set the wifi sleep policy to 'never'. however, the workaround would be to install Advanced Wifi Lock from the market for now.
Click to expand...
Click to collapse
finally someone else who feels the same wayabout the gpu lib!
thanks for the wifi suggestion bro!

[Q] TriNiTy SensationXL V 5.0 Final - Random FC/Reboot?

I've just updated to Trinity v 5.0, but my phone keeps rebooting itself after scrolling the homescreens. I flashed the 1 GHz script and changed the Kernel to Unity v10, now it's back to normal again without reboots.
Does anyone know why this is happening? No one else on Trinity's thread seems to have this problem...

Your CPU cannot handle anything more than 1GHz. That's probably the thing that caused the reboot.
Not all CPU can handle >1GHz due to the nature of the manufacturing process of the CPU, so you are a bit unlucky to get the CPU that can only run 1 GHz max, still its still satisfy what it says on the spec..

wpra3 said:
Your CPU cannot handle anything more than 1GHz. That's probably the thing that caused the reboot.
Not all CPU can handle >1GHz due to the nature of the manufacturing process of the CPU, so you are a bit unlucky to get the CPU that can only run 1 GHz max, still its still satisfy what it says on the spec..
Click to expand...
Click to collapse
Thanks, that's what I thought. But it's only after I flashed the Unity v10 kernel then it would stop rebooting. Is it because the Ruslik kernel that comes with it is custom made for OC? Should I go to Tweaks now and remove OC Daemon then?

I think the Ruslik kernel comes with OC, therefore it reboots every time, just try to make it to 1GHz it should work, if not its probably kernel bug. And you don't have to remove the OC daemon after, just set it to 1GHz and you are good to go.

In TriNiTy SensationXL 4.5 i have a reboot bug in FBReader. If i won't touch the screen for some time the phone will reboot. And in 5.0 final version i have force close in FIFA 12. Anyone else has this problem?