I have just installed the CM10 -20121129-Nightly-d2vzw. This is the first time I have tried the custom rom route. I must say I love CM10 and glad I made the move but I have having a few issues that are really bothering me. First I am getting terrible battery life, would a different kernal help? And secondly I am having screen off troubles. When ending a call I a m having trouble hanging up and getting the screen back on. I am running kernel version 3.0.48-cyanogenmod-ge67063c
Battery life with cm for me seems to be bad as well. Try ktoonz kernel it can't hurt. Report back if it helps. I'm guessing cm's kernel isn't quite optimized yet for this device. Best kernel I've tried is stock obviously on a TW ROM
Related
hey, ive been trying to figure out which custom rom + kernel combination should i use but in every rom i'm reading some or the other complaining about something not working, losing signal, or sudden batttery loss, random reboots
is ther a reliable custom rom out ther ? .. because i dont wanna miss out on an important call or message or e-mail at the right time
i really liked what brainmasters miui and kelmsking have done with their roms but still even though its written stable but users aint feeling it to b stable.
i wud like ur opinions on this, and also if u all could help me find a stable rom like the stock one. i am always travelling so i cant afford to have a buggy phone cuz i wudnt have time to go to my computer to do something about it.
i know i have read it many times ther is no best rom cuz its personal choice, but still i want to knw more about stable roms
GPA18
Sent from my Nexus S 4G using xda premium
What's GPA18? I just got my S a week ago, I downgraded from a HTC Sensation and I'm going to use this for a while until Ice Cream Sandwich comes out, but I'm using OXYGEN's rom right now. Stock kernel it comes with and everything, and it's pretty stable for me, great battery life, sometimes I lose data but that's because of the radio update, but other than that, it's great.
gpa 18 is peter alfonso rom, gpa 18 is still not stable though ..
Hi,
I tried CyanogenMod7 (Nightly Builds and Stable version 7.1.0), MIUI (latest version) and Oxygen 2.3.1.
CM7: This is a great ROM but I got random reboot or asking my PIN code. I only have Google Apps, nothing about G+ 2.0 or GWallet. I got those issue since a while on Nightly Builds.
MIUI: if you like IPhone style, this is a great ROM too. None reboot.
Oxygen: this is also a nice ROM. You need to custom it with Go Launcher, GO Weather, GO SMS, DSP Manager... because this is a little raw but, nothing to say only stable.
Performances are pretty good.
There is also NSCollab ROM which is built off Cyanogen Mod,and its a combination of both stock and Cyanogen which I've found to be more stable probably cause of the kernel I.e Matr1x which is built off the stock kernel
I'm using NSCollab 1.0.50 right now and I haven't had any issue yet
I tried netarchy and Trinity kernels with NSCollab but matr1x seems to be the best with NSCollab, gives me a Quadrant of 3000 at 1Ghz
Sent from my Expensive Magical Brick.
Brainmasters MIUI is my fav. No reboots no signal loss when installed clean.
Sent from my Google Nexus S 9020a
You could go stock deodexed, zip-aligned and with newest radio. You could play with kernels for BLN, Voodoo, and OC. Stable but with a few goodies.
Sent from my Google Nexus S 9020a
I'm running opensensation cm9 (latest version). the last few builds have been hell on my battery, on a full charge im getting 5 hours with no wifi bluetooth and so forth. my phone like overheated today and took forever to finally boot back up. someone mentioned switching kernels, idk anything about how that works or which ones are safe to use on which roms. any help would be nice. thanks.
Installing a kernel is done the same way you flashed the rom. Flash the zip file in your recovery.
I think your choices right now are either stock opensense kernel or faux's cm9/aosp kernel. Also, I don't think developers release kernels dangerous for your phone. Worst case scenario your phone gets stuck in a bootloop and you have to go back to stock kernel or reflash your rom.
Just keep in mind that a rom like that which is in alpha stage will have bugs that won't be fixed by just switching kernels. Luckily Vorbeth has been working nonstop on Opensense. One would think he was getting paid to dev.. Lol
Sent from my HTC Sensation Z710e using Tapatalk
I don't really recommend switching kernels since Vorbeth has done kernel-level fixes for OpenSensation. Flashing a different kernel has a good chance of breaking something in the ROM...until the wake lock issue is figured out, I suggest using a stable Sense ROM like Android Revolution HD or Virtuous Inquisition if you still want the ICS AOSP look.
I have been searching for related issues to no avail.
Has anyone experienced graphical errors with roms that are running custom kernels? This seems to happen to me with any rom that has a custom kernel or whenever I install a custom kernel (one without any known issues) onto a rom. The latest would be related to incubus' latest ICS with the Ktoonz integrated kernel.
The errors start with a "loading swirl" that will glitch out from time to time, and eventually my icons and menus will stop showing up. This is using stock settings on the kernels. The problems are the exact same no matter the rom, as long as a custom kernel is being used.
I get these problems even after full wipes and md5 checks, could this be hardware related?
Thanks for reading, this is driving me nuts as I have always been a hardcore OCer and it's really bumming me out that I can't tweak my S3
Any suggestions or ideas, let me know !! :good:
madeiracam said:
I have been searching for related issues to no avail.
Has anyone experienced graphical errors with roms that are running custom kernels? This seems to happen to me with any rom that has a custom kernel or whenever I install a custom kernel (one without any known issues) onto a rom. The latest would be related to incubus' latest ICS with the Ktoonz integrated kernel.
The errors start with a "loading swirl" that will glitch out from time to time, and eventually my icons and menus will stop showing up. This is using stock settings on the kernels. The problems are the exact same no matter the rom, as long as a custom kernel is being used.
I get these problems even after full wipes and md5 checks, could this be hardware related?
Thanks for reading, this is driving me nuts as I have always been a hardcore OCer and it's really bumming me out that I can't tweak my S3
Any suggestions or ideas, let me know !! :good:
Click to expand...
Click to collapse
Since you said your not running any overclocked GPU kernels (Correct?) that could cause artifacts and other related glitches, it sounds to me like that is a hardware issue. What kernel are you currently running, cause if you provide me a link to it I can double check the change log for you and make sure you didn't accidentally miss any problems that were reported or bugs .
shimp208 said:
Since you said your not running any overclocked GPU kernels (Correct?) that could cause artifacts and other related glitches, it sounds to me like that is a hardware issue. What kernel are you currently running, cause if you provide me a link to it I can double check the change log for you and make sure you didn't accidentally miss any problems that were reported or bugs .
Click to expand...
Click to collapse
Not running a kernel with an OCed GPU afaik. I have had issues running any of beans custom stock roms when I select the custom kernel in aroma, all of imoseyens custom kernels have caused the same graphical error, and running incubus' latest "[ROM] JellyBomb ICS [VZW] [VRALHE] [RLS3] [10/21/12] By Incubus26Jc" with the integrated ktoons has also caused the same graphical glitches.
I am assuming inc is using the latest ICS version found here http://forum.xda-developers.com/showthread.php?t=1853816
No one else seems to be having these issues except one person I stumbled across in a beans thread a while back. I sure hope it's not hardware
I'm having a similar error, except with certain games.
madeiracam said:
Not running a kernel with an OCed GPU afaik. I have had issues running any of beans custom stock roms when I select the custom kernel in aroma, all of imoseyens custom kernels have caused the same graphical error, and running incubus' latest "[ROM] JellyBomb ICS [VZW] [VRALHE] [RLS3] [10/21/12] By Incubus26Jc" with the integrated ktoons has also caused the same graphical glitches.
I am assuming inc is using the latest ICS version found here http://forum.xda-developers.com/showthread.php?t=1853816
No one else seems to be having these issues except one person I stumbled across in a beans thread a while back. I sure hope it's not hardware
Click to expand...
Click to collapse
Recon0212 said:
I'm having a similar error, except with certain games.
Click to expand...
Click to collapse
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
shimp208 said:
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
Click to expand...
Click to collapse
Thanks for the info, I am going to try experimenting w/ CM and report back , thanks!
shimp208 said:
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
Click to expand...
Click to collapse
I have seemed to fix the issue, it turns out that my major issue was the undervolting that comes with most custom kernels. The trick was to change settings before things got too out of whack... Hopefully this might help some others as well.
madeiracam said:
I have seemed to fix the issue, it turns out that my major issue was the undervolting that comes with most custom kernels. The trick was to change settings before things got too out of whack... Hopefully this might help some others as well.
Click to expand...
Click to collapse
Glad to see you were able to fix the problem
Hi, it really all started with the 3.4 kernel.
I'm s-off, super CIC and sim unlocked. Have been trying the carbon roms and getting random reboots which lead to a boot loop. After 3-5 loops it usually settles down again, but it Will happen again.
Then switched to codename lungo which has the best battery life for me (latest builds for carbon and lungo) but still getting the same problems, this morning it was using maps.
Also noticed that the phone was really hot, checked the battery temp and it was over 50 deg C.
I'm just wondering if there's anything that you guys do to ensure a smooth ROM installation and experience, especially in connection with the kernels? This current codename lungo buid that I'm on was installed from a TOTAL wipe, including the sd card (I mentioned this total loss in the carbon thread) so its stock kernel. But still not stable! It couldn't have been a cleaner install!
So any advice would be warmly welcomed.
I'm pretty fed up with all the CM troubles with 3.4 kernel, is it possible to revert back to previous kernel and sense ROMs? They worked great for me.
Thx
Sent from my One S using Tapatalk
Dude do you realize that there is a Question/Answer Forum and this one is to be left just for developing? and by the way yes you can go back to sense by flashing a rom or running an RUU
My mistake, I just posted here as it's where I spend all my time!
Sent from my One S using Tapatalk
Frankyg said:
Hi, it really all started with the 3.4 kernel.
I'm s-off, super CIC and sim unlocked. Have been trying the carbon roms and getting random reboots which lead to a boot loop. After 3-5 loops it usually settles down again, but it Will happen again.
Then switched to codename lungo which has the best battery life for me (latest builds for carbon and lungo) but still getting the same problems, this morning it was using maps.
Also noticed that the phone was really hot, checked the battery temp and it was over 50 deg C.
I'm just wondering if there's anything that you guys do to ensure a smooth ROM installation and experience, especially in connection with the kernels? This current codename lungo buid that I'm on was installed from a TOTAL wipe, including the sd card (I mentioned this total loss in the carbon thread) so its stock kernel. But still not stable! It couldn't have been a cleaner install!
So any advice would be warmly welcomed.
I'm pretty fed up with all the CM troubles with 3.4 kernel, is it possible to revert back to previous kernel and sense ROMs? They worked great for me.
Thx
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
Please also understand that most of the ROMs here are in beta/testing phase. That means that reboots/bootloops or other unexpected behavior is likely to appear. Event if for some of us a ROM may be stable, for others could be problematic or have some issues. This is depending on many factors even if you completely wiped as you said. hboot/firmware, radios, revision of your phone (hardware speaking) ar so many factors that influence the stability and smoothness of a ROM. The devs do their best to offer us a good experience and better ROMs but they cannot test in all conditions (even if they have testers). Even great teams like CyanogenMod had some issues with their ROMs for some of us
If you want stability, then go for a stock/sense based ROM with Android 4.1.1/4.1.2, anything else could prove to be not so perfect depending on your specific conditions
Also don't forget that such a thread will not help any of the devs nor this community....if you have issues it's is usually more helpful to provide detailed description of your problem along with logs that could reveal the root cause of it, than to complain about the instability of the ROM
Frankyg said:
My mistake, I just posted here as it's where I spend all my time!
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
you can go back to stock rom or try a stock based rom. BUT it still would be interesting why you have these problems because most of the users do not have.
I have flashed ROMs before on this device, but in all honesty, I just did it going by what other people were flashing. I always flashed the "latest ROMs" in tandem with the "latest kernels" that separate developers were building.
Now I would actually like to go back in time and try to find the smoothest and most stable combination I can get on 4.3 now that everyone's moving onto 4.4
I'm currently running PA with the stock kernel of 3.4.62-CM
So does that mean if a separate developer is building their kernel do I have to match the same exact kernel version of CM? (And yes I understand that AOSP and TW kernels are completely different, and I don't cross flash at all, lol)
I'm asking this to try to get a more thorough understanding of what is exactly going on when I'm changing a kernel, and how different versions matter.
Thanks everyone!
Sent from my SCH-I535 using Tapatalk
i cant go into detail about kernels since i dont know coding and all the other fun stuff
but they are fone depended.i personally use BMS kernel im on liquidsmooth 4.4 rom but have used BMS on 4.3 liquidsmooth rom . ive tried KT kernel but did not play nice with my fone it wasnt letting me change settings on it . i suggest from my personal experience try out different kernels run them for couple days to see how it plays with ur fone .