yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Legacystar:
Any word on mhl compatibility ? I started a bug report on it if you guys wanna vote it up https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-2111
[Verizon Samsung Galaxy S III] boricua1213:
Google Play Store Issues

I installed gapps for 10.2. Google play store FCs, and when I go to the Play store on my computer says No active devices. Any ideas? Experiences?

8/20 Gapps

Running 10.2 9/3/2013 Nightly

Thanks
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks for posting this over in this thread - didn't want to clutter the Dev thread. I was hoping someone else would have an answer for your issues. When you said you installed GApps, were you previously running the ROM without GApps (just curious)? I've had no issues with 10.2/GApps like you're describing. Sounds like you need to try again, as the GApps didn't properly install. If the GApps didn't properly install, the Play Store won't recognize your device (because it's not connected). Are your signal bars grey? What recovery are you using? You can try wiping system and reinstalling the ROM and GApps to see if that fixes it. For posterity, redownload the GApps to make sure you didn't have a bad download.
[Verizon Samsung Galaxy S III] boricua1213:
I was running 10.1 with Gapps, flashed 10.2 over 10.1 using Cyanogenmod Update function in system settings, booted then notice google stuff not working so downloaded Gapps and flashed.

Signal bars are not grey.

I'm using ClockworkMod 6.0.3.6

I'll try to reinstall Gapps.
[Verizon Samsung Galaxy S III] Hybridnoob:
Did reflashing GApps fix it?
[Verizon Samsung Galaxy S III] boricua1213:
Well, hard to tell on the FC issue. Has not FC yet, but has done that before where it won't FC for the good part of the day. Still have the issue no devices on google play website.

EDIT:

I deleted Google Account (which caused phone to reboot) and added it back in. Store site now has my device and able to install app via web. We'll see the FC comes back.
[Verizon Samsung Galaxy S III] jonathan413:
Does this rom support open gl 3.0 and/or TRIM for gs3?
[Verizon Samsung Galaxy S III] iofthestorm:
If you still have issues, I recall at some point it was necessary to flash gapps in the same recovery session as the ROM, not sure if that's still true but I do it when I have to flash a new version of gapps.
[Verizon Samsung Galaxy S III] SyddyS:
Bunofasitch. Good thing I came here to "warn" people about the 9-6 nightly ;)

Remind me to check here _every_ time before flashing.
[Verizon Samsung Galaxy S III] asymptoticFault:
Been watching the 10.2 dev and Q&A threads since they started and I get the impression the builds are still pretty unstable at this point. I understand that nightlies are, by their very nature, potentially unstable but the 10.2 builds seem particularly so. I know 10.2 hasn't been around long but it seems to be a much rockier start than 10.1 from what I remember. I've seen many posts about bootloops and freezes, as well as battery drain and FCs. I have been wanting to jump to 10.2 but have reservations about doing so from everything I've seen. I don't have any problem with running nightlies, I've actually been on an older 10.1 nightly for quite some time.

So I was hoping to get some feedback from those brave souls out there about the stability of the 10.2 nightlies. Can you get through a day without any serious issues? How's the battery life? I saw there was a fix for Focal a little while back but sounds like it is still having issues, however does it still cause the battery drain and other issues if you even open it? I don't have an issue avoiding Focal for the time being but just want to be sure it isn't adversely affecting the build stability.

I greatly appreciate any information. Also, just to clarify, I am NOT bashing the builds or speaking negatively of the CM devs. They have done an outstanding job and I love CM. I have never looked back since ditching the stock TW ROM and I am so much more satisfied with my s3 with CM on it; the customizability and speed is like night and day. I am just trying to get a feel for whether I can make the jump to 10.2 right now or not.
[Verizon Samsung Galaxy S III] iofthestorm:
For what it's worth I haven't had many issues, just don't open Focal and you're good. It might actually be sort of fixed now, at least you can open it without FCing immediately, but I still haven't bothered to look into it any more than that. I actually somehow never had issues with battery drain either despite flashing almost every nightly since 10.2 started. I do have some GPS and rebooting issues but I think it might just be because of me dropping my phone in water a year ago, though it's worked reasonably well since then I seem to get more random reboots than others so I don't blame them on the ROM.
[Verizon Samsung Galaxy S III] rgrossie:
FWIW I too haven't had any major issues with CM10.2 nightlies. I'm on the 9/5 version now since the last 2 won't boot. There are a few weird things that occur occasionally, like the occasional FC, slow-mo movement, and maybe once per day a random re-boot, but generally it works pretty well. My experience with these builds is that they improve very slowly at times while at other times the improvement from day to day is dramatic. It's a pretty good daily driver at this point. I'm grateful to the CM team for putting in the work to build a cool ROM for us all.
[Verizon Samsung Galaxy S III] asymptoticFault:
Just updated to the 9/5 nightly and so far so good :) Thank you iofthestorm and rgrossie for the feedback :) Also thank you Restola and everyone else for the heads up about avoiding the 9/6 and 9/7 builds.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I'm just popping in to give my thanks to the moderator/creator of this thread for keeping us posted on which nightlies don't boot and such! Thanks! :D

sent from my GS3 running CM10.2
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm happy to report 9/8 boots. I just flashed it...
[Verizon Samsung Galaxy S III] buschbarber:
Thanks!
[Verizon Samsung Galaxy S III] SyddyS:
Possible culprit of some folks "random reboots" ?

Mentioned a few posts back I was having rotation-related crashes. After a lot of narrowing down, and after trying it on Trebuchet as well as Nova Launcher, I've landed on Business Calendar's home screen widget as the culprit. This has been the case on every nightly that I have flashed since the first 10.2 nightly, up to and including the 09/08/13, and most often happens during the unlock process.

Removing the widget removes the problem, and I experience almost no crashes or reboots when I do.

I have contacted BizCal's support, and as it was not a "stock launcher" they did not seem to eager to look into it.

Just throwing that all out there in case it's related to anyone else's issues. When I remove the widget, pretty much all the nightlies have been just fine daily drivers, with almost no issues. Great work CM!

-SyddyS
[Verizon Samsung Galaxy S III] Crewski:
Running the 9/8 nightly right now...and quiet hours doesn't seem to work. I have it set to mute notification, disable vibrations, and disable notification light. I turn it on using the quick toggle from the notification bar, but it doesn't do anything. I still get emails notications, lights blinking, etc during the night.
[Verizon Samsung Galaxy S III] Restola:
Mine worked last night. I'm on today's version now, I just changed my quiet hours to include right now and instantly the LED stopped flashing.

Wipe cache/dalvik and re-flash your download over itself. See if that fixes it.
[Verizon Samsung Galaxy S III] ZeroCool11:
Hi I just put this CM10.2 CFW to my S3 (i535), and the thing is that i want to use it with GSM network... and i can't choose GSM...it doesn't show any network available... so, what can i do??
[Verizon Samsung Galaxy S III] Crewski:
Yep...it was my own fault it that it wasn't working. I was thinking that the toggle in the quick panel would just turn it on and off at will. I never set up times so it was the default 12:00am to 12:00am. I realize now that the quick toggle just turned "enforce quiet hours" on and off.

So, my solution was to set the quiet hours from 12:00pm to 11:59am (essentially all day) and then the toggle will turn it on and off the way I wanted.

Thanks for checking!!!!!!
[Verizon Samsung Galaxy S III] wolficus:
Curious... Anyone have an idea why I cant view my apns? They are working... Just I can't view them....

Running 9/10 nightly... I think a few nightlies ago I could.
[Verizon Samsung Galaxy S III] rhcreed:
Anyone using 9/12 nightly, everything cool?
[Verizon Samsung Galaxy S III] iofthestorm:
Random question, anyone use USB host, and does it work for anyone else on a recent nightly? Just wanted to test something out and realized it wasn't working anymore for me, but not sure if it's just my adapter (seems doubtful but dunno). It definitely has worked at some time in the past, but then so has MHL - l guess stuff breaks across kernel versions and it's hard to debug them.
[Verizon Samsung Galaxy S III] Hybridnoob:
All good here!
[Verizon Samsung Galaxy S III] Spyrano:
USB host still works for me on the latest nightly (9/13), though not right away. I had to unmount my flash drive, then remove it and plug it back in before it could read it.
[Verizon Samsung Galaxy S III] iofthestorm:
So when you initially plug it in it does auto mount it? Hmm I think I might just need to find a proper fat32 single partition drive, most of my usb drives are either formatted NTFS or have multiple partitions. I was actually trying to test to see if android/CM included NTFS drivers but it's looking like no. Lsusb does show something when I plug it in so I guess it must be working.
[Verizon Samsung Galaxy S III] bigboludo:
What Network Mode are you on? I'm on CDMA+LTE/EVDO and can't see any APNs either, but my LTE data is working.
[Verizon Samsung Galaxy S III] wolficus:
I have tried both global and CDMA+late/evdo.

The only time I saw my apns was when my sim card wasn't recognized. As soon as it saw my card.. Poof. Gone. ATM I can use APN manager pro to see and edit them.

