yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The MMS fix provided here is simply the mms.apk from M3 release of CM10.1. The difference between both is how it resizes the picture when sending an MMS. The dimensions and filesize were bumped up after M3 release and it's proving incomptible with some users on AT&T & other carriers.

The manual workaround is to send only small pictures such as pictures not taken from the camera which usually end up being pretty big or to resize them using an utility. My fix skips all that and just replaces your SMS/MMS app with an older version that doesn't have the change, so it's all done smoothly for you. No need to resize manually.

Check my post here:

http://xdaforums.com/showthread.php?p=43046457#post43046457

Rant part:

I'm in no way an Android dev, and I find bug filling for CM on their JIRA bug tracker a pain in the ass. I lack the time, patience and will to go further for something that doesn't affect me or that's I'm not in charge of.

Rather than fixing things it seems a lot of the people involved want to make you jump through hoops until you're tired. Look around and you'll see flexfulton has exposed a somewhat critical 4G/3G switching flaw which took so much effort on his part to get someone to look at...

I'm not self entitled, just don't feel like dealing with all this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
That explanation is plenty for me! Thank you very much good sir!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
the mightytext problem i have is that some longer texts dont go through anymore. and they are no where near the 500 character max.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
GFE actually searches for binaries 'n stuff. Merely messing with system settings isn't nearly enough.

GFE's root checking is a server side setting that isn't always enabled.

Edit: Not really a CM related discussion at this point though. Should probably take this to the GFE thread I linked earlier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
This seems to happen to me all the time as well and it's annoying. It's a bit retarded, but turn your screen on, send text from mightytext and it should go through. Then turn screen off.

Make sure you do that every time.

I'll get tired enough to find another fix eventually. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
Well that sucks lol but thank you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I've switched temporarily to DeskSMS. There's a free 14 day trial and I don't seem to have to switch on/off. Don't like the UI as much though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
hmm ill check it out though. thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I had the same problem too... I contacted Mightytext support...and they told me that they do not want to support custom rom... so no help for me on CyanogenMod.

I've done the switch to DeskSMS... and I'm happy! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
i tried the black gapps package and i dont like how it looks. to go back to the normal gapps package i have to wipe everything, reinstall the rom AND the gapps right? not just clear cache davlik , and then flash the other gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
I've been using MightyText and it seems that the issue is related to Wifi going to powersave mode or something like that. Once I turn off wifi and just stick to mobile data, everything works fine.

How is DeskSMS? Is it worth switching? Does it support MMS?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
Oh wow. Thanks I always have mine on WiFi I'll try that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I don't think the problem I have is related to wifi going to powersave mode... it just can't send long SMS (more than 160 characters).

No matter if I'm on mobile or wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Ah, I was talking about it randomly not sending messages for me until I unlock my phone. Short or long messages.

---------- Post added at 09:30 PM ---------- Previous post was at 08:57 PM ----------

Looks like I found the problem:

I/texty (28495): C2DMReceiver::onMessage() called....

I/texty (28495): action=send_sms

I/texty (28495): action_data=Here's a super long text message that I'm sending out as a test to see if long messages from mightytext are working! gu

ess this is going onto a new line because its long

I/texty (28495): action=send_sms, action_data=Here's a super long text message that I'm sending out as a test to see if long messages from mightytex

t are working! guess this is going onto a new line because its long

I/texty (28495): ts_last_c2dm set to Wed Jul 24 21:29:31 EDT 2013

E/texty (28495): action_data (decoded )=Here's a super long text message that I'm sending out as a test to see if long messages from mightytext are

working! guess this is going onto a new line because its long

E/texty (28495): onHandleIntent= java.lang.NullPointerException

E/texty (28495): java.lang.NullPointerException

E/texty (28495): at android.os.Parcel.readException(Parcel.java:1431)

E/texty (28495): at android.os.Parcel.readException(Parcel.java:1379)

E/texty (28495): at com.android.internal.telephony.ISms$Stub$Proxy.sendMultipartText(ISms.java:508)

E/texty (28495): at android.telephony.SmsManager.sendMultipartTextMessage(SmsManager.java:157)

E/texty (28495): at com.texty.sms.common.n.a(Unknown Source)

E/texty (28495): at com.texty.sms.C2DMReceiver.a(Unknown Source)

E/texty (28495): at com.texty.sms.C2DMReceiver.a(Unknown Source)

E/texty (28495): at com.google.android.c2dm.a.onHandleIntent(Unknown Source)

E/texty (28495): at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)

E/texty (28495): at android.os.Handler.dispatchMessage(Handler.java:99)

E/texty (28495): at android.os.Looper.loop(Looper.java:137)

E/texty (28495): at android.os.HandlerThread.run(HandlerThread.java:60)

So this might be a Cyanogenmod problem?

UPDATE: The CM team knows about the issue. Hopefully will be in a nightly soon! Don't have an ETA.

UPDATE 2: http://review.cyanogenmod.org/#/c/46009/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
160 may be a carrier limitation. If you search Google you will finds lots of talk on this in the past. Sprint sounded like one carrier with this limit.

That being said, I just sent myself a long message to see if it would split into 2 or what and it send out fine and came back as 1 big long message. I am on Rogers. So it might be your carriers.

additionally, text messages have nothing to do with wifi. They will never go out on a wifi connection so it won't matter what your wifi is doing here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
no it's not a carrier limitation. Long messages worked fine... and it suddenly stopped. It's probably an incompatibility problem with one of the latest nightly of CyanogenMod...

I can send long messages without any problem directly on my phone or with DeskSMS on my computer.

By the way, we are talking about a problem with MightyText... not sure if it's what you are talking about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
My apologies. I assumed you were talking about stock messaging app as we are in the development thread for CM. Usually we don't chat about 3rd party stuff not working.

Cheers. Once again my bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haha yep, but it worked fine before, MightyText didn't update but new nightlies don't work anymore with it. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
It was actually CM that broke the app. They've been making a lot of SMS the changes and it broke multipart messages. Koushik to fixed it in latest nightly so see if it works now.

Commit: http://review.cyanogenmod.org/#/c/46009/ (I think he meant NPE)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
I almost don't want to update to any new nightly's because I am getting awesome battery life on the 7/22 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
If battery life is your priority, why are you using a white-themed background? Light colors suck quite a bit more battery than dark colors with SAMOLED displays (ref: some s3 tests I ran last year). Stick with the dark side.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You know I didn't wan't to be that guy, but I was thinking the same thing. Embrace the darkness. :p

Edit: I should note however that your research shows an inherent flaw by relying on the information forwarded by android about the battery and that you didn't fully charge to the same level between tests. It's not rare to see 100% last for longer if you bump charged your battery or to see your battery depleting very quickly from a certain level. That's common to a lot of type of batteries too. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
there doesn't seem to be a nightly for last night. Has the 5ghz wifi channel bug been squashed? I am itching for privacy manager and focal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I've noticed too. No 0726. Thought the SMS issue was scheduled to be included in that one.

Don't think the 5GHz band issue has been corrected though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
True but I got bored with the dark colors, figured I would give this a try for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Is anyone else getting really bad graphics performance on the latest nightly? It seems like any games runs for a minute and then freezes and runs badly. I was told to turn off HW Overlay in the settings and that helped. Is this known and being looked into or anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
love cyanogen.. NO HOMO
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
I think we can just wipe the cache and davlik then flash. No need for a data wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fznwolf:
These frequent updates are badass, thanks so much!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Has any progress been made with SMS working properly? Conversion to MMS requires that both parties have data, and also because of some reported issues with different carriers not being able to MMS between each other properly...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Actually, this site was created for developers. So the whole point was for developers to test themselves along with other developers. ;)

Developers testing other developers work=Bug reports, suggested fixes, and patches.

Noob testing=No logcats and ETA requests for fixes

Don't get me wrong. All the testing done helps out a lot. Just all the BS in between sucks. Just like this post I'm creating. But hey. We're all human. ;)

