kobester

Member
  • Content count

    91
  • Joined

  • Last visited

  • Days Won

    1

kobester last won the day on April 26 2012

kobester had the most liked content!

1 Follower

About kobester

  • Rank
    Becoming Kewl

Profile Information

  • Gender
    Male
  • Location
    Kansas

More Info

  • Device
    Moto X
  1. What they have done in the past says otherwise. They will either hold the update till almost no one has the phone anymore then send it out, or claim it was causing problems with their network and not release it at all or clam it needs more testing. They have done the first with the Galaxy S2 and the second with the Electrify M. This almost seems to be USCC's M.O. So they can get people to newer phones and bring in more money, also probably to try to lock down customers with new contracts. I know when my father went to upgrade from his s3 to the s5 he was forced into a new contract even though he had used his points to upgrade two months early.
  2. I know, I was just mentioning that it says that for all carriers and not specific for us. I hope that USCC does go ahead with 5.0 for us. It would be pretty boneheaded to keep us on 4.4.2. They have already proven that 4.4.4 doesn't cause any harm with their network with the new moto x and they will prove that 5.0 doesn't cause any harm with the new moto x and the nexus 6 if they update those. All that leaves it down to is them not wanting to update older phones.
  3. Android lollipop coming to moto x

    Money on it that they'll muck it up? Weren't we one of the first to get 4.4 (or 4.4.2?)? Then disappear! 5.0 is just too big a deal, they almost will have to get going on it. I'll be throwing a fit about it if they don't, and I'm usually not one to get worked up about updates. That was back when it was a flagship for Motorola. You do have to remember they also were also supposed to push out an update to the Electrify M for 4.4 and still haven't done that.
  4. Just saw through the Motorola blog that android 5.0 is slated to come to both moto x. While this is awesome news I kinda wonder if USCC will muck it up like the 4.4.4 release. Forgot the link http://motorola-blog.blogspot.com/2014/10/its-official-android-50-lollipop-coming.html?m=1
  5. Nexus 6 Finally on U.S. Cellular!

    So I was reading about android lollipop and managed to catch this "Nexus 6 will be available for pre-order in late October and in stores in November—with options for an unlocked version though Play store, or a monthly contract or installment plan through carriers, including AT&T, Sprint, T-Mobile, U.S. Cellular and Verizon. Specific carrier rollout will be subject to certification completion and will vary." Here is the link in case anyone wants to read the full article http://googleblog.blogspot.com/2014/10/android-be-together-not-same.html?m=1
  6. KitKat 4.4

    While I hope that is true it seems unlikely. At most they can require OEMs to put more google apps on their phones, at least that is my understanding. Unless they go all in and just require stock android on all devices. Even if they required stock android (with some moto like customizations) it would be impossible to reign it all in. I'm also guessing that OEMs would sooner build out there own version of android (at least the open source part) and cut out google entirely if that were to happen.
  7. So according to the rep I just spoke to with Motorola they are testing the update. I was also told that if I expect timely updates from Motorola I should look at switching to another carrier as USCC has always been tough to get their updates through to the customers. And as if to echo that the USCC employee I was speaking to earlier today about a different problem mentioned to me that they 2013 Moto X has reached end of life with them. When I asked what that meant I was told software and hardware support would be limited.
  8. Now that the new moto x is out I'm willing to bet that we won't be seeing the 4.4.4 update. Still hopeful we will be getting the android l update though.
  9. Had a chat with them earlier. I was given two options: pay $35 for a replacement right then, or send it in and be without for two weeks. Tried asking about an in store exchange and was hung up on.
  10. Neither are turned on, just tried it again and got the same thing. Yeah I know call waiting should never be touched for any reason, but it keeps happening. I'll be on the phone when someone tries to call they go directly to my voice mail. I won't even get a notification that they called till the voicemail pops up. I really don't want to root just for that, bit of it comes down to it I guess I will. Just pretty ridiculous that I have to root out to get a basic function to work correctly
  11. Okay I'm at my wits end here, for the last three months I've had call waiting removed from my account 5 times. Yet I was still paying for it and didn't ask it to be removed. For the last three months I've also been getting calls come in to where neither of us can hear the other. This has happened to family members as well when calling other people from a USCC phone. Finally I'm also having some problems with Synchronoss TEDC, it will not let me connect to any wi-fi network without fighting with it for at least 5 mins. I've done as asked and factory reset the phone, which solved the problem for all of a day. Now I'm being told that they can send me either a refurbished phone at no cost or a new phone for $35.00 which in and of itself wouldn't be a bad deal. Except it does nothing for the first two. Am I just supposed to keep getting my call waiting turned off and keep getting calls of dead air to where I have to call that person back? As a note this is happening on the 2013 Moto X on the old Primary Plus plan. I'm also in an area with excellent coverage for both 3g and 4g LTE.
  12. That's interesting, what could they be holding up the soak test for I wonder? As far as I know there wasn't any problems with any of the other carriers.
  13. Called both US Cellular and Motorola today. Got pretty much the same response from both. It will be coming out soon, tried pushing for more and couldn't get anywhere. So pretty much pointless.
  14. With the move from WebKit to chromium webview trying to use the 4.3 aosp browser is not going to work. There is a two different aosp based browsers on the play store. I haven't tried them just remember stumbling on them a little while back. One requires root though. Other then that you might want to check xda. Sent from my Moto x