I have used Dark Jelly, Illusion, and CM 10.1 (and loved them) all with the 3.4 kernel. I am aware of the data turning off issue. When I first started using the roms it would only disconnect once a day or so. Couple weeks later it was multiple times a day. Now it is almost never on and it keeps saying my simcard is not inserted. So I was looking for a non 3.4 kernel and rom to go with it!
Any suggestions?
Latest carbon Rom (3.0.80 kernel) with bubba Kernel Vn6
foeti said:
Latest carbon Rom (3.0.80 kernel) with bubba Kernel Vn6
Click to expand...
Click to collapse
Thanks for the reply. I'll check it out.
I know that is not AOSP based like CM, but after ad enough of the connection drop issues of CM, I flashed MIUI... it's enough fast, it's nice, has no major bugs, it's well updated and has no connection drop issues
superbalza said:
I know that is not AOSP based like CM, but after ad enough of the connection drop issues of CM, I flashed MIUI... it's enough fast, it's nice, has no major bugs, it's well updated and has no connection drop issues
Click to expand...
Click to collapse
I used MIUI for 2 years or so. You're right, it is fantastic! I finally decided to try something new and thats why I am running into recent problems haha. Thanks for the tip!
foeti said:
Latest carbon Rom (3.0.80 kernel) with bubba Kernel Vn6
Click to expand...
Click to collapse
Well unfortunately, the VN6 puts me in bootloop because Carbon is a 3.4 rom. I found an older version of Carbon, 1.7, that will work on the the VN6 (at least it looks like it will). I am going to try Bubba's 3.4 kernel with carbon first and see how my data connection is. I've seen people saying that they have fixed their issue by adjusting the build.prop but I'm unsure how to do that. I should maybe update my radio? I'm on 1.13.50.05.31
Related
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
Actually, most of the times, you can flash a kernel that's based off of a different source base on a different base ROM as long as they are the same Android version (same framework). VRALG7 did not change much other than some of the apps and on the kernel side, I don't believe anything has changed. That should go true for radio too. For the OP, did you come from wipe everything and flash clean? Also, I am not sure what kind of modification the ULE went through but it may be lacking some libs or ramdisk since the rom is so damn light. Go and pull the boot.img from original ULE and see if the original kernel causes the same issue.
I installed the KT747 kernel. It runs GREAT with this ROM! No lag, super smooth & fast. Thx for the replies! KTweaker app is Awesome! The unresponsive / frozen lock screen is gone! CleanROM ULE + KT747 = Winner!
Sent from my SCH-I535 using xda app-developers app
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
I agree! Scott updated Clean ROM yesterday to 2.5 which is based off of the new G7 baseband. As Scrosler states in the OP, a new clean kernel is not available yet, so when you flash the new 2.5 you will be on stock. It's worth updating though! I'm sure an updated/upgraded kernel and mods will be out soon enough.
I had that same issue
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
SO what I did, made surei have no cpu apps runnung to be set on boot ( major problem when using titanium as a restore agent )
Then I flashed scotts clean kernel ( whatever the lastest edition is ).
Then right then and there wiped cache, and dalvik and then fixed permission.
THEN HERE IS WHERE ITS VERY IMP. I LET THE PHONE SIT FOR 10 MINS BEFORE TOUCHING IT AGAIN.
Now i am running smooth .
This is on .lk 0.9 which is essentially the same as lk .10
Guys, am I the only one getting constant reboots on the latest nightlies? I load up a nightly (have tried 3/17, 3/19, 3/23 so far) and I clear data cache and dalvik prior and post load. I also load the newest 4.2.2 gapps for jb.
The phone reboots itself on everything from Temple Run to basic browsing to music playing through Bluetooth. There seems to be no rhyme, reason, or specific app causing it.
I am using the built in kernel... Is this kernel instability I am seeing?
Please tell me I'm not the only one experiencing this. I am a big fan of cyanogenmod, have used it on many phones over the years but this has been very unreliable for me.
Thanks, Brian
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
Ok so I fixed permissions on 3/23 cyanogenmod nightly, still constant reboots. Then I flashed aokp (hilbert) newest nightly based on 3.0.68 kernel and I am getting the same problem.
Is there any other way to troubleshoot this? Can someone else speak up who is running the newest night lies without FCs or reboots so I know I'm not crazy.?
Thanks for your IMs as well... I will definitely try newer builds.
bguild said:
Guys, am I the only one getting constant reboots on the latest nightlies?
Click to expand...
Click to collapse
I didn't get constant reboots but I did get random reboots from time to time.
I also noticed the latest nightly I ran (3/23) seems very slow.
My fix was to restore my backup of CleanRom and I may just not return to CM 10.1.
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
NeoMagus said:
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
Click to expand...
Click to collapse
My thought is that in my case there may be something else going on. So far I have tried Cyanogenmod 3/17,3/20 and 3/23 nightly, a 3/23 nightly for AOKP, and now I just installed CleanROM 6.2 R2, which is Android 4.1.2 based. I think most of these kernels are 3.0.x based. I am definitely still getting occasional reboots and FCs but I will say it seems CleanROM is the most stable.
The common thread on all of these builds seems to be that the most instability occurs when attempting to connect to a bluetooth device. That is when I get the constant reboots. I'm talking like you start to play a song, and it gets through half way and just completely reboots itself.
I'm going to keep trying here, but I might have found the common thread in bluetooth instability.
Does the 3.4 kernel report as 3.4.x on the newer nightlies?
Yes it shows in the settings, I personally haven't had any issues with connecting or using my A2DP rocketfish Bluetooth headset even when I was on the newer nightlies with the 3.4 kernel, it was more of hadn't used the phone for a while went to turn the screen on and it wouldn't come back had to battery pull.
Haven't had a single problem since rolling back lockup or otherwise so I'm watching the main threads to hear when they get the issues with the kernel figured out before flashing anything newer
Hi all.
I've been reading through the forums for a bit in an effort to find a way to get more out of my Nexus S. I think I would like to try the Marmite kernel but am:
Unclear if it works with CM (I think it does)
Which version I download from the spreadsheet (which I can't link to). I think it's short url ending Idh
My setup is:
Nexus S i9023
CyanogenMod 10.1.3
Usually 30-20MB free
While I am discussing it, is there any list of available kernels for the NS?
sdfw said:
Hi all.
I've been reading through the forums for a bit in an effort to find a way to get more out of my Nexus S. I think I would like to try the Marmite kernel but am:
Unclear if it works with CM (I think it does)
Which version I download from the spreadsheet (which I can't link to). I think it's short url ending Idh
My setup is:
Nexus S i9023
CyanogenMod 10.1.3
Usually 30-20MB free
While I am discussing it, is there any list of available kernels for the NS?
Click to expand...
Click to collapse
Marmite kernel works fine with cm10.1. Choose any version that you want... Some people prefer the 8.x branch, other the 7.x... I would personally go for the latest version 9.0 as there can be problems with bln on 9.1... not sure.
As for other kernels, look in the android development section. I really like the devil kernel, but there are others that you can try. Do a nandroid backup and give them a try!
Dark_Eyes_ said:
Marmite kernel works fine with cm10.1. Choose any version that you want... Some people prefer the 8.x branch, other the 7.x... I would personally go for the latest version 9.0 as there can be problems with bln on 9.1... not sure.
As for other kernels, look in the android development section. I really like the devil kernel, but there are others that you can try. Do a nandroid backup and give them a try!
Click to expand...
Click to collapse
Thanks for that, gave Devil a spin very impressive, especially the amount of free ram but had a few teething problems I'll have to investigate (random reboots over night and killing active programs to free ram)
Marmite looks to be working fine so far.
sdfw said:
Thanks for that, gave Devil a spin very impressive, especially the amount of free ram but had a few teething problems I'll have to investigate (random reboots over night and killing active programs to free ram)
Marmite looks to be working fine so far.
Click to expand...
Click to collapse
Marmite is indeed a favorite for many people. It was not stable for me when oc but really a good kernel. Only problem is that bln doesn't work anymore on cm10.2 so that's a big turn off for me. I don't have those issues with devil... Maybe try flashing older build that are not for 4.3...
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
For TW 4.1.2 is the most current, but developers are working on 4.3. Otherwise, I would flash an AOSP ROM & I've had good luck on those too.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
HOWEVER... every custom rom has issues with a 'kill signal' with Bluetooth, so if you use BT, you need to make sure you power down the other device, before you try to turn off BT on your phone; that will send the signal to your device and unpair the two. Otherwise, your phone won't be able to reconnect to BT on that device and you'll have to reboot. It's a known bug and people are working on it.
I used Gummy all December and now I'm running SlimKat... they're stable for daily use. I'd recommend a custom kernel with Slim, though... I'm using Lean Kernel.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Take a look at this it was just released
http://forum.xda-developers.com/showthread.php?t=2591895
beepea206 said:
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
Click to expand...
Click to collapse
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?
lexluthor said:
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?
Click to expand...
Click to collapse
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.
beepea206 said:
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.
Click to expand...
Click to collapse
That's a reasonable explanation. I'm on CM11 official nightly. I usually read the changelog before I update. I did do a full wipe before updating originally and I've been running very well. I've had 1 random boot in about a week and the camera froze the system once. I had many more random reboots on TW. It's incredibly fast and I've got no lag (that was a bad problem for me on 4.1.2).
Nice one... checking the changelog and/or Gerrit commits is a good practice, IMO. I only flash a nightlie if I find some commits I think would make the rom run better for me... most are small things like language tweaks and updates to other device repos, so flashing the newest version isn't always necessary.
Regarding the random reboots, you probably have the same modem issue I do. There was a recent update to the device RILs that completely resolved the modem 'freakout' i kept having; I believe they used the updated device files from the 4.3 stock builds pushed out, so it made the device more compatible with the 4.3 and 4.4 roms.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
if you like touchwiz, MOAR and Wicked Sensations roms (4.1.2) are pretty good. I'm on cm10.2 (4.3.1) with xposed framework and it's running perfectly. I'm staying away from kitkat cause of all the bluetooth issues.
I'm using the Virtuous Inquisition rom with android 4.0.3. if I go to a rom with 4.3 or 4.4 will performance increase or decrease? also, can I keep my settings and apps or do I have to start fresh?
thanks.
You will need to full wipe and reinstall everything again.
I've never used Virtuous Inquisition, so I don't know about performance, but latest 4.4 roms we have are really smooth. If you want to test, just make a backup of your current setup, then install any new. If you don't like it you can always restore to your old setup.
Though since most roms we have are based on cyanogenmod, most of them have a bug at the moment causing the system to freeze or maybe restart. Only 4.4 rom (which I know) which isn't affected by that is omnirom.
Sajito said:
You will need to full wipe and reinstall everything again.
I've never used Virtuous Inquisition, so I don't know about performance, but latest 4.4 roms we have are really smooth. If you want to test, just make a backup of your current setup, then install any new. If you don't like it you can always restore to your old setup.
Though since most roms we have are based on cyanogenmod, most of them have a bug at the moment causing the system to freeze or maybe restart. Only 4.4 rom (which I know) which isn't affected by that is omnirom.
Click to expand...
Click to collapse
thanks. i may try that rom then since I need stability. why dont other roms like this one mention freezing under the bugs?
http://forum.xda-developers.com/showthread.php?t=2530073
Gabe3 said:
thanks. i may try that rom then since I need stability. why dont other roms like this one mention freezing under the bugs?
http://forum.xda-developers.com/showthread.php?t=2530073
Click to expand...
Click to collapse
It's an upstream bug from cyanogenmod itself and I think they list mostly bugs which they can fix. We still hope that cm is going to fix that soon.
Sajito said:
It's an upstream bug from cyanogenmod itself and I think they list mostly bugs which they can fix. We still hope that cm is going to fix that soon.
Click to expand...
Click to collapse
how does omnirom compare to cyanogenmod besides the freezing bug. is one faster than the other? why would anyone use cm over omnirom? thanks.
Gabe3 said:
how does omnirom compare to cyanogenmod besides the freezing bug. is one faster than the other? why would anyone use cm over omnirom? thanks.
Click to expand...
Click to collapse
Well both are based on aosp, so I don't think there is a big difference in performance. Cyanogenmod has more settings than omnirom, but I think differences are not that big. There are some settings only the one rom or the other has, so I think you should just try.