Was more curious if it a ROM issue.. Phone issue... Ect.
[Verizon Samsung Galaxy S III] big_boludo:
Lately I have to jump thru hoops to get LTE. I have to choose CDMA/EVDO auto, wait for it to connect to 3G, then use my drop down toggle to turn LTE on and hope it connects. It usually does, but not always.
[Verizon Samsung Galaxy S III] drake90001:
I'm having an issue with my carrier. Everything works with data, calls, etc, but this is what is says my carrier is:
[Verizon Samsung Galaxy S III] Hybridnoob:
This will be fixed on the next nightly. http://review.cyanogenmod.org/#/c/50441/
[Verizon Samsung Galaxy S III] drake90001:
Oh. I just found it weird that it has happened on Paranoid Android as well.
[Verizon Samsung Galaxy S III] Restola:
FYI focal is gone on the next nightly. Sounds like it's being returned to it's author to pursue as a standalone project (not that it ever worked that well for our devices).
[Verizon Samsung Galaxy S III] iofthestorm:
Ah, that's quite interesting. I heard (from a CM Exynos4 maintainer) that he was upset about the whole CyanogenMod Inc thing and was originally pressured to relicense it in the commercial friendly Apache license. I hope he does well with it as a standalone app though it's sad that sort of political issues prevented an improved default camera app.

Hmm, looks like it was resolved amicably from the Gerrit comments but I still want to hear xplodwild's story.
[Verizon Samsung Galaxy S III] SyddyS:
Exactly my reaction to the news...
[Verizon Samsung Galaxy S III] Restola:
Someone linked to the whole story in mastamoon's unofficial thread earlier today. It's long but worth the read.
[Verizon Samsung Galaxy S III] iofthestorm:
Yup, I read it, I was the second person to comment on the G+ post lolol. Been obsessed with it all day :/

I hope it ends up okay though. Would hate to have to switch ROMs for ethical reasons.
[Verizon Samsung Galaxy S III] tducote:
Whenever my phone is connected to a bluetooth device, I would like the notification tones and ringtones to come through my phone's speaker, while any media audio (music, video audio, etc.) and possibly phone audio to come through the bluetooth device.

Right now, the phone's speaker is basically disabled when the phone is connected to any bluetooth device. The problem with this is that if my phone is connected to my car's stereo, but I'm listening to a different input (or if it is connected to my LG Tone+ headset, but the ear buds aren't actually in my ear), then I receive no sort of audio notification when I get a text message or any other notification.

Is there a setting I can change somewhere, or a zip I can flash, or an app I can install, that would make my dream a reality?

Thanks,

tducote
[Verizon Samsung Galaxy S III] rgraville:
NFC.apk?

I just updated from cm-10.1.3-RC2 to the CM 10.2 9/19 nightly. It was a dirty flash but cleared cache and dalvik. Updated gapps.

Upon boot several apps complained and force closed (Wunderlist, Youtube, Voice, Hangouts) and the same apps would force close on subsequent reboots. I updated any app complaining about force closing with available updated from the Play Store. For Voice, it was up to date. Uninstalled Voice and reinstalling Voice. reboot. No more apps force closing on boot.

Everything seems happy, except NFC.apk does not appear to be working. The .apk file is in /system/app with the correct permissions. When I go to System Settings > Wireless & Networks > More... there is no entry for NFC to be enabled or disabled. I have tried re-launching the NFC.apk file but I get an app install failed message with no specific error listed.

Is anyone else missing the ability to enable/disable NFC? It is not force closing, i think it is simply not loading on boot for some reason. I do not know why. If my NFC.apk is corrupt, is this file included with nightlies? If not, where can i get a clean copy?
[Verizon Samsung Galaxy S III] Restola:
Re-download the nightly, wipe cache/dalvik and dirty flash it over top. See if that fixes it.
[Verizon Samsung Galaxy S III] rgraville:
That worked. Thanks for that. Not sure what happened but all seems good now.
[Verizon Samsung Galaxy S III] SerialTurd:
UPDATE - Found a post on CM's forum with this exact issue. I had to use the 0301 gapps for this to work.

http://forum.cyanogenmod.com/topic/72186-unfortunately-android-keyboard-aosp-has-stopped/

