yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheungnation:
I am noticing that I am having issues sending MMS. I flashed 7/1 and 7/5 (hoping that a later version would help) but I am still not getting connectivity. I came from a clean install of 7/1 but flashed 7/5 on top of that (with both cache clearing). There is also a substantial wakelock when I send MMS--it keeps increasing unless I reboot the phone. Data works well.

I've checked my APN settings with what has been posted here before, and the settings matched up exactly.

I also cannot connect my phone to the computer with this install despite installing drivers and trying many of the suggestions from XDA. Although I do have an microSD card to use, it is slightly more inconvenient. The device shows up under "Devices and Printer" as Android, but I cannot access it.

Is anyone else running into these issues? If not, does anyone have any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darkendes:
I'm having the same issue with MMS. I just noticed it today. I'm on the 7/4/13 build.

Sorry, not able to provide a logcat at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cheungnation:
I searched some more, and I think it could be from CM, but I wasn't sure what version PAC is using currently. Under about phone, I see this:

CyanogenMod version

10.1.1-RC0-d2att

This post outlines some of the issues and a possible fix. http://xdaforums.com/showthread.php?p=43046457&highlight=mms#post43046457

I've also tried installing MMS.apk (RC5) as the person stated, but I couldn't get it to work as intended. Perhaps I'm doing it incorrectly... You should try.

It's a bit strange that the messaging app doesn't automatically resize some images for you. Wasn't this done in the past? I never had to resized before sending out images or MMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Night lies have not built since the 5th. No logs generated either. Something going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
We changed folders and i hadn't fixed the link yet. Its fixed now

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Thanks, didn't even think to check a different folder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ledhed:
The only issue I've been having lately is that 2-3 days after I flash any new nightly I start to get "external sd removed" errors repeatedly. Anybody else got this? A new flash usually fixes for a few days. No other issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancollado2003:
can anybody drive me in the right direction to mod dpi my navbar? thx :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Hybrid Settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edgarpo:
edit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whasty:
halo not working

i might just be missing it but i cannot see the "Halo" bubble anywhere

i see it briefly when i click play in the halo app, but it goes away and i cannot figure out how to get Halo to work

I have searched this fourm and if i have missed something i apologize
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
You have to make sure it is enabled in Settings, and then turn it on in the notification shade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whasty:
awesome thank you so much
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Yup :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dirrtyswan:
Anyone having trouble editing the colors of the battery charging LED light? I could in previous versions but not on this one. Settings > Display > Battery Light. Clicking on them doesn't do anything anymore.

I did a clean flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zonen:
I haven't been able to get it to work either, coming from tw this method of changing led is a pain unless I'm just doing it wrong, but when I do assign an app and try to test it nothing happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drping11:
Battery

Sometimes the percentage while my battery is charging disappears
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dirrtyswan:
The app specific LEDs work for me...are you turning off your screen after you hit the test button? There is a popup there telling you to do so, otherwise you wont be able to see the LED blink.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zonen:
Ya I did then waited the 5 seconds or whatever and nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boxy52:
I don't know if this is the right place to post this or not and if it isn't please forgive me but I was wondering if this ROM is compatible with the newer 4.1.2 MF1 bootloader for Canadian S3's? I know it's not compatible with ICS bootloaders but I thought maybe it would be okay with the MF1 since it's jellybean.

Also, just to make sure I'm not confusing myself, bootloaders and baseband/firmware is the same thing right?

EDIT: I'd also like to clarify I understand it will give me a Status 7 error if I try flashing with an MF1 bootloader I'm just wondering if I change the updater-script and flash it anyway will I run into any major problems?

Thanks!

