Amazfit Pace Enable App list and Install Apps - Altentative way - Amazfit

Background
I was have trouble getting my Amazfit Pace to be recognized by the adb program or the ADK installer. When it was in the dock it i could look at the files but not have it recognized by the other apps. I have the Amazfit Pace US version with ROM 1.3.3a
Here are the steps i took.
Enable the "developers mode" by tapping on the legal notice.
Plug in the Amazfit to the computer and put a blank file called "launcher_config.ini" in the main directory
Restart the watch. Once it has booted up connect it via the wifi to the same network your computer is on.
Open and cmd prompt and got to "C:\Users\Rich\AppData\Local\Android\sdk\platform-tools" directory (this will differ based on you user name)
Type adb connect (ip address of watch)
Then type adb install (whatever app you want)
Not sure if this is the 100% but it worked for me and my watch was right out of the box. Hope this helps some people.

Related

How to Sideload Apks onto Android Wear Watch

I have been looking how to do this for a day now with no luck. All the other applications seem to be for early Android wear versions less than 2.0 or Android 5.1.1 or less.
Option 1 (Faster)
1: Install ADB on your computer. https://www.xda-developers.com/install-adb-windows-macos-linux/
2: Enable Developer Options on your wear watch. https://forum.xda-developers.com/android-wear/development/guide-how-to-connect-adb-wifi-t3368602
3: Make sure bluetooth is off, wifi on and connected to same network as laptop.
4: Turn on debug over wifi option in developer options and wait for it to show your IP.
5: On windows, make sure platform tools are on the main drive. Ex (C
6: Copy your APK files into the same folder.
7: Inside the folder, press shift and right click. Then press "open with CMD here or powershell"
8:Type .\adb connect 192.168.0.5:5555 (use your own IP, not the ex)
9: Once connected type .\adb install facebook.apk (type in your own APK name, not the ex)
10: Wait for success, and app should be on watch
FYI some computers do not need the .\adb, just type adb
Option 2 (Slower)
* Prerequisites:
1: Computer
2: Cord to connect your phone.
Tested and works with Lineage OS Android Nougat 7.1 and Android wear 2.7 on Verizon Wear24 watch
All the credit goes to the youtuber that created the video, I'm just passing along the information.
https://www.youtube.com/watch?v=1g77uIGxvcs
http://www.mediafire.com/file/8936ojtv5axl73g/Android+Wear+Sideloader.zip
https://www.apkmirror.com/
Follow the steps listed in the Start.bat, do not run as Admin.
The APK must be loaded into the main folder, not the app folder.
Currently installed Facebook Lite, tested and works.
Opera Mini opens but force closes after a few seconds.
You may need to open the start.bat twice if it doesnt load the localhost (watch) the first time.
Just a heads up the installation transfers APKS at 51 KB/s, slow! Takes about 2 minutes for a 5mb apk.
Can this be done without the need for an Android Phone? I use an odd couple (iPhone 7 Plus with a Ticwatch E). I have access to Android via a tablet only...
agonzalez1010 said:
Can this be done without the need for an Android Phone? I use an odd couple (iPhone 7 Plus with a Ticwatch E). I have access to Android via a tablet only...
Click to expand...
Click to collapse
The first option requires a computer and the watch only!
shawndak said:
I have been looking how to do this for a day now with no luck. All the other applications seem to be for early Android wear versions less than 2.0 or Android 5.1.1 or less.
Option 1 (Faster)
1: Install ADB on your computer. https://www.xda-developers.com/install-adb-windows-macos-linux/
2: Enable Developer Options on your wear watch. https://forum.xda-developers.com/android-wear/development/guide-how-to-connect-adb-wifi-t3368602
3: Make sure bluetooth is off, wifi on and connected to same network as laptop.
4: Turn on debug over wifi option in developer options and wait for it to show your IP.
5: On windows, make sure platform tools are on the main drive. Ex (C
6: Copy your APK files into the same folder.
7: Inside the folder, press shift and right click. Then press "open with CMD here or powershell"
8:Type .\adb connect 192.168.0.5:5555 (use your own IP, not the ex)
9: Once connected type .\adb install facebook.apk (type in your own APK name, not the ex)
10: Wait for success, and app should be on watch
FYI some computers do not need the .\adb, just type adb
Option 2 (Slower)
* Prerequisites:
1: Computer
2: Cord to connect your phone.
Tested and works with Lineage OS Android Nougat 7.1 and Android wear 2.7 on Verizon Wear24 watch
All the credit goes to the youtuber that created the video, I'm just passing along the information.
https://www.youtube.com/watch?v=1g77uIGxvcs
http://www.mediafire.com/file/8936ojtv5axl73g/Android+Wear+Sideloader.zip
https://www.apkmirror.com/
Follow the steps listed in the Start.bat, do not run as Admin.
The APK must be loaded into the main folder, not the app folder.
Currently installed Facebook Lite, tested and works.
Opera Mini opens but force closes after a few seconds.
Click to expand...
Click to collapse
Thx for explanation. Any clue how i can also sideload the setting of an app to wear?
nagelo said:
Thx for explanation. Any clue how i can also sideload the setting of an app to wear?
Click to expand...
Click to collapse
No clue!
shawndak said:
You may need to open the start.bat twice if it doesnt load the localhost (watch) the first time.
Just a heads up the installation transfers APKS at 51 KB/s, slow! Takes about 2 minutes for a 5mb apk.
Click to expand...
Click to collapse
really late, but mine transferred at 555KB/s, (so close to being 6s) but yeah, pretty slow
I came across this error when following the first option. Any advice?
error: more than one device/emulator
adb: error: failed to get feature set: more than one device/emulator
- waiting for device -
error: more than one device/emulator
Another method
Hey first of all I want to say thanks for your tutorial.
I found another method for sideloading your apps to your Wear OS watch.
It's my preferred method because you need no PC.
There is this apps called Apps2Fire it's made for sideloading apps to an Amazon fire TV, but if you enter the IP address of your watch and enable ADB over Wi-Fi you can sideload all apps installed on your phone or any .apk stored at your phone directly to your watch.
For me, this is the easiest way for sideloading, and it would be cool if you can add it to your tutorial.
Tutorial:
1. Install Apps2Fire on your Phone
2. Open the app and go to Setup,
3. Enter the IP of your watch/ or tap on network and let it search for your watch
4. Tap in the upper right corner on the Upload Symbol and chose your .apk and tap on it and then on install.
5. Enjoy
How can I extract an application installed on the watch?
hotplex said:
I came across this error when following the first option. Any advice?
error: more than one device/emulator
adb: error: failed to get feature set: more than one device/emulator
- waiting for device -
error: more than one device/emulator
Click to expand...
Click to collapse
I had the same problem - it was because my AVD was still running from Android Studio. Once I closed that and ran the command again, it worked fine.
would thet be wrong adb. most don't set a path in variables on Windows they will have issues for Windows would this be better fastboot too thanks great work glad people are working on wear
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
would thet be wrong adb. most don't set a path in variables on Windows they will have issues for Windows would this be better fastboot too thanks great work glad people are working on wear https://forum.xda-developers.com/showthread.php?t=2588979
please help! error
i tried sideloading with adb. i got the watch to connect but when i tried to install the apk i got this error:
adb: failed to install gv.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
what am i doing wrong? please help!!! thank you
lindsay
shawndak said:
I have been looking how to do this for a day now with no luck. All the other applications seem to be for early Android wear versions less than 2.0 or Android 5.1.1 or less.
Option 1 (Faster)
1: Install ADB on your computer. https://www.xda-developers.com/install-adb-windows-macos-linux/
2: Enable Developer Options on your wear watch. https://forum.xda-developers.com/android-wear/development/guide-how-to-connect-adb-wifi-t3368602
3: Make sure bluetooth is off, wifi on and connected to same network as laptop.
4: Turn on debug over wifi option in developer options and wait for it to show your IP.
5: On windows, make sure platform tools are on the main drive. Ex (C
6: Copy your APK files into the same folder.
7: Inside the folder, press shift and right click. Then press "open with CMD here or powershell"
8:Type .\adb connect 192.168.0.5:5555 (use your own IP, not the ex)
9: Once connected type .\adb install facebook.apk (type in your own APK name, not the ex)
10: Wait for success, and app should be on watch
FYI some computers do not need the .\adb, just type adb
Option 2 (Slower)
* Prerequisites:
1: Computer
2: Cord to connect your phone.
Tested and works with Lineage OS Android Nougat 7.1 and Android wear 2.7 on Verizon Wear24 watch
All the credit goes to the youtuber that created the video, I'm just passing along the information.
https://www.youtube.com/watch?v=1g77uIGxvcs
http://www.mediafire.com/file/8936ojtv5axl73g/Android+Wear+Sideloader.zip
https://www.apkmirror.com/
Follow the steps listed in the Start.bat, do not run as Admin.
The APK must be loaded into the main folder, not the app folder.
Currently installed Facebook Lite, tested and works.
Opera Mini opens but force closes after a few seconds.
Click to expand...
Click to collapse
lindser112 said:
i tried sideloading with adb. i got the watch to connect but when i tried to install the apk i got this error:
adb: failed to install gv.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
what am i doing wrong? please help!!! thank you
lindsay
Click to expand...
Click to collapse
Looks like you're trying to load an app with the wrong CPU architecture! Try to download a different arch cpu type of that app.
My Fossil Carlyle doesn't showing Wifi debugging in the dev. options. Any way to get sideload without cable working?
schuetzi13 said:
Hey first of all I want to say thanks for your tutorial.
I found another method for sideloading your apps to your Wear OS watch.
It's my preferred method because you need no PC.
There is this apps called Apps2Fire it's made for sideloading apps to an Amazon fire TV, but if you enter the IP address of your watch and enable ADB over Wi-Fi you can sideload all apps installed on your phone or any .apk stored at your phone directly to your watch.
For me, this is the easiest way for sideloading, and it would be cool if you can add it to your tutorial.
Tutorial:
1. Install Apps2Fire on your Phone
2. Open the app and go to Setup,
3. Enter the IP of your watch/ or tap on network and let it search for your watch
4. Tap in the upper right corner on the Upload Symbol and chose your .apk and tap on it and then on install.
5. Enjoy
Click to expand...
Click to collapse
awesome thanks, this seems to work...it says connected on the apps2fire app...i haven't tried to upload apk yet to watch..i have fossil gen4 sport..now to find some good apks to sideload lol
I've followed everything but when i do /adb devices it doesn't show anything and when i do /adb connect with the wifi ip address... it says unable to connect to the ip address i wrote
Thanks heaps. The first method worked for me on TicWatch Pro 3 Woohooo...
Does anyone know a tutorial on how to make an apk compatible to install on a watch please?
Smeeksmiley said:
I've followed everything but when i do /adb devices it doesn't show anything and when i do /adb connect with the wifi ip address... it says unable to connect to the ip address i wrote
Click to expand...
Click to collapse
no one has explained it properly on XDA it kind of sucks for newbies tbh
Step1: go to settings - system - about - tap build # 7 times
Step2: go to settings - developer settings - adb debug -adb wifi debug on
step3: download apk on computer
step4: go to the folder with the APK in it "Shift + right click" open powershell
step5: go to the wifi on your watch click on it - get the ip address (should be 192.168.x.xx)
Step6: powershell type: "adb connect 192.168.x.xx:5555" (your watch ip address + the port 5555)
step7: powershell type: "adb -e install appname.apk" (type in the app name where i wrote the app name)
Example:
C:\Users\Bob\Downloads> adb -e install Spotify.apk
Has anyone been able to get a gcam port working on their WearOS device?

Can't access watchface folder on my Stratos

Please excuse my ignorance here but I just received my new Stratos last week and wanted to load some new watchfaces. When I tried to drag the downloaded files to the watchface folder on the watch, it's locked and won't allow me to do so...what am I missing? Thanks in advance for any help.
What computer are you using? You need the proper MTP drivers installed fi you are running Win, or Android File Transfer for Mac. You simply connect the watch, it will mount as MTP and you can copy the files. If you have problems, try another USB port, cable or computer. As last resource, unpair and pair watch again (it will erase all data on watch).

[Guide] Wireless file transfer Pace/Stratos (workaround for no USB connection)

Requirements:
- Amazfit watch, any model, any ROM (don't need to unlock anything and it will NOT void your watch's warranty, these are simple APKs);
- PaceOne and FileManager+ by AlphaInventor on watch, any FTP client on phone or computer.
Click to expand...
Click to collapse
This works with both phone and computer, you don't need USB cable and it works both ways: you can send files to watch and retrieve files too. Don't forget to disable WiFi on watch after you are done to prevent extreme battery drain if it remains on!
----- Procedure
1. Install PaceOn and Filemanager+ by AlphaInventor on watch;
2. Configure PaceOn to turn on WiFi and start its service so screen won't go off (you can use the dim option to use less battery) and the WiFi remains on;
3. Go to FileManager and start Access from Computer (lower right option), WiFi should be on already, tap on Start Service and note the number above (IP_numberort_number);
4. On your phone or computer, use a FTP client (the same app works for Android phones, pick your favorite on iOS) to create a new Remote Access using FTP, and connect using the previous info: IP_numberort_bumber, you can set *any* name as login and password.
Now you can send and receive files wirelessly to the watch using your phone or computer. As a bonus, you can use FileManager+ also to uninstall apps directly on watch and other stuff.
----- Extra Tip: How to Setup Without USB (using WiFi only)
How to use this when USB connection doesn't work? It's not hard, but you must keep your watch screen on until you can install PaceOn. First, go to watch Settings -> Connection and connect to a 2.4GHz network, then use any scanner tool to find out what is the IP used by the watch. You must keep the screen on or the connection will drop. Once you find the IP, use adb to connect to watch:
Code:
adb connect watch_IP
where watch_IP is the actual IP used by watch (in the pics below, it's 192.168.0.26, for instance). tThen you can install PaceOn and FileManager+ normally:
Code:
adb install app_name.apk
Install PaceOn first, then use it to activate WiFi and keep screen on so the watch won't disconnect.
----- Downloads & Apps
PaceOn can be found here (please *read* the post to learn how to use it, it has pictures and it's not hard):
https://forum.xda-developers.com/sm...paceon-amazfit-pace-screen-long-want-t3700247
I am using FileManager + v1.7.1, that can be found here (newer versions may work too):
https://apkpure.com/file-manager/com.alphainventor.filemanager
You can use the same file to access the FTP server on your Android phone. For iOS, you can use FileExplorer or any other app with builtin FTP client:
https://itunes.apple.com/app/fileexplorer-file-manager/id510282524?mt=8
For computer (all platforms), I recommend FileZilla:
https://filezilla-project.org
Thanks! Lifesaving, after my USB-Connection dont Work anymore... with Installation of the Filemanager i was able to delete old MP3, to Upload new songs i can use the integrated function in the Amazifit-App, but you cant delete songs their...
Many Thanks!
My usb connection is not working on watch (Pace). So it dont connect to pc any more I have stock rom on watch. Is it possible to transfer/ install the watch faces wirelessly to watch? If yes then how? Or is there any way through which i can access the folders on watch wirelessly Please help me.
Thank you
with best regards.
Thank you very much! This worked for me in Amazfit Stratos 2 using FileManager 2.0, as 1.7.1 is no lnger available.

Install apk from Chromebook.

Hi!
I wonder if it's possible to install apk files on my Stratos from a Chromebook since I don't have a Windows PC/laptop.
1. Use adb from the terminal/command prompt (most ChromeOS devices now allow installing a Linux subsystem and then you should be able to install/run adb if it not natively available).
2. Install FileManager+ and PaceOn on watch some how, use PaceOn to keep WiFi connected, start remove access (it's actually a FTP server) in File Manager+ then use any FTP client on your ChromeBook to copy the files, then use BugJaeger app to connect to watch via WiFi and run the adb commands to install the app;
3. Install AmazMod on both phone and watch (If you can install Amazfit on Chromebook the probably you can also install AmazMod from it too).
If you have an android phone, use BugJaeger over wireless adb
https://play.google.com/store/apps/details?id=eu.sisik.hackendebug

[SOLVED] Help needed using adb to curb crazy Wi-Fi data usage by Google

Hi all,
First of all, many apologies because I imagine that my situation below has been discussed here many times. TL;DR section at the bottom.
I have been trying to use adb to set an option on my Redmi Note 5 phone, to no avail. For the background of why I need that: I have arrived yesterday at my travel destination and I've realized that the app named "Google" has used over 2.24 GB of Wi-Fi data as reported by data usage in the Security app. In less than 24 hours! I've also installed and used the app Network Connections. All of this was in an effort to control the high bandwidth speed I was seeing in the notification bar (over 100 KB/s for minutes, without interruption). I have restricted network usage for all applications on Wi-Fi as well as on mobile data, disabled Sync (all forms of sync, believe me), and done everything I could think of to prevent the huge Wi-Fi usage, including rebooting the phone each time I changed a setting. The "Test Network" tile in Security still shows that about 100% of the bandwidth usage is by "Google" app. 90% of that usage is downloads and I can't figure out what Google is downloading to my device, which I've been using for a year without ever connecting it to a Wi-Fi network, until yesterday. Somehow, on my Redmi Note 5 running MIUI 11, "Wi-Fi" is equated to "unlimited network, with no cap, and no reason to be reasonable".
The root problem is that the Wi-Fi I'm connecting to is metered, and apparently, MIUI has removed the underlying Android option to set a Wi-Fi connection as metered. The solution, as I've discovered online is to issue an adb command (cmd netpolicy set metered-network <name of network> true).
Therefore, I head to using adb. Many pages online deal with enabling Developer Options and US debugging, and I had already done just that in the past.
However, in the instructions on using adb, each such page speaks at a certain point in the list of instructions of a dialog box that is supposed to show up on the phone ("Allow USB debugging?" with something about a computer fingerprint), but it never showed up on my device. The command adb devices does not list anything, not even in a command line opened as an administrator. The adb executable that I'm using is from the Android Platform Tools (platform-tools_r29.0.5-windows.zip).
Many forum pages hint to a missing driver. But I can easily plug the phone via USB and download files and photos from the phone to the computer. If it was a driver issue, shouldn't I have problems doing file transfers?
Moreover, each time I plug the phone via USB, I see a notification from "Android system" stating "USB debugging connected" followed by "Tap to turn off USB debugging", which tells me that USB debugging is working.
TL;DR
adb devices lists nothing when my Redmi Note 5 is connected via USB. I guess it's a driver issue. How can I get the appropriate driver? I would like to avoid downloading sketchy driver packs from random websites such as the ones from xiaomi advices (e.g. the "driver" for Redmi Note 5 was uploaded on October 5, 2014!!!).
Thank you.
do you already set enable usb debugging on developer setting?
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
EriecTan said:
do you already set enable usb debugging on developer setting?
Click to expand...
Click to collapse
Yes. Both the plain "USB debugging" and the "USB debugging (Security settings)".
openCode168 said:
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
Click to expand...
Click to collapse
Well, I have installed PC Suite 2.2.0.7032 to no avail: when I connect the phone via USB, a PC suite window shows up and says "Looks like you're missing some drivers... Make sure you're this system's administrator", which I am. I can't believe that in this day and age it is so difficult to find official drivers for a device that's been sold by the thousands.
Thanks for your help.
OMFG, I did it!
Before I say anything more: I have uninstalled Mi PC Suite.
The solution is in the mode that is active in the notification shade once the phone is connected via USB to the computer. In the notification shade, there was a notification from Android system that read "Charging this device via USB, tap for more options". Once I tapped and chose "File transfer", things changed!
At the same time, the Device Manger had been opened on the computer an I was seeing a yellow overlay icon over "SDM636-MTP _SN:xxxxx" in category "Other devices". As soon as I chose "File transfer", the device "SDM636-MTP" disappeared and a new category "Android Phone" showed up, along with a subcategory that read "Android Composite ADB interface". The "ADB" in the title prompted me to try using adb. That's when it all worked! Here is a transcript of the command line session, during which at some point I got (on the phone) a dialog box about authorizing the computer, also showing an RSA fingerprint. I obviously authorized the computer :
Code:
Microsoft Windows [version 6.3.9600]
(c) 2013 Microsoft Corporation. Tous droits réservés.
D:\Programs\adb>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
fce3c2e3 unauthorized
D:\Programs\adb>adb devices
List of devices attached
fce3c2e3 device
D:\Programs\adb>adb shell
whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;none
whyred:/ $ cmd netpolicy set metered-network "WI-FI HOME" true
255|whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;true
whyred:/ $
So the problem was not about drivers like I thought and complained about, it was about choosing the appropriate mode once the phone is connected to a computer via USB.
I'll see now whether setting the Wi-Fi networks as metered will be enough to stop Google from using up the data allowance.
EDIT: Setting the network as metered did the trick: what was previously hovering well above 100 to 200 KB/s is now around 0.05 - 3.00 KB/s, due this time not to "Google" but to "Google Services Framework" and "Google Play Store"

Categories

Resources