Database Info

CM-10 08/21 bug

Since I am unable to post it the developement forum for the CM nightlies, this sub-forum is the only option. Gchat (at least on my phone) only plays thru the headset speaker (not the external). Had to hook up a set of buds to be able to converse with the wife this morning. If anyone reads this and can either move it to the DEV section, or at least let them know it would be beneficial.

CM 10 Nightly 8/21
Installed the Official CM 10 Nightly 8/21 an hour ago and it is running great. MMS works, Camera works with out crash or reboot, No reboots and a flashlight app I use that caused a reboot on 8/20 works with out a reboot on 8/21. keep up the great work. If only I could post where it would be seen.

Unless I missed a setting somewhere, the Audio through USB didn't work either. Still a [email protected] rom though and I know for most that option isn't important.

Another bug?
Anyone else having problems with Google Maps stopping. Doesn't matter whether GPS is on or off. Loads, locates and then closes. This will be one thing that makes me go back to an ICS ROM.... have to have maps working. 08/21 build.

tdperry said:
Anyone else having problems with Google Maps stopping. Doesn't matter whether GPS is on or off. Loads, locates and then closes. This will be one thing that makes me go back to an ICS ROM.... have to have maps working. 09/21 build.
Click to expand...
Click to collapse
Full wipe and reinstall appears to have fixed this.
TAPPED in on my (now unlocked bootloader) Verizon S3

I did a full wipe and install. I don't get any random reboots anymore. No echos. But the battery seems to be worse. I'm dropping at 2% per half-hour rate. This is w/o touching the phone at all. Just letting it sit there. Anyone experiencing something like this with the battery?

Can't get the USB Audio to work. So far, this is the only issue I've had.

AsmodeusLore said:
Can't get the USB Audio to work. So far, this is the only issue I've had.
Click to expand...
Click to collapse
How does Bluetooth audio look as of now?

I'm waiting for bluetooth to be 100% on CM10 before I use it as a DD. It looks and works great just need that functionality. It was the same on my trusty Thunderbolt (god rest his soul) when CM was being built for it.

SymbioticGenius said:
How does Bluetooth audio look as of now?
Click to expand...
Click to collapse
Took a 2 hour trip today, streaming Pandora the entire time. Worked fine.
TAPPED in on my (now unlocked bootloader) Verizon S3

tdperry said:
Since I am unable to post it the developement forum for the CM nightlies, this sub-forum is the only option. Gchat (at least on my phone) only plays thru the headset speaker (not the external). Had to hook up a set of buds to be able to converse with the wife this morning. If anyone reads this and can either move it to the DEV section, or at least let them know it would be beneficial.
Click to expand...
Click to collapse
thanks for confirm :angel:

DailyRoads Voyager freezes phone with CM10.1 RC2

I have been using DailyRoads Voyager for almost 1 year without any issues. Even CM10.1 nightlies that came out 2 weeks before RC2 didn't give me any problems. Unfortunately, after upgrading to RC2, whenever I put the app in background recording mode, the phone becomes extremely sluggish, and sometimes even freezes completely. Anybody has any suggestions on overcoming this?

Provide a logcat, it will help identify where the issue lies.
Sent from my SAMSUNG-SGH-I727 using xda premium

ctalcant said:
Provide a logcat, it will help identify where the issue lies.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I have uploaded the log (which I got using Eclipse Logcat) here. The log is from the start of the app till its exit. Please let me know if I can do anything else to get this resolved.

unni_kmr said:
I have been using DailyRoads Voyager for almost 1 year without any issues. Even CM10.1 nightlies that came out 2 weeks before RC2 didn't give me any problems. Unfortunately, after upgrading to RC2, whenever I put the app in background recording mode, the phone becomes extremely sluggish, and sometimes even freezes completely. Anybody has any suggestions on overcoming this?
Click to expand...
Click to collapse
Wait for the next release(s) and hope it works again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.

