yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I don't think it's any of those things. I complete wiped to clean flash 6/07 awhile back. Then, recently, I completely wiped and flashed 6/26. On 6/07, I can send a 4MB picture and (what I assume is) the default CM messaging app resizes it to 327KB. On 6/26, I can attempt to send the same exact picture, the messaging app resizes it to 1256KB, but it hangs at "sending..." forever, never actually being sent by me or received by the recipient.

This is repeatable 100/100 times. I have verified it consistently. The process is attachment (from within a messaging thread), then send. Simple as that, no gallery or capture involved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Well from what you just told me it's resizing the image to a larger size.

~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] pcshano:
Blue Marble S3: 10.1 Stable, so far so good, no random reboot, etc.

White S3: 10.1 Stable, same spec and modem, etc.. as blue s3, so far 3 random reboots...

can someone explain to me why? lol I fail to understand why one doesn't while another does
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Clearly, but that means it's not any of the things you so assuredly mentioned, "Well it's either something wrong with the message (pic too big), something derped in your apn settings, or a bad flash." Therefore, your advice to the other poster was unnecessary. It's OK to just say, "I'm sorry, I was wrong," once in awhile. :)

Something might have changed (recently, between 6/07 and 6/26) in how the messaging app is resizing images. Without being able to develop a new messaging app from scratch, or undo alleged changes, I'm not sure how he or I could "devise a method to repair them." What would you suggest?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
A lot of carrier limit MMS size to 1024KB (1MB). I would try manually resizing it and checking.

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
That's pretty much what I was saying. It's too big. I don't know why it's being formatted too big but that is why it won't send. Resizing it manually was the solution that was found weeks ago. I've been telling you this for days, man.

Sent from my Nexus 7 [CM10.1]

Samsung Galaxy S3 [AT&T] [CM10.1]

Galaxy S Captivate [CM10.1]

OUYA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haven't really been following your issue or any issue in particular as of late. Just chiming in left and right.

If somebody can verify the status of android_packages_apps_Mms/res/xml/mms_config.xml for d2att, that would be good. This config contains the maximum mms size as well as maximum height and width.

For a simple solution, replace MMS.apk with one from an older version that works. If you upload it here, I can make a flashable ZIP that would replace it automatically if you flashed it after updating your nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Any idea how far back you'd have to go to find a version that doesn't have this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haven't checked the commits to be honest, but as far as I'm aware very little was changed in mms.apk lately so taking the MMS.apk from 6/07 or 6/08 probably wouldn't really matter.

I'm wondering if it's not loosely related to the calculation bug we got not long ago.

I'm at work so I can't really go ahead and get CM on the computer and unpack MMS to verify, but yeah, switching one from another should work.

Edit:

M3 values: size:614400 height:1200

RC3 values: size:1258291 height:1944

RC4 values: size:1258291 height:1944

RC5 values: size:1258291 height:1944

06/28 values: size:1258291 height:1944

hmmmm

Edit 2: Ah ha! Found one that is different. All size in bytes, height in pixels. So M2 has 600KB, RC3 and up has 1.2MB.

Still, if it worked on RC5 but doesn't work now, there's something else. Attached both RC5 & RC4 if you would like to replace your /system/app/mms.apk by one of these and check if it works. Suggest trying RC5 first, if it doesn't, try RC4. Not flashable zips BTW, unzip and replace manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Can you try an "adb pull /proc/last_kmsg" from a desktop?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit_vector:
I haven't seen much about this anymore. I am still experiencing this, though. Maybe less, but I can still get it to happen by using my GPS nav app for several minutes. Can anyone confirm that this is not an issue for them, or that it is fixed for them? I found a JIRA issue for it posted by someone with a different GS3, but it doesn't seem to be getting much love: https://jira.cyanogenmod.org/browse/CYAN-1384
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's not fixed. I have a Tasker task that starts at boot to disable HW overlay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sidetracking:
What's the easiest way to enable (and customize) the navigation bar on CM? As far as I'm aware there's no option in the settings?

Can I customize the bar with build.prop settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I flashed this file with mobile Odin directly on my device and bootloader stayed at LK4.

