yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Master Cylinder:
Great! I remember you mentioning a Pebble.

But, BT issues are endemic on the ATT S3, too. I haven't checked other devices. On the ATT forum some have said that their devices worked right on KitKat. So, it's an ongoing battle on LP.

Article in todays New York TImes about Android and it's prospects. Cyanogen is mentioned. Might be a separate entity to Cyanogenmod hackers.

Murky Road Ahead for Android Despite Maket Dominance
[Verizon Samsung Galaxy S III] brandonb0013:
Yeah I never had issues on KK. I hope I don't have to go back to that. It was starting to get slow and more and more random reboots.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I'm on the 5/23 nightly and at the moment the only problem I'm getting is my phone not ringing through my bluetooth
[Verizon Samsung Galaxy S III] Master Cylinder:
According to this post on the ATT thread, there might be a solution for you, 4/22 build or earlier - a place in LP to plant yourself while this gets worked out, rather than going back to KK. Worth a try anyway, unless you didn't have any success on those builds from April either. I have an Invisiblek 4/19 and 4/23 if you want them. Maybe someones else has a 4/22 if needed.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Second this. Never had BT issues on KK. Do you guys have glitching issues with BT Audio? I don't ever have force closes, but during song playback, it will get really glitchy until I go to the next song. I use play music and a Sony deck. It could be some kind of buffer issue since my network is spotty when I drive.
[Verizon Samsung Galaxy S III] brandonb0013:
Again just quoting myself here, but an update, 7 hours in, no BT disconnect yet. Usually happens within an hour or two. Did the usual restore with titanium, same everything as every other build I've flashed. Hopefully it all stays good!
[Verizon Samsung Galaxy S III] stevet86:
My Bluetooth had to be connected every time I restart our if I turn it off and then back on. Once it's connected it's goog to go.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Is NE1 the best modem to use, nothing newer? I always feel like my signal was better back with other roms.
[Verizon Samsung Galaxy S III] brandonb0013:
22 hours later, BT finally crashed. I'm happy with that for now! I think the change that was made definitely had an effect on it and think it should be looked into. I took screenshots of the crash report again.

http://imgur.com/AgKwiBx

http://imgur.com/sVsljRD

http://imgur.com/CveGwAb

Notice it says 4.4.2 why is that? Obviously I'm on 5.1.1
[Verizon Samsung Galaxy S III] Master Cylinder:
Nyet!

Here's what my fingerprint is :

ro.build.fingerprint=Verizon/d2vzw/d2vzw:4.1.2/JZO54K/I535VRBMF1:user/release-keys

That's jelly beans, Touchwiz and current secondary bootloader! They it is! The Current bootloader! Got it from my nandroid log Yours has the modem
[Verizon Samsung Galaxy S III] brandonb0013:
Did... Did we solve it?
[Verizon Samsung Galaxy S III] Zeigren:
5/28 is working great for me so far, but using smart lock with NFC doesn't work for me.

I can add NFC tags but actually unlocking my phone with them doesn't work.

Any ideas of what I might be able to do to get them to work?

Thanks!
[Verizon Samsung Galaxy S III] LLStarks:
Will LMY47Z be merged?

https://android.googlesource.com/platform/build/+/android-5.1.1_r4

Not sure if anything changed since LMY48B
[Verizon Samsung Galaxy S III] Master Cylinder:
Can get current bootloader!! EDIT: Maybe not

This is fascinating, and annoying. I can't tell you how many times I looked through those dang recovery.log files that is generated in TWRP nandroids (CWM is different) and looked at this line again and again, but was not seeing I535VRBMF1 but I535VRBMB1. But it's right there in your 2.5mb log. (It does have over 30k lines of data!!!, though only the first few hundred have useful - very interesting info about your phone.)

So, IT CAN BE DONE!!!

EDIT

: Maybe not

To get the current secondary bootloader, which is what people are talking about when they say bootloader, you can look in your log around line 262 and see it, or

you have to be in recovery

and type in the Advanced>Terminal command line in TWRP, or using adb shell:

getprop ro.build.description

getprop ro.build.fingerprint

They give the same info in slightly different formatting.

I get "d2vzw-user 4.1.2 JZO54K I535VRBMF1 release-keys" with the first one, and

Verizon/d2vzw/d2vzw:4.1.2/JZO54K/I535VRBMF1:user/release-keys with the second one.

