yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ffeingol:
I'm on stock kernel with Bluetooth issues also. Watch works most of the time, but car (Ford sync) rarely works.
[Verizon Samsung Galaxy S III] stevet86:
If my phone is charging and I use bluetooth, the phone resets and there is no data. I'll reboot and it will then optimize all apps again. It looks as if the phone is good until it's charging and bluetooth is on. I'm on 5/14 with clean install.
[Verizon Samsung Galaxy S III] Stealth111:
Me too. It has been working fine for me for months solid. Somewhere along the line in the last few weeks it stopped working with my SYNC as well. Now all I can do is pair it, and it connects, then goes right to saying no phone connected. Did full factory reset on head unit. Tested 3 other phones just fine. Sadly I no longer can use my own....I may have to go back and try the last build from Mastamoon as that was about when it still worked...I still also get occasional reboots shortly after plugging it into charge...not very often though ...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I'm on the 5/15 12.1.1 build. I have a Chevy Cruze and no problems with Bluetooth. Not sure why others are having issues.
[Verizon Samsung Galaxy S III] brandonb0013:
Did you have issues w with BT on other builds?
[Verizon Samsung Galaxy S III] brandonb0013:
When I flashed 5/15 after I was setting things up, and downloaded supersu and titanium backup, it then told me I need Google play services to work. This happened before on a different build but I just reset it and it went away then. I tried that this time and it happened again.

edit: reflashed using banks instead of pa and no issue. whyyyyyyyyy?
[Verizon Samsung Galaxy S III] manfromgta:
Because he's driving a Ford and not a Chevy. Lol. Just kidding. Heh.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[Verizon Samsung Galaxy S III] Stealth111:
Maybe some bluetooth lovin coming: http://review.cyanogenmod.org/#/c/98560/
[Verizon Samsung Galaxy S III] XdrummerXboy:
That would be nice. How "recent" were the changes that messed things up that he referenced? There have been BT issues for a while now
[Verizon Samsung Galaxy S III] unimatrix725:
Could be verification settings

I get nightly notice and click download. I also use philz touch recovery, would be nice if it got picked up again. I am not very fond of TWRP, something about gui.

I would double check the settings before flashing. It could be because there is no md5 file in the directory where the cm update is.

Why CM did not bother to do that is beyond me. Furthermore they should make the app hash check the downloads as well. That would be the first thing I would do, especially with the chance of borking a system. Seems like they are very distracted...
[Verizon Samsung Galaxy S III] Stealth111:
Yeah, I still use Philz as well. There is no way I am going away from it unless I am forced to for some reason.
[Verizon Samsung Galaxy S III] brandonb0013:
... 5/17 had BT crash. I always try to report it after it happens, though I'm not sure it helps. It always looks very much similar to previous ones.
[Verizon Samsung Galaxy S III] kmoore11:
Looking through the commit history (this file, for example), it looks like he reverted the changes made on 4/26. That seems like it's about the same time things started getting screwed up. I'll do a clean flash in the AM, but I'm hopeful!
[Verizon Samsung Galaxy S III] brandonb0013:
If you have luck I'll try again but it didn't work for me. If it does though we might be onto something.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Ok, my touch keys don't work a anymore, so I use an app that requires root to have auto hide on screen nav buttons. Thing is every time I do a nightly and use it, the damn "#" sign pops up in the status area and it doesn't go away. What do I do to remedy this? If I installed SuperSU and used that, instead of the build in SU, would that help? Thanks
[Verizon Samsung Galaxy S III] kmoore11:
Yup, that icon will go away if you use SuperSU.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Thing is I always have to install or update the SuperSU binary after every nightly I install. I always dirty install & wipe the caches when doing nightlies. Is that why I need to always do update binaries over n over?
[Verizon Samsung Galaxy S III] kmoore11:
Yeah the ROM includes the binaries, so every time you flash they're being overwritten. At least that's my interpretation of what's happening. I think there's a flashable SuperSU zip out there somewhere that you could just flash right after each nightly, that might save a little headache.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I have update SuperSU 2.45 zip file, that good or should I be looking for a newer one? If ya know. Ty.
[Verizon Samsung Galaxy S III] ffeingol:
Anyone flash 5/17? Bluetooth better, worse or no charge?
[Verizon Samsung Galaxy S III] Master Cylinder:
So I'm gonna try it with Philz next time just to see it actually working. Love TWRP because of the interface. They both have their advantages but locking the screen with TWRP trumps everything for me. I always feel scared to touch my phone when Philz is active. With TWRP, start a backup and pop it in your back pocket - BAM. It takes 30 minutes to backup these dang ROMs with compression, and I only have 150 apps leading to a 2.4 GB backup!

