how to debug the theme runtime errors

[JapaneseDrunkard]

I made my custom theme for 480 x 854 screen.
It passed .checkwps.

Then I edited "wps/WPSLIST" to replace the standard theme "cabbiev2" with my custom theme.
It passed wpsbuild.pl.

Then I made rockbox.apk and installed it on my android smartphone.

When Rockbox was launched, my custom theme didn't appear.
The failsafe theme appeared instead.

In this case,  how can I investigate the problem?

[[Saint]]

This sounds to me as though the device was still expecting to be able to load cabbiev2 at first boot.

I am guessing that after loading the theme manually it "Just Works"?

I can't honestly say that I've had any experience in replacing the default theme in this fashion, frankly, because it makes very little sense to do so. We've tackled this in other posts in the past. I can't for the life of me understand the requirement to embed the theme in the binary when we provide the means to load these assets from emulated or external storage. Doing it this way just makes the binary larger than it needs to be, removes your ability to be able to report errors trivially (any reports must be reproducible with an unmodified binary), and generally creates more work for you for no obvious gain.

If I'm missing something in your use case that makes this a necessity, please do tell me.


[Saint]

[JapaneseDrunkard]

Finally I made it!

Exactly as you say,
the default theme settings are hard-coded
in the file "apps/settings_list.c".

> #define DEFAULT_WPSNAME  "cabbiev2"
> #define DEFAULT_FONTNAME "08-Rockfont"
> #define DEFAULT_BACKDROP    BACKDROP_DIR "/cabbiev2.bmp"
> ...

I rewrote these parameters, and it worked!

> the device was still expecting to be able to load cabbiev2

I have never thought that.
Thank you for your sincere support  :-)