PDXKris said:
Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.
Click to expand...
Click to collapse
No. I went back to 15 Feb 2013 nightly build.
The app has the problem even with the 10.1 stable build. The developer promptly replied to my initial query with a debug build of DRV (which has some new features also ). The logs it produced didn't indicate any problem with the app. After that I didn't follow up with him. I will do it this Saturday.

Today, I did a factory reset on my phone, wiped everything and installed ‘Cyanogenmod 10.1 stable’ along with ‘DRV 3.0 Beta 2’. Unfortunately, the problem still exists. Given below are the generated logs:
ADB Log
DRV 3.0 Beta 2 Log (this is from a version I got from the developer).
I also captured a video at the same time the logs were being generated. The video can be viewed from the links below:
Low Quality (96 MB)
High Quality (518 MB)
I had this video captured so that the developer can understand clearly what's happening. The phone slowing down can be seen from 5th minute onwards.
I have also written to the developer.

unni_kmr said:
I have also written to the developer.
Click to expand...
Click to collapse
That's the best idea since the problem is most likely the app and not the ROM. The app most likely needs an update to keep up with the constant updates that the ROM receives.
Brought to you by time and relative dimensions in space.

PDXKris said:
Did you ever find a solution for this? I've got the same symptoms on a Galaxy SIII, currently running the latest builds of CM10.1.
A build from 3/8 which I used for quite a while worked fine, but sometime in May I updated to a fresh build and found it was broke, all builds since then have also had the issue.
Click to expand...
Click to collapse
Tried AutoBoy BlackBox app today. It also freezes the phone similar to how it happens with DRV. The main difference is that with DRV, the freeze usually happens from the beginning of recording, where as with AutoBoy, it happens when I try to come out of background mode. The phone freezing/hanging part is quite similar in both apps. Can you confirm if this is happening with you?
Also, please recommend some other background recording apps I can try so that I can help in finding the root cause of this issue?

unni_kmr said:
Tried AutoBoy BlackBox app today. It also freezes the phone similar to how it happens with DRV. The main difference is that with DRV, the freeze usually happens from the beginning of recording, where as with AutoBoy, it happens when I try to come out of background mode. The phone freezing/hanging part is quite similar in both apps. Can you confirm if this is happening with you?
Also, please recommend some other background recording apps I can try so that I can help in finding the root cause of this issue?
Click to expand...
Click to collapse
I'm afraid I won't be very helpful going forward. My phone is provided via my employer, and I was just upgraded to a Galaxy S4 that doesn't have the issue (and I no longer have access to the S3). Sorry!

Just to update:
The developer reviewed my logs and has come to the conclusion that the problem could be with the ROM.
I also tried Autoguard Pro. It also has the exact same issue when put in background mode.

For anybody stumbling into this thread because of this issue:
CaroO works properly in background mode. It also reads from the OBDII sensor (if you have one), and has a map view as well. I used it for 30 minutes without any issues.

I just ran into this same problem. Voyager with 10.1.2 & 10.1.3 caused absurd sluggishness in the phone. I updated to 10.2 9/22 nightly and the sluggishness is gone.

lonesouth said:
I just ran into this same problem. Voyager with 10.1.2 & 10.1.3 caused absurd sluggishness in the phone. I updated to 10.2 9/22 nightly and the sluggishness is gone.
Click to expand...
Click to collapse
I have been using the latest DRV with CM 10.2 20131028 nightly for the last 3 days. I used DRV for approx. 3 hours in total (about 30 mins each time) along with Torque and Navfree. Didn't face any issues. :highfive:

{Q}to follow the cm 10.2 updates

Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.

Of course you can. Head over to the thread Nardholio started in the Development section.
http://forum.xda-developers.com/showthread.php?t=2405310
The first post has links to: the official CM site and to the Apex Github. The CM site has a changelog for nightlies. On the Apex Github, they maintain a list of known issues.
It's all there.
I caution you on expectations here. Android 4.4 was just announced with a very unfortunate name. I think Jelly Bean 4.3 has about 60 days to live. It would be silly to expect 10.2 to be stable by then. After 4.4 hits Nexus devices, I bet the Apex guys will shift their focus to 4.4 and we will repeat some of this process...

