No glyph for custom app if installed on SD2

Issues 2508 Goose
1

Device: RG35XXSP
muOS Version: 2508.2 SILLY GOOSE

After fixing Scrappy to be able to use SD2 as its starting point, it became clear that apps installed on SD2 won’t show their glyph in list view unless glyph directory is moved to SD1, mimicking the paths used by the app on SD2.

The installer archive uses proper structure, in case of Scrappy: /Scrappy/glyph/scrappy.png. When installed to SD2, the glyph won’t show in the list by default, but move the glyph (and only the glyph) to /mnt/mmc/MUOS/application/Scrappy/glyph/scrappy.png and it magically starts working again.

You can try it using forked Scrappy 3.0.12 (it was worked around in version 3.0.13).

I tried poking around muxapp.c to search for the culprit, but wasn’t successful, so I hope someone else can take a look.

1 Like
2

Can u test it with Bluetooth app if possible

3

BT app is installed as muxupd, always on SD1, so it works fine

4

It remains always on sd1?

5

Yes, that’s why glyph for it will work

6

This has been resolved for 2508.3 Golden Goose

2 Likes
7

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.