yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] iwearthebelt:
Been running it for about 6 hours now, had 1 random reboot. Other than that its been ok.
[Verizon Samsung Galaxy S III] YabbyYou:
Oh man the download page looks nuts for April Fools! https://download.cyanogenmod.org/?device=d2vzw&type=nightly

hahahaha "Site Created with with Notepad" :laugh:
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:

That's hilarious! It's on fire! I think they should leave it like that. :p

---------- Post added at 11:18 AM ---------- Previous post was at 11:15 AM ----------

It also has a "Netscape 3.0" button on there. Been years!
[Verizon Samsung Galaxy S III] YabbyYou:
Hello everyone, I installed the 4/2/2016 build. No change on the bluetooth audio problem, still not working. Front facing camera still not fully working, takes low light pics. I haven't hit any other problems yet but I just completed the install a little while ago. I will report back if I run into anything.
[Verizon Samsung Galaxy S III] Fenix2002:
Occasionally on boot, I get a message that the Live Lock Screen service has crashed. Other wise stable.
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, me too, but I am running the AICP version, which is based on this one. 4/2 on it might be 4/1 on this one. I flashed it today and I've got an effing rats nest of, well, rats. Turned my phone into a mass producing bug machine. Gonna post over there, though I think I'm the only Verizon S3 in the country that is using it ... Can't believe the device maintainer is keeping it going!
[Verizon Samsung Galaxy S III] Fenix2002:
Jaws uses AICP, also. I flash it occasionally to test it for fun.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Master Cylinder, you know the only time recently I've flashed a build and had a rats nest of rats was when I mistakenly booted without flashing gapps. It was a crashing nightmare, but once I managed to get the phone booted back into TWRP, I reflashed the rom and gapps and it was OK. Could you have a similar issue? My other idea was maybe a bad rom download, did you check the sha1?
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah but I think he only uses 5.1. Gotta have that front camera, right Jaws? Actually, I use the back camera for selfies - set up the camera to shoot with the volume button and boom! Pop off 3 or 4 of them right quick. MUCH higher resolution, so if your subject(s) aren't exactly centered, then you can frame it however you want and snap a screenshot. Easy peasy :p
[Verizon Samsung Galaxy S III] Fenix2002:
Oh. I thought he was on AICP MM now. He goes back and forth. He and I both mainly wanted the front camera for video chatting. It still wouldn't work for vid-chat on my app of choice, so I came back to MM, but I know it works OK on Hangouts. I also use the back cam like you for selfies usually.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh, yeah, I didn't think about the video calls. I usually don't want people to see me - I mean look at that picture below! I'm usually having a bad hair day. :(
[Verizon Samsung Galaxy S III] YabbyYou:
Some additional comments on the 4/2 build. I noticed the lock screen is being a little weird. Sometimes the lock icon doesn't appear (even though you can swipe up to enter your pin/pattern). Sometimes, the lock icons appear after the phone is unlocked, but they appear under the launcher icons. I've noticed a few bug reports about this on the CM jira site, so hopefully it's just a minor thing that gets fixed soon.
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, I saw the same thing, though my phone went psycho. Mine's definitely a different ROM, though it has the same base. It has a lot more built in features but is significantly smaller in size, strangely enough. Still, because of a couple of things I still use X.
[Verizon Samsung Galaxy S III] Jaws4God:
LOL.. yeah i sure do.. :good::D had a freaking huge scare today.. recently i've realized my phone has been taking too much of my attention away from people.. so I

"simplified"

it.. went to MIUI 7 (4.4.4) and was on that for a few days.. battery life was amazing and i've always been a fan of the IOS style launcher and fun animations... stock apps worked fairly well as well.. had a few bugs here and there.. but then this morning i had

no cell service

.. flashed to CM12.1 and no luck.. did a full restore back to stock and unrooted, no luck.. so called Total Wireless.. they ran me through several reboots but finally a factory reset did the trick.. of course i could NOT stay on Touchwiz 4.1 (clumbsy, slow, irritating, missing key features, bloated, etc) so already rooted and on OctOs (L) for now since they seem to be a great team and hoping its stable.. *whew*

as far as the front camera, I mainly wanted it to work for SmartLock Face Unlock.. I love that feature. I also do take occasional selfies with the kids and makes it much easier to see the screen (and keeps their attention).. LOL.

I'm not sure if I'll be back on MM since it seems to be so glitchy and issues with camera.. I may visit this forum from time to time via the computer... but to help keep my phone simple.. not having tapatalk to risk me having to check it constantly.. LOL

I may consider going back to MM or if you all do go to N .. so help keep me in the stability loop ya'll!

Thanks for everything.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Jaws, I totally understand the desire for some stability with your S3, but I gotta say, these nightly builds have really been working great. I know we have some issues, but for the most part the phone is nice and stable. You should hang on a nice release with us and just check in every few days to get an update on the build.

I've been reading up on Project Fi, which sounds pretty good. I just don't know if I'm ready to jump ship yet. Although, every month I look at my vzw bill and I start to consider making the jump again.

Anyways I see a commit that's Bluetooth related scheduled for the next build but I don't think it's anything significant.
[Verizon Samsung Galaxy S III] Fenix2002:
You're right. The last few have been buggier than usual, but I think it was the 3/31 build that was near rock solid, minus camera and Bluetooth.

I've read up on Project Fi also, and from what I've read it's just not ready for primetime, especially if you don't live in an urban area, like me. Some people love it, most reviews seem to agree that it's not quite there yet though. Dropped calls, bad service, weird bugs. The pricing plan is NIIICE though.

I'm not sure what your vzw plan is like, but you could check into Straight Talk. They have BYOD, and an I535 should get 4G, where the S968C doesn't. They have a new 10GB LTE/unlimited 2G plan for $55 now. I pay $43 for 5GB of LTE/unlimited 2G, except I don't get LTE with my S968C.
[Verizon Samsung Galaxy S III] YabbyYou:
I'm still holding onto an unlimited data plan! I'll look into Straight Talk.
[Verizon Samsung Galaxy S III] Jaws4God:
thanks for the comments . :) i probably will try a newer build soon.. but the camera and screen touch issues are still show stoppers.. lol

