yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Farabomb:
Is anyone else seeing a lot of random reboots? It could just be my device as it's the preorder one I got way back in the day and have had power button issues before.
[Verizon Samsung Galaxy S III] KazuDante:
just wanted to know if the s3 vzw on 4.3 bootloader can be unlocked? from what im seeing in many other threads is that it cannot be unlocked , but looking at this thread i see that its vzw as well LineageOS so i assumed maybe it can be unlock. Can someone clarify this for me please. Thank You.
[Verizon Samsung Galaxy S III] phonetool:
I thought the magic threshold beyond which the bootloader got locked was OTA 4.4.2, so that would mean your 4.3 is still unlocked.

The install instructions at the old cyanogenmod wiki used to walk you through the whole thing. Not sure where that info is now...
[Verizon Samsung Galaxy S III] Roger W:
Hi, I'm just coming back to this device after last flashing an unofficial in January. I updated TWRP to latest, and then did a factory reset, and flashed the latest nightly and gapps pico (all in one session). Now during the first-time setup process, the setup wizard crashes and keep going back to the beginning. I am on wifi for this part and got past Google account setup. Any ideas why or how to get around it? I saw a tip posted about updating permissions in Settings manually, but it hasn't requested any permissions so there's nothing shown for me to add.

thanks!
[Verizon Samsung Galaxy S III] AyUaxe:
Setup wizard crash

I had that problem a short while ago. Turned out to be a gapps problem. I always preferred Delta's but they don't seen to play nice with this rom. Try downloading from open gapps, as linked in op. Worked for me. If you haven't already, try out lonely skatter's kernel. Great options to get lots more performance out of the lil d2 that could.
[Verizon Samsung Galaxy S III] Roger W:
Thanks! That prompted me to remember that I'd previously installed a too-old gapps that I'd had on the sd card. I'd done a factory reset afterwards, but that doesn't wipe System so there was still junk there when I installed the new one on top of it.
[Verizon Samsung Galaxy S III] appye:
Hello. I am running the 10/9 nightly and everything seems to work reasonably well. The main issue I am having is visual voicemail. I am referring to the voicemail tab in the phone app, not the verizon app. The tab is not there on my phone. Visual voicemail is enabled in settings... Is anyone else having this issue?
[Verizon Samsung Galaxy S III] DarkPhazon:
Amazing that my first Android phone still getting it done. Thx.
[Verizon Samsung Galaxy S III] Farabomb:
I keep having network issues. I'll get it to work in the metro area where I work. Then I'll go home to the woods where I get 0 signal and about midway through the weekend I loose all signal and then it won't connect ever again. I'll get it to connect through some voodoo and it will work for about a week then poof, no signal again. Lather, rinse, repeat.

Anybody else having signal issues?
[Verizon Samsung Galaxy S III] mamarcac:
APN settings maybe?

When I've had this issue before, the build sometimes shipped with a wacky APN configuration in the Wireless Networks settings. It sounds like that may be what happened, if you haven't already checked it.