Is this normal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
As far as I know, Mobile Odin doesn't flash the bootloader as a safety precaution or something of the sort. You'll have to use PC Odin or Heimdall. Brewing a CWM-flashable zip from the files is also possible, but there are risks with that too, if you screw something up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sakiwinkie:
I have a Canadian version of the S3. In what way does the updated bootloader affect the device? Should I look at updating it?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
Sorry for the noob question... But... Do I have to update my bootloader?? I have a US version...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
if your bootloader is already LK4, I don't think you'll need to update it yet

for safety, for me at least, i'll wait until 4.1.2 release for i747 and flash its version of bootloader =)

P.S

doubting cm10.1 stable is actually stable =\ both my S3 experienced random reboot today
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Thanks man I'll try it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
Question to those on T-Mobile network after flashing 6/29

Do you get only Edge?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Try the T-Mobile thread. This is AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
you're clueless arent you...

forget it, I was able to fix it now

=)

though random reboot also happened to me on 9/29 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Hmm flashed stable and now whenever I try to access a song or video on my external SD card it says "SD card unexpectedly removed" and I can not access it until I restart my phone. Couple times it actually said SD card damaged, which freaked me the F out, then it came back when I restarted.

Anyone else experience this recently?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ily112:
So is this another bootloader we have to flash to flash anymore Nightlies/the 10.1 Stable? I haven't flashed anything knew since the LK4 bootloader and the 06/15 Nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
No, I think they are talking about the Canadian bootloader just added to the build info. If you installed a bootloader recently there is no reason to do it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Bootloader Assert And The Way We Do It

I've been thinking a lot lately about the bootloader asserts and the problems that CM are going to have going forward as new official releases come out resulting in a commit needed to add the new bootloader into the assert. We just saw this requirement with the new MF1 release here in Canada. I appreciate the work that Jiangyi did to get MF1 added virtually over night but he isn't always going to be here to get this done as easily.

What I was thinking would be a better and easier to maintain long term option would be to have the assert check if you have one of the old bootloaders installed instead of whether or not you have the latest installed (or any that have been released after today). This way any time a new official release comes out we won't have to add that version to the assert. We know what bootloaders are bad (anything before LK4, LK3 and LL1) and that list appears to be set. Furthermore, if we are just going to add the latest bootloaders to the assert and not delete the preceding version number it's safe to assume every bootloader going forward is going to be acceptable for use on CM ROMs.

So would we not be better off checking against the bad list instead of the good list. It would prevent having to have someone change the CM code every time a new release comes out. Furthermore it would allow new bootloaders in the future to be able to flash any ROM release and not just ones after the new bootloader was added to the assert. Example: MF1 bootloaders can't flash stable or anything before it because it was added to the assert after the Stable release but if things were done the way I suggest above, any future bootloader would still be able to go back and flash any ROM from before the bootloader was released. I realize we can't go back in time now to do this but going forward we wouldn't have to worry about it.

For example:

If bootloader = LEM, LG1, LH1, LH9, LI5, LE8, LH1 (Canadian version), LJ1, LK3 (Canadian version) ABORT flash due to unsupported bootloader

Else Flash ROM

Instead of the way we do it now.

If Bootloader = LK3, LK4, LL1, MF1 FLASH ROM

Else Abort Flash due to unsupported bootloader

We really handcuff ourselves this way requiring the addition of new bootloaders as they are released from our carriers.

We already do an assert to verify phone is d2att so we don't need the bootloader assert to verify if someone is trying to flash the wrong ROM on their phone so leaving the ability to flash the ROM with any bootloader that isn't on the blacklist won't be a problem. That blacklist will remain the same going forward.

Just my 2 cents and maybe it can't be done this way but to me it just makes sense. Means less work and less hassle going forward as new bootloaders come out.

Cheers and thanks for listening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killer Okain:
I'm getting the best battery life of any 10.1 release to date with 10.1.0. Got over 36 hours of what I consider light to moderate use. For me the stable has been flawless except the continuing issue of not being able to receive SMS notifications in-call with stock SMS app. JIRA seen here: https://jira.cyanogenmod.org/browse/CYAN-1550

It'd be nice to not have to select vibrate on call for SMS and call waiting, but rather to have an actual audible tone for both. Not sure why this is generally not the case with CM ROMs. Oh and one other minor occasional issue, had a few times when the notification light didn't come on for SMS when it should have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
Hey!

