yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] stonew5082:
I reverted to the 6/15 doesn't have the music bug
[T-Mobile, Samsung Galaxy SIII] traderx2009:
Got the mms bug too. Dang it. Wasn't there on rc5, tried the latest nightly and now “service not activated on network" error message when trying to send mms. Flashed back to rc5 and problem still persists.
[T-Mobile, Samsung Galaxy SIII] ckisgen:
guys, I posted the cause and fix for this MMS sending issue weeks ago in this thread.

the reason I haven't reposted it is because literally like 4 posts after my explanation and fix, people were already asking how to fix it.

no one searches before they post.

either way, it's gained enough momentum now that I feel like showing mercy and throwing everyone a bone.

this problem wasn't very hard to track down. I started getting the 'service not activated on this network' error when trying to send certain MMS's back in mid May.

here's the commit that screwed it up :

https://github.com/CyanogenMod/andr...mmit/88dc007b3104c07668de36a5f375a637ca9c1eb6

it increased the allowable size of pictures being sent over mms and it seems to have worked fine for Verizon and Sprint. T-Mobile, on the other hand - no bueno.

SOLUTION - grab the MMS.apk out of the nightly from 5-17 or earlier and throw it in your /system/app folder.

as a favor, I uploaded the 5-17 MMS.apk that I've been using to remedy this bug ever since last month to my dev-host.

super-noob proof steps :

1. download the MMS.apk from here:

http://d-h.st/SJV

2. using your favorite file explorer, mount your /system - r/w (read/write)

3. in /system/app folder - rename existing MMS.apk to MMS.apk.bak

4. copy/paste the MMS.apk you just downloaded from my dev-host to this folder (/system/app)

5. change permissions to RW-R-R (6-4-4 for you linux peeps)

6. reboot

7. hit my thanks button :cool:

8. win :thumbup:
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Thanks again for this bro... Hopefully people will stop asking now..
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I'm having an issue with the stock Email app not being able to sign into my yahoo mail consistently. Half the time it works and half the time it doesn't. I've tried to manually set it up with POP and that didn't work either. Most often I get something that resembles "could not sign in with email@address." Sometimes it tells me its my username/password are invalid. I'm know I'm not incorrectly typing it that many times. I use this email account frequently. I've removed and re-added the account several times to with nothing sticking, and cleared out the cache.

Anyone have any ideas or suggestions short of a complete data wipe for that app? Maybe a superior email app that also has Exchange?
[T-Mobile, Samsung Galaxy SIII] khoikn:
Anyone getting some noticeable lag when opening apps?

Tried 6/22, RC4, RC5 and it just keeps and appearing.

It's only with installed apps, YouTube and Facebook are the worst.

Things like Reddit News aren't as noticeable when opening.
[T-Mobile, Samsung Galaxy SIII] futuremonkey:
Anyone else notice that the cLock lock screen widget no longer shows the next alarm?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Mine is showing. 6/23.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
No MMS issues here on 6/23
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Looks like we're getting 10.1 stable released tonight. Looking forward to see how they've done with it, but I'm not holding my breath in anticipation of a truly stable experience given all the bugs that are unresolved at this stage.

http://www.cyanogenmod.org/blog/cyanogenmod-10-1-0-release
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
This saddens me. It's not even close to ready. At least not for our device.
[T-Mobile, Samsung Galaxy SIII] DeerSteak:
Me either, I just tested it and sent it to my wife. We both have d2tmo, mine running 6/23 and her running RC5. Once both get the stable release I'll try again. BTW I doubt it matters if MMS.apk fixes it for some people, but we're both using ktoonsez's KT747 kernel based on 3.4.x.

Maybe the issue is with people on other networks? Like the images are too big for certain carriers? Incidentally, iPhone max MMS sizes are up over 1MB as well when you get the T-Mobile carrier update so it should work on an Android device.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
So the latest nightly worked with the T999LUVAMB7 but the stable wont work The LTE Version of the T999
[T-Mobile, Samsung Galaxy SIII] lowsnamebrand:
Is the MMS bug fixed in the stable or should I use the fix a couple pages back?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Use the fix if you have any issues.
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
Is this a question or a statement? because I was about to flash the new stable, but the assert is not there for the T999L, so I'm going to wait.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
I guess it was both the last nightly 623 works perfectly tho
[T-Mobile, Samsung Galaxy SIII] lowsnamebrand:
Just updated to cm10.1 stable MMS is working without the fix
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I'm running on 0624 and working fine, I think that the assert was taken out because the newness of this version, but it might still work if you added it in, just not "stable".
[T-Mobile, Samsung Galaxy SIII] DoUknoGREG:
Just a few questions before i flash this.

