yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Aw, yeah. Official thread is a go!

Thanks for maintaining our trusty ol' S3, nardholio. This ROM runs even better than CM11 did on my phone.

I'll throw in a quick bug report, though. In all of these builds (including the unofficial ones) YouTube videos tend to freeze briefly about 8-10 seconds in. This happens with every video when viewed in the YouTube app, regardless of resolution or quality. I haven't noticed it happening with videos using the YouTube API in other apps such as Relay for Reddit.

That's pretty much the only issue I've ever had with these builds. They're pretty fantastic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Hello guys,

Just a little update regarding the bluetooth issues. I did a clean flash, and it made it somehow better but not perfect. Now, as long as the screen is on or if there is something streaming, everything works well. But, if the phone screen is off, the bluetooth commands stop working (play, next...)...and they work fine if I turn the screen back on. Same goes for the auto connect, it does work when the screen is on, but won't connect if it isn't.

What I think is that the way lollipop acts when the phone is standby simply prevents the bluetooth app from updating it's status or recieving inbound commands. Now, the thing is that it used to work fine in previous builds (amf66 before 4/28 if I remember correctly), and that would mean that some setting was changed, probably in the CM source.

Once again, good job on maintaining our old devices, it really is appreciated.

And..no pressure here, just something I think would be worth looking into.

Dom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Try turning off ambient display for your Bluetooth issues. I'm thinking of permanently disabling it for the S3 anyway as it eats battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Tried it this morning, you are on the right track. Once connected, commands now work (phone, play/payse, next etc) even if the screen is off. But, I still have to connect it from the phone, and if the bluetooth device is turned off, it won't reconnect.

Thanks for the support! Are there any other functions that might prevent the phone from scanning for bluetooth devices?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Running the 5/4 nightly. Did the cleanest install possible - formatted through TWRP everthing on the phone, installed the ROM and gApps, then let the play store install all my apps. Everyting is running well for almost 4 hours now. Not a single reboot. Bluetooth has worked for several calls.

Issues I have noticed are -

1. Audio throug the car dock is broken. Once again, as has happened numerous times in the past on Cyanogen, the audio is not being routed through the dock with the phone is docked. I really hope this one gets fixed. Much of my phones use is inthe dock in the car.

2. Although the phone initially bootted with LTE working, it eventiually lost it. As has been noted elsewhere, removing all the other APNs and only leaving the one required for your particular provider fixes this.

3. Was getting pretty bad battery drain about 5-7% per hour at idle. Turned out that fixing the LTE issue as noted in #2 also fixed this issue. Somewhat surprising since the phone is almost always on Wi-Fi anyway. FWIW, I did not have wakelocks from Google Play. Battery concumption over the last hour of idle is only .9% per hour as reported by BBS.

So now, really only issue #1 remains!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Which BBS version do you have working with android 5.1.1? I've tried a few of the betas with mixed results, but mostly FC's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I used the latest BBS, 2.1b3 I believe. Also had to flash the helper app, then install BBS again. In the end, it does work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Is it still recommended that we deny Google Play Services' Wake Up and Keep Awake permissions in Privacy Guard? I had them denied when I was rocking the earlier unofficial builds, but I have had them unblocked as of late. I didn't notice any difference at first, but not Google Play Services is my top battery drainer again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I notice that I had the contacts repeated. Only one of the contacts had information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
does it works on the sgh-i747m ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
I have the same issue with my pebble. It happens when you go out of range of any BT device you are paired with. You can avoid a reboot by force closing Bluetooth Share (which I think is the culprit) in you Apps menu, then reconnect with your watch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
MaxxAudio

Has anyone tried MaxxAudio by Soralz on this ROM or is it only for OPO?

-CM12 5.0+ / CM12.1 5.1 Optimized Another new test build V4 pulled out from CM12S libraries (Works system wide).

*Credits to [MENTION=3115338]smoki3[/MENTION]

http://xdaforums.com/oneplus-one/themes-apps/app-05q-maxxaudio-lib-t3026967

Just wondering if it may be possible?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I wonder how MaxxAudio compares to Viper4Android which sounds super amazing on my device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
Pebble connection worked back in 4/22

I have similar issues with my Pebble. The unofficial build from MatrixZone on 4/22 is what I use and it's the last one which worked with my Pebble. Since getting my Pebble on Kickstarter I can't abide a ringing phone or having to go get it just to read a txt. As a result, I stick with the older version, which is mostly fantastic aside from occasionally dropping network data connection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Reboot while on XDA posting about how smoothly 5/19 was running. Browser was Chrome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Installed the 5/19 nightly first thing this morning. Still no audio through the dock. I guess there are still some additional changes needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outlogic:
5/15 Nightly

Frequent reboots especially while charging from PC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
Not sure if it's legit to post about random reboots when I'm still using the 05/06 nightly, but I had another one while plugged in just a moment ago.

Playing music and charging still seem to be the only two triggers for reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
How long do you have to leave it plugged into the computer before it reboots? I'm on 05/18 and I'll test. Also, are you on at&t s3 or a different variant?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outlogic:
It reboots within 10-30 minutes multiple times. I'm on at&t s3 (i747).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
That would probably be accurate for me too. Not *every* time I plug it in, mind you. But when it happens, it's typically not long after plugging it in. This last time, it didn't charge more than 2% before I heard it reboot.

I'm on the standard AT&T S3 as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
I'm on the 5/17 nightly and I have had *knock on wood* no random reboots, and only 1 since I started using cm 12.1

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
i'm on the 5/19 and yes it reboots when connectede to pc only ... but sometimes it doesn't reboot ... i'm on the sgh-i747m.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Najuto9tail:
Mine random reeboots 3 or 4 times a day without using it much. I only hear it on the table going off and on again... Latest nightly...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
Syslog attached

Here's syslog form 5/18 nightly. Bluetooth not maintaining connection to Pebble. https://www.dropbox.com/s/57joyud82jvwo3x/2015-05-19_15.10.zip?dl=0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Reboots are still being looked into. The cause is known, coding around it is a bit difficult.

Bluetooth issues on CM 12.1 are not just on d2. Someone even made an app https://play.google.com/store/apps/details?id=co.loudbit.ao_shi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I'm on the 5/19 build and no reboots so far for a heavy user like me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Have you connected your phone to a PC?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Yup, used the PC for transferring huge files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
Another reboot while using Play Music tonight. SysLog lost its mind while trying to gather a log the first time, so I hope this second one is still useful. Actual reboot was about 17 minutes sooner than the time stamp suggests.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
i have questions for u

Ur front camera in candy camera and retrica work or not and the rom work good or not i have sgh-i747m and thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
On the 5/19 build Theme Chooser, if used to change anything, will start to lag when scrolling, continue to run in the background, make the phone run hot(37 C°) and take up significant resources.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
syslog after reboot on 4/19

https://www.dropbox.com/s/settmcbr0auzy0e/2015-05-20_10.29.zip?dl=0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
front camera doesn't work with retrica and candycam it make the phone reboot ... the rom work fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Use the stock camera, any other camera apps might not be upgraded. Try also open camera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
Looks like a whole host of changes in 05/21. In particular, http://review.cyanogenmod.org/#/c/98801/ looks interesting. Kind of looks like the in-call volume bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
That commit has already been reverted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Are you sitting of in call volume in general or with speakerphone? That bug looks to deal with ringtone volume.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
Yeah, it's ringer-specific, but I thought the failure method sounded similar though (volume getting stuck at 0 or 1 until reset by turning the volume up or down). If they fixed the ringer, I thought in-call volume might not be far behind.

Alas...reverted. That'll teach me to read to the bottom of the commit page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I just notice a bug in the calculator, if you sum several numbers that are more than the screen. You can't see the numbers that you type only the result that change. Just type 45+45 several times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I realized that my speakerphone volume is stuck, but normal speaker is not. UNTIL I install a program called silence. It apparently doesn't work with lollipop and now my in call volume has to be adjusted all the way up and then down. So you might be having a problem with an incompatible app.

I wonder if there is a way to get it working again without a clean flash. Because uninstalling the program didn't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Which nightly and which s3 model?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I notice that in the last three nightlies and I had a ATT i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingHaye:
is there any chance the battery life for these Nightlies might get any better? maybe not but am hoping so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
Install better battery stats from play store or the xda thread and see what is making your battery life poor. When I ran the 03/15 nightly it wasn't much worse than KitKat.