NavarroCol said:
Hi,
I m very interested in install the official 10.2 CyanogenMod based in android 4.3, but is in Nightly phase, i am wondering how much time can take to reach a more stable version, and if is posible to follow the changes, issues and fixes in the daily releases.
I hope someone can give me orientation, thx in advance.
Click to expand...
Click to collapse
it will probably never happen.
android 4.4 is just around the corner, so i guess the focus will be swapped on that, as it was for 4.3 and 4.2 before

CyanogenMod will do a final "release" build when 10.2 is EOL which will be the most stable we can make it. We also have a last 10.1 build we consider mostly stable, although it is unofficial. Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)

Nardholio said:
Right now 10.2 does have some stability issues, but most of these will be worked out (there are some bugs in our firmware we will not be able to fix until/if Samsung updates the firmware)
Click to expand...
Click to collapse
I have random freezes/reboots all the time on the official nightlies -- even the ones people claim are stable. The lockscreen freezes quite often too. Are these known issues or am I just a lucky one? I am running CWM and followed the installation instructions on the Cyanogenmod wiki.
I just installed alogerec and hopefully something will show up to troubleshoot my issue.

Problem with 10.2 nightly as well
I have a problem with the 10.2 nightlies I have tried (all from this week) that I emailed Narholio as he requested.
But since I am a n00b and cannot post to development threads yet I could not post details there. I have not done extensive testing because the screen stays black even though the buttons light up when I try to unlock the phone. I can usually get it to display by pressing the lock button again to lock it, then pressing it again to unlock it right away. This also seems to happen only after the phone has been locked for greater than 20 seconds. If the screen timeout happens, or if press the lock button to lock it, the display almost always works if I unlock it again before 20 seconds is up.
I have not noticed any reboots or other problems, but have not used it extensively because of the black screen problem.

Try http://ls.infernix.net/jenkins/job/apexq-staging/ build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app

I flashed build 336 last night and still have my phone lock up when trying to unlock it. This doesn't happen every time but when it does it either shows the back and menu buttons illuminated with a black screen or an unresponsive lock screen. In either case it will eventually reboot.
Sent from my SGH-T699 using xda app-developers app

Same problem
Nardholio said:
Try build 336
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it

I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.

Good idea
DOMF said:
I've seen that problem w/ the freezing while trying to unlock when the phone is OOM. If you can actually get it to unlock after that, check your apps memory usage.
Click to expand...
Click to collapse
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?

computerinfo21 said:
I also still have the same problem with 336 you linked. I'm running it right now and posting this using it. I have had no reboots or other problems yet, but the black screen while trying to unlock it still plagues an otherwise really great experience. I love the speed and feel of it
Click to expand...
Click to collapse
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1

computerinfo21 said:
Thanks for the suggestion. Checking memory is a good idea, although I really don't have any apps at all installed. Didn't even install gapps when I flashed this time.
Is there a preferred way to check for free memory? Terminal command?
Click to expand...
Click to collapse
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running

Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.

