yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Ibuprophen:
That was a problem i had faced. I didn't realize that it didn't copy right. I tried so many times to perform the move or copy of the file.

When trying to copy or move the file, while CM14.1 is installed and within TWRP, from the internal to the external memory, it gave me errors but, If i have CM13 installed, then i have no problems with copying or moving files from the internal to the external.

BUT, with CM14.1 installed, i have no problem with copying or moving files from the external to the internal memory.

In addition, while booted in CM14.1, nothing can be moved or copied to or from the external memory. The external memory can only be accessed but nothing can be opened, installed, etc... I can only see what's in it.

I was lucky to be able to install the Logcat Extreme manually after having to boot to TWRP and get the app on the internal memory.

I really hope i had explained it okay and am really hoping that what I had provided (besides that file) is helpful in some way.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Verizon Samsung Galaxy S III] Pierre2324:
Wich partitioms should be mount as f2fs for performance?
[Verizon Samsung Galaxy S III] Fenix2002:
lol, I want to give a quick shoutout to [MENTION=2385005]invisiblek[/MENTION] and anyone else who has made this possible -- I just pulled my S3 out of a drawer after 6 months of not thinking about it after upgrading and came here and upgraded from Lollipop to Nougat within about 30 minutes.

Had it up and running about 10 minutes now and the front and back camera works (an issue I hated on CM13 builds), and everything seems to be working. Amazing how far the S3 has come.

-Fenix
[Verizon Samsung Galaxy S III] annoyingduck:
Anyone notice that audio is distorted? Kinda like it's overdriven, the volume level has no effect, I'm getting a constant distortion no matter what volume. Same result in both Playerpro and Poweramp.
[Verizon Samsung Galaxy S III] Stealth111:
Man, sad news today. I will take this time for a moment of silence... :(

https://www.cyanogenmod.org/blog/a-fork-in-the-road

http://lineageos.org/ will be the new official home for Lineageos.....

Stealth111
[Verizon Samsung Galaxy S III] Ibuprophen:
Oy Vey!!!

Looks like the Cyanogenmod and Cyanogen is has Officially announced that they have closed shop and it will happen No Later Than 31 December 2016 as announced...

Here:

https://www.cyanogenmod.org/blog/a-fork-in-the-road

And Here:

https://cyngn.com/blog/cyanogen-services-shutting-down

BUT, on the lighter side, they are Rebranding as "LineageOS"...

Here's the new LineageOS Github page:

https://github.com/lineageos

I'm keeping my eyes open for more information as i see it.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Verizon Samsung Galaxy S III] LLStarks:
I can't get wifi or any kind of tethering to provide internet once connected.
[Verizon Samsung Galaxy S III] alado221:
NE1 baseband is what I am running and it works perfectly.
[Verizon Samsung Galaxy S III] Ibuprophen:
I also have NE1 baseband and though it works perfectly in CM13, it does the same thing as yours does after about 10 minutes using CM14.1. Connected, no Internet...

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Verizon Samsung Galaxy S III] itachi81:
Support for LM1

Why not make it compatible with ML1? I understood that it was possible to dowgrade to 4.1.2 and unlocked the bootloader everything from 4.3 ML1, but when I put ROM CM only had reboots due to incompatibility with ML1, many wanted to put radio from NE1 but only cause brick, and everything is Made and only lack support for ML1 so other large number of users can have custom roms and only missing those who have 4.4.2, I gladly try the roms in my s3 with 4.3 ML1 still do not downgrade because it would not have case if I can not put custom roms yet. And sorry to use google translate
[Verizon Samsung Galaxy S III] mamarcac:
Didn't realize the dirty laundry that was there until reading some of the back-stories. It's a shame really, that business still seems to get in the way of progress sometimes.

I have noticed in my personal opinion increased bugs and "quirks" over the last few years in the CM builds generally, with less focus on releasing Stable versions. I might be in the minority of users, who knows. As much as I like the newest shiny objects, at the end of the day I want a stable, reliable phone that won't randomly reboot or lose internet ya know? Anyways, we've had a lot of great options come from their efforts and I do appreciate very much anyone who played a part.

Looking into alternatives, has anyone tried Mokee Rom 5xx for the d2vzw? Looks like they released a "HISTORY" version on 12/16 which by their terms means Stable.
[Verizon Samsung Galaxy S III] lepa71:
I assume the download links no longer working. Did anybody can put up the latest( or whatever works better)? Thanks
[Verizon Samsung Galaxy S III] Ibuprophen:
Have you tried downloading via the website?

