Hi,
I have game Syberia 2 1.0 US installed on wm2005 (upgraded from xda-developers site) on MDA II
I have problem with backlight. When i start game, the backlight turns off and i can swith it on until the game is running.
I searched forums for solution, but i can't find anything.
Have anyone some idea to fix problem?
THX for help
have you tried taping the screen?
have you tried holding down the powerbutton to toggle backlight on and off?
have you verified that it's only in wm5?
----
just a little letter mistake
vlodeck.
Start Menu->Settings->System->Backlight.
See if the backlight power off is checked. If so, uncheck it. Good luck.
solved the same problem with an ipaq 214.
i just installed a little utility called Backlight Toggle 1.5,
executed before running the game and it worked like a charm.
actually the application was meant to toggle on and off the backlight when bound to a hardware button (record), as the requirement says:
ยท Only works on Compaq Devices and only tested with PocketPC 2002 on a Compaq 3870.
in fact it didn't work for me but it fixed the problem with syberia somehow.
FYI i renamed the app "Syberia Backlight's Fix"
Related
I recently got a Qtek 8300 (similar to an i-Mate SP5m). It's working pretty well and I'm pleased with it. However, one thing I wish I could correct is that when I have my phone in a case, slightly touching the front of the case causes the locked keyboard to unblank the screen. I have an eBook reader so I have the screen stay on for a longer-than-usual time. The problem is that unblanking the screen for no reason wastes battery power. Half the time when I glance down at the phone case, the screen is on.
Is there any way to get only the left soft key, or any other key, to unblank the screen to unlock the keyboard, and have all the other keys ignored? Thanks.
-Gary-
I'd be very curious to get a solution to this problem too. Even the Automatic Keylock utility seems to end up calling the canned WM5 keylock routine, which turns on the light whenever you touch a locked key...
I really liked the way WM2003SE locked the keys on a PocketPC phone. With that, the light stayed off until I pressed the power button. The beauty of the power button is that it's recessed and won't be pressed by a carrying case. Plus, I always knew where the power button was - even in the dark.
Dave H
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
cinimod1000 said:
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
Click to expand...
Click to collapse
From my Wizard (XDA Mini-S), turning the "lock all keys" option on and off, changes this value:
[HKEY_CURRENT_USER\ControlPanel\Keybd]
"DefaultKeyLock"=dword:00000000 (unlocked)
"DefaultKeyLock"=dword:00000001 (locked)
unfortunately, there is no "Keybd" key on my Tornado (Xda IQ, specifically) so I suspect this won't work. Shame...
Daern
Hi,
edit: sorry, my english is very bad - I mean "volume buttons.."
after 2 weeks of working fine with my 750v the side buttons for loudness up and down on the left side of the Treo do not work anymore.
Now - when I press one of the both the battery status appears on the display - instead of the loudness dialog.
No chance anymore to contol the loudness.
I tried several soft resets, but the problem remains. I did not chance any tweaks.
Anyone an idea? Thanks.
Best Regards
Gerhard
I had this happen too...had to hard reset...I think it had something to do with SBP Pocket plus or another app with a today screen plug in.
They are controlled by the same dll which applies the ringtones, dialplugin and softkeys.
There is like a app which is always running an handles the extra bits palm add to the wm o/s
I made a backup with SPB. After the backup SPB performs a soft reset - after this the Treo works fine again. After the soft resets I made before nothing changed
Treo volume button
I have the same problem and I'm also using spb pocketplus but after a softreset the functionality came back again. And after a few days the same problem :-(
Anyways we'll have to live with it. For Now
There is a volume button fix
http://www.spbclub.com/forum/viewtopic.php?t=1824&sid=6b8c6cfcd3ab44651527602ddf3f9f4a
This seems to do the trick...Just put fixvolume.exe to your startup folder.
and it works ..
Yes, I tried it and it works fine.
I've tried googling all sorts of terms but I still can't fix my problem.
I run Pocketmind PocketMusic as my preferred music player. When I try to go to key mappings, and set one of the hardware keys to turn screen display off, it does the function that's set in the Windows Mobile Buttons panel, which is to go to my Today screen instead of the player commands. Setting that button in the Buttons control panel to <Nothing> doesn't solve this problem . I'm running WM6.
The same key binding worked fine on Conduits PocketPlayer, so I suspect there is another application that is conflicting with it. Any advice would be much appreciated!
heh, Surprisingly I have the exact same issue and it just happened recently for no apparent reason... but regardless I think I have found a resolution, I was running S2U2 and XCPU and I ran iLock from S2U2 and then I did the key lock for XCPU and now it works for some unknown reason.... obscure isnt it?
P.S: Hope it works for you too! If not just remove anything that could affect key locking.
2 problems with picodrive. The directional buttens are screwed up. left is up en up is right and so on. I have solved this myself no prob just keep on trying finding the right button.
Next problem is with the ABC buttons of Picodrive. Al the alfabethical keys are mapped to the same keyadress so A=> 0xe5 B=> 0xe5
They al have the same function in picodrive.
Is this a problem regarding the Touch Pro or with picodrive or with a windows setting
somebody else on here has mentioned exactly the same problem with another emulator, so I guess the Touchpro somehow represents it's buttons as the same, either that or what you are seeing is the response from the touch screen not from the button (as was proved in another thread the whole area is touch sensitive not just the screen) in which case turning off the touch feature might sort you out.
Its not the screen im talking about. It is the keyboard.
same with final burn
have the same problem with finalburn (mame emulator). Every key from the keyboard except the directional keys, enter and 2-3 others is beeing mapped / recognized as 0xe5
does somebody has a fix?
Besides that problem - has anyone been able to play either of those emulators to evaluate speed?
I'm concerned that the Qualcomm processor coupled with the VGA screen will result in slow performance.
I'm debating getting this phone, but wouldn't want to if it's too much of a drop off from my 6700.
The speed isn't a problem. Runs flawlessy. The applications are still buggy under some other aspects. But I wouldn't buy myself a device in order to run these emus. There are cheaper ones on the market.
Back to the problem with the keymapping...
I hard resetted the device and skipped the extended rom installation. The problem with the keymapping is still there. Therefore I can exclude the applications in the extended rom causing this problem.
Anyone some advices, fixes or workarounds?
no key mapping
key mapping is weird yes.
Mate of mine has the tytn II with a pocketSNES i loved it And i was in need for a new phone... HTC touch pro / raphael / MDA vario IV was a phone i really looked out fore for a while nice design etc etc etc ... just the key mapping for an emulator is a big .. down for me
Any fixes?
same problem here:
http://forum.xda-developers.com/showthread.php?t=420159
and
http://forum.xda-developers.com/showthread.php?t=425646
SOLUTION HERE: http://forum.xda-developers.com/showpost.php?p=2703133&postcount=3
Hi everyone. Sorry if i posted this in a wrong section, but General seems a right place for it...
I just put my hands onto a used Pharos Traveler 137 today, and it's driving me mad.
From what i remember, the power button should turn off backlight when pressed shortly.
On the Traveler, it invokes a soft-reset.
This happened on both native WM 6.1 and the official update to WM 6.5.
I have even uninstalled all applications in case anything was interfering. Didn't help. I just touch the power button and it reboots immediately.
Is there something i'm overlooking?
Can anyone help me solve the problem?
Maybe the button is mapped to something wrong? Is there, for that matter, an application or a registry tweak that will remap it?
Any help will be much appreciated; thank you all in advance.
Update: i have also found out that even when i lock the device software-wise (Start -> Lock in WM 6.5) and the nifty padlock thingy appears, the power button isn't disabled, it reboots my phone just as well. can i be 100% sure this is a hardware problem or is it still a software bug?
kiruch said:
Hi everyone. Sorry if i posted this in a wrong section, but General seems a right place for it...
I just put my hands onto a used Pharos Traveler 137 today, and it's driving me mad.
From what i remember, the power button should turn off backlight when pressed shortly.
On the Traveler, it invokes a soft-reset.
This happened on both native WM 6.1 and the official update to WM 6.5.
I have even uninstalled all applications in case anything was interfering. Didn't help. I just touch the power button and it reboots immediately.
Is there something i'm overlooking?
Can anyone help me solve the problem?
Maybe the button is mapped to something wrong? Is there, for that matter, an application or a registry tweak that will remap it?
Any help will be much appreciated; thank you all in advance.
Update: i have also found out that even when i lock the device software-wise (Start -> Lock in WM 6.5) and the nifty padlock thingy appears, the power button isn't disabled, it reboots my phone just as well. can i be 100% sure this is a hardware problem or is it still a software bug?
Click to expand...
Click to collapse
Hi, have a look on this threat and you will find more people on the same boat as you http://www.howardforums.com/showthread.php?p=13533804#post13533804