and is hosted using the best US company equipment, IBM systems on US soil.We do not outsource to India like Microsoft 365 and most of our other competition does.Thankfully, we’ve put together a list of the most common problems plaguing Android Wear users, as well as bits of advice on how to get around them.A lot of users on the Google product forums have been complaining about the battery on their connected smartphone draining faster than it should.A defective SIM card won't be replaced if it's been more than 1 year.
To perform initial activation/setup on your 3G smartphone or basic phone, view this info. We back it up with our 15 Day You'll Love Us Guarantee.If you're not 100% happy with your phone, you can exchange it for a new phone or return it for a full refund.How come I am being constantly prompted to update to the buggy 6.0 instead of the rectified 6.0.1? However, when I go to About Phone and check for new OS software, I am being prompted that my software is already up-to-date. Let's take it this way: Assume that these are the Android versions - build numbers for your device: Android 5.1.1: build LJKRTY; Android 6.0.: build MOUIPV; Android 6.0.1: build MOUIPW When you would switch from build LJKRTY to MOUIPV a lot of the files required for Android 6.0 would be upgraded. By the way, it is possible that the update for 6.0.1 may be a full blown platform upgrade but your software updater is stuck at 6.0 simply because it is silly. However, when I go to About Phone and check for new OS software, I am being prompted that my software is already up-to-date. I just edited my question to point out that this is a UK Moto G, if that is relevant. Your original question was "How come I am being constantly prompted to update to the buggy 6.0 instead of the rectified 6.0.1? Your new update in question is not in consonance with your original question but can suffice as a new question.Since the manufacturer came to know about a couple of bugs in the recent release, Now there is no point in applying a patch if at the first place both the vulnerable and relevant code isn't there. You can attempt to clear its data (if it is a separate app), force stop it (or reboot) and attempt to check if it still requires to download Android 6.0.