yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] rage913:
I downloaded the 24th nightly and it borked everything on my phone. Philz Advanced recovery was trashed so I couldnt do anything kept throwing me in a bootloop. I was able to get back to download mode flashed cwm touch through odin and tried to reflash KitKat but im assuming that because my cwm recovery is slightly older thats why it wasnt letting me get back into KitKat. thank god for backups...had to revert to my jb liquidsmooth backup ill try and reflash the 24th once my phone boots and I can find the latest cwm tar
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
I dirty flashed from 1223, no issues except for bluetooth doesn't automatically connect to my car. I just have to connect it and it works though.
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
You can use any custom ROM as long as it's not below Android version 4.3. I just flashed CWM on my unrooted 4.3 update and flashed a ROM.
[T-Mobile, Samsung Galaxy SIII] Christopher4tw:
Thanks! I appreciate the help. Might try this ROM out tomorrow. Have a merry Christmas!
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
1226 nightly, I had it freeze and reboot on the boot animation twice right after install, booted up fine the 3rd time. There were a few camera modifications in the latest nightly. The camera is snapping pics faster, focusing faster on auto focus. Running good so far
[T-Mobile, Samsung Galaxy SIII] silverton:
And mine booted up just fine the first time. Weird how some devices bootloop a couple times and others don't. Mine did this on the 1224 or 1223 nightly. I panicked for a second, haha.
[T-Mobile, Samsung Galaxy SIII] rage913:
Anyone using snap chat having terrible ffc issues? It's really stretched out and it's causing my phone to lag out and force close snap chat when I try to record a video using the ffc. I use the back camera and everything is fine. Running 1226 nightly with kt747 on top.

Also anyone using visual mail can you explain what it actually is? Lol I Googled it and it's like listening to your voice mail as someone is leaving it? Or am I derpy...
[T-Mobile, Samsung Galaxy SIII] snipinu:
Visual voice mail is a paid feature by tmibile I believe its either 3.99 or 4.99 per month after a free trial it displays your voice mail in a SMS like message

---------- Post added at 06:40 PM ---------- Previous post was at 06:37 PM ----------

I also had an issue with the latest nightly i lost Google play store and most of the other apps didn't work I reflashed gapps 1215 and seems to be working but there were no changes listed for that portion of the ROM weird.
[T-Mobile, Samsung Galaxy SIII] HoustonsBirdman:
Can anyone confirm if the Camera video recording still force closes or if its been fixed
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Shot two videos on 1226, no issues.
[T-Mobile, Samsung Galaxy SIII] rage913:
Yup its all good on my end as well running the 26th as well I belive or maybe the 25th can't remember lol.

Other topic, is there a way to disable the input method notification in the tray? I know it's not a big deal it's just annoying as heck to see it up there as I type something
[T-Mobile, Samsung Galaxy SIII] vvMINOvv:
What's a trusted source for gapps? I'm worried about getting it from somewhere where it had been tampered with.

Sent from my wondrous contraption
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Wrong. See below reply.

Since there's so much misinformation about this, I'll reply. If you update your bootloader to the official 4.3's, then you cannot ODIN your way back to an earlier firmware such as MD5 or LJA (Android 4.1.x). Why? Because you'll brick. After I did update everything (to official 4.3) through ODIN, I flashed back TWRP and even flashed an ICS ROM and right after an AOSP ROM, all working. You can flash any ROM through any custom recovery such as CWM or TWRP, just don't touch ODIN or better yet, delete any earlier-than-4.3 ODIN firmwares off your PC and you'll be fine.
[T-Mobile, Samsung Galaxy SIII] meamgood:
I got mine from CM's wiki http://wiki.cyanogenmod.org/w/Google_Apps
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
Isn't that basically what I said?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
No. You said he couldn't flash anything below 4.3 which is false. He can flash anything, just not ODIN below 4.3. I guess you failed to specify and that's crucial, especially in something like this where some users have bricked due to incomplete explanations.
[T-Mobile, Samsung Galaxy SIII] silverton:
Are you using a non-stock keyboard? I don't have the input notification using the stock one.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Latest nightly trying to open the gallery causes a reboot.

To get rid of input switcher when using a 3rd party keyboard go into app manager and disable google keyboard and aosp keyboard
[T-Mobile, Samsung Galaxy SIII] yanikd:
No reboots here on latest nightly.
[T-Mobile, Samsung Galaxy SIII] silverton:
Gallery works fine here as well.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I odind with root66 to the 4.3 firmware, installed a recovery, wiped everything, tried installing the latest CM11 nightly and this is the error I'm getting:

