yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustyoemre:
In belgium ...

Hello everybody, I live in belgium and I have a SGH-I747m. Can I install this rom without problem ? I installed this rom 3 month ago, and my sim card wasn't detect ( belgium sim card ).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Cyanogenmod April Fool

http://phandroid.s3.amazonaws.com/wp-content/uploads/2015/04/android-powered-by-microsoft.png

in one of my test built on April 1 had the above boot image - Powered by Microsoft.

At first instance, it seems that Microsoft purchased Cynaogenmod. But reading on the internet, found to be ------ April Fool

More Details
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Try syncing the entire CM repo. ;) Did it last night and it was ~17GB!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Android 5.1

OP has been updated with the first CM 12.1 build. Camera is the most stable till date and flash you will be happy!!

Changelog:

Android 5.1 - Yes you read it correct

Camera Fixes

Major kernel changes!!

Stability fixes!!

Reduced first boot time!!

Please donate, if you are happy with the state of this project from where it started till date
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epicboy:
Does 5.1 fix the memory and battery issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Clean flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Quick question about "clean flashing."

Would wiping /system and /cache, flashing this ROM, and then flashing GAPPS pretty much be clean flashing? Or will the presence of old CM settings data left behind screw things up?

I'm just trying to avoid having to do a complete Factory Reset if I don't have to. I'm coming from CM11.

Also, should an official build from CM ever drop, would we then be able to use the built in CMUpdater to go from this unofficial build to an official nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epicboy:
To answer your first question, yes you have to factory reset. Especially coming from an older rom. Incompatible data will cause very bad issues. You can use a backup app to backup your apps. I recommend getting the full version of Titanium Backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
My only problem was all my app have to install one to one from Google play. Camera work good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WitnessG:
I wiped the system and tried to flash the new update but it fails. TWRP says "Error executing updater binary" I'm using a d2tmo. Would I need to do a complete wipe including data or is this another issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
What version of twrp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Alright, I think I'm finally gonna take the plunge and flash this ROM. Quick question before I wipe my phone, however. Which version of my bootloader should I have installed on my d2att in order for this to work? I'm currently on MJB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
I used Philz on my D2TMO. Worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WitnessG:
I used 2.8.5. Forgot that there is a new version. I'm going to update and try again.

EDIT: It still has the error on 2.8.6

Did you do a clean flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
Yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AcSkdw:
I apologize if this has been answered here before, but can I directly flash this on my s3 T-Mobile(t999) or do I need to make some sort of modification before I flash the file linked in OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
All my texts disappeared after updating to CM12.1, and service took awhile to start working. Google Play Services is constantly crashing, along with some Google apps like YouTube. YouTube crashes every like, 2 seconds. Over and over again.

I dirty flashed just the ROM from the latest 5.0.2 build.

EDIT: I've decided to clean flash the latest 5.1 build and 5.1 Gapps. Will report after completion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
Clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
Guys don't forget to donate to op. He's doing an amazing job for all of us and he needs the money not to became rich but to buy hardware to continue to provide us with great ROMs.

Donate what you can. I donated $10. I know it's not much but that's what I could do right now.

If you go out to a restaurant you tip I'm sure and for that time only. Well matrixzone has been delivering us great work every day. Don't you think he deserves a beer?

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Isuress:
Is this even real life? I'm actually really excited for this! I've never flashed Cyanogen Mod before and have been waiting for this to be a stable build but damn it, this looks SO tempting!

I'm currently using a Roger's SGH-I747M with a baseband of I747MVLUFNE6. Stock 4.4.2 Roger's ROM. Apparently since I last updated, there's been 2 updates for my phone. They are as follows:

2014-07-01 - I747MOYAFNF2

2015-03-01 - I747MOYAFOB1

I'm currently using Clockwork Mod Recovery and have SuperUser installed and working.

I know that I have to use TWRP instead of Clockwork Mod so I guess I'll have to figure out how to flash that.

With all that said, which of the 3 listed basebands should I use to install with this 5.1 ROM? My guess would be the latest 0B1 one but I'm not sure.

I think the process would be:

Backup important data and files from phone.

update to latest stock basebands (One of the 3).

Install latest TWRP.

Wipe /system and /cache.

Factory Reset.

Download and flash the ROM from OP through TWRP.

Flash Slim GAPPs.

Wait for long boot time.

Then it's ready to use?

Is this the correct method of installation?

Also, which version of TWRP do I download and install if I'm using a Roger's I747M S3?

