Database Info

Verizon CM10 Nightlies

Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,

Stormer1981 said:
Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,
Click to expand...
Click to collapse
You can't expect nightly builds to be stable- they will and do have issues with various things.
The vast majority, if not every single AOSP ROM for the SGS3 uses all of (or a good chunk) of CyanogenMod's code, which is why you see so many of the same bugs between builds that are rarely fixed until someone submits to CyanogenMod's Gerrit.
I can't comment on your specific issue, just posting some food for thought.

A lot of people have posted about echoes or low volume on the CM10 builds. I don't make many phone calls so I don't know if this affects every phone running CM10. But I'm sure it does to various extents. They will work it out in the coming weeks as they work toward a stable build.
Sent from my SCH-I535 using Tapatalk 2

the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140

Preferred Build
Is there a stable build other than the nightlies? If so where would I find it?

Stormer1981 said:
Is there a stable build other than the nightlies? If so where would I find it?
Click to expand...
Click to collapse
I'd check the development forum or the nightly thread.
Sent from my Galaxy S III

ripken204 said:
the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140
Click to expand...
Click to collapse
Agreed
Sent from my SCH-I535 using Tapatalk 2

No echo here. I just flashed to the 9/1/2012 nightly from stock.
Did you try playing with the call settings? I have noise suppression enabled and voice privacy disabled.

I actually have a similar problem (can't post on official thread yet).
I have trouble with my headset volume.
If i plug it in DURING a call, I cant hear anything and can't do anything to adjust the volume.
If i plug it in BEFORE a call, it's fine.
Any clues as to whats going on or any suggestions on how to fix it?

Paranoid android Sept 2nd build seems to work nice, i think it works better than the CM10 builds even though its based off it. You can also mess around with tablet mode!

Let's get the echo fixed and the roaming issue fixed and the forum will flock to these roms. Till then I would beware.
Sent from my SCH-I535 using xda premium

I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22

Defragger51 said:
I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22
Click to expand...
Click to collapse
Same results here for 904. The other forum mentions that an unofficial build has the incoming call delay fixed, though, so I'm hoping the fix shows up when the official 905 ROM comes out.

Headphones with mic not working
I'm running the 9/2 build and when I plug the stock headphones with mic into the phone I cannot talk or hear phone calls through it. No issue with music. Screen flickers when using keyboard (Swiftkey). Volume control in call doesn't seem to work. There is also a 5 second delay when I answer a call to when I can hear the other person or they can hear me. Same delay with speaker phone.
At least the damn echo is gone though :good:

Can anyone confirm whether or not the dock audio is working on recent CM10 builds? I've tried searching the thread and have done everything short of just flashing it to see.
Thanks for your replies!

The dock audio was still not working for me on the CM10 from 9/5.

landtuna said:
The dock audio was still not working for me on the CM10 from 9/5.
Click to expand...
Click to collapse
You are correct. Just tried it myself. This is the main thing holding me back from CM10. I'm going to attempt to add it in myself. We'll see what happens.

9/5 build seems to be very solid. No data issues or call issues. Cannot comment o no the dock audio though. Make sure you aren't doing dirty flashes, there have been tons of issues with dirty flashing.
Sent from my SCH-I535 using xda app-developers app

This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.

Krystalmyth said:
This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.
Click to expand...
Click to collapse
I'm going to give PA a try... I am still having serious issues with CM10, hope they will be fixed with PA

[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] 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] 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

[Q] Is there any Lollipop ROM that has a working bluetooth and audio

I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.

geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and I've tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didn't seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...

How about veneer?
Sent from my A0001 using Tapatalk

cymbaline24 said:
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and I've tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didn't seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...
Click to expand...
Click to collapse
It's been glitchy for a while. Are they planning on fixing it or is it unfixable?

Demontooth said:
It's been glitchy for a while. Are they planning on fixing it or is it unfixable?
Click to expand...
Click to collapse
CM has been working on it; I believe they just pushed two new BT commits to try to fix some of the issues in the last day or so. I haven't tried out any updated ROMs to see if it helped yet. I reluctantly left BlissPop and tried out Slim Saber with AK kernel (someone somewhere said BT worked on it) and after a couple kernel tweaks I didn't have a single skip to or from work today. And it turns out it's a pretty damn good ROM too.
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
fireforhire said:
How about veneer?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Won't swear to it, but I'm pretty sure that's one of the ones I tried and it still skipped.

CM12 Nightlies are working fine for me with BT. It used to be terrible but it's great now.

cymbaline24 said:
BlissPop worked great up until about a week ago with just the regular installation, no tweaks. CM then introduced some new commits regarding bluetooth, so as far as I can tell, all CM-based ROMs will have the same issue now (and Ive tested over a half-dozen so far). DarkoBass is mostly AOSP, I believe, and it didnt seem to have any issues - made it through a few songs with no stutter - but I missed too many other features from BlissPop so I went back tweaking it with Boeffla to find a solution. ParanoidAndroid is mostly AOSP as well - I bet bluetooth on it would work fine, and they just released an alpha build today, I think. Might just give it a try myself...
Click to expand...
Click to collapse
Blisspop?The romer who copyed mokee,which is a rom based CM

BlakeSm said:
CM12 Nightlies are working fine for me with BT. It used to be terrible but it's great now.
Click to expand...
Click to collapse
It was a little better today.

geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
BlissPop should work just fine.

No BT playback problems with Validus ROM
geeoat said:
I have read through several of the ROM threads and trying to determine which ROM and/or ROM+Kernel+Config combination works towards a stable bluetooth configuration.
I've had intermittent bluetooth connection drops on several of the CM 12 nightlies. In some cases, I've had audio issues as well.
If someone has a Lollipop based working configuration that enables a stable bluetooth, please share.
Click to expand...
Click to collapse
Had continuing problems with Temasek nightly. Switched to [ROM][5.0.2][02/04][OFFICIAL] GzRoms -Validus- [v7][Bacon] yesterday and have had zero BT music playback issues with Performance mode enabled. Couldn't be happier with this ROM.