My Google Play Store Stopped working + google play Games and also facing syncing problem with gmail and calendar , (no issue with internet connection) even after full reset .
also i am not able to add any other google account.
Nexus 5 Android 5.1.1 + rooted + xposed+ default kernel
and today i did clean cyanogen 12 installation but after adding my account this problem arrive again after some time
Have you tried narrowing down the issue, maybe a fresh install (don't root or install Xposed), add your account, run it for a day or two, or at least longer than you know it takes for the problem to occur. Just to make sure it's not an Xposed issue. I've never had issues just with rooting, but it always helps to eliminate any other possibilities.
I've seen something similar to this, and I never really figured it out. I'm using stock image, just root, but my issue was several google sync would not work, like contacts, calendar, and a few others. I tried removing the account and adding it back, it worked like you state, a few hours maybe, then it would have sync errors again. I re-imaged fresh, and I believe when I initially configured the phone the first time, I added my account when it asked instead of skipping it, like I do occasionally. It's been going strong since, but I still don't know if that was a correct "fix"
cyanogen have a setting to remove root access so i did , but the problem still there. i am 80% sure that this is not a root problem .
so i removed my google account but now i cant add any of my google account with my phone (Error -As shown in last screenshot)
i did a fresh start before so again its specifically related to my that google account (as i think)
possible cause of this problem -
1- Latest Stagefright Patch update by google on my nexus 5 (Problem occurs sometime after update)
2- Freedom app , which is used to activate some of my app . i tried this app 2 or 3 days before .http://onhax.net/freedom-iap-apk/
i found one quick solution
i Removed host file from Etc folder in root directory and now problem gone
One question, do you use or previously used an Ad-block app?
yup is that app cause problem?
Just got a Nokia 3.1 Android One (Android 8.0.0)
There is only 1 problem :
Call Recorder ACR and Bluelight for eye care are killed / stopped by Android.
Battery settings are "not optimised" for these apps.
Is there a way to prevent Android to stop them?
Arie
Bolle1961 said:
Just got a Nokia 3.1 Android One (Android 8.0.0)
There is only 1 problem :
Call Recorder ACR and Bluelight for eye care are killed / stopped by Android.
Battery settings are "not optimised" for these apps.
Is there a way to prevent Android to stop them?
Arie
Click to expand...
Click to collapse
Maybe I found a solution :
Keeping your Android application running when the device wants to sleep at developer zebra dot com
At Battery Optimization / Doze Mode I found at poit 3 this
3. Using ADB during provisioning you can manually edit the whitelist, though obviously your device must first have developer options enabled:
Add your application to the whitelist as follows:
adb shell dumpsys deviceidle whitelist +com.yourcompany.yourapp
And remove your application from the whitelist with the following command:
adb shell dumpsys deviceidle whitelist -com.yourcompany.yourapp
Developer mode and USB debugging are activated on my phone, is this safe to try?
Hi,
I was having the same issue as well. I agree it is really annoying. For me, it was happening with Night Screen and Gadget Bridge.
However, since I got the 8.1 Oreo update (I got it on the 19th), I have not had Gadget Bridge get killed. I'm finally able to enjoy using my watch again
I no longer use Night Screen as 8.1 comes with one built in that is applied system wide.
I've only had the update for two days, so I can't say for certain if the problem is completely gone. However, it is a lot better than what I was experiencing on 8.0.
I don't know how long you will have to wait for the update, my friend who also has the same phone hasn't received it yet.
Last thursday I got the 8.1 upgrade and everything works fine, no apps get killed anymore.
Anyone else getting the feeling that the new Pie Update for Nokia 3.1 Plus is wonky?
I have an applock application that basically NEEDS to be active in the background. Somehow, the Pie Update got rid of any apps ability to stay active in the background. I contacted the customer service... And they told me to reset app cache, reset individual app data, factory reset AND boot up in SAFE MODE.
Now that I've done all of this, IDK what to do with the phone. The rest of the phone works great.
Actually, scratch that. After the factory reset, my ringtone kept getting reset to default Nokia ringtone even though I changed the ringtone. It defaults every boot up as well.
Please let me know what to do.
I know this is a 3.1 exclusive thread... But IDK why there's no 3.1 Plus thread. Please do help me in this.
I'm pretty much screwed.
I too am having that problem. Here is something that might help.
https://dontkillmyapp.com/nokia
I dont know how to run adb commands yet.
I haven't had any sleep data since July except for some incorrect nap readings for full night's sleep. The watch shows I have slept but the phone app doesn't show anything. I have the latest version and I don't want to do a factory reset. Any suggestions?
Same here. I tried with factory reset, reinstalling Health app, updating HMS, uninstalling HMS and installing Wear OS, uninstalling both, unlinking Google Fit, linking the watch to two other phones, erasing all cloud data associated to the account.
The watch itself shows sleep data. Recently it started syncing no data at all, except hearthbeats.
Sent it to Huawei support, they returned it as "cannot reproduce".
Same here. Huawei Health version 10.1.1610. Device Huawei Watch GT 2e version 1.0.3.20. Still having problem sync data at least once every week.
Most of the days they work, some day failed. Not so consistent and reliable communication between device & gsm.
Hi,
I've a sync issue with google keep on my Xiaomi MI9SE (Android 10 ; MIUI global 12.0.3 stable).Every google service works well (gmail, agenda, etc) except google keep (you can see the screen capture below). When I open it, none of my notes appear. There's no problem on my PC.
I've deleted/re-authentified to my google account.
I've done all the updates on Google Play.
I've deleted/reinstalled google keep and deleted all data for this app.
I've rebooted my phone several times.
My storage isn't full, I have about 20 Go left.
[edit] Sync of gkeep works on other phone
Does anyone has clues to solve this issue ?
Thanks
one precision, I have disabled the possibility to share my notes
mimiaoumiaou said:
Hi,
I've a sync issue with google keep on my Xiaomi MI9SE (Android 10 ; MIUI global 12.0.3 stable).Every google service works well (gmail, agenda, etc) except google keep (you can see the screen capture below). When I open it, none of my notes appear. There's no problem on my PC.
I've deleted/re-authentified to my google account.
I've done all the updates on Google Play.
I've deleted/reinstalled google keep and deleted all data for this app.
I've rebooted my phone several times.
My storage isn't full, I have about 20 Go left.
Does anyone has clues to solve this issue ?
Thanks
Click to expand...
Click to collapse
This is some suggestions I saw:
This is what fixed Keep for me, on Samsung Galaxy S9, maybe because I use Mid Power saving mode:
Settings -> Device Maintenance -> Battery -> Unmonitored Apps -> Add apps -> Keep -> Done
Click to expand...
Click to collapse
Mine was not synching because my phone was out of space. I ignored it for weeks! It worked fine once I cleared out some room.
Click to expand...
Click to collapse
thank you
I've turned it to unmonitored apps but it doesn't change anything even after rebooting the phone.
another precision, I assume there's a battery drain from Android System, which uses about half of whole consumption
I've finally found a solution : the version of the apk in the playstore wasn't the last version of gkeep. It was from 05/01/2021, and I learned that another version from late january had been realased. I downloaded this last version and installed it. It solved the issue. I don't know why my playstore doesn't propose this new version
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
73sydney said:
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
Click to expand...
Click to collapse
check lot of iPhone problems..
btw, Oneplus had problem with connection GW4 after upgrade from 12 to 12.1. only one solution was reset GW. now on 1+ A13 doesnt work Google Wallet/Payments with cloned apps enabled.. Samsung is better competetion..
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
HyperChick said:
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
Click to expand...
Click to collapse
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Try updating google play services to the latest beta (apkmirror). Solved my issue
shaharofir said:
Try updating google play services to the latest beta (apkmirror). Solved my issue
Click to expand...
Click to collapse
tried latest beta (22.45.15 (190400-488417729) beta (190400))
absolutely no difference
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Cheers, but just for reference, im quite involved in Magisk circles and hiding root (have modules to assist in this)...im usually helping others hide stuff or deal with root issues.....so i know what im doing
Also the same setup i use had no such issues in Android 12, its very much a Samsung making life harder for everyone, on purpose, because theyre basically acting like the new Apple and want to lock everything down. Ive decided to go back to Pixel, off to buy one soon, Samsung has gotten their last $ from me, they can go hang...
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
JazonX said:
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
Click to expand...
Click to collapse
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
73sydney said:
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
Click to expand...
Click to collapse
Thank you for this.
I will use this If I ever lose the R/W ability in my device.
For now I have R/W - so I wrote to the file directly.
Heres what i found out......
TLDNR version:
Dont backup and restore Samsung Wearables Apps - even if you previously were able to do this for eons, like i had. I have used Migrate to backup and restore apps and app data for eons (important to note i always left the app data (middle column in Migrate GUI) disabled for Samsung Wearables apps. Always let the Watch be detected as part of device setup on stock ROM OR install the Galaxy Wearable live from the Play Store (after clearing Google Play Services/Store sata and achieving Integrity check if you are rooting your device)
Longer version:
The other night i finally got time to flash back to A12, ran my normal procedure, rooted, USNF...clear data on GP/GS and then connected Watch...only it still wouldnt connect, even though the app restore was taken from a clearly working A12 (just before i flashed A13)
So i had to alter my procedure in leaving out the backed up Samsung wearables apps during restore, and then let the installed ROM detect the presence of the Watch 4 AFTER i have rooted, USNF...clear data on GP/GS and then connect Watch...
Looks a little like this:
* Flash ROM via ODIN (including my special AIO.zip to install TWRP, format data, decrypt data etc)
* Watch 4 WAS powered on and waiting to be detected when setup wizard looks for it towards end of setup - ignored/cancelled setup this time - going to do the root, USNF module and integrity check thing firsties
* Finish setup
* Reboot to TWRP recovery
* Root with Magisk (renamed to .zip) via TWRP
* Reboot
* Install Magisk App to complete install (you can just use the stub installer which will download the full app, but im used to doing it this way)
* Reboot
* Install USNF (Mod) and put device in airplane mode clear data on Google Play Store/Services to pass Integrity Check
* Reboot
* Take device off airplane mode....
* Open Google Play and confirm its certified (just needs to show version (Device Is Certified of course comes later - as along as it doesnt say Device Is Not Certified, all is well)
* Watch 4 automatically detected (Wearable Manager Installer - this is i think obviously a stub installer to detect and call the latest Galaxy Wearable from the Play Store) and Watch setup commences
* Watch setup completes
* Restore remaining apps via Migrate (leaving wearables unselected - will leave them unchecked on next backup)
NOTE: you must do (and ALWAYS have had to do) the Watch connection AFTER clearing data on GP/GS to get Integrity to pass. If you do that data clear after you connect the Watch it will sever the connection, as it tied to GS
Noter 2: Ultimately i decided id had enough of Samsung tomfudgery, and i bought a Pixel 6 Pro and departed for sanity back to Pixel Lyfe.....
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
gettinwicked said:
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
Click to expand...
Click to collapse
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
73sydney said:
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
Click to expand...
Click to collapse
Yeah, not rooted. I'll give the clearing play store and services data a whirl. I also have a conversation going with Samsung support on Twitter. Thanks for replying!
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Root has nothing to do with, the Galaxy Wearable app doesnt stop working if your knox has been tripped.
Ive had the last 3 Galaxy watches and all my phones have been rooted with custom roms, any issues ive had connecting/pairing were user error.