Screen washed out & flickering after sleep on CTRLX + OS 3.1

[ttn-15]

Hi all,

I have a Nspire CX (non-CR) and I have encountered a very weird problem with my calculator screen after sleep. I recently installed the latest versions of nBoot + CtrlX, and then decided that I wanted to take advantage of all the great Ndless utilities w/ hooking on OS 3.1.0, so I downgraded there by flashing Boot2 3.0.1, installing the OS, then rebooting off of the Boot2 4.4 in the ExtnD partition from then on. (Note that I used the CAS patch in CtrlX as well)

All seemed fine (I was able to use my calculator normally) until I turned off the calculator using Ctrl + On. Then the screen suddenly had colors that were very washed out and unsaturated, and it was flickering (it almost seemed to have scan lines of some sort?) However, the functionality was normal and I could use all the regular functions of the calc.
I uninstalled Ndless and all my apps, but the issue still persists on a stock OS after sleep.

By the way, this issue didn't happen for me on newer OS before, and it goes away after a reset.

I can take a picture when I get back to my calculator, and please let me know if any additional info would be nice for troubleshooting. I would really appreciate any help in solving this problem! Thanks!

[critor]

Hello.


Thank you for your very interesting post.

I remember I had the screen washed out and flickering on a TI-Nspire CM with ControlX.
But if I remember correctly, this only occured within ControlX. The screen went back to normal within the OS.


What's your TI-Nspire CX hardware revision ?
(see the datestamp at the right of the serial number on the back)

[ttn-15]

Hi,

Thanks. It's a revision C.

[critor]

Thank you. Revision C is similar to the TI-Nspire CM then, so it's not surprising.

Unfortunately, I have no idea about what's triggering this.

[ttn-15]

Thanks, I see.

Would you know if this issue would be gone on some other hardware revision A-J, or what causes the flickering on the CM like you described?

[ttn-15]

Or alternatively, should I try boot2 v4.3 instead of 4.4 and seeing if the issue still happens, would that make a difference?

Thanks.