Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Release notes
This build includes a totally new kernel and Amlogic code based on their latest SDK, and I took the chance to get rid of Amlogic DVB drivers and use those from WeTek Play's OpenELEC build; by doing this I am able to run DVBAPI apps like Tvheadend.
Kodi Live TV support under Android was one of the most requested features, this experimental build allows you to run Kitkat (CyanogenMOD 11) or Lollipop (CyanogenMOD 12 or Android TV) and Kodi Live TV (WeTek Theater is no longer supported with the provided drivers).
The new 3.10 kernel brings OMX support as well (Android libstagefright media decoding), while Amlogic's prebuilt libraries work very good on KitKat they don't work at all with Lollipop.
Just to be sure to have a good media experience use Kodi, at the end of the post you will find latest stable official Kodi packed in a flashable zip and in the second post you will find a link to a modified version that should give a better experience on the WeTek device.
Now I will give you some details on how to configure Tvheadend, if you already know what to do you can skip this section.
Tvheadend will run automatically at boot and you can access to it from a web browser (even from a different device, you are not forced to do it from the box) at http://wetek_ip_address:9981
From this WebUI click "Configuration" -> "DVB Inputs" -> "Networks" and add a new Network according to the type of tuner you have (for example I created a DVB-S network called "Hotbird" and assigned the E13.0 pre-defined muxes, just pay attention that they are not bleeding edge updated so if you don't find a channel you might have to insert manually the transponder by looking at frequencies on sites like kingofsat or lyngsat).
After that go to "TV Adapters", click the link with a folder icon showing your adapter's name (if you're running the dual DVB-S2 tuner you will see two of them, #1 is the input closer to the edge of the box, while #0 the one closer to the rear usb ports), and click "Enabled", configure the eventual parameters (DiseqC, Unicable, etc.) and save the settings.
Go to the option right under the adapter name, assign it to the network that you have created and configure the eventual parameters.
Now go back to "Networks", after a couple of minutes you should see the "Scan Q length" lowering its value, when in reaches 0 everything has been scanned and you can proceed mapping the channels from "Services" section.
For further instructions, here you can find a tutorial to show you how to configure the DVB-T/C tuner, and here one for the DVB-S tuner.
Before leaving the configuration go to "Recordings" and set a "Recording System Path" pointing it to your external storage (on my roms it will be "/storage/sdcard1" for the MicroSD, "/storage/usbdisk0" for the lower rear usb port, "/storage/usbdisk1" for the upper rear usb port and "/storage/usbdisk2" for the side usb port).
Not doing that will drive Kodi's Tvheadend client plugin crazy trying to determine the available space for recordings.
Now you can launch Kodi, go to its settings, enable Live TV and select the "Tvheadend backend".
Remember that this is still something EXPERIMENTAL
Like the other Lollipop buils, remember, this is not a bug, but a consequence of the switch to art from dalvik: first boot, updates and apps installation will take longer; this happens because art compiles the apk and does not work like dalvik that was using a just-in-time approach (so expect almost 10 minutes for the first boot and future upgrades)
First install instructions
* As really first thing get this CWM recovery, unrar it and copy "recovery.img" to a MicroSD.
* Power off your device and unplug the AC power cord.
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Plug the AC power cord while you keep pressed the little reset pinhole (located on the bottom of the device) for 10 seconds (just count slowly to ten and it will be good).
* Once the device has booted to recovery perform a factory reset and flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy CyanogenMOD.
Update instructions
* If you're coming from the "regular", not "experimental" builds, please follow the "First install instructions"
* Get the latest available ROM and GAPPS version from the links below and copy them to a MicroSD card.
* Now insert the MicroSD card in your STB.
* Enable "Developer options" following this tutorial and from it enable the "Reboot to recovery" option.
* Bring up power menu by keeping pressed the power button on the STB for a couple of seconds (or pushing F4 if you have a keyboard plugged in) and select "Reboot -> recovery".
* Once the device has booted to recovery flash the ROM's zip for first followed by the GAPPS zip.
* Reboot and enjoy your updated CyanogenMOD.
Downloads
* ROM (CM12) 2015-03-20
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-03-20
* GAPPS (Android TV) 2015-01-30
* ROM (CM11) 2015-04-06 - Real 1080p output (r1)
* GAPPS 2014-06-06 (LITE)
* Kodi 14.1 "Preinstall"
Misc tips
* If you wanna start Kodi at boot go to "Developer options" and enable the last entry called "Start Kodi at boot"
* There are some keyboard shortcuts: F1 (Home), F2 (Menu), F3 (App switch) and F4 (Power menu) and some CEC remote shortcuts: Red (Power off the device), Green (Home), Yellow (Menu) and Blue (Search).
* By enabling "Google remote support" in "Other" section of "Network" configuration you will be able to control your device from your Android smartphone / tablet by using this app on it.
* When an app forces the portrait orientation, the default behavior is to simulate a portrait / phone-like UI adding black bars to the sides (an example is Antutu when it runs the benchmark, or Box.com). If you prefer to have a landscape stretched UI flash this zip. To revert to the default behavior flash this one instead.
Note that the setting will persist even if you upgrade the ROM so you have to flash that zip only once.
* Once you have configured your OSCam reader, set-up Tvheadend this way.
Real 1080p output (optional zip for CM11)
On Android Amlogic MX SOC uses a 1280x720 framebuffer coupled with a scaler to do the up/down scaling.
They did it for a good reason, 720p resolution has half the pixels of the 1080p one so the UI will be snappier and 3D performance will be better but if you don't care about that and you just wanna the best image quality (I noticed the scaler gives me a weird motion when watching sports) you can flash that optional zip.
Once flashed if you wanna change resolution go to Android Display settings, set your resolution and reboot the device (this step is required because some stuff has to be set at boot because Android is not meant to change resolution while it's running).
I didn't do it for Lollipop builds because it runs already slower than Kitkat, adding this mod might be too much
Since you have this option (WeTek Play is the only MX device that allows you to do that) I would give it a try, if you have a good TV set you will clearly see the difference.
Kodi 14.2 WeTek_mod_v1
This is a Kodi build that includes some patches not included upstream that will improve (hopefully) your overall experience.
Since it's been signed with different keys respect those from Kodi build server you won't be able to install it over the older Kodi but you'll have to uninstall it.
Take a backup of /sdcard/Android/data/org.xbmc.kodi folder before uninstalling or Android will delete it and you'll lose your configuration; restore it after installing the new APK.
Download
You can use OE's /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<cachemembuffersize>20971520</cachemembuffersize>
</network>
<samba>
<clienttimeout>30</clienttimeout>
</samba>
<network>
<readbufferfactor>4.0</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>5</minvideocachelevel>
<minaudiocachelevel>20</minaudiocachelevel>
</pvr>
</advancedsettings>
or (this is what I'm using)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<buffermode>1</buffermode>
<cachemembuffersize>31457280</cachemembuffersize>
<readbufferfactor>10</readbufferfactor>
</network>
<gui>
<algorithmdirtyregions>0</algorithmdirtyregions>
</gui>
</advancedsettings>
External disk spindown for WeTek Play
Flash this zip from recovery, once booted to android use a root capable file explorer (like Solid Explorer for example) and edit "/system/etc/spindown.conf" to fit your needs.
The default configuration is set-up to spin down "sda" disk after 3600 seconds (60 minutes) using sg3-tools.
You don't need to flash the zip again if you do a rom update because I've added the addon.d backup script.
Note: your drive have to ne able to be set to sleep using "sg_start --stop /dev/block/$disk", I've tried it with 3 drives, 2 WDs and 1 Seagate and it worked.
Debian chroot
As very first thing you have to set-up a MicroSD card with two primary partitions, the first one must be formatted in FAT32, the second one can be left unformatted because the "sdcardfiles" zip will format it (I suggest you to give at least 1GB of space to the secondary partition).
After that grab the two zips: wetek-debian-chroot-sdcardfiles.zip and wetek-debian-chroot-systemfiles-rc1.zip and copy them (together with CWM's recovery.img) to the FAT32 partition of the MicroSD (the primary one).
Boot to recovery and flash the two zips (the order doesn't matter).
How to actually use it:
The "systemfiles" zip will add an helper file that I called "debian-chroot", together with the init.d script it will set up the chroot at boot and run the configured services (as a template the /system/xbin/debian-chroot file includes the execution of dropbear daemon, so you can use it as starting point for your own stuff).
To access Debian you can just type as root from terminal emulator / serial console / adb over network "debian-chroot chroot", othwerise you can access using an SSH client to the configured Dropbear SSH server that is listening on port 2222.
There are two default users: 'root' (pwd: wetek) and a regular user 'wetek' (pwd: wetek), both can be used to access to the ssh server.
* ROM 2015-01-30
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-01-30
* GAPPS (Android TV) 2015-01-30
In the "regular" CM12 build added some things I had forgotten when upgrading the device tree from the old to the new kernel (the most important, I had forgotten to mkdir the paths for the hard drives mounting).
Included the new tvheadend posted in OpenELEC section (the one with the different decsa algorithm)
Added Android TV build and just a tip for the first boot of it...
Don't change the language, use the default english already selected (don't know why but changing language is VERY sluggish/laggy), when you're doing configuring it you can change it to your preferred one in Android's settings.
Another thing, if the screen stays black after allowing or denying the "Network location" option (the last step of the wizard) for more than 10 seconds just bring up power menu and perform a reboot, the Wizard will kick in again, you'll have to just click continue because everything is configured and it will work. I don't know why it acts like this sometimes!
Guys if you experience some freezes of the box after running for certain time an encrypted channel (I noticed that it happens to me between 45/60 minutes after tuning to such channels) it might be caused by the new decsa library, it looks like it has a memory leak.
I will revert to the older binary, in the meantime you can flash this zip to go back to the one from the older build.
After reverting I'm tuned on an encrypted channel since an hour and I don't see any weird memory issue
Oh, guys, I forgot to mention that in this build I've enabled Amlogic's "anymote" support (the backend to be remotely controlled use Google TV remote app).
To use it go to "Network -> Other" options in Android's settings and enable "Google TV Remote support", after that install this app on your Android phone/tablet and you'll be able to use it as a remote.
PS: I didn't have much luck running the "Google TV Remote" app from the Play Store, it wouldn't find the device at all, maybe they are enforcing a private key handshake like in newer Google Cast Receiver to be able to run it only on official Google TV devices.
PPS: remote audio input doesn't work, the Amlogic's anymote throws an exception regarding a class not found. Can't do much about that since it comes as a precompiled APK (and I already had to do some smali hack to be able to run it on Lollipop)
* ROM (CM12) 2015-01-31
* GAPPS 2015-01-07 (LITE)
* ROM (Android TV) 2015-01-31
* GAPPS (Android TV) 2015-01-30
* ROM (CM11) 2015-01-31
* GAPPS 2014-06-06 (LITE)
Lollipop ROMs:
* Reverted tvheadend to the older version that doesn't suffer of memory leak
* Introduced a workaround to prevent Netflix from using OMX
* Updated upstream sources
Kitkat ROM:
Added CM11 based on the new kernel. It's generally faster than Lollipop, as I have said ART probably is too much for the MX
I haven't added the extra stuff to Android settings so I'm including the ugly MboxSettings app, I have given more love to Lollipop, I have to admit it, in case if you people prefer this rom I can start customizing it more.
I suggest you to install SuperSU from Play Store, let it update the "su" binary choosing the normal way and converting it into a system app + installing the backup script to let it survive rom updates. This because CM11's SuperUser doesn't work nicely with the way Kodi request root rights.
Beside the same F1/F4 shortcuts as the Lollipop roms above, there's a further shortcut with F8 to toggle expanded desktop mode.
* ROM (CM11) 2015-02-01
* Added the most important things of MboxSettings to Android settings (display resolution, overscan, cec, digital audio and google tv remote).
* Added an entry, accessible through developer settings (at the very end of the list), to enable the autostart of Kodi at boot
* ROM (CM11) 2015-02-02
* added the new suspension method (I will quote my previous post to describe it)
ChristianTroy said:
Guys I've been trying a new suspension method, it's a better solution IMHO.
I'm going to use Android's capabilities to prevent the device from entering suspension (with wakelocks) to only let the kernel turn off everything but without really entering suspension, something like flashing the "wetek-disable-shutdown.zip" that you find in the second post of all my other rom's threads.
But I did a modification in the kernel: it will turn the power led blue/red if the display is on/off so you'll know if you actually turned it off. I decided to mantain on the eventually enabled wifi or eth led so you'll see if you have connection or not.
This thing is very useful if you're going to program a recording in tvheadend, otherwise the device won't wake from sleep (at least not with easy work without using Android's AlarmManager to create a new wake up task) and in this way the device won't have to perform boot from scratch once you put it to sleep, but it will be instantly on again.
It will consume a little bit more of power though (haven't run much tests but since this device when it's on runs at 7w, I guess it will be <5w) but I think that many of you keep it running all the time, in this way it's like if it was running but just with the output turned off
Click to expand...
Click to collapse
* corrected an unwanted (by me) behavior of Amlogic's android ethernet service that was putting off the interface when the display was being turned off. If you were connected using eth you would find yourself without network with the new suspension method... if for some reason you want your eth to be turned off when the display is off add "ro.screen_off.disable_ethernet=true" to /system/build.prop
* disabled google setup wizard that was causing a black screen on first boot because it was invoking the AOSP version of setWifiEnabled instead of CM's one with AppOps support
* enabled the execution of a boot service to set up the remote (you couldn't power off the device using the remote before this build) that I had forgotten to set up after moving to the new kernel branch
ps: let me know what you think about this new suspension method, personally I do really love it and was thinking about that since quite some time
Debian chroot
As very first thing you have to set-up a MicroSD card with two primary partitions, the first one must be formatted in FAT32, the second one can be left unformatted because the "sdcardfiles" zip will format it (I suggest you to give at least 1GB of space to the secondary partition).
After that grab the two zips: wetek-debian-chroot-sdcardfiles.zip and wetek-debian-chroot-systemfiles.zip and copy them (together with CWM's recovery.img) to the FAT32 partition of the MicroSD (the primary one).
Boot to recovery and flash the two zips (the order doesn't matter), after each ROM upgrade you'll have to flash only "wetek-debian-chroot-systemfiles.zip" (the other one is just to set up Debian, flash it in case you mess up the system and wanna start from scratch).
How to actually use it:
The "systemfiles" zip will add an helper file that I called "debian-chroot", together with the init.d script it will set up the chroot at boot and run the configured services (as a template the /system/xbin/debian-chroot file includes the execution of dropbear daemon, so you can use it as starting point for your own stuff).
To access Debian you can just type as root from terminal emulator / serial console / adb over network "debian-chroot chroot", othwerise you can access using an SSH client to the configured Dropbear SSH server that is listening on port 2222.
There are two default users: 'root' (pwd: wetek) and a regular user 'wetek' (pwd: wetek), both can be used to access to the ssh server.
Regarding the random black screen on channel change can anyone try this advancedsettings.xml (location on Android is "/sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/") and tell me if it acts better? I didn't have any black channel since using it (3 days) but I don't wanna that it's just a lucky coincidence
Code:
<advancedsettings>
<network>
<buffermode>1</buffermode>
<cachemembuffersize>52428800</cachemembuffersize>
<readbufferfactor>10</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>10</minvideocachelevel>
<minaudiocachelevel>15</minaudiocachelevel>
</pvr>
</advancedsettings>
Regarding the XMLTV EPG I set up xmltv to use tv_grab_it for some channels (47 to be precise, and it takes ~1 hour per fetched day with the --slow parameter that includes descriptions) and fix it using tv_sort on the generated output because some channels don't have a stop time and this won't let tvheadend add them to its database.
I used a Debian chroot in my Synology NAS and set up a crontab job in Synology's crond to execute a script, located at '/root/xmltv.cron' with this content:
Code:
#!/bin/sh
# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"
# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`
chroot ${CHROOTTARGET}/ su -c 'tv_grab_it --output /volume1/homes/alan/www/tvguide_wip.xml --days 3 --quiet --slow --cache-slow && tv_sort --output /volume1/homes/alan/www/tvguide.xml /volume1/homes/alan/www/tvguide_wip.xml' alan
After that I enabled "Web Station" for the users and I can access my EPG from "http://NAS_IP/~alan/tvguide.xml" and use this URL as w*g*e*t parameter for tv_grab_file
This is the result:
If you install on your Play the Debian chroot that I posted yesterday you can practically do the same, just install xmltv on it running
Code:
sudo aptitude install xmltv
(or, if you know what you're doing, compile it from sources installing the required dependencies, some perl modules)
Install a cron daemon like "vixie-cron" and add it to "/system/xbin/debian-chroot" in the "start_services" function (like the template that runs the SSH server).
Set it up, save the XML output somewhere like "/home/wetek/tvguide.xml" and replace the "w*g*e*t" line in tv_grab_file with "cat /storage/debian/debian-chroot/home/wetek/tvguide.xml"
* ROM (CM12) 2015-02-07
* ROM (Android TV) 2015-02-07
Both Lollipop roms have been updated to match features/fixes of latest CM11 builds, plus upstream sources have been updated
New builds:
* ROM (CM12) 2015-02-14
* ROM (Android TV) 2015-02-14
* ROM (CM11) 2015-02-14
* OSCam (r10566)
Oscam zip for these builds, just flash it from recovery, when booted into Android access to http://wetek_ip:8888 and add your server (remember to add it to group 1, that is the group assigned to the dvbapi user).
Open TVH configuration page and in "CAs" section add a new "CAPMT (Linux DVBApi)" with these content:
ps: this oscam has Smargo (libusb) and PCSC support
tvh-3.9.2509_oscam-r10566_android-wetekplay.zip
New Tvheadend built from sources (updated this morning), no more using OE's libraries but with another approach instead. I've built it with some enhancements in CFLAGS for the cortex-a9 cpu.
OSCam included, if you set it up the way I explained yesterday you're good to go, otherwise just configure it that way
ps: it looks like this version recognizes the hybrid c/t tuner as c only so if you need dvb-t keep using the one you're already using
* ROM (CM12) 2015-02-22
* ROM (Android TV) 2015-02-22
* ROM (CM11) 2015-02-22
tvh-3.9.2515_oscam-r10607_android-wetekplay.zip
Test zip that will change the following things:
- update tvh to latest sources (synced this morning)
- update oscam to r10607
- update wetekdvb.ko with the one from OE 5.0.4
PS: now the hybrid tuner is recognized, I had to change a couple of things
* ROM (CM12) 2015-03-05
* ROM (Android TV) 2015-03-05
* ROM (CM11) 2015-03-05
If you're upgrading from a build where you were running oscam, go to "mounts and storage -> format /system" before flashing the new stuff (or manually delete "/system/addon.d/80-oscam.sh" if you know what you're doing).
Changes:
* updated upstream code
* updated WeTek DVB kernel driver
* updated Tvheadend
* added OSCam (no support for it, it's a "grey area" thing)
* fixed a bug where the resolution was resetted to 720p @ 60hz under certain conditions (like when swapping HDMI input in some TVs), and use 1080p @ 50hz as fallback resolution
In case you wanna try a test zip with brand new OSCam and Tvheadend built with Android toolchain (NDK) flash THIS zip on top of today's build. I'd really like some reports about any crash using the native binaries.
Kodi 14.2 BETA 1 apk
This is a Kodi 14.2 BETA 1 based build with two patches added that add support for automatic frame rate switch (you have to enable it in settings) and that should behave better with the black screen bug.
Since it's been signed with different keys respect those from Kodi build server you won't be able to install it over the older Kodi but you'll have to uninstall it.
Take a backup of /sdcard/Android/data/org.xbmc.kodi folder before uninstalling or Android will delete it and you'll lose your configuration; restore it after installing the new APK.
Download
I'm using this /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/advancedsettings.xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<advancedsettings>
<network>
<cachemembuffersize>20971520</cachemembuffersize>
</network>
<samba>
<clienttimeout>30</clienttimeout>
</samba>
<network>
<readbufferfactor>4.0</readbufferfactor>
</network>
<pvr>
<minvideocachelevel>5</minvideocachelevel>
<minaudiocachelevel>20</minaudiocachelevel>
</pvr>
</advancedsettings>
* ROM (CM12) 2015-03-10
* ROM (Android TV) 2015-03-10
* ROM (CM11) 2015-03-10
- CEC improvements (codesnake's OE fix)
- Mapped CEC red/green/yellow/blue buttons to power/home/menu/search
- upgrade tvheadend and oscam with the native (android ndk) ones
- updated dvb code (same code as latest OE)
- few other minor things at kernel level
- updated upstream sources
Notes: run it with Kodi that I posted yesterday (and that you can find in the second post) with Aeon Nox skin + Live TV mod and you will get a very good experience, specially if using CM11 or, if you don't mind it being a bit more laggy, ATV
* ROM (CM12) 2015-03-11
* ROM (Android TV) 2015-03-11
* ROM (CM11) 2015-03-11
Fixed a problem with the dual tuner and the new bootloader (the one flashed by NAND version of OE and latest WeTek OS)
I created these utilities to help people complete some tasks faster/easier without having to resort to ADB or other methods. The purpose of these programs is to assist the user fine tune their watch & add functionality.
Amazfit PACE Tuner (Windows)
Amazfit PACE Tuner (Android APP for Watch)
FEATURES
PACE Watch APP
* Display enabled Keyboards on watch
* Switch between Minuum Keyboard & Stock Huami
* Test typing keyboard area
* Control WiFi & Bluetooth
PACE Tuner Windows utility
* Check for ADB devices
* Install Minuum Keyboard on watch
Since I am not the author of the Minuum Keyboard I will not be including it in the package (sorry). You will need to search online (plenty of places to download it from) and download the APK.
Download Minuum-Wear.apk and place it in the same directory as the PACE Windows utility. Make sure the naming of the file is as exactly mentioned earlier in bold.
Click on the "Install Minuum" button in the Windows utility and wait for the install to complete.
* Display PACE watch data (device name & total km's ran)
* Display Watch and paired phone Bluetooth Information
Tweaks
* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)
* Toggle between show battery % screen while charging or the watchface (you may have to wake the screen once after making changes to see them)
* # Experimental # Enable find iPhone feature from watch (works by default on Android, so only use for iPhone users)
* # Experimental # Enable Haptic feedback (app needs to support this for it to work)
* Super Brightness - Sets watch to maximum allowed brightness. Manual 'L5' allows for a value of '180' in the settings. By enabling this option your setting will be '255' (maximum allowable).
* You can force restart your watch by double clicking on the PACE watch picture (typically bottom-right)
* Kill all ADB connections (in case Windows get confused or something)
I currently own and test the utilities on a Windows 7 (x64) based machine only and a PACE International version on stock firmware v1.3.6d
Downloads
https://drive.google.com/open?id=1Ho8RK1Fh858zX-aiWlNugNt8hg0B1XRg
File descriptions:
Amazfit PACE Tuner package vx.x [A zipped file that contains both the Windows & PACE apk utilities]
Amazfit PACE Tuner (Windows) vx.x.exe [The Windows utility - It uses ADB commands to perform various tasks on your watch]
AmazfitPACE_Tuner.apk [The PACE/Android utility which will be installed on your watch - USE THE WINDOWS UTILITY ABOVE TO INSTALL - DO NOT TRY TO SIDELOAD!]
Installation
-* Disclaimer *-
I am not responsible for anything bad that happens to your watch, your PC, or anything else bad that happens to you in direct or indirect relation to using this utility package. You are solely responsible for your actions.
Now that we got that out of the way...
PC
==
1. Make sure you only have ONE Android device connected to your PC (the PACE watch) and it is turned on!
2. Make sure you have extracted the following in the same folder:
A. Amazfit PACE Tuner (Windows).exe
B. Amazfit PACE Tuner.apk
C. Amazfit PACE Tuner Release Notes.TXT
2. Run the Amazfit PACE Tuner (Windows) utility
3. Click on the "Check for ADB devices" button and wait to see in the status window for one device to show up. If no devices show up, your watch may not be connected to your PC properly. If you see an error try click the button once more.
4. You can now click on the "Install PACE Tuner" button to install the APK utility on the watch.
@@@ Product Compatibility @@@
Amazfit PACE watch (1612) [Tested]
Amazfit PACE watch (1602) [Possible]
Stratos [Possible]
@@@ Platform compatibility @@@
Vista, W7
### The Windows utility version requires the .NET Framework v4.5 (minimum) to work ###
You may download .NET from here: http://www.microsoft.com/en-au/download/details.aspx?id=30653
RELEASE NOTES
^^^ ANDROID APP ^^^
v1.1
=====
* WiFi and Bluetooth toggle switches package
* Display version at bottom of app
v1.00
=====
* First release
&& Known bugs &&
None
============================================
============================================
^^^ Windows Utility ^^^
v1.2
=====
* Added Legends for Experimental and Rooted features
* Tweaks panel
> Renamed battery status screen to better reflect what it does
> Fixed some Tips descriptions when hovering mouse cursor
> Added Find iPhone feature (experimental) for similar functionality already enabled for Android
> Added Haptic Feedback control (vibrations need to be enabled in app to work)
> Added Super Brightness option (higher than Level 5 on watch)
v1.1
=====
* Optimised UI
* Introduced exception capturing/avoiding in code
* PACE Watch data panel
> Watch name
> Total KM's walked/run
* Bluetooth panel
> Bluetooth MAC address
> BT name
> Paired device's BT MAC address
* Tweaks panel
> Allow 3rd party software installation
> Toggle charging screen while on dock (show clock/watchface instead)
* Added reset ADB button
* Implemented Watch restart on double-click of watch picture (bottom right)
* Disabled Minuum Keyboard button for this version
v1.01
=====
Fixed app overwrite (for upgrades)
v1.00
=====
* First release
&& Known bugs &&
None
Frequently asked questions
Q: I am trying to launch the utility on the watch but I am getting errors/exceptions.
A: You have to use the Windows PACE Tuner utility to install the APK since it elevates privileges required for the app to run properly. If you try to simply sideload it it will fail!
Q: I have some great ideas or need more modifications - can you please do them asap?
A: Unfortunately for you I am not a 'proper' developer. I do this as a hobby on my (limited) spare time, so I can't commit to time or my abilities to be able to do what you imagine. Your ideas are of course welcome - I will do my best, but I will do it at my time.
XDA:DevDB Information
Amazfit PACE Tuner, Tool/Utility for the Smart Watches
Contributors
darkguset, darkguset
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2018-04-08
Created 2018-04-08
Last Updated 2018-04-08
darkguset said:
I created these utilities to help people complete some tasks faster/easier without having to resort to ADB or other methods. The purpose of these programs is to assist the user fine tune their watch & add functionality.
Amazfit PACE Tuner (Windows)
Amazfit PACE Tuner (Android APP for Watch)
FEATURES
PACE Watch APP
* Display enabled Keyboards on watch
* Switch between Minuum Keyboard & Stock Huami
* Test typing keyboard area
* Control WiFi & Bluetooth
PACE Tuner Windows utility
* Check for ADB devices
* Install Minuum Keyboard on watch
Since I am not the author of the Minuum Keyboard I will not be including it in the package (sorry). You will need to search online (plenty of places to download it from) and download the APK.
Download Minuum-Wear.apk and place it in the same directory as the PACE Windows utility. Make sure the naming of the file is as exactly mentioned earlier in bold.
Click on the "Install Minuum" button in the Windows utility and wait for the install to complete.
* Display PACE watch data (device name & total km's ran)
* Display Watch and paired phone Bluetooth Information
Tweaks
* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)
* Toggle between show battery % screen while charging or the watchface (you may have to wake the screen once after making changes to see them)
* # Experimental # Enable find iPhone feature from watch (works by default on Android, so only use for iPhone users)
* # Experimental # Enable Haptic feedback (app needs to support this for it to work)
* Super Brightness - Sets watch to maximum allowed brightness. Manual 'L5' allows for a value of '180' in the settings. By enabling this option your setting will be '255' (maximum allowable).
* You can force restart your watch by double clicking on the PACE watch picture (typically bottom-right)
* Kill all ADB connections (in case Windows get confused or something)
I currently own and test the utilities on a Windows 7 (x64) based machine only and a PACE International version on stock firmware v1.3.6d
Downloads
https://drive.google.com/open?id=1Ho8RK1Fh858zX-aiWlNugNt8hg0B1XRg
File descriptions:
Amazfit PACE Tuner package vx.x [A zipped file that contains both the Windows & PACE apk utilities]
Amazfit PACE Tuner (Windows) vx.x.exe [The Windows utility - It uses ADB commands to perform various tasks on your watch]
AmazfitPACE_Tuner.apk [The PACE/Android utility which will be installed on your watch - USE THE WINDOWS UTILITY ABOVE TO INSTALL - DO NOT TRY TO SIDELOAD!]
Installation
-* Disclaimer *-
I am not responsible for anything bad that happens to your watch, your PC, or anything else bad that happens to you in direct or indirect relation to using this utility package. You are solely responsible for your actions.
Now that we got that out of the way...
PC
==
1. Make sure you only have ONE Android device connected to your PC (the PACE watch) and it is turned on!
2. Make sure you have extracted the following in the same folder:
A. Amazfit PACE Tuner (Windows).exe
B. Amazfit PACE Tuner.apk
C. Amazfit PACE Tuner Release Notes.TXT
2. Run the Amazfit PACE Tuner (Windows) utility
3. Click on the "Check for ADB devices" button and wait to see in the status window for one device to show up. If no devices show up, your watch may not be connected to your PC properly. If you see an error try click the button once more.
4. You can now click on the "Install PACE Tuner" button to install the APK utility on the watch.
@@@ Product Compatibility @@@
Amazfit PACE watch (1612) [Tested]
Amazfit PACE watch (1602) [Possible]
Stratos [Possible]
@@@ Platform compatibility @@@
Vista, W7
### The Windows utility version requires the .NET Framework v4.5 (minimum) to work ###
You may download .NET from here: http://www.microsoft.com/en-au/download/details.aspx?id=30653
RELEASE NOTES
^^^ ANDROID APP ^^^
v1.1
=====
* WiFi and Bluetooth toggle switches package
* Display version at bottom of app
v1.00
=====
* First release
&& Known bugs &&
None
============================================
============================================
^^^ Windows Utility ^^^
v1.2
=====
* Added Legends for Experimental and Rooted features
* Tweaks panel
> Renamed battery status screen to better reflect what it does
> Fixed some Tips descriptions when hovering mouse cursor
> Added Find iPhone feature (experimental) for similar functionality already enabled for Android
> Added Haptic Feedback control (vibrations need to be enabled in app to work)
> Added Super Brightness option (higher than Level 5 on watch)
v1.1
=====
* Optimised UI
* Introduced exception capturing/avoiding in code
* PACE Watch data panel
> Watch name
> Total KM's walked/run
* Bluetooth panel
> Bluetooth MAC address
> BT name
> Paired device's BT MAC address
* Tweaks panel
> Allow 3rd party software installation
> Toggle charging screen while on dock (show clock/watchface instead)
* Added reset ADB button
* Implemented Watch restart on double-click of watch picture (bottom right)
* Disabled Minuum Keyboard button for this version
v1.01
=====
Fixed app overwrite (for upgrades)
v1.00
=====
* First release
&& Known bugs &&
None
Frequently asked questions
Q: I am trying to launch the utility on the watch but I am getting errors/exceptions.
A: You have to use the Windows PACE Tuner utility to install the APK since it elevates privileges required for the app to run properly. If you try to simply sideload it it will fail!
Q: I have some great ideas or need more modifications - can you please do them asap?
A: Unfortunately for you I am not a 'proper' developer. I do this as a hobby on my (limited) spare time, so I can't commit to time or my abilities to be able to do what you imagine. Your ideas are of course welcome - I will do my best, but I will do it at my time.
XDA:DevDB Information
Amazfit PACE Tuner, Tool/Utility for the Smart Watches
Contributors
darkguset, darkguset
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2018-04-08
Created 2018-04-08
Last Updated 2018-04-08
Click to expand...
Click to collapse
Nothing happens after clicnkg to check adb...
and adb is working on regular shell
eteles said:
Nothing happens after clicnkg to check adb...
and adb is working on regular shell
Click to expand...
Click to collapse
Could be because another service is already using ADB. Try hitting the big red "RESET ADB" button on the top right, wait a few seconds then try the "Check" again
It doesn't work... And pacefied ROM auto installation doesn't work either... It's probably the same issue...
Don't know why... There's no service running adb... Manual installation works for pacefied Rom, but you do not have a manual procedure...
eteles said:
It doesn't work... And pacefied ROM auto installation doesn't work either... It's probably the same issue...
Don't know why... There's no service running adb... Manual installation works for pacefied Rom, but you do not have a manual procedure...
Click to expand...
Click to collapse
Are you running the app from a folder with a patch that includes spaces, like "c:\users\my name\app"? Try moving the app to C:\ and make sure you have systemwide adb (adb.exe path is includes in $PATH).
lfom said:
Are you running the app from a folder with a patch that includes spaces, like "c:\users\my name\app"? Try moving the app to C:\ and make sure you have systemwide abd (adb.exe path is includes in $PATH).
Click to expand...
Click to collapse
Good point! If you have not declared the paths in Windows, calling adb commands from other folders will not work. Let us know if you need help with the declaration.
I had to move the program to "c:\adb" folder to get it to work. Then it worked fine. Enabling "* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)" allowed me to be able to update Watch Droid Assistant through the watch. Thanks for the program!
danbest82 said:
I had to move the program to "c:\adb" folder to get it to work. Then it worked fine. Enabling "* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)" allowed me to be able to update Watch Droid Assistant through the watch. Thanks for the program!
Click to expand...
Click to collapse
You are welcome!
I created these utilities to help people complete some tasks faster/easier without having to resort to ADB or other methods. The purpose of these programs is to assist the user fine tune their watch & add functionality.
Amazfit PACE Tuner (Windows)
Amazfit PACE Tuner (Android APP for Watch)
FEATURES
PACE Watch APP
* Display enabled Keyboards on watch
* Switch between Minuum Keyboard & Stock Huami
* Test typing keyboard area
* Control WiFi & Bluetooth
PACE Tuner Windows utility
* Check for ADB devices
* Install Minuum Keyboard on watch
Since I am not the author of the Minuum Keyboard I will not be including it in the package (sorry). You will need to search online (plenty of places to download it from) and download the APK.
Download Minuum-Wear.apk and place it in the same directory as the PACE Windows utility. Make sure the naming of the file is as exactly mentioned earlier in bold.
Click on the "Install Minuum" button in the Windows utility and wait for the install to complete.
* Display PACE watch data (device name & total km's ran)
* Display Watch and paired phone Bluetooth Information
Tweaks
* # Root required # Allow 3rd party software to be installed directly on the watch (you would need a file manager already installed on the watch)
* Toggle between show battery % screen while charging or the watchface (you may have to wake the screen once after making changes to see them)
* # Experimental # Enable find iPhone feature from watch (works by default on Android, so only use for iPhone users)
* # Experimental # Enable Haptic feedback (app needs to support this for it to work)
* Super Brightness - Sets watch to maximum allowed brightness. Manual 'L5' allows for a value of '180' in the settings. By enabling this option your setting will be '255' (maximum allowable).
* You can force restart your watch by double clicking on the PACE watch picture (typically bottom-right)
* Kill all ADB connections (in case Windows get confused or something)
I currently own and test the utilities on a Windows 7 (x64) based machine only and a PACE International version on stock firmware v1.3.6d
Downloads
https://drive.google.com/open?id=1Ho8RK1Fh858zX-aiWlNugNt8hg0B1XRg
File descriptions:
Amazfit PACE Tuner package vx.x [A zipped file that contains both the Windows & PACE apk utilities]
Amazfit PACE Tuner (Windows) vx.x.exe [The Windows utility - It uses ADB commands to perform various tasks on your watch]
AmazfitPACE_Tuner.apk [The PACE/Android utility which will be installed on your watch - USE THE WINDOWS UTILITY ABOVE TO INSTALL - DO NOT TRY TO SIDELOAD!]
Installation
-* Disclaimer *-
I am not responsible for anything bad that happens to your watch, your PC, or anything else bad that happens to you in direct or indirect relation to using this utility package. You are solely responsible for your actions.
Now that we got that out of the way...
PC
==
1. Make sure you only have ONE Android device connected to your PC (the PACE watch) and it is turned on!
2. Make sure you have extracted the following in the same folder:
A. Amazfit PACE Tuner (Windows).exe
B. Amazfit PACE Tuner.apk
C. Amazfit PACE Tuner Release Notes.TXT
2. Run the Amazfit PACE Tuner (Windows) utility
3. Click on the "Check for ADB devices" button and wait to see in the status window for one device to show up. If no devices show up, your watch may not be connected to your PC properly. If you see an error try click the button once more.
4. You can now click on the "Install PACE Tuner" button to install the APK utility on the watch.
@@@ Product Compatibility @@@
Amazfit PACE watch (1612) [Tested]
Amazfit PACE watch (1602) [Possible]
Stratos [Possible]
@@@ Platform compatibility @@@
Vista, W7
### The Windows utility version requires the .NET Framework v4.5 (minimum) to work ###
You may download .NET from here: http://www.microsoft.com/en-au/download/details.aspx?id=30653
RELEASE NOTES
^^^ ANDROID APP ^^^
v1.1
=====
* WiFi and Bluetooth toggle switches package
* Display version at bottom of app
v1.00
=====
* First release
&& Known bugs &&
None
============================================
============================================
^^^ Windows Utility ^^^
v1.2
=====
* Added Legends for Experimental and Rooted features
* Tweaks panel
> Renamed battery status screen to better reflect what it does
> Fixed some Tips descriptions when hovering mouse cursor
> Added Find iPhone feature (experimental) for similar functionality already enabled for Android
> Added Haptic Feedback control (vibrations need to be enabled in app to work)
> Added Super Brightness option (higher than Level 5 on watch)
v1.1
=====
* Optimised UI
* Introduced exception capturing/avoiding in code
* PACE Watch data panel
> Watch name
> Total KM's walked/run
* Bluetooth panel
> Bluetooth MAC address
> BT name
> Paired device's BT MAC address
* Tweaks panel
> Allow 3rd party software installation
> Toggle charging screen while on dock (show clock/watchface instead)
* Added reset ADB button
* Implemented Watch restart on double-click of watch picture (bottom right)
* Disabled Minuum Keyboard button for this version
v1.01
=====
Fixed app overwrite (for upgrades)
v1.00
=====
* First release
&& Known bugs &&
None
Frequently asked questions
Q: I am trying to launch the utility on the watch but I am getting errors/exceptions.
A: You have to use the Windows PACE Tuner utility to install the APK since it elevates privileges required for the app to run properly. If you try to simply sideload it it will fail!
Q: I have some great ideas or need more modifications - can you please do them asap?
A: Unfortunately for you I am not a 'proper' developer. I do this as a hobby on my (limited) spare time, so I can't commit to time or my abilities to be able to do what you imagine. Your ideas are of course welcome - I will do my best, but I will do it at my time.
XDA:DevDB Information
Amazfit PACE Tuner, Tool/Utility for the Smart Watches
Contributors
darkguset
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2018-04-08
Created 2018-04-08
Last Updated 2018-04-08
I have got a small local network:
• A router not connected to the Internet
• 20 tablets that connect to it
• a computer under linux with LAMP
• a computer under windows with WAMP
When I make an adjustment on an application, I have to repeat the operation on the 20 tablets one after the other. Is there a way to automate this task? What tool could I use to transfer the settings I make to the applications on a tablet over the local network? (they all have the same apps and they are all rooted)
For example :
• Adding a start page in FIREFOX or unblocking Pop-ups in this same application
• changing preferences in VLC
• Addition of a folder to be consulted in O’CLOUD (Android application which allows synchronization with the server)
• Applications to Greenify with GREENIFY
• Changing preferences in LIBRERA
• A new module in XPOSED
• A new task in TASKER
• etc.
I have a little idea using the TITANIUM data backup tool, but you still have to go through all the tablets to restore the data. Does anyone know the best way to apply tweaks to apps on a batch of tablets?
Thank you in advance for any ideas you can share with me.
Only as an idea:
You declare one tablet - which must have an external SD-card slot what can take cards >= 256GB - as the master
Code:
adb shell "setprop persist.is_master_tablet 1"
You clone this master-tablet's desired content ( create a .TAR archive ) onto this external SD-card by means of ADB
You pull created .TAR-file from master-tablet's external SD-card to Windows OS based server by means of ADB
You push this .TAR-file to all other 19 tablets by means of ADB
You extract the .TAR on all the 19 tablets by means of ADB
The steps ( except 1st one ) can be done in one-go with a Windows command ( CMD ) script ( batch-file ).
Michael5713 said:
I have got a small local network:
• A router not connected to the Internet
• 20 tablets that connect to it
• a computer under linux with LAMP
• a computer under windows with WAMP
When I make an adjustment on an application, I have to repeat the operation on the 20 tablets one after the other. Is there a way to automate this task? What tool could I use to transfer the settings I make to the applications on a tablet over the local network? (they all have the same apps and they are all rooted)
For example :
• Adding a start page in FIREFOX or unblocking Pop-ups in this same application
• changing preferences in VLC
• Addition of a folder to be consulted in O’CLOUD (Android application which allows synchronization with the server)
• Applications to Greenify with GREENIFY
• Changing preferences in LIBRERA
• A new module in XPOSED
• A new task in TASKER
• etc.
I have a little idea using the TITANIUM data backup tool, but you still have to go through all the tablets to restore the data. Does anyone know the best way to apply tweaks to apps on a batch of tablets?
Thank you in advance for any ideas you can share with me.
Click to expand...
Click to collapse
Jbib9n nk 8ø7ic
All-in-One tool for Windows. Wear OS Tools v10
It's a tool for use with any Wear OS watch. I am releasing today an improved and optimized version with several new features.
What does it do?
It is an All-in-One tool for Windows that makes it easy to do certain things with the watch, such as:
Send files to the watch such as MP3s, images, PDFs, or download files contained in the watch.
Install applications (Sideload).
Install applications in bulk
Uninstall apps of watch (Debloat).
Enable/disable Watch apps
Remove bloatware with Universal Android Debloater. [new]
Extract all the apps you have installed on the watch and mass restore them when necessary (Backup/Restore).
Get APK for Wear OS from "legacy" APK files for the phone.
Get APK for Wear OS in bulk.
Change ringtone, notification sound and alarm sound of the watch.
Mute ringtone, notification sounds, and alarm watch.
Manage vibration of ringtone, notifications or a specific application. [new]
Change screen density
Change font size.
Use the computer keyboard to type on the watch.
Force pairing the watch with Bluetooth without resetting to factory defaults.
Repair synchronization in old watches such as Moto 360 Gen 1 or Sony Smartwatch 3.
Enter ADB commands via command line
Perform advanced reboot (Recovery Mode and Bootloader Mode)
View and control the watch from the PC with scrcpy (only Wear OS 3). [new]
Take screenshots of the watch screen, and send them directly to the PC (Screenshot).
Record the watch screen, and send it directly to the PC in MP4 format (Screen record).
Optimize the Watch.
Apply custom settings such as adjust screen timeout
View watch information such as serial number, build version, Android version, resolution, battery status...
Connection to the watch can be made via Wi-Fi, via Bluetooth or via USB cable.
History of connected devices. [new]
New way to pair and connect for Wear OS 3.
Suggest IP of the watch.
Changelog:
v1.0 (Feb 13, 2021) - Initial version
v1.1 (Feb 21, 2021) - Compiled again with Pro version of the EXE converter.
v2.0 (May 19, 2022) - Added new features (backup and restore tool, screen recorder and watch information)
v3.0 (Aug 27, 2022) - Added new functions (Change font size, change watch sounds), debugged code, optimized menus
v3.1 (Aug 30, 2022) - Fixed bug in option to change ringtones and sounds.
v4.0 (Oct 15, 2022) - Added new function (optimize Watch) and restructured main menu.
v5.0 (Nov 05, 2022):
- Added "Install apps in bulk" (in option 1)
- Added "Enter ADB commands via command line" (in option 7)
- Added "Restore optimizations to default values" (in option 8)
- Added help option to get IP address and secure Wi-Fi network (in tool startup)
- Improved optimization tool (redesigned and more detailed info)
v6.0 (Jan 02, 2023):
- Added "Advanced Reset Options" (in option 7)
- Added "Enable/Disable apps" (in option 1)
- Added option to list system apps, user apps, enabled and disabled apps (in option 1)
- Added separate window for listings (in option 1 and option 4)
- Improved function to use PC keyboard (in option 7)
- Improved function for sending/receiving files (in option 3)
v7.0 (Jan 09, 2023):
- Added option to debug by Bluetooth in older watches, as Moto 360 Gen 1 or Sony Smartwatch 3 (in previous connection).
- Added option to repair synchronization in old watches (in option 7.5)
- Added option of links for reference such as news about Wear OS, firmware table... (in option 7.6)
- Added guide to download and install AOSP Wi-Fi Keyboard (in option 7.2)
- Added guide to download and install NavExplorer (in option 3)
- Improved wired connection with USB debugging (on previous connection)
- Correction of bugs
- Debugged code
v8.0 (Jan 23, 2023):
- Added tool to get APK for Wear OS from "legacy" APK files for the phone (in option 7.7)
- Added tool to get APK for Wear OS in bulk (in option 7.8)
- Added option to set ringtone and watch sounds to mute (in option 4)
- Bug fix when installing APKs (now the APK is not kept in the watch, avoiding it to occupy space).
- Fixed several bugs
v9.0 (apr 19, 2023):
- Added option to apply custom settings such as adjust screen timeout (in option 8.1).
- Added feature to suggest the IP of the watch (not Pixel Watch) by typing "find" (in previous connection).
- Added new way to pair and connect for Wear OS 3, for now, only Pixel Watch (in previous connection).
- Improved error messages when installing, uninstalling, enabling, disabling APKs (in option 1).
- Improved option to change custom sounds in ringtones, notifications and alarms (in option 4).
- Fixed bug for adding muted sounds.
- The tool is now also available in German (by @Anarchon
v10.0 (Jun 06, 2023):
- Added function to view and control the watch from the PC (screen mirror) with help of scrcpy (in option 9).
- Added tool to manage vibration for ringtone, notifications or for a specific app (option 4.4).
- Added system to automatically download adb drivers in case of absence (on previous connection).
- Added to automate downloading of necessary files (in option 3 and option 7.2).
- Added Universal debloater to remove bloatware (in option 1.6).
- Added history of connected devices by typing "log" (in previous connection).
- Added specified folder where backup/restore is located (in option 2).
- Improved screen recording function, now through scrcpy (in option 6.2).
- Improved system for entering file and package names when installing/uninstalling or other operations, no need to type it anymore, just select it from the list (in option 1).
- Improved system for selecting sound files and IDs (same system as above) (in option 4).
- Improved optimization tool (in option 8).
- Improved simultaneous connection pre-check of several devices.
- Debugged all the code and reorganized the menus.
- Resized all tool windows.
Requirements
Windows O.S.
Have the ADB drivers installed. Here is the link to download them. During installation, make sure to enable the "Add to System Path Environment" option. Here you have more information about ADB drivers. Since v10, if you don't have ADB drivers installed, they are automatically downloaded and installed as soon as you open Wear OS Tools. [new]
Connect the watch and the phone to the same Wi-Fi network.
Enable debugging over Wi-Fi on the watch. On the watch, go to Settings > system > About and tap "Build Number" several times until you see a message that says "you are now a developer". Then go to Settings > developer options and enable "ADB debugging" and "Debugging over Wi-Fi".
If you want to connect the watch to the phone via Bluetooth or Cable USB, follow the steps detailed on the tool.
Considerations
The tool is available in English (EN) and Spanish (ES).
Tested on TWP3 and TWP5, please give feedback on other watches.
To find out the IP address of the watch, just go to "Debugging over Wi-Fi" in Settings > developer options. Under that option, you will see the IP. You can also see it in Settings > Connectivity > Wi-Fi > "Your Wi-Fi network".
You can connect the watch by USB cable, by bluetooth or by Wi-Fi network.
Wear OS watches are a bit unstable to stay connected to the Wi-Fi network especially if it is connected by Bluetooth with the phone, to make sure it connects smoothly when using the tool enable the "Enable Wi-Fi automatically when charging" option in Settings > developer options, and plug the watch to the charger. Another trick is to momentarily deactivate Bluetooth in the watch, the Wi-Fi network will be activated in a few seconds.
Since v10 you can use the tool in multitasking mode, i.e. you can for example backup watch apps while you are applying custom configurations. [new]
When you have finished, turn off "ADB debugging" on the watch, otherwise it will drain your watch battery...
Where to download?
Wear OS Tool v10
Method
Download and unzip in a folder the file from the "Where to download" section.
Make sure you meet all the points in the "requirements" section.
Locate the IP address of the watch as explained in the "considerations" section.
Run Wear OS Tools and enter the IP address.
If your watch is Wear OS 2 enter 5555 or nothing in the port number, and skip to step 7.
If your watch is Wear OS 3, enter the port number, which will be different from 5555
.
Select "Pair new device" or "Wireless debugging" (This step is only performed the first time) and enter the IP, port and pairing code, then re-enter the IP and port number as in the previous step.
A notification will probably appear on the watch asking "Allow debugging?", select "Always allow from this computer".
In the tool, choose a function to run and follow the instructions on the screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Clarification on the new pairing procedure in Pixel Watch.
In the update in March 2023 for Pixel Watch, Google has implemented the new adb pairing procedure that had already been for some time on Android 11 and higher phones. It should be remembered that Wear OS 3 is based on Android 11, that is, watches like Pixel Watch, Galaxy Watch 5 or Fossil Gen 6. For now, this procedure is only implemented on Pixel Watch, but probably in the coming months it will be implemented on the other Wear OS 3 watches.
The process is that you must first pair the watch with a device such as a PC or smartphone, entering a random pairing code and a random port number (only the first time you pair to the device) and then the connection is made through the IP address as it was done so far, but with the difference that the port number is random (it is not 5555 as before) and you will have to consult it on the watch every time you connect the watch in developer mode.
Wear OS 2 watches, and for now Wear OS 3 watches (except Pixel Watch) connect the watch as usual and with fixed port number, i.e. 5555.
What custom settings and optimizations are offered?
Apply Custom Settings on the watch from the PC (option 8) :
Hide/Display developer options menu.
Enable/Disable GPS location.
Adjust screen timeout beyond limits.
Enable/Disable ambient display.
Enable/Disable theater mode.
Enable/Disable auto brightness.
Adjust brightness manually.
Apply optimizations (option 8):
Double the speed of animations and transitions.
Optimizations to improve performance and reduce battery consumption.
Enable/disable adaptive battery management.
Enable/disable the processing speed management system.
Enable/disable useless configuration items in Galaxy Wtach 4/5.
Manage Vibration (option 4):
Enables/disables vibration when receiving calls.
Enable/disable vibration when receiving notifications.
Enable/disable vibration when touching the watch screen.
Enable/disable vibration for a specific application.
Delete cache memory (option 8).
Optimize performance (option 8) .
Reduce battery drain with the dexopt optimization method (option 8) .
To-Do
Force pairing with Wear OS 3 watches
Improve optimization tool with more optimization tasks (any suggestions from this thread for Samsung Galaxy devices or this thread for Pixel devices?).
Porting code to Linux and Mac via Java or Python.
I share this tool for free, to code the tool as it is now having taken me quite some time, I just ask for some feedback for the one who download it and try it.
If you are going to use it, please comment what you think or what bugs you see or what new features you suggest. Any opinion is interesting.
Version Information
Status: Stable
Current Version: v10.0
Release Date: 13/02/2021
Last Update Date: 06/06/2023
Big thank you for that!
And also thanks for sharing the information about changing ringtones etc. I was really surprised, as i have seen that it isn't easily possible to change the notification sound on Wear Os...
It made me think i'm back in stone age
Thank you
will good to try it out
Hello, I update the tool because it had a bug in the option to change ringtones and sounds. It did not detect the sound correctly and you only saw it on reboot, now it detects it immediately.
WearOS Tools v3.1
For the effort, if you use it, feedback, please.
Hello
When i try to open the exe, the window open and close fast, but i can read
Parameter format not correct
Then show the path( i changed the default path ) to the folder i put temp and documents with a message "is no recognizable as an internal or external command, operable program or batch file"
Tbnitz said:
Hello
When i try to open the exe, the window open and close fast, but i can read
Parameter format not correct
Then show the path( i changed the default path ) to the folder i put temp and documents with a message "is no recognizable as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
What operating system do you use?
Try disabling the antivirus temporarily.
bernarbernuli said:
What operating system do you use?
Try disabling the antivirus temporarily.
Click to expand...
Click to collapse
Windows 10
same behavior with antivirus disabled
Works great on Windows 11 ARM inside Parallels on Mac, appreciate your work.
Hello, I update the tool. The main menu has been restructured, and a watch optimization tool has been added.
I take this opportunity to remind the function 2 of the tool about extract/restore applications from our watch. In the coming weeks there will be update for several watches with Qualcomm Snapdragon 4100 microprocessor as Ticwatch Pro 3, Fossil Gen 6... which will reset the watch to factory settings, and you will lose the apps you had previously installed, this tool allows you to extract the apps to your PC and restore them once updated to Wear OS 3.
It also serves to migrate your apps from your old watch if you buy the new watch, such as the Samsung Galaxy Watch 5 or Google Pixel Watch.
Wear OS Tool v4.0
bernarbernuli said:
Hello, I update the tool. The main menu has been restructured, and a watch optimization tool has been added.
I take this opportunity to remind the function 2 of the tool about extract/restore applications from our watch. In the coming weeks there will be update for several watches with Qualcomm Snapdragon 4100 microprocessor as Ticwatch Pro 3, Fossil Gen 6... which will reset the watch to factory settings, and you will lose the apps you had previously installed, this tool allows you to extract the apps to your PC and restore them once updated to Wear OS 3.
It also serves to migrate your apps from your old watch if you buy the new watch, such as the Samsung Galaxy Watch 5 or Google Pixel Watch.
Wear OS Tool v4.0
Click to expand...
Click to collapse
This is the great tool, and extracting/restoring apps is very useful, made use of it several times, much appreciated!
bernarbernuli
still having the same problem with v4.0
now i get a screenshot of the error, the screen pop for about a second and close
Tbnitz said:
bernarbernuli
still having the same problem with v4.0
now i get a screenshot of the error, the screen pop for about a second and close
Click to expand...
Click to collapse
This tool uses the Windows command line, does it work on your PC "cmd"? Is it a Windows Lite or something like that?
bernarbernuli said:
This tool uses the Windows command line, does it work on your PC "cmd"? Is it a Windows Lite or something like that?
Click to expand...
Click to collapse
Windows 10 full, i use adb all the time.
maybe because some of the folders to the temp folder have space in the name?
Tbnitz said:
Windows 10 full, i use adb all the time.
maybe because some of the folders to the temp folder have space in the
Click to expand...
Click to collapse
Go to the Windows start bar, type ah "cmd" (without the quotes), go to the folder where you have the tool with "CD" command, type "WearOS Tools v4.0_EN.exe".
If you have an error running it, now it will not disappear in a second.
Try also to copy the tool to the root directory of the Windows hard disk, usually C.
bernarbernuli said:
Go to the Windows start bar, type ah "cmd" (without the quotes), go to the folder where you have the tool with "CD" command, type "WearOS Tools v4.0_EN.exe".
If you have an error running it, now it will not disappear in a second.
Try also to copy the tool to the root directory of the Windows hard disk, usually C.
Click to expand...
Click to collapse
Same msg as the screenshot whenever i put the exe
Tbnitz said:
Same msg as the screenshot whenever i put the exe
Click to expand...
Click to collapse
In order not to lengthen this post thread about your problem, you could be more detailed, do you recognize "Pasta" folder?, have you tried to run any exe file from cmd?, where have you installed Windows?, have you tried to copy the tool in the root directory of the Windows hard disk? I don't know, give details, because if I'm not going a bit blind, the error you show in the screenshot is relative to a folder path on your PC.
bernarbernuli said:
In order not to lengthen this post thread about your problem, you could be more detailed, do you recognize "Pasta" folder?, have you tried to run any exe file from cmd?, where have you installed Windows?, have you tried to copy the tool in the root directory of the Windows hard disk? I don't know, give details, because if I'm not going a bit blind, the error you show in the screenshot is relative to a folder path on your PC.
Click to expand...
Click to collapse
Pasta folder is a incomplete name, "Pasta do sistema" is the full name and inside i put the system temp folder.
I tried with cmd, on root C:
Maybe because the path to temp folder has a folder with space in the name?
Tbnitz said:
Pasta folder is a incomplete name, "Pasta do sistema" is the full name and inside i put the system temp folder.
I tried with cmd, on root C:
Maybe because the path to temp folder has a folder with space in the name?
Click to expand...
Click to collapse
Yes, that's most likely what it is, you have an unusual Windows installation.
bernarbernuli said:
Yes, that's most likely what it is, you have an unusual Windows installation.
Click to expand...
Click to collapse
Is not unusual, just moved temp out of the ssd
any suggestions?
will it work to just "grant" permission like this?
pm grant ... android.permission.UPDATE_DEVICE_STATS
Click to expand...
Click to collapse
but what it the package that needs it?