EDIT 2: I checked it out for myself. The latest nightly does indeed work with the MF1 bootloader. Also, loving halo!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
No, baseband and bootloader are two different things. They almost always have the same version number because the version is based on the date the ROM was built. Yeah.. Should be safe to modify the assert. Cm probably didnt modify their script because it is a Canadian release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ssssschwartz:
I wanted to update to the latest nightly (I've been lazy and last updated it in late May or early June) but got the following in CW touch recovery v6.0.3.1

Extracting System
set_perm: some changes failed
E:Error in /external_sd/pac_d2att-nightly-20130712.zip
(Status 7)
Installation aborted.

I have updated my bootloader and flashed it like the original post said in the past and again just to make sure it was done right. I had the Status 7 before but that was for the incorrect bootloader and I did update since then, but I don't understand this error since I don't think it's tied to the bootloader issue that I had before. I appreciate any help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boxy52:
Some might not recommend this, but I do this all the time as regardless of what bootloader I'm running my phone faces issues at the d2att assert since my phone is technically a d2can. I've never found a way around this other than just opening up the zip file, going to META-INF/com/google/android and extracting updater-script. Edit the first few lines of the script to remove everything that tries to verify your bootloader. These lines start with soemthing like "assert getprop" and you'll know what it is because it'll basically just be a list of baseband numbers and d2att at the top. Remove just those lines, add the edited updater-script back into the .zip (I just use the add file function in WinRAR, it automatically replaces, just make sure you're in the META-INF/com/google/android folder).

The reason people don't recommend this is because you might actually not have the right bootloader and it runs a chance of bricking your phone but if you're certain your bootloader is correct (like I am) then just do this and it gets past that barrier. Good luck!

ALSO, on a side note, been running this on the new MF1 bootloader and it's been running like a gem :) Thank you to the devs for a great ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
To get around the d2att assert, you can flash the d2att twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boxy52:
I didn't try twrp but I did flash the d2att cwm and my phone seems to still have that problem so I just opted to screw the assert altogether
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
no issues for canadian d2 with CWM recovery here.

CWM_Recovery_6.0.1.2

flash with odin

CWM_recovery.tar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boxy52:
I'll try it out. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ledhed:
Anybody else having Wi-Fi refusing to go back on after turning it off? I'm on the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ssssschwartz:
Thank you! I just now tried it and it flashed fine. I was worried it was something with the SD card going bad maybe but removing the asserts did it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wickedninjalo:
No problems here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
that happened to me last week, i was so confused and disappointed, couldnt download a new update to try and fix without using data.... bit the bullet and downloaded over data, updated, stILL DID NOT WORK!!!!

turns out i needed to reset my router!... roomate failed to tell me he didnt have wifi either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buffdaddyjr:
Any idea on timing to update to CM 10.1.2?

I see that the CM version is 10.1.1. Any plans to add in the newer changes from 10.1.2?

I wanted to say GREAT ROM, Combines the best of the ROMs I previously used and always wanted a piece from another ROM. Thanks for the work.:cyclops::cyclops::cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
We have kept up to date with cm every step of the way. We just haven't bumped the version number up to reflect it yet.

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MiteMouse:
Is it just me or is it the dirty flash? With the latest nightly my wifi doesn't stay connected and the battery icon style revert back to normal battery icon within 10 seconds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buffdaddyjr:
I thought that you kept up and incorporated all new changes but just seen that it still shows 10.1.1-RC0. So it is really 10.1.2?

Thanks for the reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
i think you answered your own question.

......actually you shouldnt ask any question when dirty flash scenario is involved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
Not to be a noob, but I can't find on the change log where it says the latest version of Paranoid Android that it was updated to. I was just wondering if the news 3.67 was included?

Sent from my Soviet-red S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] codo27:
I saw a more recent gapps package on another roms page, should I only use the one linked in the OP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Support will most likely only be offered for people using the gapps from the OP.

Sent from my NovaGen'd d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
Try it. If it works then let me know and I'll update my link to it. I usually just direct the most recent gapps from goo. Others host their own and mod them so they might have newer dates.

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] codo27:
I went ahead and tried it. Firstly I wanna say I love the rom, just looks amazing and has every feature you can name. I'm using the stable release instead of the nightly. Right from startup it started coming up and telling me calendar storage stopped, and would repeatedly do that over and over. Cleared the apps data and cache and its fine since then. I just tried the camera and its telling me it cant connect to the camera. This probably related to gapps? Is there anything I can try to resolve this before I have to flash again? Thanks

edit: okay, searched the thread and seems I'm not the first to have this issue. Maybe I'll have to try the nightly, would be a shame if I had to switch back as the camera is indispensable. It just sucks because I work in the middle of nowhere and takes forever to download anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
The stable is way out dated and has issues. U seethe latest nightly and enjoy

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] codo27:
7/19th nightly installed, camera working. Will try to get back with more thoughts after I've usEd it for a bit.

Okay, early thoughts

Battery is getting raped. What's the best preset? I can compromise some performance, although I'm enjoying the speed.

The battery icon keeps reverting back to stock after I change it. Is this a preexisting issue? It will revert whenever the number changes. Still shows whatever I have it set to in settings

Those are the major concerns so far. I don't mean to dissect your work, it's a great ROM. I just need to change a couple things to get it the way I want
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Papa Smurf151:
No worries. Yes we are aware of battery issue and it should be fixed after today. As fir battery. It takes a day or two to settle in. Also try a different kernel as that plays a part as does governor you run