I'm stuck on MF1 bootloader and can't get myself updated to the LK4.

Odin won't read my phone despite having USB debugging on, uninstalling and reinstalling the drivers, etc.

Is there an alternative method that I could try? I'd go back to stock and then re-flash to 10.1 if I could.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
I have no idea if what you are proposing is doable or not, but say it is, attn1 on IRC alerted me to a problem with it: As it currently stands, all JB bootloaders are good, but that might change one day though. We won't be able to know if every new bootloader released would be a good one, and this is especially true on the AT&T side of things it seems, since they seem to have a record of doing screwy things with the bootloader. Sure, one can argue that it would be easier to add known bad bootloaders in the future to said blacklist, but I think it's probably better that we limit users to ones that are known to be working fine and having people verify newer bootloaders as they come out.

It's not an ideal solution to me personally, but it's definitely a safe one that ensures a good CM experience once installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Fair enough. I can see arguments to both sides but since I don't make the ROM I respect the decision by the CM team. Thank you for your response and explanation.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwang0429:
I'd like to report all the builds have instagram issue, they seem to be discolored, or with the new video function, you can record only 1 long section but unable to record small sections till 15 secs, it will crash and app and reboot the phone itself every single time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deep Search:
I also see this problem in snapchat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
do you have access to another pc? I would give that a quick try just to rule it out.

---------- Post added at 08:05 AM ---------- Previous post was at 07:58 AM ----------

more info... https://jira.cyanogenmod.org/browse/CYAN-1504
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
I don't. And oddly, the Nexus 7 toolkit works, but the GS3 toolkit doesn't. Anything else I could try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
That was my best shot... do you have Kies? if so uninstall it...

do you have the phone in download mode?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
I don't have Kies installed. Heimdall recognizes my phone (on my Mac). Anything I can do with that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
random reboot: https://dl.dropboxusercontent.com/u/8573299/PhoneCrash/1372349824330.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Please post this in cm jira(online bug tracking tool) which will help the cm team in resolving this at earliest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
done: https://jira.cyanogenmod.org/browse/CYAN-1574
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
If you have heimdall installed and it is recognizing your phone, I would use it to flash the boot loader - that's what I did. Unpack the Odin file and match each partition with the appropriate image. Was talked about when the boot loader check was implemented, so search from your computer to find more detailed instructions here or read a heimdall guide.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Two cars, one phone, broken bluetooth

I have a Sony headset which works BT fine with my phone, but I have two cars which cost slightly more for which BT is beyond horrible.

Ford Edge (the one with computer display screen). Device pairs fine, audio stutters for first two minutes of play and then actually seems to sustain and work great.

Honda Odyssey 2012, phone pairs fine, then drops bluetooth connection about every 3 minutes.

Will this ever be better? Should I post in another thread? I'm happy to post any logs that might assist.

BTW, I'm pretty sure this is the whole "AOKP and native drivers" problem. I have the same BT problems on Task650.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
Try using a different USB port.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kb9nvh:
Go to the sIII general topic AND FIND THE TWRP thread. Load the latest version. In that same thread you will find s link to a cwm loadable boot loader along with an odin loadable one. Download it and flash it like you were flashing a ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
I was able to flash the updated bootloader via recovery from here:

http://xdaforums.com/showthread.php?t=2321310

Thanks for the tips that led me in that direction.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Have you tried it with a different kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Hi guys,

Been a while I haven't posted. I have a 8gb sd card on my device. Suddenly today, for X reason, I get a notice that the sd card has been removed. Ever since, the phone doesn't read it anymore. Any idea?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
With all these bootloader questions why op doesn't update the post itself? I think this is significant update to be included in the main post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
There is an issue with certain SD cards and the S3. I am not sure what it is, but you might want to google it to see if you can find more info.

Regarding your SD, if your computer can't read it either then it is probably toast now... sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Ugh, the SD card was working properly since a while. I'll try to Google it, weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
They can and do go bad. Happened to me last year. Started spitting out the same message. The died.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I've noticed over the past week or so that if I hide apps in the drawer, homescreen shortcuts disappear as well. If I even hide the HD widgets icon, all my home/lock screen hd widgets are gone. This can result in "orphaned" widgets which require a hd widgets data clear and reconfiguration of the widgets (including lockscreen).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Using the default Trebuchet launcher? How do you hide the apps from the drawer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Settings > Launcher >

