Related
NEW: I created new unlocks for (almost) all Samsung WP7 devices, including 2nd generation devices like Focus S and Omnia W! More info here. Guides will be updated as soon as possible!
In Mango there is a new type of lock: INTEROP-LOCK
Normal WP7 apps are Silverlight or XNA apps. They run managed code. Some apps also use native code (C++), but Microsoft restricts the use of native code to certain selected partners, because native code is more sensitive to errors and need higher care. But there are no real boundaries for running native code on WP7 devices, as I explained here. If your device is AppHub- or ChevronWP7-unlocked, you can run the apps with native code. For example the Version and Language tool from this thread uses native code, but it can run on normal unlocked devices. But there are also apps that need access to drivers on your phone. These apps need the Interop Services capability. This capability is only allowed to software from Microsoft and from OEM's. But many homebrew apps need this capability too, to get higher privileges for tweaking your device. The new Interop Lock means that this capability is locked down. So, even when you have a legit AppHub-unlock or ChevronWP7 Labs unlock, you still can't side-load apps that need higher privileges to run. For example WP7 Root Tools needs this capability to run. But when your device is INTEROP-LOCKED it will show error 0x81030120 when you try to deploy it to your device.
Contable and Marvin_S did research on it and found that the registry setting MaxUnsignedApp is responsible for the INTEROP-LOCK. I did more research and I identified the code that is responsible for this check. In fact, if you have the MaxUnsignedApp value set to 300 or higher, your interop will be unlocked. The value of MaxUnsignedApp is determined by the type of developer-unlock you have. A normal AppHub account will have it set to 10 and a student account will have it set to 3. So a value of 300 or higher is not a realistic value for a normal developer account. It is probably only set to this value for Microsoft employees and OEM developers.
Until now, the only way to do an INTEROP-UNLOCK for MANGO meant that you have to downgrade to NoDo first, then prepare your device by loading provxml files to your device, upgrade to MANGO and then use OEM tools to execute the provxml files and do the necessary unlocks. But that is a lot of work and for some devices not even possible, because there are simply no ROM's available.
So I wanted to allow people with MANGO shipped on their device and using a legit developer unlock, to use WP7 Root Tools and other MANGO-compatible homebrew apps.
I have developed a method to do this. I have a Samsung Omnia 7 and it works on my device. It should also work on Samsung Focus. ATLien68 brought to my attention that it is also possible for LG devices to do an Interop Unlock on Mango. So I created a guide for LG too.
This only works on devices that already have a developer-unlock!
DISCLAIMER
I will not take any responsibility for any damages caused directly or indirectly from using the software-package or the instructions. Read the instructions thoroughly and proceed carefully!
BACKUP
You may want to make a backup of your device in case something goes wrong. This is what I do to make a backup:
1. Download hx4700 Killer's WP7 Backup version 1.6 from this thread. Note that I use version 1.6, not 1.8.
2. Download this archive. It is from xboxmod's WP7 Update Cab Sender thread.
3. Use Zune 4.8 final (4.8.2345.0).
4. Setup-UpdateWP 4.8 beta 3 from the archive.
5. Extract the "Tools" folder from the archive.
6. Setup the Backup tool to reference Zune.exe and the UpdateWP.exe in the extracted Tools-folder.
7. Create your backup. The backup app will allow you to archive any previous backup. Your phone will restart and go in Download-mode. When the backup is finished, the app will tell you to disconnect. Even though your phone says you still can't disconnect, you can safely disconnect the phone and it will restart.
SAMSUNG
WARNING!! The new Samsung Omnia 7 KK2 update will prevent the use of Interop Unlock and WindowBreak! This Samsung Firmware update is accompanied with the 7.10.8107.79 if you update with Zune. Other Samsung devices are probably affected too, but I don't know if the update code for those device is KK2 too. If you are already unlocked, this update will not relock your device. If you want to keep the possibility of Interop Unlock open, then use the method described in this thread to update to 7.10.8107.79 without updating to Samsung KK2!
1. Download the software package Interop Unlock by Heathcliff74 v2.xap.
2. Connect your phone to your desktop computer, running Zune.
3. Check for updates and let all pending updates install.
4. Uninstall the Samsung Diagnosis app.
5. Dial ##634# to install the latest Samsung Diagnosis app.
6. Use any Windows Phone App Deployment tool to install Interop Unlock by Heathcliff74 v2.xap.
7. Run the Samsung Diagnosis app. You should see version 1027, 1122 or 0103 at the top. The version is the compile-date without year. So version 0103 is actually newer than 1122. Versions from before 2010/10/27 do not seem to work. If you have such an old version of the Diagnosis App you need to run the latest Samsung Update (Mango Drivers) from Zune or update manually as described here. After the update you need to perform step 4 and 5 again.
8. In the Diagnosis app dial: *#9908#
9. Select "Heathcliff74 Interop Unlock"
10. Tap "Save", tap "Close" and exit the Diagnosis app. You are now unlocked, but your 3G settings are screwed (side-effect).
11. To repair your 3G settings use one of these six options:
---- 11.1. NEW: This option only works on 1st generation Samsungs. Download "Samsung Repair 3G by Heathcliff74.xap" and run it on your phone. It should work immediately.
---- 11.2. Use the Diagnosis app (thanks to Vintage144 for the tip).
-------- 11.2.1. Open up the Diagnosis app.
-------- 11.2.2. Dial this to enable autoconfigure sim setting: *#94765# (or dial 40*047#3, it's the same - more diagnosis codes here)
-------- 11.2.3. It will ask you to restart the device. Confirm that.
---- 11.3. If your device is not locked to a specific operator, you can use the Samsung Network Profile app (for 1st generation) or Wireless Manager (for 2nd generation)
-------- 11.3.1. Uninstall the Samsung Network Profile / Wireless Manager app.
-------- 11.3.2. Download and install the latest version of the Samsung Network Profile / Wireless Manager app from the Marketplace.
-------- 11.3.3. Open the Samsung Network Profile / Wireless Manager app.
-------- 11.3.4. Select a different Network Operator.
-------- 11.3.5. Now Select your own Network Operator again.
-------- 11.3.6. Exit the Network Profile / Wireless Manager app.
---- 11.4. Use lyriquidperfection's Samsung Tools (probably only works on 1st generation Samsungs).
-------- 11.4.1 Download the Samsung Tools here.
-------- 11.4.2. Deploy the tools to your phone (which is now possible due to Interop-Unlock)
-------- 11.4.3. Start "Samsung Tools"
-------- 11.4.4. Select "Run ADC"
-------- 11.4.5. Tap "Reboot"
---- 11.4. Use WP7 Root Tools for manual repair (I will add an option to repair 3G in the next version, currently only works on 1st generation Samsungs).
-------- 11.5.1. Download WP7 Root Tools here.
-------- 11.5.2. Deploy WP7 Root Tools to your phone (which is now possible due to Interop-Unlock).
-------- 11.5.3. Open WP7 Root Tools.
-------- 11.5.4. In the registry editor navigate to Local Machine\System\AutoDataconfig.
-------- 11.5.5. Set value ConfigurationStatus to 0 and set value RunADC to 1.
-------- 11.5.6. Restart your phone.
---- 11.6. Use TouchXperience Advanced Config Tool 1.4 (thanks to Ludovic B. for the tip, probably only works on 1st generation Samsungs).
-------- 11.6.1. Download Advanced Config Tool here.
-------- 11.6.2. Deploy Advanced Config Tool to your phone (which is now possible due to Interop-Unlock).
-------- 11.6.3. Open Advanced Config Tool.
-------- 11.6.4. Go to "Tweaks" and scroll down.
-------- 11.6.5. Check "Run Auto Data Config".
-------- 11.6.6. Scroll down and tap "Reboot phone".
Resolve Samsung connection problems
Thanks for this info to lulede!!
A lot of Samsung owners have complained here about connection problems. They blamed Interop Unlock, but apparently this has more to do with enabling "Internet Connection Sharing" than with "Interop Unlock". You should be able to recover the connection, apply this:
1. Start Diagnosis App> *#32489#
2. Tap "Back" 2 times to go back to Phone Control
3. Choose: [7] Network Control
4. Choose: [1] GFC
5. Choose: [3] Setting Cancellation
Wait for it to say success, then reboot.
LG
1. Install the MFG app by dialing: ##634#
2. Open the MFG app. The password is: appmfg#*#
3. Go to Engineer Menu -> Other Settings -> Edit Registry
4. Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
5. Set your input path to "\Comm\Security\LVMod"
6. Set your input key to "DeveloperUnlockState" and set to DWORD.
7. Leave input data box empty and tap "SET".
8. The output should be 0.
9. Now enter "1" in the inputbox and tap "SET".
10. The output should be 1.
11. Set your input path to "\Software\Microsoft\DeviceReg"
12. Set your input key to "PortalUrlProd" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input key to "PortalUrlInt" and set to DWORD.
13. Clear the input data box and hit "SET".
14. Output result should be "0".
15. Set your input path to "\Software\Microsoft\DeviceReg\Install"
16. Set your input key to "MaxUnsignedApp" and set to DWORD.
17. Clear the input data box and hit "SET".
18. The output should be 0.
19. Now enter "2147483647" in the inputbox and tap "SET".
20. Output result should be "2147483647".
HTC
I didn't do this hack for HTC's all by myself. This hack is a joint collaboration of XDA members. A valuable part of this hack was done by Kounadisk and GoodDayToDie. Thanks to them!
Also thanks to CeesHeim for arranging a hand-on HTC device for me to test with.
This hack need the HTC Connection Setup app. HTC Arrive can't run the HTC Connection Setup app. Therefore this hack will not work on HTC Arrive. Verizon Wireless Trophy users should follow slightly different steps. Scroll down for instructions that are specifically meant for Verizon Wireless Trophy.
Developer unlock can be either AppHub or Chevron Labs.
Important note: From what I understand, HTC has released *two* OEM updates after Mango. The first one was released together with Mango and included the first Mango drivers from HTC. I will call those the HTC Mango Drivers v1. The second one is being rolled out now and is by other people referred to as the "tethering update". This update also contains updated drivers. I will call those the HTC Mango Drivers v2. If you have a 1st generation HTC device, you may or may not have installed the HTC Mango Drivers v1 or v2. If you are on Mango with Interop Lock, you may need this hack to perform Interop Unlock. The HTC Mango drivers have extra protection which will reject the configuration settings for Interop Unlock. The current hack for HTC defeats the extra protection in HTC Mango Drivers v1. But in HTC Mango Drivers v2 there is an even more advanced protection, which is a breaking change that causes the Interop Unlock to fail. The second generation HTC devices (HTC Radar / HTC Titan) come with the HTC Mango Drivers v2 preloaded. So currently only First generation HTC Mango devices can only be Interop Unlocked if there are no HTC Mango updates or only HTC Mango Drivers v1. So the first generation HTC devices that also have the HTC Mango Drivers v2 and the second generation HTC devices can currently not be Interop Unlocked. I am looking for an exploit in the HTC Mango Drivers v2. If you have a first generation HTC device and you have the HTC Mango Drivers v2 and you still have a backup from before that last update, you can restore that backup and apply Interop Unlock. You can update to the latest drivers again and preserve the Interop Unlock.
There are also users with 1st generation HTC devices only HTC Mango Drivers v1, who report that this is not working. This can be fixed. These people should read the notes at the end of this guide!
1. Make sure you have a backup of your device (scroll up for instructions)
2. Make sure you hava a backup of your backup (No kidding! Zune may overwrite the backup you made. Here's the backup: %LocalAppData%\Microsoft\Windows Phone Update)
3. Download this attachment to your PC: HTC Interop Unlock.xap
4. Connect your device to a PC running Zune and install the xap-file using any xap-deploy-tool. You don't need to start the app. If it starts automatically, you can close it right away.
5. Download and install HTC Connection Setup on your HTC device (if you don't have it already)
6. Start HTC Connection Setup.
7. Tap the three dots in the down-right corner of your screen and tap "manual select".
8. Tap on the country. This will open a list of countries you can select.
9. In the country-list scroll to "Interop Unlock" and select it.
10. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished.
11. Tap "Done" to exit the app.
12. Now open "Connection Setup" again. This is to prevent Connection Setup opening when you restart your device.
13. It will show you your current operator.
14. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished again.
15. Tap "Done" to exit the app.
Note for people who don't have this working: I changed the order of the steps in the guide a little bit. If you have attempted to deploy other hacks using HTC Connection Setup (GoodDayToDie version for Interop Unlock or something else) it could be that the files that were deployed are blocking this new hack. You should try to uninstall HTC Connection Setup, restart your phone and then follow the the steps in the guide again (with changed order). Hope that works for you.
Steps for Verizon Wireless Trophy users (thanks to LiFePo4 for modified instructions):
1. Make sure you have a backup of your device (scroll up for instructions)
2. Make sure you have a backup of your backup (No kidding! Zune may overwrite the backup you made. Here's the backup: %LocalAppData%\Microsoft\Windows Phone Update)
3. Download this attachment to your PC: HTC Interop Unlock.xap
4. Connect your device to a PC running Zune and install the xap-file using any xap-deploy-tool. You don't need to start the app. If it starts automatically, you can close it right away.
5. Download and install HTC Connection Setup on your HTC device (if you don't have it already)
6. Go to Settings / Cellular and set Mode to GSM. Exit back to main screen and wait for data connection to go away (there will be a little box with the crossed circle in the upper left where connection status is shown).
7. Start HTC Connection Setup.
8. Tap the three dots in the down-right corner of your screen and tap "manual select".
9. Tap on the country. This will open a list of countries you can select.
10. In the country-list scroll to "Interop Unlock" and select it.
11. Tap on the round ok-button at the bottom of your screen and wait until connection setup is finished.
12. Make sure you perform step 12 and 13 directly after each other! Tap "Done" to exit the app. This will take you back to the applist.
13. Quickly Uninstall HTC Connection Setup and never allow it to run again.
14. Power off and back on phone.
15. Go back to Settings / Cellular and set Mode to CDMA. Exit to main screen and verify 3G is there.
16. Go back to Settings / Cellular and set Mode to Global. Exit.
17. Uninstall the HTC Interop Unlock.xap
This method does not loose 3G (HTC connection setup really does no good with the CDMA network so it used only once for Interop Unlock; if it ever runs a second time it screws up the CDMA data connection).
Note to people who have trouble with their HTC Connection Setup restarting automatically on every reboot of the device, or having problems with their data connection:
Normally the Connection Setup should be restored automatically with this hack. But if something goes wrong, it is possible that your HTC Connection Setup is left in a unservicable state. I that case follow these steps:
1. Download and deploy the attachment: Repair HTC CS.xap
2. Run Connection Setup.
3. Apply settings of your operator.
4. Uninstall Repair HTC CS.
That should do it.
Note to everybody: Please report success and failure, including all device specs and abnormalities (errors etc)! I want to improve the guide as much as possible!
Have fun with homebrew now!
Heathcliff74
No link for Interop-Unlock xap
snickler said:
No link for Interop-Unlock xap
Click to expand...
Click to collapse
I added it again. My browser was behaving strangely. It got lost somehow.
Heathcliff74 said:
I added it again. My browser was behaving strangely. It got lost somehow.
Click to expand...
Click to collapse
Dude you have the legendary tools .
So, if I just have a Mango device that is Dev unlocked, I can use this and get a "full unlock" on my phone ?
I really would like to know if it works on one of the HTC leaked roms. I really want to upgrade due to the better performance, DLNA support, better radio, etc but, I can't get a "full unlock" on it due to not going back to NoDO (and there is NO backup rom for the Verizon HTC Trophy, Yes, I have looked).
Does this have the INTEROP tag in the app ? If it does not, it should install no problem on a dev unlocked device.
Almost tempted to go back to NoDo and upgrade with only a Dev unlock to 7720 to try this, if I can get a full unlock from that point, I know it will work and this would be epic !
This sounds awsome if it works on HTC devices....
Crossing fingers....
i have tried deploying it on my htc mozart. it gives an error message saying 'the program has been blocked by group policy'
no LG support yet?
(I don't need it but thought I'd ask anyway)
thanks
Ok. Not working as expected
The good news: It still seems to be working on Samsung! But you will need an updated version of the xap. I will post it in a few minutes.
I tried to deploy CustClear.provxml to \Windows. On my device that seemed to work. I thought I had disabled my root-access. But I forgot to disable some of my policies. The result was that I had access to write to \Windows this way, while 'normal' device don't have that.
But I still seem to have write-access to \provxml for Samsung. I double-checked it now.
I will update the opening post.
Sorry to HTC users
Ciao,
Heathcliff74
---------- Post added at 02:35 AM ---------- Previous post was at 01:39 AM ----------
DavidinCT said:
So, if I just have a Mango device that is Dev unlocked, I can use this and get a "full unlock" on my phone ?
I really would like to know if it works on one of the HTC leaked roms. I really want to upgrade due to the better performance, DLNA support, better radio, etc but, I can't get a "full unlock" on it due to not going back to NoDO (and there is NO backup rom for the Verizon HTC Trophy, Yes, I have looked).
Does this have the INTEROP tag in the app ? If it does not, it should install no problem on a dev unlocked device.
Almost tempted to go back to NoDo and upgrade with only a Dev unlock to 7720 to try this, if I can get a full unlock from that point, I know it will work and this would be epic !
This sounds awsome if it works on HTC devices....
Crossing fingers....
Click to expand...
Click to collapse
"FullUnlock" is a prove-of-concept from Cotulla. You can read about it here. FullUnlock is a way to run native executables.
This is slightly different. I called this "Interop Unlock". Interop locking is meant to block native code in a Silverlight app. All your normal apps are Silverlight apps. Many homebrew apps are Silverlight apps that use native code, like WP7 Root Tools. The method described in this thread is to allow Silverlight apps use native code. This is not for native executables.
Read more about the different type of unlock here.
Most custom roms already have this kind of unlock. This is primary meant for devices with Mango shipped on it.
This app does not have the Interop-flag in it. It is meant to allow to deploy other apps with the Interop flag that previously would not install.
Anyway, for now this seems to be working only on Samsungs. So unfortunately no HTC support as yet.
Ciao,
Heathcliff74
Gosh I wish the Dell Venue Pro had cool stuff, I am almost to the point of giving up hope. Ill never lose my NODO backup just in case thanks cliff
Heathcliff, you never cease to amaze me. Great work. One issue though. The Network Profile app doesn't work on my AT&T Focus, when I open it up it says "It cannot be used if in a locked state by mobile operator. If I click OK it won't let me change from AT&T.
But the good news is I was able to install your new root tools now! No rolling back to Nodo needed. I just need a way to fix my 3G without network profile
EDIT: I just tried installing the "unofficial" network profile app that works on locked phones, but the app doesn't open. It goes right back to the start screen.
EDIT 2: OK I think I have 3G back. I installed Samsung Tools by lyriquidperfection here, I selected Set 'Run ADC' flag at next boot. I now have my 3G logo back. He included the source for the xap, maybe you could include this with your xap that we can run?
Awesome!!!!!!!! Works perfectly!
I've always been able to install apps with "ID_CAP_INTEROPSERVICES". However I can never run them as they crash right away. I was really excited when I first heard of this today but now i'm just confused.
ANyone with a HTC device confirm this works ?
Nice! Worked perfectly for me (Samsung Focus) I did have to use Samsung Tools to get my 3G back since I couldn't use the Network thingy but that wasn't a problem since my phone can now sideload interop apps.
What Omnia7 ROM have you flashed, so that can get the newest Diagnosis app? I have flashed the newest WP7_Product NoDo Rom (I8700XXKC1_XXKB2) and it comes with Diagnosis ver.0103. Uninstalling and re-entering Diagnosis mode, installs the same old version.
chemeng said:
What Omnia7 ROM have you flashed, so that can get the newest Diagnosis app? I have flashed the newest WP7_Product NoDo Rom (I8700XXKC1_XXKB2) and it comes with Diagnosis ver.0103. Uninstalling and re-entering Diagnosis mode, installs the same old version.
Click to expand...
Click to collapse
I have the same ROM and the same Diagnosis app version and it works fine.
Please Help me...the trick works but i'm not able to get my 3g connection working again...I didn't understand the "samsung network profile" thing in the guide before doing the trick and now i'm without connection...how can I repair it? I'm from Italy and i have an omnia 7 and i'm not able to find the app "samsung network profile" in my marketplace...you can just tell me how to go back, it's not a problem if i'll lose the interop-unlock...
CrazySE said:
Please Help me...the trick works but i'm not able to get my 3g connection working again...I didn't understand the "samsung network profile" thing in the guide before doing the trick and now i'm without connection...how can I repair it? I'm from Italy and i have an omnia 7 and i'm not able to find the app "samsung network profile" in my marketplace...you can just tell me how to go back, it's not a problem if i'll lose the interop-unlock...
Click to expand...
Click to collapse
Just look at the previous page:
ryotgz said:
EDIT 2: OK I think I have 3G back. I installed Samsung Tools by lyriquidperfection here, I selected Set 'Run ADC' flag at next boot. I now have my 3G logo back.
Click to expand...
Click to collapse
worked perfectly on my omnia 7 with mango rtm
thanks!
so no chance for Dell Venue Pro?
I live on a boat, and wanted to use my phone as a gps source with opencpn ... turns out it wasn't too hard. Thought I'd share with the class.
You'll need com0com or some other virtual com modem. Either that, or send it directly out to a nmea 2.3 network over serial.
com0com 64bit download: available here
com0com 32bit download: available here
2 Scenarios are available, to use with software on your computer:
1. Download and install com0com for your computer architecture, the drivers are not signed by Microsoft so it will warn you of this, just say install anyway.
2. Sideload the xap to your phone
3. Run connector provided with the gpskit attachment.
4. Run the app on the phone, taking care to ensure the device is tethered to the computer being used and Zune is running.
5. Press enable.
6. If everything is running fine, you should see updates from the phone in the connector console window.
7. Running Google Earth:
- Start Google Earth
- Click Tools->GPS
- Select the realtime tab
- Set up options or just use the defaults
7. Setting up OpenCPN
- Start OpenCPN
- Click the wrench icon (toolbox)
- Select the GPS Tab
- type into the NMEA Data source the other com port (if you are using defaults: CNCB0)
8. Track away at your position
To use with an existing NMEA Network:
1. Sideload the xap to the phone
2. Start the gpskit client on the computer, and enter 9060 as the default service port and the com address of the NMEA connector that is connected to the computer.
3. Run the app on the phone ensuring that it is connected to the computer by usb and Zune is running.
And that's it, you can use your WP7 device as an external GPS device.
gpskit command line:
gpskit.exe [-p service port -c serial port] [-v] [-s]
-s must be supplied if -p and -c are provided
-v turns on verbosity and debug messages
Good hunting
Questions
withinboredom said:
I live on a boat, and wanted to use my phone as a gps source with opencpn ... turns out it wasn't too hard. Thought I'd share with the class.
You'll need com0com or some other virtual com modem. Either that, or send it directly out to a nmea 2.3 network over serial.
Simply upload it to your phone, make sure its tethered to the computer via usb, then run the app and push enable.
On your computer run NMEATest and the service port is 9060, and then a com port to write to the nmea data to. Fakegps is a service I wrote that basically uses the defaults of NMEATest and would work whenever the app was running on the phone. However, I cannot guarantee it will work and I wouldn't recommend using it. However, it contains the library that nmeatest requires and I'm not a big fan of copy/paste.
To use it with your application like google earth, opencpn simply download a virtual null modem like com0com and then point it to one of the default com ports it creates. After that, start up the app like normal and with the software running google earth will catch it under tools/gps/live menus
Have a very spledid day, I'm going sailing.
PS. I'm not sure how mono treats the serialport class ... so maybe it'll work on linux? Someone let me know.
Click to expand...
Click to collapse
Hi withinboredom
Could you please recommend null modem software for an x64 machine? Also, the instructions are not that clear.
Thank you very much for putting this together.
Cheers
andrew-in-woking
Just edited the post, that should make it a bit easier.
Uploaded a new version with command line switches
Further instructions needed I think
withinboredom said:
I live on a boat, and wanted to use my phone as a gps source with opencpn ... turns out it wasn't too hard. Thought I'd share with the class.
You'll need com0com or some other virtual com modem. Either that, or send it directly out to a nmea 2.3 network over serial.
com0com 64bit download: available here
com0com 32bit download: available here
2 Scenarios are available, to use with software on your computer:
1. Download and install com0com for your computer architecture, the drivers are not signed by Microsoft so it will warn you of this, just say install anyway.
2. Sideload the xap to your phone
3. Run connector provided with the gpskit attachment.
4. Run the app on the phone, taking care to ensure the device is tethered to the computer being used and Zune is running.
5. Press enable.
6. If everything is running fine, you should see updates from the phone in the connector console window.
7. Running Google Earth:
- Start Google Earth
- Click Tools->GPS
- Select the realtime tab
- Set up options or just use the defaults
7. Setting up OpenCPN
- Start OpenCPN
- Click the wrench icon (toolbox)
- Select the GPS Tab
- type into the NMEA Data source the other com port (if you are using defaults: CNCB0)
8. Track away at your position
To use with an existing NMEA Network:
1. Sideload the xap to the phone
2. Start the gpskit client on the computer, and enter 9060 as the default service port and the com address of the NMEA connector that is connected to the computer.
3. Run the app on the phone ensuring that it is connected to the computer by usb and Zune is running.
And that's it, you can use your WP7 device as an external GPS device.
gpskit command line:
gpskit.exe [-p service port -c serial port] [-v] [-s]
-s must be supplied if -p and -c are provided
-v turns on verbosity and debug messages
Good hunting
Click to expand...
Click to collapse
Hi withinboredom
I'm still can not seem to get this to work. Here is what I did:
Disabled UAC and put Windows 7 into Test Mode to allow unsigned drivers
Installed 64-bit version of com0com
Renamed the two virtual ports to COM17 and COM18 using the com0com graphical setup utility
Sideloaded the App onto my phone, started it and enabled the service
Started GPSKit.exe
In the command line window I set the service port to 9060 and set the Serial Port to COM17
I did not get any information showing up from the phone
Opened Google Earth and set GPS to realtime tracking
When I clicked "Start" it scanned through the ports and stopped at "reading COM17" but did not seem to provide any GPS information.
I followed the same procedure again but this time set the Serial Port to COM18 in the GPSKit.exe command line window which lead to the same result.
Can you please tell me what I have done wrong?
Thanks
andrew-in-woking
Make sure Zune is running and recognizing the phone before starting the service on the computer. Also make sure that pressing enable is the LAST thing you do before starting google earth (if you push it too early, you can press it again to start the connection over again - good for force refreshing the position if the phone decides to stop getting it.)
Yes, working now
withinboredom said:
Make sure Zune is running and recognizing the phone before starting the service on the computer. Also make sure that pressing enable is the LAST thing you do before starting google earth (if you push it too early, you can press it again to start the connection over again - good for force refreshing the position if the phone decides to stop getting it.)
Click to expand...
Click to collapse
Hi withinboredom
Thank you very much. It is now working.
Very good job.
andrew-in-woking
@withinboredom
thank you good job.
Interesting, thanks.
Sent from my ViewPad7 using XDA App
No position with opencpn or maxsea
Hi
this is the perfect solution for me, but i cant get a location with opencpn or maxsea. with google earth it is working. any ideas?
I can see that opencpn recieves data from gps, but cant show position.
I found someone with the same problem at opencpn forums. This problem is fixed in the latest beta of Opencpn.
It may have something to do with this:
"I suspect the NMEA sentences do not have CR/LF line endings. They may have only CR, or only LF.
For instance, GPRMC will be "Unrecognized" if the line endings are not correct, although it looks right to the eye."
Any chance you could check this? if this is fixed i can also use this with maxsea.
HI all
maybe its wise to start a new thread how to make an offline package for our phones
especially because of these info :
Microsoft begins to block Windows 10 Mobile updates for the majority of Windows phones
https://mspoweruser.com/microsoft-begins-block-windows-10-mobile-updates-majority-windows-phones/
https://mspoweruser.com/only-13-windows-phones-will-get-the-windows-10-creators-update/
My question is :
-how to make an offline install able upgrade/update package for our phones ( fiddler i think )
-how to update the phone with all the cabs downloaded ( uitool.exe ?? )
What i know .. first install old firmware on your phone , install fiddler on your pc and download from your phone thats connected to the fiddler proxy your files.
Can one of you guys make a SIMPLE instruction how to download these CAB files from microsoft ? and how to configure fiddler in this case
The last question ...
What i know ... use uitool.exe to "upload" / install these downloaded cab files ( through fiddler ) on you phone.
Can one of you guys make a SIMPLE instruction how to install these cab files ???
I think i can speak for a lot of people with the same question.
Now i have to google/use xda search to find what i need but all the threads are old an out-dated or have old information.
Many thanks in advance !!!
Micheal
megasounds said:
-how to make an offline install able upgrade/update package for our phones ( fiddler i think )
Click to expand...
Click to collapse
That's one way:
- you set up a sniffing proxy on your PC (like Fiddler or Paros)
- configure it to record, maybe even save a copy, of the data it passes through
- flash a rom with WDRT to uninstall updates and start from a known and replicable point, configure a network with your proxy ASAP, and just let it download updates to have a list of cabs to redownload (or even the files themselves, again I'm not terribly familiar) on your PC!
OR you can go to the Microsoft Update Catalog with a non-IE browser, search for a W10M update pack (suggested search string: "000-ru") and from there you can get a list of every single cab for the version you selected!
In fact you will find even cabs not applicable to your phone (indeed you've probably heard of this method from the "download continuum/reset protection to unsupported models" topics), plus there may be a sequence to respect (for instance you can't flash RS3 directly from WP8, as some versions - TH2 in this example - add support for new update formats ["servicing stacks", you may have seen in PC updates])
megasounds said:
What i know ... use uitool.exe to "upload" / install these downloaded cab files ( through fiddler ) on you phone.
Can one of you guys make a SIMPLE instruction how to install these cab files ???
Click to expand...
Click to collapse
This part is easy: you indeed download iutool (from some "windows sdk" download from Microsoft, or a portable version from some interop unlock topic here on xda), then the command is:
iutool -v -p {path to folder with the update files}
And you wait for the files to be copied (nothing will be obvious on the phone) then it'll just reboot to the usual "update/format progress bar" screen - assuming everything went right! All failures, you'll see on the computer screen, in a not terribly useful way...
Fiddler settings:
Tools > Telerik Fiddler Options > Connections (tab):
- Act as system proxy on startup = off
- Monitor all connections = off
- Allow remote computers to connect = on
Restart Fiddler and allow on firewall; Enable "Stream" button on the toolbar
Flash your phone, turn off all WWAN and privacy-related options during initial setup, don't use a MS account, run to the store and turn off auto updates (all of these to minimize non-update network requests)
Configure wifi to have a proxy at your computer's IP and port 8888 (you could have changed it in the settings above),
Just download the updates from system settings as usual, you'll see the list of requests fill up in Fiddler
[Do not enable File>Capture Traffic, that's for dumping the activity of the same computer that runs Fiddler, despite the name]
Once your phone gets to "preparing to install updates", all have been downloaded: so sort the columns by "Host" and select all requests related to "download.windowsupdate.com"
File > Export Sessions > Selected > Raw Files > select a dump folder and leave all 3 options enabled
The dump folder will open, now you have to flatten it (go inside the subfolders and copy all the files in one single folder; if you have Unix "find" this is easy to automate, but with only 10 folders or so it's not too tedious even by hand)
This single combined folder is now what you can pass to iutool for updating via USB!
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:
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