yashsingh1/xdaforums huggingface dataset:
[Moto Z Play Accessories] EvlSkillz:
In case anyone missed it, there are 2 new mods for the Moto Z platform:

- a Mophie 3000mAh battery pack, currently available on Verizon store at about 80 USD. It adds a little bit of bulk with about 8.9mm

- a soon to come Incipio Car Dock at 65 USD. A bit pricey if you ask me, but should be interesting with automatically launching Android Auto and an auxiliary cable to plug into a car stereo.

Motorola also claims that there will be 4 new mods at the end of every quarter in 2017, including one with the Google Tango technology.

Looks like the Moto mods ecosystem is growing. Should be interesting :good:
[Moto Z Play Accessories] microcox:
Thanks for the heads up!

Saving you a click :

https://www.google.fr/amp/s/www.cne...d-incipio-car-dock-mophie-juice-pack-battery/
[Moto Z Play Accessories] mathab:
I hope to see a bike mount, with some added feature so it can work as a cycling computer, that would be kinda cool
[Moto Z Play Accessories] EvlSkillz:
At the end of the article there are some interesting concepts:

http://www.phonearena.com/news/Lots...e-12-concepts-that-may-become-reality_id88634
[Moto Z Play Accessories] ilovemeow:
interested in 5G modem
[Moto Z Play Accessories] fourpointsix:
$65 for a magnetic vent clip, with sold-separately charging adaptor? Nope.
[Moto Z Play Accessories] EvlSkillz:
Thinking of funding this: http://www.androidauthority.com/mot...r-746322/?utm_source=dlvr.it&utm_medium=gplus
[Moto Z Play Accessories] vivebatu:
+1
[Moto Z Play Accessories] MrWilsonxD:
the moto mods would be way more successful if they weren't so darn expensive!
[Moto Z Play Accessories] mrbracht:
Agreed 100 percent! If they were all around 30 - 50.. Maybe $60 tops I would buy a bunch. Obviously the camera and projector is another story. But still, they are a little high as well.
[Moto Z Play Accessories] gostack:
We did the Gamepad Mod!

Check out our Mod on Indiegogo! It's called the Sidepad Mod :)
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] blackson2c:
Hi everyone.

I have some questions about the necessary steps for an update to mm_nexus-rom from my HDX 7 with Safetrap 4.x.x and kk_nexus-rom.

In the forum are too much information and I do not know which of them are still current and which instructions should not be used.

My original HDX 7 had the latest Fire OS 4.5.5.x Version. I used Kingroot and Safetrap 4. to install the kk-nexus-rom. So my bootloader is still locked.

Now i want to update to the mm-fire-nexus-rom withour breaking it, for this i need to unlock my bootloader.

Are the following steps correct?

1: Roll back to 3.2.4 with the steps from .3.2.4 Rollback Images

(Qustion to step 7. Copy the .3.1.0 stock update file to the root of your sdcard: Where do i Find the stock 3.1.0 updatefile)

2: User Flashify to install TWRP 3.0.2.0 from [RECOVERY][UNLOCKED BL] TWRP 3.0.2.0

3: Install mm-nexus-rom from TWRP

Or do i have to use :

[Thor][Apollo] Unlocking bootloader with any firmware
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] DB126:
Above procedure is relevant as you can now unlock the bootloader on ANY rooted 3rd gen HDX including those currently running Safestrap v4; risky rollbacks are no longer required. Be aware your device will be wiped during the unlock procedure (not always true but assume it will). Read through the unlock thread; ask questions as needed.
[Verizon Samsung Galaxy S III] invisiblek:
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Download Links

LineageOS:

Downloads: https://download.lineageos.org/d2vzw

Google apps addon:

OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)

HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.

Firmware:

Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip

Misc Links

Changelog:

Link: https://download.lineageos.org/d2vzw/changes/

Learn to build yourself:

Link: https://wiki.lineageos.org/devices/d2vzw/build

The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

XDA:DevDB Information

[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III

Contributors

invisiblek

Source Code: http://github.com/LineageOS

ROM OS Version: 7.x Nougat

Version Information

Status: Nightly

Created 2016-12-05

Last Updated 2016-12-05
[Verizon Samsung Galaxy S III] Stealth111:
reserved :)
[Verizon Samsung Galaxy S III] Master Cylinder:
Hallelujah!

Is this the eighth or ninth life of this great phone?
[Verizon Samsung Galaxy S III] Ibuprophen:
[MENTION=2385005]invisiblek[/MENTION], are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
[Verizon Samsung Galaxy S III] gcounts:
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
[Verizon Samsung Galaxy S III] Pierre2324:
Nice job! Wich partitions can I mount as f2fs?
[Verizon Samsung Galaxy S III] Ibuprophen:
Just out of curiosity regarding the CM14.1...

Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?

Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?

I had already sent the issues I'm having along with all my log files to [MENTION=2385005]invisiblek[/MENTION] and was curious as to any others experiencing the same/similar issues I experienced.

Thank you all for your time and understanding!
[Verizon Samsung Galaxy S III] azradiohead:
Thank you [MENTION=2385005]invisiblek[/MENTION] and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes

I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.

Thanks for the great work. Much appreciated!
[Verizon Samsung Galaxy S III] Ibuprophen:
[MENTION=2385005]invisiblek[/MENTION], I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.

Is this correct?

I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.

But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.

I'd really appreciate your confirmation.

Thanks a Bunch!
[Verizon Samsung Galaxy S III] Master Cylinder:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.

But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....

I'm clean installing the new official again! :mad: It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them :mad:)
[Verizon Samsung Galaxy S III] Ibuprophen:
Thank you for your response!

I always had the latest TWRP 3.0.2-0 installed.

I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.

The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...

I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.

To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.

I had to E-mailed [MENTION=2385005]invisiblek[/MENTION] the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.

[MENTION=2385005]invisiblek[/MENTION] is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.

I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...

I'm real disappointed with this...
[Verizon Samsung Galaxy S III] Ibuprophen:
Okay... I tried to sort out and answer all the questions the best i could.

I also attached the log files. They are dated according to the Nightly releases.

Q: You have a verizon SCH-I535 correct, and not another variant?

A: Yes. I have an SCH-I535.

Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).

A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.

Q: Told it to flash your 12/07 build?

Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?

A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.

Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".

A: Portable Storage.

Q: Also what type of filesystem do you have the card formatted with?

A: VFAT

Q: What file manager are you using to try to access your card with?

A: Stock & ES File Explorer Pro

Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?

A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.

I really appreciate your assistance and please don't hesitate to defer to [MENTION=2385005]invisiblek[/MENTION] if necessary.

Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...

Thank you very much!!!

I wonder if the GApps issue is the underlying issue. I hope [MENTION=6404745]MastahF[/MENTION] & [MENTION=3989659]Rapper_skull[/MENTION] is aware of and working on it?
[Verizon Samsung Galaxy S III] Master Cylinder:
I installed Stericson BusyBox Pro using Google Play and it works fine! :) Lucky me!

I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)

As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.

Oh, and my phone is purring like a kitten with 12/7 on it! XD

PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
[Verizon Samsung Galaxy S III] Stealth111:
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....

Who knows.... :confused::laugh:

Other than that, I agree, purring like a kitten!

Stealth111
[Verizon Samsung Galaxy S III] Ibuprophen:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
[Verizon Samsung Galaxy S III] Pierre2324:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
[Verizon Samsung Galaxy S III] Master Cylinder:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
[Verizon Samsung Galaxy S III] Ibuprophen:
Here's a link that, i believe, will answer your question:

http://xdaforums.com/showthread.php?t=2537119

Good Luck!

---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------

There was a member in the GApps thread who had mentioned that he had a similar issue.

He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.

I believe that others had to flash their GApps packages from about 30 days ago had worked for them.

I know that this is an issue for many others who also reported it to the Dev(s).

I can't think of what in the world is going on...
[Verizon Samsung Galaxy S III] 96heckler:
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:
[Verizon Samsung Galaxy S III] Ibuprophen:
I never really had any issues with the TWRP v3.0.2-0 backup and restore on my d2vzw...

You know that it's funny to see both an Official Nightly and an Unofficial release of LOS14.1 that's dated for today.

I'm still working on (along with a few others) a reason for the loss of Internet data on both the WiFi and Mobile. Can connect to both without any issues but neither has Internet activity.

I know that this is an issue with a small handful of individuals but, it is an issue that is a pain in the "Rump Roast"!
[Verizon Samsung Galaxy S III] J-Lindo:
Here's a fun question: it isn't a huge deal, but is there a way to record 1080p videos like we could on stock TW? No camera app I install (including LOS stock, as well as Snap HDR) will record in over 720p.

I'm sure there's a great deal I don't know about developing the software to even get the camera up and going. Perhaps we're lucky we even can record in 720p. I figured, however, it can't hurt to ask, as you fellows have been ever so nice since I arrived! :)
[Verizon Samsung Galaxy S III] javelinanddart:
I'm going to regret this....

https://www.androidfilehost.com/?fid=529152257862701929

I've been told you're having wifi issues, can you test that build (needs wipe from lineage nightly) to see if your wifi issues persist?
[Verizon Samsung Galaxy S III] stg33k:
I'd like to bring my old S3 out of retirement and install one of these Nougat builds. It was running CM10.2.1 quite happily when I stopped using it just over a year ago. The currently installed recovery is CWM v6.0.2.3. What's my best upgrade path? Specific questions:

1. Should I leave the existing recovery as is, or should I update to TWRP v2.8.7.0 or v3.0.2?

2. I'm on MF1 bootloader, but not sure what modem I'm on; I don't think I ever updated it after June 2013 when I first loaded CM. Should I flash the MF1/NE1 file from the OP anyway?

3. Can I just wipe and flash the latest build, or do I need to update to an intermediary version first?

I have no current plans to activate this on Verizon anytime soon, just want a secondary wifi-only device. Thanks for any advice you have for me.
[Verizon Samsung Galaxy S III] Ibuprophen:
I, personally, would recommend the following:

1) Update TWRP to v3.0.2-0 located here:

https://dl.twrp.me/d2vzw/

2) Update your Firmware Modem by flashing the "MF1 Firmware NE1 Modem" located here:

http://download.invisiblek.org/firmware/d2/

Good list of ROM's:

Official LOS14.1:

https://download.lineageos.org/d2vzw

Unofficial LOS14.1:

http://download.invisiblek.org/roms/lineage-14.1/d2vzw/

OCTOS (LOS14.1 Based):

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

Good Luck!

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] phonetool:
TWRP 3.0.2-0?

That's the latest that the TWRP Manager reports.
[Verizon Samsung Galaxy S III] Ibuprophen:
My bad... LMAO!

I just edited the text seeing that I had done a typo.

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] stg33k:
Success!!! Flashed TWRP v3.0.2-0 using Odin, flashed firmware+modem file via TWRP, then flashed latest LineageOS 14.1 and gapps-nano via TWRP -- got a lovely, heartwarming feeling seeing my old mainstay running smooth-as-butter Nougat! I did not flash SuperSU, since my primary objective was to use this phone for Pokemon GO, which I'm happy to report works! Wasn't listed in the Play Store (I didn't expect it to, since this is an unsupported model), but I sideloaded the APK and logged in without any problems -- no SafetyNet issues at all. Makes the phone heat up a bit, though -- hopefully that won't be a problem long term.

---------- Post added at 09:28 PM ---------- Previous post was at 08:59 PM ----------

Ehhh.... Apparently my GPS is MIA. No "Location" toggle switch in the pull-down, and when I set Location mode to "Device only" (GPS only), then I have no location data. Is this likely due to flashing the NE1 modem? or is it a bug in LineageOS?
[Verizon Samsung Galaxy S III] Ibuprophen:
It's not the modem flash.

LineageOS Nightly releases are considered to be a work in progress.

Snapshot releases are considered to be stable.

That's not to state that the nightly releases are broken but, a work in progress.

Also, the modem update is only needed to be flashed once and not needed to be flashed again.

There are individuals who have no issues with the LOS14.1 but, there are those who have anywhere from minor to major issues with it as well.

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] stg33k:
Yeah, I know the Nightly releases can have bugs, I just wasn't expecting anything that major. Not complaining, just a little disappointed after my initial elation at having it work. I'll just try some other builds and hopefully find something that works for me.
[Verizon Samsung Galaxy S III] Ibuprophen:
Why not give the OCTOS 14.1 a try and see if the GPS works.

The OCTOS thread is here:

http://xdaforums.com/showthread.php?t=3532538

The download OCTOS for the d2vzw is here:

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

We'll keep our fingers crossed!

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] Ibuprophen:
Did anyone notice that Invisiblek has a flash file named "sgs3imeirepair.zip" located here:

http://download.invisiblek.org/

Just spreading the word...

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] stg33k:
I'm a bit perplexed and annoyed... I tried the official LOS 14.1, invisiblek's unofficial LOS 14.1, OctOS 14.1 (LOS-based), and what I believe is the last official CM 14.1 nightly -- none of them see the GPS at all.

So I tried the last CM 13.0 nightly -- nope.

Then the last CM 12.1 snapshot -- still no dice.

Went all the way back to the CM 10.2.1 build that I had been running when this GS3 was my daily driver, and finally GPS works. But it's Android 4.3, so not compatible with Pokemon GO, which is my primary intended purpose for this thing.

I'm thinking maybe there's some kind of GPS-related firmware update that I need so that the newer versions of Android can use it... That's the best logical guess I have. Any suggestions??? Would a logfile help, if anyone was willing and able to take a look at it?
[Verizon Samsung Galaxy S III] Deliquified:
Ever tried tightening your screws around the battery? I've read this fixed GPS issues that some people have
[Verizon Samsung Galaxy S III] dvschnk:
That sounds about right. GPS is a finicky thing on the S3. I could never get GPS to lock on CM12.1. I got GPS to lock on CM 13, except for the last few releases (I would say the ones around august & september, I was able to get GPS to lock). I'm still waiting for CM 14.1 to mature a bit before jumping on (also waiting for xposed to be updated to support CM14.1).

I've also read, but can't confirm because sometimes its like voodoo, to install 4.3 like you did....and get a GPS lock, and then install CM whatever you want (you can wipe system and data like a normal fresh install). This may help you in getting GPS to work. One other thing....maybe try setting SELinux to permissive while you're trying to get a gps lock.

Those are all my tips and wives tales i've collected to try to get around the S3's gps. I've even tried to replace the GPS.conf on any of the current ROMs with the GPS.conf from stock 4.3 (that's given me varying success).
[Verizon Samsung Galaxy S III] mamarcac:
GPS and compass calibration

Couldn't have said it better myself, the only thing I'll add is that the Compass Calibration that works on TW 4.3 (https://xdaforums.com/showthread.php?t=1142429) doesn't seem to have an equivalent on CM/LOS that I've found. So on OctOS-M (or any CM13 derivative), even after getting a GPS lock I was never able to get the compass pointing in the right direction when using Google Maps, for example.

Sometimes knowing you're not alone helps... :silly: