Crash logs
Hi everybody
While using UL I noticed that sometimes it’s been killed by the system although it was unmarked in battery saver and battery optimization settings. I checked again and too my amazement it was marked in battery saver! I noticed that every time I unmark it, it would go back marked again… Even after reboot. Anybody knows what could be a reason of this weird behavior? Thanks in advance
Kospet Optimus Pro
You need to untag also the preferences application.
3 Likes
Huh, as simple as that! Thank you 
And thanx for the great launcher 
2 Likes
Seems to happen on A7 as well. Maybe the increased frequency of weather checks just makes it more noticeable now.
@Eric_Crochemore I’m unable to run 3.5.3 on S10pro (LEM14) with the 1.3 International Firmware. I’m not sure exactly where the issue lies, but it was fine until 1.3. I’ve posted over there too, but in case there is something going on from the Universal Launcher side, here’s the adb logs of the crash for review.
And although the log claims there was a trace written to /storage/emulated/0/WatchClockSkin_crash.trace, alas, this is not true.
Fortunately, I’ve got 2 of these guys so I ran in to this on my backup watch (I switch them when I need to wipe) so I’m still up and running fine on my current primary device with 1.2 firmware
Additional info: Just to be sure, I wiped again and did nothing else except install Universal Launcher; it still crashed. I also decided to try going in to the “Settings” icon it adds to the menu. From there, I tried to select the clock skin, but NOTHING happened. Nothing even gets logged to the adb logs except some audio related stuff for the “click” sound. It simply does nothing. Doesn’t bring up the skin selection, and no crash.
I can also add to this i can’t get it to work on 1.3 butt it worked fine on 1.2
Only thing is now is to decide to go back to 1.2 or just wait
Hi Eric
Sorry if this is out of scope but I wondered if you are planning an making UL compatible with the new firmware ?
Eric and @none and I need to talk about this problem.
But ultimately, yes we intend to make it work properly.
It may not be a problem with the launcher, we will be looking into it
2 Likes
I’m using UL on last faw fw and it works fine. I still think that it’s an authorization or battery saver issue.
3 Likes
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)…