yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dvschnk:
So I finally jumped over to LOS 14.1, from CM13. I've tried 2 builds so far 4/24 and 5/01 and am quite impressed with it. I've put it through its paces and the biggest surprise for me is the GPS. I haven't had the GPS working this fast since I was on a stock ROM. CM12 had a none existent GPS, and CM13 was only a tick better. Camera works well, and battery life for me has been better than CM13. I'm not a heavy bluetooth user, so can't really comment on that.

The only bug I've run into is the front camera. The rear camera works well, even though i'm getting some light bleed on the bottom of my photos, but I also had that on CM13 and I think my camera sensor is slowly deteriorating. But the front camera bug reminds me of the early days of CM13 where if you take a photo, it freezes the whole thing. The fix back then was to set SELinux to permissive and allow it to create some log files....I tried that here and the fix doesn't apply here. Anyone else try the front camera?

One other thing, that's not really a bug, but confusing the crap out of me is that after every call ends, I get 3 beeps. I know on old android devices, there use to be an alert setting for when the call ends....can't find that setting now to disable it.
[Verizon Samsung Galaxy S III] mamarcac:
FFC has been fixed upstream since 2016

That's disappointing to hear about the FFC, since the issue was addressed sometime in mid-late summer 2016 where the camera didn't have write permissions that was causing the freezes and once it was discovered, it got fixed in the builds. I can't imagine it got changed for any reason since it was such a big issue at the time. Maybe there's something else causing it? Have you tried Open Camera instead of the stock camera app?
[Verizon Samsung Galaxy S III] dvschnk:
Good call mamarcac. I remember the FFC being fixed upstream and but I thought that was limited to only CM13. But in the process I totally forgot about Open Camera. I just downloaded and tried open camera and front camera works fine so my guess is something is up with stock camera. Not sure what other camera apps are/are not affected...just wanted to throw that out there and be documented just in case others run into issues down the line.

Just tried a video call using Google Hangouts and that was a no go with the front camera. The app will still work (no crashes) but it looks like the front camera isn't even detected. During the call, when I use the front camera, i just have the generic user icon.
[Verizon Samsung Galaxy S III] mamarcac:
That stinks that Hangouts doesn't detect the front camera. I personally don't use Hangouts since Google is deprecating it to an enterprise software soon and they removed SMS integration recently.

FWIW, I always seem to find my way back to TW roms to have fully functioning camera/video/texting functions dependent on the camera. I'd love to be on Android 7x but since custom ROMs don't have the special Samsung blobs for the camera, there always seem to be some funkiness and issues with anything camera dependent.

Even though 4.3 is outdated by design standards, it's the last TW version (CleanROM in my case) where everything "just works". So if you rely on all functions of your phone to work, that's some food for thought from a fellow Flash-a-holic who's tried a whole slew of custom ROMs over the past several years for our d2vzw.
[Verizon Samsung Galaxy S III] phonetool:
Seems to work fine for me. I don't ever use it, though.

I snapped an image and ran a couple of seconds of video just now. I'm on the 5/1 nightly with no other modifications.
[Verizon Samsung Galaxy S III] phonetool:
I've noticed that the USB debugging and USB charging notifications persist after the cable is disconnected.

Otherwise things work really well.
[Verizon Samsung Galaxy S III] Ibuprophen:
Hello Everyone :)

I just wanted to provide you with the verbiage from the feedback I had submitted to [MENTION=5795145]javelinanddart[/MENTION] via a PM response a little over a week ago (as reflected on the above post I had quoted).

I'm just posting this as a little FYI for those who may or may not have experienced the same to be included with the in additional feedback here since javelinanddart announced the above information.

***PLEASE NOTE: This feedback reflects what i had experienced and doesn't necessarily reflect the views or experiences that others may or may not have experienced themselves.

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

Hello javelinanddart,

I had performed a clean install of the Unofficial LineageOS release from your File Host Account with the latest Open GApps Pico package and the Stable SuperSU v2.79.

Since the first CM14.1 for this device (and continued on the LOS14.1 releases), the installs took longer than normal and always ended up successful with 2 args (and the other issues you are already aware of).

This Unofficial Release, i immediately noticed a quicker and successful flash with no args at all. That gave me a warm feeling.

Now, after using it for only a few hours, the difference is like night and day. I have no data connectivity issues at first but little things slowly happen and noticed.

The major ones are that the Sync function sporadically stops functioning. The only way to get it going again is to stop/disable it then re-enable it. Also, the Internet connectivity slows to a crawl (sometimes even stops) and picks back up again. I can get it to pick back up faster by stopping/disabling the data then re-enable it. A very odd behavior. This happens for both the Mobile and WiFi Data.

