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
Related
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
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
mefistofel666 said:
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
Click to expand...
Click to collapse
nope those 3 build threads are it
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
SSPENCER10 is working very well for me. Everything he is putting out is stable and appears to be having fewer issues than KitKang. It is even working just as well with ART as it was with Dalvik. The 11-23 build also has the new CM11 boot animation.
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
You realize they are all based on exactly the same code right?
And you realize that if one makes 'progress' they all make 'progress' because they use the same code right?
[ROM][4.3.1][Official][OSE Rom][d2vzw]
I'm using this one and so far so good.
It has nightlies that have 4.4
I'd recommend KitKang. It's been extremely stable and has really good battery life. ART works very well.
Sent from my SCH-I535 using Tapatalk
KitKang!!
Second that!!
Sent from my SCH-I535 using xda app-developers app
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
Summary: I don't think KitKang is recognizing my SIM card, and is causing "Phone" to crash every second or two.
Hey guys, I tried flashing the latest KitKang ROM last night, but ran into a big issue. I wiped system, cache, dalvik cache, etc. I then reflashed the MF1 firmware (it was already flashed, but for some reason I always feel better re-flashing it every time.) Then I flashed the latest KitKang D2VZW nightly linked above, and flashed the GApps mentioned in that thread too. However, upon rebooting, every second or so it would say "phone has forced closed" (or something along those lines. Also, there was no signal. I got through the setup process after a VERY long time of pressing "okay" to that error and setting up my CM and Google accounts with one key in between each error. I thought I would be able to go into Mobile Networks and change the settings, which fixed certain early issues with CM10.1 or 10.2, but to no avail. I then tried reflashing (after wiping clean) CM10.2 again to get certain files for the phone to work, then flashing CM11 over that, and it seemed to work up until it freezes after getting to the home screen. Any thoughts on what the issue may be and/or how to fix it?
Thanks!
Sent from my SCH-I535 using xda app-developers app
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.
So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!
Honestly, I use the CM11 builds and they are working great.
XOOM XOOM!
slinky317 said:
So I'm trying to prolong the use of this tablet but keep it stable and quick, and I think CyanogenMod is the way to go. There are a number of versions available for it, with 10.0 being the last stable build that I can find. I flashed 10.0 and it was quick and stable, except for one major problem: the Google+ app just would not load no matter what, and by searching I found others had the same issues with no fix.
So I'm back to stock 4.1.2 JB now, which is fine but I'd rather move to CM if I can. I flashed the latest nightly, but was having major issues with Gapps closing and the Play Store wasn't even available (even though I flashed the correct Gapps package).
For those that are using CM, which version is the best to use? Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
CM10.1 (based on 4.2.x) really great. I used it for the past few months.
Never give me problem. Of course you must install 2/20/13 JB Unified GApps.
Looking forward to try CM11 but having hard time with TWRP (big part) at the moment.
TheMan0790 said:
Honestly, I use the CM11 builds and they are working great.
Click to expand...
Click to collapse
Another vote for CM11, but you do have to install BigPart. That isn't a big deal if you read carefully through the resource thread before proceeding. I'm certainly not a tech wizard (color TV and phones without dials were big deals when I was a kid, VCRs didn't come out until I was in college, and I was in my mid twenties when home computers just started to become widespread) and was able to run BigPart without trouble.
I got BigPart working successfully with no problems on the first go. Merely requires some reading and should work fine.
Break me off a piece of that Kit-Kat ROM!
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
No such issue here. Try full wiping and then reflashing CM.
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
avalanch said:
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
Click to expand...
Click to collapse
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Primokorn said:
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Click to expand...
Click to collapse
Thanks for that info. Good to know i am not the only one. I am on a mission of trying all the Cm12 Nightly from jan onward till today. Hopefully 1 of them will work... Any suggestion for most stable of nightly is appreciated. Thanks. Trying different roms too.
avalanch said:
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem with a 32GB nexus 5 and the recent cm12 nightlies, I have found a dozen or so forums/pages about the problem but nothing that seems to help. I have tried flashing different radio.img file and different kernels, the problem only happens in my car, my bluetooth headphones and everything else works fine. My car can take phone calls but not play back music/audio from anything without skipping every 5-10 seconds for ~1 second
That's because CM team still don't get, that it's better to start building a house from the ground, then from the roof. It's a kernel related issue.