So far no crash. But with the reduced UI-Memory the jpg-quality is not better than without.
If your CHDK build is using the unofficial ARAM configuration (instead of EXMEM), JPEG quality should be unaffected by CHDK, and the CHDK "supefine" JPEG override should actually work.
I have started experimenting with lowering the size of UI memory because some cameras have very little free memory (when EXMEM is not used). So, you can further lower the size of UI memory, but JPEG quality won't increase - you'll only get more free RAM for CHDK and the Canon firmware tasks.
BTW, the correct way to alter the amount of pre-allocated UI memory is to modify the green value in boot.c, not the commented line above it (note that 0x927c0 is the original value from the firmware):
// " LDR R5, =0x927C0 \n" // - (600000 bytes allocated for UI memory)
" LDR R5, =0x727C0 \n" // + (steal 128kB from it)When EXMEM is used by CHDK, the firmware can only allocate less EXMEM than it expects, and on some cameras this results in a JPEG size limit. If the firmware limits JPEG size, detailed images will be saved with high compression = bad quality.
@WW
Yes, that should do. Since reyalp's d10 shows unexpectedly low free UI memory, it's possible that there are other models with that condition. If you have time, try entering some more complicated Canon menus repeatedly and note the lowest numbers.