Touchscreen doesn't work properly on almost all DS(i) games on my 3DS.

Touchscreen that works in NATIVE_FIRM (3DS mode) but not in TWL_FIRM (DS(i) mode) sounds like this one:

• my DS Mode is Still bricked!
• However odd this may seem, the issue was supposedly caused by faulty camera.

Two other users reported problems like this:

• DSi / DS functionality is broken still broken after following the troubleshooting guide

and @jeffyTheHomebrewer,

• New System update just released!

 

well, the cameras still work fine. also, DS Mode homebrews still work with the touch screen just fine.

 

Messed up DS Confg? Well, you could run the ds thicc firmware as a .NDS using a flashcart.

 

:/

Do both front and rear cameras work as intended?

 

Killing a mosquito with fire is an appropriate response. No one is judging you for resorting to nuclear option.

• Creating a NAND Backup

The question now is, does this solve the problem for sure, or will this DS(i) mode touchscreen ghost input come back?

 

I'm not familiar with the inner workings of the TWL_FIRM / DS(i) mode and only have a surface understanding of the TWLNAND partition.

But if I were in your situation, I would first test whether or not the cause of the ghost input was something coming from the TWLNAND or the CTRNAND.

To do this by process of elimination, the current TWLNAND image would first be backed up, then the TWLN partition gets nuked by reflashing a generic FAT16 image, manually adding back console unique files to their respective directories, and reinstalling fresh TWL system titles from scratch. Anything that relates or contains DS user profile in the TWLNAND would not be restored, or replaced with blank copiies. How these/this blank file(s) are derived or sourced from would require more figuring out.

Assuming the super cleaned up and rebuilt TWLNAND has nothing wrong at that point, if the problem still persists, I would then come to the conclusion that the continual ghost input in DS(i) mode might be caused by something from the CTRNAND partition just as the 3DS switches from NATIVE_FIRM to TWL_FIRM.


Edit - Don't try to experiment or test for this ghost input bug as described above. It's not a guide, but an idea of how to go about narrowing our search in finding the cause.Troubleshooting with unproven procedure carries the risk of further bricking your 3DS.

 

If I remember correctly, then touch cal is loaded from NVRAM, and if it fails, then it's loaded from the configuration savedata stored on CTRNAND (in simple words, your 3DS touchscreen settings are used instead).

Also, DS Profile settings are shared because of this, because DS Profile is stored on the WiFi card, not on NAND.

Sounds like your NVRAM might be nuked, or simply just toast. I think camera cal is loaded from CTRNAND, so that might be why it's not affected. I'll have to check later.

Edit: nope. Each time you start a DS(i) game, the touch callibration should be updated on the NVRAM.

 

Whoa! So the nvram.mem is where the Touch calibration is for DS Games?!

 

It should be also stored in the NVRAM, so DS games can read it. Not sure about DSi mode, because the DSi steals the touch from the ARM11, unlike for DS mode, where it seems like it's emulated by the ARM11 itself.

 

This happened to me today too. I have modded quite a few 3DS/2DS consoles over the years. But for the first time my touch screen is not working in the Japanese Flipnote tool and I cannot get through the modding process, because when the screen with 2 options comes up, you cannot press A to proceed.

The touchscreen confirmed works fine, as I tested it extensively everywhere else