I just download the latest CM14.1 from the CM13 built-in system updater. And when it's done, i go to my file manager and move the file to my external MicroSD. Unlike using the browser that can fail when downloading, the built-in system updater is more persistent in downloading the update and continues the download if there was any disruptions.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Verizon Samsung Galaxy S III] Deliquified:
Tbh, the last build for CM 13 (mid November) was extremely stable and functional. I'd recommend flashing that
[Verizon Samsung Galaxy S III] lepa71:
I was trying to download from official site, but I get proxy error.
[Verizon Samsung Galaxy S III] Ibuprophen:
@Stealth111 & @invisiblek, I had tried again with no luck...

I provided a link to another zip file with all the logs. It includes a logcat i personally verified. It was a bit challenging but, I have it all in there.

CM14.1-Log-Files-20161228

I hope you can finally see what's going on.

I used the CM14.1 dated 20161225 and the Open GApps Pico dated 20161215.

Thank You So Much!!!

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[Verizon Samsung Galaxy S III] Ibuprophen:
Just an FYI regarding a link that's titled

"List of devices getting official LineageOS Roms"

http://www.lineageosrom.com/2016/12/list-of-devices-getting-official.html

Just spreading the word that the d2vzw is on the list. I'm hoping that it remains there for when they release the ROMs.

YAY!!!

--------------Top post was at 12:51 AM--------------

---------Bottom Post added at 12:51 AM ---------

Here's the last CM14.1 Nighty that was released on 25 December 2016:

cm-14.1-20161225-NIGHTLY-d2vzw.zip

cm-14.1-20161225-NIGHTLY-d2vzw.zip.md5

Happy Holidays!!!
[Verizon Samsung Galaxy S III] invisiblek:
This is 100% NOT legit. This guy is not affiliated with us at all and is completely trying to mislead people for whatever reason. I HIGHLY recommend not downloading anything off that website.
[Verizon Samsung Galaxy S III] Ibuprophen:
My apologies and thank you for the clarification.

That site will no longer be referred to nor referenced to.
[Verizon Samsung Galaxy S III] mb27:
I cannot get internet connectivity through the Play store either. I am running the 20161225 build of 14.1. On the MF1 bootstack/NE1 modem combo from OP. TWRP 3.0.2.0. Tried the 30 Dec 2016 aroma, micro, nano, and pico versions of open gapps, all on clean installs, but no luck. My S3 is on wifi only - doesn't even have a sim card installed. Â¯\_(ãƒ„)_/Â¯

I did notice that my serial number is currently all zeroes. Could that have anything to do with it?

awwwwwwwwwwww yiss I got it working! I flashed supersu 2.7.9 in recovery then installed flashfire. In flashfire I flashed gapps and wiped dalvik and rebooted. I now have Play store connectivity!

Update: That only worked temporarily and no matter what I tried, including going back to stock and rooting again, I couldn't get it to work a second time. My S3 is just a backup phone so it's not a big deal but I was hoping to give CM Nougat a good try.
[Verizon Samsung Galaxy S III] Deliquified:
Anyone know our future status here? Will we continue to be supported by LineageOS, or is this the end of the road?
[Verizon Samsung Galaxy S III] Deliquified:
After doing some digging, I found this branch on github.. Hopefully this means we will continue to be supported

https://github.com/LineageOS/android_device_samsung_d2vzw
[Verizon Samsung Galaxy S III] Stealth111:
Nah, looks like we are good! :) There are a few people building UNOFFICIALS for us right now, with OFFICIALS to follow when they get build servers and everything else sorted out. If you want to try it, here is a good working build: http://download.invisiblek.org/roms/lineage-14.1/d2vzw/lineage-14.1-20170106-UNOFFICIAL-d2vzw.zip

I have been running it all day with no issues, pretty much same as last CM builds were. However ***NOTE***, you MUST wipe clean before you flash this, you cannot dirty flash or upgrade this from Cm 14.1 builds due to the fact that this build does not use "test keys" as the OFFICIAL Cm14.1 builds did before shutdown..

Stealth111
[Verizon Samsung Galaxy S III] annoyingduck:
Just setting up today's Invisiblek build...so cool. Thank you as always [MENTION=2385005]invisiblek[/MENTION]. So weird not seeing the CM boot splash screen - it's been on this device for several years now. Love how Lineage is using a blue accent color over the seafoam green. Can't wait for official, but this is awesome so far.
[Verizon Samsung Galaxy S III] Ibuprophen:
I tried the Unofficial LineageOS from Invisiblek and I just don't understand why the Internet Connectivity for the Play Store doesn't work. I tried both the Mobile Data and WiFi.

It works within the Browser as well as checking for ROM updates but, not for the Play Store.

I only installed the ROM and GApps.

I used the Open GApps Pico ARM for 7.1 dated 06 Jan 2017.

The initial setup for the Play Store completed without a problem and, under the accounts, it syncs without any errors.

This is the same exact issue that i had reported on an earlier post within this thread. I even provided a good logcat file reflecting all the actions i have issues with.

I have no problem when installing CM13 with the Open GApps Pico ARM for 6.0.

Should i be trying another GApps package like Dynamic or Delta?

I have a feeling that this is not a GApps issue. I feel that the problem resides within the ROM and it may be something minor that could have been overlooked.

I'm about ready to, possibly, abandon the idea of the use of LineageOS14.1 in my d2vzw and remain using the CM13 until my confidence with the new version has returned.

I know that [MENTION=2385005]invisiblek[/MENTION] is working hard on the transition and was even wonderful to provide an unofficial release but, I'm finding it hard to accept that my issue has made it to him nor anything that he would bother with.

I appreciate the assistance of others but, all the recommendations from them has resulted in the same underlying issue. I thank them/you all anyways.
[Verizon Samsung Galaxy S III] tork1149:
Had same issue rebooted and gave it some time and it worked eventually
[Verizon Samsung Galaxy S III] annoyingduck:
I'm not seeing any playstore issues at all, nor any connectivity issues. I'm running current Open Gapps Pico. I use Wi-Fi only though (I disable the cellular radio). Build has been solid and clean with the exception of a few bugs that I won't even mention until official builds begin. Not sure what your issue could be, maybe reflash current Gapps to be sure Google play services are up to date?
[Verizon Samsung Galaxy S III] Ibuprophen:
This is what i had previously submitted.
[Verizon Samsung Galaxy S III] dltccf:
yep still can't get play store either
[Verizon Samsung Galaxy S III] AyUaxe:
I decided to come back from languishing in 13.1, to try [MENTION=6953397]invsi[/MENTION]blek new 14.1 build. Factory reset wipe, flashed 01/10 build, delta base gapps, dkp and now up and running solid for about 24hrs. Battery not as good as M, but better than earlier 14 builds. P-store updated like 8 apps after tibu restore, so WiFi connectivity is there for p-store. No active sim, so can't test 3g or 4g. Phone working with Hangouts dialer and GV number.
[Verizon Samsung Galaxy S III] Ibuprophen:
I was actually thinking about doing a backup and restore of the Play Store to see if that would work.

Did you include the Play Services?

Also, was there any specific reason that you used the Delta GApps and not the Open GApps?
[Verizon Samsung Galaxy S III] Ibuprophen:
I know that the following question is a bit out of the ordinary but, Is there anyone who can list what is needed to be included in a GApps Play Store ONLY backup to restore at a later time?

I'm just thinking of the following:

Play Store

Services

Services Framework

Though i do know that the GApps package has it all but, for my FYI, i am just curious to know for personal testing purposes only.

Thanks a Bunch!
[Verizon Samsung Galaxy S III] AyUaxe:
I've just had more consistent good results with Delta than any other and I like the simplicity of their builds. Base is really basic, other add-ons are mostly individual, so you just get what you want, not somebody's idea of mini or micro or whatever.

Re: battery life, seems WiFi is a big issue. Of I turn it off, charging nearly doubles in speed. All components are same as just used with 13.1, so it's not hardware.
[Verizon Samsung Galaxy S III] Ibuprophen:
After a ton of various scenarios, trials, etc... I do believe that the underlying issue is with the NE1 modem and the Nougat's inability to use it.

Simply, the NE1 Modem Firmware is incompatible with the Nougat and needs an update. Though there may be others that also require an update for better compatibility, the modem is working hard and may be causing issues with draining the battery by working harder than normal.

