yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mjb32803:
New Build Available!!!

Santa left a new build under the tree.

Download link is in Post #1

Included the Dec 5th Android Security updates!

Changes inherited from the i9300 include:

Remove unrecognized compiler flag 2018-12-27 22:40 UTC (android_external_v8)

Revert "Backport: Fix Object.entries/values with changing elements" 2018-12-27 22:40 UTC (android_external_v8)

Bump Security Patch Level to 2018-12-05 2018-12-18 13:43 UTC (android_build)

RESTRICT AUTOMERGE: Recover shady content:// paths. 2018-12-16 23:51 UTC (android_frameworks_base)

Pass userId through to singleton ContentProviders 2018-12-16 23:51 UTC (android_frameworks_base)

CTS error while media dump() 2018-12-16 17:24 UTC (android_frameworks_av)

Fix possible OOB read 2018-12-16 16:55 UTC (android_system_bt)

DO NOT MERGE - Check SDU lower bound before allocate p_data 2018-12-16 16:53 UTC (android_system_bt)

Changing SUPL_ES=1 for SUPL end point control 2018-12-16 16:24 UTC (android_frameworks_base)

Track own update-engine 2018-12-16 16:03 UTC (android)

Check metadata size in payload. 2018-12-16 16:03 UTC (android_system_update_engine)

Add limits check for the CTB position in a frame 2018-12-16 15:37 UTC (android_external_libhevc)

Fix signedness mismatch and integer underflow 2018-12-16 15:36 UTC (android_system_vold)

Prevent OOB error for T2T read/writes 2018-12-16 15:35 UTC (android_external_libnfc-nci)

Prevent out of bounds accesses in lppTransposer() 2018-12-16 15:34 UTC (android_external_aac)

libwebm: Cherrypick 5a41830 from upstream 2018-12-16 15:20 UTC (android_external_libvpx)

sepolicy: Allow adbd to set a system_prop 2018-11-29 00:24 UTC (android_vendor_cm)

macloader: Add new mac addresses for semcosh and and murata Observed on new s7 models 2018-11-27 22:27 UTC (android_hardware_samsung)

Fix making adb use a custom prop for adb root 2018-11-27 14:34 UTC (android_bootable_recovery)

Make adb use a custom prop for adb root 2018-11-26 21:10 UTC (android_bootable_recovery)

Make adb use a custom prop for adb root 2018-11-26 19:49 UTC (android_packages_apps_Settings)

Make adb use a custom prop for adb root 2018-11-26 19:49 UTC (android_packages_apps_TvSettings)

Make adb use a custom prop for adb root 2018-11-26 19:48 UTC (android_frameworks_base)

Make adb use a custom prop for adb root 2018-11-26 19:48 UTC (android_system_core)

Label cm.service.adb.root as system prop 2018-11-26 19:48 UTC (android_vendor_cm)

Add sampling rate sanity check 2018-11-23 14:47 UTC (android_external_aac)

Break audio element loop in case element_count becomes too large. 2018-11-23 14:46 UTC (android_external_aac)

Prevent bit buffer counter overflow. 2018-11-23 14:46 UTC (android_external_aac)
[Verizon Samsung Galaxy S III] mjb32803:
Request for specific feature testers!

I run a Netgear R7000 and R6300v2 router at home, both loaded with DD-WRT firmware (Kong builds).

For many months, I've noticed that I cannot connect ny S3 (and my Nexus 7) to the 5G band on either wifi router.

I have no issues connecting to 5G band with my Nexus 6. Both the Nexus 6 and 7 run stock Lineagos 15.1

All other wifi products in my house (Roku, Essential PH-1) also connect to 5G wifi with no issues.

I'm trying to figure out if the issue is with the wifi driver in the S3 and Nexus 7, or the issue is with DD-WRT firmware.

If anyone is using a wifi router with DD-WRT installed, I'd appreciate feedback on whether you can connect to the 5G band on your S3?
[Verizon Samsung Galaxy S III] Strephon Alkhalikoi:
With CDMA shutting down at the end of next year, these devices are going to be limited to WiFi for connectivity, at least that's how I understand it. So there's little point to updating them since anyone still using one will be forced into an upgrade anyway.

If I'm misunderstanding the situation, feel free to educate me.
[Verizon Samsung Galaxy S III] Ibuprophen:
Huh... :eek:

The following link is to this specific announcement...

