yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] YabbyYou:
AH! That is crazy! Very impressive! Keep us posted, and if you need help debugging or whatever, please let us know.

PS - Now that you posted that picture no one is going to answer my OT question about non vzw sim cards!
[Verizon Samsung Galaxy S III] AyUaxe:
All indications are that you can use a sim from a gsm provider. Pretty sure there were some posts about that in the L threads. Presumably have to flash the gsm ril blobs file that's been in an extras folder linked in the op since [MENTION=2963287]mastamoon[/MENTION] unofficial L days. http://mastamoon.truelinux.net/other/d2gsm_rilblobs.zip

All that said, I used the vzw international plan in UK a few times and it worked pretty well. Only prob was limited/expensive data. I still plan to try a gifgaf sim, now that I've got another phone, but haven't been able to get out of the USA. Not that home sweet home's a bad thing--'Murica-f__k yeah! Jelly, re: BVI! Enjoy!

---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------

[MENTION=2385005]invisiblek[/MENTION], may I be an alpha tester? Lil d2 that could is a media device these days, so as long as she's not bricked and has backups, she'll try anything. Lemmeno, bitte schon. Awesome work BTW!
[Verizon Samsung Galaxy S III] YabbyYou:
[MENTION=3056030]AyUaxe[/MENTION] thanks for the info. I didn't realize I would have to flash something else, not sure I want to do that while I'm on vaca. Verizon has an option called TravelPass that lets you use your global phone internationally. You can add it to your account, it costs $10 a day. The description says it lets you use your plan minutes/data just like if you were here in the US. Seems like a good deal, especially for someone with unlimited data. You only pay the $10 if you use it, so if you don't use it one day, you don't pay, which also seems good. Granted, $10 might be a little pricey if you just need to check something, but on the flip side, it would be nice to know I could pull up Google Maps or something if I need to. Now that I think about, do you think I still need the gsm ril blobs if I'm trying to use any GSM networks? I'm not too familiar with the purpose of the gsm ril blob, is that only needed for GSM SIM cards or does it actually enable the GSM bands on the radio?

It's my first time heading down to BVI, so I'm really looking forward to it. I've been to a bunch of other islands around the Caribbean but not BVI yet!
[Verizon Samsung Galaxy S III] AyUaxe:
I honestly don't know the tech of how it all works. My assumption is that the ril blobs do activate the GSM bands in the radio, but that may not be necessary on a Global-enabled phone like D2vzw is stock. I didn't have to flash anything or replace my USA VZW sim when I had VZW in London. I think I might have manually reset my "Cellular networks/Preferred network type" to "Global" or "LTE/GSM/UMTS" to get everything working, but that's about it. I just keep the gsm ril blobs zip on my sd card, just in case and regularly make new backups when she's running well (deleting the prior one, though I keep an old L backup that's revived GPS and such a few times when it got messed up). I will eventually try a gsm sim just to see how it works and of course I'll post results. Though D2 isn't my DD anymore, I do like for it generally to work, b/c it's my go to media device now.

Sounds like that VZW plan, combined with unlimited data, would be pretty difficult to beat for purposes of a limited time vacation! Hope yours is excellent!
[Verizon Samsung Galaxy S III] Jaws4God:
WOW! i was curious about this on the old S3 since I had to resurrect mine.. :D
[Verizon Samsung Galaxy S III] Lrr_r:
I've tried flashing that zip over the 8/30 nightly and it didn't seem to have any effect (I've seen it work with CM 12.1).
[Verizon Samsung Galaxy S III] YabbyYou:
You flashed it and tried to use a GSM sim card?
[Verizon Samsung Galaxy S III] Lrr_r:
Yes I have a GSM card inserted. The "Preferred network type" menu didn't gain any GSM-related choices, there wasn't a menu item to see available GSM networks, basically everything looked the same. It's possible the blobs might just need to go into some other directory with CM 13, I didn't care to investigate because switching networks by flashing zips is of little value to me.
[Verizon Samsung Galaxy S III] AyUaxe:
But bottom line, is gsm working for you? Do you know what gsm channels or frequencies you had before and after flashing the rill blobs? Enquiring minds want to know! Thanks!
[Verizon Samsung Galaxy S III] AyUaxe:
I got no audio except on BT with 9/4, so back to 8/14 and all audios are back. 9/4 seemed otherwise very good. Using latest dkp with both, so don't think it's a kernel prob. Champing at the bit to flash a wildly unstable N!
[Verizon Samsung Galaxy S III] vforaci:
I too would like to know the resolution. I travel to Mexico sometimes and since CM12 I had issues. I now know to flash the ril zip file but it appears it's not working in CM13. I liked it better when the ROM was global several versions back.
[Verizon Samsung Galaxy S III] Roger W:
Successful update to 9/8 to get this month's security fixes. I can confirm what was posted last week that the bluetooth problem from December is fixed - I can now use both Phone and Media profiles together without the phone crashing!

And to AyUaxe's point above, audio works fine for me through builtin speaker, headphone, and BT.
[Verizon Samsung Galaxy S III] AyUaxe:
Roger, Roger

Thanks for the update and BT details! Will flash forward and report but I want the one after 9/09 (h/t Lennon/Beatles) or some other "lucky" number.

But more importantly, where can I find that N Alpha?
[Verizon Samsung Galaxy S III] Jaws4God:
so is N Alpha now fully functioning for the S3 ??! :D
[Verizon Samsung Galaxy S III] RashidVet:
every thing works fine , but how to root it ?
[Verizon Samsung Galaxy S III] Jaws4God:
excited to hear more about N for S3! :D
[Verizon Samsung Galaxy S III] AyUaxe:
Sorry, Jaws. I'm basicly trolling [MENTION=2385005]invisiblek[/MENTION], though he's too cool to take the bait. AFAIK, all the N we've got is what he showed us in that tease screen grab a few days ago. I'm still happy to test though since my Lil D2 that could isn't a dd.
[Verizon Samsung Galaxy S III] Jaws4God:
yeah mine is my DD right now.. wish i could get something a little newer with a better camera... just can't really afford anything right now..

AICP 6.0.1 does fairly good.. but does have hiccups from time to time.. i say that now after i had to reboot about 4 times to get the camera back working... think it was omni switch.. idk.. lol
[Verizon Samsung Galaxy S III] AyUaxe:
Tough to beat the 8/14 CM build for smooth, quick, and stable. I just had what I think is the first app crash reboot (something weird with a very old "torch" app I've used off and on since A855 days) since first flashing that build. Even though she's not my DD, she's always on as my primary alarm and media device, so that's a lot of hours with no hiccups. I still use the camera some, though the XT1254 camera does seem superior (mostly, lense hasn't been abused as much yet), so it is the camera I'm using more now.

I'm about to flash forward to the one after 9/09 or so, so I'll let you know how it is.
[Verizon Samsung Galaxy S III] Master Cylinder:
On 12/20 and front facing camera still hosed. However, there is a new Xposed framework v79 out that is claimed to solve the crashing and bootloop issues of v78 - check the last post on that thread. I'm running it with Gravity Box 6.0.3 which came out today and everything seems to be working without meltdown, so far.

:D

---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------

Even disabling all of the button actions of the stock framework and activating all of the GB button controls. This gives me the capability to implement OmniSwitch as my recents controller via Home long press, plus get a screenshot via a back button double tap (I don't have a power button so I need a way to get a screenshot.)
[Verizon Samsung Galaxy S III] LegoFarmer:
Why am I having a hard time installing gapps? I've tried three different zips from the linked website. Installation abort everytime.
[Verizon Samsung Galaxy S III] Fenix2002:
Interesting. Haven't heard anyone else with this issue. You're downloading the ARM Android 6.0 GApps from OpenGApps? Maybe it's an issue with the most recent build from them. Are you doing ROM, then GApps, with no booting in between?
[Verizon Samsung Galaxy S III] LegoFarmer:
I'm switching to TWRP. Pretty positive it'll fix it.
[Verizon Samsung Galaxy S III] Fenix2002:
Aha. Yeah, TWRP in my experience seems to work well.
[Verizon Samsung Galaxy S III] LegoFarmer:
Worked with TWRP Lol swag
[Verizon Samsung Galaxy S III] Fenix2002:
Win. Were you using CWM or PhilZ before? If you prefer that format of recovery over TWRP, CyanogenRecovery is the modern revival of CWM.
[Verizon Samsung Galaxy S III] LegoFarmer:
Loved Philz (: What is CyanogenRecovery and how do I get it? Will it be as reliable as TWRP?
[Verizon Samsung Galaxy S III] Fenix2002:
I've actually never tried it. It's available from the CyanogenMod website for our device at https://download.cyanogenmod.org/?device=d2vzw.

You can download it and install it like any other; I've used Flashify (from play store) in the past to change recoveries. From new builds of CM, in the development settings menu you can choose to install Recovery, and so if you update to the latest nightly from the built-in CM updater, it should install CyanogenRecovery automatically.

Like I said though, I've never used it. From everything I've seen though, it's more like CWM. :good:
[Verizon Samsung Galaxy S III] LegoFarmer:
Just did it. It's not bad. My camcorder isn't working with CM13 (stock app), is yours? It does with this other camera app I installed
[Verizon Samsung Galaxy S III] Fenix2002:
Good to know that it worked for you.

As far as camera on CM13, it's still a work in progress. I've had varying levels of success with stock camera, Google camera, and Open Camera. So far nobody's having much luck with the front camera, but the back camera works for photos and videos for most people.
[Verizon Samsung Galaxy S III] LegoFarmer:
Hmm, I Can record, and take pictures from both camera sides using Open Camera
[Verizon Samsung Galaxy S III] Fenix2002:
Sorry, I haven't tried the latest nightly. As of my testing with 12/20, front camera was still having issues. 12/21 might have fixed those issues! :) Going to download and test it now, because that's one of the things I've been waiting for!
[Verizon Samsung Galaxy S III] Master Cylinder:
Just to report: I've been having SystemUI meltdowns today. So, I still think it's related to GB. I may try some other modules that impact the SystemUI or framework (or whatever) and see what happens.
[Verizon Samsung Galaxy S III] Fenix2002:
What exactly does GB affect? I've never tried it, tbh.

Also, is anyone else having issues with front camera still? All camera apps still crashing phone on front camera for me. :(
[Verizon Samsung Galaxy S III] LegoFarmer:
GB meaning? Also, how is your battery life?
[Verizon Samsung Galaxy S III] charliepop:
I'm on 12/22. Front camera still wouldn't work. Disabled stock camera through titanium backup and installed open camera. Everything is working including front camera.
[Verizon Samsung Galaxy S III] LegoFarmer:
Is it cool to dirty flash nightlies? Don't want to clean flash from 21 to 22 lol
[Verizon Samsung Galaxy S III] stevet86:
Haven't had any problems with dirty flashing. I've been flashing with delta updates also.
[Verizon Samsung Galaxy S III] charliepop:
No problems here either.
[Verizon Samsung Galaxy S III] Jaws4God:
do you have the link for the 8/14 build?. thanks.
[Verizon Samsung Galaxy S III] AyUaxe:
I guess I'll have to put my copy up in mega or something. Might take a while as work intrudes. I'm still having issues with audio--tried 9/8 and 9/10, no on board audio on both for me. Even flagged without dkp and DD+, still no dice, though system sounds worked. Almost makes me think the latest stage fright patch is playing havoc. But just for me, I guess. Jaws, if I were you, I'd make a good backup, then flash a current build. Overall, they're so good now, you're probably going to be better of than you were. If not, u has bkup!
[Verizon Samsung Galaxy S III] Jaws4God:
Thanks.. i'm not sure if I can use the CM Rom.. it just not have a lot of the features that these other ROMs have... So please don't put yourself out to try and find that file. ;)
[Verizon Samsung Galaxy S III] vforaci:
Is anyone that's on 8/14 having issues with locking a GPS signal?
[Verizon Samsung Galaxy S III] Jaws4God:
i'm not sure.. let me try it with OctOS to see.
[Verizon Samsung Galaxy S III] vforaci:
GPS and compass are wacky. I was wondering if anyone else on 8/14 is having that issue.

I can't get a lock on GPS of more than a couple if outside after several minutes. I've tried calibrating the compass within Maps and that seems to do nothing either. I know these phones have issues with GPS so I wanted to rule out any ROM issues before I go any deeper.
[Verizon Samsung Galaxy S III] Jaws4God:
are you on the 8/14 or 8/4 build? you noted 8/14 in the message but your signature says 8/4.
[Verizon Samsung Galaxy S III] vforaci:
8/14

I fixed the signature.
[Verizon Samsung Galaxy S III] YabbyYou:
I'm convinced the GPS hardware in our d2vzw is just flawed from the get-go. It never worked well according to all the posts from back in the day. I would even say the GPS was not great on the stock ROM. Does anyone remember the first time there was talk about tightening the screws around the GPS module and that would cause it to lock faster? That right there tells you something about the quality of the GPS.

To answer your question, I'm running 8/14 and my GPS is slow to lock, loses lock and does cause the phone to run warm (which I presume is related to increased CPU usage). I just kind of deal with it, but it is annoying.
[Verizon Samsung Galaxy S III] vforaci:
Yeah GPS is slow to lock. Last night with cloudy skies I couldn't get a lock, now I can but slow.

Also compass never shows the right direction and jumps all over the place. Calibration does nothing.

Edit:

I took apart the rear cover and cleaned the GPS contact and retightened everything down. GPS seems to lock better and quicker. The compass is all wacky though and calibration doesn't do anything to help. I'm wondering what others are experiencing.
[Verizon Samsung Galaxy S III] Blade22222:
I'm using the Galaxy S7 and the compass still doesn't calibrate right.
[Verizon Samsung Galaxy S III] AyUaxe:
Hadn't tried GPS in a while, but checked when this came up. I get no GPS locks, even if I leave the phone in a window for over an hour. Compass is 180 off. I may reset and restore an ancient backup that had working GPS, then flash forward. Seems like that, or flashing a stock image worked in the past.

PS, I still get no onboard audio with any build after 8/14.
[Verizon Samsung Galaxy S III] 996:
Hi All,

I am on the 09/17 build, and having issues with GPS locking accurately. It gets blotchy while running maps with the "gps signal lost" message popping up every 5 minutes.

Amazing ROM nonetheless.

Anyone have any suggestions?

Thanks!
[Verizon Samsung Galaxy S III] vforaci:
Does the compass work? Did GPS work on 8/14?
[Verizon Samsung Galaxy S III] Roger W:
for people looking at the compass problems - here's a tip to see how bad it is: when the phone is "face up" to any extent, as you pivot the phone the needle moves the wrong way - it moves with the pivot rather than staying fixed in space by moving against your pivot. When the phone is somewhat face-down, that part at least behaves correctly. Seems like there could be a bug in a transformation matrix in the sign of a sine/cosine to make something like that happen? It's way more broken than "calibration" because the motion of the "needle" in space does not work correctly.
[Verizon Samsung Galaxy S III] vforaci:
Mine picks North as what ever direction the compass it's started..... south is opposite this and east/west are north/south. In other works no east and west.
[Verizon Samsung Galaxy S III] AyUaxe:
I've tried full resets, old L backup and even a cm10 build, none of which would make GPS get a satellite lock. The cm10 build allowed SATs to be seen, but no locks. GPS has always been shiite and has gotten worse. Haven't tried any hardware hacks.

Following those wipes and installs, I also tried cm13.x builds from 9/10, 9/14, 9/19. No onboard sound on any of them, just BT audio. Back to 8/14 and audio returned. Any thoughts, friends?
[Verizon Samsung Galaxy S III] YabbyYou:
I'm on 9/16 and I get audio through the speaker for music and phone calls.
[Verizon Samsung Galaxy S III] vforaci:
I tried a couple of backups and no dice with Compass. Last night I tested it against my Nexus 9 and that was wacky too and that's a stock ROM.

As far as sound goes, I'm still on 8/14 so I can't comment since mines working. It's crickets in this thread!
[Verizon Samsung Galaxy S III] AyUaxe:
It is a bit quiet here, since some of the old faithfuls have gotten new devices and/or have jumped to OctOs or AICP--if you aggregate all the activity of these 3 threads, then you've got a surprisingly active community for a pretty old (but still capable, if not awesome) phone. Anyway, thanks to all who're still here and especially to [MENTION=2385005]invisiblek[/MENTION], who's given us the tease of N! I was pretty happy we got L, let alone M!

Would greatly appreciate any tech-smart person's input on the no-on-board-sound issue. I'm stumped. Tried all those builds plain and with DKP and Viper DD+ and BT audio works fine--just nothing from any hard connection. 8/14 build remains just about perfect for me, so if that's all I have until N, I'm not really suffering, but y'all know how it is when you don't get to flash anything for a while.
[Verizon Samsung Galaxy S III] J-Lindo:
On the one hand, I'm curious about those other ROMs, but on the other hand, this one's just freakin' great. Can't imagine why I'd leave it! I agree about the phone still being capable and would go on to say awesome. I've been using my S3 since I bought it brand new in 2012, and thanks to [MENTION=2385005]invisiblek[/MENTION] persevering on upgrading Android for us, I'm probably gonna keep using it until there's simply no more community support for it.

Now, for your speaker problem, that's really weird that you're only getting audio from the 8/14 build. I've been steadily moving up to builds 9/8 and now 9/20 with no speaker issues. This may seem like a dumb question, but have you tried just messing around with the sounds in Settings? Also, are you the kind of fellow (or chick?) who can perform some mild surgery on your phone? You might try cleaning the connector to the speaker assembly, or even swapping out for a different one to see if yours is having a bit of trouble. I know it'd be weird for the speaker to be working with just the one build and none of the other builds and it turn out to be a hardware problem, but hey, leave no stone unturned!
[Verizon Samsung Galaxy S III] Burdman2006:
I too have been steadily upgrading with no sound issues except my voice coming through as muffled during calls through normal and speaker modes. I'm currently on 9/4.
[Verizon Samsung Galaxy S III] PsiPhiDan:
I'm a Note 7 user that is between phones (returning Note 7 by 9/30, picking up LG V20 10/21). I have an old S3 that I had s-off and unlocked/rooted. I gave it to my dad two years ago and just got it back (he upgraded recently). So I know I'm s-off, but don't recall all the steps to making sure all the proper boxes are ticked before customizing. So my question is this:

1) Is this a good choice of ROM for making this phone usable again? Fast and stable are my must haves.

2) Can/should I use dkp kernel? I recall it being awesome back in the day. Does his support this ROM?

3) What order should I flash things? Firmware, ROM, Gapps? Anything I should do before then? I believe I still have TWRP but I'll double check first.
[Verizon Samsung Galaxy S III] phonetool:
What version of Android is it currently running? There's a cut-off around 4.2 or so that locks the bootloader. If you're before that, you can put TWRP on and any ROM like this one. If the bootloader is locked you are only able to use locked bootloader ROMs, like superliterom.
[Verizon Samsung Galaxy S III] PsiPhiDan:
I have TWRP, s-off, SuperSU, and am apparently on Clean ROM 8.1 (Android 4.3). Does that mean I'm safe to flash this?
[Verizon Samsung Galaxy S III] PsiPhiDan:
Nevermind, I flashed the ROM, Gapps, then firmware and am now successfully running it. Haven't had much time to make sure everything is running but so far so good!
[Verizon Samsung Galaxy S III] phonetool:
Great!

Yes, if you already have TWRP you have no problem.
[Verizon Samsung Galaxy S III] PsiPhiDan:
Sorry for the dumb question, but it says I don't have root. I downloaded SuperSU and it says I need to update the binary. I don't know how to do that. Any tips? Could I have lost root somehow? Anything I can quickly flash or no?
[Verizon Samsung Galaxy S III] PsiPhiDan:
To add to it, I just flashed this ROM, Gapps, and the firmware in the OP. Is it safe to use casual root? I don't want to brick my phone.
[Verizon Samsung Galaxy S III] phonetool:
CM loads up with root disabled by default. Go to settings, about phone, and tap a bunch of times on the version field. That opens up developer functions and I think in there you can activate root. I can't remember exactly what to do, but it's not hard.
[Verizon Samsung Galaxy S III] J-Lindo:
[MENTION=4602329]phonetool[/MENTION] is right; go to Settings, hit About phone, then repeatedly tap Build number until you enable Developer Settings (after a few taps, it will show a small popup that lets you know when you've enabled Dev. Settings). Then hit the Back button, and you'll see Developer options above About phone. Scroll down just a little, and you'll find Root access. Hit it and select Apps and ADB, and voilà! You have root.

Now, for my issue: anyone else facing issues with other apps using the front-facing camera for videos, like SnapChat and Glide, despite it working perfectly fine in any camera app (I'm using Snap Camera-- definitely recommend over the stock CM camera)?
[Verizon Samsung Galaxy S III] PsiPhiDan:
Thank you guys for helping with that. I think that's a strange way to implement root, but whatever. I found that any kernel tuning apps required an app like SuperSU. I eventually got everything to work by flashing a beta version of SuperSU because the latest stable one didn't work for me. My ROM would never load (stuck on boot animation).
[Verizon Samsung Galaxy S III] AyUaxe:
Welcome back to d2 pair'a dice. Highly recommend dkp kernel. Use kernel adiutor to tweak. Check my comments on [MENTION=4932679]decimalman[/MENTION]'s playground for some settings to try, though don't feel bad if you don't get the clock speeds and under volt stability I do--it's not me or you; it's just variations in hardware. As a reminder, flash dkp and vmin anytime after flashing a ROM. If things get too weird, just reflash ROM and you're back to safe vanilla.
[Verizon Samsung Galaxy S III] LLStarks:
So... this is a thing

http://www.invisiblek.org/roms/cm-14.0/d2vzw/cm-14.0-20160923-UNOFFICIAL-d2vzw.zip
[Verizon Samsung Galaxy S III] AyUaxe:
She Lives!

Factory reset (must reset; will not install over old data) and flashed this am. TWRP logged 2 errors, but installed successfully. Boot was remarkably quick. WiFi works. Haven't tried anything else, but wanted to get the word out. Lil D2 that could keeps chugging along!

Apparently must flash gapps in same twrp session as rom. Flashing after boot of rom gave non stop crashes. I used Delta gapps Nougat base. Installed and booted fine. Stock and open camera don't work. Camera is "inaccessible" i think was the error msg. Still awesome first build! Thanks and kudos to [MENTION=2385005]invisiblek[/MENTION]!