Be wary of "forcing" OTA updates using Framework Services trick, breaks stuff
I've seen this posted before in many of the "4.1.2" threads, but the info is likely to get buried in there, and since I have personally experienced this myself with my GNex, I figured I'd post this in a new thread.
The method of force stopping/clearing the data of Framework Services in the All Apps list to force any OTA to download will cause you a lot of headaches after the update. There are a couple of issues that I could see.
Firstly, ANY app (not just Google apps) that uses push notifications for anything WILL break. The only way to fix them is to either force stop/clear data from ALL of those apps (meaning you might potentially lose important app data as this basically resets the app back to when you first downloaded it), and set all of them back up again, OR to do a Factory Reset of the entire device after your device is updated.
Secondly, you will NOT be able to download apps from the Play Store weblink and "push" them to your device. The Play Store will NOT see your device anymore as it won't be in your devices list. There might be a way to fix this, but I haven't found it, aside from again, doing a Factory Reset and setting up your device from scratch. Even if I logged out/deleted my Google account, and re-logged in/re-added, this did not fix the problem.
Thirdly, Google Music/Play Store purchases of Books/Movies/Magazine/Music seem to be broken at times. Whatever the authorization process Google uses, you break it when you clear Framework Services. This happened to me once, and might have only been a one-time deal, but please be wary of this.
Now, like I've said, I've run into these issues on my Galaxy Nexus while forcing OTAs. The only way I could proceed with my newly updated device without constant Google Services/Play Store/Notification issues was to completely reset my phone and start from scratch. Now I know some people like to do this between major updates anyway, to start the device fresh, so this wouldn't apply to you anyway since you would update and then immediately Factory Reset, but if you're just planning on updating and keeping your device configured the way it is now, you will run into these issues (and potentially others that we don't know about yet).
A better idea to me would be to either wait for the OTA to be pushed automatically, or to save yourself time, flash to stock using the new factory images. Would save you a lot of time by doing that, rather than figuring out what apps broke and what you need to fix, and how to fix them.
Please be wary of this, and know the consequences if you do attempt it.
I've seen this posted before in many of the "4.1.2" threads, but the info is likely to get buried in there, and since I have personally experienced this myself with my GNex, I figured I'd post this in a new thread.
The method of force stopping/clearing the data of Framework Services in the All Apps list to force any OTA to download will cause you a lot of headaches after the update. There are a couple of issues that I could see.
Firstly, ANY app (not just Google apps) that uses push notifications for anything WILL break. The only way to fix them is to either force stop/clear data from ALL of those apps (meaning you might potentially lose important app data as this basically resets the app back to when you first downloaded it), and set all of them back up again, OR to do a Factory Reset of the entire device after your device is updated.
Secondly, you will NOT be able to download apps from the Play Store weblink and "push" them to your device. The Play Store will NOT see your device anymore as it won't be in your devices list. There might be a way to fix this, but I haven't found it, aside from again, doing a Factory Reset and setting up your device from scratch. Even if I logged out/deleted my Google account, and re-logged in/re-added, this did not fix the problem.
Thirdly, Google Music/Play Store purchases of Books/Movies/Magazine/Music seem to be broken at times. Whatever the authorization process Google uses, you break it when you clear Framework Services. This happened to me once, and might have only been a one-time deal, but please be wary of this.
Now, like I've said, I've run into these issues on my Galaxy Nexus while forcing OTAs. The only way I could proceed with my newly updated device without constant Google Services/Play Store/Notification issues was to completely reset my phone and start from scratch. Now I know some people like to do this between major updates anyway, to start the device fresh, so this wouldn't apply to you anyway since you would update and then immediately Factory Reset, but if you're just planning on updating and keeping your device configured the way it is now, you will run into these issues (and potentially others that we don't know about yet).
A better idea to me would be to either wait for the OTA to be pushed automatically, or to save yourself time, flash to stock using the new factory images. Would save you a lot of time by doing that, rather than figuring out what apps broke and what you need to fix, and how to fix them.
Please be wary of this, and know the consequences if you do attempt it.
Last edited:
