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 guys
I have an old pronlem -- all the gapps I have tried(slim, pico, delta) are eating too much at all the roms ive used(purity, sultan, orion os, aosparadox, exodus)
Even amplify does not help.
What can you reccomend?
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Joshwin Aranha said:
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Click to expand...
Click to collapse
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
saurabh40629 said:
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
Click to expand...
Click to collapse
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Joshwin Aranha said:
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Click to expand...
Click to collapse
Though you are right about first half (can't say much about later part, as I don't understand why it should make google services go crazy )
This problem traces back to Kitkat and probably jell bean but only thing which I do not understand is why only in mobile data ?? I don't see any of them popping up in wifi .
Just when I thought I could ignore it, it started non stop feast on mobile data. I had to stop background data for this. Damn you google.
try A-gapps, it allows battery optimization for google play services (open-gapps etc don't allow this)
it helped me to have less battery drain by google play services
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
Yeah... Mine are pretty obese too
After spending some time developing applications, I made an application that makes use of O's notification channels. I used Firebase's job dispatcher to schedule the notification firing service. The first time I deploy the application on my smartphone (I believe I had a mistake there), I suddenly saw that Google Play Services crashes, the app crashed and the whole system rebooted shortly.
When it booted up again, weird things started happening like launcher crashing and restarting a couple of times, various applications crashing for no reason (I believe they're related to Google Play Services, or Firebase? dunno) so I thought that my (only thing) google-play-services related code concerning the service scheduling had to do with it, I deployed a new build that just cancels the service with the same service tag used.
Everything seemed fine, for the crashing mania stopped and everything was less frustrating, and finally I could open Settings > Apps again without crashing the Settings app. But lately it started happening again with google play services, I got mad and uninstalled the application causing the problem, but now any application that uses google play services crashes on start and are unusable at all. My phone is semi-usable and this is disgusting right now.
I'd be glad if anyone could help me fix this problem either with Firebase job dispatcher, Google Play Services or the whole system/phone with the least losses as possible.
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!
So there's an app I've been using for many years: Simple Checkin for Foursquare
It's essentially a lightweight app/client for the once-popular Foursquare location checkin service.
The app has been abandoned by it's developer and hasn't been updated since 2016. I have searched but have not found another app to replace it (that works) so I still use it.
My daily driver for the past few years has been an LG V35 that's stuck on Android 8. It's actually been a great phone for me which is why I've kept it so long but is really starting to show it's age, some more modern apps are getting noticeably laggy.
I bought a new phone that came with Android 10 and it's good other than this particular app doesn't work at al. When I install (or launch it after clearing data) I'm given a warning that the app is designed for an older version of android and may not work properly before it prompts me to log into the Foursquare service, once that part is completed the app just crashes. Any time I try to launch the app after that it crashes immediately (never even loads the UI).
I've tried this on 2 different Android 10 phones and it's the exact same result. The app works fine on both Android 8 and Android 9.
I'm wondering if there's some kind of workaround for this problem or if I'm really stuck here. I have reached out to the developer of the app and he told me that he's not working on this app anymore and has no plans to update it.
Thanks in advance
Which phone?
The ancient freeware WPS office runs on my N10+'s Android 9 and 10. 10 hasn't caused many issues except it gutted Karma Firewall's valuable logging feature. On Samsung's at least scoped storage isn't fully active and Samsung has greatly modified Q to maintain functionality and the UI.
One reason I'll never load Android 11
Overlay apps generally crash on Q...
Try checking all settings on the app.
Check accessibility permissions, does it need Administrator permissions?
Clear system cache and app data.
Try disabling the internet and see if it loads.
If so then find which app is diming it out and firewall block it.
Try temporarily disabling Google play Services.
Playstore may be another trouble maker.
Try reinstalling it with internet disconnected.
See what apks popup (running services/app cache) when you try to load it as that may give you a clue to the perp apk.
Play with it... may be a dead end or not.
blackhawk said:
Which phone?
The ancient freeware WPS office runs on my N10+'s Android 9 and 10. 10 hasn't caused many issues except it gutted Karma Firewall's valuable logging feature. On Samsung's at least scoped storage isn't fully active and Samsung has greatly modified Q to maintain functionality and the UI.
One reason I'll never load Android 11
Overlay apps generally crash on Q...
Try checking all settings on the app.
Check accessibility permissions, does it need Administrator permissions?
Clear system cache and app data.
Try disabling the internet and see if it loads.
If so then find which app is diming it out and firewall block it.
Try temporarily disabling Google play Services.
Playstore may be another trouble maker.
Try reinstalling it with internet disconnected.
See what apks popup (running services/app cache) when you try to load it as that may give you a clue to the perp apk.
Play with it... may be a dead end or not.
Click to expand...
Click to collapse
Thanks, I'll try that.
FWIW the two Android 10 phones I've tried are a Motorola One 5G Ace and a Unihertz Titan
Try using Apk Export to copy it. This is app I use, freeware.