Plenty of free memory
croogrog said:
Have you tried a clean install? Wipe system,data,cache then install I have not had wake-lock since early 10.1
Click to expand...
Click to collapse
Yep, did wipe each time I tried multiple recent nightly versions which all do the same thing. The only one I've tried that works correctly is the 20130309 version.
DOMF said:
Personally, I always forget to close browser tabs and OOM that way. Check in Settings -> Apps -> Running
Click to expand...
Click to collapse
I generally keep a tab open to this Relay forum so I can watch what's happening, but not many tabs. Also happens immediately after flashing, without even running any apps, much less installing any.
orange808 said:
Look at the apps you use as well.
When Android was introduced, they rolled it out with a set of guidelines called the application life cycle.
In the document, Google specified how to develop applications and what was available. One option for devs that is powerful is running a thread as a service. It was a feature that was supposed to be used sparingly... (A service is a program that runs all the time--unless the kernel panics and shuts down everything.)
Unfortunately, developers know that Google isn't going to do anything to push them to make quality software. The market is supposed to sort it out.
In many cases, this is not working. People are taking advantage of the lack of QA.
Bottom line: App devs are building software that leaves services running in the background all the time--for no good reason, whatsoever. Many of these services are just there to slurp up your data and send it to their servers so they can sell it.
Holding the back button to fix it? That rarely works. The devs have intentionally built their memory wasting crapware to restart the service if it gets shut down.
Click to expand...
Click to collapse
I really haven't installed any. And when testing different nightlies I just flashed and it happens right away, didn't install a thing on them.
I decided to stay on a version for a while, so have had 20130920 since Friday, and I've used it long enough to know it is consistent. I have found another way to make it happen: incoming phone calls. When phone wakes that way it almost always happens as well. Today it finally showed the screen when I received a call, but 3 or 4 other calls the screen has just been black so I can't tell who's calling.
I discovered another thing since using this ROM for 6 days. Sometimes I get lines/bars/tearing on screen that won't go away until I lock and unlock the phone again.
I have some other phones that are broken, if I can fix one of them I might consider sending this one to a dev to temporarily play with since it seems to be the perfect test case for this problem. The screen is cracked (I got it used in this condition), which I would normally suspect to be the cause of the problem, however since it does not have either problem with stock ICS, stock JB, or the 20130309 CM I'm pretty sure it's related to something in CM10.2. Just new enough to Android I'm not sure how to track it down.
Thank you all for your help!

I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app

I also have a rev0 cpu phone, and I had a few lockup/reboots since I finally dove in last Monday (9/30) with Staging build 341. However, without me changing anything (still on the same build), they seem to have stopped. Last one I got was 10/2.
Edit: until just now. *facepalm*
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

I got sick of stock so I tried CM again. After flashing the 10.2-20131014-NIGHTLY-apexqtmo nightly I have not had one reboot or lockup in days. YMMV
Edit: Still haven't had a lockup on wake or reboot.
TheMaskedMan said:
I have one of these "rev0 cpu" phones and just recently went back to the stock firmware (ugh) because of the lockscreen wakeup lockups. I have gone 3 days so far with no issues. Until this issue is troubleshot, this is an option for anybody who needs stability with one of these phones. I miss CM very much though.
Sent from my SGH-T699 using xda app-developers app
Click to expand...
Click to collapse

Hmm... I'll have to try again
Hmm... Sounds like I need to try again then. I tried one released after that and still had issues, but I will try to make some time later to try it. It is fantastic other than that problem.

newer nightlies
Anyone else having issues with the newer nightlies? I have been flashing one a week for a while now and I'm coming from the 14th. tried flashing the 21,22,and 23 all of them are giving me a boot loop at the samsung screen. I have dirty flashed, cleared cache and dalvik, updated recovery. none of them are working for me. Am I missing something? they don't work so i reflash the 14th and everything is good again.
tried in
CWM 6.0.3.7
CWM 6.0.3.8
CWM Touch 6.0.3.8
all with the same errors any help would be appreciated

[Q] Cyanogenmod 11-M9 crashy as hell on Hammerhead?

Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?

starslab said:
Is anyone else running Cyanogenmod 11 M-releases on their Nexus 5?
I just got mine a week or two ago, and the first thing I did was unlock it and flash it to CyanogenMod 11. (M8 at the time)
I'm using the device encryption, because I'm a paranoid bastard (And I love the fact this phone is actually usable while encrypted, unlike my Nexus S), and I find it very crashy. Several times per day, seemingly totally random, often while entering into the keyboard, though sometimes while it's just in my pocket. I've been able to determine no rhyme or reason.
No error messages, no apps crashing, no force closes, just several times a day it'll just freeze and reboot. Data loss is a common occurrence. I've lost my WhatsApp! database several times now, and a few others as well.
Is this just me, or is CyanogenMod 11 this crappy for other people too? I can't find a way to prove to myself that this is a hardware problem, the Android Stability Test app just keeps going and going. I've been watching adb logcat during a crash, and nothing interesting is output. Any suggestions on how to troubleshoot this?
Click to expand...
Click to collapse
Try without encryption. It's hardly useful and only causes issues on Android.