By the way, I manually generated an md5 file in the cmupdater folder and got the same "Checking for MD5 file...Skipping MD5 check: no MD5 file found" and a fail, but when I install manually immediately after, the md5 file was checked for, found and processed successfully.

If you mean "Optimizing Apps" forever, no, we all have to do that whether you wipe the cache or not (n'est pas?) , except one person [MENTION=5881122]ChrisWNY[/MENTION] on the cyanogenmod thread who said through Philz he had been able to avoid this after install by booting back into recovery and wiping dalvkik/cache. http://forum.cyanogenmod.org/topic/...ences-issues-lessons-learned-etc/#entry518544

If you're talking about auto-installing of all of your apps like after a clean install, then, hmmm....
[Verizon Samsung Galaxy S III] brandonb0013:
I posted earlier, I still had BT issue. Curious if anyone else does.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Ok, thanks. ?
[Verizon Samsung Galaxy S III] thelangosta:
The most recent beta is 2.49. I've used that on two devices and it seems fine. Stable is 2.46.
[Verizon Samsung Galaxy S III] Master Cylinder:
So you're saying that CMUpdater runs the script all the way through? Or do you manually install after download?

I tried using Philz and the cmupdater script would not auto-install. It failed with different errors reporting:

E:unknown volume for path [@/cache/recovery/block.map]

E: can't mount [@/cache/recovery/block.map]

Install aborted.

I guess the cmupdater script, which I can't find, is mounting that location incorrectly.

I mean it's no big hardship to install manually, which I assume everyone's doing already. The CMUpdater update check frequency by default is set to weekly, so if one installs a nightly, they will never even activate an update check if they flash another nightly within a week and don't change the settings.

EDIT: I did some more searching and this seems to be a known bug that's been around off and on for months, so ...
[Verizon Samsung Galaxy S III] Master Cylinder:
WELL! I have run across a tool that I'm surprised I've never heard of before! Cyandelta: http://www.cyandelta.com/

This app analyzes the changes between your currently running build and the newest nightly. It will then download only the data difference (showing you a changelog if desired) and create a patch by which it will then, if selected, automatically reboot into recovery, install patch, and reboot the phone. The total data download as stated on the site is usually no more than 10 MB. I just upgraded to 5/18 and it only needed to download 9 MB worth of data and patched the build, rebooted, voila! (I lit some incense and did a ceremony so that it would not have to "Optimize Apps" but twas no avail...)

It keeps an uncompressed build in it's folder on /sdcard and won't operate with the external sdcard. So, it is keeping a 441 MB uncompressed build file on my phone that one has to allow room for on the internal, plus the first time you set it up, you'll need an extra 250 MB or so (whatever the size of the build zip, to around 750 MB total free) for the original build zip as it converts it, but the original will be deleted after it's unpacked into Cyandelta's folder. That build is constantly updated and current.

Some complained about the use of space on Google Play and their tight internal sdcards, but no one said exactly what was needed, but this is it.

This is pretty cool!
[Verizon Samsung Galaxy S III] mastamoon:
Somebody fix the title, or close/lock this thread and start new! :silly:
[Verizon Samsung Galaxy S III] Master Cylinder:
Time for Original Development Thread

Agreed - it should really be an Official Nightly in the Original Development forum. More likely to be found with the right name in the right place.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Just did an update with cyandelta and it worked fine except for it replaced decimalman's kernel with the stock kernel from the update.
[Verizon Samsung Galaxy S III] brandonb0013:
Any updates on BT? Anything I can do to help? I wanna get this bug squashed!
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Noticing on the 5/18 I'm having trouble sending texts.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 05/18

Working: Bluetooth connecting fine to three different earpieces, MMS/ SMS sent and received, Camera (Open Camera). Boots up just fine - no hung process. I just flashed this, so I'll keep an eye out for any random reboots.
[Verizon Samsung Galaxy S III] brandonb0013:
Did you have BT issues before? Also, it was never right away for me. Usually between 15 minutes and a few hours.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
No. I did not have any previous BT issues before. It finds and then connects within 10-15 seconds.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I've been getting annoyed with A Better Camera Unlocked (always works, just not a fan of how it's configured, ease of use etc), so I was using the stock camera for a day and I had no issues so far, but I see some still not using it, does it still FC & not start at times? Nothing like getting a pic of the kids or something important & the camera doesn't work at all. What's the verdict?
[Verizon Samsung Galaxy S III] brandonb0013:
I think all of us don't have issues with connecting, but randomly it will just shut off Bluetooth and say Bluetooth share has stopped. Then you need to reboot to fix
[Verizon Samsung Galaxy S III] hallstevenson:
Yes, it will do that. It's comparing the original ROM ZIP with the the latest posted one and looks for "what's different".

---------- Post added at 11:32 AM ---------- Previous post was at 11:29 AM ----------

Is it really slow when using the flash as well ? I'm using a different LP ROM and am seeing that (I counted off 6 seconds between hitting the button and it taking the picture !) as well as "Can't connect to camera", which requires rebooting to resolve. I presume this is a Google/AOSP issue, not a ROM one.

I also downloaded the Google Camera from the Play Store and saw the same behavior.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
After tooling around in the settings, I seen where you can have a secondary zip installed automatically for kernels I would imagine
[Verizon Samsung Galaxy S III] NoCrAppleHere:
No, none of that, just don't like how A Better Camera is setup, ease of use. Since LP 5.1 the camera has been great from a regular functionality prospective. Maybe give A Better Camera a try? See that, I'm asking for help and I'm giving it instead, gotta love. Lol
[Verizon Samsung Galaxy S III] mastamoon:
Maybe this will finish up the BT fixing if/when merged. http://review.cyanogenmod.org/#/c/98804/
[Verizon Samsung Galaxy S III] Master Cylinder:
Ah, yes, it looks like it will auto-flash it. Could put a kernal or SuperSU in there, apn fixes, other build mods ...

I don't feel like I have any skins on the wall to open a new thread in Android Original Development for Official Nightlies but I'm thinking about doing it since no one else is stepping up to the plate.
[Verizon Samsung Galaxy S III] mastamoon:
As the OP of an official build, there isn't much to do besides maybe put useful links or known bugs in the OP. Hopefully people wouldn't be looking to the poster for dev stuff.
[Verizon Samsung Galaxy S III] brandonb0013:
I don't seem to have issues with audio, I even have it happen sometimes before I start an audio whatsoever.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
BT: I have not had that happen to met yet. I'll keep an ear out for it and see if I run into the same issue.

Camera: stock camera hasn't FC on me yet.
[Verizon Samsung Galaxy S III] Master Cylinder:
Okay I'll do it. I'll put up the new thread sometime tomorrow. :good:
[Verizon Samsung Galaxy S III] Master Cylinder:
New CM 12.1 Thread Started in Android Original Development

ANNOUNCEMENT

New thread started in Android Original Development titled:	[ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw)

Let's move this thread over where it belongs and where others can find it.

http://xdaforums.com/galaxy-s3-veri...m-cyanogenmod-12-1-nightlies-verizon-t3113037

See ya there!!

:good:

PS - Thanks to [MENTION=2963287]mastamoon[/MENTION], [MENTION=2385005]invisiblek[/MENTION] and [MENTION=4131011]amf66[/MENTION] for keeping us going, and also I copied most of the OP from one of Invisiblek's threads.:o
[Verizon Samsung Galaxy S III] NoCrAppleHere:
OK, I'm on the 4/6 build and all has been good today, I fresh installed it btw. 2 things so far are no matter what I do, Aosp keyboard's swipe typing doesn't work & I turned on rotate the lockscreen feature but no matter what I do, it won't turn off now. Any ideas? I started with the 4/6 build bc from it was reading it was the most stable build.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I've had weird issues with that before, even with mastamoons builds I think.

I don't remember what I changed/did to get better results...
[Verizon Samsung Galaxy S III] MrBrady:
DKP just released an updated 5.1 kernel yesterday. Check it out on his thread.
[Verizon Samsung Galaxy S III] DubleJayJ:
iirc aosp keyboard swipe has always been stupid like that if installed from gapps. Get Google Keyboard, literally the same app
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Thanks. I feel so far like every other setting I adjust it doesn't work. Like, I like to have volumes separate, the setting doesn't work. I try to change the lockscreen to not rotate but it doesn't work. I keep finding a new setting that doesn't work every few hours. Lol.
[Verizon Samsung Galaxy S III] DubleJayJ:
Lockscreen is also rotating for me, even if it's off in settings. Turned off auto-rotate for now.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
What build are you on? I'm curious.
[Verizon Samsung Galaxy S III] DubleJayJ:
Build 4/10
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Okay. I'm on 4/6. I was trying to see if a diff build fixed the issues. Obviously it's still an issue. Thanks.
[Verizon Samsung Galaxy S III] LLStarks:
CM12.1 is running and optimizing faster with /data and /cache as F2FS.