set_metadata_recursive: some changes failed

E: Error executing updater binary in zip '/extern

Error flashing zip '/external_sd/cm-11-1228.zip'

Updating partition details...

Failed

Any ideas?
[T-Mobile, Samsung Galaxy SIII] sswb27:
Are you on the latest recovery?
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I had to switch from TWRP to CWM. I got it going. Can you not use TWRP at all? Thanks!
[T-Mobile, Samsung Galaxy SIII] sswb27:
You would have to use the latest TWRP from goomanager for cm11 to flash.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Must have been a bad download :/ gallery would open but hang and freeze when loading my folders. Pressing home caused the reboot. I found ways around it using another app. I'm sure tomorrow's download will be fine
[T-Mobile, Samsung Galaxy SIII] yanikd:
Flash fine with CWM here.
[T-Mobile, Samsung Galaxy SIII] Lawful123:
cm recommends cwm.
[T-Mobile, Samsung Galaxy SIII] rage913:
Yeah I've frozen the aosp keyboard through titanium back up but I do use the Google voice speech for when I'm driving. I just tried SwiftKey's version and it opened up a new window pain that had me speak into my mic and It had to guess my words versus Google speech to text writing what I was saying as I was saying it. It's a small annoyance but just irritating. Lol.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I think I was trying 2.6.3.0 instead of 2.6.3.1. Thanks.
[T-Mobile, Samsung Galaxy SIII] Snipe175:
Im not sure where to post this, but hope you guys can help me out. I'm on cyanogen 10.1.3, firmware 4.2.2 and I have been trying update my phone to a more current update. I tried even upgrading for 10.2 stable and every time I do, my phone bricks (starts just restarting over and over on black screen). Of course I restore with a nan droid backup but any update I try to do bricks my phone. I'm not sure what I'm doing wrong here. Any suggestions?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Wipe data, cache, and dalvik in recovery before flashing. Then if you boot loop again, reboot to recovery and wipe data/cache once more.
[T-Mobile, Samsung Galaxy SIII] jet8300:
I've been having an issue with MightyText, and I've found that the problem looks to be fixed but there hasn't been a build of 10.2 since the patch. Is there a way I can get a patch for the following fix?

http://review.cyanogenmod.org/#/c/55481/
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I use smart keyboard pro. I don't like swiftkey. I recently gave it a try and it just wasn't as good as smart keyboard has been for me. I have google voice typing set to off under settings, and when I hit voice typing on smart keyboard its very accurate, It seems exactly the same as when I use google now to type
[T-Mobile, Samsung Galaxy SIII] mondokat:
bluetooth still broken

my bluetooth has been broken for days. i usually just leave it on to connect to my car when i turn it on. But i have to keep re-pairing to make it recognize the phone and just now on the latest nightly i turned the car off and walked into work and the phone still thinks it's connected to the car. Turning BT off and on is iffy, too. why does it seem like bluetooth and CM on this phone never want to play nicely?

:mad:
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Settings>Apps>Running>BluetoothShare

Close all services.

Close any processes still open (if any, they should auto-close when you kill the services).

Toggle BT off, then on, then off again. Make sure it is really off. Then reboot.

Turn BT on, connect to car.

You should have no further issues after that. If it crops up again, the same steps should fix it.

I will say, that in the 7 months I have had this phone, connecting to BT at least twice a day (often more, as I use a couple different BT speakers at work), I have only had to do this twice.

My theory (conjecture really) is that the connection isn't always fully closed when you exit the car, thus the service stays running, thus you can't turn BT off. Since you can't turn it off, you can't turn it back on again to have it reconnect. The toggle will flip back and forth, but nothing actually happens. If you navigate to Settings>Bluetooth while this is happening, you should see either "Turning Bluetooth On..." or "Turning Bluetooth Off..." at the top, and the button will be greyed out. After performing the steps above (sometimes even without the reboot, ymmv, always reboot for best results), both toggles (Settings menu and QuickSettings) should function normally.