d2can? Or d2att? I thought that all S3s were roped into D2LTE or something like that? I can't find that in the TWRP downloads?

Which do I get for my phone?

Did I miss any steps though? Anything else I should do that's important?

Like I said, I have no experience with flashing Cyanogen Mod. I've only ever flashed Stock ROMs from Sam's Mobile.

I guess if worst comes to worse, I can just wipe everything again and reflash the latest Stock ROM, right?

I'm a little scared but excited.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Loving 5.1, greenify now has the ability to track cutoffs line xposed used to do. And camera is better, not perfect yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epicboy:
You will need to edit the updater script located in /meta-inf/com/google/android

Delete all text that comes before mount.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
Do you happen to know if snapchat video's work? I'm using an older stable version of this rom but don't wanna update because I'm really stable. Unless of course snapchat video's are working, then it'll be flashed in 0.0000001 seconds. Any feedback is great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
I can test that for you. You mean recording videos or watching video snaps?

I just clean flashed the latest 5.1 ROM.

---------- Post added at 03:12 PM ---------- Previous post was at 03:06 PM ----------

I just tested, back facing video works but front facing video starts but when you stop holding the recording button it doesn't work.

Viewing video snaps seems to work normally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
Much thanks, downloading now! I meant recording, sorry for the lack of info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Help

Is it normal on lollipop for LTE to be unstable. Like I have to switch from 2G and back to LTE to get it to work sometimes. I just installed 5.1 on my i747 S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
My understanding is that you should be on at least a 4.4.2 bootloader. The minimum would be NE4 for the i747. Most comments I have seen confirm this. I have seen one person state that MJB works fine for him on the 5.0.1 version of CM12. I haven't seen him comment about using MJB on 5.1.x.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
I also have a d2tmo and I have the same error.

Do you mean delete all text that comes before the first word "mount"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] epicboy:
Open the file in a text editor. And I'm sorry, delete anything before "ifelse".. That's what I did on my d2tmo on the updater script for cm12.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Everything seems to be running great so far after letting the ROM settle. Google Camera let me take a few pictures without issue, and after some initial flakiness LTE seems to finally be sticking.

Excellent work, matrix. I'll be donating soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Flipnotic:
Coming from CM11, and I tried backing up my SMS, and contacts (SMS, call logs, etc.) using Titanium Backup and when I try to restore "data only", the dialer and messaging app constantly crash. Any ideas?

I backed up the one that says Phone/Messaging Storage (SMS/MMS/APN)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crandy2:
Same problem here. Had to switch back and forth to get it to connect at all. Then after a reboot would have to do it again just to get it to connect again.

Wifi was flakey too. Wouldn't connect at all on 5ghz, would drop frequently on 2.4ghz. I'm on ne4 baseband and mjb modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] insaini:
Wifi

Hi Guys. I've done a clean flash of 12.1, and I'm having an issue with saved wifi connections not connecting when in range. When I see the connection in the list I can manually connect it and it'll work. Also, if I remove it and recreate it, I get an error ("Failed to connect to network"), but after a reboot the recreated connection will appear and be connected automatically or requires a manual connection...real random. Any ideas?

Thanks for the fabulous ROMS MatrixZone! :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I am on the ne4 bootloader as well and have had the same problems with wifi. Thinking of going back to 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
So I had this issue with camera back on kitkat and just encountered it on 12.1. If I try to use the stock camera app as we all know it tends to say it can't connect and closes. OK no big deal. However I can open messaging, twitter, Facebook, various other apps that access the camera, and try to take a picture to post in said apps it opens the stock camera and it works without problem. That makes me wonder how something can utilize the stock camera app and it works but if you open the stock camera app it crashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lullcat:
Same here. After 10-20 minutes in "deep sleep" the WiFi connection is gone.

Also sometimes the cellular connection icon would have the exclamation sign on it - what's that?

All connections get restored after reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
That data won't restore without issues... Especially if you are going from KK to LP. Clear the data and start fresh. That's the only way the dialer and messaging app will work.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Flipnotic:
Thanks, I know that the donation version of Titanium Backup has SMS + Call log XML backup/restore. Would this work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Don't do it.

Downgrading bootloaders to an earlier version, once you are on MJB or newer, as you are, will most likely brick your phone.

