yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Ibuprophen:
Well I tried a handful of different ways of installing the LOS14.1 and, so far, found that the following had worked for me to a point...

1) I had wiped EVERYTHING in TWRP.

2) I then only installed CM13 and GApps 6.0. Then wiped Dalvik and rebooted.

3) I went through the setup and did some minor customizations.

4) Rebooted back into TWRP, without wiping anything, i installed the LOS14.1 Experimental version (CM Migration) and GApps 7.1. Then wiped Dalvik and rebooted.

5) I went through the setup again and found that the customizations i had already performed was still there.

6) Rebooted back into TWRP, without wiping anything, i installed the latest LOS14.1 Nightly, GApps 7.1 and SuperSU. Then wiped Dalvik and rebooted.

7) The initial setup didn't show. Also found that the customizations i had already performed was still there. I then setup SuperSU.

Conclusion: I was happy that the Play Store was working as well as everything else was pretty much going good. I did see that, for some reason, the WiFi indicator on the top right (that reflects the signal strength) still had the "x" on the bottom right of that WiFi indicator. Though the apps can be manually installed and was seen that it was installed on the Play Store, I did notice when I had selected an app, on the Play Store, it reflected that it was trying to download but, it wasn't. So downloading an app from the Play Store was a NOGO.

I'm happy that, at least, progress was being made. I'm going to just keep on trying to figure this out.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] mamarcac:
This is a shot in the dark, but what are the chances that Doze is causing the issues...I had read about the Gmail sync issues that started with Marshmallow and it boiled down to Doze optimizing battery usage of the app to the point where it basically wouldn't work. On my OctOS-M installation, Google Play Services is not eligible under Battery Optimizations but Google Play Store is; I wonder if you don't let Doze optimize Play Store if that would make a difference? It's an easy change to make and test at least.
[Verizon Samsung Galaxy S III] J-Lindo:
Just tried updating to the 02/21 nightly, and it got me in a boot loop (unless it's supposed to take more than 20 minutes?). With all the CAF code merging and whatnot, is a factory reset/data wipe warranted, or should I be able to dirty flash this?

I'll roll back to the previous nightly, save what I need (texts and all that), and try doing a data wipe with this nightly. I'll come back and share whether I had any luck. Either way, just thought I'd say something in hopes of saving someone some headache. Or if someone's got the solution already, that'd be great too :)

Edit: Data wipe worked! 02/21 Nightly is not bunk! Perhaps someone else will have better luck than I did, but if dirty flashing results in bootloop, it will go through in a clean flash.
[Verizon Samsung Galaxy S III] Deliquified:
All the latest builds require a clean flash if coming from cm 13
[Verizon Samsung Galaxy S III] J-Lindo:
I was coming from Lineage's 02/13 Nightly.
[Verizon Samsung Galaxy S III] Deliquified:
There has been a lot of changes in the last week so that doesn't surprise me.
[Verizon Samsung Galaxy S III] J-Lindo:
Alright, I've been having to clean flash the past few nightlies, ever since the big re-base. Dirty flashing just results in bootloops. Anyone else having this issue, or am I missing something?

Have tried wiping Dalvik/cache both before and after dirty flashing. No dice.
[Verizon Samsung Galaxy S III] Ibuprophen:
To be honest, I've always stated that dirty flashing really only works appropriately 90% of the time.

Though, there are many individuals are successful in performing this, it doesn't always work.

Just remember to perform a backup before doing so. This way you can restore your device in case the dirty flashing doesn't work out.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

********************************************

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**

********************************************
[Verizon Samsung Galaxy S III] Deliquified:
I believe titanium backup is up and running again to make the flashing process faster
[Verizon Samsung Galaxy S III] J-Lindo:
Can confirm, used it to backup and restore my apps and their data today. Made clean flashing a bit less painful this time around.
[Verizon Samsung Galaxy S III] xj333t:
has anyone been able to get visual voicemail to work? (d2vzw on LineageOS 14.1 03/06/2017 official nightly with open gapps stock 03/05/2017) thanks, Joel

---------- Post added at 08:37 PM ---------- Previous post was at 08:31 PM ----------

sorry for the quick 2nd post... any issues with using the Lineage system update to go from one nightly to the next? or is it advisable to wipe data and do a clean install? I would be going from 14.1 03/06/2017 nightly to 03/13/2017 nightly.
[Verizon Samsung Galaxy S III] Deliquified:
I'd flash superuser, use titanium backup for your apps, then clean flash. You'll likely bootloop if you try to dirty flash
[Verizon Samsung Galaxy S III] xj333t:
Thanks! I don't think I have ever dirty flashed or taken OTA updates... always done data wipes and clean installs.

Any suggestions for the visual voicemail problem? Currently everything on the ROM is working great except for visual voicemail (d2vzw on LineageOS 14.1, 03/06/2017 nightly, open gapps, stock 03/05/2017, google dialer v8.0.148481159). when I go to phone>settings>calls to enable visual voicemail I get the com.android.phone has stopped message and then it asks me to select my SIM card. I have tried clearing date, cache, rebooting etc., but nothing seems to work. visual voicemail is enabled on my Verizon account. thanks!
[Verizon Samsung Galaxy S III] vforaci:
I flashed the official LOS 14.1 (4/3 build) with open gapps and everything seems to be working well. Not much activity anymore here. Curious to why there is no new thread for LOS?
[Verizon Samsung Galaxy S III] phonetool:
Thanks for sharing your results. I'm still on 12.1 and have been watching the progress on 13 and then 14, waiting for everything to work right. I think I won't be too far behind you getting 14.1 running. Strange how quiet it got lately.
[Verizon Samsung Galaxy S III] vforaci:
The only reason I waited as long as I did moving to LOS was the this thread was dead. I was previously running CM13.1 for over a year with success.
[Verizon Samsung Galaxy S III] mamarcac:
Any issues with texting a video?

Since you've run 13.1 for a year, were you able to capture and send a video via the standard texting app? Mine didn't work so I wound up having to change ROMS since my S3 is still my Daily Driver.

Thanks for any feedback!
[Verizon Samsung Galaxy S III] Ibuprophen:
Am I going crazy?

The last Android 6.0 that was released was CM13. I don't recall ever seeing a CM13.1...

I have the last Android 6.0 (CM13) they released currently on my device.

Also, I am still working on the Mobile/WiFi Data Issues with the LOS14.1.

A slight workaround was performing a CM to LOS Migration using the Lineage's Snapshot release.

Let me know how you did if you install LOS14.1.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] vforaci:
I was using Hangouts and rarely send videos mostly pics.

