yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] riven67:
hello my d2spr died on me today, cracked screen. I have another S3 but it is a triband d2refresher and I am a little confused as to if this rom will work with this phone. the op is not clear as Do not use on d2refresher is striked through. Can anyone confirm one way or the other if this will work? also if anyone is so inclined pm me with specific things to avoid or to do in order to root this model thanks.
[Sprint Samsung Galaxy S III] naterza:
D2SprRefresh will work with any D2spr ROM, so long as you have D2spr TWRP flashed for it, and that you flash the symlink fix. I've has this phone for the last year and have exclusively been using d2spr ROMS. You'll need to root with ODIN in order to flash TWRP. Also, I flash the symlink fix immediately after the ROM.

Steps:

Flash ROM

Flash Symlink Fix

Flash APN fix if needed

Flash Gapps
[Sprint Samsung Galaxy S III] avd:
No weekly nightly?
[Sprint Samsung Galaxy S III] :
The terms weekly and nightly refer to the rate at which builds will be rolling out. If a ROM is using a nightly release system, you can expect a new build every night. If a ROM is using a weekly system, you can expect one every week. So in this case, you'd ask "no weekly release?" or something along those lines
[Sprint Samsung Galaxy S III] clearchris:
The ROM is nearing completion, we are putting in effort to release a stable next week. I think from here on out, we are going to release once every two weeks until O, when we start all over again.
[Sprint Samsung Galaxy S III] madbat99:
You guys gonna keep d2 going on O ?
[Sprint Samsung Galaxy S III] clearchris:
Lineage has been keeping it alive far beyond my expectations. I think they will keep it going for O.
[Sprint Samsung Galaxy S III] avd:
Id happily take 7.1.2
[Sprint Samsung Galaxy S III] clearchris:
Actually, word just came down, after the stable comes 7.1.2.
[Sprint Samsung Galaxy S III] JakeG1984:
Contacts, Gmail, People details refuse to sync. I've been searching for other people having this problem and have come up fairly empty. This leads me to believe this is self-inflicted. I have followed the flashing procedures. Rom, then Gapps, then root. I have tried with and without root. (oct-n-weekly-20170401 with md5 | opengaaps 7.1 nano from 20170410 | addonsu-arm-signed.zip). Is anyone else having issues syncing anything google? A few times it has actually synced a few contacts (like 50 out of 500) but usually, I can get nothing. I have tried clearing contacts storage data and cache as well as clearing various other google app data and cache. I have tried multiple reboots. I have tried deleting my google account, restarting, then adding my google account. I have tried opengapps via aroma installer picking what I want. I have tried redownloading all rom, gapps, root zips. Everything seems to work except syncing with gmail, contacts, and people details. I don't know what else to try.
[Sprint Samsung Galaxy S III] avd:
There a problem with the latest gaps. Uninstall and reinstall each app with play store and they will start working again.
[Sprint Samsung Galaxy S III] clearchris:
YOU! Perfect timing!!! I have been searching for someone experiencing this problem.

I have a potential fix for this. I don't want to post it due to it's experimental nature, please PM me your gmail and I'll get you setup on the Octos S3 chat.
[Sprint Samsung Galaxy S III] JakeG1984:
PM sent to Clearchris but wanted to follow up.

I tried a version of your suggestion. I went with a full wipe and reinstall with Gapps pico from 4/1/2017 and then installed everything else from the PlayStore. No dice. Same symptoms (i.e. gmail, contacts, people details will not sync). If I go back sufficiently far with Gapps will this resolve itself? Am I a unique case with this???