4/11 is solid so far.
[Verizon Samsung Galaxy S III] mastamoon:
FYI,

Tonight's build should have lockscreen rotation toggle fixed.. http://review.cyanogenmod.org/#/c/94397/
[Verizon Samsung Galaxy S III] amf66:
No new build yet. Updated gapps in OP.
[Verizon Samsung Galaxy S III] timedroid:
What are you using to convert to f2fs? I don't see a setting in twrp.
[Verizon Samsung Galaxy S III] LLStarks:
Philz TWRP multiboot: http://xdaforums.com/showthread.php?t=2646538

Why? Because the TWRP devs refuse to update our device tree from 2012 code.

Though, I don't think the multiboot works with f2fs.

Which also begs the question as to why PA gapps doesn't either and does a hard check for ext4.

Euroskank gapps have been wonky regardless of filesystem. Google Now and search give network timeouts. Exchange doesn't work in Gmail either.

Edit: Hopefully our build gets bumped from LMY47I to LMY47O (ayy lmao)
[Verizon Samsung Galaxy S III] MrBrady:
Which Gapps are reliable? I was having connectivity problems with Gapps as well.
[Verizon Samsung Galaxy S III] LLStarks:
The newest PA gapps stock/modular/whatever is a good base to update from

But PA gapps is dead and is becoming increasingly outdated

I'll probably use dhacker's gapps, they're pretty complete
[Verizon Samsung Galaxy S III] mastamoon:
[MENTION=2385005]invisiblek[/MENTION]'s buildbox was derping.. says new build should be up tomorrow.
[Verizon Samsung Galaxy S III] amf66:
To all of those having gapps issues: have you been using the ones I put in the OP? I've been using them for weeks with no problems.
[Verizon Samsung Galaxy S III] LLStarks:
Yes, but euroskank gapps are pretty minimal.

The core problem with pretty much any gapps I've flashed over the past few days is that Now can't be enabled due to network timeouts and the same applies to the search widget.

Doesn't matter how many times I wipe and start from scratch.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Why not delete the app with something along the lines of titanium backup and reinstall from the play store
[Verizon Samsung Galaxy S III] MrBrady:
I've tried that and it doesn't seem to solve the problem. It does seem somehow tied to the Gapps package, even on 4.4.4 ROMs.

It's not just Google Now, Google+ is doing the same thing. I had to revert back to Google+ 4.9 to get it to connect. Since they moved to 5.0 it's had issues.
[Verizon Samsung Galaxy S III] kmoore11:
Wow I'm glad I'm not the only one having these problems. I've been going crazy trying to figure out what's going on. I've tried multiple gapps, 4.3, 4.4, 5.0, 5.1, stock and TW with no luck. Started probably a month ago for me. I was just about to do a full-wipe odin before I saw this.
[Verizon Samsung Galaxy S III] MrBrady:
Google seems to have changed something. If you look at the Play Store reviews it seems like most of the people complaining about connectivity are on S3s.
[Verizon Samsung Galaxy S III] Rushead:
Another good reason to disable "Auto update apps" in Play Store settings.
[Verizon Samsung Galaxy S III] amf66:
New update for 4/15/15! Go get it from the link in OP.

Should have lots of fixes from the past four days.
[Verizon Samsung Galaxy S III] MrBrady:
Exactly! I do the same thing.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
I'm coming from the 4/6 build, the new 4/15 is okay to just dirty dirty or should I follow another procedure? Ty, I just started toying with cm12, was on cm11 for the longest, so I haven't updated anything since my clean install of 4/6. Thanks
[Verizon Samsung Galaxy S III] KaffeDisco:
Dirty dirty

I've been using TWRP's advanced wipe to just wipe system, then flash the ROM + gapps. I don't know if it makes that much difference vs. clean or dirty, but the marginally soiled technique seems to be working okay for me so far.
[Verizon Samsung Galaxy S III] talk2nate:
Can I dirty flash over a march build of moons with this? Or is it better to just clean the slate and reload? Moons build has been so good for me that I don't want to risk messing it up lol
[Verizon Samsung Galaxy S III] dvschnk:
Got a new update to google+ today...fixed my connectivity issues, on version 5.3.0.91034052
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I always do a clean install, but that's just me. :D
[Verizon Samsung Galaxy S III] MrBrady:
Did a clean flash and can't get camera to work at all. Even Open Camera.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Flashlight a no go and after a soft reboot, the option disappeared from the drop-down menu. Anyone else?
[Verizon Samsung Galaxy S III] LLStarks:
Google Search 4.4.11.16 resolved the Now and search issues

Make sure you reload Search or reboot after updating

Edit: Maybe I spoke too soon
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Flashlight working fine on 04/11 and 04/15 build for me. You should be able to add the flashlight panel if it's missing.
[Verizon Samsung Galaxy S III] jbleach:
clean flash of 4/15 with gapps-L-4-16-15 has sent me into a bootloop... Seems to get finished with updating apps and then reboots and does it all over again.

----------------

seems like a gapps issue, possibly due to coming from a different package? but I'm not sure. Tried a few various things included reinstalling the gapps that I was on but no dice. I have retreated back to the relatively safe confines of 12-20150311 build...

-----------------

so apparently not a gapps issue. I was able to flash the 4/11 build with gapps-L-4-9-15.
[Verizon Samsung Galaxy S III] kmoore11:
Google+ is working for me with the update, but Search and Now are still having connectivity issues.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm getting this on a dirty flash over 4/11. Did not flash any GApps. Have thought I had created a problem by installing Philz TWRP Multiboot which would turn off the phone in the middle of a backup. Then flashed 2.8.6.0 and had the same problem (Got to learn to read instructions! Have to come from 2.8.4.0 to go to 2.8.6.0. Philz is 2.8.3.0.) But, put 2.8.4.0 on and all seemed normal, until trying to install 4/15. Can backup and restore normally. Was about to try installing an earlier build to see if I borked it but it may be something else ....

I like a challenge (and I got too much time on my hands) so I'm gonna keep bangin' away at it. (Insert animated emoji banging his head against a wall here.)
[Verizon Samsung Galaxy S III] kmoore11:
Just a heads up, A Better Camera Unlocked is free on Amazon App Store today. Somebody else here recommended it, and I've been using it without any issues for pictures and video.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I went to get it and it was not there for me
[Verizon Samsung Galaxy S III] kmoore11:
Interesting. It's still there for me, under their $105 in free apps/games deal they have going on. Also still showing up as free here: http://www.amazon.com/Almalence-Inc-Better-Camera-Unlocked/dp/B00HUP8UZA/
[Verizon Samsung Galaxy S III] Master Cylinder:
Thanks man - that's awesome! I have been using it for quite awhile so this is great. It's a great app with tons of features.

Here's a QR code:
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Guys, any issue sharing videos? I can take them fine, but when I share to Facebook, the video goes to a green screen but full audio is there. Doesn't matter the video length, as I've tried different lengths.
[Verizon Samsung Galaxy S III] mastamoon:
pull a set of logs after this happens.. probably something stupid like selinux denial.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Sounds good, sorry, but how do I do that again? I'm not a noob, but idr how to pull a log. Lol. Thanks.
[Verizon Samsung Galaxy S III] mastamoon:
Download syslog from the market, easiest way.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Ty, kind sir. Post the log here after, just making sure.
[Verizon Samsung Galaxy S III] mastamoon:
you can email it to me if you want at my user name here [MENTION=5499064]gmail.com[/MENTION] or post it.. you can use the 'scrubber' in the app to remove any personally identifying information.
[Verizon Samsung Galaxy S III] Master Cylinder:
Never have gotten 4/15 to boot :~/ patiently waiting for next build...:eek:
[Verizon Samsung Galaxy S III] Stealth111:
As well. Gotta feed my crack flash addiction..
[Verizon Samsung Galaxy S III] kmoore11:
4/15 has been excellent for me, best flash I've had in a long time. Had one random reboot early on and the battery level was "stuck" at 15% while charging last night, but a reboot fixed that. I flashed Euro's 4-9 gapps, Search and Now are still having problems, but Google+ and Photos are working again after updating.
[Verizon Samsung Galaxy S III] NoCrAppleHere:
Hey, I sent you an email w/ the syslog. Just wanted you to know in case it went to spam. I titled it "Hey, NoCrAppleHere from XDA" etc. Thank you. :)