Tag Info

Hot answers tagged

3

Most likely, a lot of Android devices will not receive the update. Only devices that have received updates recently from the manufacturer (Such as Samsung GS6) are likely to receive the security patch. Device like mine (LG Optimus Fuel/Zone 2) that have never received updates for any reason, will most likely be left vulnerable to the security issue. I am ...


2

Update will took some time to become available in every country. If you check on Sammobile, 5.0.2 was released today (2015-07-16), and it is for United Kingdom. There no version for other countries. You can flash UK version via Odin, but better wait some days for it to get released for other countries. After that you should be able to update it via OTA, ...


2

Turn off Wifi during the intial setup, it will skip that screen as all updates exceed 20-30MB which is deemed too large to do on a mobile connection.


2

Notes: OP already know the details, but I've elaborated things considering other readers in mind. I've assumed that the device is rooted, and my solution is tested on Android 4.2, 4.4 and 5.0, all running Play Store v5.6.8. (Sorry! couldn't test it on Kitkat but no reason to believe that it wouldn't work.) The solution by Craig is actually quite ...


1

Probably Not. Android updates before Lollipop checked each system file and replaced them but after Lollipop, the updates check the whole system block as a part and update it. Since rooting modifies the system files, the System Block won't match and the update will abort. Since you have a custom recovery, the update won't even go that far because you need ...


1

For a smartphone, you can expect security updates to be supported for 18-24 months. Google says Nexus devices receive updates for 18 months. Nexus devices may not receive the latest version of Android if they fall outside of the update window, which is usually around 18 months after a device has been released. The Nexus line is nominally supposed to ...


1

There is an idea by Firelord in the comment here which I think should work: The best way I think is to have a backup of the app (at least its APK if not the data files; APK of earlier version of an app can also be obtained from some websites (beware of malware) if you updated the app and doesn't have the backup) so that if you end up disliking the ...


1

Sounds like you need to update your Google Play Account and remove the old credit card. From your phone hit Google Play store app, go to your account, go add a payment method, or edit an existing one. Once there delete the old card and add the new one.


1

You're going to want to clear the cache of your Google services on the device. Note that this will remove your Google Account from the device - so you'll have to re-add it. Navigate to Settings > Applications > Manage Applications > All Clear the data for Google Play Services, Google Service Framework and Google Play Store Reboot the device Log ...


1

On some phones it can take very long, even to half an hour, so try to wait a little more. If that does not help you should try to do a factory reset and wipe /cache & /dalvik partition (from Recovery, if you have access to it). Usually this procedure would solve the issue: stuck on boot animation/reboot loops.


1

To answer your question: Installing the zip will delete (or change some apps) but not all. When you flash the zip it overwrites the "system" partition on your phone and so it changes which system apps are on your phone. Since google apps are system apps, but are not included in the CM zip, this is why you have to reflash gapps after because they get ...


1

It may be problem by the rom clear the data clear dalvik cache reinstall ROM This may help cause you may have directly the ROM without clearing data Footnote: Though in Android 5, Dalvik was replaced by ART, parts of the Dalvik stuff are still used (/data/dalvik-cache/arm/*; also see e.g. Should Dalvik Cache be wiped in ART). While in the end, ...


1

For Samsung devices (unbranded ones) the answers are pretty simple: As long as the model is the same (exactly the same, even the characters after the numbers), the ROM is compatible. (Usually the bare models without any special characters after them have more international firmwares). Yes, it's enough if you flash an international/regional firmware on top ...


1

The answers given were great but I felt something needed to be added: If you boot into Android, you should be able to download the OTA file directly from your web browser.


1

There are many ways to copy the files from PC into your SD card. Simplest is the Android's native MTP mode, which you might be having trouble with detecting the device in Ubuntu/Mint. Method 1 You can use ADB as mentioned here by Izzy. Setup ADB and detect device on your PC (see Is there a minimal installation of ADB), open terminal and enter: adb push ...



Only top voted, non community-wiki answers of a minimum length are eligible