https://www.verizonwireless.com/support/knowledge-base-218813/

... where it states:

I don't recall ever noticing if the I535 falls under this specific category.

I'll look into this myself to see but, I wouldn't doubt if it did either... :(

EDIT: Just an FYI... The following link reflects the Frequency Bands/Capabilities for the I535 device...

https://www.frequencycheck.com/models/GPXaz/verizon-samsung-sch-i535-galaxy-s3

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Verizon Samsung Galaxy S III] Strephon Alkhalikoi:
Thank you for providing the links. I had found all of that info but was not in a position where I could provide the links, being out and about. The I535 doesn't have HD Voice support to the best of my knowledge, and the bulk of its frequencies are using 3G. Therefore, Verizon will not activate it. The Straight Talk S968C (uses Verizon towers) acting as a desk clock and information station on my desk is already dead in the water. It was deactivated a year ago, and with it not having LTE at all cannot be activated, period.

If the device is already activated, then it will continue to function until Verizon shuts down the network. So if you haven't upgraded, you have until they shut down the network to do so.
[Verizon Samsung Galaxy S III] mjb32803:
Someone with a SIM card I their phone, please check under settings, network, and see if d2vzw supports VoLTE , HD Calling, or Advanced Calling Features. It's been so long I don't remember.
[Verizon Samsung Galaxy S III] Ibuprophen:
My GS3 was accidentally left at my Brothers House... LMAO!

It should be dropped off by tomorrow but, to answer your questions.... YES, and actually the Samsung Galaxy S3 is the first Galaxy device that was given this feature within their release of the Android 4.4.2 Firmware.

The Verizon Samsung Galaxy S3 (I know, at least, Sprint and T-Mobile as well) supports "HD Voice" aka "Voice Over LTE" aka "VoLTE" aka "Advanced Calling".

I do believe that Verizon is the only carrier that referrs to this feature as "Advanced Calling" but, I could be wrong since I'm going by memory myself.

I did locate some references regarding this feature via the following links (if your interested):

The following has a reference stating "The S III was the first smartphone to support Voice Over LTE".

https://en.wikipedia.org/wiki/Samsung_Galaxy_S_III

Just a little discussion thread regarding it.

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

The following is an article that uses the GS3 statement "Samsung Galaxy S 3 for VZW (SCH-I535) antennas (3 for cellular)" as an example of what's lacking on a specific iPhone for this feature.

https://www.anandtech.com/show/6295...ous-voice-and-lte-or-evdo-svlte-svdo-support-

The following is a KB Article regarding the Activating HD Voice on the Android.

https://www.verizonwireless.com/support/knowledge-base-130983/

The following is an FAQ regarding an the HD Voice for Android.

https://www.verizonwireless.com/support/hd-voice-for-android-faqs/

I hope this is helpful for you! :)

Happy New Year My Friend!

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Verizon Samsung Galaxy S III] mamarcac:
Hi there, thanks for all of your builds, and now I can finally help _you_ for once. I have a Netgear R8000 as the main router and (2) WRT54G-TM's as access points downstream. I ran DD-WRT on the R8000 for a year and have had the old Mega build of DD-WRT on the WRT54G-TMs for several years now, and the S3 never had issues with either one (I had it on the 5 GHz channel of the R8000 and it would switch to the 2.4 GHz channel on the WRT54G-TM's when roaming). I have since changed the R8000 to Tomato Shibby for better stability, and have had no issues there either with my S3. I have however reverted the S3 to 4.3 firmware and re-purposed as a music server.

Dumb question, have you played with the 5 GHz channels? My old Samsung SM-T230NU and Roku's will only see certain 5 GHz channels so I'm thinking it's related to that maybe. I know DD-WRT opens up 5 GHz channels that are non-standard in the US (if that's where you are). https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax)
[Verizon Samsung Galaxy S III] mjb32803:
Thanks for the info. I have my R7000 and R6300 both set for the US Regulatory Domain. My S3 can "see" both wifi 5GHz SSIDs, and I can even "connect" to input a wifi password... however the connection always fails. I've tried switching channels, and channel width, but nothing seems to make a difference. I only have this issue on two of my devices, the S3 and my Nexus 7 tablet (both running Lineage. My Nexus 6, also running Lineage will connect to 5GHz with no issues. My S3 has no problem connecting to my neighbors R6700 5GHz, which is running stock firmware.

