Recent content by Samsung.Galaxy.S3

  1. S

    Gear VR registration/approval/shipping/arrival info & also problems.

    Via Samsung's website, it says Gift Shipped. However, I've yet to receive any tracking notification. :'(:'(:'(
  2. S

    Verizon S8 / S8+ Pre-Order Discussion

    Re: Verizon Pre-Order Question S8+ It has shipped with tracking a number! :D
  3. S

    Would you buy an S8 if it had no microSD slot?

    No. I would not buy it if an external sd-card option is not available. :)
  4. S

    What color looks the best?

    Red. However that is not an option.
  5. S

    Does it seem like the fingerprint scanner is on the wrong side?

    I'm with you. I'm a two-handed user (hold phone with left hand and use the right index finger for touches). So for me, the location of the fingerprint scanner is fine (though better if it's directly below the camera as stated many times).
  6. S

    Samsung Desktop Charging Stand.

    Why wouldn't the S8 charge on your existing charger?
  7. S

    LG V10 stuck on "Life's Good" screen but won't turn on

    Everything on the phone is wiped. It will be as if you just bought the phone brand spanking new.
  8. S

    LG V10 stuck on "Life's Good" screen but won't turn on

    Be prepared to pay $72 (if out of warranty) for LG to repair it.
  9. S

    LG V10 Bootloop

    Sign me up!
  10. S

    LG V10 Bootloop

    Yep. I got the same message. Out of warranty fix = $72.
  11. S

    LG v10 Smart Lock problem

    Umm, just change it to password/pin/pattern lock, no? :p
  12. S

    An open letter to LG in regards to the V10 bootloop issue

    I'm officially a Bootloop member as of Monday. :mad:
  13. S

    LG V10 Bootloop

    Another one bites the dust here. It occurred 01/30/2017. :mad:
  14. S

    Verizon gets marshmallow tomorrow... (Update: It is out now!)

    Re: Verizon gets marshmallow tomorrow... Open the floodgates! It's coming!
  15. S

    Verizon gets marshmallow tomorrow... (Update: It is out now!)

    Re: Verizon gets marshmallow tomorrow... The January 7, 2016 update [should have] addressed this already. It did for me.