On to the topic at hand. I think I might have busted the wacko LED Notification bug. Edit- Looks like cm team has it covered. :highfive: :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Jealously sucks dude. try and tone it down a notch please. this is a development forum. remember that. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] americasteam:
Are you for real? You just sucked me back in Sparky. Sorry, but I don't have anything backwards. I appreciate all the hard work from each and every dev here. They take time away from family and friends to make our devices awesome. There's a difference in correcting someone that's breaking the rules and just being an arrogant prick just because you're a dev. I guess you think its ok to treat others like trash when things aren't exactly as you like it? I certainly don't. I guess we were raised different. ;)

Cyanogen, thanks for the new build. The community appreciates all the hard work you and your team put in to each and every device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
k guys. its over. leave it be. who really cares anyways. none of us. lets just hang out and watch the development. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
Errmahgerdd, I don't have wifi and I'm 300mb from my data cap with 6 days left on my bill cycle. D;

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] harryrasul:
what are the latest gapps to use with these? Is it the justinbean inverted gapps+
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
it doesnt matter which ones you use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
here you go http://goo.im/gapps/gapps-jb-20120726-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
I just fixed the LED bug, the PMIC driver is really stupid about parsing the string you give it. The fix isn't in the 29 build but will be in the next one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nismax:
I just have respect for this thread.... that's all now its over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
It doesn't "matter" but there are a few fixes in the latest. I think one of the big ones is Google maps(if memory serves)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
lol. i noticed you guys got that handled. its almost like i have to check the patches that are submitted every 3 seconds to keep up. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Have been using AOKP for half a week and moved back to CM10 when I saw the new update. Absolutely BUTTERY SMOOTH. I can definitely feel it. Thanks for a job well done, as always.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
I've tried everything for Camera ICS+ it keeps FCing. I give up lol I'll just wait for an official fix here. Until then it's blurry camera!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simplex123:
I'm pretty sure it just looks like it doesn't focus but try to point your phone at some words and move it away. It should refocus right away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omar300:
why is there no like button?

i honestly like so many comments and wish there was a like button, so many member have same thoughts or issues on rom like me,

just wish there was like button....

---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------

What is the best focus to use? infinite, auto or fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No, running fine here on yesterday's nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
I just started using cm...I see this nightly thread. Is there a normal cm thread around here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
This is it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
I'm sorry. I just got confused. I thought this was a separate thread just for nightlies because other ROM thread just put [nightlies] in the thread title

---------- Post added at 08:51 AM ---------- Previous post was at 08:51 AM ----------

Sorry again..I guess I should have thought about it a little more... Sorry
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
No need for apologies dude
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
CM 10.1.2 Front Facing Camera Bug

Hey guys,

First of all, I apologize if this problem has been addressed and / or fixed in a nightly build but I can't seem to find a solution anywhere.

I'm on the latest stable build of Cyanogenmod 10.1.2 and I'm having a weird issue every time I take a photo or video using the front camera on any app aside from the built-in one.

Whenever I try and take a photo or video, the phone screen goes black with the capacitive buttons left on for a few seconds and then the phone reboots. Originally, I thought this was limited to the app I had been using (Snap Camera HDR Pro) until I used another app yielding the same results. However, there seems to be no problem when using the built-in camera app except for the quality and features just simply aren't there.

Could someone point me in the direction of a fix if there is one or recommend an app that doesn't do this to use until a fix is issued?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's a known bug and there's no workaround so far that I know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
that happeend to me a twice but then never again. not sure why
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
So you're able to use 3rd party camera apps with the front facing camera and no problems? Are you on the same build as me or one of the nightly's?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
So I'm a little confused on versions. I was on version 10.1.2, on the top of this attached image, but then I saw a nightly that was created today so I downloaded and updated to that. Is that a newer version and why is it not listed on top? Main version released with numbers and nightlies with dates? Is that how it works?

