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.

[Kernel] Dragon TEST... SetCPU profiles support...

http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..

Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App

Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?

just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots

coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..

PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try

Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.

Testing now, Just UV'ed my clocks, and now setting profiles.

Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.

Confirmed I can not run this either.

Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App

junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.

yikes ! i smell quadrant score in few min lemme install it

Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.

kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D

bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....

Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.

Touchscreen Issues

Hey guys. Bought my NC yesterday and rooted it last night. I've had no problems at all with it until now. Ever since i flashed honeycomb v4 and set up a dual boot, i've been having touchscreen issues. My screen is becoming very unresponsive. Forcing me to have to tap things many times to get it to respond. Multitouch test app works fine. No unresponsiveness at all. Should i get rid of the dual boot??
Thanks, Brick
Sent from my LogicPD Zoom2 using XDA App

Also i should note that im typing ths from honeycomb, which is having no touchscreen issues whatsoever

Ok now im having issues when pushing the power button to put the NC to sleep. It causes bootloops. Please note that these problems are only in autonooter. Honeycomb works fine
Sent from my...

CM7 Root Issue - Screen Flashing When Turned On

Hi There,
Noob here. I did a CM7 (update-cm-7.0.3-encore-signed) root and everything seemed to go fine except when I turn on the unit, the screen flashes a white color. This is not the entire screen. It does it for a spit second then loads.
I thought maybe I screwed up the device, so I did a factory reset using CWR which did as was supposed to. Once factory reset, it didnt do the screen flash.
I then went and reinstalled CM7 with the same issue occurring.
Any thoughts?
Thanks,
Herschel

That's normal, nothing to worry about. It does that when it switches boot screens.
Sent from my CM7 Nook

Is normal mine dose the same thing , it will do it also when you unlook the screen
Sent from my NookColor using Tapatalk

its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display

TainT said:
its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display
Click to expand...
Click to collapse
That will do nothing for the OP.

Is there a fix for that, it doesn't look good to eyes, when the screen suddenly flashes in full bright white, after the screen starts again after a timeout.
Sent from my NookColor

TainT said:
its configurable. Check in your settings for screen on/off animations.
menu>>>>settings>>>>cyanogenmod settings>>>>display
Click to expand...
Click to collapse
priyank_bolia said:
Is there a fix for that, it doesn't look good to eyes, when the screen suddenly flashes in full bright white, after the screen starts again after a timeout.
Click to expand...
Click to collapse
You two are talking about a totally different issue than the OP, but TainT's post should answer your question, pb. If screen-on animations are not your issue, you'll have to clarify.
Also, as a PSA: installing CM7 is not rooting. You may have rooted (unnecessarily) in the process of installing CM7, but not any and every modification to an Android device is a "root." Rooting is the process of gaining Super-User access to an Android OS on which you were previously denied it. When you install CM7, you are running a completely different operating system in which you already have root access.

For me the screen on/off animations are disabled, still when the screen timeout or when I press the power button, the screen flashes very brightly for a brief time. It looks very ugly and painful at night when the screen flashes.
This is not a device issue as this happens with CM7 only.
I hope that I am clear in explaining the issue now.
Sent from my NookColor

Sorry, I don't get anything like that--if I wake the NC with either power or 'n' it just comes on at normal brightness. I still get the flash horizontally across the screen when powering on the NC, if it was actually powered down (what the OP was talking about). Otherwise, no bright white lights.
What CM7 are you running? 7.0.3? The beta 7.1? A nightly? SD or eMMC?

7.0.3 from emmc.
Sent from my NookColor

Well, you could try grabbing a nightly, or the original 7.1 beta. I know I don't get any weird flashes with those, but I don't really remember if I did with 7.0.3.
Or you can wait--there should be a stable build with the new kernel before too long. I ran the 7.1 beta for over a week, OCed with dal's 5/23 kernel, and it was rock solid stable.

CM7 Nook freezing issues

My nook is booting up fine, but once it gets to the android interface after a couple seconds or minutes, it just freezes and I can't do anything until I reboot. Has anyone else had any similar issues like this?
If this is a repost, I'm sorry just point me in the right direction as I could not find anything.
Edit: This may be linked to beautiful widgets? I have reflashed CM7 twice now, seems to be linked to that.

Yep, BW will do exactly that. Fancy Widgets is a decent alternative for a large clock widget

I've been having a similar problem after I rerooted and installed phiremod. I can rarely even boot up and have a functional tablet. It almost instantly freezes and must be reboot only to do it again.
reeeaaally pissing me off.
---------- Post added at 05:24 PM ---------- Previous post was at 05:10 PM ----------
after about 10 reboots I was able get it running long enough to uninstall beautiful widgets and after another reboot it seems to have solved the problem. Its a bummer though cause it a good app.

I had the same problems with Beautiful Widgets and the BeWeather widgets. I've read Fancy Widgets work and I'm currently using HD Widgets since it has a 4x4 widget and hasn't given me any problems.
Sent from my PG86100 using xda premium

