Calculator Community > Other Calculators

TouchPad 1.x downgrade problems


I'm opening a topic to list 1.x downgrade problems with TI-Nspire TouchPad, as I've had something frightening yesterday.

Feel free to contribute.

Calculator: TI-Nspire CAS TouchPad
OSes: 1.6 & 1.7
Problem: The OS doesn't start with any of the 4 available keypads (TouchPad, TouchPad CAS, ClickPad, and 84+). We either get a keyboard error dialog box, either continuous reboots.

Calculator: TI-Nspire TouchPad basic
OSes: 1.1-1.7
Problem: The OS doesn't start with the TouchPad keypad (continuous reboots).

Calculator:  TI-Nspire CAS TouchPad
OSes: 1.1-1.4
Problem: The TouchPad keypad keys are mixed and the arrow keys don't work at all.

Calculator: TI-Nspire CAS TouchPad
OS: 1.4
Problem: When plugging a mini-USB A plug into the Nspire (even if the cable is not connected to anything else) a dialog box is triggered saying that the connected USB peripheral is not working properly, asking to disconnect and reconnect the peripheral, and saying that the hardware might be faulty if the problem does persist.
When validated, the dialog box is triggered again allmost immediatly.
Moreover a strange alternative but regular noise could be heard from inside the USB connector; something like: noise for 1second, silence for 1 second, noise for 1 second...
It does not happen with a mini-USB B plug, and the TI-Nspire seems to be able to communicate properly with that plug.
A reboot didn't correct the problem.
After reupgrading to 2.0, the problem disappeared.

DJ Omnimaga:
The fact OS 1.6/7 doesn't even work even with a clickpad on the Touchpad Nspire is pathetic. Some people would have liked to use a smaller OS.

Thanks for posting this critor. SOmeone should sticky this, as I often have been looking for that info before.


DJ Omnimaga:
Cool, thanks :D

I just had this exact problem with my TI-nspire CX CAS. It stopped responding to a lot of keys and the keys that did respond where keys like 8, which typed an a and 2, which typed a 2. This was really weird because the thing that triggered it was me dropping it. It seemed to fix when I connected it to a nspire click-pad CAS and sent the OS. I thought it was a hardware error, but maybe it was not. now that I look at this, it seems to look like it switched to using boot 1.


[0] Message Index

Go to full version