I'm having an annoying issue with my Charge. Whenever I try to record with the Camera the phone just freezes and reboots after about 10 seconds. Yes I'm undervolted, which is what I'm suspecting as the issue but I went into Voltage Control and set the voltages back to 0 and to no avail, it still just froze and rebooted. I tried overclocking to 1.2Ghz without undervolting that clock speed at all(1GHz and below were still all undervolted) and it still just froze and rebooted.
The weird thing is this happens on the stock undervolt settings that the kernel comes with. I'm going to assume Imnuts' just didn't have the time to test all the apps individually for stability issues when implementing his undervolt script. I know it's an issue with the kernel(almost positive it's from the undervolting itself because i had stability issues exactly like this back on EE4 when i would undervolt) because if I reboot and flash imoseyons 4.0.0 kernel recording is fixed.
edit: I just tried removing my Voltage Control boot settings so there shouldn't be any undervolting going on(aside from the stock undervolt script thats included with the kernel) and it still just freezes and reboots. I'm guessing it's either the undervolt script or the kernel itself. Anyone else have this issue? If so how'd you fix it? Thanks in advance.
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
mromblad said:
just tested. i use the default uv settings, oc to 1200.
camera was able to record fine. no freeze.
Click to expand...
Click to collapse
How long did you let it record? and was it on 1280/720? It usually freezes on me after about 10-20 seconds
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
adrenaline_rush said:
I just tried to record.. Freezes after 4 seconds reboots just like you described. Eclipse ROM+PBJ 1.15 kernel. Oh also no overclocking at all for me
Click to expand...
Click to collapse
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Mine did the same thing and I am just using the kernel and the new eclipse
Sent from my SCH-I510 using xda premium
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Also getting freeze-up when trying to record HD vid.
Running Tweakstock 1.1 and PBJ 0115
edit: *UPDATE* - I just flashed Imoseyon's 4.0.0 kernel to test, and HD recording worked flawlessly. So it does seem to be the kernel which is causing the issue (in my case at least). Can anybody tell me how to pull a logcat so I can send it over to imnuts?
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
Where did you find the kernel? Everything works great except the video.
Does anyone know of a stock, rooted version?
Sent from my SCH-I510 using xda premium
shrike1978 said:
That seems to be an issue with Eclipse rom. A lot of people are having that problem and nitro is aware of the issue and says the next version will have a fix.
Click to expand...
Click to collapse
I believe it's an issue with Imnuts' 1/15 kernel, not the ROM.
cujo6801 said:
just tried hd vid. on eclipse w/Imos 4.0 kernel with no problem....
Click to expand...
Click to collapse
See anyone running Imos kernel doesn't have the issue so I don't believe that Eclipse is the problem, although it is still possible.
dwitherell said:
While I never use the camcorder at that resolution, I tried it now and had the same freeze-up. Running tweakstock (fancy that lol) and pbj kernel - I tried this without any voltage control-style modifications. I have some vague recollection of similar issues at some other point, and for some reason I remember the class of sdcard being part of the conversation... I of course can be (and most likely am) completely off on that, just thought I'd mention it.
Click to expand...
Click to collapse
Yeah I remember back when Gummy2.0 was released I had that issue. I know it's not the same thing though because whenever I would record it would give me an error message like "This SD card does not support HD video recording" or something like that and it would just close the camera app, it wouldnt just freeze and reboot.
shrike1978 said:
I remember that class 2 cards can't do HD video, but class 4's are supposed to be able to. I never do video, but I have a class 4, so I tried to see (on Eclipse) and it crashed to the point of forcing a reboot. Not sure now if it's ROM or kernel.
Click to expand...
Click to collapse
I'm positive it's not a problem with the SD card. I'm on Tweakstock so for now it's to be assumed that the kernel is the problem since cujo6801 already tested Eclipse with Imos kernel and had no problem, but adrenaline_rush tested Eclipse with Imnuts' kernel and it froze/rebooted. Pretty sure it's a kernel issue at this point.
jimc5423 said:
I have been running the pb&j 1/15 kernel and Infinity rom for a day now with no freeze-ups or reboots. I haven't messed with OC'ing or voltages, just wanted to see if the new kernel made a difference. The phone is now much smoother in operation and quicker in response. Very impressive.
I saw this post and walked around the house scanning barcodes using shop-savvy and had no issues at all. This app does a lot of stuff on top of using the camera and just flies now.
Click to expand...
Click to collapse
Try your actual Camera and attempt to record video @ 1280/720, then tell me if it reboots.
I got the freeze and reboot every time with Eclipse and PBJ at 720p. Flashed Tweakstock with PBJ and it worked. Then tried Eclipse with the ep4d kernel and that worked too. I thought it might be the camera so I copied the one from from Tweakstock into Eclipse and 720p recording worked fine undervolted and oc'd to 1200.
Edit: Tried it again since reflashing updated Eclipse and it locked at 10 seconds. Guess I was lucky last time. Shot multiple 45 second plus videos ok.
Sent from my SCH-I510 using XDA App
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
kvswim said:
Just tried on mine. Eclipse with PBJT kernel, froze instantly.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Same config and instant, several attempts.
benb1974 said:
Same config and instant, several attempts.
Click to expand...
Click to collapse
Tweastock with PBJ freezes and reboots on mine too. Never froze on Tweakstock with included kernel
Checked the comments on Imnuts' kernel over at RootzWiki and i can confirm it's a problem with the kernel, in addition to that the HDMI port doesnt seem to work.
I have been getting froze screens and 1 reboot also, since running imnuts kernel. I thought it was maybe the ROM but doing a little research IM finding the kernel has an issue. I didn't try the camera with imnuts kernel but I've flashed imo 4.0 kernel and the recording does work w/o force closing on me.
Sent from my SCH-I510 using XDA App
Also be careful overclocking on PBJ, I set it to 1600 max on SetCPU, and after a few moments it froze and rebooted. When it rebooted, as soon as SetCPU was granted SU, there goes another freeze. I wasn't able to change the settings due to the freeze, and after a few reboots I was taken to the setup screen like you would see after a factory reset. But this came with random F/C errors and lots of non-functional apps. You can't do anything at this point but restart from stock+PIT and go up from there. Reflashing the ROM, kernel, restoring, even ODINing another ROM won't rid the F/C hell.
Same thing as this, when I tried to use the Voodoo screen tuner:
http://forum.xda-developers.com/showpost.php?p=21629058&postcount=176
Oh also people stated imyosen kernel was a battery drain, but it's been very good on battery so far.
Related
Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?
No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...
Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?
Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Mines running fine. Maybe try reflashing?
jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.
How is CM7 working now? when I had one, it would drop data, boot with no data, and the battery drivers were all screwed up...how is it now? Have a lot of the mistakes been corrected from the original G2x's that were shipped? (reboots, data drops, etc)...??? Any help would be appreciated. Tired of this Single core phone, and found a good deal on a G2x.
mm0
muzicman0 said:
How is CM7 working now? when I had one, it would drop data, boot with no data, and the battery drivers were all screwed up...how is it now? Have a lot of the mistakes been corrected from the original G2x's that were shipped? (reboots, data drops, etc)...??? Any help would be appreciated. Tired of this Single core phone, and found a good deal on a G2x.
mm0
Click to expand...
Click to collapse
Mine is working great.. Came running 2.3.3 with no problems. I rooted and left stock rom for awhile still no problems. Then flashed faux123's oc/uv kernel ran fantastic. Tried a few different roms and settled on triggers 8/22 2.3.5 rom with faux123's oc/uv kernel as my daily driver with no problems so far...
Sent from my LG-P999 using xda premium
Running the CM7 nightly on my G2x for past two days. Haven't noticed any problems. Been stable, battery life is good.
The APN Issue is still there, but it no longer drops data. Battery life is AMAZING now.
I couldn't deal with the piece of **** iPhone 4. I came running back to the G2x. Ive kept it stock so far and it's amazing!
Sent from my LG-P999 using XDA App
I've been running MIUI. WiFi Calling isn't working yet (which sucks) but I'm using Faux's 4.2 Kernel and getting great battery life and very little issues.
With Faux's kernel, WiFi will sometimes fail which requires a restart, and sometimes using USB Mass Storage will lock up.
Sounds bad, but aside from WiFi calling not working, the other issues are pretty rare.
player911 said:
I've been running MIUI. WiFi Calling isn't working yet (which sucks) but I'm using Faux's 4.2 Kernel and getting great battery life and very little issues.
With Faux's kernel, WiFi will sometimes fail which requires a restart, and sometimes using USB Mass Storage will lock up.
Sounds bad, but aside from WiFi calling not working, the other issues are pretty rare.
Click to expand...
Click to collapse
Also running MIUI, runs great, some FC (music player) but mostly its pretty stable, my favorite rom thus far.
Just picked it up...it is currently running Warrior rom...is it any good? Seems ok so far, but it's only been 30 minutes or so...
mm0
muzicman0 said:
Just picked it up...it is currently running Warrior rom...is it any good? Seems ok so far, but it's only been 30 minutes or so...
mm0
Click to expand...
Click to collapse
hahahahaha warrior??? im pretty sure u mean the weapon rom
yep...not sure why I typed that...anyways...know much about stability of that rom?
muzicman0 said:
yep...not sure why I typed that...anyways...know much about stability of that rom?
Click to expand...
Click to collapse
yes one of the most stable roms, it is based off stock 2.3.3 but imo way better with the edt tweaks such as lockscreens and battery configurations, very fast and reliable
By the way. Has the reboot issue been fixed if i flash the newest weapon?
Sent from my HTC Glaicer using XDA App
I'm running jboogies 2.3.3 right now with fauxs 1.3 kernal ... Its his first g2x rom. I guess he usually devs for motor but I haven't had any problems .... Fits has a real good kang out right now with some awesome lockscreen rings... but he's not posting here so you have to Google for it...
formeforfree said:
By the way. Has the reboot issue been fixed if i flash the newest weapon?
Sent from my HTC Glaicer using XDA App
Click to expand...
Click to collapse
For me, I had absolutely no reboots at all on the newest version until I went and flashed Faux's OC/UV kernel. To be fair, my battery life is plenty better, just a little unstable. Weapon by itself is amazing.
EDIT: Forgot to say I came from 2.3.5, so I came from a complete wipe.
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Which ROM are you using?
Oops. Sorry. CM 7.1.0.1.
hadoob024 said:
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Click to expand...
Click to collapse
Faux has 2 kernel versions.... one that is PRE-Overclocked and PRE-Undervolted; and the other that is starts with stock speeds and voltages.
I've NEVER been able to get the pre-OC/UV'd kernels to work on any of the several phones I have went through. I get EXACTLY what you are getting now, just a black screen and unable to boot.
Download his "SV" rom. That is his kernel that starts off with stock settings. You'll get all the features and you can OC/UV manually.
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
You'll get all the features and you can OC/UV manually
Click to expand...
Click to collapse
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
hadoob024 said:
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Sent from my Calculator with Android.
jose makalolot said:
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Click to expand...
Click to collapse
Are you talking through Settings->Manage Applications->SetCPU?
hadoob024 said:
Are you talking through Settings->Manage Applications->SetCPU?
Click to expand...
Click to collapse
Yes.
Sent from my Calculator with Android.
jose makalolot said:
Yes.
Click to expand...
Click to collapse
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
hadoob024 said:
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
Click to expand...
Click to collapse
Never mind, mods please delete.
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
jamadio said:
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
Click to expand...
Click to collapse
Hmm.. Interesting. I'll keep an eye out for it. Today's my first full day with that combination of mod and kernel. Other than the weird battery charge amount readings, it seems to be stable with a better battery life than the CM kernel. Wish I could mess with the voltages too to try and eek out even more battery life. Oh well though.
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
jamadio said:
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
Click to expand...
Click to collapse
No kidding??? Nope. Hadn't heard about that. Will give that a shot late night tonight after I fully charge it when I get home. Thanks for the tip!
Any thoughts on this issue with SetCPU and not being able to access the "voltages" tab?
I went back and read over from the beginning of this thread to refresh myself. Two reasons come to mind:
1. It could be because I don't think Faux's SV kernel is optimized/set up to have it's voltages changed. On his OP, he won't even troubleshoot problems unless they're on the SV kernel. Hence, it makes sense not to give people the freedom to OC/UV it so they can't complain about problems they made for themselves.
2.It could also be SetCPU, I know other's have gone to Pimp My CPU (You can search it on XDA) because PMCPU was built from the ground up to OC and UV, but it's features outside of that are sparse. But eventually SetCPU caught up and is the No.1 for OC/UV.
Maybe giving Pimp My CPU a try wouldn't hurt, if it doesn't work than you know that the kernel won't allow it.
Cool. I guess I'll give this current combo a try and see if I even feel the need to mess with voltages. Got pretty good batter life today so far. Going to go home, charge the phone fully, wipe the battery stats and then resume testing.
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
hadoob024 said:
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
Click to expand...
Click to collapse
No problem. Yeah, that's what makes SetCPU so legit. I don't believe Pimp My CPU has that feature. Just establishing max, min, and their voltages. Could be wrong though.
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
hadoob024 said:
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
Click to expand...
Click to collapse
Any update?
I'm going to have to try later this evening or tomorrow. I forgot but when doing app updates, CW ROM Manager got updated. Anyway, I guess this update did something because when I tried rebooting into Recovery, it never did, it just rebooted normally into CM.
I finally launched CW ROM Manager, chose to "Reboot into Recovery", it then asked for su permissions (or something) and finally worked. Anyway, I rebooted like 4 or 5 times before I realized that this was the issue preventing me from rebooting into Recovery like I normally do. That put enough of a drain on the battery where I didn't want to wipe the battery stats <sigh>
And of COURSE I didn't bring my charger
Will try again this evening and post the results.
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
I was this kernel for a couple days and it was almost perfect. However after a couple hours voodoo sound app would tell me the rom author broke the app and the kernel didnt support voodoo sound. I tried googling but no real answer as to how to fix it.
I downloaded the voodoo app from the devs site and uninstalled the one I had installed from play store. After I installed the app everything worked for a couple hours then the popup message about it being broke. A reboot would solve it but shortly after it would break.
This only happened on the versions with oc/uv natively activated. Finally used gremlin remover and started over. Only I flashed v1 and the voodoo app from the dev site. So far everything seems good.
Has anybody else noticed this? I like the voodoo sound processor better than dsp or the beats audio ports.
yes, also when there was no voodoo sound, just voodoo lagfix. Sometimes reinstalling the Voodoo app from market fixes this, sometimes you have to reinstall the rom. I think files get corrupted.
I seems that Supercurio (author of Voodoo Sound app) checks if his app was installed from market, even if it's free. This means that this app cannot be pre-installed with a ROM, it has to be downloaded by the user. Nothing really bad about it, just uninstall with Titanium and reinstall from market.
I think I figured it out. I could reproduce the results by using tegrak on the oc/uv native kernel like you would on the non-native oc/uv kernel.
@AntonX yes it is to avoid the cracked apps from being used. However he also has the app listed on his own site.
Hey, I have a question: Why don't we use NoLED instead of BNL as NoLED is free, too and it doesn't drain battery so much (I'm using it and still get 15+ hours w heavy use - always OC to 1.4)...so, What is the advantages of BNL over NoLED? (Have everyone ever tried NoLED?)...
daothanhduy1996 said:
Hey, I have a question: Why don't we use NoLED instead of BNL as NoLED is free, too and it doesn't drain battery so much (I'm using it and still get 15+ hours w heavy use - always OC to 1.4)...so, What is the advantages of BNL over NoLED? (Have everyone ever tried NoLED?)...
Click to expand...
Click to collapse
NoLED has never really required kernel support. I've tried it and didn't like it. Your screen stays on, it drains you battery. I've also tried BLN (BackLightNotifications), my screen stays off and my battery drains less than with NoLED. Now users have a choice, they can use whichever one they wish. User demand for BLN is higher because it's better.
Ya, I see, at first I also had the sreen always on but seem like it had option to turn of the screen use the sensor so when in pocket or be up side down, it not drain much, anw just bcause of your post, I will go and test BLN now and will mark on battery drainage btween BLN and NL w srnsor option thanx u
Sent from my 8-bit NES
I prefer NoLED too. In my experience the difference in battery drain is negligible. I just got used to the customized notifications that NoLED provides. Being able to tell what type of notification I'm getting without having to unlock the phone is very useful.
Sent from my SGH-T959V using XDA
Hi guys
I have found that all AntonX's kernels after ver. 1b3 are having trouble to have more than 65MB RAM free working with Adrenaline Shot 14.1.
On ver. 1b3 I have 118MB RAM free without a problem.
For me it is fine, since I couldn't care less about UV/OC. Phone is already fast & battery drained as it as.
Sent from my SGH-T959V using xda premium
If i'm using VB final, what's the ideal kernel for me to use, to OC my phone?
So I just installed re installed tegrak today to boost up to a 1.2 (that's what I've always run). When I opened it I found it was already clocked at 1.4? I thought you had to enable the OC before it took effect?
Bassmanjames said:
... thought you had to enable the OC before it took effect?
Click to expand...
Click to collapse
I'm pretty sure that tegrak will see those higher frequencies regardless if you've set them... It should limit itself to whatever you set under governor scaling
Sent from my SGH-T959V using xda premium
so real odd issue. If Im plugged into my computer charging app that run off the sdcard will not load. The sdcard is still mounted icons show up just fine but various apps will not load or lag. As soon as I unplug it they will load perfect. This only happens with usb charging.
v1.1rc3.test2 on unnamed rom.