I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)

mondegreen said:
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
Click to expand...
Click to collapse
Are you overclocked? And I assume since you mention SD card, you normally run from the internal storage? And is this a hard freeze while you're using it, or some time later while the screen is off?

1. Not overclocked. Completely pure, just-installed, CM7 with no changes to default settings. No GApps even.
2. I had the same problem when running from internal. Switched to the SD card to see if that would change anything--it didn't'.
3. Hard freeze occurs while using it.
Thanks!

I also had major freezing w/7.1. I flashed the last nightly (11/16/11) and gaaps.
http://download.cyanogenmod.com/?device=encore
Although freezing might happen once in awhile, it's rare now. I only use one widget (wifi signal). Everything else is pretty much default. No overclocking, live wallpaper, themes, etc.
I've downloaded about 20 apps so far.

Yep, it is caused by beautiful Widgets. I had the same thing happen and I posted on their development forums. I was able to get the startup logs and send them to the developer. Then the response was he could not figure out the bug. The logs clear showed a problem when trying to load the bw, but the bug may have been down deeper the operation system.
Not sure. But bummed none the less.....
Sent from my NookColor using Xparent Green Tapatalk

I was having a similar issue. However I didn't have Beautiful Widgets installed. I solved this by going to the Cyanogen CPU settings. I set minimum to 800mhz, max to 1200mhz and the profile to performance. I also checked the SET ON BOOT (can't recall the exact wording.) After a reboot, I haven't experienced any freezing. Hope this helps you guys.

Thanks.
I will give that a try with a beautiful widget on my home screen. then I will report back on my findings.
Update: nope that did not fix the problem for beautiful Widgets. I made your changes, rebooted, added a super clock widget to my home screen, rebooted, it froze. Thanks for the idea, though.
Sent from my DROID2 using Xparent Green Tapatalk

I've been following this thread as I have been experiencing the same thing, I ridded the nook of BW and it hasn't helped the freezing upon boot issue, even knocked up the min setting to 800. I've reflashed a million times. This came out of no where.
Edit: its getting really annoying. This thing isn't even useful. Never occurs with the ics preview. Only with any cm rom.
Sent from my PG06100 using xda premium

Sorry to hear that. The only time I have really experienced freezing, it was always because of some application. Is there some application that you always install that could be causing the issue. I know at one point it seemed like a certain version of flash would freeze mine, even if it was just installed not being used. Are you using the most recent stable build of cm7?
for now I have switched to ics on my nook, just for fun, I wanted to be able to make my own nightlies so I set that up . Will have to try a beautiful widget on there once I make a backup.
Sent from my DROID2 using Xparent Green Tapatalk

same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
---------- Post added at 04:10 PM ---------- Previous post was at 03:30 PM ----------
carlosraf20 said:
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
Click to expand...
Click to collapse
reporting back still freezes , i will install cm-7.1.0-encore-signed.zip stable tonight and see what happens, what oc kernel to go with stable cm?

So for what it's worth currently beautiful Widgets seem to work on nook color ICS without freezing it up. But ICS is still in it's infancy.
By the way are you running off an sd card or Emmc? Running off an sd card is not nearly as good and that can cause a lot of freezing. Just throwing that out there.
Sent from my NookColor CM9 pre-alpha using Xparent Green Tapatalk

Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium

peanjr said:
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
how do u find out it was nook tweaks that was causing this?

Because it always ran just fine, until I installed nook tweaks checked "set on boot" for the cpu settings. I didn't change them, just ticked it. After that, anytime i rebooted, it was a fight to keep it on. So i removed the last thing i put on there, nook tweaks. Its not froze one time and I've rebooted it a whole since then. I reinstalled it but never opened the cpu settings, just edit the audio stuff, no freezes. Kinda wierd.
Sent from my PG06100 using xda premium

I just install cm 7.1 stable and change the kernel to daligrin 603011 and still having freezing issues . I don't want to do it ,but i guess i will have to do a complete wipe and then install cm 7.1 fresh.

Nook Color freezing issues
I too have having freezing issues.
Symptoms: I'll be using my Nook Color with no issues when it suddenly just locks up. No error of any sort on the screen. Screen does not black out. It just locks up. I think everytime it has happened has been after I've transferred several MB (over 5 at least) of data over Wi-Fi.
I'm running CM7.2.0 RC0 KANG build from 11/30/2011 from eMMC.
I'm overclocking to 1200 with the Min CPU set to 800 and the governor set to Performance. I also tried Max CPU at 1100 but that didn't make a difference. I'd had Min CPU at 300 but moved to 800 based on a suggestion found here. Setting the Governor to Ondemand didn't make a difference either.
I do have Nook Tweaks installed but have changed nothing from the defaults and nothing is set to start up at boot time. (I use it to get to USB Host Mode.)
With this build I haven't had any screens of death like I was getting on CM7.1. Just the freeze-ups.
Anyone else seeing a pattern with Wi-Fi?
I've never installed Beautiful Widgets.