Yes, it’s working fine for me, too.
1 Like
Hi
On 1.3 b3 for me when UL is installed it just shows a blank screen and then shows the pop up that’s the app Keeps closing .
When I did a restart because UL was the default I couldn’t use the watch at all until I could close the app from the pop up
So if you are using it did you do anything that we could do to make it work ?
Also what version of UL are you using ?
If it’s not causing you any issues then I’ll try to install 1.3 b3 again and give it another go
Here is the WatchClockskin_crash text if its any help
Date : 2021_08_27_23_37_39
java.lang.RuntimeException: Unable to resume activity {com.ricktop.ClockSkinCoco/com.ricktop.ClockSkinCoco.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.view.ViewGroup.setVisibility(int)’ on a null object reference
--------- Stack trace ---------
android.app.ActivityThread.performResumeActivity(ActivityThread.java:4233)
android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4265)
android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2041)
android.os.Handler.dispatchMessage(Handler.java:107)
android.os.Looper.loop(Looper.java:214)
android.app.ActivityThread.main(ActivityThread.java:7386)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)
--------- Cause ---------
java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.view.ViewGroup.setVisibility(int)’ on a null object reference
com.ricktop.ClockSkinCoco.MainActivity.onResume(SourceFile:19)
android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
android.app.Activity.performResume(Activity.java:7939)
android.app.ActivityThread.performResumeActivity(ActivityThread.java:4223)
android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4265)
android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2041)
android.os.Handler.dispatchMessage(Handler.java:107)
android.os.Looper.loop(Looper.java:214)
android.app.ActivityThread.main(ActivityThread.java:7386)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)
Date : 2021_08_28_16_27_06
java.lang.RuntimeException: Unable to resume activity {com.ricktop.ClockSkinCoco/com.ricktop.ClockSkinCoco.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.view.ViewGroup.setVisibility(int)’ on a null object reference
--------- Stack trace ---------
android.app.ActivityThread.performResumeActivity(ActivityThread.java:4233)
android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4265)
android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2041)
android.os.Handler.dispatchMessage(Handler.java:107)
android.os.Looper.loop(Looper.java:214)
android.app.ActivityThread.main(ActivityThread.java:7386)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)
--------- Cause ---------
java.lang.NullPointerException: Attempt to invoke virtual method ‘void android.view.ViewGroup.setVisibility(int)’ on a null object reference
com.ricktop.ClockSkinCoco.MainActivity.onResume(SourceFile:19)
android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
android.app.Activity.performResume(Activity.java:7939)
android.app.ActivityThread.performResumeActivity(ActivityThread.java:4223)
android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4265)
android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2041)
android.os.Handler.dispatchMessage(Handler.java:107)
android.os.Looper.loop(Looper.java:214)
android.app.ActivityThread.main(ActivityThread.java:7386)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)
1 Like
I’m setting up a new Prime 2 with 1.3B3 and I had the same crashing issue with UL. I seem to have fixed it by setting
Settings > Apps & notifications > WatchClockSkin > Home app > Yes
5 Likes
It works! It ends up as a sort of permission issue - Make Watchclockskin the default home apps then no more crashes. Thanks for the advice.
Hi
Yes I confirm that’s works perfect thanks
Confirmed working here too…I’m just worried about what’s gonna happen when it “forgets” that its the home app (which happens about once a day)…
Yep, permissions 
I’m not a super techy guy, but understand enough (I think). I’ve got a Prime2. FAW VER 1.2 and WatchClockSkin UL VER 3.5.2, The launcher freezes up quite often, many times a day… Then I get the ‘close app, wait’ screen. Neither really resolve problem and within minutes it happens again. Clockskin is chosen as ‘default home app’. I have unistalled and done complete factory reset 3 times. Each time I have checked the permissions for battery optimization and home app default along with regular slew of permission requests. No change in results. When it eventually asks me to select default home app it shows HOME and Clockskin. I am pretty sure I removed the original WIIWEAR app files but some still show (see pics). I cannot remove HOME even when I have Clockskin set as default home app. I am in fringe T Mobile service area and most of the time I’m on home wifi or Hotspot to my Note 20 with ATT service, although crash still happens when I have 2 bars T Mobile while in town. I love Clocksin UL interfaces and icons and do not want to go back to standard. Here are some photos and crash log. I have a complete copy of Prime 2 on my laptop hard drive in case it really goes bad, not that would really help, but better to be safe. Is this the same issue as post #844 on Aug 15, 11:01 AM?
Can y’all help me please?
https://www.dropbox.com/s/hbmhnvektxyeujx/watchclockskin_crash.txt?dl=0
This is a known Android 9 bug, strangely it should have been fixed in A10. I can look for a workaround. I’m not having the issue with the FAW 1.0. Maybe i’m lucky.
@Eric_Crochemore
May be because the version of 1.2 being used could be a victim of the confusing firmware threads…
There was a stable v1.2 and an unstable v1.2.
If this was installed recently (last 2 weeks) it is probably the bad v1.2.
@Bil_Forslund I would suggest that stock is flashed and UL tested again and see what happens.
1 Like
Eric, can you refer me to a post or how to flash to stock please.
Thanks so much!!
This has been happening to me for EVERY FAW firmware since 1.0. It crashes (while asleep even), and then Android forgets who the home app is, though not every time. Sometimes even reverting to the FAW launcher on it’s own. Or it just hangs for while after waking before crashing. I thought this was a known issue though regarding crashes if there is a problem getting weather updates.
New version of UL 3.6 published : it solves the “Not responding” issue.
9 Likes
Hello, I have a zeblaze thor pro 3g, I had not used it for a while, now I have a small problem of a constant notification, only on the clock screen (and only with Universal Launcher), the notification says “bad response” , but I don’t know what it refers to…
Everything works, but in addition to being annoying, it makes the battery drain faster…
What could I do?
Sorry if I don’t write very well, but I use the translator
It relates to the weather not working. You have an old version of UL. Just update to the 3.6
4 Likes
Thanks, I could not do the update, I uninstalled the old version and installed the 3.6, everything perfect!
1 Like
Hi Eric,
I hope you can help me on this one, I am trying to put an Tap action in a .watch face, so I can take it to a 3rd party app on the watch, but the code I am using is not working
E.g.
wm_action(‘m_app:Heart rate monitor’com.cenon.heartrate’com.cenon.heartrate.HeartRateMonitorActivity’)
or
wm_action(‘m_app:Amazon Alexa’com.amazon.dee.app’com.amazon.dee.app.Launcher’)
Am I doing something wrong or does it just not work in UL for .watch faces.
All your help would be great, again Please keep up all the good work you are doing. I love this Launcher to bits.
Best regards