Hi all,
thankyou very much for enabling nightly builds!
I have installed omni-5.1.1-20150630-hammerhead-NIGHTLY.zip
I have done it like fresh install, wipe data, chache dalvik.
But for some purposes does the OTA functionality not work. Even there are new nightly builds I get the message, the device is on a actual state, nothing to update.
I remembered for 4.4 it was necessary to uncheck Security within the OTA settings.
But this also didn't help.
Do you have any idea what the issue could be or is this currently not working?
Kind regards,
Chris
Same reason we've had OpenDelta OTAs get stuck before - weird things happen when the download server runs out of disk space.
We're in the process of getting a new server with more space set up, and also our server admin was away due to holiday stuff when we had the space run out this time around.
And how it works?
Related
Hello,
I have strange behavior every time my Hero connects to internet (via Wi-Fi and also 3G) -> I'm getting "com.htc.provider" crash... After this exception everything seems to be working (Exchange mail push, weather updates, google talk) but this happens every time the phone connects to the network (for example to check the mail).
I'm running Modaco's latest ROM.
Anyone had this problem? Found a solution?
Thanks,
Darky
I had that problem when I first applied the 2.0 Modaco ROM. I had done a factory reset to wipe it.
I tried a second time, using the recovery image to wipe the data and then applied the ROM again. That seemed to have fixed the issue.
Hope that helps.
Thanks.. So you think this is a matter of wiping the info before? Will it also erase custom applications, locale settings?
The wipe removes all data related to applications and set up so you lose everything you may have customized. Some things have changed under the new ROM so some of the data formats aren't compatible anyway (unless you want to hack your data files). The "com.htc.provider" issue seemed to have been related but I couldn't be sure. I just noted that doing the recovery ROM wipe and a re-install of the new ROM cleared the error - which was a very annoying error when connecting via WiFi (or disconnecting).
YMMV.
Thanks... Did "wipe" and upgraded to latest Modaco ROM - now it is perfect
I did a wipe from the rescue menu and re-installed this morning but I'm still getting the com.htc.provider error! I'm reluctant to try again immediately as I had a lot of set up done before the error re-surfaced. Has anyone any suggestions? Should I wipe the sd card too?
There's a suggestion on androidforums.com that it might be something to do with twitter (see here) but my friend has a Hero (with RUU ROM) and he's not getting the error!
http://forum.xda-developers.com/showthread.php?t=563684
enlightener said:
http://forum.xda-developers.com/showthread.php?t=563684
Click to expand...
Click to collapse
Thanks enlightener! Guess I'll just live without the twitter widget for the time being!
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Same here!
mbt28 said:
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Click to expand...
Click to collapse
I can't update to 4.3 because of the same reason.
In my case, I installed both vfx and vhifi.
I deactivated and turned both of them into safe mode and tried to flash the update with stock recovery.
However, I still got "assert failed: apply_patch_check system/vendor/etc/audio_effects.conf"
There is a way to get the OTA update back, but I repeatedly failed, and ended up with error.
Someone please help us!
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use 2-factor authentication via google, you'll need to add a new application password for your tablet.
I succesfully upgraded the system. As you said I replaced these file with the original ones. Now It works fine. The only problem is mx player doesnt work. I think they will update it soon.
plastikowl said:
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use w-factor authentication via google, you'll need to add a new application password for your tablet.
Click to expand...
Click to collapse
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
sabx13 said:
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
Click to expand...
Click to collapse
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
I'm pretty sure he meant tablet. I'm having the exact same problem on my N10.
plastikowl said:
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
Click to expand...
Click to collapse
A bit of a weird one.
Updated to CM12.1 Atares ROM :good: I have been running CM12 ROMS for ages and updated to the 12.1 via the OTG in settings and using Nightlies.
I have only noticed problem yesterday and going back to CM12 just causes more problems, also going back to the previous Nightly doesn't help
I cannot access Google Play Store. 'Check your connection and try again' All WiFi settings are correct etc... even when using mobile data, I still cannot get access.
My GT1905 has disappeared off my devices list on the play store too! I've also noticed that Google+ has disappeared off my phone too, but more interestingly my SUBCARD app has gone too! (not sure if others have gone but I noticed this as I like a subway :yum: ) But... if I go to the playstore on my phone (or PC/tablet etc...) via chrome it says it's installed! I cannot access it via my apps list.
So other than doing a wipe of my phone if there any other suggestions?
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Lennyz1988 said:
Did you perform a full wipe before updating?
You cannot just flash it over an old CM 12 you need a fresh install.
Click to expand...
Click to collapse
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
GiGoVX said:
Well I would of done if it hadn't come via the OTA updates, never noticed it went from CM12 to CM12.1 until Monday/Tuesday last week.
Will do a full wipe later on today and see what happens.
Click to expand...
Click to collapse
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
GDReaper said:
Custom rom OTA's are not like official rom OTA's. Doing a wipe is still recommended. Anyway, force stopping google play and clearing app cache and data might help you in this case.
Had similar issues on other roms, even though I wiped before flashing.
Click to expand...
Click to collapse
I tried clearing all data and cache and also force stopping. WhisperPush kept crashing too.
Wiped the phone and started again, all sorted now with CM12.1 latest nightly build
Cheers for the advice guys.
Hello guys,
I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization.
I formatted the phone after receiving the Oreo OTA and the phone is full stock.
Anyone know how to fix this issue?
Thanks!
VSTOLL said:
Hello guys, I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization. I formatted the phone after receiving the Oreo OTA and the phone is full stock. Anyone know how to fix this issue? Thanks!
Click to expand...
Click to collapse
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
v12xke said:
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
Click to expand...
Click to collapse
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates.
My build number ends with .019
VSTOLL said:
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates. My build number ends with .019
Click to expand...
Click to collapse
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
v12xke said:
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
Click to expand...
Click to collapse
There was no failed or hung syncs but I removed and added my account again anyway.
I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events.
My bootloader is locked.
VSTOLL said:
There was no failed or hung syncs but I removed and added my account again anyway. I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events. My bootloader is locked.
Click to expand...
Click to collapse
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
v12xke said:
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
Click to expand...
Click to collapse
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?
I found this post: https://productforums.google.com/fo...utm_source=footer#!topic/calendar/FzD9Y6ojci4
Theres a reply by Mikel Rodriguez that says:
"The cause of the calendar notifications failure is a change in the architecture of the calendar provider module. It is a content provider located at the application framework layer. Supposedly they changed the architecture of the module because it wasn't compatible with the doze feature of Marshmallow. So, all phones running Marshmallow or higher are fully affected by the failure. The only solution is to root, install titanium backup, make a backup of package com.android.providers.calendar, then uninstall it, then download and install the same package for version 5.1.1 (Lollipop). Because that version is not compatible with doze, it is necessary to remove it completely. Download "Boeffla Doze Control", open it and turn on "disable doze at start up" and "show toast message", then reboot, then open it again and check that doze status is off. That means that doze is not working. Calendar notifications will work again if you follow all the steps."
I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
VSTOLL said:
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?....... I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
Click to expand...
Click to collapse
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
v12xke said:
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
Click to expand...
Click to collapse
I'll wait for the next OTA then, and if it doesn't fix I'll try formatting and restore it with the Google tool you said.
By the way, I didn't received a incremental OTA. I live in Brazil, so the update arrived later here, I received it 2 weeks ago and was a 1GB download and I haven't received any security or incremental updates since that day.
I set an event and it'll remind me in 2 hours, I'll let my phone down and will not use it to see if the nofication will work, if it doesn't, I'll try this app: https://play.google.com/store/apps/details?id=com.github.quarck.calnotify&hl=en
Hi there, i searched all over the net, but all i found were older ways to do it.
Anyway, I am on 8.1 and I have a pending Pie update bugging me (restart now to update), I do not want to do it until the camera issues with gcam are completely resolved.
I have unchecked the "automatic system updates" in developer options, but the update was downloaded before that, so it keeps nagging me to update. I am afraid that if my phone reboots / runs out of battery ill end up with Pie (happened to my gf and brother). Camera means more than pie to me
I am unrooted. Tried searching internal storage for anything mentioning OTA but to no success. Can anyone help me find/delete these downloaded temp files?
Thanks,
jaka
Since we have an A/B partition device, maybe the update have already been applied. You can try to disable update app through adb using a computer, but I guess if you reboot, your device will be updated.