Related
I've tried everything I can think of to resolve this, but I need some suggestions.
So - my husband finally got a smartphone, after getting by with a keyboard phone for years. I talked to him about different phones - iPhones even - and after looking at several, he took my advice and got a Droid Maxx. Of course I helped him set it up, etc. Everything went well for a day or two, but then he started getting all sorts of errors - Google sync problems, Google account sign-in problems, "Unfortunately Google play services has stopped" etc. I was able to solve most of the problems by uninstalling updates to Google Play, and a few other things. He was still having some issues, though. The phone occasionally shut itself off. So, I decided to do a factory reset.
Since then, everything is working much better. The phone hasn't shut down at all, etc. However, in the last day or two, he will get an error notification that's something like "Trouble signing in to Google Account". He has to tap the notification and enter his Google password. Then everything seems fine until it happens again sometime later. Now it's happening frequently
He has almost no apps installed. The two or three he has installed are the same ones that I have used forever on my android devices, including on my Droid Maxx and Moto X - so on the same or similar devices. I have checked every setting I can think of. He doesn't have 2-step authorization on his Google account and he never has problems with that account on his desktop, laptop, etc.
Any ideas what could be happening? He does drive through an area with no cell service every day, so that could have something to do with it, but I drive through the same no-service area, and I have never, ever had to sign in to my Google account after initial setup. Sometimes this issue crops up when he has perfectly good service.
jkmasi said:
He does drive through an area with no cell service every day, so that could have something to do with it, but I drive through the same no-service area, and I have never, ever had to sign in to my Google account after initial setup. Sometimes this issue crops up when he has perfectly good service.
Click to expand...
Click to collapse
i think that's the problem, i had issues the first time i passed by a no service area and the problem showed up ''we have trouble authenticating this account, tap here to solve'' and thats all. it solved with the tap in the notification, and never appeared again, i suspect your rom data its corrupted and i recommend reinstalling the phones firmware 4.2 or 4.4 whatever version is. that should solve the problems.
Jaocagomez;50875823 your rom data its corrupted and i recommend reinstalling the phones firmware 4.2 or 4.4 whatever version is. that should solve the problems.[/QUOTE said:
Thanks for your reply! Can you please explain what "your rom data its corrupted" means?
Also, how do I reinstall the firmware? This phone is not rooted and was updated to 4.4 KitKat OTA.
I'm hoping that it was just the magnet on his pouch case interfering with the radios. He realized that he's always noticed this problem after the phone has been in the case. This afternoon I asked him not to put it in the case as an experiment.
Click to expand...
Click to collapse
After updating to Android Pie, I can no longer use Ok Google or manually hit the mic for the google app. I can type and use it though. Just the microphone option is broken for some weird reason.
I've tried everything. Factory reset, fastboot formats, clear app cache/data, ect... If you know what's wrong, let me know. Never had this before with any of my phones. Almost seems like an issue on Google's side?
woundman said:
After updating to Android Pie, I can no longer use Ok Google or manually hit the mic for the google app. I can type and use it though. Just the microphone option is broken for some weird reason.
I've tried everything. Factory reset, fastboot formats, clear app cache/data, ect... If you know what's wrong, let me know. Never had this before with any of my phones. Almost seems like an issue on Google's side?
Click to expand...
Click to collapse
I had this issue in oreo when I messed up with system apps.
It got fixed with complete fresh install of Pie.
There were two scenarios;
Upgraded from oreo to pie - didn't worked
I freshly installed HavocOS, I was surprised that OK google still won't work - have to tap mic button everytime.
Completely wiped phone, used MSMtool.
Restored to 5.1.5
Wiped again with TWRP
Installed Android Pie again.
Then it started working.
Conclusion- it seemed google side problem as it said I had already saved voice model on other phone ( oreo) and I could not retrain.
And there were no fixes on XDA OR reddit.
woundman said:
After updating to Android Pie, I can no longer use Ok Google or manually hit the mic for the google app. I can type and use it though. Just the microphone option is broken for some weird reason.
I've tried everything. Factory reset, fastboot formats, clear app cache/data, ect... If you know what's wrong, let me know. Never had this before with any of my phones. Almost seems like an issue on Google's side?
Click to expand...
Click to collapse
Just contact Google Support.
drmjp93 said:
I had this issue in oreo when I messed up with system apps.
It got fixed with complete fresh install of Pie.
There were two scenarios;
Upgraded from oreo to pie - didn't worked
I freshly installed HavocOS, I was surprised that OK google still won't work - have to tap mic button everytime.
Completely wiped phone, used MSMtool.
Restored to 5.1.5
Wiped again with TWRP
Installed Android Pie again.
Then it started working.
Conclusion- it seemed google side problem as it said I had already saved voice model on other phone ( oreo) and I could not retrain.
And there were no fixes on XDA OR reddit.
Click to expand...
Click to collapse
I'll give MSMTool a shot. I followed this guide to correct the issue, but still not working. I'll update thread after I've updated to Android Pie from Oreo. Hopefully it works. Everything is working fine, google is just broken for some reason. I wonder what happened exactly.
woundman said:
I'll give MSMTool a shot. I followed this guide to correct the issue, but still not working. I'll update thread after I've updated to Android Pie from Oreo. Hopefully it works. Everything is working fine, google is just broken for some reason. I wonder what happened exactly.
Click to expand...
Click to collapse
I think you need to do fresh install of Pie.
drmjp93 said:
I think you need to do fresh install of Pie.
Click to expand...
Click to collapse
I've done a fresh install multiple times. Tried flashing thru TWRP as well. Only things I haven't tried are ADB sideloads and MSMTool. I'm in the process right now. It's working right now, we'll see if Android Pie works too.
MSMTool fixed it. Guess flashing thru MSMTool is better than the .bat files on the guide I was following. Thanks for the help @drmjp93.
Edit: Not fixed. Soon as the Google app updates, it breaks.
woundman said:
MSMTool fixed it. Guess flashing thru MSMTool is better than the .bat files on the guide I was following. Thanks for the help @drmjp93.
Click to expand...
Click to collapse
I am glad to hear that.
I know the feeling, I was united to Ok Google after 4 months.
??
drmjp93 said:
I am glad to hear that.
I know the feeling, I was united to Ok Google after 4 months.
Click to expand...
Click to collapse
Weird... Okay, so it seems there is something wrong with the Google App still. Everything was working fine, but soon as the Google app updated, it no longer works. Am I the only one having this issue? I am so confused.
Again, I've done everything! Factory resets, MSMTool, cleared app data...
Edit: Turns out my Google account is breaking it for some reason... No clue why. Soon as I remove my google account, google detects my voice. So weird... Now to figure out how to fix it.
woundman said:
Weird... Okay, so it seems there is something wrong with the Google App still. Everything was working fine, but soon as the Google app updated, it no longer works. Am I the only one having this issue? I am so confused.
Click to expand...
Click to collapse
At moment yes.
I updated my app too.
It's still working.
What does your voice train model page looks like?
Can u retrain?
drmjp93 said:
At moment yes.
I updated my app too.
It's still working.
What does your voice train model page looks like?
Can u retrain?
Click to expand...
Click to collapse
Turns out my Google account is breaking it. No clue why. Soon as I remove my google account, google detects my voice.
Not sure how to fix the issue. Do I contact Google?
woundman said:
Not sure how to fix the issue. Do I contact Google?
Click to expand...
Click to collapse
Yes may be its related to accounts, as during voice training it said I cannot train new voice as my account has already one saved.
I contacted them. It was an automated reply or a third person - an volunteer talks with us.
But if u do, do ask them to clear your trained voice saved to your account.
I don't know but I did every possible thing to get it working back.
Just ask them in particular to delete your all Voice related settings and activity.
drmjp93 said:
Yes may be its related to accounts, as during voice training it said I cannot train new voice as my account has already one saved.
I contacted them. It was an automated reply or a third person - an volunteer talks with us.
But if u do, do ask them to clear your trained voice saved to your account.
I don't know but I did every possible thing to get it working back.
Just ask them in particular to delete your all Voice related settings and activity.
Click to expand...
Click to collapse
Spoke with google support, they tried pretty much everything I've tried. They told me to report it to the developer's. Am I really the only one having this issue? I find it hard to believe I'm the only one having this issue on Android Pie now. Is your Google app widget working when you manually search?
Yes bro it works.
And regarding you are only the one is incorrect.
There are random ppl affected.
Including me but it was magically solved.
security updates:
https://source.android.com/security/bulletin/2019-07-01
fixes:
https://source.android.com/security/bulletin/pixel/2019-07-01
References Category Improvements Devices
A-130340628 A-130625396 Hotword Improves "OK Google" and music detection Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL
A-131176531 Bootloader Fixes an issue for some devices getting stuck during boot Pixel 3, Pixel 3 XL
A-122000615 A-133150859 Bootloader Fixes an issue for some devices getting stuck in EDL mode with a blank screen Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL
A-131312444 UI Improves Unicode Japanese language support Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL
A-133197843 Performance Improves Titan M module Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL
Still no sign of those performance improvements they supposedly found in July?
I notice a difference. I see the performance to Titan M chip in the changelog. So that could be it?
flash-all (minus -w) worked fine. Magisk 19.3 is working fine, and twrp-3.3.1-1-crosshatch installs (using ramdisk install method) and decrypts fine. Edge Sense Plus doesn't crash the system but automatically disables on install and after re-enabling and rebooting it comes back up unchecked. Now, I get to wait xxx days until Google Play shows as certified and shows installed apps/updates since I had to clear data/cache to get certification back and everything gets lost for days when previously using Edge Sense and clearing data/cache (at least with ElementalX which is what I am running). Might be time to lose Edge until it get figured out a little bit clearer on this device/kernel (certification has been lost every month for quite a while now). I had to clear Google Play cache/data on my wife's P3, and certification came back immediately along with installed apps and updates. No Edge Sense on her phone.
sliding_billy said:
flash-all (minus -w) worked fine. Magisk 19.3 is working fine, and twrp-3.3.1-1-crosshatch installs (using ramdisk install method) and decrypts fine. Edge Sense Plus doesn't crash the system but automatically disables on install and after re-enabling and rebooting it comes back up unchecked. Now, I get to wait xxx days until Google Play shows as certified and shows installed apps/updates since I had to clear data/cache to get certification back and everything gets lost for days when previously using Edge Sense and clearing data/cache (at least with ElementalX which is what I am running). Might be time to lose Edge until it get figured out a little bit clearer on this device/kernel (certification has been lost every month for quite a while now). I had to clear Google Play cache/data on my wife's P3, and certification came back immediately along with installed apps and updates. No Edge Sense on her phone.
Click to expand...
Click to collapse
what am i doing wrong?
Clean install of factory image
fastboot boot twrp image
Install the twp zip
Flash magisk 19.2
Phone doesn't like to boot up
nevermind . 19.3 fixed it
masri1987 said:
what am i doing wrong?
Clean install of factory image
fastboot boot twrp image
Install the twp zip
Flash magisk 19.2
Phone doesn't like to boot up
Click to expand...
Click to collapse
I see a few possibilities. You did clean install where I did 'no -w.' I do not see a version of TWRP. I used the twrp-3.3.1-1-crosshatch test build posted a bunch of pages back. I haven't used the TWRP .zip installer in months. So much easier to use the ramdisk method under advanced (make sure to have a copy of the .img file on your computer and run that method after fastboot booting). I installed directly to 19.3 Magisk instead of 19.2 +update.
For starters though, did you install TWRP after Magisk? If so, you'd need to install Magisk again to patch boot again.
---------- Post added at 03:41 PM ---------- Previous post was at 03:29 PM ----------
sliding_billy said:
flash-all (minus -w) worked fine. Magisk 19.3 is working fine, and twrp-3.3.1-1-crosshatch installs (using ramdisk install method) and decrypts fine. Edge Sense Plus doesn't crash the system but automatically disables on install and after re-enabling and rebooting it comes back up unchecked. Now, I get to wait xxx days until Google Play shows as certified and shows installed apps/updates since I had to clear data/cache to get certification back and everything gets lost for days when previously using Edge Sense and clearing data/cache (at least with ElementalX which is what I am running). Might be time to lose Edge until it get figured out a little bit clearer on this device/kernel (certification has been lost every month for quite a while now). I had to clear Google Play cache/data on my wife's P3, and certification came back immediately along with installed apps and updates. No Edge Sense on her phone.
Click to expand...
Click to collapse
j to the 4n just reminded me that he added the bootloop protection to Edge Sense if the security version is newer than supported, but that doesn't change the need to clear cache and data in Play Store (to get certified) and losing a ton of time if Edge Sense was installed. Not his fault, but still a PITA.
So, no fix for the muffled sound in calls?
So I updated to the July update and performance is definitely improved from before. I can use the camera and other apps at the same time as Pokemon Go without Pokemon Go reloading. I couldn't do this before.
BoboBrazil said:
So I updated to the July update and performance is definitely improved from before. I can use the camera and other apps at the same time as Pokemon Go without Pokemon Go reloading. I couldn't do this before.
Click to expand...
Click to collapse
Seems too early to confirm the ota helps with performance as performance for me is always better after a reboot for a while. If it stays smooth like it is for me nearly two days after updating then I would have more confidence the performance improvements are helping.
Hi
Can someone can post the full procedure please ?
I have downloaded the whole factory image
xmen06 said:
Hi
Can someone can post the full procedure please ?
I have downloaded the whole factory image
Click to expand...
Click to collapse
Here ya go:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
Ok thanks
nomisunrider said:
security updates:
https://source.android.com/security/bulletin/2019-07-01
Still no voice activated shutter for the camera. This is extremely useful, Google. Samsung and Huawei have it.
VERY disappointed to lose it with my recent switch to Pixel from Samsung.
Click to expand...
Click to collapse
Do you guys think that this security update has a bit of drain on the battery guys?
Goku80 said:
Do you guys think that this security update has a bit of drain on the battery guys?
Click to expand...
Click to collapse
Yes, definitely.
I've seen that Whatsapp and Spotify doesn't go to sleep. Whatsapp was at last more than eleven hours online in Background.
Hoping that this is an issue of this update here and they can fix it soon.
I don't now, where I can search, but it's very annoying.
FormelLMS said:
Yes, definitely.
I've seen that Whatsapp and Spotify doesn't go to sleep. Whatsapp was at last more than eleven hours online in Background.
Hoping that this is an issue of this update here and they can fix it soon.
I don't now, where I can search, but it's very annoying.
Click to expand...
Click to collapse
You could stop Spotify using tracking permission. I know thats one reason it's in the background so much other than music cause it tracks your steps. Could restrict WhatsApp in the background?
I see google have run into a serious issue for august then, not a sniff of an ota.
boe323 said:
I see google have run into a serious issue for august then, not a sniff of an ota.
Click to expand...
Click to collapse
Usually always around 8/9 am pst, and first Monday of every month. Just like last month.
fullofhell said:
Usually always around 8/9 am pst, and first Monday of every month. Just like last month.
Click to expand...
Click to collapse
Oh so its monday morning in USA, no probs then.
devsk said:
So, no fix for the muffled sound in calls?
Click to expand...
Click to collapse
Nothing. The same sh!t
By months my 3a won't automatically update itself even with update/download "over any network", I have already tried to restore and wipe from recovery but still unresolved.
Does anyone noticed this issue?
I tried waiting almost one month without system (monthly patch) and apps (all pending) updates popup.
Google support after few attempts, just proposed me a warranty replacement but the phone otherwise is perfect.
Manual updates works.
Any tips?
TY
I had the same issue back in January and didn't get a system update well into April. So I had to manually update. Still haven't gotten the May update yet, but we'll see.
Also with the apps?
If you have an unlocked bootloader, I would not count on automatic monthly updates. They work sometimes, but not most of the time. My personal experience is that I have to sideload the monthly updates about 90% of the time.
As far as app updates, I generally manually check it every couple of days and find that there are pending updates. I will hit the "update" button and manually update them if I see pending updates. That being said, if I don't check it for a while (maybe a week), the phone will eventually update the apps, but it certainly doesn't happen on a daily basis, at least not in my experience. I just wanted to add my experiences as they seem to be very similar to yours.
sic0048 said:
If you have an unlocked bootloader, I would not count on automatic monthly updates. They work sometimes, but not most of the time. My personal experience is that I have to sideload the monthly updates about 90% of the time.
Click to expand...
Click to collapse
Having an unlocked bootloader, too, but I never had issues with updates until now, they are coming directly at the first day Google is sending out the OTA.
I wonder if our phone service provider is also a factor? I have not been seeing the updates available within a day or two of when they are posted on the first Monday of the month. I get my phone service through a T-mobile MVNO. Maybe people on Google Fi are more likely to get it OTA quickly?
My phone is rooted with Magisk.
But I'm impatient so I have always just applied the update manually. It's a bit more of a pain because it means that I have to download not only the update but also the factory image to extract the boot image file and patch it with Magisk.
I have not had a problem installing updates for apps through play. I just have to remember to NOT update youtube so that I don't lose youtube vanced!
Hi all and thanks for your time!
I have a good news.
After avoid to do any manual update, right now I see that few apps have been updated themself from 11 hr and 2 days ago, but other 22 apps are still pending (when I wrote here the 6th May they were 40).
Around the 23th of Feb I had to do manual update search because it still was with Jan patch, even in March and April I did the manual search the week after the day 5th.
My phone is not rooted and during the day it uses both cellular and WiFi networks, mostly of the nights I put it in airplane mode and battery save (so it lasts easily for 2 days).
The cause was because I put all the nights the phone in airplane mode with battery saver, last night I leave it connected to WiFi and under charge, this morning I found the advice to reboot for install the system patch and after boot also the apps were updated.
The system patch has been found around 4 am.
I'm having a similar issue with my rooted 3a. I have stock rom, elemental kernel, and magisk. But apps that came installed as part of the ohone won't update in Google play. Stuff like phone, contacts, sim carrier, Gmail, camera, etc
There's literally about 20 updates right now that won't install. They download, and say installing, then they just skip to the next and still say there's an available update. After the final one is tried, I get a message saying that it was unable to update those apps.
Any app that I downloaded from play or as an apk, allows me to update without any issue at all.
I have googled it and followed the recommendations, but so far, nothing has helped. I cleaned the cache, hard reboots, switch update settings, turned off play protect, deleted cache and data of play store and play services. Removed my account and added it bad. And have some a few more things that I read about -- but yet nothing fixes it.
If I should start a new thread, that's no problem. I don't want to hijack this one. But saw that it dealt with update issues and thought maybe I would see if I could find help.
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.