Drawer > Uncheck "Hidden apps (shortcuts)"

Is that what you needed?

Settings > Launcher >

Drawer > Hidden apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I just tried KT747. It had no impact on bluetooth issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Steve Kondik and Koushik Dutta are doing an interview on the new CM privacy features they are implementing at 5PM EDT.

Go to the geek.com G+ page to watch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
That's a life failure for me. It was right in front of my eyes :eek:thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Hello can i flash this rom over ics 4.0.1?

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
You should update to the most recent stock rom version before flashing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
We had an ICS 4.0.1? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I had the same problem around the same time as you, in fact. I plugged the card into an sd reader in my pc, ran the chkdsk tool on it, ejected it, and now it works in my phone again. No data loss, this time anyway... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Have any of the recent nightlies fixed the issue that was present in the stable build where audio through either Bluetooth or the headphone jack would only play through the right channel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It is fixed. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
I'm running the stable build and I have no such issue... Is it selective? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cstark27:
I am running the 6/29 nightly and BT audio works and sounds great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, I just updated to 07/03 and my Bluetooth audio is working correctly now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Was running Slim Beam...just switched over to this ROM. Very nice, clean, Android experience. So far no issues to speak of. Had to change from TWRP to ClockWorkMod to allow updating properly, but not a big deal.

Very nice, clean ROM. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Look into CyanDelta. Using this you can download very small delta files to update your rom automagically (like 15mb instead of the full package everyday). Free on the play store. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Cool. I'll look into it. Not really a big deal as I'm on wifi most of the time, but does this integrate with the ROM to download nightlies?

Do I have to disable updating in the ROM then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Disable the integrated rom updater. You can also move back to TWRP when using this utility for seamless flashing. I find CyanDelta particularly useful since it only downloads the changes and merges them so you technically end up with a full rom but spares you time & download.

I'm myself on wifi most of the time though, but it's good when you need your flashing fix and you don't have access to wifi. Saved me once, I was out and about and I had flashed a buggy nightly that morning. Didn't use my phone all day, when I went to use it that night it kept bugging on me. 2 minutes after I was flashing the newest nightly which fixed my problem and I could resume my wild night of partying. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Tried the 6/21, 6/29 and 7/1 nightlies and CM10.1, but with none of them do my gmail notifications sync between my GS3 and my N10 (rooted stock android). Previously, on the 3/8 nightly and M2 version, the notifications synced. By sync I mean when I archive or swipe away a gmail notification on my GS3 or N10, the notification would go away on the other device within 10 seconds or so. Now, this is no longer the case. Anyone else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Getting an error trying to update from 3.17.13 ROM to the 7.4.13 nightly.

...

Verifying update package...

Installing update...

assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop ("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"

E:Error in /sdcard/0/cmupdater/cm-10.1-20130704-NIGHTLY-d2att.zip

(Status 7) Installation aborted.

Anyone have this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea, you need to update your bootloader before you can update past a certain build. See my quoted post above for help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Looks like Koushik got texting with Google Voice working with the stock messaging app:

https://plus.google.com/+CyanogenMod/posts/Eq2ivfAX2Ki

Looking forward to trying this out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea that's a serious win.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Unless you don't live in the U.S. and can't get Google Voice...:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fatty001:
Out of two identical S3s, one running 5/12 nightly with stock kernel etc, and another on 6/24 stable release, how could the 5/12 phone be getting almost a full signal and 3G inside the house while side by side the 6/24 has no signal, unless it is against the window or outside (where it gets under 1 bar signal)?!?:confused:

I have tried dkp and ix kernels for a tiny improvement, but maybe I'm thinking I need to reflash the CM kernel from the 5/12 release to get a better signal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Make a nandroid backup and try the 5/12 build on the phone with the bad signal to see if they're the same with the same... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Doomstick:
Nvm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Go to Settings->About Phone and tap on the Build Number until you see the Toast message telling you Developer Options is enabled. They are hidden in Android 4.2 behind this process.