However, if you do it with the phone booted you will not get this but different build info and the modem version instead of the secondary bootloader. which is what brandonb0013 got from the crash report generated. The phone was booted. This is also the info in the Philz CWM-based recovery log, strangely.

I assume many of those specifications can be revealed with a getprop, though I wonder how many would be different when booted. Using adb bugreport probably will tell that, along with thousands of other things - best to redirect that to a file if you want to see what's in there, or use 'more'

It's pretty interesting to browse through the first 300-400 lines of a recovery.log file to see interesting, and sometimes confusing and contradictory information about your phone.

I will post this on the OP. I'm gonna check my Philz to see if it works, too.

EDIT

: Not yet.

EDIT: Philz CWM-based recovery using Aroma Filemanager>Open console and entering commands gives:

d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys

EDIT: Actually, if others would check this with their phone I'd like to get some confirmation that it's repeatable at all.
[Verizon Samsung Galaxy S III] hallstevenson:
Don't know if that means anything. That comes from /system/build.prop. It's hard-coded too, not a queried value.
[Verizon Samsung Galaxy S III] Master Cylinder:
Actually, that's both right AND wrong. What shows up in build.prop is: d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys. A new build.prop comes with every new build, n'est pas? That's not hardcoded.

What comes from those commands in recovery is: d2vzw-user 4.1.2 JZO54K I535VRBMF1 release-keys

I installed VRBMB1 back when I rooted and unlocked the bootloader (I don't remember which one and the exploit they used.)

I agree certain parts seem hardcoded. Don't know why it would show 4.1.2, and shows 4.4.2 when "queried" booted, or through CWM.

The "query" command getprop gets properties. I'm gonna figure out where it's getting those from in recovery. They aren't completely accurate

EDIT: Correct me if I'm wrong.:good:

EDIT: I guess this is still an inquiry, but nothing certain yet.
[Verizon Samsung Galaxy S III] brandonb0013:
Let me know if there's anything you would like me to try, test, theorize etc. Let's squash this bug.
[Verizon Samsung Galaxy S III] hallstevenson:
I get the same values.

A build.prop does come with each ZIP but it's not always updated each time other than a few lines that are build or date specific.

By the way, I'm running LiquidSmooth at the moment and my build.prop has the same line, down to the 4.4.2, KOT49H, and VRUDNE1 references.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 05/28

MMS/SMS ringtone not working. Messages coming through, but no ringtone.

UPDATE: my "Interruptions" setting turned it off, doh!
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm getting SMS ringtone but no MMS...:(
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 05/29

The App Drawer now has vertical scrolling. I don't like it. It seems like Android M has dropped in CM?
[Verizon Samsung Galaxy S III] AyUaxe:
So was your app drawer paginated before 5/29? I use kk launcher to get smooth, fast, continuous scrolling. Highly recommend. Vastly smoother/faster and more customizable than trebuchet (del with each flash) carp. Since I'm being all heretical up in here, I've finally had the chance to use my BT ear bud more on 5/23 and now 5/27 with no problems at all. Links up automatically and plays music/does calls for hours. Only weirdness is phone and bt ring for incoming calls. No biggie. The salient diff between my set up and those who've reported BT probs seems to be that I've been using dkp kernel. The 5/08 dkp build is also highly recommended.
[Verizon Samsung Galaxy S III] phonetool:
Are you using the Trebuchet launcher that CM provides?

Try Nova Launcher for much more control.
[Verizon Samsung Galaxy S III] ChuckFarley:
Just wanted to give a quick thank you to the devs keeping my S3 and unlimited data alive! I've been happily running 5/27 for a couple days. Stellar work!
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
The default Trebuchet launcher has the new vertical scroll Drawer App.
[Verizon Samsung Galaxy S III] Stealth111:
And I personally love it!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] justinnotjason:
What's everyone using for free Wireless Tether? Is it built in or Is it still possible to do that edit using the SQL app in the appstore?
[Verizon Samsung Galaxy S III] hallstevenson:
Built-in has worked fine for me for years
[Verizon Samsung Galaxy S III] brandonb0013:
Built in works fine. Having the option to toggle using the quick status bar is convenient
[Verizon Samsung Galaxy S III] AyUaxe:
Is anyone else getting "Unfortunately Google play services has stopped" messages? They crop up @ 1/hr. Every thing else seems OK. Had flashed cm gapps a while back. Tried flashing banks 5/27, to see id that would help, but no change. I'm still on 5/27 cm build. Thanks for any input.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I used to get that issue back with 4.4 using ART. I believe it IS a Gapps issue according to others here though. I personally haven't had the issue since 4.4, I am currently using banks Gapps with no issues. Maybe a clean flash is somehow necessary.
[Verizon Samsung Galaxy S III] brandonb0013:
I had it when I flashed certain ones. I used the ones in the op just fine. Same with the banks. Don't recall which was bad as I deleted it
[Verizon Samsung Galaxy S III] LLStarks:
Was enough M Preview source released to compile with?
[Verizon Samsung Galaxy S III] afx337:
I'm on 5/26 and everything seems to be working perfectly, aside from Wifi. It keeps dropping out when the phone sleeps.

Stock camera has been working for me, which is nice. First time since CM11.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Usually the answer is no
[Verizon Samsung Galaxy S III] phonetool:
Try setting location to device only. See if that helps.
[Verizon Samsung Galaxy S III] Master Cylinder:
Might check your Privacy Gaurd>Advanced setting for it to make sure Wake Up is set, and check other settings there. Might also look into your Titanium Backup to restore a previous version, or update through the Play store. Make sure it's not "Greenified.'" I had this once and flashed different GApps to fix it, or restored from TiBu, can't remember.

I couldn't send MMS on 5/31 or 6/1. (Also couldn't dload 5/29... to try to fix.) Also Google Speech to Text stopped making that noise that lets you know it's working. Restored last nandroid - 5/22, and all is well. Might put 5/29 back on or wait till what's next.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 06/01

