yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] cherishd1:
my samsung galaxy 111 was changed over to metro pcs from tmobile. since then i have only used the phone for my wifi games and apps already installed from the year of these services. NOW no matter where i connect it to on my lap top, it only showes as unknown device. ive tried to update driver like it suggests in the trouble shooter program. what can i do to make it compatable with my computer? the unchanged galaxy tmobile phones have no problem with compatibility. thanks to any helpful answers from anybody!:confused:
[T-Mobile, Samsung Galaxy SIII] serio22:
It's actually galaxy s III for 3. Download the drivers from Samsung website under support, or install kies
[T-Mobile, Samsung Galaxy SIII] BizzyBeth:
Hi cherishd1

It sounds like you have a driver issue on your laptop as serio22 said.

Go to: samsung.com/us/support/

Input your model number or go down to cell phone section and click the link for cell phones > click T-Mobile cell phones and then input your model.

From there it will give you a few options, but you'll want to go to downloads. Click the "see more" and scroll down to USB driver. You could also choose to download the first link which is for the "Device Install" (first one listed) but like with cell phones, who needs a bunch of software installed and running that you rarely use. The driver should be sufficient to get you connected to your laptop.

I don't know what OS you're running on your laptop, so just make sure your laptop meets the system requirements before you download and install anything. Good luck!
[Verizon Samsung Galaxy S III] Orion116:
​

LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.

Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!

While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.

We ask that you do your part to know your device and know how to recover from problems before you flash!

cameron581

cdub50

Cl3Kener

CPA-Poke

deadman96385

iiD4x

itsmikeramsay

Jarrid42

johnnyslt

jsnweitzel

liquid0624

mtb300gt

Ntemis

reginald476

rkpeterson

rwaempires

sandtod

Somber73

sspencer10ls

TheBr0ken

timpohladthomas

Material Black Theme
DPI Changer
Status Bar Settings
I'll update more features later on

[url="https://plus.google.com/b/102153960718796996774/communities/117452480298315341829/stream/d5e8c0fe-5ee7-44df-97a5-6dd8cdcf8bb8"]Check are Google+ for a updates[/URL]

[url="http://github.com/LiquidSmooth"]LiquidSmooth Github[/URL]

[url="https://bitbucket.org/gideonx/bms-jb-3.4.y/commits/all"]Kernel Source[/URL]

d2vzw Download With CM Theme Engine

d2vzw Download With Layers

Gapps Download

​

CLICK HERE TO SHOW LIQUIDSMOOTH SOME LOVE :D​
[Verizon Samsung Galaxy S III] Orion116:
This is a beta build for the Samsung Verizon S3 (D2vzw)

Bugs:

Samsung Verizon S3 (D2vzw) specific bugs:

Install Instructions:
[Verizon Samsung Galaxy S III] Orion116:
Reserved
[Verizon Samsung Galaxy S III] Beeko:
Gave it a go and flashed it, have been using it all day and this is what I've noticed so far. You added Viper4Android as the default equalizer (which I love personally) but I can't for the life of me figure out how to add it to the app drawer. The signal has been a little iffy still, sometimes I'll lose signal for around a minute or so. Other than that so far so good. Keep up the good work.
[Verizon Samsung Galaxy S III] noingwhat:
Hmmm... just flashed and for some reason my home button isn't working. It will work to wake the device up, but i can't use it to take me to the launcher, or if I change the settings, double press, and long press don't do anything either.
[Verizon Samsung Galaxy S III] Orion116:
Viper is built into the ROM so you can add it to the drawer. Signal is modem related what is your is the last three digits of your baseband?

Sent from my SM-P600
[Verizon Samsung Galaxy S III] Beeko:
I'm on NE1, and after using it it seems to have settled and now signal isn't going in and out. Been on LTE all morning without issues.
[Verizon Samsung Galaxy S III] Orion116:
That seems to do that, lol. I know WiFi does that when I first boot my d2usc.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] pyrite123:
This says Lollipop in the title but the screenshots don't look like Lollipop... I got all excited because I was waiting patiently for someone to finally make a d2lte Lollipop ROM because I loved the UI.

Anything new in this one?
[Verizon Samsung Galaxy S III] Beeko:
This is lollipop. Even says it in the title and download.
[Verizon Samsung Galaxy S III] Deliquified:
Lollypop has been available for this phone for awhile now.. CM12 = LP.

