Actual custom themes with themehax.

[yellows8]

TODO: figure out some way to properly load custom-theme data from {filepaths that Home Menu normally doesn't use} via ROP, and maybe fix #3 in the process. This is very difficult, so who knows if this will get done before next release, or ever get done at all.

Or, at bare minimum, figure out some way to let the user have BGM without building themehax manually, without breaking the normal BGM when custom BGM isn't available.

[yellows8]

Well, the actual theme-loading part works with my local changes. But Home Menu later hangs when trying to allocate memory from the same heap where the heap memchunk corruption occurred(enters a loop and never exits). Strangely this doesn't happen with the original RET2MENU, but not 100% sure if this exact code gets executed there too or not.

Getting the heap state repaired might be rather difficult....

[yellows8]

During Home Menu startup, that particular memalloc seems to be done always(?) normally: it triggers when no theme is used, and when a custom theme is used.

The only time this memalloc ever hanged was with my plain-SD theme loading(using a theme with the themehax itself works fine). Therefore, the second 0x2a0000-byte buffer allocation(same one mentioned in the README) must cause this particular heap state corruption(which originated from the original CTRSDK memchunkhax).

[yellows8]

Got the heap state restored, but BGM is broken. I'm guessing this is related to the object data which gets corrupted during the CTRSDK memchunkhax.

[yellows8]

NVM, object data mentioned above doesn't seem to get corrupted... Not sure why BGM is broken. :-/

[yellows8]

Home Menu is opening the BGM with the extdata archive, not the SD archive. Not sure why...

[yellows8]

Everything is working fine now, BGM included. Disabled changing the BGM filepaths, and switched the filepaths to using my own extdata filepaths instead. My testing nandimage system currently has an actual custom theme(BGM included) and themehax installed at the same time.

This issue will be closed once the local commit for this is finished(mainly support for <v10.1 Home Menu).

[yellows8]

"support for <v10.1 Home Menu" That's done now, except that I'm getting a hang without any crash for v9.2 RET2MENU under my testing nandimage. :-/

EDIT: Ugh, same loop as before except this time it's with allocating the 0x2a0000-byte buffer...

[yellows8]

v9.2 is now supported by this(as of last night). Have to verify that this works correctly with certain system-version(s) still.

[yellows8]

Closing this now since the local commit was finally done.