Thanks!
[Sprint Samsung Galaxy S III] solnoy:
always pop up the " Setup wizard keeps stopping " how to resolve this please :(
[Sprint Samsung Galaxy S III] tnippett:
I have been searching for a solution to this for days now. Not not only am I having issues with contacts, and calendar, but also with downloads from the Play Store. Any other ideas on fixes?
[Sprint Samsung Galaxy S III] koobie777:
Well after using this rom for a couple weeks I deff got some cam issues. Snapchat all videos I send are black so everyone says anyways. FB messenger, video is black, Skype doesn't even work period and the Skype preview app just fc's. I can up a bug report but I was wondering if anyone else was experiencing this. As far as setup wizard force closing I just uninstalled it, that also fixes the activating cellular network issue as well on all n roms
[Sprint Samsung Galaxy S III] clearchris:
This is the next issue we will be looking at after the boringssl fixes go up. Bug reports are always welcome. If you are interested in testing, send me a PM with your gmail id. Must be willing to get on hangouts.google.com.
[Android Q&A, Help & Troubleshooting] Mohamedbeni1234:
Hi, my Samsung young 2 with single sim card van not detect it. I made a wipe but nothing. I tried to flash a new custom ROM but i found only Rome d'or young 2 with two sim card ( duo). Sorry for m'y english.
[Android Q&A, Help & Troubleshooting] ImTheDuck:
Take sim card out put in DONE
[MX Player] azsde:
Hello,

I am experiencing issues with MxPlayer, when trying to play a video.

Steps done :

Launch MxPlayer

Choose my h265 movie

Seek to a position near the end of the movie

Nothing responds anymore, the system crashes and my phone reboots.

Current Setup:

OnePlus 3T - OxygenOS 3.5.3 - Android 6.0.1

MxPlayer 1.8.12

I tried with HW decoder, HW+ decoder, with and without custom codecs, and the result is the same in every cases.

Relevant logcat traces:

01-05 17:17:15.719 828 7731 E OMX-VDEC-1080P: OMX_COMPONENT_GENERATE_HARDWARE_ERROR
01-05 17:17:15.719 828 7731 E OMX-VDEC-1080P: ERROR: Sending OMX_ErrorHardware to Client
01-05 17:17:15.723 7437 7448 E OMXCodec: [OMX.qcom.video.decoder.hevc] OMX_EventError(0x80001009, 0)

I'm going to try with another h265 file to see if the issue still happens.

Do you guys think the issue is on your level or on the android level ?

Regards,

Azsde
[MX Player] cca310:
I discovered this issue yesterday too. I have a OnePlus 3 running CM13.
[MX Player] azsde:
I'm glad i'm not the only one having this issue.

Turns out it is not related to MxPlayer but is rather a OnePlus 3 / 3T bug.

Please see :

Xda-thread

OnePlus Forums Thread

This thread can be closed, sorry for the false reporting.
[Verizon Samsung Galaxy S III] mamarcac:
AOSP for d2vzw?

This is AWESOME!! Correct me if I'm wrong but it looks like there's a placeholder for LineageOS-based OctoOS but not AOSP. Any chance there'll be an AOSP version for our precious d2vzw?

Thanks for all your work! :highfive:
[Verizon Samsung Galaxy S III] Pierre2324:
Nice cant wait!
[Verizon Samsung Galaxy S III] canodroid15:
OK guys first round of weeklies up on site! Go get em!!

https://www.teamoctos.com/oct-n-weekly-lineageos-base/

Enjoy!
[Verizon Samsung Galaxy S III] Pierre2324:
F2fs compatible? To system, data and cache?
[Verizon Samsung Galaxy S III] clearchris:
We tried to get AOSP working for D2 (among others) when I was at PACROM working on M. Let's just say that trying to support devices on AOSP without upstream support is a big reason why PAC burned out and disbanded.

That's a long way of saying: No. ;)
[Verizon Samsung Galaxy S III] clearchris:
I just checked and f2fs support is in the kernel. I haven't tested it, but if you do, please report back. :)
[Verizon Samsung Galaxy S III] Pierre2324:
I tested it and working f2fs on data and cache..when formatting system to f2fs it doesnt boot
[Verizon Samsung Galaxy S III] Jaws4God:
are their any known issues with this ROM? I need to find the newest ROM for this phone that is stable since I plan to give it away to someone in need. Thank you.
[Verizon Samsung Galaxy S III] clearchris:
If you can wait until friday, I'd go with the new build. There's a fix for the TWRP backup problem coming. All N ROMs have this issue, soon all will have fix because I sent it upstream to lineage.
[Verizon Samsung Galaxy S III] Forsonkwesi:
please , i am not getting mobile network....there is a sim card but it says, no sim card.
[Verizon Samsung Galaxy S III] clearchris:
Latest weekly has the TWRP fix. Reports from users who have installed, backed up, and restored this ROM are welcomed.

Thanks!
[Verizon Samsung Galaxy S III] clearchris:
Try the latest build. The TWRP fix might also fix your issue.
[Verizon Samsung Galaxy S III] knightride101:
I am also having issues with sim card, it says no sim card!!!, please help!!!!!!!!
[Verizon Samsung Galaxy S III] clearchris:
What build are you using? Who is your carrier? Did you flash opengapps? Xposed? Clean flash?
[Verizon Samsung Galaxy S III] Ibuprophen:
I just may give this a try since I have been having some issues with the Unofficial LOS14.1.
[Verizon Samsung Galaxy S III] knightride101:
I have flashed it with OCT-N-WEEKLY-20170120-2100-d2vzw with opengaps and did a clean flash, my local company is Telcel mexico. Thanks!!!
[Verizon Samsung Galaxy S III] Ibuprophen:
This and the Unofficial LOS14.1 has been giving problems with both the WiFi Data and the Mobile Data. The WiFi connects but, no Internet and the Mobile connects to the tower but, no mobile data and the APN is good.

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

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

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

Has anyone ever looked into this?
[Verizon Samsung Galaxy S III] clearchris:
Interesting! Can you get a logcat?
[Verizon Samsung Galaxy S III] Ibuprophen:
I had previously used the Logcat and when I, and a few others, had reviewed it deeply, we saw the data issue but, nothing specific to the MAC. There won't be any annotations specifically regarding the MAC, only the errors that were returned when anything attempted to access the WiFi or Mobile Data (ie.. The Play Store).

I'm still hacking out some ideas to grab the MAC while in CM13 and when the Nougat is installed, the MAC will be verified and changed within the System.

I have some manual commands but, looking to create something easier, like a flash file, to perform the necessary changes.

From what I can find, so far, within the "/efs/wifi/" directory, there is a file ".mac.info" that has the MAC address.

A work in progress but, am always looking for constructive input.
[Verizon Samsung Galaxy S III] Ibuprophen:
Restoring the MAC file worked to a point.

It corrected the MAC but, still no Play Store though, i was able to use the browser without a problem.

Still a small leap accomplished...
[Verizon Samsung Galaxy S III] clearchris:
What was it before and after?

Was the number different or was there a format change in the file?
[Verizon Samsung Galaxy S III] Ibuprophen:
It provides different beginning numbers followed by all zeros (ie... Begins with 02 followed by all zeros for the remaining).

There are some individuals I've been working with that have different MAC sequences.

What a headache!

I've put together some possibilities but, i haven't tried them yet but, when I'm more confident on the work, i plan to try them out.
[Verizon Samsung Galaxy S III] clearchris:
Well, you know where to find us if you need an assist.
[Verizon Samsung Galaxy S III] clearchris:
Official builds for d2 with the TWRP fix are up!
[Verizon Samsung Galaxy S III] Forsonkwesi:
After applying the latest ROM update.... I still have this sim card problem..

It seems to be fixed by using/dialing this code *#*#4636#*#* going to phone information and then changing from LTE/CDMA auto (PRL) to WCDMA preferred. I will attach images on my next post
[Verizon Samsung Galaxy S III] Forsonkwesi:
Here are the pictures of what I do b4 I get my network.....the network goes of at every restart....so I go through this process whenever my phone how's off....thanks a lot for this ROM .....hope this problem is solved soon
[Verizon Samsung Galaxy S III] serusaert:
did clean flash of OCT-N-WEEKLY-20170210-1709-d2vzw using latest TWRP (twrp-3.0.2-0-d2vzw) without any issues. flashed the safe parts of the MF1/NE1 firmware at the same time. all seems to be working. no simm card issues encountered so far.

one issue: i did have to install "nano" gapps due to not enough space for "stock".

thanks to everyone who worked on this - it's amazing that we can get nougat on this old phone!
[Verizon Samsung Galaxy S III] Ibuprophen:
Did you know that the "MF1 Firmware NE1 Modem" update is only needed to be flashed Once?

This is according to one the Official LineageOS Dev (Invisiblek). He stated that in an email to me a while ago.

He also stated that that update is placed in a devices permanent location that is not affected even when you perform a full wipe of the device.

Just an FYI...

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] serusaert:
yes, just once. i had been on the ML1 firmware and a different ROM and i can attest that there were issues. i had put this phone aside as i thought something was wrong with the hardware. hopefully it will work better now.
[Verizon Samsung Galaxy S III] Ibuprophen:
I did notice that Invisiblek has a flash file named "sgs3imeirepair.zip" located here:

http://download.invisiblek.org/

I'm not sure if that's some kind of fix for the S3.

I may try it.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[Verizon Samsung Galaxy S III] mamarcac:
Snapshot plans for 7.1.1?

Hi [MENTION=6264948]clearchris[/MENTION], love OctOS rom! Any plans to release snapshots for 7.1.1? I use my phone for work and can't flash a ROM every week or so.

Thanks for all your hard work! :highfive:
[Verizon Samsung Galaxy S III] clearchris:
Not yet at any rate. Lineage moves on and we keep adding new goodies to Octos. I'd stay on what you are happy with and only upgrade every so often.

This weeks build will include rootless, it has been working for me, but if stability is your #1 concern, I'd probably not update for a month or so.
[Verizon Samsung Galaxy S III] mamarcac:
Awesome, thanks for the feedback! Been rocking OctOS-M, everything is great except for snapping a video in the texting app (screen just locks and takes a static picture instead).

I'll keep an eye on the builds and maybe test one out in a month or so.
[Verizon Samsung Galaxy S III] donhiser:
When/ why would we use the MF1 firmware and NE1 modem update? I'm on OctOS M, and love it. I've flashed N a few different times, and love it, aside from a couple of small things. It seems like my data drops off to not working on 7.0, and no matter what text app I use, and manually entering APN settings, I have no MMS. Everything else works fine, so it's a bummer to not have those two working for me. Would the MF1 firmware NE1 modem fix this, or is it for something else entirely?
[Verizon Samsung Galaxy S III] Ibuprophen:
Your confusing the ROM with the Device Firmware Drivers. They are completely separate.

Very Brief Comparison... 101...

In order for the ROM to be able to use the components in your device (ie... Camera, Modem, etc...) it uses the device firmware drivers.

Lets say that you're performing a clean install of the OCTOS and you wipe everything... The wipe doesn't touch the devices firmware drivers. And when the the ROM begins to install on the device, you'll see the information reflecting that it first confirms the device itself matches the ROM your installing. So if you try flashing another devices ROM, it will provide an error reflecting the wrong device.

With that stated, the ROM confirms the device by way of the device firmware and drivers.

Installing the updated modem Firmware drivers will allow the ROM to be able to use the modem more efficiently.

This is a challenge to briefly explain via text but, I hope i had explained it okay.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**
[Verizon Samsung Galaxy S III] mamarcac:
OctOS-N Milestone M1

Just noticed the awesome dudes at OctOS posted a Milestone build for 7.1.1 prior to 7.1.2 being released! Anyone given that a try yet? Out of the different variants/builds for my d2vzw, OctOS seems to be the most fluid/stable so I'm looking forward to giving this one a try. :victory:
[Verizon Samsung Galaxy S III] clearchris:
The new build is up, everyone is strongly encouraged to upgrade. This is the last verision of 7.1.1 and 7.1.2 won't be released by us for a while.

The issue is that early issue snapdragon chip has a neon flaw that causes problems in boringssl. We added patches to recognize these flawed chips and to not use the neon optimizations on them. All lineage based roms had this issue. I helped them fix it upstream, so it should flow down to the other ROMs quickly.
[Verizon Samsung Galaxy S III] mamarcac:
Thanks Chris

Yes, thank you for the heads up, I downloaded the new 4/21 build with the fix. Thanks again for supporting our lil ole d2s!
[Verizon Samsung Galaxy S III] Master Cylinder:
New user on board. This is the last place for customized ... well lineage now for these old Army Jeeps. Just glad it's here!

:good:
[Verizon Samsung Galaxy S III] Master Cylinder:
I dirty flashed 5/5 with GApps and SU over 4/28 and all seems well. Pretty slick so far, though I'm still testing and haven't found a place to control the back button. Selecting 'long press kill app' in Dev Tools hasn't helped. Minor nick. Major performance upgrade over MM.

New life for this old jeep.
[Verizon Samsung Galaxy S III] clearchris:
Yeah, next build that option should be gone. It apparently conflicted with some stuff that was brought over from DU.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well Brother, just thank you for keeping us in mind and churning out builds for us die-hards.

:good:
[Verizon Samsung Galaxy S III] ginger709:
Straight talk?

Is this rom compatible with the straight talk version of the S3 if you change some of the APN settings? I think I heard that the sch-s968c is basically the verizon version. If I am completely wrong or in the wrong place, please begin the flaming. xD
[Verizon Samsung Galaxy S III] clearchris:
No one has reported on that one yet. If you decide to take the plunge, make sure you get backups first! Let us know how it goes!
[Verizon Samsung Galaxy S III] mamarcac:
Video texting camera freeze

Anyone else getting the camera freeze when capturing & texting a video through the Messaging app? Had the same issue on 6.x. Instead of capturing video the Messaging app just takes a picture. Back on the TW 4.3 Messaging app it would reduce quality when recording video for texting. Wondering what's going on since the same exact issue was on 6.x and now 7.x. Also noticed on the Camera app in 4.3 there was an option when recording Video that said "size for MMS" and I don't see that with 6.x or 7.x CM/LOS/OctOS roms.

