Related
Tonight i moved to cm7, if im not mistaken it is the latest nightly thats been release.
Specs as followed: Mod Verision: CynaogenMod-7-08312011-NIGHTLY-G2x
Build Number: GRJ90
CPU Info: ARMv7 Processor rev 0 (v71)
Kernel Version: 2.6.32.45-cyanogenmod
Android Version: 2.3.5
Please give me inputs and thoughts as to which kernal and rom combo would get me the biggest improvments I'm really looking to be wowed as much as i was when i upgraded from my G2 to the amazing G2x now i want more. Sorry for all the run on and this not being short.
Please leave personal information/reviews of your suggestions if you can. i know there will be a few different options and I've been loading the roms and setting everything up and backing up and trying new ones that way i can "Hot Swap" Rom if i want to change on the fly.
Thanks Again,
Jon
The first i have ever tried was the CM7 Nightly Build124 and had running with Faux123v0.4.1 Kernel. Great ROM and wicked fast and ok battery life. Then i moved onto Weapon G2X v2.5 but noticed it wasn't quite as fast as CM7 so i decided i wanted to try a different ROM but with a CM7 base. So i tried Eagleblood 1.9. Fast but wasn't stable and battery life sucked. Then i thought i'd give MIUI a try. After first boot up, i really wasn't feeling the whole iPhone feel...but as i got to play around with the different themes ande theme edits, i thought to myself: this is it. It's the perfect blend of iPhone functionality and simplicity along with Android endless customizations and amazing speed. Now my G2X feels like the best phone out there.
But it's really a personal preference. It's your phone and you want it enjoy it the way you want to.
Oh and its always good to have other ROMS and kernels as backup on your SD card.
yea id definately like to stay away from iphone anything, i really like android , bought my first android when the g1 first came to tmob, and been a fan ever since (tried windows mob 6 and despised how laggy it was) , ive played with iphones and do not like the lay out, i love the simplicity and customization of android roms and all, so id like to stick to something similar just looking for different internals to increase performance and battery life, all the features are fine pretty much , i wish it was as easy as computers just upgrading the ram inside the phone but i highly doubt we can upgrade from 512 mb of ram to 1 gb or more but can miui be swapped away from the iphone look/feel? i tried running cm7 with faux kernal but everytime i attempt to load the kernal zip from rebooting into recovery and loading zip from sd card, i get tossed into a boot loop (lg boot image, then switches to lg boot image with a blue and black loading bar, just keeps swapping back and forth between the two) so i end up recoverying to either my gb stable or a cm7 with stock kernal .
Yes ofcourse. With MIUI you can always run a different Launcher...like Go Launcher Pro or ADW. But the MIUI launcher is what sets it apart from all others...its very easy to customize. Here's the MIUI themes thread: http://forum.xda-developers.com/showthread.php?t=1183979
Oh and to avoid bootloop...whenever you flash a new kernel always wipe cache and wipe dalvik cache. sometimes it helps if you fix permissions as well.
Ill check it out, are you running the faux kernal on the miui rom?
Thanks ill try whiping the dalvic and cache before flashing. And ill check out the miui thread you posted. Is there a faster kernal out there besides faux
The best performance and battery life combo I've experienced so far is CM7 with faux's kernel.
I've tried various different roms so far and my experience has been that anything based on stock LGE roms (such as EB and Weapon), although a big improvement over stock, is still plagued with incompatibilities and instability.
For example gtalk video doesn't work on anything based on stock, and netflix still doesn't work despite the most recent update providing compatibility with all froyo and gingerbread devices. Also because of LG's buggy bluetooth stack, you cant use wii or sixaxis controllers... pretty sillly on a fast phone capable of emulating N64 and PSX without lag and supports HDMI out.
That said CM7 is the best bet as long as you don't mind not being able to use a2dp... as far as I'm concerned its a small price to pay for all the extra functionality, battery life and speed CM7 brings to my phone.
I've also tried some CM7 based roms, but have never seen a big enough improvement to stray away from official CM7 or a kang such as fitsnugly's.
Right now I am using fitsnugly's kang.
As far as kernels go, I've experienced at least a 30% increase in battery life on faux's CM7 kernel maybe more. He has two versions, I recommend the one with the CM battery driver because the DS driver will make you want to pull your hair out.
Also I would recommend getting the July 15th baseband via the lg updater tool. It improves battery life and makes GPS lock instantly.
based on your last post of you bringing up that lge buggy blue tooth driver, i just purchased a new headset, Jawbone Icon, it syncs and connects with my phone just fine but when i attempt to make calls or answer calls no audio can be heard by bluetooth device, and unknown if my speech is heard on the other end. is this a conflict related to the bluetooth stack provided by lge
Jon_Mull said:
Ill check it out, are you running the faux kernal on the miui rom?
Thanks ill try whiping the dalvic and cache before flashing. And ill check out the miui thread you posted. Is there a faster kernal out there besides faux
Click to expand...
Click to collapse
Yur welcome. As far as the fastest kernel, Trinity15 is quite fast too but i always seemed to prefer Faux for some reasons.
so i wiped the davlic and cache, reinstalled the cm7 rom , it loaded right, restarted a second time and went back into recovery , and attempted to load the faux kernal i have loaded on my sd card, i again cleared dalvick and cache, and ran fix permissions, it appears it was going to do boot loop after i restarted but instead got to the s/w ugrading screen, but it sat there for approximately 5 minutes before i decided to restore back to previous settings
Weren't you already running CM7?
Did you flash a newer nightly or something?
Also, make sure the faux kernel you downloaded was the right one. One is intended for CM7 and one is for stock GB, they have separate threads.
If you are sure you flashed the one intended for CM7 and it was the undervolted one, try the standard voltage.
Also based on your post I'm not sure what order you did things in but after wiping cache and dalvik, flash the kernel then fix permissions.
Good luck.
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
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...
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
yellowfuse said:
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
Click to expand...
Click to collapse
Were you using Glitch before, or some other custom kernel? I didn't think cyanogen's stock kernel supported overclock. If you install a new nightly you have to reinstall your overclocking kernel.
I have been using cyanogenmod only. I never purposefully installed a custom kernel then the rom. Just used Odin to root/clockwork and so forth. Never heard of Glitch. Through out all of my custom rom experiences with the captivate I have been able to use the sys. settings or osmonitor to overclock to a max of 1.3ghz. I have tried miui or whatever its called for about five minutes. other than that just cm6/7, then updated to cm9. in the past whatever kernel i had, stayed in effect, i guess.
I will do a search for custom kernels for cm9 on captivate.
I havent seen any yet, but who knows. I am used to simply stunning roms and the moto droid one. That was great! SS/chevy~ would always have links to the latest kernels avail. for the current builds etc. Good job too.
SO... the search continues.
*Mystery: If I cant even change cpu settings in osmonitor (up or down), yet it lets me enable root mode, what does that mean? The greyed out overclocking area in perfomance settings (up or down)???
I need to learn more"!"
As mentioned, glitch kernel b6 is a great ics kernel. Flash over CM9 and install nstools from the market to control all the kernel settings such as oc/uv, voltages etc etc.
Sent from my glitched ICS Captivate using XDA App
The options are greyed out because the stock kernel currently doesn't support overclocking. Glitch is awesome, and Semaphore kernel is pretty nice too.
Sent from my CM9 ICS i897 Captivate
IcyGlitch for OC, and Semaphore for 400MB mem.
Well Glitch has 387 MB of free RAM
both kernels are good
I want my 13 MB! They are unused so occupying them is unforgivable. IcyGlitch is solid kernel, and I hope 400MB will be added.
b-eock said:
Well Glitch has 387 MB of free RAM
Click to expand...
Click to collapse