Database Info

[Q] Are CM10 nightlies better than stable?

Just a quick question. The stable CM10 for our vzd2w devices is dated for 11-13-2012. I feel I should know this, but I am wondering, are the nightlies, say, for today, 12-08 more stable than the stable candidate released almost a month ago?
Is that the point of nightlies? To fix bugs and improve anything on previous candidates?
Do nightlies sometimes present with new issues/bugs?
Again, I know I should know this, but I NEED clarification as a search of any kind leads me to the nightly download site or ROMs based on the nightly releases. These questions are not addressed.
Thanks for your replies!!

tcsheen said:
Just a quick question. The stable CM10 for our vzd2w devices is dated for 11-13-2012. I feel I should know this, but I am wondering, are the nightlies, say, for today, 12-08 more stable than the stable candidate released almost a month ago?
Is that the point of nightlies? To fix bugs and improve anything on previous candidates?
Do nightlies sometimes present with new issues/bugs?
Again, I know I should know this, but I NEED clarification as a search of any kind leads me to the nightly download site or ROMs based on the nightly releases. These questions are not addressed.
Thanks for your replies!!
Click to expand...
Click to collapse
In general the nightlies are completely usable. They are used as a means for the cm10 team to test new features, and attempt to squash bugs. With software development when changes are made it is not uncommon for new and unforseen bugs to arise, its sort of a game of cat and mouse. Because of this, every so often things that had worked fine previously become broken in one nightly and are then promptly fixed in the next. For the last month or more the cm10 nightly builds have suffered from a host of bluetooth, microphone, nfc, and screen wake issues that seem to vary in severity from one nightly to the next. Some of these problems have been found to have flashable fixes, others do not. For many, myself included, this is the simply the price of being on the cutting edge of Android development. If this doesn't sound appealing then perhaps the stable builds are the way to go. Keep in mind that although the stable builds tend to be more reliable, they do have their fair share of bugs and glitches, some of which have since been sorted out on the nightlies. Either way cm10 is a far slicker experience than touchwiz, and in my opinion, the way to go. Just an fyi, I have dirty flashed one nightly to the next without incident, and if thats the route you decide to go it could save you some time.

i think stable is better... nightlies can work or not, so hit and miss....

I have personally never had a problem with the CM10 nightlies, and I have been using them for a couple of weeks now. But your experience may vary depending on your setup.
Good rule of thumb is if you're not prepared to deal with any issues that could arise then stick with stable. I always seem to have a few builds on my SD card and a titanium backup in case things really go sideways on me.

It depends on what your priorities are with this phone. For example the same 11/10 nightly was the last one without the bluetooth low bass bug, but but the 12/06 and newer nightlies have improved data drops for a bunch of people. If you rely on mobile data a lot the 12/08 nightly might be the one for you to try, but if you do a lot of bluetooth streaming then maybe the 11/10 nightly would work best for you.
Sent from my SCH-I535 using xda app-developers app

CM10
I switch from ICS to CM10 nightlies, which was for the most part a great daily driver. Then I flashed the new Jellybean leak and battery life was great (50% more than CM10) but I lost bluetooth. Last CM10 I used was in mid October. Has the battery life improved in the last 2 months?

[Q] Which 4.2.2 Rom has Bluetooth working?

All,
Been on Synergy for the past 3 month and my flashing itch is coming back. I want to start trying 4.2.2...getting tired of TW. Has the 4.2.2 Roms gotten stable as a daily driver? I will predominantly using this for work so stability is key and driving, hence the bluetooth functionality.
I was roaming around the thread cyanogen, carbon and liquid and seem like they all have bluetooth issues?
Anybody on a current ROM that have both stability and working bluetooth?
Thanks for any opinion.

cant comment on bluetooth, but they are certainly stable and daily driver worthy.
hopefully someone else can chime in on the bluetooth specifically