Wondering if this has to do with the lack of a Samsung camera blob on the CM/LOS base?

Thanks for any thoughts.
[Verizon Samsung Galaxy S III] manfromgta:
Update: May 19/17

Weekly 05/19 is up on site.

Download: https://www.teamoctos.com/oct-n-weekly-lineageos-base/
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm running OctOS perfectly on my d2vzw that I had switched to Straight Talk a few months ago. The APNs configured themselves just fine. I've been running this ROM for a few weeks and I've got 5/19 on it now: all is well.

:cyclops:
[Verizon Samsung Galaxy S III] manfromgta:
Update: May 26/17

Weekly 05/26 is up on site.

Download: https://www.teamoctos.com/download/oct-14.1/d2vzw/OCT-N-WEEKLY-20170526-1239-d2vzw.zip

Changelog: https://www.teamoctos.com/download/oct-14.1/d2vzw/OCT-N-WEEKLY-20170526-1239-d2vzw-changelog.log
[Verizon Samsung Galaxy S III] mamarcac:
"Gallery has stopped"

Spent Sunday installing this puppy from scratch (the 4/21 M1 release to be exact); full wipe of everything x3 (data, cache, dalvik, data/media, system), installed pico gapps and some typical apps from Play Store (Twitter, Google Drive, nothing hokey or abnormal). Got settings the way I like them, made a Nandroid backup Sunday night after the ~6 hour effort of a truly fresh install from not using TiBu or any shortcuts.

Less than one day later, taking a picture with stock camera, went to view the picture and was greeted with "Gallery has stopped". Having the Gallery unstable is a tough pill to swallow...also I still can't create and text a video from within the stock messaging app. The wife and I use this a lot so it's kind of a big issue for me, although I know that may not be the case for others. FWIW, none of these issues persist back on CleanROM 8.2 so back to Android 4.3 I go.

I've tried CM 5x, CM 6x, and now LOS 7x based ROMs and haven't found that any one of them is truly stable as a DD which makes me sad but that's just the reality setting in of having an old phone.

Sharing this experience so if anyone else is seeing the same behaviors, you're not alone.

Shout out to the devs who keep on cranking out builds...maybe one day I'll hit one that "just works". *crosses fingers*
[Verizon Samsung Galaxy S III] clearchris:
I forget what version it was, but I think going from L to M, you had to format your SD card. If you go back to L at all, even just one boot, you can't go higher again without formatting the external SD card again.

Also make sure you are running the latest TWRP and modems.
[Verizon Samsung Galaxy S III] mamarcac:
Oh man, did not know that about the SD card. That would make sense since the Gallery looks at it...I feel silly for not having known that, for how much reading I've done on these forums as a lurker.

I've got the TWRP and modems covered, the modem/firmware thanks to the AIO zip that [MENTION=2385005]invisiblek[/MENTION] posted after the NE1 update (https://xdaforums.com/showthread.php?t=1788313).

I flashed back to 4.3, used it for a day, then flashed the OctOS 7.1 Nandroid last night and it seems to be running better now. I'll have to keep an eye on the SD card thing (set it as Portable Storage not Internal FWIW).

Thanks so much [MENTION=6264948]clearchris[/MENTION] for the help! Love the OctOS line of ROMs especially the Tentacles.
[Verizon Samsung Galaxy S III] clearchris:
Yeah, if there's a problem with gallery, it's permissions or SD card. Usually the SD card though.

Glad you are up and working now!
[Verizon Samsung Galaxy S III] Master Cylinder:
Intermittent Call Problems

I'm having frequent problems with dropped call attempts, perhaps an inability to connect to a tower or something, ending with 4 tones.

I put a Straight Talk SIM in my Verizon phone in January and it seems to have been fine, though I don't say that's not it. I don't know maybe Straight Talk renegotiated their contracts and lost their priority level accessing towers? That's an uninformed guess. Also my phone IS over 4 years old and sustained only about 1,247 drops, including recently, so there are numerous potential issues.

I'm restoring nandroids from earlier OctOS ROMs and others to see if there is a software issue.... Will report back.
[Verizon Samsung Galaxy S III] Ibuprophen:
I'm in a similar boat with you...

Only when I turn the device ON, i sometimes have to go into the Cellular Network Settings and just Toggle the Preferred Network Type to LTE and back to Global. I only have to do that once until I power up again from a restart, power down then turn it back on, etc...

For me, that does the trick. It's a pain but, it's no big deal for me... :)

***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...