Related
Dear Community,
Greetings,
I have been using the mate 20 x for a while now, and very happy with it, what is missing from the phone (and the mate 20 pro too) is the pocket mode in the settings of the dialer app. I had this option on my old Huawei P9.
When having the phone in my pocket, and a phone call starts ringing, the ringtone volume starts increasing, and this doesn't look good when I'm at work or in a meeting.
Is there any ADB command to bring the option to the settings (I used the ADB commands on P9 to show the Font Styles which was missing from the phone).
Regards,
Pocket mode gone
Hi I have the same problem,
latest with EMUI 9.0.0 the pocket mode setting cannot be found via dialer > three dot menu anymore.
Regardless of volume settings (except for vibrate only) the ring tone volume keeps increasing to embarrassing loudness levels when the phone is in my briefcase.
Is there any change to disable the pocket mode "feature" when you cannot access it anymore?
Regards,
MaeSiuS
Finally, a solution to missing pocket mode option
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Does this solution works on a Huawei P30 too?
There is the same problem.
flummi19200p said:
Does this solution works on a Huawei P30 too?
There is the same problem.
Click to expand...
Click to collapse
Most probably, yes.
download the setedit application, and make sure you have the secure table, and there is a line "hide_pocket_mode".
Let me know if it works.
Hash_droid said:
Most probably, yes.
download the setedit application, and make sure you have the secure table, and there is a line "hide_pocket_mode".
Let me know if it works.
Click to expand...
Click to collapse
Is the procedure with adb Shell, conecting to PC and the adb console on a PC not necessary?
flummi19200p said:
Is the procedure with adb Shell, conecting to PC and the adb console on a PC not necessary?
Click to expand...
Click to collapse
It is necessary since it will grant permission to the setedit app to modify the secure table, without ADB, setedit won't work.
Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Oh man, this is so great! I have a P8 Lite from work which has pocket mode visible, but I also just bought a P Smart 2019 which doesn't have it visible. Or should I say HAD, because thanks to Hash_Droid I now have Pocket mode visible and disabled. I can't begin to tell you how you made my day. Thanks a lot!
Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Thank's a lot for this. It works perfectly on P30 Pro :good: :highfive:
It's hard to understand and unlogic why manufacturers like Huawei hide options like Pocket mode in their software. Most users, even the simpliest, surely are interested to customize ring tone options.
Thank you very much Hash_droid, works on P20 pro. :highfive:
Hash_droid, works perfectly on a Mate 10 Pro (I had the same issue) . Thanks a lot.
Thanks, confirming also for Mate 9, EMUI 9.1, not rooted (BL locked).
Btw, I've also enabled virtual HD sound - not sure if the call quality is better
This works on Mate 20 pro. But, if your ADB doesnt recognise your phone, install Huaweis HiSuite. Only so ADB listed my phone.
However, person at Huawei who decided that removing option to disable pocket mode should ne fired. Also, who ever designed the diler app. Huawei, just copy Samsungs dialer, or at least use google phone app. My galaxy S6 had 10x better dialer then my Mate 20 pro now has. At least I have google phone now.
Hash_droid said:
Hello,
I have finally solved it, I tried it and it works perfectly.
Here are the steps:
1- Install settings database editor by 4A from Google Play store
2- Allow developer options in your phone's settings
3- Allow USB debugging
4- Install platform tools ADB on your PC
5- Connect your phone to PC
6- Make sure your phone is recognized by ADB, type command: adb devices
7- if the ADB console list your device number, type the command:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8- On your phone, open the application Setedit
9- Go to the Secure Table from the top right menu
10- Find the line "Hide_Pocket_Mode", select the value, change it from 1 to 0.
11- Restart your phone, and you'll find the option in the dialer options, More settings.
Hope I helped, it took me time and some research, but it was worth it. lots of embarrassment caused by high ringtone in the office.
Click to expand...
Click to collapse
Thanks! This guide worked also for Huawei P40 Pro (emui 10.1.0.154) :good:
enable magisk hide on those apps in screenshot. Use xmlpak magisk mod if you don't see Samsung in play store after activating it on your watch
Please edit title to state that is requires a rooted phone, a simple "[ROOT]" would be fine. Don't want to have a misleading title.
I'm running a rooted note 9 and latest magisk, yet I don't see any of those apps in magisk hide? Not sure why
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
Delete
Dbj.Dhaval said:
Delete
Click to expand...
Click to collapse
Sorry, My mistake, instead of APK mirror link, i entered xda link, now edited the original post, please check.
ca_guri01 said:
Sorry, My mistake, instead of APK mirror link, i entered xda link, now edited the original post, please check.
Click to expand...
Click to collapse
I followed your steps, but chose SEK as region (thinking it was Sweden). However, now it's impossible to connect to the watch again with sdb. When trying to connect, I sometimes get responses like ¥¸ºeÇþx or other strange characters
EDIT: After the reset when I changed the region, the watch was also showing cyrillic characters for the instructions. However, as soon as I connected my phone, the watch changed to english.
EDIT2: I installed Tizen Studio to get the most recent version of SDB. And after a reboot of the watch, it looks like I'm getting closer:
Code:
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
connecting to 192.168.0.199:26101 ...
device unauthorized. Please approve on your device.
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
192.168.0.199:26101 is already connected
PS C:\tizen-studio\tools> ./sdb shell
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
EDIT 3:
I followed instructions here: https://stackoverflow.com/questions/54120334/sdb-device-unauthorized
To delete the key, and after restarting the watch again and running sdb kill-server, I was able to connect again and get the request to confirm my computer.
Damn Samsung, why is this **** so buggy?
Inrego said:
I followed your steps, but chose SEK as region (thinking it was Sweden). However, now it's impossible to connect to the watch again with sdb. When trying to connect, I sometimes get responses like ¥¸ºeÇþx or other strange characters
EDIT: After the reset when I changed the region, the watch was also showing cyrillic characters for the instructions. However, as soon as I connected my phone, the watch changed to english.
EDIT2: I installed Tizen Studio to get the most recent version of SDB. And after a reboot of the watch, it looks like I'm getting closer:
Code:
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
connecting to 192.168.0.199:26101 ...
device unauthorized. Please approve on your device.
PS C:\tizen-studio\tools> .\sdb connect 192.168.0.199
192.168.0.199:26101 is already connected
PS C:\tizen-studio\tools> ./sdb shell
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
device unauthorized. Please check the confirmation dialog on your device.
EDIT 3:
I followed instructions here: https://stackoverflow.com/questions/54120334/sdb-device-unauthorized
To delete the key, and after restarting the watch again and running sdb kill-server, I was able to connect again and get the request to confirm my computer.
Damn Samsung, why is this **** so buggy?
Click to expand...
Click to collapse
Yeah deleteing the key is the work around, glad you get the answer [emoji3]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
Yeah deleteing the key is the work around, glad you get the answer [emoji3]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thing is, the .tizen folder didn't exist when just installing the tools from this post. Only after I installed tizen studio
Sent from my VOG-L29 using Tapatalk
Inrego said:
Thing is, the .tizen folder didn't exist when just installing the tools from this post. Only after I installed tizen studio
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Strange, i don't have tizen studio, never installed, and still i have .tizen folder, make sure hidden items are shown in windows option
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
Strange, i don't have tizen studio, never installed, and still i have .tizen folder, make sure hidden items are shown in windows option
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
It is enabled. And it did show after installing Tizen Studio.
EDIT: I even ran the tools on another pc, and here's the user folder:
Inrego said:
It is enabled. And it did show after installing Tizen Studio.
EDIT: I even ran the tools on another pc, and here's the user folder:
Click to expand...
Click to collapse
Ok, then may be i was lucky [emoji23] [emoji23]
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
Click to expand...
Click to collapse
It is show me a failed to connect
[email protected] said:
It is show me a failed to connect
Click to expand...
Click to collapse
Delete .tizen folder from c:/users/your user name, make sure you have enabled the option of seeing hidden files, .tizen is hidden folder, if u can't see this folder, install tizen studio and remove this folder
Sent from my [device_name] using XDA-Developers Legacy app
I ve added all to magisk hide. But still cant open samsung pay watch plugin. Still getting access denied
Hey,
Is it possible that thanks to your method I will be able to turn on Samsung pay in my country (Poland) if it is not supported? Only Google pay works. Maybe I will need to do it using paypal? Thank you for your help in advance
Miccia said:
I ve added all to magisk hide. But still cant open samsung pay watch plugin. Still getting access denied
Click to expand...
Click to collapse
Fixed by using an older version of the plugin
FYI, I just received my Galaxy Watch today. Installed Samsung Pay (ver. 1.9.1206) on my Pixel 3XL and tried to run it but was denied because of Magisk (ver. 19.3 stable). So I hid the Manager via Hide Magisk Manager from within the app. I then was allowed to go through the setup process and add a credit card.
Failed to connect with remote device.
I have getting error failed to connect with remote device while connecting to galaxy watch . How to fix this.
Hello guys,
I also have error - failed to connect. When I try to ping the watch, the ping responses...
I tried it on fresh Windows 7 and 10 installations, also on Mac. Also tried to add the port to IP address. But always failed to connect... There is no message on the watch.
Any idea guys?
Thanks a lot.
I have OnePlus 7T Pro with STOCK 10.0.4.HD01AA Global version NOT ROOTED!!!
How to enable Native Call Recording,that WILL working even REBOOT:
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time :laugh:
11.100% TESTED AND FULLY WORKING!!!
Confirm, it works. Activated after restart. Good quality recordings. Thanks.
Sadly the google drive file doenst exist anymore on the server ?
Please fix.
Thanks!
zat0x said:
Sadly the google drive file doenst exist anymore on the server ?
Please fix.
Click to expand...
Click to collapse
Done.
Worked also for me... Thanks !
Hi. tried on 7T also and it work. Vers. 10.0.6 HD65AA model HD1900
fail
(('adb' is not recognized as an internal or external command,
operable program or batch file.))
please help !!
Works on my OnePlus 7T PRO HD 1910 , Oxygen OS 10.0.4.HD01AA. Thanks and keep up the good work !
Do you have to utilize the Joneplus app? Or is there a way to manually enable?
Just follow the instructions carefully.
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/d....joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/att...7&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time
11.100% TESTED AND FULLY WORKING!!!
ivo777 said:
I have OnePlus 7T Pro with STOCK 10.0.4.HD01AA Global version NOT ROOTED!!!
How to enable Native Call Recording,that WILL working even REBOOT:
1.Download and Install Joneplus app from Google Store: https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools
2.Enable USB Debugging option in Settings
3.Download https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037 Fastboot and ADB
4.Connect your Phone with PC and click on Home Screen Shift + Right button on mouse and click Open Command Window
5.In Command Promport write: adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
6.Press ENTER
7.Start Joneplus App and in Call Rcorder Settings Enable Call Recorder
8.Woala,now in Phone-Settings will appear New Option,named Call Recorder,just enable these 2 options: Call Recording and Call auto-recording
9.ENJOY,now you have Native Call Recording on your phone,that WILL WORKING EVEN AFTER REBOOT!!!
10.Now starting pizza and beer time :laugh:
11.100% TESTED AND FULLY WORKING!!!
Click to expand...
Click to collapse
Made on OnePlus 7T Pro Maclaren and working.
Thank you.
many thanks, it works in my 7T 1900
AFTER REBOOT - JUST TURN ON call recording IN JONEPLUS APP
All,
It works fine on HD1913
Thanks
All works as it should
HD1913
Sent from my OnePlus 7T Pro using Tapatalk
Great work,thanksssss
Sent from my HD1913 using Tapatalk
Do not survive a reboot I'm afraid. Needs to be toggled manually on each boot. [OxygenOS 10.0.5.HD01AA]
tal_sarid said:
Do not survive a reboot I'm afraid. Needs to be toggled manually on each boot. [OxygenOS 10.0.5.HD01AA]
Click to expand...
Click to collapse
Not in my case, it automatically starts after booting and unlocking the phone.
Oxygen 10.0.5.HD01BA
without Joneplus app and if youf dont reboot
adb shell settings put global op_voice_recording_supported_by_mcc 1
Click to expand...
Click to collapse
Does the phone update later without any problems after applying this guide?
OTA updated already 3 times with joneplus installed without problems.
OK guys your watch will still work with many Wear OS apps but apps won't sync up with your phone any more. The problem is that the version of Google Play Services on your watch is way out of date.
The solution is you need to sideload a newer version of google play services and then like magic all your apps that can still work with Wear OS 1.5 will work again.
You need to download and install adb fastboot on your PC, and the USB drivers for your particular model of phone. Then go to apkmirror and download the latest version of "Google Play Services (Wear OS)" as an APK.
Now put your Smartwatch into developer mode by going to settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable) and Bluetooth debugging (enable)
Back on your phone, Wear OS App --> Advanced Settings --> Debugging over bluetooth (enable)
Enable Developer options on your phone as well through settings --> About --> Software info --> Build number seven times. Enable USB debugging.
Plug phone into PC with usb and open a command prompt in the directory where you've installed the adb files
Code:
ADB devices
should show your phone unauthorized. Authorize it on the phone popup prompt. Now the command should show your phone as "device"
Code:
adb forward tcp:6666 localabstract:/adb-hub
adb connect localhost:6666
On your watch, authorize the connection
On your phone, Wear OS app, Advanced settings, you should see Host: connected and Target:connected
If you get into trouble, run
Code:
adb kill-server
and try again.
Now you can install the apk
Code:
adb -e install -r (path to apk)
it will take a long while and may appear to hang. Give it time, at least 15 minutes. Go do something else. Wait for the command prompt to come back.
Now reboot your watch and revel in the magic as your apps suddenly reappear.
You also try sideloading other apps your mileage may vary. On APK mirror you can sometimes find older verions of Wear OS apps, look for ones that require Android 6.0+ Instead of 7.1.+
FYI I've tried sideloading several apps, and while many don't work properly, I was able to get Maps working by sideloading
com.google.android.apps.maps_10.35.2-1035250000_minAPI23(nodpi)_apkmirror.com.apk
Hi,
Thanks for this =)
Is there a reason to push the app through the phone instead of directly to watch?
EDIT: just do the same but directly connect the watch through USB worked well for me, including installing more apps like GMaps and Messages.
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445
stormPremier said:
EDIT2: Just did this, so people could find this workaround faster =) https://support.google.com/wearos/thread/55427445
Click to expand...
Click to collapse
Sorry, this page can't be found. Do you have another link?
i5510 said:
Sorry, this page can't be found. Do you have another link?
Click to expand...
Click to collapse
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.
stormPremier said:
Weird, I can't access this page using Private Navigation, you may need to be connected to your google account to access it ?
Also, it may not be published yet.
Click to expand...
Click to collapse
Unfortunately, I don't use an account by Google. Would you mind quoting your solution here?
Hey first of all, thank you to bring me a light to follow,
I can confirm that if you use usb is more quickly, just I have:
1: installed "15 seconnds adb installer v1.4.3" found on this forum
2: Plug my smartwatch 3 on my pc (windows 10)
3: downloaded the most recent google play services (wear os) from apk mirror
4: rename the downloaded apk with a shorter name
5: placed the apk on C: and then open a power shell window in that location (****f+right click)
6: put this command adb install -r -g aplicationname.apk
7: wait 5 minutes
8: enjoy
by: Alexai Medina
i5510 said:
Would you mind quoting your solution here?
Click to expand...
Click to collapse
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this
Thanks for posting a simplified process.
I only used Bluetooth because I have other Wear OS watches that don't work over cable connect, so it's the way I am familiar with. I like to use different watches depending upon activity and mood. The Smartwatch 3 is a great watch for outdoor activities because it is sleek, waterproof, and very sunlight visible.
stormPremier said:
Hi people,
I own a sony smartwatch 3, got some problems about sync multiple times. I always found simples workarounds but some days ago, Google dropped support for wear 1.5 devices.
I consider this as an official announcement:
https://support.google.com/wearos/thread/5538033?hl=en
Therefore, we have a "workaround" for those that need more time to buy another smartwatch or else.
Inspired from this: https://forum.xda-developers.com/smartwatch/smartwatch-3/fix-app-sync-smartwatch-3-dead-t4121409
# Download the latest GService for Wear OS
Using apkmirror website you can find the latest apk for "Google Play Services (Wear OS)",
This link will give you the page of GService v20.21.17 which is the latest available on 2020-06-25.
You must ensure 2 things:
- Is it the latest version
- Is it compatible with Android 6.0+ (as it's the wear android version, 7.0+ and above will not work)
You can also download other apks to install, see the "More" section at the bottom of this post.
Soon or later, Google will definitely drop android 6.0. When this will happen, the latest version will not be available anymore for android 6.0+, therefore it will be the end.
# Download/Install adb debugging tools on your computer
There are multiple ways to install the adb debugging tool, I recommend following the steps you'll find on XDA website: https://www.xda-developers.com/install-adb-windows-macos-linux/
Available for Windows, Linux, and macOS.
# Enable ADB Debugging options on your watch
Enable developer mode by going to
Settings --> about --> build number (click it 7 times, congrats you are now a developer)
Now go to Settings --> Developer Options --> ADB Debugging (enable)
Then open and keep the command line window (aka "terminal")
# Connect your watch to your computer
Then using the terminal, type "adb devices", after a moment, you should get a prompt asking for debugging permission on your watch: accept.
In the terminal, you should now see something like "14452D11F536B52 device" when typing "adb devices" again.
If you see "unauthorized" or else, you're not ready for the next step, go back and try again.
If you struggle at this step, you may need specific drivers or else for your watch, google will be your best friend at this point.
# Send the app to your watch
In the terminal, type "adb install -r path_to_the_apk_file", replace path_to_the_apk_file by the path to the file you download from apkmirror earlier.
Then wait, the installation can take several minutes. Once it's done, restart your watch and you should see the apps beginning to synchronize themself =)
----
If you're new to the command-line tool (aka "terminal"), I'll assume you're a window user.
So you may need to type something like "adb install -r C:/Users/Robert/Downloads/file_downloaded.apk", again, you'll have to replace Robert by your windows username and file_downloaded.apk by the name of the file you downloaded earlier.
The best way to get this line right: open the file explorer, click "This computer" in the sidebar, then click on your main hard drive, then the folder "Users". Here you should see a folder with your username, click on it, then go through folders & files until you see the downloaded file. Once it's done, you should be able to get the full pathname by click in the explorer address bar (didn't understand ? See https://winaero.com/blog/show-full-path-address-bar-windows-10-file-explorer/ ) then at this point you should know how to execute the last command by reading again the last step "Send the app to your watch"
----
# More
You can follow this step and install any apk you want, but I don't recommend installing apk not made for Wear OS even if it works
More apps installable this way on your watch if you don't want to wait for app sync:
- Google Messages (SMS), latest is v6.1.095 on 2020-06-25
- Google Maps, latest is v10.35.2 (android 6.0+) on 2020-06-25
The GMaps is a good example about obsolete versions: on 2020-06-25, the real latest available is v10.43.2, but it's android 7.0+ only, so don't expect GMaps to work indefinitely for your watch, it will stop working soon or later.
# Say thanks
Please, if you can click upvote or post an answer: it will help people with the same problem find this
Click to expand...
Click to collapse
Thank you very much!!!!
You saved my watch!
Hi. In the link to install the adb debugging tool, I can only get as far step 6 connecting my phone. When i type 'adb devices' in the command prompt it says -
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
Nothing appear on my phone as per the step 7 "On your phone’s screen, you should see a prompt to allow or deny USB Debugging access"
Can anyone help?
@MrFleas
1) go again on EVERY.SINGLE.STEP this may feel dumb to do but it could help
2) if it does not work, try googling for swr50 USB drivers, you may need to download Android SDK and drivers - then reboot - then start again at step one
3) come back here to thanks or asking for more help
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
Hi people, just realized we can also download the sony app to our phones (directly from phone or by using adb like on watch) so we can edit stock watch faces again =)
Here's the app to download to the phone: https://www.apkmirror.com/apk/sony-...ditor-2-0-0-20-android-apk-download/download/
Once installed, to edit watch faces, go to wear app, the edit watch faces =)
Seems like the same issue...
My hardly used smart watch is ALIVE again!
Thanks a lot guys!
I have latest but sync not working :/ i have a question is possibile install app with higher api or change apk API level ?
check the play service on your phone and install exactly the same version of the wear app
then it works
Cheers for doing this! Got my old smartwatch working cause of that. If anyone else reading this has issues at the' ADB device' point, and is using a linux based system, remember to use sudo on the commands -as otherwise i found that it would not enable the prompt to let me 'authorise' the device in order to send the apk to the watch.
Question- given that google have disabled the onboard step counter function on wear 1.5 devices (like this one), can we sideload a fitness apk via adb with this method that will then sync to our phones?
skwal83 said:
check the play service on your phone and install exactly the same version of the wear app
then it works
Click to expand...
Click to collapse
Hi, I've got the same issue. I had to change my phone. I've installed the same version of google play services on the watch with the description in this threat. But the phone is still not syncing the apps to the watch. Is there anything more I can do to trigger the sync (already triggered 'resync all app in Wear OS' without effect).
You might try to go Settings-Permissions on the watch and set the Permissions for your app. Sometimes I have got this to make the app work, when it is already installed on the watch but not working.
It works! I first downloaded this version of Wear OS for my phone:
Wear 2.43, the newest one somehow broke the sync for me.
By using ADB with " ADB install -r "I installed the last working Google Play Services for my Watch and also the last available version of Google Fit for Android 6.
Play Services : Play Services Wear OS - 20.45.16
Google fit : Google Fit - 2.10.36
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet. (Edit 27/06/2023: new updated apk available here)
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Not works for me... I have the italian operator PosteMobile
Doesn't work for me... I tried to use a custom ROM so I could have VoWiFi, but I felt something was off. I got back to OOS13 on my OnePlus 8 Pro (IN2023) with AT&T and tried this method but no success...
omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh. You should see somewhat like "Shizuku is running" at your phone.
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Thank you! It worked on a LE2121 with Android 13!
Update:
I just updated to 13.1 and lost VoLTE. Re-did the steps and got it back.
Added an edit to step 5 in OP, as with 13.1 I had to uncheck "Disable permission monitoring" in developer settings).
It's not work. Oneplus 10 pro. Oxygen os 13.1
yasador said:
It's not work. Oneplus 10 pro. Oxygen os 13.1
Click to expand...
Click to collapse
Need to be more specific.....
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
momiloco said:
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
Click to expand...
Click to collapse
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
omar302 said:
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
Click to expand...
Click to collapse
Thanks bro.
I tried like what you suggested but still the same error.
Managed to do it using wireless USB debugging. Much easier.
Thanks
omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
kmahesh said:
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
Click to expand...
Click to collapse
I think you missed reading the first paragraph. It worked for me on my OnePlus 9 Pro on OOS 13 & 13.1. I am using a Tello (US) line which is basically T-Mobile and got VoWifi to work using these steps.
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
kmahesh said:
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
Click to expand...
Click to collapse
It seems that it doesn't work for all SIM cards. I also tried the same with a 1+ 7 Pro using another SIM and it did not work. Maybe I'll try with the Tello SIM on the 7 Pro just to test if it's an issue with the phone or SIM.
Thanks Omar for trying. All I am trying to find out (1) Is my phone the culprit (or) my T-Mobile is the culprit (2) Is there a solution (with or without rooting) to make this work for USA carriers?
Any help would be appreciated.
Thanks
Mahesh
Hello everybody. I have Oneplus 9R OOS 13.0 Android 13. I did everything according to the instructions using wifi debugging. The volte switch slider has become active. However, when making a call, the phone still falls into the H+, H or 3G network. I have 2 SIM cards installed, before starting the algorithm, I did not deactivate the second one. Could this be a problem? If so, what would you recommend to do in this case?
I tested SIM card 1 used for calls and the Internet in another device, Volte works on it.
Updated to LE2123_13.1.0.580(EX01) and off course lost VoWifi, however, repeating the steps re-enabled it.
Also found an updated Pixel IMS apk (link to download) that has more options when enabling VoLTE or VoWifi.