Edit: probably a good idea to clear the saved BT device history from your car as well. The (possibly dozens of) duplicate pairing entries can't be helping your situation any.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Nope. Only have one pair in per device. I unpaired, killed all BT procs, erased data and cache, rebooted after doing this a few times. I repaired and 15 seconds later it randomly crapped out again. There's a bug in here somewhere, because 10.2 worked fine for ages with no twiddling.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Well I'm stumped. Grab a logcat and maybe one of the devs will be nice and take a look at it for you.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I'm pretty sure this has nothing to do with the nightlies at all, but does xda refresh the page on the topic list when pinching to zoom? It doesn't do it in threads, but on the thread listing page, and the page to choose what sub forum when I pinch to zoom the page reloads. Its super super annoying, and it has been doing this for several weeks now. Why?

I'm using chrome
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
That happens on my phone and tablet no matter what. I've resorted to using Tapatalk.
[T-Mobile, Samsung Galaxy SIII] mondokat:
When you press "take bug report" under developer options, where does it store the report?
[T-Mobile, Samsung Galaxy SIII] mondokat:
bugreport attached

bugreport attached. hopefully somebody can help out. I'd post it to the CM jira site, but there's no M1 to post against yet...
[T-Mobile, Samsung Galaxy SIII] pappuhathi:
Is it just me or was the Android home removed in the Jan 2nd nightly?

EDIT: Side loaded googlehome.apk and got the google launcher again.
[T-Mobile, Samsung Galaxy SIII] silverton:
I still have the Launcher app, but I didn't format the /system partition either when I flashed the nightly.
[T-Mobile, Samsung Galaxy SIII] skewty:
Anyone else having Dialer FC issues? I can't dial out most of the time without it crashing.

I clean flashed yesterday to Jan 1st build.
[T-Mobile, Samsung Galaxy SIII] PrimeNemesis:
I have have the FC issue. Whatever it is carried over to the 2 Jan Nightly as well. Wiping the caches again did nothing for it.

I hope it gets fixed in tonight's. I make a lot of call from the car so it becomes a pain. And voice texting doesn't always get the message I need across.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I've been making calls all day with no force closes. I usually just select my contacts though. I tested making a call using the dialer and it connected, end call worked and didn't have any problems. I'm on the 0102 nightly.

Tomorrow's nightly has a decent amount of commits added. Longest changelog I've seen in awhile
[T-Mobile, Samsung Galaxy SIII] domreplv:
Phone Dialer FC

Having the same issues with Phone Dialer.

Tried the Following without resolving the issue.

Full Wipe

Clean Flash of CM11-Built: 2014-01-03 AT 07:22 AM with out Gapps...

Currently Running the Following

Baseband: UEMJC

From Build: UVUEMJC

OS: JB 4.3

Release Date: Nov, 2013

Re-flashed CM11 - Built: 2013-12-31 AT 07:20 AM
[T-Mobile, Samsung Galaxy SIII] Lawful123:
Having allot of issues with latest nightly. Dialer force closes. "OK Google" no longer works. Did clean install same issues. Any insight?
[T-Mobile, Samsung Galaxy SIII] silverton:
Also dialer issues on the latest nightly. It would also disconnect me from the mobile network. flashed to previous nightly and no issues there, phone calls work perfect.
[T-Mobile, Samsung Galaxy SIII] skewty:
Just dirty flashed m2 and it still has dialer issues.
[T-Mobile, Samsung Galaxy SIII] bentheexo:
So about this Dialer and Google Now issue that makes you reboot the phone to use either...It is a problem related to a piece of software not releasing the microphone after use. Sometimes its Google Now when I use OK Google to activate it, and others its the Phone application after I hang up the call.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I'm on the latest nightly and I'm still not having dialer issues. Its been working perfect for me. I am having voice recognition problems. Ok google is not working and when I would go to voice my text messages it was not hearing what o was saying. I think it might have something to do with the mic not getting activated? But it works during phone calls
[T-Mobile, Samsung Galaxy SIII] snipinu:
I am also having the dialer fc issues and have to reboot, I have the utmost confidence in the developers though
[T-Mobile, Samsung Galaxy SIII] Pantera82:
Anyone's speakerphone volume extremely low on the last month or so of nightlies? Will this be fixed at some point? Its only low on phone calls that are on speaker. The speaker itself works fine otherwise
[T-Mobile, Samsung Galaxy SIII] Lawful123:
OK Google now working. Something still crashes when I use the dialer. Things are getting better.
[T-Mobile, Samsung Galaxy SIII] rayman2k1:
Wi-fi all effed up?

I've been having this issue since, I think, the first 4.4 nightly:

Wifi settings are messed up. I can't connect to any Wifi (all are saying out of range). I can't delete the saved networks (says that it failed) and I basically can do sweet **** all with Wifi. I got the issue resolved, temporarily, by wiping everything and doing a clean flash. That lasted all of two days (if that). I haven't really done a lot of experiments, but I think it may somehow be correlated with/caused by enabling Google's location service.

