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.
Related
I am having terrible battery life. Before upgrading to CM7 I never noticed my battery life being bad. That said I have scoured the message boards trying every solution imaginable. I typically lose about 11% of battery every 90 minutes while the phone is in standby. This bad battery life started right when I installed CM7.
What I have tried:
-Installed System Panel and I don't have any rogue apps
-Factory data wipe, cache wipe, battery stats wipe (with and without), dalvik cache wipe -> then reinstall CM7.
-Battery has been bad on Alpha 1,2,6 & 7.
-Tried both suggestions on battery life in the CM7 Bible thread under Battery Issues section
-Upgraded to FAUX kernel Joe's RCU 0.2.0
-Changed CPU to max 1026 MHz.
I have waited 1-2 days before making each change and nothing has helped or hurt the battery.
I am very happy with CM7 with everything except the terrible battery life I am experiencing.
Use standard kernel without oc. It's really really good. Record us almost six days
sent from Sensation with awesome cm7!!!!
wixi909 said:
Use standard kernel without oc. It's really really good. Record us almost six days
sent from Sensation with awesome cm7!!!!
Click to expand...
Click to collapse
I am using Faux kernel with super undervolt. Battery life is still horrible comparing to other roms. maybe I will try using the stock kernel.
jcalifornia, are you also experiencing bad battery life with stock cm7 kernel?
Have you tried a stock kernel, maybe GPU freq is running higher than stock.
c19932 said:
jcalifornia, are you also experiencing bad battery life with stock cm7 kernel?
Click to expand...
Click to collapse
Yes, the bad battery life once I started using CM7. I used it for over 1 week.
tuner562 said:
Have you tried a stock kernel, maybe GPU freq is running higher than stock.
Click to expand...
Click to collapse
Yes, I tried the stock kernel for over 1 week and was experiencing bad battery life the entire time.
What was your battery voltage right before it went dead? I have a feeling that our phones (or just these HTC batteries) are cutting out long before they are truly dead. I notice mine drops out at 3.4v. The battery itself is usually protected from UV at 2.8v. I am waiting for my chichitec to die now so I can compare cutout voltage.
For the record, I was seeing 18-20 hours with CM7 and faux's kernels. 1.56Ghz
Since you have the issue on multiple ROMs/kernels, maybe your battery is bad/defective. Maybe T-mobile can send you a replacement under warranty? I'd call/chat with them to see. Worst they can say would be "no".
One other thing, you wouldn't happen to be using the performance governor?
jayyo said:
Since you have the issue on multiple ROMs/kernels, maybe your battery is bad/defective. Maybe T-mobile can send you a replacement under warranty? I'd call/chat with them to see. Worst they can say would be "no".
One other thing, you wouldn't happen to be using the performance governor?
Click to expand...
Click to collapse
I thought the battery may be bad too, but I was getting great battery life before I went to CM7. Last night I did a "superwipe" and that seems to have fixed the problem. I am down to 71% after 9 hours when before the wipe I would be at ~25%.
I guess you had something hanging around from a previous ROM somewhere. Good luck!
try tiamat kernel + VIpermod undervolting. It helped me a lot
c19932 said:
try tiamat kernel + VIpermod undervolting. It helped me a lot
Click to expand...
Click to collapse
I have been using Tiamat kernel and still getting bad battery life. I flashed Vipermod and when I run su -> vipermod from a terminal it says vipermod: not found.
jcalifornia said:
I have been using Tiamat kernel and still getting bad battery life. I flashed Vipermod and when I run su -> vipermod from a terminal it says vipermod: not found.
Click to expand...
Click to collapse
Yea Tiamat helps a bit but the bad battery life of CM7 is still inevitable I guess.
For Vipermod: (from viperboy's faq page)
Q. I can't find vipermod in /system/bin after flashing in recovery! Where is it?
A. Well, I need to know this! Please contact me via email or post about this in the correct device thread on XDA. Due to the differences in devices and the commands they use to mount /system you may encounter an issue. Here is a workaround:
Manually place vipermod in /system/bin
Use a terminal app and type:
su
chmod 0777 /system/bin/vipermod
vipermod
The script will then run. Please see my note in the previous question to make viperMOD easier to launch.
Click to expand...
Click to collapse
or you can just use root explorer: extract the vipermod file from the zip, place it into /system/bin, change the file's permission manually, and you are good to go
I have tried every radio and my battery life is still bad. If I recall correctly I was also getting bad battery life until the late August OTA and then my battery was great. I think I am going to have to switch back to the stock ROM because the battery life I am getting with CM7 won't cut it.
Try using the app battery calibrator. Or go in your recovery menu and chose advance(I think) and chose clear battery stats. But do this when your battery is full
Sent from my HTC Sensation 4G using XDA App
http://forum.xda-developers.com/showthread.php?t=1187698
Good calibration guide, many have found that the calibration app isn't the only factor in calibrating. All it does is remove a file that Android recreates every boot.
I recently rooted my P999/G2x and installed CM7.1.0.1, and am extremely happy with it. Am looking to tinker just a *little* bit more, but have some questions... I have LOTS of answers on the forums, but am somewhat skeptical about the currency of some of the information out there (let's face it, stuff changes fast!). So, down to it:
Kernels:
- Did CM7 overwrite the stock kernel?
- I understand the benefits to changing the kernel; what about drawbacks?
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
- Recommendations on a good, reliable kernel to use w/ CM7? I am looking at faux123's CM and morific's Trinity. Thoughts?
OC/UV:
- Can you OC on stock/CM7 kernel?
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
Thx in advance!
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Using eagle blood (cm7 based) with faux kernel.
I heard trinity kernels may have random reboot but don't quote me on that.
Try faux kernel with oc/uv. Its very good, latest is 0.48. But if you go with the ds version (debaouch?) The battery percentages are all over the place... Lol one minute its 50% the next it may be 34%...
Use set cpu. I've uv additional 25mv across the board with no I'll effects. Screen off profile at 503 mhz max and some other profiles will have you getting 24hours easily with normal usage.
Make sure test it out before you "set on boot"...
Sent from my LG-P999 using XDA App
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Trinity ELPmax with Phoenixblood is the best combo. Trinity batterylife is amazing. When i leave the house my phones battery is 100%. 11 hours later (I when i make it home) my battery is always under 60% but never less then 40%. I play music as soon I leave the house, and till I get in the house. I also turn of data when not using and have setscpu set to 900mhz max and screen off profile set to 432 max 216 min.
Just my personal results
e4e5nf3nc6 said:
- Did CM7 overwrite the stock kernel?
Yes
- I understand the benefits to changing the kernel; what about drawbacks?
Since not all the chips are made in the same way, you could soft brick your phone if you try to flash an undervolted kernel. This is the way mine is, and it's somewhat irritating but not all that bad using the stock voltage and overclocking to around 1.4ghz rather than 1.5ghz+. Also, battery life should be expected to be less with an overclocked CPU. It's up to you to decide how you want to run your device.
- Does CWM back up your kernel with Backup and Restore? If not, how do you do this?
Yes, backup creates an image of the entire thing. Before you start making changes, always make a backup so you can revert to previous settings should you soft brick your device. Make a backup, clear cache/dalvik, flash the kernel and reboot the phone. First boot times will always be a little longer when flashing a kernel, so be patient and don't pull your battery right away. For me personally, if it hasn't done anything noticeable after about ten minutes, I pull my battery. Reboot into recovery and restore from the backup you made. If you started off trying an undervolted kernel, time to try the standard voltage now!
- Can you OC on stock/CM7 kernel?
No, and you'll be able to tell once you flash CM7 and use SetCPU (or whatever you use) and see the max is still at 1ghz.
- What is the best app to manage OC/UV? I have my eye on setCPU, cpu Master, and Android Overclock (JRummy16)
Personal preference. I think probably SetCPU is used by most people including myself.
- Any recommended settings for the G2x? Any settings to avoid? My plan is to incrementally adjust, but don't really have an idea as to where to start.
If you want to be safe just start out at 1ghz. If you have no random reboots with your kernel then move it up to 1.1 or 1.2 and see if it's stable there. Personally, I just went ahead and overclocked to 1.4ghz. For the most part people don't really have problems with this I guess. The problems usually lie in whether or not you are undervolted and by how much. If you find your device can run an undervolted kernel, I would just leave the undervolt settings the way they are. As I said, I can't run OC/UV and have to use SV, so I never touch any of the voltage settings.
Hope this helps!
Click to expand...
Click to collapse
+1 to everything you said
just to add if you want to over clock then go with faux or trinity. the cm7 kernel is faster then both @1000mhz, if speed is what your looking for without the dangers of oc. The stock cm7 kernel also lacks the ability to under volt soo battery life might not be as good though
Rbern144 said:
I tired using DS OC/UV Kernel Version 0.4.8 kernel on my g2x running the latest stable release of CM7 1.0.1. Followed all the necessary step of wiping cache, and darvik but when I reboot, I get the blue lg sign after which the screen just black out and its stuck like that till i pull the battery out. Any one know what I may be going wrong here? ? ?
Click to expand...
Click to collapse
Format data/ factory reset.
Wipe all cache.
Format system. (don't forget)
Flash cm.
Flash kernel.
It may take a while for the system to boot, 5 min. Let it load, and reboot, enjoy.
Sent from my LG-P999 using XDA App
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.
So, after trying out many other roms, I've come to the conclusion that WeaponG2x is the one that works for me. However, I was also wondering if it was stable and smooth because of the stock kernel or is it the rom?
I've been using Weapon for a week and a half now and it runs smoothly, never crashes on me, never have to pull battery, and I did realize that battery was better than the previous roms.
Now I want to know if I should use any other custom kernel(overclocked or not)? The roms runs great, except I noticed that it lags a bit here and there, but not too much. Like when i'm downloading an app, the screen will be still for like 1 milisecond when it's installing. That's probably the trade off for the decent battery life, but I'm not sure.
So what kernel are you guys using with Weapon? Let me know, I've been thinking about using Faux kernel, overclock it to about 1100 with SetCPU. But im worried it'll have a major impact on battery life.
Thanks.
NekoNyapii said:
So, after trying out many other roms, I've come to the conclusion that WeaponG2x is the one that works for me. However, I was also wondering if it was stable and smooth because of the stock kernel or is it the rom?
I've been using Weapon for a week and a half now and it runs smoothly, never crashes on me, never have to pull battery, and I did realize that battery was better than the previous roms.
Now I want to know if I should use any other custom kernel(overclocked or not)? The roms runs great, except I noticed that it lags a bit here and there, but not too much. Like when i'm downloading an app, the screen will be still for like 1 milisecond when it's installing. That's probably the trade off for the decent battery life, but I'm not sure.
So what kernel are you guys using with Weapon? Let me know, I've been thinking about using Faux kernel, overclock it to about 1100 with SetCPU. But im worried it'll have a major impact on battery life.
Thanks.
Click to expand...
Click to collapse
That lag when installing apps is an Android problem, not ROM. I believe Google fixed that in ICS. If it ain't broke no need to fix it is what I believe, so I say just stick with what kernel you already have.
But if you really wanna try something new then try the Dragon Kernel that was repacked by Mr.Apocalypse. Or you can try Faux's. But make sure you try the one that's for the 2.3.3 GB OTA by Faux, not the CM7 version.
Stay with stock kernel. Since no drivers for the kernel were ever released, technically stock is the best aside from the tweaks, but then it becomes a sort of ported kernel.
buru898 said:
Stay with stock kernel. Since no drivers for the kernel were ever released, technically stock is the best aside from the tweaks, but then it becomes a sort of ported kernel.
Click to expand...
Click to collapse
Stock kernel is good, I think that's the reason my battery life was great. But I'm gonna stay with Dragon and see how things go.
Wooooooo, im rocking faux's kernel repackaged by loterious for faster boot times.
Sent from my G2X
You will get best battery life/stability on your stock weapon kernel. If you want to oc go with faux but prepare for noticible bad battery life.
P.s. try pheonix blood on stock kernel way better imo
Making bad decision's one at a time.
I.R.Chevy said:
You will get best battery life/stability on your stock weapon kernel. If you want to oc go with faux but prepare for noticible bad battery life.
P.s. try pheonix blood on stock kernel way better imo
Making bad decision's one at a time.
Click to expand...
Click to collapse
I love PhoenixBlood, but I like Weapon better, it seems more stable, everything works!
NekoNyapii said:
I love PhoenixBlood, but I like Weapon better, it seems more stable, everything works!
Click to expand...
Click to collapse
Wise choice. Weapon is a great rom. Back it up and try "new clip". Follow the instructions and give it time to settle. There is a new updated weapon rom coming soon. In new clip you will get fast GPS locks. Fast/quick interface. Very nice. The one quibble is clock placement.
jcbofkc said:
Wise choice. Weapon is a great rom. Back it up and try "new click". Follow the instructions and give it time to settle. There is a new updated weapon rom coming soon. In new click you will get fast GPS locks. Fast/quick interface. Very nice. The one quibble is clock placement.
Click to expand...
Click to collapse
New Clip*
I ran weapon r1 and new clip and you are right both are the bees knees. The gps fix in new clip was an unreal change in fix time as well! Good luck with the weapon!
Making bad decision's one at a time.
I have always used weapons and Faux is the way to go. I use setcpu and I run my processor at 1.552 when the screens on and. 389 when its off and I get over 15 hours per charge with moderate use. Just customize the profiles in setcpu to your liking.
Weapons for life!
What exactly is this "New click"? Is it a new weapon mod?
Anyways I have been using weapon r1 3.0 for about a week now, everything is stable and smooth, however gps isnt exactly the fastest, often it doesnt even lock indoor (which, my old phone does). Takes roughly 15s-1m to get a lock outdoor too. I personally think that is slow.
Other than the gps, i am fairly satisfied with the WeaponG2x_30_R1_1022.
hhwong said:
What exactly is this "New click"? Is it a new weapon mod?
Anyways I have been using weapon r1 3.0 for about a week now, everything is stable and smooth, however gps isnt exactly the fastest, often it doesnt even lock indoor (which, my old phone does). Takes roughly 15s-1m to get a lock outdoor too. I personally think that is slow.
Other than the gps, i am fairly satisfied with the WeaponG2x_30_R1_1022.
Click to expand...
Click to collapse
Sorry for the typo. It is "New Clip". New Clip is new revision by Kwes1020. He has taken ownership of the rom now that the original dev no longer has a G2x. GPS is much improved and the entire interface has been tweaked for a smoother faster response. It is flashed over Weapon from CWM. It retains all your settings, apps etc. It is a worthy upgrade. Soon there will be an all new version of Weapon, but for now it is the best solution.Try it, you will like it.
Yep... I've tried about 3 or 4 roms before I came up weapon.... This is definitely the most stable by far. Have no issues with it in about 3 weeks now. Also don't suffer from the SoD anymore either.
Tried CM7 Stable looked nice but had SOD issues on lock
then i used root explorer to flush out the bloat ware and ran that for a few hours and backed it up and installed
weapon_r, only problem seemed to be if i rebooted i had to re install from backup need for speed and the nova demo. or they would crash boot on start. but
just flashed new clip and after reboot no lockup on need for speed or nova!
love this rom.....everything works and lots of options. nice and fast (maybe too fast) i was used to a ginger lol optimums t that i gave to my mom after disablement of data(she can use wi fi) i'm not paying for a data line for her.
I tried out faux's kernel but I don't like it. Either it's the kernel or setcpu's default values, but my phone keeps turning off randomly over night.
How do I go back to weapon's kernel without flashing the whole rom again?
id3alistic said:
I tried out faux's kernel but I don't like it. Either it's the kernel or setcpu's default values, but my phone keeps turning off randomly over night.
How do I go back to weapon's kernel without flashing the whole rom again?
Click to expand...
Click to collapse
Boot into CWM
Flash Weapon
Flash New Clip (optional)
Wipe cache
Wipe dalvik cache
Reboot
All settings should be retained. I remember reading somewhere that when you change kernels, you should go into application management and clear data and cache from SetCPU or some of the old settings will be used. Not sure if that's true or not. And actually, maybe that was the original problem for you on faux's kernel. *shrug*
I didn't have SetCPU prior to faux kernel... I wanted to try overclocking and my phone would randomly shut off. So I just left the values at default and it still did it.
Bumping since I have another question.
Every now and then on the home screen, when i try to slide to the next screen, the screen will pan out and show all of my home screens instead. I'm not sure how to change it back without rebooting.
Anyone know what I might have did?
id3alistic said:
Bumping since I have another question.
Every now and then on the home screen, when i try to slide to the next screen, the screen will pan out and show all of my home screens instead. I'm not sure how to change it back without rebooting.
Anyone know what I might have did?
Click to expand...
Click to collapse
If your using go launcher you can set the swipe up and swipe down on your homescreen to do stuff I disable it cause its annoying.
Edit: On your homescreen (assuming you have go launcher) > preferences > gestures > glide up > select the option 'disable'
Make sure you do the same thing with "glide down" option.
Pin it to Win it.
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...