XDA Moderator
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheHow7zer:
Hey, papa-smurf? Just wondering if you can answer this for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
where do you think all the holo bug fixes, ect are coming from?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] codo27:
Installed the 21st nightly. Battery icon issue persists, now swype doesn't work on the stock keyboard either. Also how can I disable halo? I really dont care for it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TRusselo:
Double tap and slide halo to the X that appears at the top of screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cprager:
Has anyone else seen an issue disabling the navigation software buttons in ROM control after being in tablet mode where they do not go away? Ive searched around but couldn't find much.

Just removing the buttons not the whole nav bar because when in tablet mode it also removes the status bar when going into hybrid and setting it to 0.
[Asus  Eee Pad Transformer Prime] jaii:
How the hell is it done? I've seen plenty of threads relating to switching the icons for WiFi, BT, GPS, etc.....but nothing for the Back, Home, and Menu buttons. Just flashed Androwook 1.4 hoping my icons would match those in the screenie, but no go >.<

Any input....or hints even?
[Asus  Eee Pad Transformer Prime] flumpster:
What screenie?
[Asus  Eee Pad Transformer Prime] jaii:
The photoshopped screenies that pretty much act as the header for the AndroWook post.

If you look at the center image, you'll see that the back, home and recent apps icons are all pretty like. How are these swapped out?

Also, good looks on that Bluestacks issue when flashing over the recovery. Thanks again :D
[Asus  Eee Pad Transformer Prime] flumpster:
They will be an install option in HB 1.5.
[Asus  Eee Pad Transformer Prime] AnnonymousFalcon:
Try this;

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

Not the easiest way, but it should get the job done
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Alright so Cyanogenmod has posted on Google+ that the international S3 has a got a working 10.1 ROM. What is the difference in the two devices?

(Regular S3 and international version)

And are we gonna see a 10.1 ROM for the USA version?
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Here is a pic of the system info....
[Verizon Samsung Galaxy S III] droidx2.3.3:
I'm sure we will we a 10.1 ROM soon. And the international version has a quad core CPU while the us version has a dual core.
[Verizon Samsung Galaxy S III] kintwofan:
Also less ram, and some other hardware. Oh and different partitions (that's why an international ROM hard bricks us).

Sent from my SGS3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] tonu42:
Yes we are getting it in the near future. We DO NOT ask for ETA's EVER on ANY cyanogenmod release.
[Verizon Samsung Galaxy S III] Addiso:
That's a nice build prop edit...

:silly:
[Verizon Samsung Galaxy S III] TechSavvy2:
Yeah, because that's how CM team rolls..... :sarcasm:
[Verizon Samsung Galaxy S III] jellydroid13:
I think we should see one soon but the devices are for the most part different. The international is running the Exynos 4412 with 1gb of ram while we have the Qualcomm Snapdragon S4 with 2gb of ram. So basically the hardest part of getting it working is completely different on the two devices.
[Verizon Samsung Galaxy S III] Addiso:
It be a very good troll though just saying ;)
[Verizon Samsung Galaxy S III] Stran93r:
Why couldn't we get the quad core and all of the other goodies of the international version? :confused:
[Verizon Samsung Galaxy S III] jellydroid13:
Because at the time the exynos 4412 didn't support lte or tmobiles hspa+ 42 so the us got a dual core version, but to compensate they gave us 2gb of ram
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Do you want the link to the Google+ post?
[Verizon Samsung Galaxy S III] Nopi45:
What you failed to mention is that it boots buts it completely useless what the post really says.
[Verizon Samsung Galaxy S III] funnyperson1:
Not to mention that dual Snapdragon S4 cores are almost as good as quad core A9 cores in benchmarks. They're probably better in most real world scenarios where the increased clock speed and ipc of the S4 will outperform in apps that aren't designed to take advantage of four cores.
[Verizon Samsung Galaxy S III] Addiso:
Was just joking bud, don't take it to heavily lol
[Verizon Samsung Galaxy S III] LLStarks:
CM10.1 will boot on the i535.

But the screen will not activate since the proprietary driver doesn't play nice with the new code.
[Verizon Samsung Galaxy S III] kidhudi:
link to the google+ post please. i want to start following. i searched the cyanogen place i have followed but didn't see anything about the i535 maybe i am at the wrong one. i am psyched about the possibility of 4.2.
[Verizon Samsung Galaxy S III] kintwofan:
Can you show me were you saw this? The only 4.2 build I've seen for us was not booting.