This has been a tough quirk to solve....
[Verizon Samsung Galaxy S III] rholm:
Installed yesterday on my SIII. Works awesome! It is amazing how well it works. Brought back some nostalgia, I really loved this phone. While I used a custom ROM on my Samsung Charge, this was the first phone I modded in a big way.

Thanks!

Cheers,

Rich
[Verizon Samsung Galaxy S III] bmeek:
Thank you, [MENTION=4013543]mjb32803[/MENTION]!

As per your request to raise a hand if using these builds, I'm flashing now to my old d2vzw that still mostly lives (it has a dead power button that I can compensate for using a Play Store app called "Button Savior".)

FWIW, I've decided to try using it as a wifi-connected Roku remote (with Private Listening via Bluetooth) while my main phone is acting a WiFi hotspot to put my granddaddy vzw unlimited data plan to use for binge-watching Netflix, etc. on the big-screen.

Edit: After updating TWRP and flashing the ROM with a fresh download of OpenGAPPs-mini, all worked well (as expected). I then flashed the latest Magisk and installed the ViPER4Android/FX module to ratchet up my Bluetooth audio experience... Excellent! It's all working perfectly.

Thanks again,

-- brian
[Verizon Samsung Galaxy S III] mjb32803:
New build coming soon

The January security patches just dropped yesterday, so I am attempting a build right now. Will know in about 30 minutes. Standby.
[Verizon Samsung Galaxy S III] mjb32803:
New build available for download

Instructions in Post #1

We finally got Jan 5th, 2019 security patches.

PLEASE READ: This build was NOT tested with any Gapps installed.

WHY: This is part of a broader experiment to see how frustrating it is to use Android, Google Free.

I am using F-Droid with Yalp to install most of my preferred apps.

The only Google apps I routinely used are Maps and Voice.

Of course this means I will not be able to test my builds as thoroughly.

I don't anticipate this to be too much of a risk, but you never know.

For everyone's benefit, It would be helpful if a couple of users could verify proper functionality with Gapps and post accordingly.

ps. My phone is working just fine.

I do NOT have a cellular plan on this phone, so it is configured in Airplane Mode, with WiFi and Bluetooth ON.

Tested GPS with OSMAND, Bluetooth, WiFi, Firefox, K9 Mail, external uSD storage.

Up and running since yesterday so I was confident enough to post..
[Verizon Samsung Galaxy S III] Ibuprophen:
I had been asked some questions (Sporadically) that primarily involves obtaining one or more of the Baseband Modem Updates specific to the Verizon Samsung Galaxy S3 (d2vzw) device.

They all can be obtained on the following thread that I had created quite some time ago and everyone is more than welcome to them.

[MODEMS]Verizon Samsung Galaxy S3{SCH-I535/D2VZW}[ODIN] by Ibuprophen

Thanks a bunch! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Verizon Samsung Galaxy S III] bmeek:
9 Feb build running fine with GAPPs

I just dirty-flashed the latest build from 9 Feb 2019 over your prior build that I had configured with OpenGAPPS (ARM / 7.1 / mini) and Magisk v18.1 (with Busybox and VIPER4Android FX modules). Both GAPPs and Magisk survived the dirty-flashed LineageOS update process... Everything seems to be running fine.

Thanks again, [MENTION=4013543]mjb32803[/MENTION], for taking the time to make these builds and keep these old devices pluggin' along.
[Verizon Samsung Galaxy S III] J-Lindo:
Word is Lineage has officially dropped support for 14.1. Will we get one last home-cooked build for the road?
[Verizon Samsung Galaxy S III] mjb32803:
Looks like 14.1 has come to an end.

I just did a sync repo to grab the last of the changes.

Looks like we will get the Feb 2019 security patches plus about 10 more security/bug fixes.

There hasn't been any other activity since Feb 21st.

I'm building now... update will follow later this evening.
[Verizon Samsung Galaxy S III] mjb32803:
New Build Available

New build is available to download. Instructions and download link in Post #1.

The d2vzw still lives! New build with the Feb 2019 security patches.

The file size grew about 800 KB to 300.7MB (which had me worried), but I installed and it is working for me.

Reminder: I am still running my test phone WITHOUT GAPPS installed, so my testing is limited.