we went with Total Wireless due to price.. $62 for wife and I to have unlimited talk / text and share 5gig 3g.

but i do love to flash and try new things.. right npw hunting for simple and battery friendly.. suggestions?
[Verizon Samsung Galaxy S III] phonetool:
And here I thought I was the only one left with the OG plan!
[Verizon Samsung Galaxy S III] YabbyYou:
Hey phonetool, there are less and less of us everyday, exactly what vzw wants! That last $20 price hike really annoyed me, plus I have been reading there is some other change coming soon for us unlimited people, I don't know what it is but I doubt we're going to like it. In light of all this I'm always weighing my alternatives. I have a coworker who switched to tmobile about two years ago, he says it's been working great for him. He mentioned a few areas where he has some signal problems but he says all of the places he spends most of his time have coverage. Granted I'm in the northern NJ/NYC/lower Hudson Valley area, so coverage may be a little better here then some other places. He loves his 6P.

Back on topic, did anyone install the 4/6 build yet, I'm curious if that one Bluetooth commit has any effect on our bt situation.
[Verizon Samsung Galaxy S III] Fenix2002:
Go forward to 4/6? I got fed up with lock screen and overlay issues in a few apps (messaging is one) and went *back* to 3/31 for now. I was having an issue where old text messages were showing on top of new ones, making everything a big jumbled mess. Let me know if 4/6 fixed any of those issues!
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey [MENTION=4602329]phonetool[/MENTION], there you are!

I didn't think ANYONE still had the Unlimited. Have to say, over on the AICP thread, I'm pretty sure I'm talking to myself.

They been sayin' that for years on the Unlimited. Or should I say Unlimited users have been passing around rumors for the entire age of my phone (see below,) that any day it's gonna get pulled.

However, on VZW in Albuquerque I'm surprised at the major busy retail areas where I can't get squat on data! I may look into a couple of these alternatives now that y'all mentioned it.

Ha! I wasn't the only one with a bug factory. ;P