Sent from my Samsung Galaxy S III using the XDA premium app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Traevore:
The last few nightlies have been terrible for my battery life, yet nothing stands out in better battery stats. It was good a few nightlies ago though, I'll try to track down when it went downhill.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Nightly 21 was great in sleep using 0.6%. Will see how regular usage influences the battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I moved to 21 last night, I'll see today what all works and how battery is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
5/21 no longer rebooting when connected to pc :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Now we just need the Bluetooth sorted out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
AT&T S3. Nightly 5/23. App drawer page scrolling still very laggy/juddery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
this had to do with the trebuchet launcher that cyanogen use. Switch to nova and there is no lag at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Does anyone else have issues with google keyboard giving random suggestions in the autocorrect bar?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I don't know about random, but it seems like more often than not, the word I want is not one of the suggestions.

Of course, as I type this, it's doing a pretty good job. Who knows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pradyu09:
Can dirtyflash

Cyanogen calls it updating
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
Thanks. Working fine now.

Imo the Google keyboard has always had poor suggestions. Give SwiftKey a go. I set mine to always have numbers on top and space inserts a space, and I'm golden. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Just got a random reboot.

Will upload last_kmsg to drive and link later.

Trying again.

https://drive.google.com/folder/d/0B23aWUqcJkwxWGxYUFVBQ2RFWGc/edit

[MENTION=2044079]Nardholio[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Issues with can't connect to camera

https://docs.google.com/file/d/0B7u_Do3wdBUTZHRBOENzcDNCd0E/edit?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
I've had that problem before, try rebooting, fixed mine.

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Has anyone experienced bootlooping in the Android is starting window after updating the rom? I experienced it yesterday when updating from 5/21 to 5/23. 186 out of 186 apps have finished optimizing and then it rebooted. After it rebooted it optimized my apps again from 1 to 186.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ngotan9:
Earphone not work in buid 23/05 with my phone, help..how to fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Nope, it seems to load and then crashes. I took many videos yesterday before it crashed, and hasn't resumed working.

https://docs.google.com/file/d/0B7u_Do3wdBUTQ1JDNldzTnlCN0U/edit?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I had a Chromecast and I can't use the Cast screen option build in the ROM, does that option is working?

I can cast the screen from Chrome cast app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
I've not had cast screen work in either KK or CM 12.1.

Sent from my SGSIII using the XDA premium app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Sometimes ROMs with built in screen casting will either not detect your Chromecast or they'll disconnect immediately. If you see that, try the mirrorenabler app. I've had mixed results with it on lollipop roms, but sometimes it works.

http://xdaforums.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Working in the 5/24 build. I did not run the 5/23 build, so cannot comment on it directly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
Happened to me also. I had to pull the battery, factory reset in TWRP, then reinstalled the full rom.

To add to that, how do I take screenshots with this rom? I tried holding power and home like I did with stock KitKat, but all that did was pull up the power menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
In setting, buttons, power menu you need to select screenshot. Then you only press power and then screenshot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LambdaStrider:
Power + volume down works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
I haven't had any trouble with casting to a Samsung TV with this LP ROM. I can't speak for KK. I'm currently using the 05/21 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodflood:
Hello,

Me too... shows no MD5 file found and in red font: Zip file is corrupt [for CM 12.1 dated 25]

Will try CM 12.1 dated 24 after downloading on PC and checking hash.

Factory reset will wipe data, right? Will prepare in that case : )

Any other suggestions?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
1. Is it possible to show the actual number of contacts you have on your phone or at least in each account?

2. In KitKat, it was easy to see exactly how long your phone has been running using the battery menu/app. Lollipop's battery app seems to omit that very helpful information. Yes, you can "approximate" run time by looking at the usage graph but that does not give you an exact reading down to the minute. Although helpful, I am not as interested in how much time my battery has left. Is there a better/easier way to get an exact run time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
if you are using the the built-in cmupdater with twrp recovery and you get that message you speak of (see attached screenshot) ..

and you have safely done a nandroid backup just before allowing cmupdater to run ..

then you can safely do the following in twrp immediately after you see that error

tap Install

choose the zip sdcard/cmupdater/cm-12.1-yyyymmdd-NIGHTLY-d2att.zip

slide to flash

do NOT wipe dalvik & cache

do NOT flash gapps

reboot system

the main point is that cmupdater initiates the addon.d backup/restore scripts via twrp so that your gapps, supersu, etc get backed up .. the zip wipes the system partition and installs the new system image ... then your gapps, supersu, etc get restored ... and then ALL apps get re-compiled during the reboot

cheers

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodflood:
cLogic,

Wow... who knew... at least not me! Thanks for the info!

My current status, before doing a Q&A on XDA...

​

I applied the update using Cmupdater got the error. rebooted. tried again, this time on error, wiped dalvik and cache. Tried again, same error!​

At this point, can I safely follow the steps you have outlined?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
here's a little exercise for you

look at the screenshot ... notice how there is this:

Running boot script ... followed by Finished running boot script ... you should see that each time you boot into twrp

then there is this:

Processing AOSP recovery commands...

and then there is Installing ... yada yada

the AOSP recovery commands were CMupdater telling twrp to:

run addon.d in backup mode

copy addon.d files somewhere

install the nightly zip

copy addon.d files back

run addon.d in restore mode

twrp ran 1, 2 and 3 ... then stopped because the install of the zip failed

but it is simply waiting ...

when you reboot (end twrp) it will continue with 4 and 5

so if you manually install the zip at this point ... the zip will do a full flash as if there is no rom

when you reboot, twrp finishes the aosp commands 4 and 5 :good:

so ... if you are understanding how cmupdater works with twrp ... then you can see that as long as you used cmupdater (Settings> About phone> CyanogenMod updates> tap on available update with mobile device icon) to initiate twrp ... then this procedure works

if you manually reboot into twrp and then tap Install and flash the zip, then the addon.d process was not initiated and flashing the zip would wipe the system partition and there would be no gapps, supersu, cerberus, etc

see?

---------- Post added at 11:17 AM ---------- Previous post was at 11:03 AM ----------

note that My previous post was a simplification, lol ...

in actuality the backuptool stuff is inside the zip

open the zip with something like ES File Explorer ... it is in install/bin/backuptool.sh

the actual updater script is in META-INF/com/google/android/updater-script

you can see how the script extracts the install folder, and then runs backuptool.sh backup

and then near the end of the script it runs backuptool,sh restore

so technically ... everytime you flash a cm zip, it WILL run addon.d scripts and maintain your gapps, etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Better battery stats for 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I got that when trying to let CM do the update, but it flashed fine manually in twrp.

---------- Post added at 01:39 PM ---------- Previous post was at 12:52 PM ----------

Every update I've done before the 5/25 nightly I gave just booted to twrp, flash the zip and wipe dalvik/cache. So yeah, no problem updating that way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
what is the best cpu governor and I/O sheduler for this rom ?:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AriaOfSorrow:
I'm on 4.4.4 and my modem is LK3. Can/should I upgrade to MJB before I do anything else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bluntneedle:
Yes first to MJB (reboot) then to NE4 (reboot) and then to NJ1. Please make sure that Modem and Bootloader versions match.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
Play Store stopped working for me after installing Nightly 5/26. Gives message "Unfortunately, Google Play Store has stopped."

Tried all of the usual methods to get it working. Clear data and cache in Apps, reboot, uninstall and reinstall the Play Store apk, etc. Nothing is working. Was browsing the store JUST before checking for & installing the Nightly update.

Edit: Just to be sure it was the update that caused it, I re-flashed 5/25 & Play Store worked. Updated to 5/26 and it quit working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
The is no single answer. Depends on your usage and objectives. There is a great thread on the subject which I recommend. http://xdaforums.com/showthread.php?t=3048957
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Did you try flashing the latest banks gapps? That worked for me on an earlier build. Right now I'm on 5/25. Haven't moved to last night's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bklyndiaz:
gapps link?

Can you post the link for Banks Gapps? Thanks

---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------

Ok, found the link here http://xdaforums.com/android/software/gapps-consolidated-gapps-thread-t3064693
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
Thanks, that fixed it. Curious as to why the update borked it in the first place though, and why re-flashing CM's own 12.1 gapps didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
The YouTube freeze has been eliminated in the latest build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Glad to hear it. I don't think the CM ones are the fully latest. Banks keeps his with all the latest libs and frameworks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Oh, cool. Looks like my only niggling issue with the nightlies has been resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KAUSHDROID:
Its nice