yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
If what you are saying is related to Crapbook Messenger, then seems to me that its a App issue.

Have either of you tried the app on other LP or KK Roms ? Any crashes there ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Crapbook Messenger... LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=3639717]Perseus[/MENTION], it is most definitely "crapbook" messenger lol its been a pita during testing since the beginning of LP. I'm glad to see the official builds are back. Congrats, I'm definitely gonna boot this bad boy up! ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Yea I didn't mean it to be a knock on slim. Definitely an app issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maddogg_cz:
So any fix for red around the screen flick? Other than that this is a great rom!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yeah I have one. Sorry been sorting out other stuff. Will post an update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Did TRDS not make the transition to lollipop? I swear I've checked every setting and menu item a few times, but I haven't found it. I'm running the 11/16 build.

Also is RRO not in 11/16? I can't find a layers setting or app either.

I like the ROM, but my phone is looking a little white. I'm used to blacked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Please see, [BitSyko] Official Layers and BitSyko Apps [RRO]

The rom supports changes, necessary. You need to install the app from that thread and download all the required layers. I am not including them in the Rom for variety of reasons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
looking forward to the squashing of red flickering..? no ETA though. Still running great... thanks [MENTION=3639717]Perseus[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Look No further than my File Host.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
yeeh! downloading asap ? can't thank you enough, thanks so much [MENTION=3639717]Perseus[/MENTION] really appreciate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
FOR THIS ONE THREAD ALONE -

I am relaxing the NO ETA Rule a little bit. You can ask for a build if I have not posted in 3 weeks. Still can't ask "When will you........." :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] critikality:
hahaha...quite funny [MENTION=3639717]Perseus[/MENTION]...yes oo when will u?..lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Am I missing the settings option to remove the phone and camera shortcuts from the lock screen or is there no such option on slim?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The lockscreen shortcuts are managed by

Settings > Security > Shortcuts

Camera and phone are LP default ones. You'd have to use a custom launcher such as CLauncher should you want to remove those too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guywong:
Does this ROM work on Chromecast?

Just wondering if I can use this ROM to cast the G3 screen on TV using Chromecast. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
It's working for me. D2ATT running on the previous build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Little update; I've flashed the lastest update and it runs flawlessly. The red flickering is definitely gone for me!

Note that Ive dirty flashed the update over the previous build; clean flashing it resulted as an error on TWRP screen. (Of which Ive forgot to take note, damnit)

Keep going the good work [MENTION=3639717]Perseus[/MENTION]! I really appreciate it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
That error could have been due to Bootloader version mismatch. Can you let me know your Baseband or bootloader version ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
[MENTION=3639717]Perseus[/MENTION], is there any chance of you cooking up a Slim MM build? :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes SliM is on the cards. Patience is a Virtue. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Ahh... no rush... was just curious. Awesome! :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
[MENTION=3639717]Perseus[/MENTION]

Baseband version is the lastest for a Canadian phone working on Koodo network.

I747MVLUFOB1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
now I am really curious in the Error message. Do I assume correctly that you have a D2CAN or D2ATT ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
To be correct, it is a D2CAN.

But since the Canadian is so freaking small, I got to rely on any version made for the D2ATT. Since both are almost similar, I usually get the same bugs as a "real" D2ATT phone. I've been on many, many differents version since then but this time, it's a first for me.

My phone was originally locked with Bell when it was given to me. Went through the "secret" submenu to unlock it in order to make it work on Koodo network. I've manually flashed the lastest modem update (FOB1) to get a better signal, which works greatly.

I believe I've said everything about it. Well, I hope so lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Thanks for the clarification. The whole reason I asked this was that, there are certain filters in the updater Script called Asserts. That sometimes block the zip from being flashed if wrong device bootloader is expected. That results in errors in Recovery.

In this case, D2CAN is one of the permitted ones. So technically there shouldn't be any errors. But since you did have an error, I asked for your Bootloader. Since that happens to be d2can, I am now interested in what the error was.

Can you install the app build.prop editor from Play Store and get values for

ro.product.device

and

ro.build.product

for me ? Particularly, do this on the setup you had before you flashed. Perhaps you had a Nandroid from back then ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Will do on thursday morning.

I'm currently on the road and I rather have a wifi access while re-flashing since I never did a Nandroid backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Little update about the re-flash; for some reason, the error didn't showed up with AND without a clean wipe...

I've even tried dirty flashing it over another ROM (Oct-Os L to be precise) and it still was a success.

I seriously don't ****ing get it...

Anyway, for the rest, here it is.

ro.build.product = d2att

ro.product.device = d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Oh Well. It happens. Please let me know if it happens again. Thanks for the values.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
UPDATE

I've been meaning to post this for a while now. Just was pushing it out.

There have been rumblings with Slim Roms as you might have read elsewhere. This has caused delays in developing for Android M or 6.0.1. I just wanted to give a heads-up that there have been delays with updating sources. How long before the builds are ready? I really am not sure. I might be able to get out one build at best, but might not be able to keep it up unless the core trees are maintained and updated.

Unfortunately I ended up trading my S3 as part of my change from T-Mo to US Cell. So now I am relying on Testers to test the alpha builds and provide priceless boot logs and Radio logs. Without those logs, I will not be able to proceed any further.
​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
Thanks for your time [MENTION=3639717]Perseus[/MENTION].

I believe that Im talking for everyone who tried your builds, that were really appreciated because they were top notch!!! ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voo-doo68:
+1 with above!!

I started off with SlimKat and loved it. Now running SlimLP and have no regrets. I look forward to SlimM, but know it will be when you think it's ready.

Great work Perseus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adri_sefp:
Hey, sorry for the noob question, I got a Samsung S3 LTE (i747m) from Telcel with Android 4.3, then I installed the lastest official 4.4.2 from Rogers via Odin, but when the phone booted up I noticed that this FW doesn't have Spanish on the "Language and input" settings, I was looking for a tutorial to downgrade to 4.3 but all I found is that it is impossible because I have the newest Kernel (or Bootloader?) with Knox, so, can I flash this ROM without bricking my device? Will I have Spanish again?

PD: I have rooted it and tried with Language Enabler but just some things are showed in Spanish. Thnx for ur help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Not Sure I follow, are you saying you want Spanish or you Don't want Spanish ? Either way, you can look for correct language firmware from Rogers. Typically, upon first boot after flash, it should prompt you for language.

However, to answer your question, yes this rom supports Spanish.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adri_sefp:
I guess I didnt explained it clearly LOL, I always use Spanish but after intalling the Rogers rom I only have Enlgish, French and Chinese. Language Enabler doesn't work. I'll try to install this rom and lets see what happens (hope I wont brick my phone :v)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Please note [ROM] [AOSP][6.0] Slim6 Early Alpha 0.1 now exists.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
Slim has always been one of my favorites. Good to see that it's moving on to M. :):thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Nice! Very few ROMs have run as flawlessly as SlimKat did for me. I am looking forward to rocking Slim6! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Did you run into issues with Build in OP ? Remember, OP is D2GSM. ALL GSM Variants can use it. Its not AT Alone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] coyotefiveoh:
No it will not flash. I'm a CDMA variant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Ok I've got to ask what is going on with the infrastructure? No commits to github and not able to access gerrit since Feb 21st. To be clear I'm not asking for any sort of ETA I'm just curious what exactly is going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
How's it going, Perseus? Is there any news?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Good news everyone! http://www.xda-developers.com/slimroms-updates-on-the-horizon/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I was on Vacation and just getting back. Will be working on Dropping 5.x.x
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Lots of commits happening on slim gerrit these days! Can't wait for the 5.1 to roll out!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Build is up on Perseus' AFH.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Another Build is up on my AFH. I cleaned up the download folder into 2 sub folders. Let me know if you have issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Hmm... tasty! I'm surprised no one has commented on these two builds so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Welcome back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
Running very smoothly

Flashed this, on my i747m d2mtr and it works great. Camera is taking pics, Data and Wifi are working. Life is good.

Can't wait for more Slim goodness.

Awesome work on the ROM, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JonathanJS:
Glad you're back, I've missed SlimLP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
Never ran Slim Kit Kat but always good to have more i747 devs!

Sent from my Amazon Fire HD using the XDA premium app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbird57:
sjamie,I just installed this ROM will get back with a report.....later on

I am surprised no one has any comments :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Please do, my friend. I'm trying to work out some other issues with my phone before I flash this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Do I have to flash supersu after flashing still? Also, texting doesn't work on the d2tmo build. When I send messages, I hit send and the message disappears.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
SMS not working

After flashing, I noticed SMS wasn't working. I would go to send a text, and the message would not appear in the message thread after I hit send. The recipient would not receive the text. I tried a few different messaging apps and nothing worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
No you don't need SuperSU. Just Enable Root under Dep Options like always. As to MMS, read on.

Please can you check to see if your APN is set correctly ? It so happens that on T-Mo, I always land with MetroPCS APN and I have to always change to T-Mo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
APN is set fine here. I'm on wind. I also reinstalled and completely lost the signal. It was there for some time but vanished. I think it vanished after I texted. I'll restart and test again.

edit: well this is weird, i have a 3g and h+ signal, but it doesn't seem like any data or texting is going through. APN's are all fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
Just tried SMS again, making sure APN was correct, it was. I discarded it anyway and made a new one to be sure. SMS still doesn't work, the message disappears after I hit send.

My data is forsure good.

Sorry, I meant to be saying SMS, not MMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Are you using Google messaging or stock message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
I've tried both apps, stock and Google messaging, with the same result.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nicklovell23:
SMS issues is a known issue and it's being worked on. In the meantime some 3rd party apps and hangouts should work for texting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The Recents are not fixed yet. But There's some other customizations for QS Tiles & More importantly ability to get rid of the # Symbol is now in Developer Options. New Build Up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
I ran the new build this weekend, and it was quite successful. All the important things for me worked perfectly, Data/Wifi, Camera, phone, and SMS, yay.

Plus, could have just been me, but I thought it was running quite fast. Faster than other lollipop ROMS from what I've seen.

Such an improvement since last build.

Keep up the awesome work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Switching the camera back and forth between picture and video modes a few times crashes the camera. A reboot is required to use the camera again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
I had no issues with any of the features or functions that were in this ROM, except for the recents. There are still very few Slim options, but the core is running very, very smoothly.

I could easily have used this as my daily driver, however I"m going to wait for a bit longer to use it as that, I would like to see more Slim features first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Curious, does this use CM as a base?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Punkgambit:
apparent modem issue

Hi, hope anyone can point me in the right direction.

If been using slimroms for some time now and some months back while playing around a decided to install the NJ1 bootloader/modem and since that day i've been having signal and connection problem. i've read a few threads but haven found any information that can help me with out risking bricking the phone. i haven't try any other rom, only slimroms.

thanks for any help any of you can bring.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Most people report an increase in signal quality when updating to NJ1 firmware. Not sure what's happening in your case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VGMC0001:
Are you using i747 or i747m? I have an i747m and was at NF2 and didn't have any issues like that. However, I also updated to OB1 not too long ago, and haven;t had any issues with that either. I found my firmware update on Sammobile(which seems to be down at the moment)

Secondly, try another lollipop ROm and see if the problem persists.

Thirdly, how long did you wait for before you decided you were getting signal drops? Data connectivity can sometimes take a little while to settle down when installing new ROMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Punkgambit:
1st. at&t I747

2nd. I'll try that. i'll also try going back to Slimkat and compare.

3rd. A few months, it was manageable but it increased with SlimLP, so i was waiting for a few updates before trying anything else.

Thanks for the replies. I'll be a little busy today so i'll post any update on what i found probably tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Punkgambit:
Hey Guys,

Here is an update on problem. I did a full wipe yesterday and installed Perseus Latest alpha, the first boot up gave me a blank base band on status and no signal at all. i wiped again and installed the ROM. after that apart from a little lost signal time in the morning the rest of the day had been a non issue one, I've been dialing from time to time and haven't seen any signal lost or no network available indications until now. i'll give it a few days and update again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
So far, I'm in LOVE with this ROM and it is lightening quick! Everything is working including the ability to change camera storage to the sd card which is a major win. The only issue I've noticed is the keyboard takes a while to appear sometimes but it does eventually appear. Coming from SlimKat, I certainly miss features like long press back to kill and a Dark/Black theme. I'm about to go on a 3-hour drive so I'll test the signal, bluetooth, and GPS. Excellent work, [MENTION=3639717]Perseus[/MENTION]. I can't wait for the next release!

Note: This ROM is really too stable to call it an Alpha release! :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MetalHead66:
I'm gonna have to try this then. Is there no long press back button to kill in developer options? At the bottom? Or maybe that was KK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
If it is there, I just haven't found it yet. It was definitely there in SlimKat which has been my daily driver for a long time. I don't believe many Slim special features have been added yet. Definitely give this ROM a try. I'm the process of restoring all of my apps from TiBu to see if I can use this as my daily driver in its current condition. I think I can!!!

This white theme is growing on me but it can't even come close to the dark theme SlimKat and many other CM 12.1 ROMs have. I know it is just a matter of time before [MENTION=3639717]Perseus[/MENTION] adds it. I have to keep telling myself, "One step at a time..." LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MetalHead66:
Well I just finished backing up CyanideL and getting ready to try this. As for features my S3 is no longer my daily phone since upgrading to the S5. I mainly want to use this for my music because V4A isn't supported due to the locked bootloader AT&T has so generously given us(bastards). Plus I have the 7000mah battery in my S3 and can for days without plugging in. As for kill app back button, its in developer options in Cyanide. Love that feature. Hope its here as well. But regardless, I'm need to flash something. Getting restless not being able to do much on the S5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I've found a few minor issues:

1. Go to Menu > Settings > Apps > Pick any app and notice its version number and file name overlaps towards the top of the screen. Someone else is also experiencing this behavior on a different Lollipop ROM - http://xdaforums.com/showpost.php?p=60699054&postcount=165

2. Sometimes when I hit the hangup button on my bluetooth headset, the disconnect tone is played but the call is still connected.

3. While on a call, if the speakerphone is turned ON, the audio volume cannot be controlled.

4. Holding the menu button on the homescreen brings up the old school Google search instead of Google Now. (see attached)

Here's something interesting worth noting. After I restored my apps from TiBu, I rebooted twice for different reasons and immediately after the 2nd reboot, a message popped up on the screen stating, "Android is starting. Optimizing app x of y". In my case, it took about 45 minutes to "optimize" about 189 apps before I could use the phone. I've only seen that behavior after wiping dalvik cache. Maybe something happened after TiBu restored my apps that caused the dalvik cache to get erased. But no "optimization" took place until after the 2nd reboot after the apps were restored. I did NOT restore any system apps.

LTE, Camera, GPS, SMS, and MMS all work well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NeverSeparate:
[MENTION=4204995]sjamie[/MENTION], I don't think dalvic exists anymore. Just art. And art does take longer initially. Once they are done they should run better than they did in dalvic. But I may be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Ahh... that makes sense. This ROM is running very smoothly and I'm getting the best battery life on LTE I've ever experienced! My battery is draining at less than 5%/hr with light usage.

However, the signal can be a little wonky at times. This dev seems to have found a fix. Hopefully [MENTION=3639717]Perseus[/MENTION] can incorporate a similar fix in the next release. :)

http://xdaforums.com/galaxy-s3-att/development/unofficial-cm12-nightlies-d2att-4-7-t3075452.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I found the Swype keyboard to be reasonably timed. I did notice and reported the fact that for the first time the Keyboard is all white and you need to press one of the invible buttons to make it visible.

Hard Button Reconfig is coming. In testing right now. Be happy to post a test build.

1. Noted just now. Will need to pass up the food chain.

2. Don't use BT Headset. But noted.

3. Need to test this one.

4. Yeah that's Goog Now stealing Menu Button. Can't help there. At least not yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MetalHead66:
I'm in no hurry. S3 is my backup phone now. I did install the latest build but haven't had time to mess around with it or restore my apps. Maybe I'll do that later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Chromecast

Does Chromecast work on this ROM?