http://xdaforums.com/showthread.php?t=2569769
[Verizon Samsung Galaxy S III] Orion116:
This is Lollipop. The pictures are old, lol.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] Orion116:
Please don't post other Roms in my threads. If you what tell someone about it PM them. Thank you.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] pyrite123:
Installed and going to test drive it for a few days. It is indeed Lollipop! Despite the screenshots it has the lovely material interface and it is Liquid Smooth and Lightning Fast. Thanks for the wonderful release!
[Verizon Samsung Galaxy S III] core2kid:
Having some trouble installing using TWRP 2.8.4.0. I did the default wipe, installed the 1/31 nightly and tried flashing Gapps which failed. Upon rebooting, 10 mins in and it was still loading.

I came from stock unlocked 4.1.2 on a VZW S3. Any ideas? Is it supposed to take longer?
[Verizon Samsung Galaxy S III] Orion116:
Is it still on the boot screen? Lollipop takes time time to boot it can take you to 15 minutes. Just wait.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] core2kid:
I got it. Realized that I had to wipe "System" also.
[Verizon Samsung Galaxy S III] savagebunny:
Having great results so far. My issues have always been in the past were Bluetooth from any AOSP rom would crash, not connect, or hot reboot phone. Not having one single issue.

PSA: If you are having issues with Viper4Android show 'abnormal' status on Driver Status, or when you're playing music and go open V4A, it says you gotta re-install it. I found a fix for that.

Download these zips and flash them in recovery. http://xdaforums.com/showpost.php?p=56964275&postcount=15914

Once you installed those zips, reboot and download SELinux Mode Changer, don't open V4A yet - https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en

Once installed, change SELinux to permissive. Open V4A and install the driver. Reboot your phone and now it should be working for you :)

Working for me using GoneMad Player
[Verizon Samsung Galaxy S III] Mtsprite:
[EDIT] funny as i posted this my wifi decided to work lol. XD
[Verizon Samsung Galaxy S III] pyrite123:
I'm having problems with WiFi. It works at first with no problems but when I toggle it off and try to turn it back on, it says 'turning on wifi' forever. When I restart phone it is working again. Some reason, like right now, I can't Even turn WiFi off. *shrugs* other than this, great rom! Still gonna use it until contract is up :)
[Verizon Samsung Galaxy S III] lepa71:
Does camera and video recording work? Thanks
[Verizon Samsung Galaxy S III] Orion116:
Read the Q&A thread please:)

Sent from my SM-P600
[Verizon Samsung Galaxy S III] Orion116:
We will being creating two nightlies now one with CM theme choser and another with RRO Layers. There will be two night lies folder's from now on.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] Krystalmyth:
Is that available now or on the next release? Available sometime soon I hope. Love Liquid and loving the themes out for CM12. Liquid is far more stable than the unofficial CM12 ATM so I'm really eager for the next shot. c:
[Verizon Samsung Galaxy S III] Orion116:
Soon tonight I hope.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] ysury:
After upgrade it, my phone cannot hang up a call, both either I make a call or receive a call.

Does anybody know how to fix it?

Camera can be fixed by Open Camera.

So far, other things are normal.
[Verizon Samsung Galaxy S III] Beeko:
The only problem I'm having is the signal issues. Usually after I toggle WiFi I'll either have no signal or I'll have LTE, it's never consistent.
[Verizon Samsung Galaxy S III] pyrite123:
I saw in several places where the builder said there were new builds up. There are no new builds in either vzw or USC and instead some are now missing...
[Verizon Samsung Galaxy S III] Orion116:
I have also stated that LS is being rebased meaning I will have to wait a few days. Also I am a full time college student so my time is limited.

Side note: d2usc will be done before d2vzw because I own the d2usc.