FWIW, the OctOS variant of LOS has the APN correct for the d2vzw and I didn't have network issues while on that ROM.
[Verizon Samsung Galaxy S III] Farabomb:
I have a feeling it might be the same issue cyanogen had with verizon's network and the s3. I'll take a look at OctOS because this is getting quite annoying. Thanks!
[Verizon Samsung Galaxy S III] Farabomb:
Well the issue is still present on OctOS so I have a new SIM on the way. Hopefully that works because I'm sure any replacement S3 they ship out to me will have their craptastic relocked bootloader so that's not going to help. I have the GF's old S3 but sadly she updated it and now the bootloader is locked on hers. Sucks because the S3 is still a great phone but as usual, Verizon's meddling ruins it.
[Verizon Samsung Galaxy S III] mamarcac:
Sorry to hear that, hopefully the new sim fixes it. If you don't need the latest and greatest, you can roll back to a TW 4.3 rom and see if the radio issue persists. From what I've seen LOS 14 never really reached a stable level, I read posts about it working "flawlessly except for camera sucks and call quality is worse than TW". I guess flawlessly means different things to different people, my point is I keep going back to 4.3 TW when I need the whole phone to "just work" so there's always that option. Basically we each have to choose what trade-offs are acceptable. ¯\_(ツ)_/¯
[Verizon Samsung Galaxy S III] Farabomb:
The new SIM isn't working so I have to come to the conclusion that I might have to retire the S3. The charge port is a bit wonky, the power button is possessed and the phone doesn't owe me anything. I have a M8 as backup but that thing is also possessed and resets permissions constantly. I could get a new phone but everything is locked down and I can't be without root and a unlocked bootloader. Maybe I'll have verizon send out a replacement and see what software is loaded on it. If it's locked down then I just won't swap it.
[Verizon Samsung Galaxy S III] Droidriven:
Pretty much all of Verizon's devices are locked down, even the Pixel, which is strange to me considering it's a Google device when all other Google devices are usually bootloader unlocked/unlockable. N5X, N6, N6P or some version of One plus may be viable options if you find one in almost new/barely used condition.

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] Farabomb:
That is what may finally push me away from Verizon. I can't get service in my house anymore. It was bad when I moved but after the FCC told them they need to sell some of their towers it got much worse. I rarely get texts and I have to walk up the street to maybe get signal and even then it's a crap shoot.

I'm going to try and flash some more things and maybe get the radio back to where it can connect to towers when I get to civilization. I don't want to retire the phone since it's been working fine for all these years.
[Verizon Samsung Galaxy S III] Droidriven:
Have you pulled any radio logcats to see if there is anything strange/suspicious?

Roll back through the various modem versions one by one, maybe one will work.

Have you verified everything involving SIM/radio in build.prop, some lines there deal with radio processes.

Go through the .ril files and see if you can make sense of whether it's in order and has all the libs and resource files. It's been a while since I've done it but there is a method using adb commands to chase down if all the radio files are being accessed in sequence to power on radio at boot, at each step, if the next required file isn't there it will tell you, then you just get a copy of that file, push it to where it's needed then continue the chase through the sequence, replacing each missing file along the way until you reach the end of the sequence.

Use the dialer menu codes to access radio settings and verify the values there.

If I think of anything else I'll drop a line.

DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S III] cigikomar:
Hello there,

So after some years I decided to "upgrade" my old vzw i535. Everyone recommended me Lineage (former Cyanogen). So I took an action and started to play with my phone.

Before flashing I had rooted phone and unlocked bootloader and I was at I535VRLEC radio using some modified stock ROM based on 4.0.x ICS Android. I am using the phone in Europe, so back in old days I had to install Phone info app, make it system app using Titanium Backup and switch network mode to Global and manualy add some APNs. Lets say phone was functional.

Now I started flashing the newest lineage, I sticked to the guide in the first post. So I took following actions:

1) switched from CWM to TWRP recovery mode.

2) backup and wipe everything

3) flashed the combination of MF1 / NE1--- firmware/radio using TWRP from invisiblek sites

4) flashed nightly version of Lineage 14.1 vzw

5) flashed magisk.zip (root)

6) installed magisk manager or maby this was already in ROM build I dont remember installing it

And of course problems happened:

1)Seems like my SIMcard(Europe SIM not vzw) or my radio doesnt cooperate with the phone at all - I dont receive any signal, I am not even asked for PIN number during booting the OS - I looked for the similar problems in this topic and in the whole s3 vzw section, some people had the same issues and they solved it with removing SIM, power down, switching network settings ->CDMA subscription to RUIM/SIM instead of NV after that power Up with SIM inserted (tried, didnt help and I had SIM subcription by default with fresh Lineage installed) .

Additional info: I cannot change almost any settings under Settings -> mobile network settings . Everything except CDMA subscription and APNs is grayed out and when I try set the APNs manually, they wont be saved. Then I tried some dial codes: Phone info is working, I can enter mobile network menu and see that I am having no signal :D But I cannot turn ON/OFF radio with the switch button or I cannot change the network mode ( more precisely I can do it, but none of these changes are applied into the phone settings.)

2) I am not sure if this has some relation to firmware version. I thought that by flashing MF1/NE1 combination I should see .....MF1 in firmware version in my about option: Currently I see somethign like Build number: lineage_d2vzw-userdebug 7.1.2 NJH47F and some numbers

Baseband(radio) is alright: i5350YUDNE1

[IMG="Info About phone"]C:\Users\jcn2bj\Desktop\Screenshot_20171123-081355.png[/IMG]

So please does anyone have an idea how to solve it or where could be the issue? I tried few other ROMs (some older Hyperdrive - was functional, OctOS - same behavior as Lineage, but I was able to switch my network to Global, but didnt receive any signal).

Thank you for any advice in advance sorry for the long post...
[Verizon Samsung Galaxy S III] jtnc:
For the second part, your baseband version looks correct. I've had no issues with that one on mine. Though I am using a Verizon sim.

For the first part, I am not sure I can help much. I have not seen that behavior on my s3. I know on my s2 when using it in Costa Rica I had to enter a pin to unlock the sim after a reboot. I think I occasionally saw an issue similar to what you describe when I would flash a new OS on it there. Typically doimg a factory reset and then a reinsrall would fix it. But I have not traveled overseas with my s3 to have to try that. your settings sounded time for Verizon but not sure for Europe.

I have never tried using Magisk with lineageOS as they supply a su zip you can apply to get root. You might try that and see, but I wouldn't think it'd effect what you're seeing.

Good luck

John
[Verizon Samsung Galaxy S III] cigikomar:
Ok, so I just wanted to let you guys know I solved my issues.

My functional procedure was:

1) Back to JellyBean "stock"

2) Do some stuff to switch network mode and add APN manually. I did APN config using HiAPN global app.

3) It was workin on Jelly Bean (I was able to receive cell signal and data also). So I tried MF1/NE1 firmware/radio combo, also working.

4) Flashed Lineage, also working.

5) Happy ending :)
[Verizon Samsung Galaxy S III] dvschnk:
So....it looks like all the d2 branches just lost their maintainer for LOS. Has the S3 finally reach its end?

https://www.lineageoslog.com/14.1/d2vzw
[Verizon Samsung Galaxy S III] Ibuprophen:
Not necessarily...

I believe that the Lineage Team is a bit short handed and, recently, I've seen a little bit of juggling around for some maintainers on a few devices (Maintainers added, removed, re-added, etc...).

Typically, if a device is dropped completely from future builds, it's announced in one or more different ways though, i can't state this as a fact for all devices.

I believe that It used to be [MENTION=2385005]invisiblek[/MENTION], [MENTION=5795145]javelinanddart[/MENTION] & one other...

Then it was just invisiblek & javelinanddart...

Then it was just javelinanddart...

I believe (or should I state that I'm hoping in this case) that some Maintainers are being shuffled for more attention being made on other developments/builds/devices.

I hope that one of the LineageOS Developers can chime in on some type of clarification. Or even just to state that the d2vzw is still being developed upon and the loss of Maintainers is only a temporary change until further notice.

I'm not going to worry about this, personally, until something indicates otherwise.

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

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] javelinanddart:
D2 is no longer maintained. I just don't have time. There's no such thing as "shuffling" maintainers. A maintainer is someone who willingly takes up the device because he/she owns the hardware, and has time to do it.
[Verizon Samsung Galaxy S III] Ibuprophen:
That's why I had stated that post as an assumption and didn't want to make it look like a factual one... :)

Thank you so much for clarifying this :thumbup:

I'm just wondering...

Is this change is a permanent one?

--OR--

Was this change made with the possibility of the D2 development to be picked up by another Maintainer at a later (undetermined of course) date?

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

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] mamarcac:
Thank you for all the fun!

Totally understandable, and the d2 has had an amazing run. Thank you so much for keeping our little guy alive for so long!
[Verizon Samsung Galaxy S III] javelinanddart:
I'm not sure. I thought I made this clear -- it's picked up by someone who has time. If I knew someone who had time, I would've transitioned maintainership to them, instead of discontinuing it.
[Verizon Samsung Galaxy S III] Ibuprophen:
Understood completely...

Thank you very much for your time, patience and support for the d2 developments.

I know that you and [MENTION=2385005]invisiblek[/MENTION] has played a key role in getting the d2 developments to where it is today and I really hope it gets picked up by another developer in time.

Maybe this Lineage team can place a Classifieds ad on the website with a "Help wanted for a d2 developer!"... LMAO!

I'm sure that Unofficial Builds will keep the device alive in hopes of a new Official LineageOS Developer.

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

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] Droidriven:
I'll ask the OctOS d2 guys, I have the team chatter thread and S3 testing thread on hangouts. I've collaborated with them for a couple years now. I'll see what the future holds for d2.

Also, remember that XDA is not the only place that has d2 development. A lot of guys have gone to using Google+ and other platforms to share development instead of XDA to have more freedom with less politics and still stay within the lines.
[Verizon Samsung Galaxy S III] Ibuprophen:
I apologize to everyone for the following... Questionable language... I'm about to state!

I'm a member of other forums as well and I am sure there's more out there that i don't know about too.

I do like the crDroid and the OctOS developments too. I was very impressed with what they've accomplished too.

I remember being invited by a member of the the OctOS team to be a part of their team and i did eventually say yes but, I had unfortunately been getting taken from that by my other developments and commitments and didn't want to abandon my other responsibilities as a developer myself.

Fortunately my primary device is a kltevzw and my alternate device is the d2vzw and others i have as well but, I do use them all for various testing purposes too.

Your a very good member Droidriven and I appreciate your input. Please let me know if you make any headway with the other developers.

Also, you can PM me for this to prevent any thread hijacking charges from the XDA police. LMAO!!!

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

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] mamarcac:
Did not know this...thanks for sharing. Also, OctOS has always been the most stable on my d2, that team just seems to have it locked in on their builds. I actually have 2 fully working d2's and would love to keep em alive but zero expectations understanding the effort that it can take.
[Verizon Samsung Galaxy S III] ombikram123:
Hhh
[Verizon Samsung Galaxy S III] hasan.sy:
is there any news about maintain d2 devices ? hope we get los15.1 on it or the end?
[Verizon Samsung Galaxy S III] Ibuprophen:
Based on what [MENTION=5795145]javelinanddart[/MENTION] had stated, earlier in the forum, i hope that I have the following correct {And please keep in mind that this is regarding the Lineage Team and work as a whole.}...

Due to the limited number of Lineage maintainers (aka developers), as well as the workload, they had to drop the d2vzw device until further notice.

Based on the Official LineageOS Device Info pages, for all the S3 devices, the one that still has a maintainer (who is "forkbomb") is the I9300 (aka Samsung Galaxy S III - International).

I vote to drop ALL but, the d2vzw... LMAO!!! (just a joke).

Just keep in mind that there's other custom ROM's for this device that are still being maintained (Both Official and Unofficial) and I'm pretty confident that this device will have a custom ROM of Android Oreo soon since i believe that this device has and will continue to remain strong for a long time.

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

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] Droidriven:
Any of the d2 ROMs can be flashed on any other d2 device with a few modifications involving rilblobs, APNs, build prop edits and a few other minor things maybe, they are about 98-99% the same. They can be flashed as is and then modified on the device after flashing or they can be ported, about the only differences between the d2 variants is bootloader and modem. Try this thread.

https://xdaforums.com/showthread.php?t=2069850

Post #2 is where you need to start then go from there piecing together what you need. Android versions have changed since then and CM switched to LOS so there may be some additional stuff required that isn't in that thread.
[Verizon Samsung Galaxy S III] javelinanddart:
You managed to completely misconstrue something I thought I said very clearly. It's _me_ not having time to maintain it. Maintainers are not allocated to devices; it's not us dropping d2 because the project can't maintain it, it's me dropping d2 because I can't maintain it.
[Verizon Samsung Galaxy S III] Ibuprophen:
I deeply apologize if I had offended you. :(

I never intended to "misconstrue" anything. I had placed a caveat in the beginning of my statement that was intended for corrections if I was wrong.

Please forgive my misstatements... :o

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

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] doug_scott:
Not sure this is the correct place for this so...

I am using a Huawei GR5 (KII-L05) phone, running LineageOS 7.1.2 build from January 17. I am having issues of very slow WiFi data transfer speeds. I recently tried my friends phone(exactly same phone as mine, except not rooted and is running the current supported version of Android, 6.0) and got transfer speeds of about 10mbits. My phone barely gets 10% of that, run seconds later, through the same access point. Mobile data rates are the same on both phones. Is there some setting difference between the two operating systems? I have been running LineageOS since about last July, and I am pretty sure it was not this slow until the last couple of months. Any ideas?
[Verizon Samsung Galaxy S III] Ibuprophen:
This is not the correct thread (as you can see by the thread title).

The following is the Official LineageOS thread for your device.

https://xdaforums.com/showthread.php?t=3528488

If all else fails, then your next best bet is the following Q&A thread that's specific to your device.

https://xdaforums.com/showthread.php?t=3525734

Good Luck!

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

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] doug_scott:
Silly me, I was simply following the recommendation of a user who sounded like he knew what he was talking about in this thread..

https://xdaforums.com/lineage/help/extreme-slow-download-speed-lineage-os-t3564897/post75225729
[Verizon Samsung Galaxy S III] Ibuprophen:
That was my bad... I do apologize for this! :eek:

EDIT: My deepest apologies to [MENTION=1271889]doug_scott[/MENTION] for providing the incorrect thread link. The following, original, thread post was just appropriately edited with the correct thread link.

https://xdaforums.com/lineage/help/extreme-slow-download-speed-lineage-os-t3564897/post75225729

Thank you very much and I wish you the best of luck!

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

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] Droidriven:
You clicked the wrong link in the other thread. [MENTION=4828250]Ibuprophen[/MENTION] answered two different people, one of those people he gave a link to this thread, he gave you a different link. You clicked the link that he placed above your quoted post and he placed a link below your quoted post. You were meant to click on the one BELOW your quoted post, NOT the one ABOVE your quoted post, that was meant for the other member that he replied to. When someone replies to more than one post at once and yours is one of the posts replied to, their reply to YOU will be below your quoted post in their reply.

Understand?

Edit: disregard, I've been informed that the multi-post I referred to was edited prior to my reply. I'm still going to leave the post as I left it because I have seen other members that do get the multi-posts confused and lose track of who is replying to whom and who "this" or "that" information is intended for. This may help them understand.
[Verizon Samsung Galaxy S III] sheffy6:
Bootloop after flashing

Hi everyone. Is anyone having boot issues after flashing this rom? My device is stuck in a bootloop where the screen shows the loading animation for a while, then goes black, then shows some scrambles pixels at the top, and finally reboots. I've had the same results with OctOS M, OctOS N, CM 14.1 and now LineageOS 14.1. If I flash back to CM 10.2 it boots fine. At one point, I flash 10.2 and then 14.1 on top without wiping and it showed the updating screen on the first boot, but then started the boot loop. Not sure what's going on. Any ideas? Thanks in advance!
[Verizon Samsung Galaxy S III] sheffy6:
Ok, RTFM wins the day... I didn't see that I needed to update the firmware/modem. Once I did that it booted with no issues.
[Verizon Samsung Galaxy S III] hasan.sy:
Update your device to latest firmware and bootloader 4.3 you need latest bootloader on cm12 and up
[Verizon Samsung Galaxy S III] Droidriven:
As far as I know, the latest 4.3 bootloader is locked. I know d2vzw needs to flash the latest modem but that's the first I've seen anything said about the newer bootloader. I know that the first version of stock 4.3 for d2vzw was bootloader unlockable but the 4.3 update that followed that was bootloader locked and after taking that bootloader update, custom recovery and ROMs won't work.
[Verizon Samsung Galaxy S III] momin73:
How can I install this