Omnimaga
Omnimaga => News => Topic started by: DJ Omnimaga on May 28, 2011, 11:33:56 pm
-
Although we do not know if it is on the latest TI-Nspire CX OS (3.0.2), it seems that the CX wasn't 100% bug-free upon release.
If you add two empty strings together, the calculator crashes then reboots:
In addition to that, Yunhua98 recently reported (http://ourl.ca/10869/210378) about a bug with the LCD updating, causing some portions to not be updated properly when switching screens:
(http://www.omnimaga.org/index.php?action=dlattach;topic=8272.0;attach=7835;image)
Again, we do not know if those were fixed in OS 3.0.2, but since people will probably stick to 3.0.1 until they are sure they can downgrade fine, those are potential glitches you might encounter when using your brand new calculator that TI recently started to release. Hopefully they get fixed in later versions, even if the bugs are rare or not commonly triggered.
-
By the way, iirc the second image is not an actual screenshot of the glitch, just an idea of what it looks like.
-
I think this is why TI gave some devices out so developers can test them.
I still wonder, could it be possible that the CX was rewritted from scratch? Regular nSpire will display a syntax error, so it's possible that TI could've missed this little detail when editing some code for the CX.
-
I'm not sure. Maybe they accidentally introduced that bug. I know Casio did it with the Locate command on the Prizm, but fortunately it did not cause any crashes.
By the way, iirc the second image is not an actual screenshot of the glitch, just an idea of what it looks like.
Yeah I know. He sadly did not have a camera when the glitch happened. It was a rare bug.
-
This is TI for you ahaving their customers be their bug testers. I'm halfway between I hate TI and TI might be good. They have things liek this happen but they also release tools for Lua dev
-
I'm surprised it actually causes a reboot, has anyone reported the bug?
-
I already heard of adding two empty strings together crashing older versions of the OS. So this means that they haven't fixed that bug...
-
Again, we do not know if those were fixed in OS 3.0.2, but since people will probably stick to 3.0.1 until they are sure they can downgrade fine, those are potential glitches you might encounter when using your brand new calculator that TI recently started to release.
Downgrading is impossible on the CX anyway... The older OSes aren't supported and since 3.0.1 or higher is pre-installed, we can't TNOC it. (Unless you meant downgrading to 3.0.1 from 3.0.2, but I don't see the point in doing that unless there's some new 3.0.1 exploit that we'll find)
-
Well I meant for those who decide to stick with 3.0.1. (assuming they get their calc with it). I am sure older OSes wouldn't even work, unless maybe modified (which requires the 2048 bit RSA key).
-
Hum, this most certainly is bad. So it's an older bug TI didn't fix? :/
Also, the video is private, can I be invited to see it DJ?
-
Yeah, I changed the privacy settings for now, but the bug was here for a while, you can test it yourself by addind two epty strings (the " "+" " thing, with the dotted square inside the ")
-
Hmm why did you made the video private? ??? Couldn't you at least make it so people who know the URL can still watch it? ??? Now it no longer plays in the news above...
-
yes, sorry
-
Cool thanks. I'm still curious why it was made private, though. Did TI threaten you or something?
-
why is it private. I wouldn't think TI could tell you to make that private
-
No, no :P
But I wouldn't like it to be completely viewable to the outside world (especially from TI's people) with what's going to happen soon-ish between them and me+other people...
the other videos I posted about hacking the memory and the TI.Image format, I just made them private for now (just as a precaution), but this one is ok.
(can't tell more :P)
-
Oh ok. I hope you aren't hired by them to work for them, forcing you to end every contribution you did for the community, though O.O
-
Not at all, don't worry !
and I can still do whatever I want (as in h*cking stuff ... :P) for the community
-
Ah phew... at least I'm glad you're not going to contribute to further OS 2.71MP protections. :P
-
By the way, iirc the second image is not an actual screenshot of the glitch, just an idea of what it looks like.
Yeah I know. He sadly did not have a camera when the glitch happened. It was a rare bug.
the glitch isn't that rare, its just that it lasts for about 1-3 secs, I think i may have something to do with updating the screen?
-
By the way, iirc the second image is not an actual screenshot of the glitch, just an idea of what it looks like.
Yeah I know. He sadly did not have a camera when the glitch happened. It was a rare bug.
the glitch isn't that rare, its just that it lasts for about 1-3 secs, I think i may have something to do with updating the screen?
Hmm, it goes away after a few seconds? Sounds like it could definitely be a data cache issue as I thought. After more code is run, which will be a small amount since not much is happening, different data will fill the cache and the graphics data will be dumped into the actual memory and be displayed by the driver.
-
Ah phew... at least I'm glad you're not going to contribute to further OS 2.71MP protections. :P
And here we go again. People at the google nspire site are having trouble updateing their os to the latest one. Ref: http://groups.google.com/group/tinspire/browse_thread/thread/73244e7d5467b928?pli=1
Is it just me or is it impossible for ti to do anything without f-ing it up?
-
You right Dingus TI has screwed up everything they've done for the past few years
-
By the way, iirc the second image is not an actual screenshot of the glitch, just an idea of what it looks like.
Yeah I know. He sadly did not have a camera when the glitch happened. It was a rare bug.
the glitch isn't that rare, its just that it lasts for about 1-3 secs, I think i may have something to do with updating the screen?
Hmm, it goes away after a few seconds? Sounds like it could definitely be a data cache issue as I thought. After more code is run, which will be a small amount since not much is happening, different data will fill the cache and the graphics data will be dumped into the actual memory and be displayed by the driver.
Could the screen updates itself by chunks, but sometimes fails to update some parts due to sending data to the LCD memory too fast? Ah phew... at least I'm glad you're not going to contribute to further OS 2.71MP protections. :P
And here we go again. People at the google nspire site are having trouble updateing their os to the latest one. Ref: http://groups.google.com/group/tinspire/browse_thread/thread/73244e7d5467b928?pli=1
Is it just me or is it impossible for ti to do anything without f-ing it up?
X.x
-
The strange thing is, that the TI-nspire CAS Teacher Software does not crash when performing " "+" ", so I think it's some kind of low-level problem.. Most of the things that crashed the nspires also crashed the simulator. ("The Application 'TI-Nspire CAS Teacher Software' has unexpectedly quit")
-
Hmm strange. ???