1. Is there built in customization ie. change battery icon, battery color, etc.

2. I doubt it but, is there a way to get the halo notification on cyanogenmod?

3. Does the camera have photo sphere?

4.How awesome is it in terms on cyanogenmod exclusive features?

5. Im on paranoid android. Is it worth flashing cyanogenmod?

This will be the first time i flash CM10 on my GS3, so some help will greatly be appreciated :)
[T-Mobile, Samsung Galaxy SIII] rojovilla:
Please search as all five of your questions have been discussed at point or another. Just flash it brochacho :D
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Anyone test for the Google music volume bug?
[T-Mobile, Samsung Galaxy SIII] DoUknoGREG:
awwww searching is soo much work D: but i'll take your word for it lol :good:
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Ok, so I got 10.1.0 installed with stock kernel. So far it seems snappy, but still has the same bugs as nightlies and rc 4,5 (at least the ones that affect my device, I don't use mms, so I can't comment on that). Namely, no Google+ auto backup photos setting. Dsp is still messed up and Bluetooth sound quality is crap (low end distortion).
[T-Mobile, Samsung Galaxy SIII] rsilv377:
It works but for some reason i check use dark theme but doesn't work... Stays on the light theme
[T-Mobile, Samsung Galaxy SIII] Spiyder:
On 10.1.0 stable stock kernel, no mods. I am getting reboots randomly while trying to open videos in the gallery. No complaint just an fyi for the users ;)

Edit: A fix permissions in twrp seems to have fixed it.
[T-Mobile, Samsung Galaxy SIII] s_special:
I have a question about why I can't seem to update to any new version of CM. My last nightly was back in March. When try to update through teamwin recovery it says fail. When I try to do it through the cm updater it just reboots without doing the update. I'm left in the past here.

Does anyone have any ideas?
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
SEARCH

then update your firmware to the latest. SEARCH to find the zip.
[T-Mobile, Samsung Galaxy SIII] s_special:
What firmware? CM firmware?
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
This one
[T-Mobile, Samsung Galaxy SIII] s_special:
Sorry, I had no idea. Thanks for the link!
[T-Mobile, Samsung Galaxy SIII] munkyvirus:
Yupyup, try the MD5 and the LJC and figure out which works better for you.
[T-Mobile, Samsung Galaxy SIII] s_special:
I'm up and running on the stable release finally! Thank you again for helping out the uninformed lol
[T-Mobile, Samsung Galaxy SIII] rage913:
Just want to share the ridiculousness that was my battery lastnight. I doubt I'm going to be able to get the same battery today or any day for that matter. But hey figured I would share.

Cm10.1 6-22 plus ktoonz 6-8, with a team k mod added Ontop... Yeah. My phone was beastly yesterday!!!
[T-Mobile, Samsung Galaxy SIII] Liquid602:
After changing everything and rebooting, should I mount my /system from r/w back to r/o? Or just let it be
[T-Mobile, Samsung Galaxy SIII] timosuomi:
It should revert back to r/o on its own. If it doesn't, you can change it back to r/o manually.

Sent while playing on my phone.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Stable for 24 hours

I've been on 10.1.0 for 24 hours so far and looking good. Battery stats are from when i got up this morning. Bluetooth works, stuff is just working.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Sorry to be a downer, but I've been on this since last night too, but it's been less than stellar for me. I'm on a cross country road trip and maps/navigation freezes every so often and causes the phone to lag beyond a recoverable state - sans reboot (if you are able to activate the power button menu that is). Had to do two 10 second power holds today (equivalent of a battery pull in case you're wondering). Bluetooth has been better than rc5 in staying connected and no Bluetooth service lockups. Dsp still is wonky though. Can't judge the battery cause I'm plugged in all day.
[T-Mobile, Samsung Galaxy SIII] trofmoc:
latest is nice-

still has bt issues. mono bt is great but only on phone not audio, also stereo bt disconnects on second call as in past but nice on audio. hmm:fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] rage913:
Noob question for the night!!!! First time I'm physically editing my permissions within a .apk I've changed my messenger to (. Apk. Bak), no parentheses) and I uploaded the working apk back on. So I've gone into my file Explorer to change permissions and I've already got rw-r-r selected for me. Couple of questions if anybody is willing to share/help