It seems like some sort of permissions issue, but I'm not sure. I've tried:

- dirty flashing nightly

- flashing new modem (was on VLDMF2, now on VLEMK5--I'm with WIND MOBILE)

- rm -rf /data/misc/wifi

The only thing that seems to temporarily resolve the issue is doing a clean flash.

There is one other thing: the wifi settings seem to be re-written from Google's backup service (before deleting them with "rm -rf /data/misc/wifi", I was seeing saved SSIDs that I haven't connected to in years--I don't see how they might have survived several clean flashes (I also manually wipe my /data /system and /sdcard periodically). Is it possible that google restores wifi settings from backed up data and marks the file as r/o?

I can try providing a logcat if anyone is interested in helping me out.
[T-Mobile, Samsung Galaxy SIII] silverton:
Interesting, I've never had an issue with WiFi. The AP names and passwords are backed up with Google but I can't imagine it would be written r/o to the device when restored.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
Google does save wifi passwords for your account. They say so when your signing into your google account after clean flashes
[T-Mobile, Samsung Galaxy SIII] rayman2k1:
Got it.

I don't think it's related to that though. Looking thru the logcat, I saw:

After I did a

touch /data/misc/wifi/ipconfig.txt

I don't see that error any more, but I do have a new snip from a log that I've attached. Again, if anyone's interested in helping me out, I can be available to provide more info.

Thanks
[T-Mobile, Samsung Galaxy SIII] silverton:
Dialer issues on 01/04 so I experimented and formatted system partition. First try ended up with a FC, following calls did not.
[T-Mobile, Samsung Galaxy SIII] silverton:
I lied. Only the first call seems to work, then FC.
[T-Mobile, Samsung Galaxy SIII] ergibson83:
I can confirm same issue as well. This started about 3 nightlies ago though.
[T-Mobile, Samsung Galaxy SIII] Jiggs82:
These commits should fix dialer/phone fc on the next nightly

http://review.cyanogenmod.org/#/c/56867/

http://review.cyanogenmod.org/#/c/56626/
[T-Mobile, Samsung Galaxy SIII] silverton:
I was able to make two consecutive calls today while testing those commits. Data connection did drop though. Came back on Edge and stuck there for a few minutes before getting 3G/HSPA back.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Been on m2 a while, calls work great. Haven't tried Bluetooth yet though...
[T-Mobile, Samsung Galaxy SIII] maelstromm:
I'd be curious to know how your testing goes. Bluetooth has been hit or miss for me. It works on generic adapters but keeps disconnecting on my car. I stayed away from the M2 and later builds due to dialer issues everyone reported. Trying PA now, not much improvement with Bluetooth on car :(
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
The latest nightly had 2 new commits to fix the dialer issue. I never had a problem with it on previous builds though, and its working great on latest too
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
I wonder what's in store for us.
[T-Mobile, Samsung Galaxy SIII] silverton:
Knowing my luck the S3 will probably start rocking about the time I pay mine off and get an N5... haha
[T-Mobile, Samsung Galaxy SIII] tidewblch:
Need some help

I am on a t mobile sgh t999 running 10.1.0 from build date 6/24/13 on baseband uvdmd5. I want to upgrade to at least the 10.2 stable. I don't want to screw this up. Can someone please tell me what I need to do. I have been off here for a while and don't want to screw up my phone. I also would like a link to the site where you can download the modems for our phone. I used to have it but cannot locate it anymore.

Any help would be appreciated.

Thanks,

TIDE
[T-Mobile, Samsung Galaxy SIII] silverton:
MD5 is a good enough modem. No point in changing it unless you're having issues with reception. As far as changing android versions I would back up both internal and external SD cards, format both of them inside a recovery along with system/data/cache and flash the ROM file you want along with the GApps listed on the CM wiki page for that particular CM version.
[T-Mobile, Samsung Galaxy SIII] tidewblch:
Just so I understand. If I back up both internal and external and then format them I have to reinstall all my apps and redo all my settings for such apps?
[T-Mobile, Samsung Galaxy SIII] silverton:
Yes. But it's the recommended way when switching Android versions.
[T-Mobile, Samsung Galaxy SIII] tidewblch:
Hopefully final question, what is the best way to back up internal and external. Connect them to my laptop and copy the entire folder for each, or is there a better way. I'm on a Mac in case that matters.

Also how is 10.2 stable? Was it a big improvement over 10.1 before I bother doing this or should I wait for 11?

Thank you so much for your time and help.
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Wait. Why are you wiping storage? You only need to wipe internal if coming from 4.1 or lower to 4.2 or higher, because of the multi user /0/ folder issue. You never need to wipe the external unless you have a problem with the card. If really concerned, just remove the external card rather than waste time backing up, formatting, and restoring.

Also note that if you wipe internal, you lose not only apps and settings but also pictures, music, pretty much anything you have saved.

As far as cm version goes, I'm on cm11 now and its rock solid. There were some reported issues with builds from the last few days, I am on the 12/23 build and have no problems.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I made the mistake of not wiping internal memory when I upgraded to 4.2. I got my s3 black friday 2012, rooted it and kept it on debloated touchwiz for 2 months. When a stable 4.2 rom wad released I installed it and never went back. But now I am still stuck with a /0 folder. I haven't done anything to fix it cause its really not that much of a big deal, just a few extra clicks to get around in ES explorer
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
Wow have been using PAC-ROM for ever and assumed CM11 never came out because PAC didn't have it, just flashed today version of CM11 everything is PERFECT and fast. Only complaint is the FFC lags (IE: snapchat) so on. But def daily usable.
[T-Mobile, Samsung Galaxy SIII] eugenile:
anyone able to use instagram and post a video?

For the longest time on several nightlies, you can record the vid, and get up to chosing the screen, but on the next part always force close.
[T-Mobile, Samsung Galaxy SIII] tidewblch:
So if I make a backup of my OS and just install 11 right over it without wiping, I will end up with a 0 file, which I don't think I would really care about. But if 11 is glitchy can I downgrade back to my backup without issue or will I have a problem?
[T-Mobile, Samsung Galaxy SIII] silverton:
New android has multi user. So main users files are in 0/, secondary in 1/, etc etc
[T-Mobile, Samsung Galaxy SIII] xheavymetaldadx:
Would anyone happen to know how to get the cm guys to add t999luvubmk4 to the updater script, cus honestly doing it manually everyday is a bit of a pain in the ass ;)
[T-Mobile, Samsung Galaxy SIII] yanikd:
It's in today's nightly.
[T-Mobile, Samsung Galaxy SIII] xheavymetaldadx:
Must not have noticed it when I did it manually, appreciate it
[T-Mobile, Samsung Galaxy SIII] maelstromm:
Anyone have any improvements on bluetooth with newer nighlies? I'm on the 1/4 build and still facing issues with bluetooth randomly disconnecting or getting bluetooth FC.
[T-Mobile, Samsung Galaxy SIII] G1-evolve:
I wiped and tried CM11 for the first time on 1/7 I am on 1/8 now and use my wireless bluetooth head phones with no problem.
[T-Mobile, Samsung Galaxy SIII] mondokat:
The last nightly I was on bluetooth was crashing in my car. I am now on the M2 and haven't tried it yet, but there have been no commits in the changelog related to bluetooth, so I'm not hopeful.