ugg again I'm having trouble with install CM. I posted about this a couple pages back but every time I install a clean version of CM, the android keyboard doesn't work. I get a message about the android aosp keyboard doesn't work.
[Verizon Samsung Galaxy S III] Restola:
I didn't see your earlier post. Have you tried a clean install with the 8/20 gapps in the op?
[Verizon Samsung Galaxy S III] SerialTurd:
Yes. I used the latest gapps posted in the open and that have me trouble with the keyboard
[Verizon Samsung Galaxy S III] npro1464:
I flashed the stable CM 10.1.2 a week ago (before the 10.1.3 stable release), and I've been getting terrible battery life. Is my battery shot? Will flashing 10.1.3 help? Thanks!
[Verizon Samsung Galaxy S III] bigboludo:
Anyone else having this issue? I just did a full wipe/clean install (of 9/25) and still having problems. My phone will not connect to LTE unless I go change the network mode to "CDMA/EVDO Auto", wait for 3G, then switch the LTE on.
[Verizon Samsung Galaxy S III] drake90001:
Can anyone tell me if they have any issues with DSP Manager? When I use it, I get a loud pop in my music rather than the effect. It sounds like the files corrupted, and doesn't stop till I restart the track with it off.
[Verizon Samsung Galaxy S III] Decantur:
On 9/26 and do not have this issue - switched several settings in DSP Manager while music playing.
[Verizon Samsung Galaxy S III] drake90001:
I reflashed and the issue remains. Not sure how to describe it. Enabling compression causes a poping sound, tried three different pairs of headphones.
[Verizon Samsung Galaxy S III] ummduh:
I recently had to odin back to stock.

Not sure what went wrong, but my phone started crashing/rebooting at random 6+ times a day. Usually after locking the screen, but it'd crash during phone calls, while web browsing, taking pictures.

I tried clean flashing, dirty flashing, wiping everything, nothing helped. I even had to odin 2 times, the first time it crashed just as much. Still not sure what changed, but the second odin flash fixed it, and it's been great since then without a single crash.

Anybody have any clues as to what could have gone wrong? I'd like to go back as TW sucks, but I'm a bit hesitant now.

I had been downloading the nightlies via cmupdater, and flashing using CWM non-touch.
[Verizon Samsung Galaxy S III] Decantur:
Just tried with a couple of different headphones, with compression and other settings and just not seeing it. Might be you have a hardware issue. Sorry, man.
[Verizon Samsung Galaxy S III] jbjarko:
On CM 10.2 9.27 nightly since this morning. Didn't have any issues all day til about an hour ago or so. Flashed 9.26 & 9.25 - didn't fix the issue. I can receive SMS, data works, etc. Wiped everything, and flashed 9.27 and it worked for a bit. and then quit working.

Slept on it and nothing has changed, still doesn't work.

What I don't get is that it just suddenly stopped working, one minute to the next.

Thanks
[Verizon Samsung Galaxy S III] ericsdeadinside:
lpa.decode=false

Has to be set in your build.prop
[Verizon Samsung Galaxy S III] drake90001:
Aye, that did it. Thanks!
[Verizon Samsung Galaxy S III] yhknq:
Is there a way to adjust screen resolution? For instance on slim bean rom you get 7 apps on the dock and you get a whole lot more on the screen because everything is smaller. I was hoping to be able to get that look on cm.

Thanks for any help
[Verizon Samsung Galaxy S III] Restola:
If all you want is more apps on the dock and more space to put apps on your homescreens then a new launcher will do that for you. Check out Nova launcher for example. You can adjust the grid size of the home screens and add more slots on the dock.

I dont think you cannot do that in the stock launcher.
[Verizon Samsung Galaxy S III] yhknq:
Thanks for the help
[Verizon Samsung Galaxy S III] XdrummerXboy:
Have you guys had any random reboots with the night lies for the past week or so? Nothing really triggers it. A couple times when I pull down the notification bar, a few other weird times. Sometimes even when I don't even have my phone awake or doing anything.

sent from my GS3 running CM10.2
[Verizon Samsung Galaxy S III] Hybridnoob:
I'd say I've had random reboots since the 10/18 build. I just keep updating every day waiting for it to be resolved ;)
[Verizon Samsung Galaxy S III] ayush20m:
I recently updated to 10.1.3 stable but didn't get a chance to test the GPS. Turns out it has a lot of issues getting a GPS lock and randomly losses GPS signal. Discovered it too late. I'm on a trip. Dis anyone know of the same issues with 10.2. If not I'll give it a try and see if I can complete this trip without having to buy a GPS.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Works fine for me, but every person can have a different outcome it seems

sent from my GS3 running CM10.2
[Verizon Samsung Galaxy S III] dcorwin822:
Bluetooth MAP support