Sent from my SM-P600
[Verizon Samsung Galaxy S III] savagebunny:
Good to know about the builds. Can't wait till the baked in themes. Well, It's not a big issue, but something I've noticed the past few days. When I use the WiFi toggle, it takes quite a bit to turn on. I noticed when I was in System Settings > WiFi, It keeps auto-toggling off/on/off/on when i activate it to use WiFi, It soon does though connect. Does the same before and after fresh reboot.
[Verizon Samsung Galaxy S III] Orion116:
Right now I would just leave the WiFi on. Then you don't have the toggle loop, but you do have to goto WiFi setting when you reboot or reconnect to a network. We have no clue why this is happening. I will check this in my next build.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] core2kid:
Anybody have issues with GPS not working? It'll find my location but won't update it while driving. Also camera crashes a lot even with Open camera. In Snapchat for example, I cannot record a video.
[Verizon Samsung Galaxy S III] Orion116:
Disable stock camera and uninstall all camera apps, then reboot and install Open Camera.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] pyrite123:
No problem friend, take your time. And sorry if I sounded rude. It is frustrating trying to navigate this forum on Tapatalk with this unstable Comcast connection. I miss my PC ×~×
[Verizon Samsung Galaxy S III] Orion116:
No problem. I am running a new build now?

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] pyrite123:
Awesome, thanks for the new build! Just happened to check the download page and saw it was uploaded 2 minutes before lol
[Verizon Samsung Galaxy S III] Orion116:
Lol. Your welcome I had a little bit of trouble building it last night.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] griz.droidx:
Saw the new build myself just now on AFH. Thanks. I understand you're a student, and your studies must and should come before anything else... For Real man. Thanks again for the build. I'll probably load it up tonight. So far though I haven't been all that impressed with lollipop. There are some good and bad things about it like anything else that's new. At least it wasn't as drastic as say win7 to 8 or from kde3 to kde4. Anywho thanks
[Verizon Samsung Galaxy S III] griz.droidx:
According to the rro layers page linked in the slimpop thread, rro is available for liquid builds. You have to follow the directions, join the G+ community, then request beta access. I haven't tried it yet. The regular theme engine worked fine for me. But RRO is supposed to be better and more secure from what I've read. Again, I haven't tried it, on liquid or any other pop builds but according to the bitsyko wiki of sorts it should work after you install the app and so on. It's all new to me so read up on your own.
[Verizon Samsung Galaxy S III] Orion116:
Liquid is currently being rebasing to Slim because RRO isn't work with a CM base.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] pyrite123:
I was running the new build since the moment you uploaded it and something was just brought to my attention. I can send and receive texts and make phone calls just fine. However I cannot receive phone calls. The people calling me get a message "call cannot be completed at this time".

It might be my modem now that I think about it. I went back to 4.3 and back to this.
[Verizon Samsung Galaxy S III] Orion116:
Sounds like the modem

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] pyrite123:
Unfortunately it wasn't the modem. I tried 3 modems and the one I'm on now is the NE1 and now when trying to place a call it says dialing forever and when canceling it says hanging up forever and I can't stop it.

Not sure if it's Rom related or not but I seem to remember having this problem on a few DU 4.4.4 builds.
[Verizon Samsung Galaxy S III] Orion116:
Ask the other maintainers if anyone else has similar issues

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] savagebunny:
Xposed has came to Lolipop now.

*DISCLAIMER* Make sure you do a full nandroid backup before flashing. This is a very early release of Xposed so may not work or have bugs.

http://www.xda-developers.com/xposed-framework-for-android-lollipop-is-here/

Official Xposed Thread
[Verizon Samsung Galaxy S III] Orion116:
Don't report any bugs if you use xposed.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] astonmartin214:
yea it's in Alpha so still not ready
[Verizon Samsung Galaxy S III] Nomad1600:
Thinking of going from my current 4.4.4 ROM (Spirit) to LS Lollipop. I am still on ML1 (always seemed to do well for me and my phone). Do I need to update to ML1 (or something newer) to run LS 5.02? Its been a while since I had to flash a modem... so if someone can refresh my aging memory about where I can find a flashable (and how I can flash)>

btw, I update my TWRP to 2.8.4.0 (saw there was a 2.8.5 but read there were some issues).

Thanks in advance!
[Verizon Samsung Galaxy S III] pyrite123:
You shouldn't need to flash a new modem, though it may help. Your recovery is fine. If you decide to upgrade your modem just ask and I can upload some. I remember the modems being somewhat of a pain to find.