---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------

Maybe it was cm13. I haven't noticed any issues mobile/WiFi issues. What's the issue?
[Verizon Samsung Galaxy S III] Ibuprophen:
I have no problems with the CM13, it's the LOS14.1 that I've been trying to figure out what in the world is going on with the data... LOL!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] vforaci:
What problem are you having with data? Mobile or WiFi? Let me know and I'll confirm if it's happening on the build I installed.
[Verizon Samsung Galaxy S III] mamarcac:
WiFi and 4G drop intermittently

I can't speak for [MENTION=648656]Ibuprofen[/MENTION] but I did a trial installation of Resurrection Remix (LOS 14.1 based) this past weekend and experienced WiFi and Mobile Data dropouts/disconnects on my d2vzw. This was a fresh install after wiping dalvik, cache, data, data/media, and system.

So back to CleanROM 8.2 (Jelly Bean 4.3) for me. The d2vzw is still my daily driver...
[Verizon Samsung Galaxy S III] vforaci:
I've had none of those issues on the official 4/3 build. Mine is also my daily driver so all needs to work or a restore my previous backup. I've been running for 5 days so far. The only glitch I've noticed (happened once) is that I lost notification sounds after a quick boot it worked.

Not sure if it makes a difference but I also flashed: Gapps pico and the su in the extras after a full wipe.
[Verizon Samsung Galaxy S III] Ibuprophen:
I've posted what was going on and described it on a number of occasions within this thread.

Here's one of my posts with a description.

https://xdaforums.com/showpost.php?p=70126519&postcount=78

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] vforaci:
I didn't modify and of the Wifi or Mobile data settings. I connected to Wifi during the setup and it's been working well (both wifi/data) so far. Maybe it's the modem?

I know in the past (CM13) I noticed than where I traveled to far remote areas (hiking trips) I'd have no signal but after a reboot I would have signal. In a few weeks I'll see if this also happens in LOS14.1.
[Verizon Samsung Galaxy S III] Ibuprophen:
Mine is similar but, not exactly the same.

I have no issues at all with CM13.

It's something strange with the LOS14.1...

I'll have data for both the WiFi and Mobile on the initial setup but, loose it shortly afterwards. Though, the device connects to the Mobile towers and WiFi connects too but, no Internet services.

There was a way i got the data to work even with the device reflecting no Internet when i first flashed the Experimental build for CM Migration. When it was done, I then had flashed the latest Nightly to complete the migration.

The migration process isn't something that should have to be performed unless there are circumstances requiring it. Even with doing that, the underlying issue still remains.

I've been trying to work this out on and off for a while too.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] Deliquified:
Hmmm anyone having issues reaching

https://www.cmxlog.com/14.1/d2vzw/

I'm hoping this doesn't mean we've lost support or our builds are going away..
[Verizon Samsung Galaxy S III] razorloves:
This is the correct official changelog site https://download.lineageos.org/d2vzw/changes/

But nighties have been stopped https://review.lineageos.org/168362
[Verizon Samsung Galaxy S III] Deliquified:
So d2 builds are dead for good? Or just temporarily on hold until the SSL bug is resolved?
[Verizon Samsung Galaxy S III] razorloves:
till someone fixes it
[Verizon Samsung Galaxy S III] Ibuprophen:
There's an official build on Lineage dated 4/10 and Invisiblek (the lead developer with lineage for the d2vzw) who had released an Unofficial build dated 4/13.

I'm not sure why you assumed this?

Official releases are not like clockwork and i don't begin to worry about any such thing unless i don't see both an Official and Unofficial build for at least one to two months because anything can happen to delay releases for whatever reason.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] Deliquified:
The Cmxlog link I posted was the original site for CM changelogs. Lineage adapted and continued using it so it's correct when it says
[Verizon Samsung Galaxy S III] Ibuprophen:
LOL! No they don't use cmxlogs any longer...

The following is for the LineageOS.

https://www.lineageoslog.com/

No big deal... I don't even believe that they even advertise it.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] Deliquified:
They did up until at least the 10th because I just looked at d2vzw changelog on Monday on cmxlog and it worked fine until that latest commit stopping builds
[Verizon Samsung Galaxy S III] Ibuprophen:
I know that this will be popping up at some point....

For those who had noticed on the LineageOS Logs site for the d2vzw:

"https://www.lineageoslog.com/14.1/d2vzw"

There's an entry under the "Latest changes on the build roster (this device)" that states "hudson: Kill D2" with the d2vzw within a list of 4 D2 devices.

DON'T PANIC!

I had researched this a bit on a few sources of theirs and found additional information on 2 of the sources with the Github having the most information.

https://github.com/LineageOS/hudson/commit/96e020eb0abbe1acaaea6bf13d4ee98d0c142767

Okay... The "hudson: Kill D2" is ONLY regarding a single entry called "boringssl" that's present within the 4 devices in question.

Furthermore, there's a "serious SSL bug" they are aware of that affects the 4 devices in question that (after a bit of backtracking) they had tried to address and, when they had merged this fix for the 4 devices in question (each having their own builds), had ended up with 4 different results "diff sizes were much too large to be reasonably considered" because the sizes for them should have reasonably matched and also be within a manageable size for each individual device image.

In closing, the above results had caused them to ultimately decide that since they can't fix where the ssl bug was located in, they just decided to just remove it completely to see if that ultimately addresses the bottom line issue.