Lethargy said:
Try without encryption. It's hardly useful and only causes issues on Android.
Click to expand...
Click to collapse
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.

starslab said:
We'll have to disagree about the usefulness of encryption, (I like that if my phone is powered off, my data is PRIVATE until and unless my passphrase is entered) but I'll wipe the phone this eve, TRIM it, and get setup on it again without encryption.
Click to expand...
Click to collapse
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.

Lethargy said:
Maybe it's useful if you have something important on your device, but really, if you do, it shouldn't be kept on your phone anyways.
On Android, encryption is nothing but trouble, maybe it doesn't cause issues right away, but eventually it'll cause many. If you really wanted to keep things secured then I don't see why you would unlock the bootloader, flash a custom recovery and install a custom ROM.
Click to expand...
Click to collapse
CyanogenMod has Privacy Guard, which is another feature I'm using, mostly with the aforementioned WhatsApp!, which has a list of permissions longer than my arm. I don't like it, but I need it for work.
I'll grant that the custom Recovery and ROM may slightly weaken the encryption (specifically an attacker could alter the ROM from Recovery), but even so having the encryption makes the phone a million times more resistant to data theft and tampering than not having it. It's worth noting that tweaking the ROM is the _worst_ an attacker could do. If I suspected such a thing had happened I could re-unlock the bootloader (which would wipe my data), and re-flash a known good Recovery and ROM. I'd lose my data, but even if the attacker had dumped the partition they still wouldn't have my key, and my data would still be private.

And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
its more then likely the encryption. Disable it, re-flash and see what happens

No encryption. Wiped and trimmed the phone yesterday, now 4 crashes.

Try another ROM, see if it crashes. If it still does, flash factory images and see if it still does.
If so, RMA.

Nothing but trouble for me since upgrading to m9. I have been using the various M builds since March with no problems. M8 was fine. No device encryption for me. I tried turning it on and instead got stuck redoing the whole phone.
Now I get frequent crashing. I switched to the most recent nightly yesterday. Apps stopped crashing. However the os itself still crashes. Several times the screen wouldn't turn on after removing it from my pocket. The light was blinking so it definitely didn't just turn off. It also has stayed black after a few (but not all) phone calls. I've had to hard reset every time to recover.
Thinking about reverting to m8 backup. Willing to give it a few more nightie and see if it works out.

Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
Where did you get it? I'm using the stable M9 snapshot off the CM site for hammerhead and it works pretty good.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Got it from the OTA update. Unfortunately I'm not experienced enough to know how to debug it or use proper logs. It could be that its an app I'm using combined with the most recent update...

Im using M9 snapshot too and i have not had 1 problem its been excellent

No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
+1. I installed another kernel (Chaos) for that reason and it's way faster.
OP: Maybe a bad flash? I would download M8 latest stable snapshot, and do OTA upgrade to M9. That's how I got mine.

C0dy said:
No problems for me on the M9 snapshot either. I'm coming up on 100 hours of uptime. Have you tried another kernel? I've always found that the stock CM kernel isn't the best. I'm using ElementalX 1..04 and it works pretty great.
Click to expand...
Click to collapse
Thanks for the suggestion. I actually have been using elemental and forgot to install it after the OTA. Will put that on now and see if it helps.

starslab said:
And the phone has crashed twice today. I'm going to repeat my original question - is anyone running Cyanogenmod 11-M on their Nexus 5, and if so is it stable? Should I be RMAing this phone, or should I try reverting it to stock first?
Click to expand...
Click to collapse
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.

simms22 said:
cyanogenmod is not what it used to be. it ALWAYS has one type of issue or another.
Click to expand...
Click to collapse
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Sent from Tapatalk on Nexus 5