1 . what is the difference between group, owner, others

2. How do I know which read, right, execute I need to select for? Since there's three possible selections for them all

3. What exactly I actually doing :o

4. You guys are badass!

Just trying to learn and I feel like everyday is something new with my device let alone android lol thanks!

Edit: scratch the second question off... Common sense just dawned on me. :what: go by colum rw-r-r. Man I feel derp:p
[T-Mobile, Samsung Galaxy SIII] DrewCSchultz:
"What exactly I actually doing?"

Not sure, your terminology is kind of strange. What I THINK your're trying to do is replace your Mms apk with one from an older version to get multimedia messages to work. In this case, just follow the steps.

1) obtain an older copy of MMS.apk. I got one from the post a couple pages back.

Edit: here's the link: http://d-h.st/SJV (THANKS CKISGEN!!!)

2) Open the stock cyanogen file manager, then go to settings, then general settings. Change the option from "safe mode" to "root access mode".

3) go to the root of your device. That's all the way up, keep pressing "parent folder" until you can't anymore. Folders near or at the very top should be "acct" and "cache".

4) scroll down and click on "system". Then click "app". In that folder is "MMS.apk". Check the box, hit the options button (its two rows of dots), and rename it to "mms.apk.bak". All you are doing here is preserving your old messenger app in case you need to revert back. That's what .bak stands for (backup).

5) Now go and find the MMS.apk you downloaded or pulled from a different ROM. You'll click on storage, then emulated, then 0 to get back to where you started.

6) check the box next to the MMS.apk.

7) go all the way back to the root of your device where you were before. When you're in the "app" folder, hit the options button again and click "paste selection here". You should now have mms.apk and mms.apk.bak next to each other in the folder.

8) close the app, then reboot. Voila.

I hope this helps!
[T-Mobile, Samsung Galaxy SIII] bosna110:
Please excuse me for the foul language, this ****ing calling and MMS issue I'm having for the whole 2 weeks is irritating the hell out of me. I don't know what to do anymore. I can't talk on the phone cause the other person can't hear me and I can't send any MMS even when I have wifi on or off. I'm to the point where I don't want to unroot this device and leave it unrooted. Again I apologize for the harsh foul language. Someone please help me. Thank you
[T-Mobile, Samsung Galaxy SIII] Spiyder:
I don't want to the guy that says this but I would suggest going back to stock TW. If it frustrating that much roll back to stock. Root the stock os and call it good. :)
[T-Mobile, Samsung Galaxy SIII] rage913:
Lol that I gathered of just getting the apps to my system/app directory. I suppose your right. I didn't word what I wanted to get across correctly. I was able to replace my apks fine. I just wanted to know what rw-r-r was/and what each specific group "means" in terms of permissions. And in terms of "what I'm doing" I meant in "what am I doing for the permissions that requires a re-write of them"

Thanks though homie! Appreciates it:thumbup:

---------- Post added at 01:57 AM ---------- Previous post was at 01:50 AM ----------

Alright. Let's trouble shoot:

Have you upgraded to the latest firmware?

Have you been doing dirty flashing ?

have you been running a custom kernel?

have you tried the MMS.apk fix posted earlier?

The best thing I can tell you to do is backup your ROM to your external. Download the newest nightl/Rc5 and move that to your external as well as having the newest gappsover. Boot into recovery, wipe cache/delvik cache, wipe factory data reset. Go to mounts and storage and wipe ONLY internal SD card. Reflash gapps plus Rc5 /nightly and see how that works out.
[T-Mobile, Samsung Galaxy SIII] bosna110:
I admire what your suggesting me to do but I like having the latest versions of everything. I can't stand having something old and still functional if u know what I'm saying. If I knew how to cook up a ROM I'd love to make it one of the best but my mental capacity would be like of a 1 year old.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
You can accomplish anything you set your mind to my friend. I am living proof. I'm one who's always been computer stupid but after months of reading/researching, here I am actually helping out tons of users on the forums. I'm actually so motivated to getting into ROM development that I'm actually considering doing it. but of course PATIENCE is key.
[T-Mobile, Samsung Galaxy SIII] bosna110:
What is the latest firmware?

