CM10 Known Issues - Verizon Samsung Galaxy S III

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.

Related

Problem With AOKP

OK Im having a problem with AOKP, So im running AOKP 6.2 a couple days ago and Ive been running it for a while and every once in awhile it randomly reboots, OK No Big Deal, but then i need to use Google Nav to find the hospital my mom is currently in, so i launch the app type in the address and BOOM.......Random Reboot ok so i wait for it to reboot and load it again, BAM same problem every single time i launch Google Nav it randomly reboots so i get home and see that 6.4 has been released so i download it, Flash it and Launch Google Nav and it runs fine for awhile and then i exit out of Google Nav, Then This Morning I get in my car and type in the address of my moms hospital and hit Go and everything is fine until i get to the main road and guess what happens?......... IT ****ING STARTS THE WHOLE **** OVER AGAIN OVER AND OVER AND OVER IT JUST KEEPS REBOOTING. So my question is has anyone else had this same problem or a problem with AOKP randomly rebooting and did you fix it if so what did you do to fix it, Thanks ahead of time
because your running aokp that isnt official for our device yet.
Same for cm.
If you want no reboots, then use a stock rom. xS or scots roms, or the beta build by calkulin
And why dont u post this in the aokp thread???
expertzero1 said:
because your running aokp that isnt official for our device yet.
Same for cm.
If you want no reboots, then use a stock rom. xS or scots roms, or the beta build by calkulin
Click to expand...
Click to collapse
Not true. This isn't an AOKP problem, it's a problem with the latest version of Google Maps:
http://forum.xda-developers.com/showthread.php?t=1838280
Silellak said:
Not true. This isn't an AOKP problem, it's a problem with the latest version of Google Maps:
http://forum.xda-developers.com/showthread.php?t=1838280
Click to expand...
Click to collapse
Yup I had it happen to me as well. On AOKP.
gunnyman said:
Yup I had it happen to me as well. On AOKP.
Click to expand...
Click to collapse
Yeah, AOKP is definitely affected by it, but the problem exists on multiple devices and multiple ROMs.
On CM10 now and I haven't bothered to upgrade Maps because even if the reboot issue is gone, it still causes huge battery drain in the background. Dammit, Google.

[Q] Stability of CM10?

I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
brob925 said:
I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
Click to expand...
Click to collapse
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
brob925 said:
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
Click to expand...
Click to collapse
The night lies have been down because some changes were made to the code upstream that causes the Evita build to fail. They're working on the kernel fixes to get the night lies to compile again but apparently its very involved.
Sent from my One X using Tapatalk 2
There was an experimental one posted today
my wifi doesn't crap out on the experimental nightly which was my only issue with 10/12
One should always read at min the last 10 pages of a thread of a Rom you might flash, an really it's expected of anyone.
WR
Sent from my HTC One X
Just a heads up dont know if anyone else is having this problem.
I rooted my 2.2 with the new 2.2 root instructions and downloaded the latest (10/25:experimental[cm-10-20121025-EXPERIMENTAL-evita.zip ]) cm10 build, everything works great, even wifi, except MOBILE data. I'm on straight talk, and man im getting slow speeds, nothing changed to APN, i think its a radio problem. anyone got any suggestions? I attached the radio link, which radio should i flash?
http://forum.xda-developers.com/showthread.php?t=1694012&page=99

CM 10.1 (JB 4.2) on my Cappy = awesome

Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yeah Factory reset is recommended. And its Working great. I must ask you to consider updating to 4.2, 10.1 nightly build. Its literally flawless...
Sent from my SGH-I897
cm10.1 really cool. Waiting for slim android 4.2
Several days ago I did the upgrade to 10.1 from 10 without the factory reset - no problems, but wipe the caches). You need to clear the clock data first and do the upgrade from the boot screen (not the update screen in about phone). Do a backup just in case you have problems.
for further info go to :donandroid.com/how-to-update-cm10-to-cm10-1-with-cwm-recovery-581
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
+1
Sent From the Land of Defrag
if you do Erase SD Card, does it erase internal storage instead?
I tried the stable version of CM10, and it seemed to work great except for one thing. I could connect to my employer's Exchange server at all. I tried all kinds of things and it just couldn't connect. I took it to the IT guys and they fiddled with it for a while and couldn't get it to work either. A little quality time with Google told me that JB has a bug that sometimes makes it impossible to connect to corporate exchange accounts. I ended up switching to CM9. Do you know whether CM10.1 fixes that? If so I think I'll give it a try.
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
Slim 4.2.1 has been available in beta for a week or two now... I've not encountered any problems with beta 2 so far.
http://forum.xda-developers.com/showthread.php?t=2060386
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
thank quá hay :
theoctagon said:
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
Click to expand...
Click to collapse
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
laughingT said:
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
Click to expand...
Click to collapse
So for a stable fast ROM, you would suggest CM 10.0 over AOCP or some of the other 4.1.2 "final" version ROMs like SlimBean?
depends on your personal preference I suppose. you need to get to CM9 at least, preferably 10.0, to flash slim bean, right? So, if it runs well on 10.0, then you could go slim bean
you wrote that you just want the basics, nothing fancy. so, yes, CM10.
Sent from my SGH-I897
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yes, I did. And I didn't really have any problems with Semaphore, it just seemed a little laggy.
RichMD said:
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
Click to expand...
Click to collapse
I would highly recommend Sephhi's [ROM][4.2.1]Captivating (Xperia Themed)
It is CM10 based and is stripped down to run smooth.
http://forum.xda-developers.com/showthread.php?t=2057574
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
BELbX said:
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
Click to expand...
Click to collapse
Try hellybean 4.2. Hellybean came a long way from when i used it a while back! It's a much smaller and light weight package as compared to the xperia one. Barely any issues. Boot times and first boot are quick. Over clocking is fun again too. I thought it was oc'd at first for being smooth. It's so smooth and stable. One or two things, but nothing compared to others. I like the xperia one but it's heavier with more to be worked. It's running better then aokp 4.1 with semaphore.
Sent from my SGH-I897 using xda app-developers app
3g Problem
I just flashed 4.2.1 AoCP 5 and lost my 3G. Anyone know what's up?