Sent from my SGS3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] Chuckleb0ne:
Just search for CyanogenMod. And there was no announced i535 just yet. Just S2 and S3 international.
[Verizon Samsung Galaxy S III] Stranger_84:
4.2

Can't wait for any updates on this subject ...
[HTC Pico (Explorer)] nightfurious:
Hey guys,

I am new to this and ran into a problem and would appreciate it if i could get some help.

So i recently rooted my phone and flashed CM 9,1 Build 9 and drained my batter to try to recalibrate it as suggested at quite a few locations here. Well, the phone died and when I plugged it in for charging, it sort of woke up (slight white screen ) and then nothing. now it refuses to charge or turn on. I am going to try a new battery tomorrow but for the time being, any suggestions please?

thanks

Edit : I was reading the help section on HTC rezound and apparently it has something to do with CWM not allowing offline charging once the battery is fully dead. I'll try charging the battery through some other means and update you guys if it works. Also there is a way to get it to boot into recovery using adb with some trickle charge but that hasnt worked for me.

Thanks again !
[HTC Pico (Explorer)] shortyoko:
That's from the official cwm recovery, next time use twrp or yannou's, only thing as far as I know is, take from somwhere another battery with some charge and change recovery.
[HTC Pico (Explorer)] nightfurious:
Thanks for your help. I am using yannous recovery and yet ran into this issue. Resolved by charging the battery elsewhere. Worked fine after that. Mods can kindly close the thread.
[EVO 4G Q&A, Help & Troubleshooting] subnoize soulja:
Just a quick ? my girlfriend owns an evo 4g and she is still running 2.3.5 and i tried updating her phone and there is no updates found or it says its up to date??? Didnt sprint ever roll out and ICS update for this phone? I thought i read somewhere that it did? Anyways thanx in advance for and answers!!!!
[EVO 4G Q&A, Help & Troubleshooting] Soap:
No ICS update. Just 2.3.5
[EVO 4G Q&A, Help & Troubleshooting] nrvlljr:
Plenty of awesome ics roms around these parts though..if she wants it you can make it happen for her.
[EVO 4G Q&A, Help & Troubleshooting] subnoize soulja:
yea i could make it happen but she doesnt want it to happen!! Ive rooted every phone i ever owned but she wont let me touch her phone but o well she doesnt know what she is missing out on and i try telling her all the time!! Her problem not mine
[EVO 4G Q&A, Help & Troubleshooting] subnoize soulja:
O i thought it read somewhere that sprint started rolling out the ICS update in august for this phone but maybe i just miss read it!?!?
[EVO 4G Q&A, Help & Troubleshooting] Soap:
That was probably the evo 3D. I heard they got ICS.
[HD2 Android Q&A, Help & Troubleshooting and Genera] slamdunk58:
MOD EDIT: XDA doesnt condone warez
[HD2 Android Q&A, Help & Troubleshooting and Genera] mengfei:
congrats!

& next time break your note into small paragraphs:cyclops:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nigeldg:
Don't post warez please, everyone knows how to get free software if they want it but it's not allowed on XDA.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Marvlesz:
^As he said, warez are not allowed on XDA.

If you are not familiar with the site, I strongly advise you to have a look at the forum's rules.
[Fascinate Q&A, Help & Troubleshooting] abcs1:
Not sure which CWM I was coming from, but I wanted to go back to stock. Here is what I did:

C:\Users\Brian\Downloads\Cell Phone\CI500_VZW_EH03_GB_CM.tar.md5

C:\Users\Brian\Downloads\Cell Phone\atlas_v2.2.pit

I select the partition box and got this error.

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> param.lfs

<ID:0/003> Sbl.bin

<ID:0/003> boot.bin

<ID:0/003> recovery.bin

<ID:0/003> zImage

<ID:0/003> factoryfs.rfs

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Please help. I dont know what else to do. Thanks so much.
[Fascinate Q&A, Help & Troubleshooting] abcs1:
I literally have tried everything. Not sure if the .tar is incorrect, or what is happening. Phone wont turn on though, its stuck on the samsung logo boot.
[Fascinate Q&A, Help & Troubleshooting] Crawshayi:
Have you:

Tried a different usb cable (or several)?

Tried a different usb port?

Tried a different OS?

Tried a different version of Odin?

Tried redownloading the files?

Tried stock 2.2 Froyo instead?
[Fascinate Q&A, Help & Troubleshooting] abcs1:
Looks like it was the USB cable. Damn i spent like 2 hours researching and trying everything . Thanks for the response bro. Have a good one.
[Fascinate Q&A, Help & Troubleshooting] Crawshayi:
No problem, it's always the last thing you think of. Glad you got it though