I'm on AICP 4/1, which is probably 3/31 on CM, but am thinking about putting a 12.1 back on to see about the dictation quality. I dictate a hell of a lot - voice to text, and since MM came out it has been quite buggy and unreliable at times, now being one of them. Once they get one bug fixed, another pops up. You should see some of the hilarious crap that gets typed in sometimes! However, startin' to not be funny anymore. I really want it to work! Or, pay a few hundred $ to get a dedicated portable machine ...

The frustration level has me scouring eBay as we speak (type ...) (This is from one of my computers, with Windows 10 on it and "Cortana" which is claiming can do anything from you speech including iron and fold your shirts! So it's about time to see if IT can type my voice.)
[Verizon Samsung Galaxy S III] phonetool:
Is there a forum section for carrier/plan? I just looked and all I find is phone phone phone.

Good old Howard Forums used to have sections like that.

I was gonna start a thread for the unlimited plan die hards.
[Verizon Samsung Galaxy S III] YabbyYou:
Haha! What the heck would we talk about? It would turn into a huge *****-fest about how expensive it's getting! Then trolls would come in and tell us to leave Verizon, blah blah blah.... I already have a headache just thinking about it. :p
[Verizon Samsung Galaxy S III] YabbyYou:
It looks like [MENTION=2044079]Nardholio[/MENTION] has another pending commit that's related to Bluetooth waiting for some code review. I hope this gets merged and then pulled into our nightly build to see if it helps with our Bluetooth issue.

This is the code review entry: http://review.cyanogenmod.org/#/c/137321/

There is also the older one, which hasn't seen any activity but would also be great if it were merged and/or worked on: http://review.cyanogenmod.org/#/c/136368/
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh:

Oh man! This is so true!! And it was 3 years ago when I started this little journey.

---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------

The good news is that there are so few of you left that I ain't heard it in awhile. :p
[Verizon Samsung Galaxy S III] Jaws4God:
Thank you for the update and encouragement...:good: hope it is a fix!. :laugh: then maybe *cough* front camera *cough cough* could get addressed... ;) lol
[Verizon Samsung Galaxy S III] YabbyYou:
Yeah, it seems the front camera issue is right there, since it works in low light. Such a weird bug.

Personally, I can deal with the broken front facing cam, but I'm having a hard time dealing with the lack of tunes through my bluetooth speaker/headphones! :eek:
[Verizon Samsung Galaxy S III] YabbyYou:
Looks like the next build includes some code to maybe fix these weird lock screen issues, we'll see.

http://review.cyanogenmod.org/#/c/139877/
[Verizon Samsung Galaxy S III] Master Cylinder:
I would think this could be a deal-breaker for a lot of people, especially if you have bluetooth built into your car.

Flashing latest AICP 4/8. Not sure if it's based on 4/8 or 4/6 yet of CM. Same bugs, etc... No one to talk to over there, though. :(
[Verizon Samsung Galaxy S III] YabbyYou:
I flashed the 4/8 build. Front facing cam still not working, bluetooth also not working (boo!). It looks like the lock screen weirdness may be resolved though.
[Verizon Samsung Galaxy S III] LLForbie:
I am on Android 4.4.2

Baseband I535OYUDNE1

Can I flash the linked MF1/NE1 zip?
[Verizon Samsung Galaxy S III] Master Cylinder:
If you do it will crap out your phone.

You can look at firmware/bootloader downgrade threads, 2 of them I think, on the "Development" thread, minus the Original in this subforum for our phone. Whether or not you can flash a ROM like this afterwards is something you'll have to check with folks in those threads. But, you can't flash this firmware you mentioned after either, or you'll get a permanent brick.

---------- Post added at 09:30 PM ---------- Previous post was at 09:26 PM ----------

At the moment my lockscreen swipe to unlock seems hit or miss. I frequently have to swipe 2 or 3 times to unlock it. Anybody seeing this? Haven't seen this before myself.
[Verizon Samsung Galaxy S III] YabbyYou:
I'm not seeing that behavior at the moment but I'll pay attention and see if I run into this. I did see people commenting about that issue on the CM bug tracker, so the problem is out there.
[Verizon Samsung Galaxy S III] Deliquified:
Most people use aux if I had to guess.. You get a decent audio quality degradation over Bluetooth
[Verizon Samsung Galaxy S III] Fenix2002:
I do. Good sound quality, no issue over BT crapping out and having to sync. It has drawbacks though.. A wire hanging out in your car, primarily.

