Eric12341

Originally Posted by JNDSDA

I have X50 and it was set to backup (Sprite) & reset itself every night. Still have the screen problems from time to time. Getting so annoyed that I went back to X5, X5 works like a charm and like a true pda, in my opinion.

u should do like alot of us and try to get it replaced with an x51v on a12 it really flies

Jake_Speed

Well, I did the fake sever trick again with activesync, I think I left out a step last time. Two days now, no reset, no screen problem and it seems faster with A12.

Eric12341

Good that u aint havin that problem anymore cuz that ish looks plain disgustin I jumped the first time I seen it on my x50v.

x51vuser2

Two days may be not enough.
I am pretty sure I saw link webpage in other thread which I can not find now.
That webpage produced error almost every time.

Eric12341

I have a12 and I seen it on this site

Beweglich

Got my x50v that worked fine just slow with WM5 replaced with a x51v
When I first used the complete shutdown feature and everytime i turn it on it flashes vetical not horizontal gray line just a second like turning an old tv, no the glitch i see described hear but.......

cerouno

I have the same problem, but only happened when using PIE and a web site www.emarket.com.do, (just a local "EBAY like site"), if anybody knows how to fix this problem let me know.
Thanks.

blkballoon925

Originally Posted by dp44

Did it look like this? I have had this problem on multiple X51v's. The most recent running A06 with no third party apps installed. Hope Dell/MS fix this soon. It is a real drag.

So I'm not the only person with this problem! :)
I've had this happen with 2 units from A02 (my first unit came with) through A06. I never tried A12 again after my first unit was rendered unusable by the upgrade. Anyway, this does seem to be a video issue. A soft reset will temporarily solve the problem, but AFAIK there is no way to permanently stop it from happening.

Jake_Speed

After doing the fake server trick, mine has never done it again, or at least I haven't been able to duplicate the problem again.

Beweglich

It must be the video decoder. Intel 2700g.
The screen runs through this for Intel optimized games and TCPMP.

protochu

I bet it has something to do with the fact that the Processor is self-adjusting. I have noticed it happens a lot when my axim starts a program that is video-intensive (like any PDAmill game). I would bet money that it is a delay when the processor adjusts to compensate for the increased graphics processing. The 2700g and the X-Scale Processor must not comunicate this, so when the processor halts for a split-second to speed up, the 2700g has no processing power to draw graphics, so nothing is drawn to the screen.

Was that technical enough, or am I totally wrong?

blkballoon925

I don't know if that's why for sure. I notice that once it starts rendering video incorrectly it will continue to do so until you soft reset.

ebaumgar

protochu, I think you are on to something there. That sounded like the most logical reason. I wonder if we set p speed to constant if it would happen as much or if at all?

Mokubai

The 2700g doesn't need the processor in order to draw things, the processor simply says, "draw this rectangle, copy data from this block of memory to the screen" and the 2700g gets on with it. The problem seems to be that there is an API to allow programs direct access to graphics memory and programs that are badly written don't know how to deal with things when exceptions occur.

I've seen this with a few programs that don't like being put into standby (games mainly) and when brought out of standby they "loose" whatever information they have regarding the screen memory, some error occurs that they don't catch and so they end up writing garbage thus corrupting graphics memory and a restart is required. I know IE does this sometimes and it seems to be a similar exception, mainly on graphics intensive pages, it encounters some problems it can't handle and writes garbage to the display buffers.

This may be exacerbated by the processor scaling feature, as protochu suggests.

Thinking about it, in the process of scaling the processor it changes the bus, memory *and* LCD bus speeds, it could be that this (done at a bad moment) causes the graphics system to respond with an LCD error which the software completely fails to catch and so does the computing equivalent of a major hissy fit.

Jake_Speed

Another thing that has happeded to me lately, I play mp4's. Downloaed from PhotoshopTV. They used to play very smooth using TCPMP, but the last three I've played have been very choppy. There will be a pause in the video while the audio keeps going and then the video will catch up and finally get going again. It does this continuosly through the whole mp4. I didn't check if it started before or after A12. It's a pain!