Hey guys, and what’s about .apk Watchfaces, anybody knows? I mean, we can use simple skins and .watch faces, but there are a lot of skins which could be downloaded and installes as stand alone APK’s - would they work as well with the Eric’s launcher?
May 3, 2017 11:43:27 GMT 1 yawa said:
Hey guys, and what's about .apk Watchfaces, anybody knows? I mean, we can use simple skins and .watch faces, but there are a lot of skins which could be downloaded and installes as stand alone APK's - would they work as well with the Eric's launcher?
No, if you're talking of APK for KW88...
May 3, 2017 11:47:46 GMT 1 ricktop said:May 3, 2017 11:43:27 GMT 1 yawa said:
Hey guys, and what's about .apk Watchfaces, anybody knows? I mean, we can use simple skins and .watch faces, but there are a lot of skins which could be downloaded and installes as stand alone APK's - would they work as well with the Eric's launcher?
No, if you're talking of APK for KW88...
Yes, I meant them, thanks, Eric!
Hi ricktop , I think, I got a new bug: Even if I switch off to “silence” without “alerts” my watch is going on and vibrates when a new notification comes.
NB. I’ve got a problem with clock skins, notifications etc. again today, the watch was running out of battery. So I’ve tried to simply set back the app permissions but it didn’t help, so I’ve reinstalled the launcher. Some crash logs pls find attached, I think there ist smth new for you this time, I mean android.widget.ImageButton.getVisibility().
PS. Yesterday I’ve tested the alarm clock. Is it ok that it doesn’t work when notifications are switched to “silence”? I think it can be considered as a bug as well
What do you think?
PPS. By the way, these problems can not only occur when the watch is running out of battery, but also after the watch has been in flight mode and has to be reconnected. Eric, what do you mean, do you have any idea how to fix this annoying bug?
Doesn’t work on my LES 1. When I change watch face, it goes back to the same face. I have to reboot the watch to get the new face to show. Heeelllppp!!!
May 4, 2017 10:12:35 GMT 1 kjskot said:
Doesn't work on my LES 1. When I change watch face, it goes back to the same face. I have to reboot the watch to get the new face to show. Heeelllppp!!!
He-he ... Welcome in club!
2.1.4 finow x5 plus skin change only after reboot. Weather not update, battery prc not update.
Hi all
From my experience only “solution” to frozen skin (unable to change, various indicators not working etc) is clean reinstall of Universal Launcher (as shown in this post coourtesy of holandeca11). IMHO the crutial point beeing clicking on “Done” (or “OK”) instead of “Open” after installation (as shown in 0:27 of mentioned video). Bad part is that this doesn’t survive restart of watch (somebody asked me to check this but I was away for couple of days).
ricktop that cocos library caches some settings? Something that survives restart/power off?
May 4, 2017 12:39:21 GMT 1 nameless said:
Hi allFrom my experience only “solution” to frozen skin (unable to change, various indicators not working etc) is clean reinstall of Universal Launcher (as shown in this post coourtesy of holandeca11
). IMHO the crutial point beeing clicking on “Done” (or “OK”) instead of “Open” after installation (as shown in 0:27 of mentioned video). Bad part is that this doesn’t survive restart of watch (somebody asked me to check this but I was away for couple of days).
that cocos library caches some settings? Something that survives restart/power off?
“ok” or “open” is IMHO “a matter of trust” or “… of taste”
I’ve already tried both methods. I guess, it’s only about the order how you grant permissions to the launcher, nothing more. At the very end the Launcher gets all permissions it needs. And then it works till the next flight mode / restart / battery empty and so on …
Hi
If i changed the watch to silence and set the alarm clock,then in alarmtime i can see a little window with day & time and i have 2 buttons to cancel or to snooth.
My clock ist KW88 and it worked very well with Erics launcher but i have to reset it first. Than after the last 3 days I have no mistakes or error logs.
greets
pego2007
May 4, 2017 14:47:59 GMT 1 yawa said:May 4, 2017 12:39:21 GMT 1 nameless said:
Hi allFrom my experience only “solution” to frozen skin (unable to change, various indicators not working etc) is clean reinstall of Universal Launcher (as shown in this post coourtesy of holandeca11
). IMHO the crutial point beeing clicking on “Done” (or “OK”) instead of “Open” after installation
“ok” or “open” is IMHO “a matter of trust” or “… of taste”I’ve already tried both methods. I guess, it’s only about the order how you grant permissions to the launcher, nothing more. At the very end the Launcher gets all permissions it needs. And then it works till the next flight mode / restart / battery empty and so on …
This kept me thinking for a while… It’s not about permissions I think. And it’s not just a matter of trust/taste. See when you click “Open” you run this app on top of builtin launcher - it still runs in the background. This can be recreated on phones too (install another launcher and open it - as long as you don’t hit “Home” button you’ll be using that another launcher - when you hit it you’ll either get asked to choose or be put back to your default launcher). On phones this mostly is harmless but I suspect that this android version is heavily customized and we have no idea what parts have been edited out or changed. For the same reason it might act oddly after reset (ULng is running along original launcher).
Clicking OK replaces original launcher and there is no interference from it on ULng.
A bit of a long shot here but…
(I wonder if this can be confirmed/rejected by peeking at process list - adb log generates so much noise it’s almost unusable
Yuhuu, ricktop , I’ve gathered some new exceptions!
Well, I mean, they are new for me, I guess I’ve never seen them before. Would you take a look pls?
May 4, 2017 19:44:24 GMT 1 nameless said:May 4, 2017 14:47:59 GMT 1 yawa said:
"ok" or "open" is IMHO "a matter of trust" or "... of taste"I’ve already tried both methods. I guess, it’s only about the order how you grant permissions to the launcher, nothing more. At the very end the Launcher gets all permissions it needs. And then it works till the next flight mode / restart / battery empty and so on …
This kept me thinking for a while… It’s not about permissions I think. And it’s not just a matter of trust/taste. See when you click “Open” you run this app on top of builtin launcher - it still runs in the background. This can be recreated on phones too (install another launcher and open it - as long as you don’t hit “Home” button you’ll be using that another launcher - when you hit it you’ll either get asked to choose or be put back to your default launcher). On phones this mostly is harmless but I suspect that this android version is heavily customized and we have no idea what parts have been edited out or changed. For the same reason it might act oddly after reset (ULng is running along original launcher).
Clicking OK replaces original launcher and there is no interference from it on ULng.
A bit of a long shot here but…
(I wonder if this can be confirmed/rejected by peeking at process list - adb log generates so much noise it’s almost unusable
Well, perhaps you’re right. It’s difficult to say whether there are really some interference if I first open the launcher which has no granted permissions yet. I simply thought, the order doesn’t matter. The problem is still there though: either “ok” or “open” - sooner or later you’re running into the prob with skins & notifications & widgets. We have only one hope, its / his name is Eric
Yes working on that. For those rooted, you can try disable the main launcher, it could help. But i’m hoping to find the main reason for those things even If i think there’s not one reason, but many…
May 4, 2017 21:48:14 GMT 1 ricktop said:
Yes working on that. For those rooted, you can try disable the main launcher, it could help. But i'm hoping to find the main reason for those things even If i think there's not one reason, but many...
Good news, Eric, many thanks! My watch is not rooted yet, but I could take a look how to get it rooted (DM368/LF16). And yes, it was the same I was thinking today - it might have several reasons for these problems You'll get it. I'm sure, good luck!
OFF
There are new watch faces for the DM368’s stock launcher!
/OFF
I try to install it on my ourtime x200 , but is not fit on the screen…will the apps can be use on x200 later? Love your apps.
May 5, 2017 20:47:56 GMT 1 eeww said:
I try to install it on my ourtime x200 , but is not fit on the screen....will the apps can be use on x200 later? Love your apps.
What’s happening on this watch ? it looks like standard 400x400 screen. Do you have picture ?
May 5, 2017 11:43:45 GMT 1 mtibee said:
OFFThere are new watch faces for the DM368’s stock launcher!
/OFF
can post some ?
Can you please add time to time shuffle feature for watchfaces?