Keep in mind, though, d2vzw/lte Lollipop roms have issues with camera. Some people claim that some 3rd party cameras work, though.
[Verizon Samsung Galaxy S III] Orion116:
Open Camera does work

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] Nomad1600:
Many thanks... I will try with my current modem and if signal seems weak I will bother you for the modem help. One last question... does the ROM have SuperSU or do I need to flash or install it separately?

btw, I use both the Google Camera and Camera Zoom FX on my current phone, so using a third party camera app isn't an issue. Does "Pocket Mode" work?

---------- Post added at 04:10 PM ---------- Previous post was at 03:19 PM ----------

btw, Camera Zoom FX appears to work, in case people are looking for working cameras. I don't believe Camera Zoom FX has its own video (camcorder) as it appears to look to connect to the stock camcorder (which I don't believe works on Lollipop ROMs, correct?).
[Verizon Samsung Galaxy S III] Krystalmyth:
Cannot for the life of me set selinux to permissive mode on the latest build. Changer app does not work. SuperSU reports this error.

/system/bin/setenforce: Could not set enforcing status: Invalid argument

Cannot manually run the string either. This is preventing ViperAudio from functioning.
[Verizon Samsung Galaxy S III] Nomad1600:
Trying to access advanced power menu. I believe its under developers options, which I think I need to expand by tapping on build number. But tapping on build number seems to have no effect. Am I doing something wrong?

Update, I found advanced power menu under Security menu. But I guess my question about tapping on build number still is making me wonder if developer options is already extended?
[Verizon Samsung Galaxy S III] Orion116:
It was moved to security settings.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] Droidriven:
I noticed you are a maintainer for the d2vzw devices. I don't know if you've been asked this or not but I have straight talk S3 which as you know is a d2vzw device. My question is since the last few builds of KK for d2vzw and most of the d2lte ROMs and now the lollipop ROMs are requiring our devices to have a SIM inserted to have working data, our devices are 3G and shouldn't require a SIM. Do you have any ideas of what modifications we can make so that we don't need the SIM and our system handles connectivity as normal?

I've been digging and working at this since November. I've collected a lot of information and made mods that have shown some results but hasn't completely fixed it, we've swapped and edited build.prop using pieces of stock and KK, we have used our devices RILD, adb chased the chain in the ril files, we did the same with all the libraries.

What I keep coming to every time seems to be the systems initial reference to the SIM at startup and not what goes on in action while system is booted and running, to clarify it seems that if a SIM is not present at that startup reference and "switch" then system doesn't boot into a connected state, even if all the proper system files for service and data are in place, it never gets a chance to use them. There are lines that deal with the SIM in build.prop that if deleted seem to get rid of the initial SIM query and the icon in status bar but also kills service period. The edits to build.prop, ril and libs has the radio coming on, registering on right network, get prop has correct values, baseband shows in system but phone number does not, I haven't gotten any further than that, IMEI stays in place no problem but don't know my next step.

I just thought I'd run that by you, I'm looking for any input or info on this in as many places as I can. I think if the answer is finally found it could potentially solve all the other 3G devices problems that don't have a SIM slot so they can run LP also, the method would just have to be applied by how their system works but the changes would basically be the same for all devices I would think, whatever part seeks the SIM can be directed at our system files for its function instead of the SIM, its just a matter of getting it to jump the track in the right place in its sequence, I don't know how to find it or where to look anymore. Sorry if I've bothered you, I just think it could make difference for a lot of users of many different devices so its not like its a small group of just a few devices. I would appreciate any ideas if you or anyone else is willing to think about it for a minute.

Dripped from the Tapa of my (Deathly)Liquidsmooth S3
[Verizon Samsung Galaxy S III] Orion116:
I actually own the d2usc but I am pretty sure that the d2's are 4g/LTE devices. That is why the unified KK was called d2lte. I think your issue is that your device doesn't have the right modems. The I had trouble with radios and sound not functioning because having old JellyBean modems. I will have another d2 maintainer look over this to make sure I got this right.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] Droidriven:
Yes, from what I've learned about this model, it was formerly a 4G of the same model but 4G was changed or deactivated when it came to Straight talk I believe. I know the issue is that the ROMs are actually made for 4G devices which means a SIM is required, before this though the d2 ROMs were working fine with service and data, the devices the ROMs are made for haven't changed, just the ROM so theoretically these ROMs should be able to be converted to work as they did before the last changes made in KK around Sept/Oct last year. Thanks for your reply, I appreciate any consideration.