Speculation: As long as "generic" LOS 14.1 changes go into repository, they "should" get sucked into my builds. We will no longer get Samsung Galaxy S3 specific updates, since the I9300 has dropped 14.1. I am hopeful that we should continue to get the security patches as long as 14.1 is still maintained. Thoughts anyone?
[Verizon Samsung Galaxy S III] Ibuprophen:
All i can think of suggesting is to see what & where the following Unofficial LineageOS 15.1 & 16.0 builds for the I9300 device are obtaining those applicable updates that were being obtained from the same source as you were getting yours from.

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

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

Let's keep our fingers crossed My Friend! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Verizon Samsung Galaxy S III] bmeek:
Dirty flashed over previous build and all is well (same config as last time - a WiFi-only mini tablet). Thanks again!
[Verizon Samsung Galaxy S III] J-Lindo:
Funny TWRP for S3 still gets updates despite no further ROM development :confused:
[Verizon Samsung Galaxy S III] jasonmerc:
I want to flash this to my friend's Verizon S3, but he wants a stable ROM. It's been a while since I was in the S3 ROM scene so I'm out of the loop. Can anyone tell me a list of what's not working? I didn't see a what works/doesn't work section in the OP

Thanks!
[Verizon Samsung Galaxy S III] Ibuprophen:
I haven't, personally, found anything wrong myself...

I would state that this is pretty stable.

Unless someone else has any additional feedback here.

Good Luck!

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] singingandroid:
My only complaint was that the phone ran hot, leading to poor battery life. Possibly doing some kernel tweaks with a Kernel Manager like Kernel Adiutor or a similar app would help. Personally I moved on to an LG G3 running AICP 13.1.
[Verizon Samsung Galaxy S III] jasonmerc:
Thanks for the quick response, and once again thank you for the work you're putting into this thing. It's cool to see a phone this old still get so much love from the community
[Verizon Samsung Galaxy S III] noidodroid:
I was running this version that I themed. I had a few issues but more than likely that was due to the theming.

Off subject.. I hard bricked (9008 atm) my TFN S3 on H1 last nigh. Still can't figure what files i flashed would have done it when installing a base rom and trying to get multirom going for d2vzw. I'm still searching for a working H1 debrick image or anything unlocked still (need to check and see where the OTA doomed this). I had an image i downloaded from the start but my connection isn't the most reliable as of late so i am just now finding out the archive is corrupt.. Hopefully i can backtrace to find it here where i obtained it. Great to see that the S3 is still chugging along with the latest TWRP.

I now have a 12GB organized repository put together for returning here in a thread compiled if i get this little guy out of brick status. Took a lot of deep searching to find files no longer present on here. (AS Usual for these older devices) Maybe when i get time i will also mirror a lot of what i have compiled ./ done on devices older and newer so that people once have access to these golden oldies and modded newies.

---------- Post added at 10:12 AM ---------- Previous post was at 10:02 AM ----------

Thanks for the help bro. I have been busy on this S3 the past couple of days and found the pick of the litter for the most part. Got some tested then he up and went to 9008 land. lol Hopefully I can fix this issue without need of TP's as im not that experienced in using TP's yet as you know from my first Orbic Wonder TP experiment.

I have some copies of Lineage OS more current that whats on here just won't know their stability / reliability and all that good stuff just yet. Tersted up to roms up to 6.0 for a bit.

---------- Post added at 10:16 AM ---------- Previous post was at 10:12 AM ----------

I look forward to testing it out and submitting feedback. Thank you for you contribution to the community. I have ran some of your work i believe on other devices and all has went well from what I remember.
[Verizon Samsung Galaxy S III] Teracotta:
hi will this work with d2usc

I flashed d2tmo on d2usc, it works but not baseband, because all US S3 have same SoC/PIT...but!! need CSC specific for TMO, ATT to properly access LTE now with CDMA gone

I see LOS 14.1 randomly on google, by h2h but I do not trust..
[Verizon Samsung Galaxy S III] Ibuprophen:
It might work since US Cellular does lease the Verizon towers.

I can't confirm it since I don't have that variant device myself.

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] Teracotta:
ok I'll give it a shot

how is LOS handing the csc/baseband on these older androids, is the csc just ported from qualcomm or do you make mods to it
[Verizon Samsung Galaxy S III] Ibuprophen:
The builds here for the LineageOS 14.1 looks like it's not going to be progressing any further than 14.1 because it requires an updated kernel that either hasn't been released, released yet or doesn't exist to be released (though the last one looks like it).

