I am having way too much fun with the satellite archive lolol

This has been a bug for a long time, but with the new update that allows satellite to go down to -90C, the problem's gotten even worse.

For example: A spot where it's -37C is green, but according to the custom scale, it should be blue.

Also if you try to use -91C in customizing the color scale, then reload, it goes back to -81C. I can only assume this is because the code thing isn't properly ready for anything below -81C.

Okay so it wasn't just my WiFi being stupid as usual. Something actually gone wrong with METEOSAT. Or at least receiving the METEOSAT data.

@AngelPandaEarth

well nevermind then apparently the newest mobile update fixed the issue LOL

So I'm testing out a custom satellite scale with Super Typhoon MAWAR and I've noticed this bug.

This is what I get on PC when I look at MAWAR as of the beginning of May 25

However, on mobile, it looks like this:

The thing to note is that the PC bar starts at 0:00z while the mobile bar starts at 4:00z (because I live in EDT, four hours behind UTC). The setting actually changes what time the bar should begin on PC (since switching it off will make the bar start at 00:00 EDT (4:00z)) while it doesn't on mobile.

And it gets weirder. On mobile, I move down to May 24 and slide up to 00:00z, assuming that is May 25 at 00:00z. But what I get is this.

It's a completely different image from the PC version. So going back to May 25 and the slider remains at 00:00z. And well, well, well...

So that's the situation with this and it's confusing me because I don't know which one is true. Turning off UTC display has no disparity; both versions start at 00:00 EDT.

Also I didn't realize how large the mobile screenshots would be uhhhh oops... is there a way to shrink them?

I am having way too much fun with the satellite archive lolol

This has been a bug for a long time, but with the new update that allows satellite to go down to -90C, the problem's gotten even worse.

For example: A spot where it's -37C is green, but according to the custom scale, it should be blue.

Also if you try to use -91C in customizing the color scale, then reload, it goes back to -81C. I can only assume this is because the code thing isn't properly ready for anything below -81C.

Somebody noticed the last issue, and an update even came out, but these problems still aren't fixed. So, I'll post it again.

The mobile Windy.com app and widgets has two problems:

1.) It crashes over and over again. How to reproduce is just to go in the app and normally use it. It'll crash for no reason at all. It doesn't even crash, matter of fact, as my phone doesn't even detect these. And I never had this problem while using Windy.com in the Chrome browser.

2.) Widget have problems loading and don't update. If it makes any difference, I use the ECMWF model.

A temporary fix is to uninstall and reinstall the app, but the fix lasts less than an hour. Another temporary fix for problem one is just to use Windy.com in the Chrome app.

In case you need them, here are my device specs:
▪︎Samsung Galaxy A20
▪︎Android 9/OneUI 1.1 (We've should've actually got Android 10/OneUI 2.0 this May, but Samsung just being stupid again)
▪︎3GB RAM
▪︎Exynos 8871 or some like that

Trying to customize wind colors and accidentally saved one line and then windy.com never load; only solution was to delete and recreate my account and clear all Windy.com data off my browser.

Lesson learn: DO NOT SAVE JUST ONE LINE OF COLOR