Dirty flashing? Yes cause cm updater downloads the nightlies and flashes the new file for me

Custom kernel, I have sometimes but it is always getting outdated and hard to keep up

As for the MMS.apk no I have not.

All the backing up and moving to external and everything else is just tedious work although it I must do it I will.
[T-Mobile, Samsung Galaxy SIII] rage913:
When I say latest firmware I mean your bootloader. A while back touchwiz introduced umd5 onto the scene and it caused a **** ton of panic. If your still able to update to the newest nightlys then you're good.

You're right, cm updater does wipe your caches for you, but if you have an underlying issue sometimes that doesn't get wiped. For the longest time I was getting glitches with my notification tray to the point that I was sick of it. Moved everything to my external did a full wipe put everything back.

CM updater doesn't wipe/format your internal for obvious reasons so that's why almost every Dev say do a full system wipe. Even down to your internal because you still have data saved in random ass spots.

It may sound tedious but do the pro's out way the con's? What's probably ten minutes versus the frustration of not being able to call someone. Let alone text them. So I guess that's what you're going to have to judge it on. Do you want a working phone or a fancy paper weight?

You should always have at least one back up of your phone. That's like suicide to not have one. So many times I'll flash something and completley forget that I don't have a back up. I have my own folder on my ext SD that has everything. Cm10.1 roms, backups, modems, kernels. Your call mang.
[T-Mobile, Samsung Galaxy SIII] mikejet:
any word on the CM messenger?
[T-Mobile, Samsung Galaxy SIII] mondokat:
I'm stock CM kernel, stock everything. You can see from my screenshot i've been playing ingress, which uses the google maps api and gps functions, and had no issues. What non-stock stuff are you running, maybe it's not the rom?

My bluetooth has been connecting to my suv just fine, calling has been fine. dunno about the dsp/music stuff so much, i use an ipod for music, or spotify on my desktop.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Am I really the only one having issues with incoming and sometimes outgoing calls not working?

Think 4/27 was the last solid build.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Everything working for me on stable
[T-Mobile, Samsung Galaxy SIII] mondokat:
Yes, you are exactly and precisely the only one, ever.

I'm just kidding. :p

It seems like the samsung firmware (not the CM ROM) is a little finicky in the newer versions. You can't just flash the radio or bootloader, or the other individual pieces without flashing all the bits and pieces from the same release. Have you tried flashing the official stock firmware of the version you want (I am running MD5 with no issues) and then re-install CM. i did this and restored user data via twrp so it was like nothing changed, and everything is working great.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I am running full LJC firmware.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
I started with stock everything, but it was a bit unsatisfactory. I added kt747 and that didn't help it out either. Then the mystery battery drain hit at 32 percent battery life. Sucked it down at a record rate of 36.6%/hr. The offending app or wake lock doesn't show up in bbs. On top of that, I couldn't even connect to Windows via usb as a media or storage device . Deal breaker there.

I went back to rc3 today, which was released around May 30. Let us know how 4/27 works out. I'd like to try that if rc3 isn't stable for me.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
What firmware are you on?

Build 4/27 with ktoons 4/28 is solid. I managed another S3 with that setup. It was in use for nearly two months. If you don't use bluetooth it's solid.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Uvdmd5

I do use Bluetooth. So far rc3 is working out, but we'll see.

Looks like ktoons just dropped an update. I wonder if that might fix things. I'm a bit hesitant to try.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Flash the LJC firmware. Link is in my signature. People have been reporting issues with MD5 on CM. Some of them annoying, some of them serious.
[T-Mobile, Samsung Galaxy SIII] rage913:
Does anyone remember being able to have both a password/pin PLUS the shortcut icons on the lock screen? I think it was way back in Christmas that I was able to use my shortcut slider to access am app but still have to put in my pin to actually get in. Does anyone know if this is still possible? I've screwed around with my lock screen options but I still don't got anything. If not does anyone know of an alternative?
[T-Mobile, Samsung Galaxy SIII] skewty:
I am running 10.1 stable and experienced some issues on a phone call with headset plugged in. Basically, DTMF tones weren't being sent properly when (mute was enabled). This works on TW ROMs. I believe the tones may be sent but at low volume when mute is enabled.
[T-Mobile, Samsung Galaxy SIII] twoxa:
why I thought HALO is in this rom...
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
No go for me with the MMS issue. Pushing the uploaded MMS.apk and changing the proxy in the APN settings did not help. Pictures do not send.