I'm hoping that [MENTION=2385005]invisiblek[/MENTION] reads this and, hopefully, can take a different approach regarding the possibility with the d2vzw NE1 modem Firmware compatibility issue.

That is my opinion/conclusion...
[Verizon Samsung Galaxy S III] Deliquified:
There's no update to be had. NE1 was the last and final modem released for the d2vzw model.
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm aware of that and never stated otherwise...

I was just pointing out my opinion/conclusion as to the compatibility issue regarding the Modem and Nougat.

Oy Vey!!!
[Verizon Samsung Galaxy S III] AyUaxe:
I'm on ne1 and have occasionally rolled back to ml1 without noticeable affect. I think if there was incompatibility between modem and rom, there would be no communication or major corruption of data, which we're generally not seeing. I would suggest trying full wipe, including system, then reflashing ROM and delta gapps base. Don't restore anything from backup, especially not any Google app, like gmail, maps, etc. YMMV.
[Verizon Samsung Galaxy S III] Ibuprophen:
I did all of that but, I haven't tried the Delta GApps.

I'll download it and try it out...

I'll get back to you with the results. I'll also use the logcat to submit a log.

Thanks!
[Verizon Samsung Galaxy S III] mamarcac:
External SD Card Write Permissions?

I never got CM 13 or its variants to allow proper SD card Write permissions. Can anyone share insight if the dreaded SD card write permissions are "fixed" in this release? It's the one thing keeping me on older Android versions. And I understand there have been Xposed modules that work for some but just being able to write a file to the external SD card should require zero hackery in my opinion, and I prefer to avoid Xposed in general for stability reasons.

Thanks for any insights!
[Verizon Samsung Galaxy S III] Ibuprophen:
Personally, i found better luck with performance using exFAT and some MicroSD cards perform better using vFAT but, using FAT32 does do the trick for most.

That's my opinion.
[Verizon Samsung Galaxy S III] mamarcac:
So you saw the way the SD card was formatted making a difference with Write permissions? Or were you just talking about performance in general?
[Verizon Samsung Galaxy S III] Jaws4God:
hey guys.. I think its going to be time for the S3 to find a new home... but they asked me to put on a newer ROM (currently back on stock).. is this CM14.1 fully functional and stable?

Thank you!!
[Verizon Samsung Galaxy S III] Ibuprophen:
The company formerly known as CyanogenMod never released a stable/snapshot of CM14.1 nor have they released a stable/snapshot of CM13.0.

As of yet, the current LineageOS company has not released anything for any devices.

With that stated, many of the the LineageOS Developers has released Unofficial Nightly builds and, for the d2vzw, invisiblek (the primary LOS Dev for the d2vzw) has been releasing Unofficial LOS14.1 Nightly builds which is located here:

http://download.invisiblek.org/roms/lineage-14.1/d2vzw/

This is the last of what my understanding is and, if I'm wrong, can someone please correct me so I also can take note.

----------The post above was added at 01:54 PM----------

----------The post below was added at 02:05 PM----------

I'm going to try to briefly explain it the best i can.

The 3 file system formats i had listed for MicroSD storage doesn't determine the Read/Write permissions. They affect the speeds in which information is sent to and from the external storage.

With that stated, the Android OS along with the device determines the way in which the information is written and read along with the permissions of said information.

I hope i had explained it okay. If not then can someone else chime in to try explaining it in another words (in layman's terms if at all possible).

EDIT: Have you tried looking through the following thread? It may pertain to your inquiry.

http://xdaforums.com/showthread.php?t=3296266
[Verizon Samsung Galaxy S III] mamarcac:
Yeah I've scoured every single thread about it that's why I mentioned I don't want to have to go the Xposed route due to stability, etc. That thread link you shared is for a flashable zip that has mixed results and many users report app issues after it appeared to work from flashing but they later found the app issues with it. So you get external SD card Write permissions but some apps start barking at you and malfunctioning.

/begin rant

This is something that's really puzzled me as I keep going back to CleanROM 8.2 (Android 4.3) because literally everything just "works". Full access to everything and full control. I don't know why Android M changed that, and from spending countless time researching the issue, it's a huge complaint by users. External SD Card cannot be written to like it should be and it's something that is baked into the OS.

/end rant
[Verizon Samsung Galaxy S III] Jaws4God:
I ended up putting on CM14.1 from their website (12/26 date i believe)... I was able to get it to boot (after selecting a smaller GAPPS) .. tried out the camera's and did not receive any errors.. wifi was connected.. I didn't get to test anymore.. I'm supposed to deliver the phone this evening.

So do the newer LOS14.1 builds have any fixes over the CM 14.1 ?

Thank you!
[Verizon Samsung Galaxy S III] Ibuprophen:
Just a follow up...

I had performed a complete system wipe and installed only the most recent LOS14.1 Unofficial and Delta GApps. Then, when i had finished the initial setup process, i immediately installed the Logcat App and began recording.

The same issue with the both the Mobile and WiFi data was there.... There wasn't any for the Play Store.

I attached a zip file with the Logcat and Recovery Logs.

I hope someone can get a better idea as to what is going on.

Thanks a Bunch!
[Verizon Samsung Galaxy S III] Droidriven:
You miss spelled his name, he won't get a notification of your mention so he might not see your post. At best, he would get a notification that you posted in his thread but there's no guarantee he'll read your post.
[Verizon Samsung Galaxy S III] Jaws4God:
are other people having Mobile Data and Wifi issues? I know the short time i tested mine on CM14.1 it did have working WIFI.

Thanks!
[Verizon Samsung Galaxy S III] Ibuprophen:
Within this thread, there are those who are having the same issues regarding Data (both WiFi and Mobile). Most all of those individuals have stopped reporting them since they've went unresolved. Within the CM13 thread, i even uploaded the last CM13 Nightly to my File Host Account when i was asked if I still had it. I haven't even mentioned the offline communication too.

This Data issue has been unresolved from the first CM14.1 Unofficial to the CM14.1 Official Nightly and still currently with the LOS14.1 Unofficial.

Don't get me wrong, I have no idea what is going on behind the scenes since I'm unaware of or if anything is going on.

On a few occasions, i had forgotten about uploading logcat files and was immediately responded/corrected as a "shame on you" style response but, when I did, in fact, provide logcat and other log files, i went either ignored or was recommended to try something that was previously attempted on an earlier post.

I, as well as a group of others, are very discouraged with reporting anything (though I am probably one of the few) on this post convinced that it's just getting ignored, including the Dev...

As a final note, this post will probably attract someone (or more) who will, more than likely, either lecture me or something else in a similar way.

Thank You for your inquiry regarding this...
[Verizon Samsung Galaxy S III] jtnc:
I've been using Invisiblek's 11/27 build (pre official CM 14.1 builds) with very few issues. Zero wifi or mobile data issues, reliable Bluetooth connections to car radio for media streaming. Calls to the radio are hit and miss though the jawbone headset is reliable for calls. Amazing battery life.

For me CM 14.1 is much better than CM 13 ever was. Rivals TW 4.3, though multiwindow mode is less useful than TW and battery life is much better.

Been lagging on updating since I needed to do full blown wipes due to the signing differences, and why mess with a good thing! I will probably give a shot with LineageOS before too long, maybe this weekend.
[Verizon Samsung Galaxy S III] Ibuprophen:
This and the Oct-OS Unofficial LOS14.1 has been giving problems with both the WiFi Data and the Mobile Data. The WiFi connects but, no Internet and the Mobile connects to the tower but, no mobile data and the APN is good.

After doing a bit of research, i found that, for no apparent reason, the MAC address may not be correct for many individuals who are having the same issues.

Somehow the MAC address requires a manual correction within the Nougat in order for the Data to connect.

I found that this happens with other devices but, not all.

Has anyone ever looked into this?
[Verizon Samsung Galaxy S III] J-Lindo:
Hey, [MENTION=648656]Ibuprofen[/MENTION], you mention issues connecting to Play. Whenever I clean install one of these CM/LOS 14.1 builds, I get a similar problem, and I have to try and retry and close and reopen until Play finally cooperates. I also, as I've mentioned before, have trouble with the Gmail app as well as the changing wallpapers feature of the Pixel Wallpapers app, and I've also found Keep takes a few tries to get going as well. Strangely, Inbox by Gmail works fine. Have you experimented with other Google apps as well, or just Play? I'm wondering if we have the same issue, and whether it's something about the way the ROM is attempting to communicate with Google (as I think you've also speculated). I'm hardly an expert on diagnosing this sort of thing, but I figured I'd ask to see.

For the record, I haven't had any major issues with either wifi or mobile data.