Oh yeah, [MENTION=968349]motorhead[/MENTION] gets the credit for what has been accomplished to get what I told you about to the point I described. It was at this point that he suggested it might be java related, I found a post that took me to the CM code review page that dealt with the setup wizard which is where the SIM is initially requested and seems to be the point after which nothings happens. The code review there was java related, it has two commits there that motorhead said didn't have anything to do with our issue but he did say that there could be an overlay. Thought I'd add that.

Dripped from the Tapa of my (Deathly)Liquidsmooth S3

---------- Post added at 01:15 AM ---------- Previous post was at 12:53 AM ----------

Hmmm...

If its modem related then there probably won't be much we can do for our devices then, but if that's the case then why does the device work fine and has service and data when a SIM is inserted? Wouldn't it require the modem to work for that to happen? Our device still has the SIM slot, it wasn't removed from its former design, also the device supposedly can't be unlocked.

Dripped from the Tapa of my (Deathly)Liquidsmooth S3
[Verizon Samsung Galaxy S III] Orion116:
Every time I build the d2usc I have to change a statement so I get the proper modems. Boost, Verizon's pay as you go, I think has the same issue as the d2usc. It is late where I am at, so I will talk to the other two d2 maintainers and see what they say.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] cinco312:
............
[Verizon Samsung Galaxy S III] Nomad1600:
Has anyone had an issues with the 2/22 update?
[Verizon Samsung Galaxy S III] Orion116:
Haven't had any on the d2usc build of the same date.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] Droidriven:
Have you found anything concerning the SIM dependency I asked about? Just keeping tabs, I'm collecting as much info on this as I can from everywhere. I was hoping that those that actually work on the ROMs for these devices could give me a good idea of where I need to focus to solve this issue. Thanks again.

Tapped in ice from my Ice Cold lollipopped S3
[Verizon Samsung Galaxy S III] J913B:
What is with our phones and camera apps on 4.0/5.0? It's really annoying. Had the Facebook app show the stretched out face whenever I took something from the front facing camera and Open Camera only works 50% on this build. It's going pretty smoothly so far, thanks maintainers!
[Verizon Samsung Galaxy S III] Orion116:
I believe the non-working camera has to do with Samsung not releasing the code for their camera, so it has to be rebuild after each android update.

LiquidSmooth d2usc/d2vzw maintainer
[Verizon Samsung Galaxy S III] Nomad1600:
Have you tried Camera Zoom 360? I don't use Facebook, so I can't comment there, but I use that camera on my phone and tablet running different lollipop ROMs.
[Verizon Samsung Galaxy S III] JDC2389:
Can you please make the kernel a seperate download for users that just want the updated Lollipop kernel and not the ROM? No offense but the LiquidSmooth design style isn't for me.
[Verizon Samsung Galaxy S III] Orion116:
For the Lean Kernel or the BMS kernel?

LiquidSmooth Maintainer for the d2usc/vzw
[Verizon Samsung Galaxy S III] JDC2389:
BMS please and ty!
[Verizon Samsung Galaxy S III] Orion116:
There is a zip on AFH
[Verizon Samsung Galaxy S III] Krystalmyth:
I have to ask a second time, but as I went unanswered and went off to try AICP the last few weeks I've decided to give LS anothrr go. The issue however seems to still exist. I cannot change the SElinux mode to Permissive on this ROM. Just this ROM.

Works on AICP and Masta's cm12. You have viper audio loaded by default and it doesn't even work because of this SElinux state. Could anyone shed some light on this? This is the most stable ROM I've tried on lollipop, and this is one of my only issues with it

The next being it seems there is no way to get software navigation on this build? Please tel me I'm just derping and can't find it.
[Verizon Samsung Galaxy S III] Orion116:
Wait for next release for nav bar. The other I am not sure. It might be kernel related.
[Verizon Samsung Galaxy S III] griz.droidx:
If it's kernel related try dkp or BMS. Dkp has treated me well personally
[Verizon Samsung Galaxy S III] Orion116:
These builds are related to BMS. All builds after 3/6 will have LiquidSmooth version of LeanKernl.

LiquidSmooth Maintainer for the d2usc/vzw