Hi , i managed to face error 963 , i read quite a lot about it but got to realize that all thoughts about it had been off , here are some hints :
1 - clearing cache / data / google account is bs , it never solves it as claimed
2 - the error rise only on attempting to download / update an app that installs itself to SD card
3 - it happens only on lollipop version of android
Here are common symptoms that leads it to happen
1 - reinstalling google play store app from external source (unknown source) / backup even if 100% sure the source is clean
2 - integrating updated version into system using apps like link2sd / lucky patcher / happy patcher etc.
3 - integrating updated version of google play services into system using above apps
4 - unknown causes indicated by app moving somehow from rom side of launcher to user apps side
The theory about it :
some how google play app start to be recognized by lollipop as a user app not allowed to access SD card directly yet however it doesn't get the chance other apps get like requesting authorization to access SD card because apparently its handled through APIs and services but not through direct access of app to SD
Work around :
1 - if you were lucky and you still had the early stock play store you can uninstall update and luckily this will lead trusted play store app to kick in and take up its permissions again this is however not valid with all those who integrated updates or installed it from an external source
2 - unmounting SD card during updates help since it forces play store to use internal memory but this is like the peg leg solution
Trouble shooting the issue :
-now my question is , how to get lollipop to trust back play store to use SD card for those who know about the iffy lollipop security ?
-also maybe attempting to integrate exact version of stock play store / google play services back into rom might fix it but i never tested , so any body willing to post links to those ?
*as a side notice this error surfaced on several other devices than samsung so it lead me away from thinking its a knox security issue but i need a second opinion about that .
1 - clearing cache / data / google account is bs , it never solves it as claimed
2 - the error rise only on attempting to download / update an app that installs itself to SD card
3 - it happens only on lollipop version of android
Here are common symptoms that leads it to happen
1 - reinstalling google play store app from external source (unknown source) / backup even if 100% sure the source is clean
2 - integrating updated version into system using apps like link2sd / lucky patcher / happy patcher etc.
3 - integrating updated version of google play services into system using above apps
4 - unknown causes indicated by app moving somehow from rom side of launcher to user apps side
The theory about it :
some how google play app start to be recognized by lollipop as a user app not allowed to access SD card directly yet however it doesn't get the chance other apps get like requesting authorization to access SD card because apparently its handled through APIs and services but not through direct access of app to SD
Work around :
1 - if you were lucky and you still had the early stock play store you can uninstall update and luckily this will lead trusted play store app to kick in and take up its permissions again this is however not valid with all those who integrated updates or installed it from an external source
2 - unmounting SD card during updates help since it forces play store to use internal memory but this is like the peg leg solution
Trouble shooting the issue :
-now my question is , how to get lollipop to trust back play store to use SD card for those who know about the iffy lollipop security ?
-also maybe attempting to integrate exact version of stock play store / google play services back into rom might fix it but i never tested , so any body willing to post links to those ?
*as a side notice this error surfaced on several other devices than samsung so it lead me away from thinking its a knox security issue but i need a second opinion about that .
from xda-developers http://ift.tt/24uKXQ6
via IFTTT
Aucun commentaire:
Enregistrer un commentaire