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.

[Q] Why does my hero keep restarting? (Gingerbread 2.3.2 aosp)

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.

Blitzkrieg trouble

FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!

At least you got it installed, I couldn't even get that!
Sent from my Gingervolt-ed VS910 4G using xda premium

Mark Once Again said:
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
Click to expand...
Click to collapse
Was it still unstable if you turned it down to 1GHz instead of keeping it at 1.5GHz?

I never could get that far. As soon as the phone was almost up it would restart. I tried about 5 or six times. I am happy with the phone without Blitzkrieg. Just thought I would pass along the info.
Thanks to all!

Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...

vortmax said:
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
Click to expand...
Click to collapse
I wonder why of all things, that would make a difference. You must've figured that out by chance? Haha
Sent from my Supercharged, Blitzed LG Revolution using xda premium.

I tried plugged into the usb on my pc, plugged into the charger and not plugged in at all. Same result each time. No complaint, just thought it might help having the info out there.
Thanks again!

You might try first installing a CPU utility like setcpu, and setting it to do no more than 1ghz on boot, and then flash it
Sent from my VS910 4G

Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
Turn up the min. That fixed it for me

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
You can turn off the haptic feedback to minimize that vibration reboot but it won't solve the issue tho
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

For those who use blitzkrieg kernel I recommend using cpu tuner instead of setcpu
I've been testing both app extensively for the past 2 weeks and notice cpu tuner is much more stable than set cpu and both have the same features
I use the free set cpu verison that you can download on the xda site that's the same as the paid version you get on the market
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?

I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.

keynith said:
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
Click to expand...
Click to collapse
keynith, try to set the min cpu speed to 768 in setcpu.
So far after changing the min cpu speed i haven't had any issues again.

Did that yesterday and no problems since seemed to work
Sent from my VS910 4G using XDA App

brad08stanggt said:
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
Click to expand...
Click to collapse
Best thing I can say to do is to Restore to default and install things one or two at a time. It's likely an App causing the issue. I have had that happen a few times on my Droid 2 Global. Every time I would run the Goggle Nav App, my phone would randomly reboot. Don't have it installed, would be perfectly fine, until I installed Pandora app. Some buggy apps can cause such issue, and also bad settings. So, I would suggest going the 'long way' and starting from scratch and installing only necessary apps one or two at a time. If things work good, move on to next apps. When things go bad, recall the apps you just installed where the problem occurred. Restore your phone, install only those apps and see if you have reboot issues. If so, you are closing in to finding the real problem. I doubt, even by the post you wrote, that it's the phone or hardware. You need a factory fresh restore, including wiping ALL data, including settings for your apps.
-Cybie

Well?
I don't know if you guys fixed your problems yet, but I kinda had some of the same issues and I do not use CPU Tuner or Set CPU! Also I know that when you install Blitz 1.3 It defaults to normal CPU speeds that are already in phone settings as checked by CPU Spy after flashing Blitz. I have been using Antutu CPU Master Pro to set speeds and profiles works great for the price I use it on my Viewsonic G-tablet as well! Anyway what my first issue is the screen locks I had them all the time and the only way I kept them from happening was to set my min at the 245.76 MHz and my all the time max at 1200MHz. I also set the screen off at 122.88MHz - 245.76MHz On demand scaling profile to keep it not wakening from sleep quick enough. Antutu has all kinds of settings in the Pro version and If you want a overclock I think its the best to use.
The only Issue I have not figured out is you guys get a 10 sec vibrate then a reboot I get a Vibrate forever until I reboot I got woke up this morning at 4:00 A.M. by my phone vibrating next to my bed only happens at night and only when I start receiving emails early in the morning. I tried several screen off settings and not having vibration on at all and still happens figure that one out and I will gladly try anything you come up with!!! The only time it doesn't do it is if it is plugged in and charging!

Softkey lights
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
EDIT: charging to 100% fixed this.
Thanks for the quick reply and all your other posts too mt, they are very informative.

anangelablaze said:
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
Click to expand...
Click to collapse
Charge it to 100% and it will stop

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!

Random crashes and reboots on Thrillseeker 3.1

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