The biggest complaint I have right now concerning aux is that you can still use hands-free but sometimes it confuses a normal aux for an inline mic aux and won't pick up my voice. CM12.1/AICP LP had it working flawlessly at the end.
[Verizon Samsung Galaxy S III] adobeman:
Aux in car and Chromecast audio in home (which is insanely good). BT audio has always been choppy/stuttery on any ROM I've ever had on my 535.
[Verizon Samsung Galaxy S III] Roger W:
Several months ago, I switched to using my car's built-in SD card reader for music instead of phone BT. It's not an option for everyone and I liked the convenience of keeping everything in one place (plus I recognize that a lot of people want to listen to something besides static music files). But I did it when I did some digging into BT audio quality and found that several years ago, Android lost support for sending direct MP3 bitstreams to the receiver without recompressing. Now it all gets converted to SBC on the fly, which sounds noticeably worse than the source and also burns more battery.

Incidentally, have others here had annoyances getting the phone to simply auto-play music in the car consistently? Seems like there have been a big set of bugs over time that lead it to not fire up the audio player when BT connects. The best part about not using the phone for audio is not having to take 20 seconds every time I start the car, just to get music playing manually.
[Verizon Samsung Galaxy S III] Fenix2002:
Flashed the 4/9 build, and it seemed like some of the lockscreen issues went away -- except that alarms, timers, and anything that would normally pop-up over the lockscreen showed up under the lockscreen. Not terrible, but inconvenient. I also started get acore crashes. I flashed back to 3/31 (the last mostly working build I had) and still getting the acore crashes.
[Verizon Samsung Galaxy S III] YabbyYou:
Well, the commit I was hoping might fix our Bluetooth issue is scheduled to be included in the next nightly. However, the comments on the code review site don't sound very optimistic, so I have a feeling this isn't going to be fixed yet. I'll try to get the next nightly installed as soon as possible. Fingers crossed.
[Verizon Samsung Galaxy S III] vforaci:
Running 4/9 and gapps FULL. Other than the already posted, front camera, bluetooth audio not working. I'm noticing android keyboard sucking up battery. Going to try apps stock and see what that brings. Which gapps does everyone recommend?

Weird thing was I couldn't install the google keyboard to replace the android ASOP one. This was my logic for installing the stock gapps package.

I'm new to CM13 since it's my daily, the first build I tried was 4/4 and other than the mentioned above issue and lock screen the battery life seemed good.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey vforaci, welcome to the forum. Glad to hear you had a successful first flash of CM13. I'm running the gapps mini install, that's been working well for me. I use SwiftKey as my keyboard.

My battery life was sucking on this 4/8 build. I narrowed it down to the mediaserver service (as always right?). After trying all kinds of tricks to tame it, I found that clearing the image cache in Quickpic and forcing it to only scan a few directories that I keep pics in solved it. So far the battery life has been acceptable, I'll see what happens.
[Verizon Samsung Galaxy S III] AyUaxe:
Been on 4/2 since 4/2. Clean clean flash from last cm12.1. Decent battery, stability, etc. SOSO front camera in anything brighter than a night light and no BT audio. BT file transfer works, but very slow. YMMV, as this little d2 that could is no longer activated on vzw. Just using it on WiFi as media device. Also using dkp kernel and base Delta gapps. Found I could overclock about 3 steps above previous Max 1792, but there was a little instability, so dropped back to 1792 and all good.
[Verizon Samsung Galaxy S III] YabbyYou:
Hey AyUaxe, you're still able to run the dkp kernel with some decent stability? I had to give up on it a few builds back, I just couldn't get the phone to behave. Maybe I'll give it another try, is there a particular build date of dkp you are running?
[Verizon Samsung Galaxy S III] bigbaluka:
New Weather Settings in Settings?

Just curious if anyone knows anything about this? I found a little talk in forums about it. I'm not a developer so Gerrit Review didn't mean much to me.

http://forum.cyanogenmod.org/topic/123591-weather-provider-service/

http://www.teamsuperluminal.org/forums/topic/cm-13-0-20160402-new-weather-settings-menu/