A better option may be to upgrade to NJ1 to see if that improves things. But if you do upgrade you will be in the same position of not being able to downgrade to an earlier version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
I use a app called SMS & Call Backup. I use Titanium for apps & then I restore my SMS backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
My friend modified CM 10.2 to work on my NE4 bootloader and it works great. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It's very true that a 4.3 ROM will work on the NE4 bootloader and modem. I was concerned that you were speaking of downgrading the bootloader as opposed to changing ROMs.

Glad it has worked out for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Oh no I was not. That might brick my S3 and I don't want to do that since it is my main phone. I guess we have to wait till 5.1 becomes more stable but with the way its going now I feel that there will be a official CM ROM soon for the S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
That should work better than restoring app data.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
That worked [emoji1]

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
Ummm .... D2CAN

I've had no problems at all with this ROM until now...

My phone says (paraphrased), " ROM is for d2lte, d2att ... your phone is d2can". Your ROM's have always worked before, so what might be the problem?

P.S.: My BF is going to kill me if I can't fix this!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Anyone keep getting the voicemail alert on 5.1? I checked my voicemail.. I dont have any.

WiFi is really unstable as well. Camera is more stable for sure. Things are looking up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
What recovery are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] praneeth19912:
can you share links for nj1 bootloader!! thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Sadly, xposed is not working (yet) with android sdk - 22 which is in cm12.1, otherwise,nice release! Only problem i encountered is the "failure to connect to network" bug when connecting into wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxkid123:
http://xdaforums.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

must be on ne4

If you happen to be on mjb (like me, oops, forgot to update) then here's the mjb to ne4 link

https://www.androidfilehost.com/?w=...f0be91501f8d702b5a4afcfd7a1587c93de908982c865

I'm going to update from mjb to ne4, reboot, clear dalvik, and then run the ne4 to nj1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
I can say- this is one of the most stable (camera, mostly) releases by far. (5.1)

Camera works nearly flawless in Google Camera. Tap to focus a few times consecutive in a row works, video recording works, everything just works better than previous releases in my experience. Only way I've got it to crash so far is by zooming in and out rapidly.

I haven't encountered any random reboots.

Android 5.1 feels a lot smoother and more refined than Android 5.0, but it might just be the placebo effect.

I have encountered one issue. It seems that sometimes frames will get all messed up (only been able to reproduce in Android Lollipop easter egg and resizing text in Snapchat). I attached a screenshot of what it looks like. I'm pretty sure this is a CM12.1 issue, but just something I noticed.

WiFi also doesn't auto connect after a reboot/first turn on, so you need to turn off and then turn on WiFi to get it to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Does xposed work for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
Xposed doesn't work on any Android 5.1 device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Thanks for clarifying mate!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Testing wifi fix, hope this works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rutilant:
Clean flashed the newest 5.1 build. Some of the bugs I found:

- Camera's a lot better. Stock camera works the best, Google Camera crashes a lot. Using the volume button as a shutter button crashes the app every time though.

- Google Messenger can't send or view convo histories, while Hangouts and the Stock Messaging app work fine.

- Videos in Snapchat record and send fine, but end up being received as a green screen with audio only (this has happened for the past few builds).

Everything else is perfect, haven't had any WiFi problems. Seems a bit smoother too though I don't know if that's cause I wiped my phone. All the new little 5.1 animations are pretty cool.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunkin11:
NJ1

NJ1 firmware fixed my WiFi and LTE issues. I was on NE4 before and the LTE signal wouldn't stick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I concur for the Google Messenger bug, other than that, ROM is sleeeeeeeek! Thanks matrix!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s.vivekananda007:
Whats your model? d2att?

I am having crazy wifi dropouts. Im on NE4 - d2att. and NE4 is the latest firmware available for d2att.

Any suggestions is appreciated. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
NJ1 is the most recent for the d2att. There is a link to it on the previous page, in this post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s.vivekananda007:
THanks a lot man

Just clarifying: I see these "d2att_I747UCUFNJ1_bootloader_modem_4.4.2_12-3-14.zip" - 19mb (and) "UCUFNJ1_Rooted.zip" - 980mb

It should be OK if I just flash the modem.zip right? I dont need to flash the latter and install CM again, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunkin11:
Yea, I am on at&t. Just flashed the firmware. I didn't wipe and reinstall cm12
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s.vivekananda007:
Thanks. I upgraded to nj1, I still face most of wifi issues as earlier(connecting and finding issues), except that wifi dropouts are lesser or rare now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxkid123:
Im on nj1 now and my signal still has random drop outs. I already tried reflashing the nj1 firmware and that made no difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pradyu09:
on NE4 baseband signal and wifi very good sometimes wifi doesn't auto connect other than that very stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andPS2:
dirty flash from 5.0 lead to constant play store crashes