Any other suggestions? 10.1.0 STOCK kernel, MD5 firmware. I'm frustrated.
[T-Mobile, Samsung Galaxy SIII] lowsnamebrand:
Are you on the stable build if so I did a complete clean flash and didn't have to push the MMS fix if you didn't do a clean install try that and let us know if it works
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I did a clean install. I came off RC5. It seems the issue doesn't start happening until I restore something in TWRP. If I backup RC5 and restore 10.1 for example and restore back RC5 again the issue appears. If I leave it alone from the initial clean install MMS seems to work. I previously did not experience the MMS issue on RC5 initially clean installing when it was released. Not sure if that's worth anything and sounds odd but that's my experience with it.

I just did another clean install of RC5 but have not been able to test it. T-Mobile provides me a horrible signal where I live so the next chance I get I will try to send a few pictures taken with the camera. Screenshots go through fine.

Maybe it will get fixed soon. If RC5 works out I'm jumping off the nightly train for awhile. I'm flashed out and frustrated.
[T-Mobile, Samsung Galaxy SIII] duhitsrandy:
im getting a status 7 error when i try install either of the past 2 newest versions of cm on my phone.. older versions from may and before flash fine though.. any ideas?
[T-Mobile, Samsung Galaxy SIII] GenericAsianGuy:
I'm on the latest nightly (6/26), enabled Privacy Guard for most of the applications on my phone (sans keyboard apps + instant messaging apps).

One thing I noticed was that my phone would freeze+reboot for certain apps (e.g. Facebook, Google Play, PowerAmp). Once my phone rebooted, the app has Privacy Guard for it, so all is well :)
[T-Mobile, Samsung Galaxy SIII] jgc731:
I have been trying to search but could not find anything. Does anyone else experience the camera to be distorted when switching between the front facing camera and rear facing camera? The image looks stretched. I have to exit the camera app then reopen it to get the image back to normal.
[T-Mobile, Samsung Galaxy SIII] DoUknoGREG:
What would you guys say the best kernel to run on CM 10.1 is?
[T-Mobile, Samsung Galaxy SIII] jankies:
Try installing latest recovery?.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Update your firmware. See aerowinder's signature for the links.
[T-Mobile, Samsung Galaxy SIII] yanikd:
Sometimes the screen briefly flashes then the phone become unresponsive for like 30 second to a minute, then it gets back to normal. In these moments I usually get the android message saying apps not responding, wait/close/kill. I get it on stock kernel as well as KT747. This has been going on for a few weeks now. If I disable HW overlays I don't experience it tho. But the device is not as smooth with HW overlays disabled. Strangely enough I don't experience it on Vanilla Rootbox. Any ideas?
[T-Mobile, Samsung Galaxy SIII] G1_enthusiast:
whole thread dint really mention A2DP
[T-Mobile, Samsung Galaxy SIII] TheSeanTeam:
Maybe you should ask about features/bugs of a CM9 ROM in the CM9 thread.
[T-Mobile, Samsung Galaxy SIII] Six6Sicks:
Maybe you shouldn't be a complete douchebag and try to help.
[T-Mobile, Samsung Galaxy SIII] andybess22:
I searched the thread and I cant find anything so I will ask. Is the built in wireless tether not working on CM10 yet or is it just me? And if it doesn't work is there any app that works? Thanks
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
Yep. That's the only real bug I've found. Obviously A2DP doesn't work but I don't use Bluetooth on my phone anyway so that doesn't matter to me.

I should mention that after writing my initial post I got on the train to head home from work and got a black screen while listening to Spotify. I wasn't able to get out of without pulling the battery. But this only happened once and it rebooted right up and worked just fine after that.

---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------

Great find. After reading your post I downloaded the lite version and started messing with it. This is a great camera app replacement that I will be sticking with. Thanks!
[T-Mobile, Samsung Galaxy SIII] ikhtiaralam:
I was just carrying conversation. No need to direct me anywhere. I know where everything is. Just on this OP, it says A2DP is broken. On the latter, it just says a few things. Just making sure A2DP is Bluetooth.