Server problem?
Hello!
Recently i got to use again my old Chronos Eko and i find out that watchfaces server didnt work anymore, but luckily goclever server worked, but didn't had most of watchfaces and it sometimes dies.... so i made my own
HTML:
https://github.com/grzesjam/weloop-watchface-serverlike
i hope someone is going to use it, and its going to be useful, and if anyone have any questions fell free to ask.
Hi Grzesjam
I've taken a look at your solution (
https://github.com/grzesjam/weloop-watchface-serverlike):
"weloop-watchface-serverlike
Simple CMS-like server for own watchfaces for Goclever Chronos Eko and Weloop Tommy in PHP and HTML
1) Usage
Put all files on WWW server, change $URL in watch.php and index.html to correct domain and create "uploads" folder
2) Prerequisites
Any web server
3) Preparing modified version of app
Unpacking app by Apktool
java -jar apktool d [name of apk]
4) Modifying address of server
on Chronos app (in weloop probably in similar place) in
[name of apk]\smali\com\yf\weloop\activities\SendDialActivity$13.smali in 107 line
to "http://[domain]/watch.php"
5) Packing app
java -jar apktool b [name of folder]
6) signing apk
Find on google how (sorry)"
I've done the above things step by step, but when the app is installed and the smartphone is connected with the watch and I click on the "Watchfaces" button, the app attempts to download them for about 2-3 seconds, then the process ends. There are no notifications about any mistakes or anything like that....
I've got a few screenshots from my work:
1. The file which was supposed to be modified.
2. The Apktool app rebuilt.
3. The app signed and ready for use.
4. The server. I used Fenix.
I suppose there must be something wrong with my server....
Any help greatly appreciated :highfive:
[UPDATE ]
Grzesjam contacted me in connection with this problem. That was a very fruitful and terrific conversation where the ideas of high quality were exchanged, and as a result of it the immediate solutions have been implemented. His solution is a fully functional answer in this nasty situation. Additionally, he underlined that everyone who thinks of this solution needs to remember that the server solution that you choose needs to support PHP.
Personally, I chose the solution where my server was really functional and user-friendly, but I didn't read the technical documentation in full and unfortunately it did not support PHP, so that I encountered quite a lot of problems in the beginning. However, everything functions as it should right now.
Many many thanks Grzesjam.