Suggest using a different (older) android phone as I had that problem earlier on too!
Weloop Tommy Smartwatch (FAQ/Updates/Hacks)
- Thread starter taleboblen
- Start date
Suggest using a different (older) android phone as I had that problem earlier on too!
Problem
Hey. Tell Tommy and watch how you can revive it? Since I ask them to Chronos was all gud. Who I changed my phone was turned off sync when loads dials, Tommy moved to 3.19 all the rules but there is Chinese, flashed on the 3.18 firmware has passed and the clock is turned off and all. And I can not turn on.
Hey. Tell Tommy and watch how you can revive it? Since I ask them to Chronos was all gud. Who I changed my phone was turned off sync when loads dials, Tommy moved to 3.19 all the rules but there is Chinese, flashed on the 3.18 firmware has passed and the clock is turned off and all. And I can not turn on.
Thanks, that worked for me. I installed both bootloader and firmaware, but I can't see the extension on the watch, like the music player etc. Do you have any idea ? Many thanks for your support.
Try the Google groups site (https://groups.google.com/forum/#!forum/ossw-beta) - you will need to install the latest OSSW app, download and install the extensions, utilities, applications then the watchfaces.
Try a different phone - I had to use an older android first (4.4) to install then it works fine on 5. But timing is everything and it can take several attempts to get it past the 4%. I also went back to original bootloader to "unbrick" my phone a couple of times!Hi, when im trying to install ossw, it stucks on 4%, later on 7%. I cant do anything.
---------- Post added at 11:47 PM ---------- Previous post was at 10:53 PM ----------
meeeh, and now my weloop tommy is bricked
Finally, i do it, but now, im lost.
What are the controls of ossw? Where are the apps? Help!!!
WeLoop Tommy aka Goclever Eco also is YF Tech SmartWatch B01
http://www.yftech.com/B01.html
There is a lot of development for WeLoop Tommy 1(小黑1) for Chinese market.
Latest Chinese firmware(固件版本) is 3.38 or 3.40(I am not sure about 3.40) Note this is Chinese language only firmware.
There is also new app for all WeLoop products. This app just like GoClever app(com.yf.foreign.goclever) and WeLoop Tommy app(com.yf.smart.weloop) are developed by YF TECH http://www.yftech.com
Look at digital signature of all three apps.
There is new app for all Weloop products - smartbands, Tommy 1 and Tommy 2. It should allow flashing WeLoop Tommy 1 3.38 firmware.
AppName: WeLoop
Package: com.yf.smart.weloopx.dist
Version: 4.0.1
Revision: 141
App requires registration and it is in Chinese only too.
All YF TECH apps may contain some baidu adware - there is always Baidu folder created.
http://www.yftech.com/B01.html
There is a lot of development for WeLoop Tommy 1(小黑1) for Chinese market.
Latest Chinese firmware(固件版本) is 3.38 or 3.40(I am not sure about 3.40) Note this is Chinese language only firmware.
There is also new app for all WeLoop products. This app just like GoClever app(com.yf.foreign.goclever) and WeLoop Tommy app(com.yf.smart.weloop) are developed by YF TECH http://www.yftech.com
Look at digital signature of all three apps.
There is new app for all Weloop products - smartbands, Tommy 1 and Tommy 2. It should allow flashing WeLoop Tommy 1 3.38 firmware.
AppName: WeLoop
Package: com.yf.smart.weloopx.dist
Version: 4.0.1
Revision: 141
App requires registration and it is in Chinese only too.
All YF TECH apps may contain some baidu adware - there is always Baidu folder created.
Last edited:
Not very positive news
Yes, in Chinese maybe. For other languages markets Tommy Weloop and GoClever Eco are dead in the water. And YF Tech follows the same policy, so its stillborn.
Of course one has the OSSW project but it is not thanks to the manufacturers that decide to drop a market. Or is it?
Yes, in Chinese maybe. For other languages markets Tommy Weloop and GoClever Eco are dead in the water. And YF Tech follows the same policy, so its stillborn.
Of course one has the OSSW project but it is not thanks to the manufacturers that decide to drop a market. Or is it?
There areplenty of Weloop watchfaces ported to ossw:
https://www.dropbox.com/sh/yofx9xjvvw9ht9m/AAAHjoV7L3nUfZl-C7FjCElKa?dl=0
And Tommy to OSSW watchface converter so there is something new going on:
https://github.com/aleasoft/ossw-importerwatchface
So as you see @GastonP there is plenty of things going on even with Weloop "stillborn" Tommy
https://www.dropbox.com/sh/yofx9xjvvw9ht9m/AAAHjoV7L3nUfZl-C7FjCElKa?dl=0
And Tommy to OSSW watchface converter so there is something new going on:
https://github.com/aleasoft/ossw-importerwatchface
So as you see @GastonP there is plenty of things going on even with Weloop "stillborn" Tommy
I said the manufacturers' firmware and apps, as far as they matter for non-Chinese speaking are stillborn. Chinese-only apps are good to a big market, but I'm pretty sure not many around here care about that apps.
I am an OSSW user myself and am extremely happy with it.
I am an OSSW user myself and am extremely happy with it.
I can confirm that my watch, bought on 11.11 from aliexpress come with version 3.40, shipped at end of november, the seller informed me that is a only chinese firmware.
Now I switch to OSSW, so I can not provide more information.
I have an error, I can not get into the air, I'm leaving and returning to OSSW Weloop, but is always in SW01 BF57 Updating screen ... 0%
---------- Post added at 05:56 PM ---------- Previous post was at 05:00 PM ----------
I was using BONE and even I as a developer, was getting lost in how to help. I think some things missing document. Would help to improve, but even being lost in how to use some things.
---------- Post added at 05:56 PM ---------- Previous post was at 05:00 PM ----------
I was using BONE and even I as a developer, was getting lost in how to help. I think some things missing document. Would help to improve, but even being lost in how to use some things.
you'll have more luck going to the google group for the project... very active.
Found a new bug on Chronos Eco firmware(and possibly on Tommy too): Is don't know a leap year! From February 28th it jumped to 1st March. Trying to set it up manually confirms that this date cannot be entered. The question is if tomorrow it will correctly set da date back to 1st March on Tuesday or it will screw all the calendar beyond now.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
16The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
- better health monitoring
- profiles
- sleep monitoring
- more alarms weekdays/weekend
- and more.
Q: What does the settings do?
- Backlight- 24H: Backligth always turns on when button is pressed
- Nite: Backligth turns on when button is pressed at night time (from 17–8)
- Off: Backligth Always Off
- 24H: Motion detection always on (backlight turns on when motion is detected)
- Nite: Motion detection on at night time (from 17-8)
- Off: Motion detection Off
- On: Notification vibration disabled at night (from 23–8)
- Off: Notification enabled at night
- On: every whole hour the watch will vibrate. 12'O'clock etc.
- Off: Off
- On: Fitness functionality on
- Off: Off
- Chinese
- English
- On: Alarm when Phone is out of BT range
- Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t286444410WeLoop Tommy Watchface Creator new version released!
Changelog:
2015/04/30 [v1.10.12]
* New feature: add date to watchface
* New feature: generate digit images from fonts (two color combinations)
* Fixed gallery
* Faster image loading in gallery
* Bug fixes
Screenshots:
Download links are in first post. (link)
Please hit the Thanks button to let me know it works without problems, or if you encounter a problem, please tell me.9Hi Everyone!
A few days ago I have started developing a Windows application: WeLoop Tommy Watchface Creator
I don't have much freetime, but I will try to release it here soon.
It will come with limited functionality, but will add more when I will have time for that
I hope it will be useful.7So I've finally got around to starting to look into some stuff, and here's a few bits and pieces I've got so far:
-Watchfaces are stored on phone in a folder called "DIALS" in the root of the storage (for me it was internal storage, if your phone has an SD card it might be there instead). This folder contains all current watchfaces, as well as preview images. The watchfaces are in .BIN files, the previews are .PNGs.
-Opening the BIN files in a Hex Editor, made some interesting observations:
Couple of things to note here:
1. First 0x14 bytes are largely identical in every dial I've looked at so far [red boxes]
2. Exception are bytes 0x04 & 0x05 which seem to be an "ID" of some sort for the dial, also found in the file name [yellow boxes]
-Closer inspection of dial "0108" shows this:
Obviously this is just a sample, but it's quite clear that this forms the shape of the numbers 22. The files goes through 00, 11, 22...99 and then through them all again, with slight changes (presumably the first are for hours, the second are for minutes?). My guess would be that each of the hex values has a "meaning", it seems like 0xE0 for example comes at the end of a "row", and 0x03 comes at the start. When there's a solid row, it seems to be filled with 0xFF in between the 0x03 and 0xE0, but when only some of the row is filled, different values are used. (Different hex values could correspond to different line thickness perhaps? Just a thought)
And of course, this is just one dial that I have inspected slightly more closely (and still not that closely, really). For reference, here is the preview image from this dial:
I have also not yet tried replacing a dial on the device storage and trying to sync it with the Tommy. I don't know if the app re-downloads the files if they're modified or if it would sync a modified one (if it syncs a modified one, it would obviously be more beneficial to reverse engineer the format, not much point in making custom faces if we can't get them on to it).
Final thing I want to mention is that I have learnt that Android (as of 4.4) includes a built-in bluetooth logging capability. If you go into Developer Options in Settings (if it's not enabled, go into About Phone and tap on Build Number seven times, it'll pop up "you are now a developer" and then go back to settings and Developer Options will be there), there is an option "Enable Bluetooth HCI snoop log", which will dump a log of all packets being sent over bluetooth to the SD card/internal storage. This dump can then be read with a tool like Wireshark. Not sure if it's very useful, but maybe people who know more about bluetooth protocols and whatnot than I do would be able to make some use of it.
EDIT: Woot, first custom watchface (PoC):
EDIT: From this PoC, I can confirm that the first instances of each number are for the hours and the second are for the minutes (for dial 0108, anyways). I added the horizontal lines towards the tops of the first instances and towards the bottom of the second to verify this. I assume also that the "left" number is for the left of the screen and the "right" number is for the right of the screen, although I have not yet verified this (seems logical, editing a dial, transferring to phone and syncing takes time so haven't bothered verifying).
Just to clarify, I got this onto the watch my editing an existing dial and replacing the .bin file in the "DIALS" folder on the root of my internal storage (i.e. the storage accessible over USB).
EDIT: It's probably also important to note that the dials all have different file sizes, so clearly they all have different layouts etc. My guess would be in the 0x16 bytes that follow the 0x14 bytes mentioned above there are details about the layout (size of characters in bytes and such). It seems (although this could be inaccurate) that the actual dial starts at 0x30, and so the first 0x30 bytes (0x00 > 0x2F) are a "header".
EDIT: Figured out part of the header, I believe:
(from dial 0108)Code:Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 00000000 0A 0B 09 5C 08 01 00 00 10 00 00 00 00 00 00 00 ...\............ 00000010 30 00 30 00 30 19 30 19 06 02 4A 02 06 56 4A 56 0.0.0.0...J..VJV 00000020 40 50 40 50 40 50 40 50 00 00 00 00 00 00 00 00 @[email protected]@[email protected]
If you look at offset 0x10, the first 8 bytes are:
Taking these as two byte "words", and reversing the endianess (basically switching the order of the bytes), you get 0x0030, 0x0030, 0x1930 and 0x1930. Which are the offsets for the beginning of the first digit for the hours (0x0030) and the minutes (0x1930). Of course, as I mentioned before, each digit comes as a pair in this dial, so the first two words (0x0030 and 0x0030) I guess refer to the beginning of both the "0" digits for the hour, even though the second hour digit actually begins at 0x38.Code:30 00 30 00 30 19 30 19
Hope you guys understand what I am talking about here.
EDIT: Current estimate of header:
Code:Offset Length Description 0x00 0x04 Magic 0x04 0x02 ID 0x06 0x0A ??? 0x10 0x02 Offset for left hour digit 0x12 0x02 Offset for right hour digit 0x14 0x02 Offset for left minute digit 0x16 0x02 Offset for right minute digit 0x08 0x18 ???6Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
- Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
- Reset from watch (Last menu point, this resets everything)
- Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
- Connect your watch to the charger. (watch must be charging)
- Press all 3 buttons on the side simultaneously
- Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
- Delete connection from phone
- Connect and pair from app and upgrade
- If you are on an Android device and it cannot connect, try an ios device, and vice versa
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
- Download latest ECO firmware to phone
- Disconnect Watch from phone, install ECO app
- Go to “Check For Upgrade”
- Tap on the middle circle six times
- “Select a firmware file___ [Browse]”
- Watch must be in forced OTA
- Update watch.
- You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
- To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
- Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
- Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
- Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
- Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
- Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
- Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
- Notification not always deleted from phone when deleted on watch
- Watch freezes sometimes
- Being able to set the night time manually would be great (This can be done with the Goclever fw)