last four hours have been fine since adding elemental. Hopefully works in the long run. 8/18 nightly.
Yeah it'll never be like the GB days. There's either audio problems, crashes, or other random problems. It's sad because people are expecting it to be like it was in old days. CM is not for stability, you can quote me on that.
Click to expand...
Click to collapse
What roms do you think are more stable than CM at this time?

trobbs said:
What roms do you think are more stable than CM at this time?
Click to expand...
Click to collapse
Just about any

[Q&A] [ROM][CM11.x]mastamoon's unofficial cm11.x

Q&A for [ROM][CM11.x]mastamoon's unofficial cm11.x
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM11.x]mastamoon's unofficial cm11.x. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hello, I just rooted my galaxy s3 from metro pcs and I have no signal!!!!
Can someone please help me. I used the the latest rom 10-24-14

CM12
Just installed on my verizon s3. All seems to be working well. Now I get to install all my apps. Thanks for putting this out there Masta
---------- Post added at 01:21 PM ---------- Previous post was at 12:39 PM ----------
swipe does not seem to work yet. home button doesnt bring phone out of sleep

The phone does not react as not to enter the call
Friend I need help my problem is that since 9/16/2014 M10 CM11 can not update my phone because when you upgrade to the latest version of CM11 and now updating your rom CM12, everything works fine wifi, data, text messages, all but the only thing is that I if I can make calls perfectly, but if someone calls me, the phone does not react as not to enter the call, but to put it together on the phone that is calling me hear them (tic, tic, tic) as when you put it near a speaker, meaning that the call reaches the cell, but the cell does not react. I hope someone help me or help me since I can not upgrade my phone.

juankva said:
Friend I need help my problem is that since 9/16/2014 M10 CM11 can not update my phone because when you upgrade to the latest version of CM11 and now updating your rom CM12, everything works fine wifi, data, text messages, all but the only thing is that I if I can make calls perfectly, but if someone calls me, the phone does not react as not to enter the call, but to put it together on the phone that is calling me hear them (tic, tic, tic) as when you put it near a speaker, meaning that the call reaches the cell, but the cell does not react. I hope someone help me or help me since I can not upgrade my phone.
Click to expand...
Click to collapse
If you've installed CM 12 your going to run into bugs on the rom as masta posted on several pages in the actual thread itself that there is and will be bugs
From my CM11 S3

What modem are you on?

sjpritch25 said:
What modem are you on?
Click to expand...
Click to collapse
ML1, been on it for quite awhile and I've never had any issues at all
From my CM11 S3

Weird. I'm on the same baseband & don't have that issue.

ShapesBlue said:
ML1, been on it for quite awhile and I've never had any issues at all
From my CM11 S3
Click to expand...
Click to collapse
I also have a SGS 3, now running Masta's Lollipop CM 12 initial release. I was on the same modem but updated to NE1 one posted by Masta in his thread. It does NOT lock the bootloader. Good luck and post back your results. Have a nanod backup just in case. Gary

Raphael0311 said:
Hello, I just rooted my galaxy s3 from metro pcs and I have no signal!!!!
Can someone please help me. I used the the latest rom 10-24-14
Click to expand...
Click to collapse
try putting a random micro sim card or a regular sim trimmed to fit micro sim in the sim slot, this works for the d2vzw and d2lte roms on the straight talk s3, we were having the same problem with these roms but a sim fixes data for us, maybe it will for you too, doesn't have to be a working or active sim just needs a sim in the slot to connect for some reason, hope this works for you
Sent from my SCH-S968C using Tapatalk

Misc data usage now at 40%, that's a lot higher than it was.
At 30% right now with one hour screen on time.
Pretty bad, haha
Sent from my SCH-I535 using XDA Free mobile app

