Hey there,
I have a relatively recent Android 8 install (Superman ROM on an S7 Edge), rooted, and various apps no longer sync, including Firefox, and DAVDroid, but probably also others.
There have been times when initiating a manual sync within Firefox would actually make it work again (including DAVDroid, which uses the Android sync framework, as well), but that doesn't work anymore. The few times it did, I'd actually see a toast "Auto-sync timers have started", which Taskwarrior emitted upon reception of a broadcast intent probably related to system boot (see here: https://github.com/Doctor-Andonuts/...rc/main/java/kvj/taskw/data/BootReceiver.java).
Rebooting doesn't fix things, and neither does wiping Dalvik & cache.
I am really at a loss here and thinking that something is not starting up the service or threads or whatever it is that controls the Android sync framework. Auto-sync is obviously enabled, and dis- and re-enabling doesn't fix the issue either. Firefox and DAVDroid are set up to sync, and everything else appears normal.
So what is missing for the sync framework to start? What could be preventing it from starting, or killing it?
Thanks for any help!
Related
Just got a new tablet. Looks like it's a clone of something of these:
AMLogic A9
iRobot a907
Ramos W10
MaPan MX19S
Hyston 9587
Anyways, it didnt come with market, so I rooted and I installed gapps. It's running android 2.3.4. Everything seems to work except that Google Services Framework crashes all the time. Pretty much background sync doesnt always happen, because Services Framework crashes. It happens all the time! I tried like 4 versions of framework, the one that came with the gapps, honeycomb version (honeygapps from xda), version 2.1, version 2.3.7 and it just doesnt fix it. I cleared data a million times, online says that it might be contacts db causing it to fail.. I removed anything contacts related (the sync adapter and everything.. so there are no contacts anymore on my tablet)... but nothing seems to work.. it just continues to FC, I even disabled background data and auto-sync, it still force closes!!!!! The only method to stop it is to disconnect wifi. I don't know what to do. Any suggestions? It's annoying always popping up every few minutes / seconds.
Thanks.
Hello,
yesterday, I got my Galaxy S3 (custom build cm10.1) from my pocket to notice it said "safe mode" on the bottom. It might be that I accidentally pressed buttons to get into safe mode; but thats not the problem here.
I noticed that all my custom accounts were now missing (Caldav, Carddav, Xing, and some more). Only the google accounts remain. As all my contacts and calendar entries are on the caldav/carddav server, they went missing, too (of course, they will come back when re-adding the account). I didn't know about the existence of safe mode, I thought like "what the...", and restarted the phone, and it came up without safe mode now. But - the accounts are still missing, and taking a closer look I noticed that some customized or account-related widgets (K9 for example) are also missing now. At least most of the app data seems to still be present; even the Xing app works as expected, even though the related account is missing from the settings. It seems all the account related data is still there.
I've got three questions now:
1) Is it normal, that the described accounts/widgets get permanently lost when entering safe mode?
2) Is there a way to restore these without manually entering/configuring them again?
3) What _other_ data/settings I perhaps didn't notice until now can go missing when entering safe mode?
Thanks in advance
Nico
McNetic said:
I noticed that all my custom accounts were now missing (Caldav, Carddav, Xing, and some more). Only the google accounts remain.
Click to expand...
Click to collapse
Same with Nexus 4 (Stock firmware 4.3): Inadvertently (don't ask how ) but manually started safe mode. The result after a normal reboot was the complete loss of all custom accounts and related widgets.
lonesomecoder said:
Same with Nexus 4 (Stock firmware 4.3): Inadvertently (don't ask how ) but manually started safe mode. The result after a normal reboot was the complete loss of all custom accounts and related widgets.
Click to expand...
Click to collapse
Same with Nexus 5. All accounts and widgets lost. All (non-Google) contacts lost. Calendar lost.
There should be a warning on the on-line instructions for using safe-mode unless this is a bug in Android that needs to be fixed.
This is NOT a bug. This is how Safe Mode is designed and works very similar to Safe Mode on the computer. It disables all 3rd party apps, widgets, data, etc so you can make sure if your phone is having trouble that it's not from something you have done or installed. You should just be able to reboot and Safe Mode be disabled. If it is not, then make sure your Volume keys aren't stuck.
es0tericcha0s said:
You should just be able to reboot and Safe Mode be disabled.
Click to expand...
Click to collapse
That right. However, the problem is not safe mode or leaving safe mode, but the problem is, that afterwards, when booting normally, all third party (non-google) accounts and some widgets (and maybe other data, but that I don't know) are lost and seem not to be recoverable. (see post #1)
Ohh sorry, thought you were still stuck in Safe Mode and wondering why the stuff wasn't there. Sorry. But yea...definitely not normal for it to lose all your stuff after you boot back to normal mode. As far as restoring it - only if you had a nandroid of the same rom or everything backed up with like Titanium Backup.
This happened to me last night.
I left my Nexus 5 on my bedside table. Usually I put it into aeroplane mode before going to sleep, but this time I didn't. When I woke up this morning, I picked the phone up and all my widgets were gone from my home screens apart from Google Newsstand and the Google search bar and all of my accounts were gone apart from my main Google account. My wallpaper had also reverted to the stock Nexus 5 wallpaper.
I rebooted the phone, but it booted up in Safe Mode for some reason - and it was still messed up - so I turned it off and on again and it booted into normal mode, but it was STILL messed up and all of my widgets/accounts were gone apart from the Google ones.
I ended up doing a factory reset. I have no idea how this happened as the phone was on a bedside table all night, untouched. The only thing I didn't do that I would normally do at night is put it into aeroplane mode.
Well it's 2020, and this fault still occurs! I've a Samsung Note 3 (Android 5.0) that just disconnected and deleted my CardDAV sync connector/account. I've lost all my unsync'd contacts (There were quite a number, as it's been a while since I sync'd -- so it's quite the loss). I've tried various contact recovery tools, to no avail. Here's a description from from DAVx⁵ tech support, as to what seemingly happened .... (DAVx⁵ is a CardDAV sync adapter, but mine was similiar: CardDAV-Sync Free):
-------------------------------------
"At some occasions (especially when booting), Android looks for orphaned accounts which are not associated to a sync adapter. Unfortunately, this check is sometimes run before DAVx⁵ is available.
So, if this check doesn't find DAVx⁵ for whatever reason, it thinks that all DAVx⁵ accounts are orphaned and deletes them, including all your local contacts, calendars and tasks (together with all unsynced changes). This problem is known for at least these cases:
- when DAVx⁵ has been moved to the external storage or SD card (although this is forbidden by the app manifest),
- when the device is booted into safe mode, and...
because of a Google Play bug which may affect users who have got DAVx⁵ via Google Play on
many Android 4.4.x devices, regardless of the manufacturer, for instance LG G3 (LG-D855) with Android 4.4.2, and some other devices.
How to fix it:
- DAVx⁵ must not be moved to external storage (SD card or USB storage).
- Upgrade your device to the latest available Android version (if your firmware is really old, you may consider a custom ROM).
- If you boot into safe mode, be prepared that all local DAVx⁵ data (including unsynced changes) will be lost. At the next synchronization, all data will be downloaded from the server again.
- You may consider to install DAVx⁵ from another source (e.g. F-Droid)." --https://www.davx5.com/faq/accounts-gone-after-reboot-or-update
---------------------------------------------
I've spent many, many hours searching the net and trying to recover what I lost, to no avail. It seems that most people go for the "set it up again and re-sync to the server"... which restores everything up until the last sync. So they don't loose too much... so the occasional problem doesn't get a lot of attention, nor does it garner enough outrage to get it fixed, it seems. I have no great confidence that this won't happen again, so I'm taking the precaution of:
- Upgrading to a phone with Android 8, and not using Google Play to install the sync adapter app
- or -
- Disabling safe mode for Android v7 or lower (https://www.hexnode.com/mobile-devi...fe-mode-on-android-devices-using-hexnode-mdm/)
My Google Calendar on my phone has been randomly crashing pretty much since I got my Note 2 last January. I've been searching for answers, most of which seem to suggest either A: the coders for Android are idiots who can't manage to make things work on their end, or B: Samsung's coders are the idiots. I've tried factory resetting, installing both Google and S Planner, uninstalling S Planner, uninstalling Google, wiping the database, completely deleting my calender and starting fresh, separating events into their own calendars, setting the timezones for all events instead of letting it happen automatically, force stopping the update, clearing the cache, clearing the data....nothing, NOTHING has fixed it.
Then I saw a suggestion that UCCW was crashing them: I uninstalled it, and thought I was in the clear. Nope: it crashed today. From my logcat, I can see:
E:/CursorWindow(10169): Could not allocate CursorWindow '/data/user/0/com.android.providers.calendar/databases/calendar.db' of size 2097152 due to error -12.
E:JavaBinder(10169): at com.android.providers.calendar.CalendarCache.readDataLocked(CalendarCache.Java:228)
E:JavaBinder(10169): at com.android.providers.calendar.CalendarCache.readData(CalendarCache.Java:202)
E:JavaBinder(10169): at com.android.providers.calendar.CalendarCache.readTimeZoneInstances(CalendarCache.Java:114)
E:JavaBinder(10169): at com.android.providers.calendar.CalendarProvider2.query(CalendarProvider2.Java:986)
D/ALK (14643): ALK *** Utils.readCalendar(): caught exception: java.NullPointerException
I'm currently on Beans 22. Has anyone else seen anything like this, or has a suggestion?
I'm on Android 8 (SuperMan-ROM), and I used TitantiumBackup to freeze all apps I don't need/use, especially all the Google and Samsung tracking stuff. This has worked well for me for years.
But then I ran into a problem wherein the sync framework wouldn't work anymore. I may have finally resolved this by unfreezing all apps, rebooting, wiping Dalvik and caches, and then refreezing the apps. Now sync works again, even across reboots. Previous attempts at wiping Dalvik&caches to fix this (without unfreezing) did not yield the desired result.
In order for me to understand what's going on, I need to understand what the sync framework is, and what provides it. I mean, I am certainly not freezing what seems like core Android services, but maybe the sync framework is included in some other service that just doesn't have a name indicating that?
Do you have an idea which app/service actually provides the functionality behind the Android sync service?
Suddenly my Pixel 6 running Android 13 can no long use Google Voice. I have tried 2 different cars, 3 different USB cords, clearing cache and data, uninstalling and reinstalling the Android Auto App. All with no luck. About the only thing left I can think to do is factory reset. I hate to go to that extreme, but I drive a lot and need a functioning Android Auto.
Android Auto lets me answer calls. (It may actually be the car that is doing that). Any attempt to read incoming messages, ask directions, text a contact, ask a question, or place a call come back with "Oops, something has gone wrong, try again later". Once unplugged from the vehicle, everything works fine.
Do you have Ad Guard or some sort of adblocker installed?
I had the same problem and had to disable it for android auto, assistent, google apps and all other google apps I could find.
Problem solved
nrdl said:
Do you have Ad Guard or some sort of adblocker installed?
I had the same problem and had to disable it for android auto, assistent, google apps and all other google apps I could find.
Problem solved
Click to expand...
Click to collapse
No ad blocker installed.
Another odd thing is this: On the Android Auto screen, You Tube Music is now at the top. I do not use it. I use Pandora instead. This is really strange.
You can disable YouTube Music on your mobile, it won't show up or in Android Auto select what should be on the screen.
As for your initial problem, this is not really related to the Pixel 6, the problem is related to the Google Assistant and the Google App.
Cheers
Yes, I suspected as much.
You should check your internet connection is working fine, update the Google Voice and Android Auto app, also make sure that DND is not enabled.
maggiem2481 said:
You should check your internet connection is working fine, update the Google Voice and Android Auto app, also make sure that DND is not enabled.
Click to expand...
Click to collapse
Done.
No difference.
draexo said:
Suddenly my Pixel 6 running Android 13 can no long use Google Voice. I have tried 2 different cars, 3 different USB cords, clearing cache and data, uninstalling and reinstalling the Android Auto App. All with no luck. About the only thing left I can think to do is factory reset. I hate to go to that extreme, but I drive a lot and need a functioning Android Auto.
Android Auto lets me answer calls. (It may actually be the car that is doing that). Any attempt to read incoming messages, ask directions, text a contact, ask a question, or place a call come back with "Oops, something has gone wrong, try again later". Once unplugged from the vehicle, everything works fine.
Click to expand...
Click to collapse
Perhaps using the beta versions of Google Play services, Google app and Android auto fixes the issue you're encountering. And make sure that all permissions are enabled aswell.
Ps : the beta versions can be downloaded from apkmirror.
Ended up having to factory reset the phone to fix this.