The minor ones is that there is no internal text editor as the CyanogenMod had and did like very much for simple text files. Also, when I'm within the "recent apps switcher", and if i select an area outside of the app listed, it doesn't take me to the main launcher screen as it used to be able to do. The built in file manager has no settings option for customizations like it used to.

Thank You So Much for this and I see progress being made very well.

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

Thank you all for your understanding!

"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] vforaci:
I did the same and it appears to work well in my testing. Although I never use the FFC.
[Verizon Samsung Galaxy S III] Ibuprophen:
Hello Again Everyone!

This is just an FYI for those of you who uses TWRP for the d2vzw.

On 01-May-2017, there were 2 issues reported in the appropriate d2vzw (device specific) area for TWRP in Github and just posted the details within the following thread.

[RECOVERY][d2vzw] TWRP 3.1.0-0 touch recovery [2017-03-10]

I'm letting you know here for posterity as well as just filling you in on this information.

Thanks a Bunch!

"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] javelinanddart:
So it's not just me.....I'm not sure where the issue is, but it's not a big deal. If you reboot, it goes away (as would be expected). It may be a hardware issue, d2 is getting very old, and this isn't affecting some others I know who help me test d2.
[Verizon Samsung Galaxy S III] Droidriven:
It's been like that since 5.0.1
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm surprised in the number of individuals, who use LineageOS, doesn't know of the FTP Mirror Link for LineageOS...

Here it is for those of you who doesn't know it.

https://lineageos.mirrorhub.io/full/

Happy Hunting!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] AyUaxe:
Hi, gang, back from M zombie land! Little d2vzw that could keeps thinking she can! Can someone point me to some instructions re: regaining root after clean flash to current 14.x? Haven't been able to get proper root with either May builds, though they are otherwise excellent. Thanks in advance and extra props to lonelyskatter for kernels that really pop!
[Verizon Samsung Galaxy S III] phonetool:
Lineage ROMs do not include the superuser stuff at all. Search their site for the download page and flash the SU file.
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm curious about why [MENTION=2385005]invisiblek[/MENTION] never changed the thread title from CyanogenMod to LineageOS or even open a new thread for the LineageOS 14.1 as a new thread would, likely, be a more appropriate thing to do to separate the CyanogenMod 14.1 and LineageOS 14.1 releases as he had previously done to separate the different releases.

Though, i do know that it's not a real important item but, i was Just wondering...

Maybe [MENTION=1050103]sykopompos[/MENTION] would either know or ask [MENTION=2385005]invisiblek[/MENTION] this too?

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] vforaci:
I dirty flashed to the 5/29 build, so far so good.
[Verizon Samsung Galaxy S III] AyUaxe:
Is a clean flash necessary to switch between official & unofficial? I seem to recall that they were signed differently, so clean flash was needed. Huge thanks guys for keeping the little d2 that could thinking it can! BTW, ScatterKernel is working great with these builds. Best stability at highest (1944) mhz ever. play app updates work perfectly.
[Verizon Samsung Galaxy S III] Ibuprophen:
If your referring to dirty flashing...

It's not recommended though, It has been done only for dirty flashing from Unofficial to Official but, not the other way around.

Yes, they are both signed differently. The Official is signed by the Lineage's QC Developer and the Unofficial (from invisiblek) is signed by Invisiblek. Invisiblek is the lead developer on the LineageOS d2vzw team.

For dirty flashing, I, personally, would recommend keeping with the build that's installed (ie... Official to Official and Unofficial to Unofficial). This is because changes, improvements, fixes, etc... that are implemented for the 2 builds can differ enough, between them, whereas cross flashing may potentially create an unstable update/install.

Remember that Nightly builds are categorized as Unstable Releases and Snapshot builds are considered as Stable Releases.

I don't believe that LineageOS even has any Snapshot builds released yet for any devices but, I could be wrong though, I, personally, haven't seen any yet.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] raisins:
Has anyone had an issue where the phone will randomly not be able to connect to any cell service at all? It has happened to me twice this past week, the only thing to fix it seems to be a factory reset and clean install. But even then, after a few days service drops again.

For me, my LTE switched over to 3g, and then it dropped to 1x. After rebooting, I can't connect to Verizon at all. Not sure if my antenna is going bad or what. Anyone have this issue? Happened to me on an old CM14.1 nightly, and now the LineageOS 6/19 unofficial invisblek.
[Verizon Samsung Galaxy S III] Ibuprophen:
LMAO!!!

I get this too and, sometimes, i have to perform a, sort of, workaround by going into the devices "Settings" then into the "Cellular networks" and then, under the "Preferred network type", i would just quickly toggle it from "Global" to "LTE" then back to "Global" and all is well.

This has been something I've, sometimes, needed to do with CM13 and LOS14.1 (Official and Unofficial Builds).

I had reported this on a few occasions and had used a few different methods on reporting this to them too within the past 6-8 months and then i had given up about 3 +/- months ago.

