Database Info

CM10 Known Issues

Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?

I just read you can sometimes follow the developer, does anyone know who that might be?

docdockstader said:
Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?
Click to expand...
Click to collapse
I can tell you that the 8/25 nightly breaks the dialer. 8/23 was working quite nicely, though. Only thing that was flaky for me was the bluetooth stopped auto connecting in my car.

http://code.google.com/p/d2vzw-cm10-bugs/issues/list?q=label:Priority-Medium

docdockstader said:
Is there a page that lists the known issues with the official CM10 nightlies on our GS3? I'm running it and haven't run into anything. Considering using it as my daily, but want to know what I might run into. Also, is there any Jelly Bean ROM that is 100% stable for our GS3's yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1840414
Some informal tracking is going on in ^this thread.
Official/Nightly CM10 is still suffering from occasional screen flicker (never did get that one resolved on MY phone) and the odd hot reboot now and again. Tell you what though... It was a lot smoother than ICS.
Unfortunately the S3 is my daily driver so I'm back on SynergyROM for the moment.

Back to Synergy 1.7 R50 & Theme DarkHorse v2.1
noobabuser said:
http://forum.xda-developers.com/showthread.php?t=1840414
Some informal tracking is going on in ^this thread.
Official/Nightly CM10 is still suffering from occasional screen flicker (never did get that one resolved on MY phone) and the odd hot reboot now and again. Tell you what though... It was a lot smoother than ICS.
Unfortunately the S3 is my daily driver so I'm back on SynergyROM for the moment.
Click to expand...
Click to collapse
Have had jb unofficial & official roms loaded this week and still
for me not a daily driver. Nice work and canot wait to use jb
as daily. Aug 29 I think they release jb international and will see
how long it takes to see the new roms & themes hopefully. Until
then spoiled on the Synergy 1.7 r50 & theme DarkHorsev2.1

dingurt said:
I can tell you that the 8/25 nightly breaks the dialer. 8/23 was working quite nicely, though. Only thing that was flaky for me was the bluetooth stopped auto connecting in my car.
Click to expand...
Click to collapse
Now that your mention it, this has been happening for me too. My Sync in my Ford can't find it and I have to toggle the bluetooth on my phone so it sees it again. I can live with it for now. I am just happy they have the boot loader unlocked now.

[Q] CM10 Google Nav crashing. Can anyone help?

I have been on CM10 for the past 4 weeks or so. Love it, but google navigation keeps crashing anywhere from immediately to ~30 seconds after launch. Maps, directions work fine, just when I launch NAV. running 20121101.063920 but this issue has been happening in the last couple of builds. Can anyone help?

I am seeing the exact same problem on recent CM10 builds for the Sprint EVO 4G LTE. I've been unable to find the cause.

wolfson292 said:
I am seeing the exact same problem on recent CM10 builds for the Sprint EVO 4G LTE. I've been unable to find the cause.
Click to expand...
Click to collapse
Yes, I've been following the issue as well. Still no luck, but it seems to be in the pipeline for a fix. Here's hoping.

Me too
I have the same issue. HTC EVO lte Other than that really annoying bug in GNav, I LOVE cm10. One other issue that I have is that sometimes on third party apps, when I pause music, it will pause, and then play for a second and then repause itself.

Same issue here... It happened to me since first nightly... I've lost hope... Will change to a sense based rom.

labroste said:
Same issue here... It happened to me since first nightly... I've lost hope... Will change to a sense based rom.
Click to expand...
Click to collapse
will not change, read the posts about the stock jb release sense based, we have the same problem. HTC is obviously sitting on its ass!! As usual.

Stuck with crashing NAV now.
Yep... I've tried several sense based roms since I originally posted this. I'm tempted to go back to stock ROM, but I'm Cincinnati Bell Wireless and haven't been able to find my stock one. I wasn't smart enough to back up the original ICS that came with the phone. Guess I'm stuck with whatever NAV can give me in the 15 seconds before it locks up each time.
fsamoggia said:
will not change, read the posts about the stock jb release sense based, we have the same problem. HTC is obviously sitting on its ass!! As usual.
Click to expand...
Click to collapse

Another EVO LTE user with same issue
Another EVO LTE user with the same problem. Almost immediately after opening to the navigation screen after selecting a destination, the app crashes. This seems to happen on 10 and 10.1.

Any fix yet?
Anyone know a fix to this yet?
Seems whether I run a stock-based or CM-based ROM I still get this issue if it's Jelly Bean.
The workaround has been to run Google Navigation in 2D mode... ALL the time...
Took some getting used to, but it's pretty silly to be stuck with this.
Long term... I'm moving to S4.

Phone freezes during a call on AOSP

I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?

ECrispy said:
I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?
Click to expand...
Click to collapse
I'm having the same issue running in baked

ECrispy said:
I'm running Rootbox (v3.9.1) and a few times, the phone just freezes during a phone call, and battery has to be pulled.
Have you seen anything like this? Could this be related to the kernel?
Click to expand...
Click to collapse
It's happened to me on Carbon as well as Liquidsmooth. It's probably related to Cyanogenmod (since most (if not all) AOSP ROMs are based off of CM).
sent from my anthraxed GS3 with MOAR goodness

Thank you us for the confirmations. I've noticed this is other AOSP roms and have given up, I hope it gets fixed by CM team soon.

Yeah sadly for that exact reason I had to ditch aosp hope they fix it . usually j would talk on the phone but when I hit the 5min mark my phone would freeze and either stay on or stay off then a couple mins later the call would get dropped and u would have to do a battery pull and what not I was running carbon 1.6.1
Sent from my SCH-I535 using Tapatalk 2

its been fixed on slimbean for over a week if you want to try that out.
havent had that problem running paranoid android either.

[Q] PA 3.60 Phone Calls Not Working

I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!

Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium

andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.

I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.

antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app

kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.

Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app

Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.

had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.

I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?

for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.

ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.

AOSP Random reboots

I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?

As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
As far as I am concerned CM is not very stable. Plus if you flash nighties that could be your issue. I read other people having random freezes and hot boots on LS 2.10. My suggestion to figure out if it's really AOSP (seriously doubt it) try LS 2.9. probably the most stable AOSP ROM out there. Also I have heard good things about older Slim Bean Builds. Do NOT do anything 4.3 related. 4.3 ROMs are still considered unstable.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive been using several 4.3 roms without one issue. Dirty Unicorn and Carbon have been prefect so far. Using latest twrp, full wipe and stock kernels.

Noremacam said:
I've been having a lot of random reboots when using AOSP based roms. So far I've used CM10.1.0, 10.1.3, 10.2, and liquidsmooth 2.10. As long as it is AOSP, the phone randomly reboots. Sometimes while it's just sitting on the charger or in my pocket.. After digging through this site I tried installing the firmware from here:
http://invisiblek.org/d2firmware.html
but I'm still having random reboots. I have a stock battery, and a later model brown S3 phone. TW roms work flawlessly.
Any advice?
Click to expand...
Click to collapse
What revision is your phone? Rev4? Rev5? My phone is a Rev0 and I'm not having any problems with running AOSP based ROMs.

I did too. I'm not sure WTF was going on, but ASOP/CM would be great for about a month, and then it'd start random rebooting. After it'd start random rebooting, the way to stop it would be to ODIN back to stock, and start over. Clean installs, nandroid restores, full formats.. None of it worked.
So here I stay on a crappy 4.1.2 TW ROM.. itching to return, but not really seeing enough improvements to warrant another go.

How are you restoring apps and data? I had problems after restoring via titanium backup, but when I restored selectively (just apps and data I really needed) with helium it's running fine.

this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?

Noremacam said:
this has to be a very late revision of the phone because it comes in the brown color that Verizon didn't start offering until recently. Even so, how do I determine the revision?
Click to expand...
Click to collapse
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
I believe it states the version when in download mode. (Vol down + home + power at a powered off state)
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Check in terminal emulator.
Su (enter)
cat /proc/cpuinfo (enter)
This will give you the revision number and a lot more about your phone.

I have "rev 4" on my brown GS3 and have been running CM10.1.3. The only time my phone crashes/reboots is when I attempt to use the front facing camera with a third party camera app.

Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.

Noremacam said:
Is it possible to get some logging of what's triggering the crash, so someone can take a look at it? Also right now, to the person who asked, I am reinstalling my apps from scratch from the play store. Since I haven't built up a lot of custom data for this phone to make it worth backing up.
I miss AOSP something fierce.
Click to expand...
Click to collapse
Download aLogCat from the play store and start the app. Then trigger the crash
Sent from my SCH-I535 using Tapatalk

What do you do if you can't cause it to crash? Mine are always totally random. It'll crash during a call, it'll crash while web browsing, it'll crash while locked in my pocket.. The only time it won't crash is when you want it to!
Do you just end up with a giant log file then or what?