Here are all the possible fixes you can try to fix this dreaded error. How to Fix Unfortunately Google Play Services Has Stopped Error on Androidįortunately, it’s quite easy to fix the “Unfortunately Google Play Services Has Stopped” error on Android. “Unfortunately Google News has stopped”.Why is my phone saying Unfortunately Google Play Services has stopped?.How do I reinstall Google Play Services?.How do I fix “Unfortunately Google Play Services Has Stopped” on my Android?.
What causes the “Unfortunately Google Play Services Has Stopped” error on Android?.FAQs About the “Unfortunately Google Play Services Has Stopped” Error.Getting Google Play Services Working Again.Uninstall the Recent Google Play Services Update How to Fix Unfortunately Google Play Services Has Stopped Error on Android.but I digress), and clean out the directory manually for a start. 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)