http://review.cyanogenmod.org/#/c/137481/
[Verizon Samsung Galaxy S III] Fenix2002:
I noticed it, but haven't figured anything out yet. I'll check those links later today. If anyone figures out what it is or how it actually works, let us know. Lol
[Verizon Samsung Galaxy S III] YabbyYou:
I've been reading over the comments and code but I'm not sure if it's fully implemented yet. I guess it will be a way for the phone to get weather information from different sources. We'll have to see if more parts are pulled into our build in the future.
[Verizon Samsung Galaxy S III] Deliquified:
It looks like CMs answer for built in weather tracking. They've used Yahoo weather on cm12, but I've noticed it hasn't updated in nearly 2 weeks and I can no longer refresh the data.. Perhaps this was in response to that. I really wish we could get ffc to work.. This thread was started 4 months ago and it would appear we're more likely to get the next version of Android before we get a working ffc which is a deal-breaker for a lot of people to make the jump
[Verizon Samsung Galaxy S III] YabbyYou:
Hey Deliquidied, I understand your frustration with the ffc not working, I feel the same way about bluetooth audio! I would open a bug report on the ffc cam but the problem is I can't open it in the Nighties section because they only track regressions in there (aka this used to work on build x and now it's broke on build y). Since the ffc never worked on these nightlies, I can't open a bug report there. The other spot to potentially open bug report would be for the "released" version of CM13. Problem there is, I don't run it! Since I don't run it, I can't create a logcat to upload with the bug report. If you or someone else is willing to install the released build of CM13, test the cam and capture a log, then we could get a bug opened. I use my S3 as a daily driver, so I don't want to go back to the released build because I feel I'll have too many additional problems. With the current nightlies, I know where the issues are so I can plan accordingly.
[Verizon Samsung Galaxy S III] Deliquified:
I use mine as DD as well and can't be upgrading back and forth at the moment.. I feel as if they're likely well aware the camera doesn't work, but simply don't have any devs left with the knowledge/desire to fix it. It's worth a try to submit a report and hope for traction I guess.. Just doesn't look likely as if it was gonna get fixed it probably would have happened already. Lollipop took about 3 months for ffc to get fixed but xda devs like Mastamoon were pushing out builds like crazy then. Now that development has essentially halted, it seems we need to find an active maintainer again that will address our issues if CM continues to support us into the future
[Verizon Samsung Galaxy S III] vforaci:
Unfortunately I was forced to go back to CM12. Too many little things (already mentioned) and the sudden battery being sucked from the keyboard were the reason. Hopefully this stuff gets resolved and I can try flashing again in the future.

FYI: 4/4 ran ok (FFC and bluetooth audio not working) other than the lock screen weirdness which was the reason I flashed newer builds and it went down hill from there.
[Verizon Samsung Galaxy S III] AyUaxe:
DKP 12/27/15 for 6.0

Running DKP 12/27/15, afaik, the only dkp build for 6.0 (stable 1792 was a typo--it's 1782--getting random reboots at 1944, but man, is it fast in between!), tierservative gov. I saw some comments that people were having instability and I had lots of problems, too, with previous 6.x flashes, both AICP and CM. I kinda think what finally did it was the nuclear option. Nandroid/TWRP backup (precautionary/fall-back--haven't tried to restore data, 'cause that seemed to be a big part of the problem before), factory reset + wipe system, then flash ROM and gapps, wipe dalvik & cache. Boot and be sure it's working, then flash DKP and anything else (e.g., boot animation, audio enhancements). Back when 6.x builds first started for d2vzw, I tried the last 5.x DKP with it and it also seemed to work OK, but other problems chased me back to 12.1.

I'm planning to keep flashing the "lil d2 that could" as long as it and our glorious devs ( [MENTION=2385005]invisiblek[/MENTION], pbuh and [MENTION=2044079]Nardholio[/MENTION], pbuh) keep saying "I think I can! I think I can." I thought I'd start flashing every nightly, but just don't have the time and still want to keep it useful as a reader/media device (great for reading on flights--go-tos are AcroDesign's Study Bible and FBReader, both in night mode--and avoids drain on my dd phone). So yeah, BT fixes would be super nice. Guess I'll pick the next build based on what I see here and/or checking out the change logs. Quark has a cool community, but this one sets a high bar!