Message UI has a lot of empty space with the new firmware/app update

[Poolitzer]

Hi, this issue started recently when I updated my bangle js. I can hunt down which version change brought the issue if needed. I think its the new font

There are two big areas where we miss a lot of space here. The biggest is the one below the left right icons and the actual message content. The second biggest is the empty area above the blue header saying which app send the message from whom, with the red back arrow. I know we mostly honour this widget line except for clock faces, but imo this message display could also be an exception, since one might want to see a lot of info there. And if we render them, at least show my usual widgets which tells me the time up there.

Also I would suggest to maybe not maybe make the heading smaller. Like I know its important so it makes sense to render it big, but that is really big and with the extra padding takes up like a third of the screen...

[gfwilliams]

What firmware version are you on? Maybe an old one? I believe on recent firmwares you won't have the widget bar at the top, and that will push things up so the text is aligned properly and that gap makes sense

[Poolitzer]

Hi, its 2v27, which according to the Bangle js app is the most recent one. Thats the one I took the screenshot with.

And its not the actual widget bar showing widgets, its just the back arrow. E.g. the lock icon shows up below the red arrow in the blue header thingy, which usually goes in the widget bar.

This is how my actual widget bar looks like.

I went into the messages app settings, show widget is disabled, widget messages is set to 3, whatever that means. I can't remember ever setting these settings.

[gfwilliams]

I just tried it here, and I see:

Which seems good to me - we can't 'half-space' the text so it's either there or one whole line up.

Does anyone else see this? You can reproduce by pasting this in the Web IDE: require("messages").pushMessage({"t":"add","id":1575479849,"src":"Telegram","title":"Poolitzer X","body":"Look at the big space above",reply:1,negative:1})

Is it possible you've got some app installed that's overwriting the default showScroller implementation? Please could you copy/paste the app list from the App Loader's 'More...' page?

[Poolitzer]

Sure.

App list

widlock (0.08), numberchaser (0.01), widbat (0.12), widclk (0.08), widalarm (0.02), about (0.15), game1024 (0.12), diceroll (0.02), guitar (0.03), mylocation (0.11), notify (0.14), stopwatch (0.06), reply (0.03), widmessages (0.07), poweroff (0.05), setuichange (0.04), sudoku (0.01), launch (0.25), alarm (0.52), daisy (0.17), android (0.44), sched (0.33), messagegui (0.87), messages (0.67), ptlaunch (0.16), messageicons (0.09), boot (0.66), weather (0.28), setting (0.79), health (0.35), msgtwscr (0.01)

[gfwilliams]

Great - there you go. Uninstall setuichange - that's what is breaking it. It's already deleted from the app loader, but I guess for those that tested with it, it was left on your device.

[Poolitzer]

Thanks a lot! For the record, the space above vanishes when the message gets longer, so its fine.

[lunctis-viribus]

The recent changes in Message UI brought some more bugs. For instance touching the red/green arrows doesn't work anymore. And regularly, when a new message arrives, it doesn't show the new message but an older one.

[thyttan]

However, showScroller can also handle touches of course so we could add it again.

I'm personally not too keen on the idea though, since scrolling very slowly can trigger a long-touch which may in turn then trigger the actions involuntarily. Not a super big problem admittedly (EDIT: and we could mitigate it by disregarding long touches specifically).

[gfwilliams]

Thanks for digging into it!

Yes, I'm with @thyttan on this - I feel like encouraging swiping is probably better than re-adding the press.

I'm open to adding again if there's a good reason though.

[Poolitzer]

Always swiped, always thought thats the best way to do it

[lunctis-viribus]

I don't think touching the arrows ever worked? They were there to signify that you have to swipe left or right to perform that action.

We had a whole thread where the new changes were proposed and folks tried them out for a while before they got merged in, and nobody brought this up. Maybe you can see if you can find a way to reproduce the new message issue from gadgetbridge debug menu or with GB commands and I can look into it?

Or if enough people are upset I can just revert it all

I managed to reproduce the new message issue (with newest firmware and app versions).

• Prerequisite: at least one unread message (created by an generic Android app notification) needs to be in the Messages app.
• The go to Android app Bangle.js Gadgetbdrige - Debug
• Send a Test1 message
• Do nothing and wait till you are back on the default clock on the Bangle.js2 (this is the crucial part!)
• Send a Test2 message
• Now the Bangle.js2 Messages UI shows Test1 instead of Test2.

It looks like there is some bug going on where a new message is arriving on the Bangle.js2 but where the content of the message doesn't arrive in the Messages app. In my example the message Test2 can never be seen on the Bangle.js2 while the Messages UI app did open (with the previous unread message) when this message arrived. When there is nu unread message it also happens that instead of opening Messages UI the Bangle.js2 opens up the Messages screen with all read messages (and never returns to the clock screen).

Hope the issue is reproducible with this information :)

[gfwilliams]

Can anyone else reproduce this? I just tried with two test messages:

• GB({"t":"notify","id":2,"src":"Twitter","title":"Tweet!","body":"testing..."})
• Wait until we go back to clock
• GB({"t":"notify","id":3,"src":"Hangouts","title":"A Name","body":"message contents"})

And it all seems to work great for me. I wonder whether it's some specific setting you have that's causing problems?

So you're saying that when you do it, if you go back from the displayed message by pressing the button the second time, you don't see both messages in the list?