PockeHAL and raw framebuffer (LG KS20)

[s.l.i]

Hi there!

I am an owner of a LG KS20 pocket pc. This device has a big problem with every application that uses PocketHAL and nearly all other applications that use direct video access techniques.
The screen doesn't update and only a small rect on the lower right area will be shown.
I played around with some C++ GAPI samples and figured out that the RAW FRAMEBUFFER mode is the problem.

Now my question:
Is it possible to say PocketHAL that it should not use RAW FRAMEBUFFER access?
That would be great!

[j.edwards]

I have received feedback from users of my PHAL based app indicating this device has the problem as you described also. Thanks for investigating the issue. Hopefully there is an easy work around.

[s.l.i]

Please, could anyone here say yes or no? YES, it is possible to say PHAL to not use RAWFRAMEBUFFER? Or NO, forget it!

If there is no function or flag available to set such an option, I would be happy to get an extra version of the PHAL libs where RAWFRAMEBUFFER access is disabled.

[Kzinti]

I have posted a logging version of PocketHAL 1.0.4 in this thread: http://www.pocketmatrix.com/forums/view ... hp?t=27784

Can you download it, build your app with it and run it on your LG KS20? This will create a log file in the root of your device's filesystem. Please post that log file here.

[s.l.i]

Hello,
here is the log file.
I compiled the fireworks sample with the logging lib.

Code: Select all

1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20

OEM String: "LGE" PocketHAL (Version 1.0.4) Display::Create( hwnd = 7C08D470, W:0, H:0, O:0, S:1 ) Initializing display... VideoDetect::DetectDrivers() GDIDriver: Detect() GDIDriver: Found W:240, H:320, D:16 VideoDetect: OS Version is 5.2 DriverVGA: Detect() DriverVGA: Raw info: W:240, H:320, X:2, Y:480, FB:4A5D27F0 DriverVGA: Native orientation is 0 DriverVGA: Found W:240, H:320, D:16 DriverVGA: Offset is 0 DriverVGA: Final framebuffer address = 4a5d27f0 CreateDriver( 00000008 ) Initializing video driver... DriverVGA: Initialize() Driver initialized! Success, returning display params to caller (W:240, H:320, O:0, S:2)

20 lines; 0 keywds; 29 nums; 79 ops; 1 strs; 0 coms    Syntactic Coloring v0.4 - Dan East

Am I wrong, or does it look ok?
It's courious. My first experience with applications that use PHAL was that only a small rectangle of the screen was updated. Now I have a battery meter installed, that is about the windows taskbar and start button. Exactly this area is now updated but not longer the small rectangle as before. Very very strange.

I think, we LG KS20 owners have to wait for LG and new drivers...
Thanks for your efforts.

[Kzinti]

Everything looks ok. This should be updating the entire screen. You are saying it isn't? If that's the case, then there is a problem with the device and we can try to work around it.

There is a version of PocketHAL that uses DirectDraw here:

http://www.pocketmatrix.com/forums/view ... c&start=15

You could give this one a try? It should also generate a log file.

[s.l.i]

It seems like LG has fixed their video driver in a new ROM version. We'll now have to send it to a service centre and so on... So this thread has not to be continued. Anyway, thanks for your efforts.

[Kzinti]

Any chance of getting you to test the DirectDraw enabled version of PocketHAL on the LG KS20?

[s.l.i]

Oh, forgot to mention. I tested it with firework sample and with j.edwards PointUI and it did not help. The same problem with not updating screen...

I will give it a try again when I get my KS20 updated.

[drgoldie]

I finally got my KS20 and as reported before PocketHAL does not work (does not switch to graphics mode).

I tried 1.0.4, 1.0.5 and the DDraw version.

Is there anything I can do to help solving this issue?

Daniel

[Kzinti]

Any chance you can try a plain GAPI application (that doesn't use GETRAWFRAMEBUFFER) and see if that works?

[Kzinti]

So I've read in a few places that if you update the ROM on the LG KS20, it will fix the problem.

I'd rather not revert to GDI on this phone if there is a ROM upgrade that works. (GDI can be very slow when screen rotation is involved.)

[drgoldie]

I've also read that but it seems to be very hard to find those updated ROMs.

Any ideas?

[Kzinti]

Well the situation is that:

1) GAPI doesn't work
2) GETRAWFRAMEBUFFER doesn't work
3) DirectDraw doesn't work
4) There is a ROM update that fixes these issues

So I would try to find the ROM update.

If I could get my hands on an actual device, I might be able to figure out a way. But I can't do reverse engineering remotely.

[drgoldie]

I fully understand that you can't do a lot in this situation.

The ROM on my device is 10a from Feb 26th. I believe that this is the latest version (it seems that the other versions 1c, 1f, etc. that are floating around are just lanuage specific as they have pretty much the same date).

Since the KS20 can do H/W OpenGL ES we'll probably use that method only anyway. Still, even the OpenGL ES driver seems to make problems. The same goes for camera access and other things.