Should I have updated or just stayed on 10.1.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
In the updates menu in About This Phone you should see a selection to choose whether or not you want to see the Nightly updates or just the stable ones. By default, I'm assuming, they have stable builds listed on top and nightly's listed after. Technically speaking you're on a newer version of Cyanogenmod but you're no longer on a stable version so expect bugs. If you want a daily driver I suggest flashing back to 10.1.2 stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
You could always check get.cm. They're listed in order of date added as far as I'm concerned. To answer your question the 10.1.2 stable was added on 7/11 so yes, the latest nightly is newer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
The term "daily driver" simply means that the ROM is stable enough to be used on a daily basis without the user needing to flash his or her device back to the stock ROM for stability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jhego:
This is probably a long shot. But i used to have LoserRom on my S3, i use Spotify thru bluetooth connectivity on my Pioneer x930bt and i was able to skip tracks on my steering wheel control, and also on the headunit itself.

Now i upgraded to Cyanogenmod Stable 10.1 (latest version), and now, i cannot skip tracks like i used to on both headunit and the steering wheel control. I was wondering if there is a fix to that and will the nightly build have some sort of fix done to this issue.

I'm not sure the how large the user base for this type of use but i hope someone has the same issue/fix for it. I really hate to go back to the old rom as this has everything i need

UPDATE*

Further searching, the Cyanogenmod 10.1 seems to be missing AVRCP 1.3 which provides the title/track/album info, and possibly control functions to the headunit/steering wheel control??? Not quite sure, any word of it being implemented?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
AFAIK this is included in 4.3 but in 4.2 and lower it had to be implemented by vendors, hence no CM. Assuming this can be ported, we hopefully will see it with CM 10.2. Obviously no guarantees since they don't even have d2 booting yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ehartqu1:
Is anyone else having a problem not getting notifications from messenger or gmail?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
Battery life has been absolutely pitiful in the 7/25 nightly. Anyone else have the same deal or is it just time for a clean flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Seems worse here also. No longer sure what build I was on. Used to idle down to 1% an hour, now closer to 3%. Also a dirty flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
Huh. I just don't wanna clean flash cause I'll have to re download my entire play music library. Guess I'll give one of the newer nightlies a shot tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
not a big deal but i guess it should be reported as a bug. if im wrong let me know. the option to show quick button was there in messenger when I first flashed the rom 7/25 but then after i flashed the MMS fix it was gone. i can still click "emoji support" but under it used to be "quick button" option but its not there no more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Gmail is not showing notifications for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Privacy Guard

I didn't realize till today that Privacy Guard blocks location access as well. Apps like Network Signal Info and GPS Essentials can't get location and GPS lock with Privacy Guard enabled.

Pop Up Message while enabling Privacy Guard only mentions contacts, messages and call log.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
A clean flash does not include wiping your music. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Pretty sure it will if he has it on his internal storage. Clean wipes are rarely ever necessary anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You have to wipe the internal SD separately. It is not included in a normal wipe for a "clean" install/flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Shouldn't be posting then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
True. It's just good to completely wipe the thing clean every so often. Gets rid of orphan files and anything else uselessly taking up space. By clean flash though I mean remove EVERYTHING and start fresh.

---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------

Whatever whatever. I do what I want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
That kind of attitude isn't necessary on XDA, or a development thread. Keep your feelings to yourself please
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
It was a joke, man. Lighten up a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Fine! That's fine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I often forget that some people on here are too young to know South Park
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Or that some people don't know about Poe's law. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Jokes are fine, but just put in a jk or something so we know. Lots of people on xda that cause grief. No harm done and sorry for the over reaction :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
Latest nightly crashes when running game killer. It crashes when you run a search in gk.... Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I read something...might have been related to koush's Google voice text thing but I'm not sure....whatever it was there was some new functionality that involved monitoring something or other. Whatever it was that I read said that the monitoring was using processor time which had a negative effect on battery life.

I wish I could remember more details but there have been a lot of new features lately. If someone takes a close look at the processor usage it should show up. And if it's a different feature causing it then my apologies to Koush for casting aspersions on his work.

~L.T.

Sent from my Galaxy S3 [AT&T][CM10.1]

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Is it true cyanogenmod team disabled any way to get boot sounds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
They haven't specifically disabled annoying bootanimation audio; they're just not supporting it. Pretty sure you can still use initscript hacks that use stagefright to play your audio.

EDIT: Gooooogle sayyys: blarrrgggghhhh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Looks like this commit was merged, and 4.3 CM10.2 will now boot on our d2's. :)

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