XdrummerXboy said:
Misc data usage now at 40%, that's a lot higher than it was.
At 30% right now with one hour screen on time.
Pretty bad, haha
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Tried out the lollipop rom, it was solid until it froze on making calls. Flashed back to my backup of CM11 M12. I'll seriously wait until the bugs are worked out. Spotty calling doesn't make me want to run it at all
From my CM11 S3

Hi Everyone,
I'm still on an old CM10.1 masta build from 7-30-2013 and I'd like to get back into things with these CM12 alpha builds. How should I go about this? I know I need to update my firmware/baseband (still on MF1) as well, but what should be my order?
Recovery - nandroid
Flash - Firmware/baseband
Reboot - to make sure all is well
Back to recovery
Wipe data/cache/factory reset
Flash - rom/gapps/SU
Done?
Then just dirty flash subsequent builds?
Thanks for your help, I've had solid performance from this old rom but looking forward to an update.

Dfuentes said:
Hi Everyone,
I'm still on an old CM10.1 masta build from 7-30-2013 and I'd like to get back into things with these CM12 alpha builds. How should I go about this? I know I need to update my firmware/baseband (still on MF1) as well, but what should be my order?
Recovery - nandroid
Flash - Firmware/baseband
Reboot - to make sure all is well
Back to recovery
Wipe data/cache/factory reset
Flash - rom/gapps/SU
Done?
Then just dirty flash subsequent builds?
Thanks for your help, I've had solid performance from this old rom but looking forward to an update.
Click to expand...
Click to collapse
flash the ROM and Gapps THEN do your wipes, if you don't you might flash the ROM and when you reboot it might be buggy and you might think its the ROM when it might be something left behind from before so do your wipe so you don't run into that; always flash then wipe before reboot, sometimes you can skip that step and flash one over the other without wiping to fix issues in what you are flashing new but that's for experienced people to play around with and doesn't always work, anyway fkash rom and gapps then wipe and reboot
Sent from my SCH-S968C using Tapatalk

Ambient Display
So, this is in regards to the CM12 alphas, and since I don't have 10 posts yet, gotta post here.
Ambient Display was merged, which is pretty sweet, except it seems to randomly display for no reason. I don't have any notifications showing up, so why is it coming up? It can display several times in a minute, or go several minutes too, it seems pretty random. Only thing I can think of is it's picking up subtle vibrations and thinking I've picked it up?

no incoming calls
Anyone else having an issue with no incomming calls? Ive realised since a few months on cm11 i get no incomming calls unless its a private number.. I would love to use cm12 but theres the same issue. Seems to affect people using this phone outside the US like i am. I saw someone mention this in the main thread but im stuck posting here since im a new member :/

Yes my girlfriends phone after i installed cm11 on it. Never did figure it out.

Top and bottom mic swapped in skype and other such apps?!
First off my last no calls issue was solved with this file. i cant post links so maybe search d2gsm_rilblobs.zip
Ever since I've used CM on my S3 i noticed during my skype calls when i hold the phone to my ear the other person doesn't hear me well especially when there's allot of ambient noise!
I soon discovered that when using any app that records audio it uses the top mic only. but in regular phone calls through the network its normal using the bottom mic! Does anyone experience this? i mean it works fine and if u don't pay attention it may not bother you, but as an audio technician i notice these things! u can try if u have skype using the test call talk in the top and then bottom and you'll see the top is louder when its played back.
I went back to stock and the mic worked at the bottom as it should.. maybe there's a fix for this floating around? I have the Verizon S3 but if anyone notices this i would love to know its not just me!!

On masta's CM12 nightlies, I'm having an issue with data between flashes. When I dirty flash a nightly over the previous one, the phone refuses to connect to mobile data, even though everything is apparently fine. Anyone else have this issue?

ajtauro said:
On masta's CM12 nightlies, I'm having an issue with data between flashes. When I dirty flash a nightly over the previous one, the phone refuses to connect to mobile data, even though everything is apparently fine. Anyone else have this issue?
Click to expand...
Click to collapse
You try turning airplane mode off then back on? Make sure your mobile network is set to lte or 3g and not global.