Search the Community

Showing results for tags 'samsung'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • TeamUSCellular Blog


    • * -[READ THIS THREAD]- * Common Q&A and our Terms!
    • Shoutbox
  • Team US Cellular
    • Contests and Giveaways
    • Site News and Blog
    • Reviews
    • General Discussion
    • Suggestion Box
    • (¯`·.¸¸.-> °º Birthdays º°
    • Ask The Employees
  • US Cellular
    • News
    • Rumor Mill
    • Contract & Billing
  • Android
    • Android Discussion
    • Android Development
  • Google Pixel
    • Pixel & Pixel XL Discussion and Development
  • Nexus 6P
    • Nexus 6P Discussion
    • Nexus 6P Development
  • Nexus 5X
    • Nexus 5X Discussion
    • Nexus 5X Development
  • Nexus 6
    • Nexus 6 Discussion
    • Nexus 6 Development
  • Apple iPhone
    • General Discussion
    • Development Q&A
  • Ubuntu for Android
    • General Discussion
  • Windows Phone
  • LG V20
    • LG V20 Discussion
    • LG V20 Development
  • LG G3
    • LG G3 Discussion
    • LG G3 Development
  • LG G4
    • LG G4 Development
    • LG G4 Discussion
  • LG G5
    • LG G5 Discussion
    • LG G5 Development
  • LG G Flex 2
    • G Flex 2 Discussion
    • G Flex 2 Development
  • Motorola Electrify M
    • Electrify M Discussion
    • Electrify M Development
  • Motorola Moto X
    • Moto X General Discussion
    • Moto X Development
  • Motorola Moto X (2nd Gen)
    • Moto X (2nd Gen) Discussion
    • Moto X (2nd Gen) Development
  • Moto X Pure Edition 2015
    • Moto X Pure Edition Discussion
    • Moto X Pure Edition Development
  • Motorola Moto G
    • Moto G General Discussion
    • Moto G Development
  • Samsung Galaxy S8
    • Galaxy S8 Discussion
    • Galaxy S8 Development
    • Galaxy S8 Plus Discussion
    • Galaxy S8 Plus Development
  • Samsung Galaxy S7
    • Galaxy S7 Discussion
    • Galaxy S7 Development
    • Galaxy S7 Edge Discussion
    • Galaxy S7 Edge Development
  • Samsung Galaxy S6
    • Galaxy S6 Discussion
    • Galaxy S6 Development
    • Galaxy S6 Edge Discussion
    • Galaxy S6 Edge Development
  • Samsung Galaxy Note 5
    • Note 5 Discussion
    • Note 5 Development
  • Samsung Galaxy Note 4
    • Note 4 General Discussion
    • Note 4 Development
  • Samsung Galaxy Note 3
    • Note 3 General Discussion
    • Note 3 Development
  • Galaxy Note Edge
    • Note Edge Discussion
    • Note Edge Development
  • Samsung Galaxy Mega
    • Mega General Discussion
    • Mega Development
  • Legacy Devices
    • BlackBerry
    • Samsung Galaxy S5
    • HTC Desire
    • HTC Hero S
    • HTC Merge
    • HTC Pro 7
    • HTC Wildfire S
    • Huawei Ascend II
    • LG Apex
    • LG Genesis
    • LG Optimus F7
    • LG Optimus U
    • LG Splendor
    • Motorola Defy XT
    • Motorola Electrify
    • Samsung Acclaim
    • Samsung ATIV Odyssey
    • Motorola Electrify 2
    • Samsung Axiom
    • Samsung Galaxy Note 2
    • Samsung Galaxy S Aviator
    • Samsung Galaxy S II
    • Samsung Galaxy S III
    • Samsung Gem
    • Samsung Galaxy S4
    • Samsung Note 7
    • Samsung Galaxy S4 Mini
    • Samsung Mesmerize
  • Tablets
    • Windows Phone Discussion
    • Asus Eee Pad Transformer
    • Windows Phone Apps & Media
    • Asus Eee Pad Transformer Prime
    • Galaxy Note 10.1
    • Galaxy Tab 8.9
    • Galaxy Tab 10.1
    • Galaxy Tablet 2 7.0
    • Galaxy Tablet 2 10.1
    • HP TouchPad
    • HTC Flyer
    • Kindle Fire
    • LG G Pad 7.0
    • Motorola Xoom
    • Nexus 7
    • Tab S2
    • LG GPad 8.0 V2
  • Other
    • The Lounge
    • Buy/Sell/Trade
  • Trash
    • Trash Bin


  • Google Apps
  • Alcatel Shockwave
  • Blackberry 9350
  • Blackberry 9850
  • HTC Desire
  • HTC Hero
  • HTC Merge
  • HTC One V
  • HTC Wildfire
  • Huawei Ascend II
  • LG Splendor
  • Motorola Electrify
  • Motorola Electrify 2
  • Motorola Electrify M
  • Moto X
  • Odin 3.09/3.10
  • Samsung Aviator
  • Samsung Axiom
  • Samsung Galaxy Note II
  • Samsung Galaxy S II
  • Samsung Galaxy S III
  • Samsung Galaxy S4
  • Galaxy S5
  • Samsung Mesmerize
  • Samsung Metrix
  • Samsung Repp
  • Samsung Galaxy S6
  • Samsung Note III
  • Samsung Galaxy Note 4

Found 33 results

  1. READ THROUGH FIRST BEFORE DOING. MAKE SURE IT APPLIES TO YOUR SITUATION. THREAD WAS WRITTEN FOR PEOPLE WHO WERE ON STOCK 4.3. ANYTHING BELOW 4.3 WILL NOT WORK WITH THESE FILES. SAME PROCESS, JUST NEED THE RIGHT FILES YOUR STOCK TOUCHWIZ VERSION. Works with Windows XP, Vista, 7, 8, 8.1, and 10. Hey guys. If you're an idiot like me, you might have flashed the wrong firmware for your phone and now the Galaxy SIII is as useful as a brick. Well, you've come to the right place. I accidentally flashed the MD4 radio on my SCH-R530U. After countless hours of research I finally conceived a plan on how to revive the phone. Symptoms of a Soft Brick: Bootloops, Stuck at Galaxy SIII screen, uhh and other stuff where the display actually turns on. If it does any of these, wrong thread. Symptoms of a HARD BRICK (what you're probably here for): Power does nothing, no output to display, no download mode, no recovery mode, computer recognizes it as QHUSBLOAD or something like that. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Let's get fixing. You'll need: 16 or 32GB CLASS 10 Non UHC-I MicroSD Card (complicity matches internal memory of the phone, although I used a 32GB SD card for a 16GB phone and it worked just fine), a hardbricked Galaxy SIII duh, a Windows PC with a SD Card reader, MicroSD to full size SD card adapter, proper files (included later), a wall charger, and time. I'm writing this thread to try and not have people go through hours of research to get their phone back. 1. Download all the required files. 2. Make sure that the SD card is class 10, non UHC-I (I used a SanDisk Ultra 32GB card), and has no files on it. ALL FILES ON THE SD CARD WILL BE OVERWRITTEN. 3. Unzip the Win32DiskImager program and run as administrator. YOU MUST BE AN ADMIN ON THE PC. 4. Put the MicroSD card into the Micro to full size adapter and plug it into the PC (if you haven't already). In the DiskImager program, click on the drop-down box under device, and select the SD card's drive letter. Mine was F: for example. 5. Click on the folder-looking icon and point it towards the file named "SCH-R530U_CND4_debrick.img" once downloaded. 6. Once you are sure that that is the drive letter click "write" and then "Yes". The write process should only take a couple of seconds to finish. Once finished, take out the MicroSD card from the adapter. 7. Open up the Samsung Galaxy SIII. Take any existing MicroSD for SIM card out as well as the battery. Put the SD card that we just formatted and insert it into the phone. Plug the phone in using the wall charger. The red LED should light up indicating that the phone still knows that the MicroUSB slot still exists. If there is no red LED, then this will probably not work. 8. Reinsert the battery. The phone may start up on it's own or you may have to hold down the power button. My phone started on it's own. If all goes right you should get output to the display and maybe boot into Android. If you were like me and flashed the wrong ROM, you're gonna need to flash a new one. 9. For the people that the phone booted into Android, you MUST have the SD card in your phone or else it will become unbootable again. Don't want to have to have the card in there 24/7? Keep reading. 10. For both the groups of wrong ROMs and anti SD booters, you'll have to flash the stock TouchWiz firmware. So backup your data (if there is any) and download this file: 11. This file will take people that were still running 4.3 and move them up to 4.4.2 KitKat. People that already had 4.4, this will work too. I was still on 4.3 because I rooted. 12. Open Odin Download: 13. REMOVE THE SD CARD FROM THE PHONE OR ELSE ODIN WILL WRITE THE BOOTLOADER ONTO THE SD CARD WHICH MEANS YOU'VE SUCCESSFULLY DID NOTHING YOU WANTED TO DO. 14. Press "start". No, not the Start Button. Start in Odin. Yeah I'm bad at this. 15. This will take several minutes to complete. Be patient. Do not touch the phone just to reduce the chance of something screwing up. 16. If Odin finishes and says "PASS!" in a green box, congratulations! You've just successfully unbricked your Samsung Galaxy SIII! (Yes you can boot without the SD card now too. If you want to keep the SD card as a "Oh sh*t I messed up" card, feel free. But you can use the card normally by using a free Windows program called Minitool Partition Wizard and make the card normal again by deleting all the small partitions and creating one big one.) If this helped you, you're welcome. If you wouldn't mind swinging by my YouTube channel and giving it a sub, it would be greatly appreciated. Twitter: realZekTech Instagram: zek_tech Have a great day with your SIII!
  2. So this came in...

    So starting Monday you can get one of these for a penny on a new contract. Not a bad phone for the average person.
  3. Does anyone have a 4.4.2 debrick file for the galaxy s3 r530U 16gb model ? I requested this earlier but only got the 32gb model which is not compatible with my 16gb version of the s3.. HELP!
  4. Odin 3.09

    Version 3.09


    This is the latest version of Odin - for your flashing pleasure. Simply unzip the file and run as admin.
  5. Samsung Galaxy Note 2 For Sale

    Up for sale is my Samsung Galaxy Note 2. This phone is used but in very good condition. The phone is rooted and currently running Halo ROM. It includes the charger, USB cable, 4G SIM card and an Otterbox Commuter case, which was on the phone for the majority of its life. I have lots of pictures so I will attach as many as I can. If you have any questions please do not hesitate to contact me. I'm going to leave this here for a few days and if I don't get any offers it will be going to eBay. I am asking $400 for everything, but I will consider any offers. I will pay the shipping. Full Name: Myles Douglass Location: Waterloo, Iowa Price: $400 or best offer PayPal Address: Thanks!
  6. I have an upgrade coming up on the 29th. I have the Motorola Electrify and ready for an upgrade. I've been looking at a few phones...and I'm having a hard time deciding what to get. I mostly use it for facebook, pictures, sometimes skype, and to keep up to date on sports as they happen. The phones that I'm looking at are: Samsung S3, S4, Mega Motorola Moto X HTC One Thank you in advance for all that respond. Greatly appreciated.
  7. Alright guys, I know I've been here a lot talking about different ROMs and such, but I think I found a decent ROM. It definitely has it's moments though. I have the AOKP ROM installed currently and I love it. Could be better, but from what I've tested, I like it by far the most. Be warned, this is just a Nightly build and I don't really know if it's official. Here are some troubling things with it that I have found. The system will randomly restart. I haven't pinned why it does it, but it usually happens when I'm trying to load a heavy app like a game. Ex: Tapped OutPhone: Calls are flawless, however if you make a call and try to hang up, the phone app hags and you can't end the call. The other person has to end it for you. This is troublesome when talking to an automated process like your voicemail.Camera: Camera also works good. However if you use HDR and take a picture, the app will hag and it will save a blank file. It seems that there is no extension on the file. I have not tried to manually name a file yet.. I will try that and get back to you guys.Messaging: Also works well, however do not send a message that will be long enough where it automatically sends two messages, it won't send the message at all. It just "fails". You can send one just fine, receive MMS/SMS, have not sent a picture yet, but have received one. I'll play more with this later and get back to you.The Cellular reception bars don't really display anything? It tells me that I have 4G, 3G, or X1, but it won't give me a signal strength.. or it's the same color as the background one; can't tell. F-Charge doesn't turn on...? But it seems that my phone charges REALLY fast, which is fine with me. I plugged in my phone this morning for about 10 minutes and it went up about 10%.The Torch button is sort of finicky. It works, but it doesn't. It just seems weird.. Or its just a delay.GPS works good, no issues with that yet.Cellular Location: I've noticed this isn't totally right on Google Maps.... Like it was miles off. I'll play around more with this to test it. With that said, WiFi location works great.Have not test Bluetooth. I don't really have any Bluetooth devices besides my Laptop.*#*#INFO#*#* works via the phone on this ROM.One thing this ROM could use is a music player.. not necessary, but it would be nice. I bought Shuttle+ though and I love it.When you plug in Headphones, the ROM doesn't tell you that you do. It would be nice that it recognizes that you do, just for some feed back. With that said, Shuttle did pause when you unplugged them though. However it had an option where you could plug them back in and the music would resume, but since the ROM doesn't really recognize that, it just does nothing. Not a big deal, just something I noticed.Brightness works good, the auto function works well also. Battery life has been good for me. I haven't had the phone long enough to really test it though. Plus its better than my HTC Hero S, so I don't really care... LolNotifications: Some apps don't really work well with notifications. However, it seems to be doing fine now. It might have just taken a few restarts in order to really set them in stone. If you guys want any more information, let me know. I'm also going to link the developer for this ROM, to this forum. I just wanted to give him some feed back I can also take screenshots.. if you want.... Dominic EDIT: Added another bullet point.
  8. SOLD Samsung Mesmerize sch-i500 like brand new, excellent condition. clean esn# has never been rooted comes with stock oem battery. no SDcard you need your own. both have stock firmware version 2.3.4 gingerbread i sold one, i have one left for 50.00 o.b.o Location:ellsworth maine Price:50.00 USD you pay shippng i do have paypal upon request
  9. Hi guys, I just finished following your excellent root guide for my little brother's Galaxy Axiom. It went flawlessly, thanks! The purpose of the root was to allow us to swap internal and external SD card locations by using a script. The Axiom only comes with 2gb internal, and with the new ban on moving apps to external storage we aimed for this solution. Unfortunately the only options are for the Galaxy S3 and Galaxy Note2. Do you guys have any advice? Thanks!
  10. Preorders for the Galaxy S IV start April 16th! The best part of this whole thing is that our version of the S4 passed the FCC before ANY other carrier. Take that VZW - ATT - Tmobile! We may not launch it first, but who knows? Still exciting! --Check it out-- Recent FCC approvals: USC's SIV page: Funny comments on how VZW sucks - because they didn't announce it first. - LOL:
  11. Galaxy S4

    It is official!! U.S. Cellular will be carrying the newly announced Galaxy S4. They just announced it about an hour ago on their Facebook page. I thought I read "sometime in April", but I can't find for sure where I read that.
  12. Samsung Galaxy Metrix 4G Now Available

    The Galaxy Metrix (basically a rebranded Stratosphere on Verizon) is now available. It features a 4.0 inch touchscreen, 5MP rear-facing camera, 1.3MP front-facing camera, and 4G LTE. It's available for $129.99 after $100 MIR.
  13. So the question is the title. But I was talking about this method it works on the Verizon Galaxy S3, so why not our US Cellular one?
  14. K, not going to go too deep in this, got a replacement on the phone, COMES 2.3.5 SHIPPED! Anyways, did the "" unlock method, gives me the error that happens when unlock won't work. So am I basically screwed over by Motorola? Also do this Pudding method work for Electrify? Peace, and thanks guys. Pudding Link: Saddened.
  15. The last couple of weeks, my Aviator has been getting worse and worse. It is locking up at least once a day. And it's doing it at with the most mundane tasks. Once was while I was browsing with Dolphin. Once was while I was going through G+ posts. Many times, I just hit the power button to wake up the phone and nothing. Many times it has locked up on me overnight resulting in my alarm not going off. I've rooted the phone, but other than SuperUser, TitaniumBackup, there is nothing that I'm doing that is out of the ordinary that a regular user wouldn't be doing. And I've replaced the rootable kernel with a stock one (FG04), so I know it's not an unofficial kernel issue. I know that I could try to use a logcat to isolate the issue, but I don't have a lot of experience with that and wouldn't now what to look for. So, I'm just here to find out if anyone else is having issues or if it's just me? My wife has an Aviator as well, and while hers does lock up occasionally, it's not nearly as bad as mine. I think she has to reset her phone about once every other day or so. And her's is completely stock. Not rooted or anything.
  16. NFC Problems

    Right after I flash A ROM or take it back to stock the NFC will work for about 5 Minutes but after that time If I try to turn on NFC it will automatically turn itself off as soon as I Press the button... Help Please... Let me know if you need more information
  17. Hey everyone! Just wondering if there are any MIUI roms that will work for our device. Thanks!
  18. As much as i hate to be the bearer of bad news, I think this needed to be shared on here, and @sno ( if posting the article like this is prohibited, ill take it down and just have the link posted) Samsung loses some developer support for Exynos-based phones "Remember when many U.S. customers were thrilled that they would finally be able to enjoy the quad-core Exynos 4412 chipset together with LTE in the Galaxy Note 2? For most of Rootzwiki's readers, though, the first question we ask about a new superphone is "will it have developer support?" Unfortunately, the Galaxy Note 2 and other Exynos-based phones will not have the same developer support that the newest Snapdragon, TI OMAP, and Tegra 3-based devices enjoy. CyanogenMod/Team Hacksung developer codeworkx, among others, have withdrawn support for the international version of the Galaxy S III, citing a lack of developer support from Samsung for its signature chipset. Other Samsung Exynos-based devices facing decreasing support from developers include the international Galaxy S II, the international Galaxy Note and all versions of the Galaxy Note 2. In a conversation I had with Codeworkx, he pointed out that AOSP ROMs running on new and recent Exynos-based devices face a variety of bugs because of failure on Samsung's part to release source code for its Exynos chipsets. For example, bugs in the international Galaxy S3 (i9300) include certain camera features, broken Bluetooth and WiFi tethering, and unsupported TV Out. In the international Galaxy S2 (i9100), issues include incomplete Jelly Bean support from Hardware Composer (referring to the Mali GPU included in the Exynos chipset), broken camera recording, slow transfer of data over USB in Mass Storage mode, and TV Out (as in the i9300). The international Galaxy S3 hasn't completely lost CyanogenMod support though, as developer Xplodwild is still supporting the device at the moment. I’ll stay away from all exynos powered phones as long as there is no proper support from samsung in form of documentation and sourcecode (especially userspace) to get aosp properly working on it. - CyanogenMod/Team Hacksung developer codeworkx Both codeworkx and other developers I've talked to have said that Qualcomm, nVidia, and Texas Instruments all provide a greater measure of support for their system-on-a-chip (SOC) processors, thus devices with those chipsets will receive more support from the development community. While the Snapdragon series and the Tegra series come with more support than the Exynos series, Texas Instruments provides the most extensive support of all for its OMAP chipsets. Unfortunately, Texas Instruments announced that it is shifting its focus away from smartphones and tablets for its OMAP architecture. As codeworkx and others have also pointed out, Samsung is under no obligation to release documentation or source code for its Exynos chipsets, just as Qualcomm, nVidia, and Texas Instruments are under no obligation to do so. SOC-specific code is proprietary, and is regarded a trade secret, though Samsung is the most secretive of the four companies. It's also important to note that proprietary code is not covered by the General Public License requirements and is entirely different from device manufacturers (such as HTC, Motorola, and Samsung) releasing kernel source for their Android-based handsets and tablets."
  19. I have a Samsung Galaxy S2 R760 for alltel. I installed CM9 then flashed CM10 and ran into a few issues and for some reason my backup copy got erased. So I downloaded the stock odin files for the usc galaxy s2 flashed them over and now I have absolutely no data. I tried flashing other roms to see if I just lost a file I needed but so far no luck. My job requires driving so I need my gps. If you can help me please do so!
  20. Please HELP!!!

    Hello all, Ive been a heavy flasher going through the mesmerize, electrify, GS2, aviator, electrify2, and now the GS3. I have never messed up a flash before or encountered problems. I tested a few Jelly bean roms for the GS3 and i found the liquid build to be the most reliable and stable. When i was on stock i used the GS3's encryption function for added security to keep a roomate out of my phone. I flashed the liquid build and then used the encryption feature and i started having data problems so i went to unencrypt it, when going to settings> security> encryption. However rather than it saying "unencrypt" like it should it only says "encrypt phone" which i have already done, when i click it nothing happens. I have went into recovery and tried multiple factory resets, tried reflashing stock/liquidbuild/other roms and it will not flash anything, have even tried odin and it will not work. Because it is encrypted it will not mount something and therefore i cannot reset the phone or flash anything, i either need a harder form of a reset or a way to make the liquid build fuctionalbility of unencrypting the device to work.If anyone has had this problem b4 or if you have any advice as to things to try i would greatly appreciate it. Thanks so much, you all are my last hope.
  21. We enjoy Android for what it is. Open source goodness. We're coming from Verizon with a Droid Incredible 2. Had no problems with the process of rooting and installing Cyanogenmod which we loved for zero bloatware. After all we would be just fine with android stock out of the box like god intended but for whatever reason few companies get that the customer’s liberty is paramount, not their ability to strike padded deals over drinks and golf games…not that drinks or golf games are bad, mind you. Admitedly I am pretty much a n00b and no matter how much I read (2 days now on this phone) a lot of this just doesn’t make sense. I was hoping someone here sees an inherent problem or can help me figure this out with a step by step. We're trying to get this either booting in to Cyanogenmod...or back to stock with no counts so I can take it back and just buy a friggin pantech. (kidding about the pantech btw) We’ve tried just about everything to install either the Cyanogen nightlys or the new monthly. We have root. Wiped data/Factory reset + wipe cache + wiped Dalvik Cache, install from zip a compressed file from HERE via both internal memory and SD card (formatted both ways) but we get this message every time: Installing update… Assert failed getprop(“ro.product.device”) == “ d2usc” || getprop(“ ==”d2usc” E:Error in /sdcard/cm-10-20121027-NIGHTLY-d2usc. Zip (Status 7) Installation aborted. CWM-based Recovery v5.5.0.4 ODIN MODE PRODUCT NAME: SCH-R530U CUSTOM BINARY DOWNLOAD: Yes (4 Counts) CURRENT BINARY: Custom SYSTEM STATUS: Custom QUALCOM SECUREBOOT: ENABLE
  22. Hey to the forums. Need some help with this rooting situation. I have a Samsung Galaxy S2 under Carolina West Wireless contract. was wondering if there was any info on here on how to root it to install new Jelly Bean ROM and maybe a new kernel. Can't seem to find any information on my specific carrier's model. Any help and info would be greatly appreciated. Here's my "About Phone" information.
  23. I recently read a viewpoint on the entire lawsuit that put new light on the proposed ban of certain Samsung phones by Apple. In the past, when facing lawsuits from Apple (HTC, anyone?), companies have simply updated their software pre or post launch to avoid infringement. My argument is this: Many of the models that Apple seeks to ban are running older software (2.x.x) including the SII's, the S 4G, and Droid Charge. Android's new software is not only meant to streamline Android and even run better on lower-spec hardware, it also finds loopholes around the patents Apple is defending. So, a simple solution to keeping the Galaxy phones available for sale in the US if they are banned via their old operating system? Update them to 4.1. In short, Apple suing the pants off of Samsung may just force a lot of companies to expedite 4.1 upgrades to their phones to keep them available. Just a thought. Yours?
  24. Google Wallet?

    Does anyone know if USCC plans to enable Google Wallet on this bad boy?
  25. I am first of all upset at the terrible performance of my Galaxy S III's reception. Specifically it's radio. This is well documented in another post here and by the fact there is a rumor of Samsung replacing the phones. In the mean time I have been using my S III on CDMA only while at work and other areas where the data signal wasn't constant between CDMA and LTE. Band aid to a problem that should have been solved before releasing the phone. Today I started reading up on Samsung radio's because I have thought all along this is a hardware issue. The following articles are what I found and in my humble opinion, further my hypothesis. Back in December 2011, Samsung released the Galaxy Nexus under the guise of a Google phone. It was released on both GSM (AT&T, T-Mobile) and CDMA (Verizon/Sprint). The CDMA version was plagued with reception issues similar to the S III is having right now. I first found this article that explains in great detail why the radio in the Galaxy Nexus is inferior on CMDA. Read this, its a great explanation: http://mobilecentral...on_GSM_and_CDMA Then I found a forum post about how this specific radio plus Verizon's CDMA infrastructure equals problems. http://androidforums...zon-radios.html Not a objective post, but insightful none the less. Fast forward to now, We have S III users with no issues and others with major issues. My completely unscientific research and purely speculative opinion is: Samsung used the VIA Telecom CBP7.1 CDMA2000 baseband modem is some of the S III's and these are phones having problems. (Plausible but not probable). The baseband modem in the S III is another VIA Telecom and this one is having similar problems to the Galaxy Nexus on Verizon. (More likely). I could be completely off base here because Samsung could have used a Qualcomm modem in the SCH-R530 US Cellular S III. But I still think there are issues on the backend that CDMA providers like US Cellular and Verizon need to work out on switching signals between 3G and 4G between tower and phone. I apologize for the rambling, but I am disgruntled at the performance of my S III, US Ceullar's LTE spectrum, and CDMA in general.