With that stated... The LineageOS 14.1 for the d2vzw is really a good build and I really don't run into any issues much at all. It's been quite some time since I had any issues and I only recall very minor ones that was more of 1 or 2 app compatibility items.

I had just recently been able to get a hold of the (PDF package) Samsung Factory Service Repair Manual for the SCH-I535 device.

I have 2 of them along with a selection of the newer Galaxy devices that I hold on to for backup but, primarily, for testing purposes.

Good Luck!

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm just curious as to any updated builds [MENTION=4013543]mjb32803[/MENTION]?

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] Teracotta:
[MENTION=4013543]mjb32803[/MENTION]

I'm using the latest build on d2usc

Phone boots fine but sim card is not detected.
[Verizon Samsung Galaxy S III] Ibuprophen:
This may not be working out for your specific variant.

I wasn't 100% sure if it would work myself.

I wish I had a resolution for the USCC variant... :confused:

EDIT: You may be able to obtain something specific for the d2usc by checking out the following post & threads.

https://xdaforums.com/showthread.php?p=76442620

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

The following threads were builds for Custom Firmware that were for the d2lte that was supposed to work for the d2usc device too. It's been a while since I even used any of them.

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

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

The following one might work for you as well. You should be able to obtain a confirmation on that thread if you ask.

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

I also just remembered that I have some old CyanogenMod 11 builds on my AFH Server for the d2lte if you're interested.

https://www.androidfilehost.com/?w=files&flid=148387

I know that they're a bit dated but, this is about it on the XDA Forum that I can locate.

Good Luck!

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

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S III] mjb32803:
My d2vzw has moved on to electronics heaven, so I will no longer be providing updated builds.

I will leave the last builds in my dropbox until the end of the year.
[Verizon Samsung Galaxy S III] blueman2:
I just updated to the last version provided by [MENTION=4013543]mjb32803[/MENTION] and all is working great. Thanks so much, mjb32803, for sharing your work with us.
[Verizon Samsung Galaxy S III] mjb32803:
Long time since I've been back, but thought I'd mention that I did manage to resurrect my d2vzw. I'm going to try and setup a build environment again. I'm not even sure if it's still possible to collect all the files I'd need, but I'm going to give it a shot over the holidays. Would still be an unofficial 7.1.2 build, but likely only include security patch updates (if it even works). Wish me luck.
[Verizon Samsung Galaxy S III] thelangosta:
I got mine working again yesterday. Not exactly sure what I did but it booted up. Good luck
[Verizon Samsung Galaxy S III] decibel23:
I would love to have an updated version of this build. :D
[Verizon Samsung Galaxy S III] Jason Roach:
dude, i wish you were still working on this.
[Verizon Samsung Galaxy S III] Teracotta:
I obtained an i535, I unlocked the bootloader but when flashing LOS 14 I got "unauthorized software" error. Explanation?
[Verizon Samsung Galaxy S III] mjb32803:
My build is for the Verizon version only.
[Verizon Samsung Galaxy S III] mjb32803:
Not sure if anyone is still using this phone, but I will be deleting all the files from my dropbox very soon, so none of the download links will work afterwards.
[Fire TV Q&A, Help & Troubleshooting] clint3421965:
my fire tv 2nd gen is showing 2 diff. ip's but one mac address in my router attached devices window . netgear WNDR4300v2

192.168.49.1 is showing whether i connect my fire tv , wired or not wired, to my network. it shows as UNKNOWN under DEVICE NAME

this just started recently .

not sure why this started, JB
[Fire TV Q&A, Help & Troubleshooting] BRICK0044:
Do you have a different launcher by chance? The reason I ask is mine shows that same ip address when using Halauncher if I enable "show ip" in settings. I can only adb into it using the ip I get from settings.
[P8lite Q&A, Help & Troubleshooting] Hawathan:
Hi,

My phone is on B196 fw, rooted, TWRP w/o problem. OTA update B198 just appear as FW update notification. I've flashed back to stock Recovery (B170) and rebooted. When I've tried the OTA B198, phone fails using the 330 MB patch and switches to the download of the FULL version. After downloading the file, I'm getting checksum error every time I try so I can't perform the OTA update. What I'm doing wrong? Do I really need stock Recovery B196 for doing this OTA update?

Thanx in advance for any help.