For updating you might have to download the latest Play store APK file and install it by copying the file on to your device. Try reinstalling the app or update the Play store app in case not working. This method might be able to fix most of the errors. Now come back to Google Play and you might be prompted to accept the licensing terms and Play store will start working. Go to Settings-> Accounts and remove your Google account and add it back. If the two steps above does not work, you need to remove your Google account and add it again. Once you fix the data and time, come back to Play store and check. This error even happens on Windows Phones as well. A lot of times Play store will not work properly if the date and time is not correct. Open the app and hit clear cache button and also force stop this app.Now try opening the Google Play store again and see if the issue is fixed.Ĭheck if the data and time on the device is correct. For this go to Settings > Apps and scroll to All apps section and find the “Google Play Store” app listed there. So the easiest solution is to clear the cache. One of the reasons for this error could be the cache of the Play store.
but I digress), and clean out the directory manually for a start.How to Fix Google Play Store “No Connection- Retry” Error The only thing I would suggest is to use File Explorer (just as I type this I realised yeah, root. Why /cache and /data/local/download? it is found in the init.rc script in the ramdisk of the ROM in question which has the following environment variables that tells the Google Play store, where to save the downloaded apps. Rm /cache/download/downloadfile*.apk >/dev/null 2>&1 system/xbin/busybox mount -o bind /data/local/download /cache/download # bind mount /data/local/download to /cache/download if cacheĬACHESIZE=$(df /cache | tail -n1 | tr -s ' ' | cut -d ' ' -f2 | tr -d )ĭATAONLY=$(getprop dalvik.vm.dexopt-data-only) (see this script below to see what the second trick is about) #!/system/bin/sh The other trick is that /data/local/download is re-binded to the /cache/download directory. The trick employed by ROMs is this, the /cache/download is either sym-linked to /data on the /data partition. If that fails, then it sounds likely that the /cache partition is very small not to hold the downloaded files.
Maybe that's what you should try doing, reboot to force the system to clean up the directories and try again upon bootup? Some ROMs do have this facility or feature in place, called run-parts, which is invoked by the busybox which does this clean up on boot to clear out the temporary downloaded files saved in the specified directories. Its indeed quite possible that either the two directories residing on the filesystem, /data/local/download or /cache/download is probably full of temporary files and is not deleted which contributes to the symptoms of the app not installing after 100% downloaded.
0 kommentar(er)