MMS (sent & received), blutooth, all working just fine here.
[Verizon Samsung Galaxy S III] AyUaxe:
don't know why, but switching to GPS only worked.

Have not had a Google play services crash since changing this setting as phonetool suggested. Thanks for such a simple solution. But why does it work?

Crap, spoke too soon. It just crashed, though just once today, instead of once/hour.
[Verizon Samsung Galaxy S III] phonetool:
It seems that a few days ago Google updated the Google Play Services app and since then custom ROMs of all sorts are having problems. My DD Gnex, for one. I don't know what's behind it, but I trust it will be resolved in a week or two.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks. Maybe it's like a thermos. You know, keeps hot things hot and cold things cold, but how does it know?
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 06/02

MMS (sent & received), blutooth, all working just fine here.
[Verizon Samsung Galaxy S III] Master Cylinder:
I was just unable to update apps today: the update shows to be in progress - 10 apps showing the progress bars, but nothing happening. No downloading. Using TiBu, I first restored Google Play Services to a late April one - it was updated a couple of days ago apparently, but still no joy. Then I rolled back Play Store to one from the same day as the other - BAM, it worked. I selected to detach from the market for both for now - don't know if this really works though.
[Verizon Samsung Galaxy S III] brandonb0013:
Any luck with xposed on this ROM? I hear Samsung has boot loop issues. I assume that's a stock style ROM but I want to ask before I give myself a headache.
[Verizon Samsung Galaxy S III] justinnotjason:
Flashed early today using CWM. No issues in the flash that I can see. I have been using it for about 12 hours and besides one BT drop right after a reboot, BT has been solid on my pebble. Everything else seems good.
[Verizon Samsung Galaxy S III] Master Cylinder:
Some have been using it with success on the ATT S3, as long as one doesn't activate a feature the same as cm's at the same time. Here is the thread where it's from: http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

I'll be trying it myself in a day or 2, once I get my MMS working right again - won't download automatically.
[Verizon Samsung Galaxy S III] AyUaxe:
Dirty flashed 6/02. Left location on "device only." No Google play services crashes all day. Good battery life and performance with stock kernel. Much better, it seems, with dkp kernel. Basic BT pairs and works well. Was able to update 3 apps in play store.

Reenabled high accuracy location and Google play services crashed almost immediately. In app management, I don't find an option to roll back play apk. I can only f/c, disable, clear cache and data. I'm OK with GPS only, but it's a weird bug.
[Verizon Samsung Galaxy S III] brandonb0013:
Aaaannnd we use arm not arm64 correct?

---------- Post added at 11:56 PM ---------- Previous post was at 11:55 PM ----------

Seeing as you have a Pebble as well, did you have issues with bt on prior builds?

---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------

Also, I want to flash 6/02 but am worried about the play store issue. What's the workaround for that? Anything but device only mode? I use Tasker to switch back and forth depending on the app I'm in.
[Verizon Samsung Galaxy S III] Deliquified:
Mine is on high accuracy and i haven't had anything force close on me.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Xposed works well for me.

And yes, arm NOT arm64. Arm64 is for 64-bit phones, and the S3 is not.

You'll have to reflash the Xposed module every time you flash a nightly though.

And make sure you're using the latest Xposed installer apk and Xposed bridge
[Verizon Samsung Galaxy S III] kmoore11:
I'm on 6/2, and haven't had any Bluetooth issues. MMS working. No Google Play issues, but I never had any of those. I'm still getting WiFi connection failures though, I woke up this morning disconnected for some reason. Is there a fix for that I missed?
[Verizon Samsung Galaxy S III] Master Cylinder:
According the the host thread here you should be able to skip the bridge? I guess it won't hurt to install it. What does it give you?

On the S3 ATT thread, the same BT issues reported here have seemingly been cleared up since 5/29, including Pebbles.

I haven't heard of any wifi problems reported as an ongoing issue ... No one here or on other cm12 threads I've checked lately have been reporting any. Sorry. Still looking around...

Meanwhile, I also haven't heard of any MMS issues reported, but I can't get mine to auto-download, and therefore notify that it's arrived. Anyone got any ideas? I've checked the APN, copied [MENTION=2963287]mastamoon[/MENTION]'s apn*.xml file in, on NE1. I'm about to do a clean flash to see what that does. HATE to clean flash!! Tried last night with latest GApps from the OP and it wouldn't dload any of the 99 apps that have to be individually downloaded. :mad:

PS - this is obviously not a ROM issue.
[Verizon Samsung Galaxy S III] brandonb0013:
Never once have I dirty flashed, but since I'm already on a nightly, I should be ok to do so? How do I go about doing it? Don't wipe anything just install the new nightly? Do I install gapps again? I'm starting to dislike the initial hour I spend setting up afterwards just to find that BT crashes on me. Lol.
[Verizon Samsung Galaxy S III] Master Cylinder:
I bet!! Just install it straight without doing anything! You can wipe dalvik/cache, though "dalvik" will be rebuilt anyway as it boots for 20 minutes or more. I wipe cache for no good reason really, just in case of a new system app conflicting with something in cache, which I don't know if it's true. I used to never even wipe anything.

EDIT: no need for GApps cause you already have them installed. Won't mess with them.
[Verizon Samsung Galaxy S III] Master Cylinder:
I was referring to an App backup program like Titanium Backup. There are others, including one in ES File Explorer I guess. (I don't use it since I use TiBu.) ROM Manager. There are a bunch of them.
[Verizon Samsung Galaxy S III] justinnotjason:
First NIGHTLY flash (06/02). Before I was running an out of date stock rom.

This has significantly improved performance on my phone. :highfive:

EDIT:

Is there any easy way to have a different lock screen wallpaper than regular wallpaper? What I've found online had to do with navigating Root and renaming files.

http://xdaforums.com/android/general/guide-change-cyanogenmod-12-lock-screen-t3014524

Also investigating how to easily add home screens.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I might be mixing up terminology. What I meant by that is basically just flash the newest zip of Xposed that's available, which is for 5.1.1
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I don't what happened but starting today I can't send texts. They just keep failing. Any ideas. APN is correct and I have not changed anything.
[Verizon Samsung Galaxy S III] cmjester6421:
any chance this can flash with safestrap on NE1 firm
[Verizon Samsung Galaxy S III] kmoore11:
Nope, no chance. You're stuck with TW only.
[Verizon Samsung Galaxy S III] phonetool:
You are on the stock OS? Last stock upgrade? Then, no. You have a locked bootloader and very limited options. Look for paulpizz or superliterom.
[Verizon Samsung Galaxy S III] cmjester6421:
im on superlight right now and not stock i do have 4.4.2 and yes its a locked bl guess that changes nothing

point blank i want to get to 5.0 idc what rom as long as its 5

and as for paulpizz what would i be looking for i see nothing
[Verizon Samsung Galaxy S III] J913B:
How does this run? I've been on Liquidsmooth for a long time, but that Playservice awake bug is killing my battery. Seems like this is really the only rom left for gs3.
[Verizon Samsung Galaxy S III] phonetool:
The only way that you will get away from 4.4.2 is to get a different phone that has not been upgraded to the locked bootloader level of stock OTA updates. Re-read the superliterom and your safestrap recovery threads. Point blank you are screwed.
[Verizon Samsung Galaxy S III] msolaw:
I'm on the cm stable 10.2.1 after dabbling with slimkat a while until I had wicked random issues on it. Is this worthwhile? GPS and bt work? How's battery life? I'm guessing I should stay put unless this really would be a step up in terms of performance/battery life etc?
[Verizon Samsung Galaxy S III] brandonb0013:
I'm on 6/03, been trying nightlies for a couple weeks. It's very stable. Random people have issues with wifi (very few) a few more people have issues with bt (me included but this build hasn't crashed once) but it's still a very solid ROM. No reboots for me, battery hasn't changed for me from C-Rom 6.3 which was android 4.4.2. My phone has become a lot faster and more reliable on lollipop. Also, front camera actually works!
[Verizon Samsung Galaxy S III] AyUaxe:
6/02 build is butter for me. There are some mild peculiarities with Google play services and store, but that seems to be a gapps issue, not really the rom. I use kk launcher instead of stock trebuchet, dkp kernel with adiutor to tweak. All working well!
[Verizon Samsung Galaxy S III] XdrummerXboy:
Do installs take forever on the play store for you guys too?
[Verizon Samsung Galaxy S III] Master Cylinder:
Had the same problem - seemed like it wasn't dloading at all! I rolled back my Play Store and Play Services to a previous version using TiBu and it works normally. Hopefully a new version will come out soon to fix whatever the problems are.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 06/04

GApps: PA-Micro

MMS/SMS, blutooth, etc. all working well.
[Verizon Samsung Galaxy S III] dvschnk:
I agree. I'm on 6/01...and I'm just so pleasantly surprised how quick development for CM12.1 has gone. It's probably the smoothest and snappiest ROM that i've had on the SG3, especially for a phone that's soon to be 3 years old. For me everything works...the only thing I don't use much of is BT. I haven't had any issues with WIFI, the camera (front and back) works and i'm ecstatic that Xposed is available. So for us stragglers that are unlocked...I say CM12.1 is worth the upgrade.
[Verizon Samsung Galaxy S III] justinnotjason:
Will confirm. I'm on 06/02 and this ROM has breathed new life into a phone I was ready to throw through the wall.

Butter smooth. No WiFi issues (though I don't use it all that much), BT hasn't crashed on me (Pebble always works). Small issues with the ROM like not being able to figure out how to have different wallpaper on lock screen/home screen, and the vibration feels light, but these are very minor.

Never going back :D
[Verizon Samsung Galaxy S III] phonetool:
System settings / themes / menu / lock wallpapers

System settings / sounds / vibrator intensity
[Verizon Samsung Galaxy S III] AyUaxe:
Have not had any issues with slow or stalled app updates.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
The only apps that take a while are Facebook and Messenger but that's because it's installing all of it's bloat.
[Verizon Samsung Galaxy S III] toosurreal01:
Great ROM for the S3. Been flawless for me!
[Verizon Samsung Galaxy S III] Master Cylinder:
The problem with that option to change lockscreen wallpaper is you must use an installed themes wallpaper. You can't choose anything off your phone, unless I've missed something.

However, I've just installed Xposed from here and using my own choice of custom wallpaper with Gravity Box, as well as changing and tweaking other things. Also using CM Settings module that eliminates the status bar hashtag, finally, amongst other things.

Only one should flash the Xposed zip with each new nightly. It forces a rebuild of the run time so to avoid that after initial installation flash them together. There's an APK to install, too, initially.

Running 6/5 and ALL seems well, including dozens of new toys to play with!!:D
[Verizon Samsung Galaxy S III] msolaw:
I was trying to install this, and I've downloaded all the files except gapps. I try to get the arm file and it downloads it... Except it's like a 45k file. And there's no way that's right. Anyone else having this problem?
[Verizon Samsung Galaxy S III] razorloves:
just tried it and it works fine, 81mb zip.

try this direct link to it...

https://github.com/cgapps/vendor_google/blob/builds/arm/gapps-5.1-2015-06-02-15-19.zip?raw=true
[Verizon Samsung Galaxy S III] msolaw:
Loving this ROM! I'm setting up my screens and I've only noticed one problem. My bookmarks are nowhere to be found! I always use the stock browser, and there's always something in the options about being signed in under your account, and I thought also in the accounts settings that bookmark syncing was there... Except I can't find either, and I see no way to sync the bookmarks. Did a settings option just get moved? Am I missing something?