It seems like the issue has to do with transferring my phonebook or call history to the car, the initial connection seems ok.
[T-Mobile, Samsung Galaxy SIII] WoodmanMN:
Yes.
[T-Mobile, Samsung Galaxy SIII] Nitefire77:
I wouldn't reccomend flashing cm11 over your current rom. Chances are it will force close or crash a lot. You always want to do a clean flash when installing a new android version or new rom. The /0 comes from the sdcard partition. The internal SD. Formatting that before upping to 4.2+ is reccomended. Make sure you move all the files you wanna keep to your external sd
[T-Mobile, Samsung Galaxy SIII] Adreaver:
I don't understand the sudden confusion. It's essentially the same instructions as any of the AOSP 4.2+ we have been flashing for months.

reboot recovery

MAKE A NANDROID (to the external sdcard if you are on 4.1 or earlier)

IF ON 4.1 OR EARLIER ONLY; wipe internal storage (make a backup first on PC or external SD, you will lose pics, music, etc)

wipe data

wipe cache

wipe dalvik

flash rom

flash 4.4 gapps

reboot system

if you bootloop, reboot recovery, wipe data and cache again, reboot system
[T-Mobile, Samsung Galaxy SIII] eugenile:
Running 1/8 nightly. I never had issues with BT syncing with my av receiver or car stereo since Nov iirc.

Still instagram fc wen trying to submit a video