If you go to the following link:

Info about d2vzw - Official LineageOS Wiki

Towards the bottom, there's 2 Officially assigned Maintainers/Developers that's listed for the d2vzw:

[MENTION=2385005]invisiblek[/MENTION]

AND

[MENTION=5795145]javelinanddart[/MENTION]

I'm not certain about this but, with this issue existing since CM13, it doesn't look as though anything is really being done about this.

That workaround i had stated above should work for you.

Good Luck!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] jtnc:
I've never had it not connect at all, but have had it get stuck in 3G. This seemed to be retained across boots which I found confusing and implies to me something in non volatile storage is getting set wrong. Toggling airplane mode fixed it for me. May or may not help your issue.

Generally when I've gotten stuck in this mode it's because I either went into airplane mode or turned off data when in remote areas.

Good luck

John
[Verizon Samsung Galaxy S III] Ibuprophen:
Toggling airplane mode and toggling the network type accomplishes the same thing. It just resets the connection to the cell towers.

I believe that these issues (more appropriately... small pain in the neck) primarily affect those who are on some type of BYOP (Bring Your Own Phone) Program that utilizes the Verizon cell towers.

I believe that the CyanogenMod/LineageOS is compatible for them but, something just causes this issue.

To clarify... I'm not stating that everyone that uses the BYOP Program experiences this but, I believe that there's a good portion of them who does.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] Droidriven:
I always had this on my Straight Talk S3 on Straight Talk network usually when in poor service areas. I was using a Verizon SIM so the d2vzw ROMs would work so that might have something to do with it. There was also a strange issue that never got pinpointed where some of the Straight Talk S3 devices using d2vzw ROMs and SIM would randomly dial *22890/*22891. I never personally had this issue though so I never got a chance to troubleshoot it.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] Ibuprophen:
Really? Wow, I've never heard of any type of random dialing issues.

I've heard that (though, quite a while ago) there were issues, in the early stages of the TracFone BYOP (using Verizon towers) that the Verizon specific Bloatware of the d2vzw devices were causing all kinds of different issues like crashing (and similar) but, that was when TracFone had just gotten into the Verizon portion of the BYOP program.

At that time, CyanogenMod, wasn't really configured for the BYOP either. I think CM12 or CM12.1 for the d2vzw was just coming out too... Wow... am I feeling old now LMAO!!!

Anyway, that was when individuals had to either manually program the APN for TracFone too. And I also remember Flashing PRL's then too... LOL!

My brain is overloading with the memories of the past. I may have to Meditate now :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] phonetool:
This has happened to me three different times over the past year or so. First LTE goes out and you're on 3G for a day or so, then finally it's just 1x data but the phone still works. Then the phone drops out and 'no service' appears. During the week of this decline, I try rebooting (of course), airplane mode, fiddling with the network settings, wiping dalvic, and other minor things. I've never tried a full on wipe and re-install.

The only way out of it for me has been to go to Verizon and get a new sim card. It's free, but does cost you the time for the store visit.

If you go to a Verizon dealer they'll charge you $10.
[Verizon Samsung Galaxy S III] Ibuprophen:
Wowah!

I have Net10 (using the BYOP Program for Verizon Devices) and used to have a similar issue but, more frequent and primarily no MMS/Internet Data at all, i only was able to make Calls and use SMS.

All i did was open a Net10 Chat Session with Support and they just reset my SIM information on the Verizon system (of course it was attached to my IMEI) and... WHAM! my 4G LTE was working like a charm. All was well and peaceful... LMAO!

The whole chat session took around 3 minutes +/- and I kid you not. This was needed around 1-2 times per month and lasted about a year before their system updates seemed to have solved this issue and I haven't had to contact them for about 6 or so months now.

I've spoken to other Verizon users who had a similar/same experience with Verizon directly and the Verizon company always performed (and had the customer perform too) the same steps and always resulted in a new SIM.

I'm pretty happy (though their not perfect) with Net10 and using the Verizon towers. I don't have to deal with Verizon at all. It costs me $40/mo with 5 GB/mo of data (then like 2G after) with unlimited everything else. I rarely use up the 5GB because i primarily use WiFi anyway.

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] phonetool:
Sorry, but my story left the impression that phone and message service stays dead. While a period of blackout occurs, it does recover. Data stays off though.

I always wondered if the "failure" of my sim has been related to flashing nightlies or maybe my big 7Ah battery that sits over it.

Sounds like it's really a Verizon problem? I'm going to try the service chat and sim reset next time.
[Verizon Samsung Galaxy S III] phonetool:
I've been flashing the nightlies as they come out on the LOS site with no problems and developed a confidence that pushed me away from making frequent backups.

Lo and behold the latest version (6/26) gave the phone fits of bootloops like I remember from the old OG Droid days. Without a recent backup to easily drop back to, I allowed the looping to continue. I figured it was incrementally getting further each time through the app setup required after a dalvic wipe. Sure enough, after several hours it finally booted all the way.

Running well this morning. No problems yet discovered.

Not sure if anyone will have the same experience I had, but just a reminder to keep a recent backup in case you don't have the hours to spend watching your phone loop.
[Verizon Samsung Galaxy S III] GeTex:
i am having similar issues with the radio, with a VZW sim keeps cycling the radio and service bugs out every time data is activated. Occurs on every lineage based 7 rom, not occuring on android 6.0. Going back it seems
[Verizon Samsung Galaxy S III] raisins:
Hmm... I tried getting a new SIM when this was happening and it didn't fix my issue. The only thing that fixed my issue was factory resetting and flashing a new ROM. I flashed a newer 14.1 nightly, and I had data/cell service back, but after a few days, the same issue happened.

Now i'm on a android M ROM for over a week and haven't had the issue. Not sure if it's an android N issue or what. Just weird because the first time the issue happened to me I was on N for like 6 months with no issue
[Verizon Samsung Galaxy S III] J-Lindo:
Hey, fellas!

You might remember a while back I had issues with Gmail and Google's Wallpapers app. Gmail would never load, nor would the rotating wallpapers (there may have been some other small issues I can't remember). And nothing I tried would make either work... Until today. What did I do to make my problems go away?

I flashed the darn MF1 bootstack/NE1 modem combo in the OP. I had been riding on the MF1 modem the whole time, never realizing that I hadn't updated the stupid thing. Now that I've done that, everything works PERFECTLY. So now I'm over here kicking myself for overlooking something so obvious :silly: But hey, lesson learned. Thanks to everyone who tried to help, and I hope my solution ends up helping someone else!

PS: I've also mentioned before about not recording video in 1080p and Snapchat not sending videos properly. Those issues remain unchanged, though they're a small price to pay for this otherwise fantastic ROM.
[Verizon Samsung Galaxy S III] phonetool:
M

So, here we are again. LTE dropped off a couple days ago, then down to 1x last night. Still had phone then, but that's gone today.

I chatted with Verizon via their app on wifi, but they said there is no reset they could perform that would reach the device because it showed offline. They did do the reset anyway, to no result.

I went to the Verizon store for a new sim, but that didn't work either.

Following my normal method I can try waiting for the phone signal to return (it has in the past), or I could try other things... like flashing the radio again (meh) or a full wipe and rebuild (ugh!).

The Verizon people were funny. "You're running 7.1.2 on an S3??"

You betcha!

Edit:

Flashing the me1 package from the first post didn't change anything.

I popped the new sim into the old Gnex and we'll see how that goes for the next few days.
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm not sure if there's any known issues reported to [MENTION=2385005]invisiblek[/MENTION] or [MENTION=5795145]javelinanddart[/MENTION] but, the last release of the LineageOS for the d2vzw doesn't seem right to me.

It looses root fairly quickly but, I've got a few things to try out before making a final statement as to what's going on (with logs and such to provide).

Please let me know if there's anything I should be aware of in case my attempts are a futile one.

Thank you very much!

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] blueman2:
I just installed last night on my old S3, and this works wonderfully!!! Phone still feels very fast and modern. I did have to download the SU file for root, but that was the only part of the process that was unusual. I am SUPER happy!! Thanks so much to the authors!!!!!
[Verizon Samsung Galaxy S III] Ibuprophen:
That's great to see! :thumbup:

I'm probably looking at this too much but, I'm just wondering what you meant by downloading the SU file? :what:

Was it the Lineage SU, SuperSU, etc...? :confused:

This is purely out of curiosity. :D

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] blueman2:
I did not realize that the ROM came un-rooted, so at first did not download the su.zip file from the LineageOS site. I now have that installed and root is working fine.

On my second day using this ROM and really loving it. Rock solid! I am amazed to still see people supporting the old S3!!
[Verizon Samsung Galaxy S III] AyUaxe:
The little D2 that could keeps thinking she can and keeps chugging along. I stayed on M for a long time b/c i didnt want to lose root with each flash. finally figured out Magisk and it's all good. rock steady, clocking 1.89 ghz with lonely scatter's 3-26-17 kernel!

Mega THANKS to all the maintainers and devs!
[Verizon Samsung Galaxy S III] JeRiCkY_pOpS:
will this work in a locked bootloader??
[Verizon Samsung Galaxy S III] Droidriven:
Nope. You can't use any kind of custom recovery or true custom ROMs such as CM, LOS, AOSP, etc... with a locked bootloader.

You can only use something like Safestrap recovery with modified stock Touchwiz(TW) ROMs, or flash a modified stock ROM tar.md5 via Odin or push a modified system.img via adb/adb shell.

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE