I have one too :
1 Like
What I see in this article is that an array out of bond can reboot the device as could several exceptions if not handled correctly.
The fact that I have those reboots on Prime 2 in UL and not in the native launcher all while using the same watchface and every other things beeing the same let me think the exception has a very high probability being in ULā¦
Of course programming is far from an exact science so nothing is never 100% sure!
I see this in the crash report :
āSecurityException: Permission Denial: starting Intent { act=android.appwidget.action.APPWIDGET_CONFIGUREā
And I can link this with a problem I had when I created widgets in UL.
Once I was asked to add a permission to create a widget, and I did as asked.
BUT, I created a widget from ATV Launcher and then a new green cross replaced the white cross for creating a new widget.
I think ATV Launcher was then in charge of creating the widgets :
The dialog was completely different
I could create a widget with only an app icon to launch the app.
It worked flawlessly for a while and then reboots happened.
After restart the widgets where all black with a tiny message āCanāt create widgetāā¦
Perhaps ATV Launcher failed to ask the right permission.
Iāll let you see if this makes sense for you!
If necessary, tomorrow, Iāll send you screen copied to illustrate this.
BTW, I only installed ATV Launcher in the afternoon and my crashes and reboot problems were there long before this even if after a clean reinstall of UL 3.4.2 it became very rareā¦
I just tried one more thing :
I created a widget, inside ATV Launcher.
It asked me permission to create and use data from the widget.
Then the widget was correctly created inside ATV Launcher.
BUT, when I created a bottom bar of widgets from ATV, although it was done without a problem I tried to reboot the watch.
After restart the bar of widgets was all black and I had to delete every widget to avoid further problemsā¦
Iāve had reboots also, and I have no idea if they are related to UL or not. But I will say this - when using 3.4 I had a reboot about once a day or so, and since using the first 3.4.2 Iāve had none. I havenāt yet tried the pedometer fix version because itās not that important to me.
Itās great - but only if this is the real problem.
Any logcat or crash reports are extremely important right now
This morning, five minutes after I woke the Prime 2 and put it on my wrist I had a reboot.
Here is the log :
That time I had no widget in the bottom bar!
And after that it has been several hours without a problem all conditions the sameā¦
Have you enabled the Heart Rate sensor in UL ?
I donāt know if the heart rate question was for me but yes I enabled it.
1 Like
Iām afraid this log is an old oneā¦
I donāt think UL leaves an error log when the watch reboots!
I had a full day with the Prime 2 on my wrist with UL and a non so simple .watch watchface :
I had one reboot 5 minutes after the Prime 2 awakening with no app running in the background and no bottom widget.
After that it worked flawlessly until the beginning of the afternoon where another reboot occured in the same conditions.
Around 6PM UL crashed without a reboot and I was stuck on the recents page!
The home button brought back the dialog where I had to choose between the original launcher and UL.
BUT, when I choosed UL, it immediately crashed and I was back to the dialog.
I had to choose the original launcher that worked fine.
Then I had to reboot the watch to get access to Universal Launcher again.
After that no more problem until the battery was drained...
The watch was in always on mode all day.
I don't know if that can help without a new crash log.Just had my first reboot in days. What if any logs can I send and how do I find them?
(I also have HR enabled, and have 2 widgets)
BTW, what API level are you targeting?
Crash file is in the root of the sdcard.
Target API is 28 to bypass restriction coming with 29ā¦
I still see a UL crash, when it arrives, i usually have to try several times for UL to start. The crash is generally in the compiled library, that makes it very difficult to analyse and thereās no crash file or very few information in itā¦ This A10 FW is hard to understand, maybe next FW updates will bring more stability.
I donāt see a crash file there.
To make my app compatible with 29 all I had to do was set requestLegacyExternalStorage=ātrueā. UL has different abilities so yeah other restrictions may apply. Not sure how Iām going to deal with API 30 though.
I tried a full day of Prime 2 use WITHOUT ULā¦
No reboot or crash.
That is to put my last day experience with a full UL 3.4.2 day with a few reboots and crashes in perspective.
Note that those incidents were very rare and didnāt affect much my day experience.
1 Like
Crash file:
1 Like
Try disabling the heart sensor in UL, itās not really useful anyway.
Why do you say itās not really usefull?
Iām beginning testing with heart rate disabledā¦
Today my steps in UL are 7396, while in build-in health app, it is only 4938. Some days they are equal, but not today. I understand those days where UL have a lower number, because not being the launcher all day, thus not able to perform count. But how can it get a higher number than the build-in app ?
maybe UL saves the number of steps when you change launcher, and the when you change back to UL it adds together the saved value and the total number of steps it receives from the health app. I have no idea if this is how it actually happens, but itās one possible explanation as to how it could happen
1 Like
This one happened at a reboot. HR was disabled.
Heart rate sensor disabled in ULā¦
One day and a half without crash or reboot!
2 Likes