TF3D crashing
 

When flipping through pics within TouchFlo it gets to a specific pic located on my memory card and the screen blanks out and touchflo restarts. Every time I get to the pic the same issue occurs, however if I go full screen, I am able to flick through every pic. Anyone get a similar issue?

Re: TF3D crashing
 

Try a hard reset to fix the issue, if that doesn't work, take the phone back.

Re: TF3D crashing
 

It's not a hardware problem, so taking the phone back's not going to help anything. Sounds like a glitch in the software. Try moving that photo out of the folder and maybe recompressing it or something and see if that clears it up. That photo's overwhelming the software.

Re: TF3D crashing
 

i did a hard reset twice same thing

Re: TF3D crashing
 

If no one else is reporting the issue, then it sounds like the phone is defective. I had a Touch Diamond that was giving dll errors all the time, and I tried hard resetting it, and using different ROMs to no avail. I took the phone back to Sprint, and they exchanged it out for another one, and that new one does not have the dll errors in windows mobile. Just saying.

Re: TF3D crashing
 

OK..so I removed that pic that I thought was having the issue, it appears to happen when trying to move onto the 4th picture. These are all pictures that were taken with my mogul 1200x1600 jpeg.

Re: TF3D crashing
 

How large is the picture and what type of picture is it? Jpeg or bmp?

Re: TF3D crashing
 

What you may want to try is saving the image as a jpg and maybe shrinking it down to see if the same issue occurs, if it does I would do a return sounds more like a TF3D curroption

Re: TF3D crashing
 

you could also try opening the pic using the native windows mobile pic viewer and seeing it if it loads properly.

Re: TF3D crashing
 

Yes, but no one else has the exact same images he has. That's my point. Software crashing when you open a specific image is no evidence that his hardware is faulty until you've opened the exact same set of images on more than one device and it hasn't happened on the others. You have to duplicate the circumstances exactly, or prove that they can't be duplicated, before you start making assumptions about the hardware.