Omnimaga
Calculator Community => TI Calculators => General Calculator Help => Topic started by: floris497 on January 29, 2013, 01:47:25 pm
-
Hi
I had a problem with my TI nSpire CX,
if I turn on my calc its slow as hell it takes about 15 second to get my documents selected with the arrow buttons
when i reset the calc every thing seems fine until i leave my calc alone for i think half a day a few hours or something is again very slow
unfortunately i had to delete ndless :( , so i cant reproduce the problem... maybe if i reinstall it. (will do that in the near future after my exam week).
Is it memory that is not released?
-
Do you have a lot of large files stored? If you do, that could be causing the slowdown when opening the doc browser
-
no only linux its 16MB or, so and some regular TI .tns files
it was really wired, it was just unusable. when i pressed the calc button to go to the calc it took 15s or more(did not count) and it took almost the same time to fill in a number and so on.
probably went something wrong with installing ndless but it is strange because it didn't dit something strange before it started
-
As said before if you have a large amount of files it takes a long time to index them or something like that. That doesn't explain the scratchpad lag tho..
Is it overclocked? Do/did you have any custom stuff installed (theme editor, nclock, stuff like that)?
(note that those two don't seem to have any problems, they're just examples =P)
-
at the time i had the problems the only thing was linux and some regular ti files.
but i think we will never be able to find out what was wrong... i only wanted to say the problem existed.
and i never over clocked my device (to risky for me) i already lost one CX :(
-
Have you tried deleting the 16 MB linux file? (After making a backup ofcourse :P) IIRC the nspire re-reads the entire documents tree when going there. The scratchpad and numer lag can be cause by having a medium sized file open (say 300k) or a file with lots of graphs/text etc. I've had that a couple of times myself. Usually clearing the calculation history fixed it for me.