[Q] Most Stable JB Rom?

Hi, I was wondering what in your opinion is the most stable JB rom? My parents and I all have a Skyrcocket, and they have been on CM9 for a while now. They don't know much about how to use their phones, so that is why I got them a stable version of CM9 last summer, while I have been on JB since it came out.
I have tried a wide variety of JB roms, but I know how to use them all well and what to do in case of most issues, even minor ones such as having no connectivity on reboot. My parents however get really confused when stuff like this happens, and don't even think to reboot, even though I have told them about how to fix it numerous times. On the CM9 they have, stuff like this never happens and it all is pretty stable.
However, my mom recently started having random problems on CM9, so i upgraded her to the latest stable CM10 and installed gapps, UCLK4 radio, which works the best for me, and lightning zap kernel. Now she is having weird problems like her camera not working due to the error 'no external storage present,' which i have encountered on another jb rom before, and reflashed a different one to fix it. i just tried slim bean 3.1 for a while to test for her, and i get weird stuff like the no connectivity on boot issue i mentioned before, which can be fixed with a reboot, but is too big of a problem for my parents to handle. i also tried cm9 the latest nightly just yesterday, and am experiencing some weird minor issues as well.
i even thought about going back to ics, although she would prefer to upgrade if possible. and i thought about flashing the latest att jb leak, but i figured that would most likely have even more issues, haha.
so does anyone think there is a jb rom out now that is as stable as cm9 ics was? thanks!
Just put them back to stock. You're nuts putting a custom rom on someone's phone who isn't into the issues they have. They all have something that doesn't work as you'd expect.
Sent from my SGH-I727 using xda app-developers app
I think you have to read through the threads and see which one(s) fit your needs best, then try those ROMs for yourself instead of starting a best thread.
jd1639 said:
Just put them back to stock. You're nuts putting a custom rom on someone's phone who isn't into the issues they have. They all have something that doesn't work as you'd expect.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I'm with you, i like official roms, I personally like HTC phones before using my skyrocket (ROMS work great on HTC and stock ROMS are also great), the official ICS on skyrocket sucks big time (to laggy), but I still like it better than custom.
Sent from my SGH-I727 using a crappy windows XP machine.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
onearmedscissor said:
Hi, I was wondering what in your opinion is the most stable JB rom? My parents and I all have a Skyrcocket, and they have been on CM9 for a while now. They don't know much about how to use their phones, so that is why I got them a stable version of CM9 last summer, while I have been on JB since it came out.
I have tried a wide variety of JB roms, but I know how to use them all well and what to do in case of most issues, even minor ones such as having no connectivity on reboot. My parents however get really confused when stuff like this happens, and don't even think to reboot, even though I have told them about how to fix it numerous times. On the CM9 they have, stuff like this never happens and it all is pretty stable.
However, my mom recently started having random problems on CM9, so i upgraded her to the latest stable CM10 and installed gapps, UCLK4 radio, which works the best for me, and lightning zap kernel. Now she is having weird problems like her camera not working due to the error 'no external storage present,' which i have encountered on another jb rom before, and reflashed a different one to fix it. i just tried slim bean 3.1 for a while to test for her, and i get weird stuff like the no connectivity on boot issue i mentioned before, which can be fixed with a reboot, but is too big of a problem for my parents to handle. i also tried cm9 the latest nightly just yesterday, and am experiencing some weird minor issues as well.
i even thought about going back to ics, although she would prefer to upgrade if possible. and i thought about flashing the latest att jb leak, but i figured that would most likely have even more issues, haha.
so does anyone think there is a jb rom out now that is as stable as cm9 ics was? thanks!
Click to expand...
Click to collapse
Install official ICS to them, no more problems, but on the downside, a lot of lag will be present!!!
From the moderator
DO your research on this as it really is a personal decision. As stated by others all roms have something that is buggy. My personal take if they are not into customizing but want good battery life, and the basics to work well and do not need a bunch of bells and whistles you might try AOKP roms as they work well and are easy to configure for a novice.
That said, there are way to many "Best rom" threads..... So
>>>>> ........ THREAD CLOSED.........>>>>>

[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

Categories

Resources