So I updated my Google Play services to 8.1 but I had package disabler (which is now turned off) running on my phone which problem is the culprit. But after updating my phone started heating up, freezing constantly and giving all kinds of google play update errors.
I thought, great I will just uninstall the update and everything will be fixed. Well uninstall and force stop are both greyed out. So I went to the device admin and turned off Android Device Manager but, it just turns right back on and greys out if I restart my phone it goes back to normal but then when I try to disable it does the same thing. I have tried with Android Device Manager both installed and uninstalled same issues.
So I can't disable Android Device Manager, I can't uninstall Google Play Services update... anyone have any ideas short of factory reset?
Thanks in advance...
Disabled Google Play Store, and Google Services Framework and was able to kill it through Package Disabler... Thank goodness
I did the same thing. Never had an issue sideloading those kids of updates in the past but I didn't have package disabler. Had to do a factory reset and spend a couple hours getting everything back the way it was.
matt.b.powell said:
So I updated my Google Play services to 8.1 but I had package disabler (which is now turned off) running on my phone which problem is the culprit. But after updating my phone started heating up, freezing constantly and giving all kinds of google play update errors.
I thought, great I will just uninstall the update and everything will be fixed. Well uninstall and force stop are both greyed out. So I went to the device admin and turned off Android Device Manager but, it just turns right back on and greys out if I restart my phone it goes back to normal but then when I try to disable it does the same thing. I have tried with Android Device Manager both installed and uninstalled same issues.
So I can't disable Android Device Manager, I can't uninstall Google Play Services update... anyone have any ideas short of factory reset?
Thanks in advance...
Click to expand...
Click to collapse
Play services versions are pretty specific. Installing the wrong version will result in lots of issues with Google Apps. Currently the note 5 on 5.1 uses play services ending in 440. With marshmallow that prefix changes from 4 to 2 for Lollipop so Lollipop will be version 240 and when marshmallow is released it will use 440. You will need version play services 8.1 version 240 which is not out yet.
Sent from my SM-N920T using XDA Free mobile app
jmerlos said:
Play services versions are pretty specific. Installing the wrong version will result in lots of issues with Google Apps. Currently the note 5 on 5.1 uses play services ending in 440. With marshmallow that prefix changes from 4 to 2 for Lollipop so Lollipop will be version 240 and when marshmallow is released it will use 440. You will need version play services 8.1 version 240 which is not out yet.
Sent from my SM-N920T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the Info on that. There's such a steep learning curve with androis
Sup fellas just posting this from my phone
Basically I rooted it with CFAUTO root I found on a site that seemed trustworthy due to its credibility found on various sites.
Root works perfectly along with Xposed for awhile but eventually a week later every single app will start force closing, or immediately fail to launch on touch. From instagram to KiK to play store itself.
Rebooting is not a good solution as it resolves into a boot loop.
This has been happening consistently for a few weeks. The only solution to get my phone back up and running is to do a factory reset (which in turn means setting everything up again to my preferences. )
This pretty much led me to leave the phone as it comes plus a few common apps and just rely on my iPad more.
Does anyone have a solution? I followed the tutorial down to the T. Video and guide. I'm considering switching to stock but want to see if anyone else had this issue or was able to fix it
I would say to use this guide.
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Havent tried CFAUTO root, and I dont think its recommended.
I had a similar issue with apps force closing, though I didn't use cfauto root.
The issues I had, after finding out from much trial and error, was that after I rooted my apps would update before Google play services. This would cause problems because the updated apps needed the updated play services to run.
Revert back to stock, then make sure that Google play services is up to date before updating any other app. After play services are up to date, make sure your play store is up to date. Then go ahead and update all of your apps. Next reroot your phone.
Like I said before I didn't use cfauto root, but I hope this helps.
I had Samsung Gear / S Plugin update on Google Play today (10/10) for my S2 and afterwards, all I get are FC's and the S Plugin constantly crashing on my device, making the watch completely unusable.
I had to force stop and remove the software from my phone and factory reset the watch. I'm not the only one who is dealing with this issue either.
https://us.community.samsung.com/t5/Wearable-Tech/bd-p/wearabletech
So if you're constantly getting crashes today, at least you know why. I'm not sure if there is a workaround for this or not. If there is, please let me know. Everything was working great until Google Play updated the software today.
Thanks!
Had the same issue, but I did have xposed on my rooted phone. Without xposed the update seems to be working fine...
Sent from my HTC6545LVW using Tapatalk
I switched from SuperSU to Magisk last week and have "hidden" all the Samsung Gear apps from root. Now, I can use Samsung Pay (and Android Pay) on my phone. Before switching to Magisk, some of the Gear apps were listed as incompatible. Everything works great now including all the latest Gear Apps & Plugins.
High phone cpu usage
Hello to everyone. I'm dealing problems after last update of gear app software. Every time Gear S2 tries to exchange data (reconnection, data to Shealth, watch apps install) with Galaxy S5 (android 5.0 and android 6.0.1) it uses 99% of phone cpu for 50-60sec, , sucking both batteries (phone and watch). Tried on android 5.0, android 6.0.1, rooted or not. Is there any ideas what is wrong?
Hi there guys. i have a problem which i noticed today. i will try to be very specific on what happened etc, so that i may get the best help possible.
I have a xiaomi mi note 10 pro, with miui global rom 11.0.16 running android 9.
i have it rooted (first phone i ever rooted).
i had android auto installed and also android auto enabler (what a great app, got it from xda). alla was working fine more the few months i had my phone.
yesterday i noticed that android auto wouldnt start.
i was getting a message "android auto requires one or more google play services that are not currently available".
This must have happened in the last 3-4 days, because iremember having opened android auto few days ago, and all worked fine.
well, first i tried downgrading android auto, uninstalling, reinstalling it, getting updates from google play and aptoide for google play etc, removing them, deleting cache, deleting settings restarting and all that.
no matter what,i got the same error. one or more google play services is not currently available.
i was really desperate. today, i noticed an app named google services.
i opened it and it says on top "gms installer"
under it, it has 4 names. (google framework, google service, play store, google maps). all have ticks, apart from google framework.
google framework states it is corrupt. i press the button there is to fix it, it starts fixing and it stucks at 94%. doesnt go any further. upon trying to restart, it gets stuck at 0%.
after clearing cache data and restarting phone, it gets again at 94%. i am thinking thatthis framework is the problem. and i cannot do anything to fix this.
searching on the internet, many had this problem with android auto. and many of them had the problem these last few days. any ideas what i could do? at least to install the framework again?
ps. i never uninstalled the framework. or google services, as i have read it is a very bad thing to do.
thank you
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.