Nutzzer said:
All,
Been on Synergy for the past 3 month and my flashing itch is coming back. I want to start trying 4.2.2...getting tired of TW. Has the 4.2.2 Roms gotten stable as a daily driver? I will predominantly using this for work so stability is key and driving, hence the bluetooth functionality.
I was roaming around the thread cyanogen, carbon and liquid and seem like they all have bluetooth issues?
Anybody on a current ROM that have both stability and working bluetooth?
Thanks for any opinion.
Click to expand...
Click to collapse
I use cyberon voice commander for BT voice dialing. I have found on all ASOP roms, it works but the volume is low and there is a delay of up to 5 second in acknowledging the voice command.

Bluetooth works fine for me on a Carbon nightly....really like this ROM.
Sent from my SCH-I535 using Tapatalk 2

LiquisSmooth 2.5 is very stable. Been using it as a DD since January. Bluetooth works fine when I use it, which isn't much.

I have CM 10.1 RC5, and it's the most stable release they have. I believe they fixed the bluetooth a while ago. I only use it for audio streaming to my car, so I can't really comment on headsets or whatever else you might use it for.
But to my knowledge, bluetooth works. :good:

[Q] bluetooth headset does not work in cyanogen MOD ?????

I have tried 4 ROMs but none of them support my bluetooth headset (plantronics backbeat 903+ )???

cm 10.1.2 jenkins was a nice ROM ...but when I connect mobile with bluetooth headset ...it says "Bluetooth pin request rejected by device " ???

There's a known bug for bluetooth a2dp on the CM 10.1.x builds. It's gonna take a while yet before it gets fixed, so if a2dp is really important to you, you should probably try a different rom for now.
____________________
Sent from the moon.

Bluetooth Loops using ROM CM10.2-20131228-Nightly-p500
Syd_M said:
There's a known bug for Bluetooth a2dp on the CM 10.1.x builds. It's gonna take a while yet before it gets fixed, so if a2dp is really important to you, you should probably try a different ROM for now.
____________________
Sent from the moon.
Click to expand...
Click to collapse
I am running ROM 10.2 latest nightly (build cm_p500-userdebug 4.3.1) titled and phone's Bluetooth is not synchronizing, goes into a fast loop (on/off/on/off/on/off/...), detections works on occasion then never completes. I consider Bluetooth availability a safety issue for driving. My question is, has this problem been addressed or does your recommendation to go to another ROM still stand? I like this ROM otherwise, but have to back-out to ROM v10.1 to get Bluetooth to work. thanks.
Also, being the New Year, I wish the team the best of success, health & strength, peace & happiness for the coming year.

o0snoopy0o said:
I am running ROM 10.2 latest nightly (build cm_p500-userdebug 4.3.1) titled and phone's Bluetooth is not synchronizing, goes into a fast loop (on/off/on/off/on/off/...), detections works on occasion then never completes. I consider Bluetooth availability a safety issue for driving. My question is, has this problem been addressed or does your recommendation to go to another ROM still stand? I like this ROM otherwise, but have to back-out to ROM v10.1 to get Bluetooth to work. thanks.
Also, being the New Year, I wish the team the best of success, health & strength, peace & happiness for the coming year.
Click to expand...
Click to collapse
I don't use bluetooth other than for file transfer, so I can't speak from experience. It's probably best to check the various ROM dev threads for more details regarding existing bugs and whatnot. IMHO, if you really want a completely bug-free experience, stick with GB or ICS roms. 10.+ roms are more or less still works in progress. If you're interested in trying out the latest cutting edge releases, though, you might want to give this pre-trimmed KitKat release a try. That, plus sweetnsour's version 13 kernel looks pretty good so far.

Bluetooth Loops using ROM CM10.2-20131228-Nightly-p500
Bluetooth is has been broken for a while then. Can you direct me to the Bluetooth code out of curiosity? Thanks for your reply, i'll take look at pre-trimmed KK. I like to live at the cutting edge so I am tracking KK/CM11 on Jenkins with anticipation and rooting for the team!:fingers-crossed:

[Q] Previously reported BT issue in CM 10.1.2 - any fix?

First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps

Not an official one, no, I have had the issue since the 4/24 build, but with some recent commits shortly after 10.1.1 it's been much better, but still not 100%. I know carvsdriver has identified the issue and just needs to get some time in to fix it, so it should be coming soon-ish to the latest nightlies. I don't know how likely it would be to get into a 'stable' release very soon, but for me, the nightlies are way better than the stable releases anyway.

Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

BT Problems - Getting better
rajb12 said:
First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps
Click to expand...
Click to collapse
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update

cejack said:
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update
Click to expand...
Click to collapse
I don't know that the commit was a complete fix, but it certainly helped. I saw a post on G+ about it (I think), and the developer mentioned that after 30 BT connections/re-connections, it would stop working, and that it would be hard to fix. It's definitely way better than it was.

Stereo Bluetooth works pretty well. Just listened to 3-4 hour podcast with Stereo Bluetooth P311 headphones.
Also used Motorola H500 bluetooth headset as well. No problem there. Also using 9XX Plantronics headset. No problem either.
All in all - can't complain about BT too much anymore after going from latest stable to more recent "nightly" releases.
If you run into problem.... you'll have to re-boot.

Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.

chas101 said:
Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.
Click to expand...
Click to collapse
All I can say is that with 4.3 (CM 10.2), in the past week I have only had to reboot once to fix bluetooth issues, that I can remember.

[Q] problem with S3 GPS ... and audio out?

I've been fighting with the cm11 d2lte builds since I updated to a nightly in the beginning of September; since then (I believe the 9/7 nightly was the last one that worked), I've had trouble with GPS losing locks, or getting locks at all. I tried several nightly updates in hopes this was a known and fixed problem, as I've seen many complaints about GPS in cm11, but none of the nightly or snapshot updates helped, and some made things worse.
I have tried everything I could find, including toggling between Maps and other map/GPS related apps, full ROM wipes and fresh installs, wipes to flash stock firmware and then come back to cm11 after getting a GPS lock in stock, 3rd party apps like GPS Status to update/wipe aGPS (assisted) data, etc. The state my phone is in now is:
- Did a full wipe of data and cache partitions
- Installed stock backup, got a GPS lock, and rebooted
- Wiped again and installed the most current cm11 snapshot for d2lte (11-20141008-SNAPSHOT-M11-d2lte)
- Using GPS Status and toggling between Maps and Waze to try and get GPS locks
I'm able to get a lock sometimes, but not often enough and not when I need one most: Maps recently turned a 1.5 hour trip into a 3.5 hour nightmare with a really bad route and no ability to reroute.
As an afterthought, I realized that when I'm in my car, I'm usually using the phone for 2 things:
- GPS/maps
- audio output from headphone jack to car aux input
While playing with GPS on the way home today, I unplugged my audio cable from the headphone jack ... and I suddenly got a GPS lock. Plugged the audio cable back in, and lost the lock. Pulled it again, and got a lock. WTF? I've been fighting with this for a month, and don't think I've seen a single mention of audio affecting GPS.
Can anyone else possibly verify this? And any suggestions on a fix?
Thanks!

I've read before that tightening the screws inside the back of the battery sometimes solves this issue
From my Wicked S3 on SOKP

Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.

ShapesBlue said:
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
Click to expand...
Click to collapse
Not sure what you mean, but if you mean the 10 screws surrounding
the frame, I've tried tightening them. I don't know of any screws on or beneath the battery.

MrBrady said:
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
Click to expand...
Click to collapse
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?

deesto-xda said:
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
Click to expand...
Click to collapse
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.

MrBrady said:
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
Click to expand...
Click to collapse
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.

deesto-xda said:
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
Click to expand...
Click to collapse
Most custom roms are based off other roms, aicp is one of the many. I switched directly to CM11 today because I was on another version of a cm based rom and the reboots were too much for me.
From my CM11 S3