fresh install can't connect to wifi at all

uploading bootloader to nj1 didnt help

p.s. back to 5.0 unofficial

will try again in the future

p.s. never do firmware reset as in my case that messed up my twrp which i had to reflash with odin
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
For the people mentioning the fact that WIFI does not auto-connect anymore, I'm also experiencing the issue on my d2att phone, but as well on my cm12.1 touchpad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
bump
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for sharing the update. You saved me troubleshooting this issue.. Will wait CM to fix this issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, I think the WiFi bug is in the CM source at the moment. Not a huge deal. Everything else works so damn well that I can't complain.

---------- Post added at 10:04 AM ---------- Previous post was at 09:52 AM ----------

Yeah, I've encountered those graphical glitches during certain app animation transitions here and there as well. Hard to reproduce, though. Just seems to happen at random.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Discussed before, let's you know your not using data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gocats7:
root

disregard post about root. Had to enable in developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
Hi check in setting\developers options and go to root access
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 911Guy:
As promised! Great work!

Confirmation number: 99C01579Y0438345V
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ervinasp:
Well, built-in camera still not working for me after 04/03 12.1 update, google camera crashed after trying to switch to video mode. After trying to disable and enable it again, it says can't connect to camera.

Am I the only one? got the cm 12.1 after a clean wipe.

Update: just had a random reboot as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry, it seems I have wrong Paypal email id associated with my XDA Profile. Can you please cancel this transaction and transfer funds on the new Paypal ID.

Sorry for the confusion.

This is applicable for other users also. Please cancel your donation transaction if you have transferred through my XDA Profile. I have corrected the email ID

Thanks for your donation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andPS2:
ok did some more tests

with slim mini gapps i keep getting google play store crashes after a while

even after wipe everything i get better results with gapps-L-3-28-15 (dont know where

i got these from)

when connecting to wifi the first time i get an error

but when i leave it and reboot then later that connection does work

still excited that galaxy s3 is my second android device on 5.1 now

thanks [MENTION=4551784]matrixzone[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Holmes108:
I keep trying to restore apps with titanium and that's when the play store immediately starts crashing for me, even rebooting and reinstalling gapps doesn't fix it. I need to start from scratch.

This is with slim normal gapps.

Edit: going to try and completely ignore titanium and see if it still happens.

Same wifi issue as well. Toggling wifi fixes it for me though, rather than a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirdizzle415:
try uninstalling the newest update for the play store.

I had an older version of gapps 5.1 that I installed. it worked fine. installed the newest play store update and it would constantly crash. uninstalled the update and it worked fine again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
I had this last night. I ended up disabling the Google play app until I'd restored all my apps, then I enabled Google play, which would then stop regularly. I then cleared data in both the store and the service. Opened up the store and redid the check box thing. It's been fine since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mklein994:
GPS bug fixed (I think)

After a clean flash of the latest build (it was the 04/03 release; my CyanogenMod version number says 12.1-20150403-UNOFFICIAL-d2att), I found using the "GPS Test" app that the GPS bug that's been plaguing my phone since CM11 was fixed. Before I was unable to locate any satellites, but now it finds them and locks on.

I'm using a Rogers d2can, running CyanogenMod's version of clockworkmod (version 6.0.5.1) and did a clean flash (i.e. wiped /system, /data, cache, dalvik cache, and then just formatted the entire internal sdcard) from the 03/27 update. Also of note, I'm using 04/03 Slim Gapps mini.

Hope this helps.

P.S.

I highly recommend SMS Backup+ for backing up texts and call logs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andPS2:
i used to get the play store crashes after playing back some apps via titanium as well

but the different google apps fixed that for me!

p.s. guys i just realized us three found three different solutions!

gonna love the creative vibe on xda developers! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Along with stock camera crashing switching to video; when charging, the lock screen no longer displays the time to full.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s.vivekananda007:
Guys, my google play store kept crashing after restoring apps from titanium backup. All I did was go to settings -> apps -> All apps -> select Play store and clear data and cache.

Its working perfectly fine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Everyone having issues with gapps take a look @ this https://plus.google.com/+MWasifChauhdary1/posts/YZ7eQyD4Yib I used these on 3 5.1 lp ROMs & they're as good as they ever were???