Does the nightly have bluetooth MAP support?
[Verizon Samsung Galaxy S III] sharoon01:
Network Operator / Roaming Issue

I'm currently in the UK on a MVNO that works off of Vodafone's network. It works wonderfully on CM 10.1.3. I tried to dirty flash CM10.2 and under mobile networks the Network Operator option was grayed out. I was still able to use the data for the network (Sainsburys), but I couldn't receive calls or texts. Tried to restore to a backup with no luck.

Restored to stock, rerooted and all that jazz, went back to 10.1.3 and it was working fine. Tried to do a clean install of 10.2 to see if it works, still no luck. Tried a different nightly and nada. My network provider says Verizon instead of Sainsburys and I can't get it to pick-up anything else. I'm using the MF1 baseband. Anyone have an idea of what I might be doing wrong or forgetting to do?

Thanks!
[Verizon Samsung Galaxy S III] puroc:
Manage Networks option grayed out.

I tried the 10/27 Nightly [d2vzw] PAC-Man AIO and the Network Operators in Mobile Networks setings option is grayed out. I am using the phone with a Lycamobile SIM so I need to manual register the network sometimes. Rolled it back to 10/21 nightly and the option is available again. I do a complete wipe prior to each install. Anyone else have this issue?

---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------

Does anyone have a work around for the DTMF issue? It seems that ASOP will not allow in call DTMF tones and all the posted work arounds (Turning off dial pad tones,long pressing keys) have been patched:rolleyes: Lycamobile is touch tone driven when setting up the SIM. Seems silly that I have to pull out my old flip phone everytime I need to do something. Also useful with checking voicemail.
[Verizon Samsung Galaxy S III] bjazz69:
Does mhl sound work?
[Verizon Samsung Galaxy S III] rhcreed:
Everything solid on 10/28? Running 10/21 and wanted to be sure nothing is broken. Thanks!
[Verizon Samsung Galaxy S III] Restola:
[MENTION=4494791]rhcreed[/MENTION] 27 is great. Traveling for a few so haven't flashed 28 yet (never flash on the road lol) .
[Verizon Samsung Galaxy S III] Hybridnoob:
10/27 has been great for me. Had some random reboots on every build since 10/18, so happy to see this one more stable.
[Verizon Samsung Galaxy S III] fluffman86:
Hi, I just dirty flashed to 10.2 from 10.1, wiping only cache and Dalvik. Since I switched, I've had some trouble with Gmail not syncing and my signal bars turning gray. Wifi / Data still works during this time, but I have to manually check for new messages in Gmail as I never get the notification.

The only way I've found to fix this is to Disable Gmail under the Apps menu (which also uninstalls the updates) and then to re-enable it. Then my bars turn blue and new mail starts coming in, at least for a few hours. Then I repeat the process.

I'm running 11/1 nightly with the Mastamoon 8/20 GApps. Thanks for any help you can give. I'd prefer not to completely wipe as it takes so long to install apps and get my home screens rearranged and quick settings set up, etc.
[Verizon Samsung Galaxy S III] Restola:
[MENTION=1003556]fluffman86[/MENTION] try clearing app data for gmail. You'll need to set it up again, but only that app.
[Verizon Samsung Galaxy S III] fluffman86:
Yeah I've cleared data and cache for gmail several times, and even uninstalled updates and disabled.
[Verizon Samsung Galaxy S III] droidfreak02:
Is the cm 10.2 snapshot a stable release or is it still a nightly
[Verizon Samsung Galaxy S III] Restola:
It's a M
[Verizon Samsung Galaxy S III] bcurtiswx:
So I've been using the nightlies, but would like to start staying with stable releases. Can I just flash an M1 and be good, or is it more complicated than that?
[Verizon Samsung Galaxy S III] Hybridnoob:
Yep, it's really easy. Provided you're already using CM10.2 nightlies, just use the built-in Cyanogenmod Updater. Backup first just in case, but all should be well.
[Verizon Samsung Galaxy S III] joedajoester:
I've found that this version has the absolute worst battery I ever had. Anyone else? It was the fastest cm yet, but the battery drained incredibly fast.

*EDIT* I reflashed it and I'm getting good battery life now. Maybe it was an app I had that was draining it. Also, anyone know a better workaround for the bass bug? I found only a temp fix that lasts about 1 or 2 songs.
[Verizon Samsung Galaxy S III] iclickjohn:
I haven't been able to access the (CM) change log (web) since Thursday. Downloaded the official app and it is blank as well. I'm on latest nightly. Does that mean I've got M1?

Edit: is working again. And I understand that I'm past M1. And can say is still stable for me.