So when they announced "hudson: Kill D2", they were only referencing where the ssl bug resided in due to an initial failed attempt to fix it.

2 other things that I had found (on another note) while looking into this...

1) This must explain why invisiblek had opened up Unofficial releases for the d2vzw after stopping them (reflected by the removal of the d2vzw directory in his website) since shortly after LineageOS began their Nightly releases for the d2vzw.

2) I did notice something else too (NOW DON'T GET TOO EXCITED LOL!). I had noticed that the d2vzw had begun reflecting entries (not too long ago) with links to Android 7.1.1 & 7.1.2. I can't be 100% sure of their intentions but, could it be? LMAO!!!

I'm done... Take care everyone!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] phonetool:
Well I'm finally on 7.1, thanks to Lineage. I wiped my lollipop and installed the 4/3 build, "stock" open gapps, LOS accessory su, and started rebuilding my phone.

Been running and tuning for about a week. Everything seems to be working ok. Although I must say that I don't stress test every little thing.

No bootloops, no failed phone or data connection, no trouble, really.

For a day I ran with leaving data on while still on wifi and that did nothing for me but wipe out the battery. Running at normal data/wifi shifting since then gives me just a shade worse battery life than lollipop, but I'm still taming the apps that came with "stock" gapps.

Overall, pretty happy with the install. Some little quirks here and there, but nothing dramatic.

This is my daily phone, too, which is why I've been so hesitant to update the os.

Thanks to everyone who has been working on this phone!
[Verizon Samsung Galaxy S III] razorloves:
um... what? you have no clue what you're talking about. lol
[Verizon Samsung Galaxy S III] Droidriven:
Lol.....damn.

I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] yosmokinman:
^Yeah but it's true. I read it like five times and was left with "wut"

I'd be interested in the reason for the "too large to consider" comment. In what partition would it be too big? I can't find more info than on the commit.
[Verizon Samsung Galaxy S III] mamarcac:
What "quirks"?...

Hi [MENTION=4602329]phonetool[/MENTION] we might be the only 2 people left using our d2vzw as DD, so when you say "little quirks" what are you experiencing? I have the itch to flash but would love to hear your experience. One man's little quirk might be another man's dealbreaker hehe.

Thanks!
[Verizon Samsung Galaxy S III] phonetool:
So far everything works without issue. Phone, data, wifi, camera, install of apps, settings, etc. Haven't come across a deal-breaker for me.

The quirks are like the "downloading" arrow/icon in the notification bar when pulling down and installing an app or update from the play store. It flashes briefly after I initiate the update, but then disappears. The play store still shows the download happening, tho. Eventually the notification changes from download to install, then finally installed. But the little animated arrow is a no show.

Oh, one setting that doesn't work for me is to wake the device with volume buttons. No biggie.

Little things like that.

Haven't exercised the gps yet, or any navigation. But I'll try it sometime soon.

Themes seem few and far between, but I just wanted the dark background and floaty bubbles. Again, no biggie, just not a fan of big colors as a background. And the boot animation is freakin stoopid, apparently the lack of theme support affects the availability of options there. I'll be patient and keep looking.
[Verizon Samsung Galaxy S III] vforaci:
I too use my S3 as my DD and haven't found any deal breakers. I can confirm GPS works for me. It's a little more sluggish then my previous cm installation and battery life is slightly worse but that's to be expected. I too had the boot animation, I'll replace that at some point.
[Verizon Samsung Galaxy S III] mamarcac:
Ah gotcha. Thanks so much for taking time to give details! Really appreciate it. Sounds like it's ready for prime time.

---------- Post added at 04:57 AM ---------- Previous post was at 04:53 AM ----------

