Ok, thanks. I think the original reason that my T3 got this problem (the screen would go all glitch, fade and the device would lockup) was because when I was a beginner in programming and working on an application, the program was somehow writing to the wrong address (like the LCD). Anyway, that is not a problem. I just wanted to make sure that my device wasn't going to do something funny. :)
-Donald "Ben Combee" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > At 08:01 PM 1/12/2006, you wrote: > >Interesting. So the device is not all of a sudden going to turn off and then > >not come back on (or did what my T3 would do on occassion and the screen > >would change to a bunch of screwed up pixels and start fading, and > >occasionally not respond to soft or hard resets)? > > If that happens, you've hit some sort of problem where LCD refresh > has stopped and the system wasn't able to blank the screen before > removing power. That's not a "exit to console", that's just broken. > > If you see the blinking, it's waiting for a debugger to connect to it > or for you to reset it. > > > -- Ben Combee, Senior Software Engineer, Palm, Inc. > "Combee on Palm OS" weblog: http://palmos.combee.net/ > Developer Forum Archives: http://news.palmos.com/read/all_forums/ > > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
