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
Related
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
I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
kabads said:
I had the update notification for 4.3 today and went to install it. Everything appeared fine. However, when the phone rebooted and showed my usual screen unlock, I swiped it in and then the phone crashes back to the X - so android is loading and I can see my wallpaper and the time and everything as usual, but screen unlock reboots the phone. The only other problem that I've noticed is that the forward camera doesn't work to use face recognition to get the screen to unlock - the screen is always showing as black when normally my face is there.
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
abaaaabbbb63 said:
Do you have an unlocked bootloader?
Click to expand...
Click to collapse
Yes - why? Can I download the data somehow using adb? What difference does this make?
Got the same problem on my Nexus 4, updated via normal Ota, unlocked bootloader and rooted.
Any solutions apart from a complete factory reset?
Sent from my GT-P3110 using xda app-developers app
kabads said:
Yes - why? Can I download the data somehow using adb? What difference does this make?
Click to expand...
Click to collapse
Well, you could make a nandroid backup. That way, you will have your data saved. After that, install a stock rooted 4.3 ROM and only restore data from recovery.
Or, Adb could work too. It would backup your data to your PC, and you could restore after you reinstalled the ROM.
I don't really know why, but many updates to 4.3 failed. That's why a data wipe is always recommended.
I always use Titanium Backup. It's very simple and easy to use.
I've used Nandroid before - not sure why I didn't think of it - thanks.
kabads said:
Any tips for a fix? I'd rather not wipe all my data as I'm on a slowish bandwidth connection for the next couple of weeks.
Click to expand...
Click to collapse
I had this exact same problam and was able to fix it without losing data, settings or installed apps.
My Solution:
Download factory 4.3 image and extract system.img. You need to untar the gzipped file and then unzip the included zip file to get system.img
Flash only the system.img and reboot. (fastboot flash system system.img)
When the phone is rebooted, root will be gone, but all installed user apps, data and settings should be preserved.
Background:
After the 4.3 OTA, my phone would reach the lock screen and receive notifications. Sometimes a call would make it through and I would be able to answer, but most of the time calls went straight to voicemail. Callmaster might have contributed to this behavior.
However, if I attempted to enter a pattern on the lock screen, the phone would immediately reboot.
I was rooted using SuperSU prior to the OTA. My Nexus was also affected by the issue were attempting to access the 4.2.2 Security Settings resulted in an error. I never got around to fixing that issue, but suspected that the 4.3 and 4.2.2 problem were related.
solution that worked for me: keep failing pattern until prompted to type in google account details to login, it then worked for me after that, no longer rebooting when unlocking
Hello, I recently got the September update for Moto X Pure and I want to know how to update my phone. I've read around and it seems that I need to restore to unrooted stock before I can flash the image as opposed to just flashing the image without doing anything else then re-install TWRP and reroot. Can anyone provide steps in how to do this?
Do you have systemless root?
Open SuperSU, settings, full unroot. if you have Xposed installed, you'll need to flash the xposed uninstaller through TWRP. Now to remove TWRP, you need to download the latest stock rom and flash only the recovery.img from your computer.
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Sean89us said:
Honestly I wouldn't mess with it. It's just a security patch. Wait until Nougat gets to our phone in a month or so then do a clean install (or follow the steps above) with that.
Click to expand...
Click to collapse
Is there a way to stop the constant notifications that I have a system update that needs to be applied?
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
eigerzoom said:
use titanium backup and freeze Motorola Update Services 8.0.2 , i believe should do it.
My question is where is the update stored?
can someone tell me the location in the root of the device that ota gets downloaded to?
I'm trying to find the latest security update and back it up, so I dont have to download it again if it is large.
I saw a huge hit on my montly data usage around 700mb which i assume was the update but all i found in /cache was Blur_Version.24.11.18.clark_retus.retus.en.US.zip and was only 6.53MB in size.
I also checked /data/data/com.motorola.ccc.ota/ ....nothing there
Thanks for any info.
I suspect my carrier is bloating my reported data usage, but i'm unsure.
Click to expand...
Click to collapse
The OTA update in January, dated Sept 2016, is 40.2MB in size and build number 24.221.8.en.US.
Not sure what is chewing up 700mb of data, but it isn't the OTA... Do you have automatic update on in the Play Store? There were tons of large updates in January, I may be exaggerating but it seemed like 2-3 times a "normal" month.
I got the notification of 8.2 Stable update but I am confused whether to update through official update app or through TWRP.
If I update through official update app will it create any problem since I have unlocked my device and rooted through TWRP?
What is the safest way to update without losing any data?
My suggestion is through twrp , since you can disable DM verify, once you've installed that ROM.
So I can't update it using official updater app since I've unlocked my phone?
Any other precautions before I update? Please help.
kernel.debugger said:
So I can't update it using official updater app since I've unlocked my phone?
Any other precautions before I update? Please help.
Click to expand...
Click to collapse
Backup your data and have a lot of patience during installation. For me installation took about half an hour.
kernel.debugger said:
So I can't update it using official updater app since I've unlocked my phone?
Any other precautions before I update? Please help.
Click to expand...
Click to collapse
Just do a backup in setting if you want, will backup your apps, calls and sms (your image, photos and videos wont be erased).
Now go to into TWRP and wip (Dalvik, Cache, System and Data..... DO NOT TOUCH internal or SD) then flash the .zip through twrp like any other rom, but remember, before you reboot you must disable DM-Verify or you go into bootloop. Did this then reboot. Warning! You phone wont turn on, be calm, is normal the first time after flashing. You must push the power button for (more or less) 10 second till the phone show MIUI logo.... take long time the first boot.
Your phone will be on 8.2.4.0, with twrp and unlocked booloader... easy and smooth. Then flash SU 2.78 from twrp to get root access.
But I have some doubts and questions and I need your help with the same.
> Should I still be worried that something must've gone wrong during initial flashing process and it can brick my device again at anytime?
> Should I clean up the data of apps installed in older MiUi 8.1 version? If yes than how should I go about it.
> How can I restore my synced messaged from Mi Cloud in new update? New update deleted everything but I have synced important data like Phone History, Contacts and Messages.
> In Device Certification it is showing "Uncertified". Will this create any problem?
> Should I go back to older version?
Kindly help the fellow member.
Thanks for you reading this patiently.
Somehow I have received malware on my stock, untouched G5 plus. I've performed a wipe of user data and performed factory reset from the boot option (power and volume key at startup) Still, the malware exists and redirects webpages to pop-ups even with fresh install.
Does anyone have an untouched factory ROM, that will receive all OTA updates ? Lenovo will not provide! Help very much appreciated.
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738 here
vantastic415 said:
Somehow I have received malware on my stock, untouched G5 plus. I've performed a wipe of user data and performed factory reset from the boot option (power and volume key at startup) Still, the malware exists and redirects webpages to pop-ups even with fresh install.
Does anyone have an untouched factory ROM, that will receive all OTA updates ? Lenovo will not provide! Help very much appreciated.
Click to expand...
Click to collapse
If you have a stock, untouched Moto G5 then there is something else going on... It is not possible for malware to infect the system after a factory reset, unless it is coming from an app you are reinstalling or your SD card.
acejavelin said:
If you have a stock, untouched Moto G5 then there is something else going on... It is not possible for malware to infect the system after a factory reset, unless it is coming from an app you are reinstalling or your SD card.
Click to expand...
Click to collapse
That's not quite true. There have been a number of vulnerabilities (like the Dirty Cow one) that can be used to get root, and then cause havoc on your system. In general, if you just get regular apps from the Play Store you'll be fine, but if you get external sources, who the hell knows.
You might want to contact Motorola support and see if they have steps. I would think flashing the stock rom would solve it.
I also didn't believe this to be possible, but unfortunately that's the situation.
I barely even install apps on my phone, or use my phone for much. I'm one of those weird people that stay largely disconnected from tech. I have whatsapp, color note, good budget, swype, and Amazon music. That's it. All from the play store.
The virus had to originate from the web. Occasionally I click on ads or "news" with interesting looking content. You know, the sort with 20 pages to click through and ads everywhere. I know better, but that's where it came from.
First virus in 31 years of computing. I guess now I get to learn about rooting Android and flashing ROMs. :good:
Thank you for the replies and link to a clean ROM. Very appreciated!
Edit: No SD card in the phone, and I've factory reset from within Android, and during boot. Erase cache, data, everything. Virus persists. =( oh well, no biggie now.
You have not got the dodgy whatsapp, should be removed from playstore now, but that was a advertising machine.
Perhaps I'm not understanding. In the provided link I don't see many ROM, just 4.
I have the standard G5 Plus (non Amazon) on T-Mobile. Model: XT1687. Build number NPN25.137-83. Any idea where I could get a stock ROM for this and get my phone back to virus free?
I've searched but can only come up with a TWRP flashable ROM, and I've no idea what TWRP means, but I see that for some reason it doesn't receive OTA updates, so that's unfortunately a no-go.
Thanks so much for the help! You all rock.
vantastic415 said:
Perhaps I'm not understanding. In the provided link I don't see many ROM, just 4.
I have the standard G5 Plus (non Amazon) on T-Mobile. Model: XT1687. Build number NPN25.137-83. Any idea where I could get a stock ROM for this and get my phone back to virus free?
I've searched but can only come up with a TWRP flashable ROM, and I've no idea what TWRP means, but I see that for some reason it doesn't receive OTA updates, so that's unfortunately a no-go.
Thanks so much for the help! You all rock.
Click to expand...
Click to collapse
If your phone is stock and with a locked bootloader, you need to contact Lenovo/Moto customer support and send it in for repair or replacement.
If your bootloader is unlocked, your warranty is void and you might as well learn about TWRP, root, and flashing ROMs.
The possibility of someone to code a virus that persists through complete flashing of the stock rom is not very likely... When you flash stock rom (correctly, via fastboot) you are completely wiping your phone and either erasing (formatting) each partition or flashing that partition back to its original factory image. If you are experiencing webpage redirects after flashing, it is far more likely that you are connecting to a network that has been in some way compromised. It is not uncommon for malware to redirect traffic in a network, and trivial to implement such redirections if you have privileged access. Think about how a business/hotel WiFi network redirects all traffic to their login page when you try to connect to a website. Just my 2 cents, but it's highly unlikely that someone targeted you with such a specific, sophisticated virus that it somehow found a way to survive when the entire phone is flashed, only to redirect you to ad sites.
---------- Post added at 06:15 AM ---------- Previous post was at 06:11 AM ----------
As for flashing, if you really want to return to stock you should relash stock images with fastboot instead of Twrp images. This will COMPLETELY wipe your device (user data, etc). When I read your first post I had thought you had already done this. If not, it should fix your problem. Here is a guide with links to firmware images: https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738