So they're 3 of us lol! Didn't mean to exclude you [MENTION=4941458]vforaci[/MENTION]. Yeah from what I've read on Reddit etc is that battery life takes a bit of a hit. That's tolerable tho for me as I have one of the Zerolemon batteries and get 5-7 days continuous uptime between charges on 4.3. Boot animation is definitely not a biggie for me.
[Verizon Samsung Galaxy S III] dvschnk:
Good to see people still DD the S3. I'm still DD on CM13, and haven't made the switch because I'm still holding out for xposed to support it. Nice that people are giving quick reviews of it too...makes it more enticing for me to jump. Quick question, are you guys running the last official build of lineage1 or are you back on invisiblek's unofficial builds? That's another reason that I haven't jumped yet. I was about to switch to lineage when they pulled it from the official repository. Thinking about trying out the unofficial builds, but I know that once they fix the issue, I'll have to do a full wipe to hop back onto the official builds.
[Verizon Samsung Galaxy S III] Droidriven:
My stepson still uses my old S3, still running strong, he's not into the custom software though, all he cares is that it works.

I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] phonetool:
https://download.lineageos.org/d2vzw

What do you mean "pulled it from the repository"?

Still there so far as I can see. Or maybe you mean 13. I don't know about that.
[Verizon Samsung Galaxy S III] dvschnk:
Oh I'm use to downloading from the cmxlog site, and that completely removed d2vzw. I didn't dig as much on the official lineage site.
[Verizon Samsung Galaxy S III] javelinanddart:
Chill guys, everything will be fine.

I'm planning to restart nightlies for d2 after this week, the issue that [MENTION=4828250]Ibuprophen[/MENTION] was talking about with connectivity seems to have been fixed, (I already PM'ed him a test build: https://www.androidfilehost.com/?fid=673368273298949105). The "SSL Bug" was the issue Ibu was talking about, it was a bug in the SSL library that caused a workaround to not be applied properly, and the workaround not being applied meant that the crypto library that Google uses (for things like Play Store, gmail) was broken. When I said the diff sizes were too large to reasonably be considered, it meant (at the time) that the patches to fix the issue were much too large, because I didn't know where the issue was. I was blindly applying patches from the AOSP master branch (which is their "unstable" branch, where all new patches go). However, thanks to some new information, the specific patches that fix the issue have been identified, and are being reviewed this week so that nightlies for D2 can restart for nightlies next week. The bug was critical enough that I felt it should be pulled temporarily. Apologies if it caused any confusion
[Verizon Samsung Galaxy S III] phonetool:
Thanks, that's some good news.

My 4/4 install reminded me of the 4/10 release, so I allowed it to attempt the download. It got the first third about three times before I gave up and installed a decent download manager.

Wiped cache and dalvic, then dirty flashed. All ok. Boot animation is normal again, guess it was their April Fools Day version before.
[Verizon Samsung Galaxy S III] yoahmad1995:
I have 4.4.2 bootloader and stuck there is it possible to flash this with flashfire by chainfire? Also I heard that its possible to downgrade to 4.1.2 with jtag without bricking the device....
[Verizon Samsung Galaxy S III] phonetool:
As far as I know once your phone has been upgraded to 442 there is no way to go further. The bootloader is locked and a Q-fuse is set.

Your only option is to use a 442 based stock rom like SuperLiteROM.
[Verizon Samsung Galaxy S III] yoahmad1995:
Unfortunately, I'm a AOSP guy so I'm sticking to my International S3, Note2, S5 and Grand2. :)
[Verizon Samsung Galaxy S III] Ibuprophen:
I see that there's Nightly just released today...

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] Deliquified:
https://www.cmxlog.com/14.1/d2vzw/

Works again for changelog if you prefer it like me over lineage's official website
[Verizon Samsung Galaxy S III] Ibuprophen:
I prefer the following LineageOS Changelog link:

https://www.lineageoslog.com/14.1/d2vzw

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[Verizon Samsung Galaxy S III] phonetool:
I'm pretty happy with the last couple of weeks worth of updates. Running the 4/24 since yesterday.

Occasionally I find my phone has turned itself off, though. Not sure why that might be.
[Verizon Samsung Galaxy S III] vforaci:
I had the same thing happen maybe a year ago. It got worse over time. It turned out the battery was slightly lose where it sits. I figured it out when I dropped the phone and it shut off. Now I keep a business card thick tab on the back side to keep things tight and never had a issue again.