Hi there,
I'm now allready a few days busy finding a way to turn off the pda programmatically. The only thing untill now I've found is:
- turning off the pda which put the pda in a stand-by mode
code:
SetSystemPowerState(NULL, POWER_STATE_OFF, 0);
or
keybd_event(VK_OFF,0,KEYEVENTF_SILENT,0);
keybd_event(VK_OFF,0,(KEYEVENTF_KEYUP|KEYEVENTF_SILENT),0);
- soft resetting the pda
code:
KernelIoControl(IOCTL_HAL_REBOOT, NULL, 0, NULL, 0, NULL);
- hard resetting the pda (didn't try this)
code:
SetCleanRebootFlag();
KernelIoControl(IOCTL_HAL_REBOOT, NULL, 0, NULL, 0, NULL);
But I'm looking for a way to actually turning of the pda. Like (for the QTek 9100) holding down the power-off button for 5 seconds. Then you get the question "Device will be off, and ...". When you answer "yes". The device really turns off. Also in this situation the phone is off.
Does anyone has some ideas ?
I'm working with the following configuration(s):
- QTek 9100/MIO A701/HTC 3300
- WM5
- EVC 4.0
Greetings,
Juan
This function was not yet implemented on WM 2003, but on WM 5 and 6 you could try this:
Code:
ExitWindowsEx(EWX_SHUTDOWN, NULL)
Unfortunately I did not have the chance to test it.
Hi Levenum,
Thanx for your respons. I tried this option, but unfortunaly it doesn't work for the pocketpc. Also according to the documentation (in aygshell.h) only the reboot works:
// [in] Specifies the type of shutdown. This parameter must be one of the following values.
// EWX_POWEROFF - Shuts down the system and turns off the power. (not supported on PocketPC)
// EWX_REBOOT - Shuts down the system and reboots
WORK-AROUND
I've found a work-around to achieve the real power-off.
1) On the QTEK/HTC/MIO devices there is a special program used to perform the actual power-off.
For theQTEK/HTC: /Windows/PowerOffWarning.exe
For the MIO: /Windows/ShutDownApp.exe
2) This program I start from my application (with CreateProcess)
3) From my application I also send a message to confirm the power-off question within these dialogs.
So in the end I now have what I was looking for, but it would have been nice to have the actual code to do the real power-off. As in PowerOffWarning.exe and ShutDownApp.exe.
O2 XDA Flame has this feature.
Short press of power button to normal standby, long press switches the phone completely off.
O2 XDA Flame is using WM5 AKU3.2 or AKU3.3 I think.
So it should work if you get the correct command. But I am not sure which one.
Related
Hi all,
I've got a case sometime on Qtek 9100, which is protected by a password (in fact 4 digits) you have to tap when the device powers on.
Sometime, on the first screen , where i should tap the password, a countdowns appears, going from 512 to 0, then from 1024 to 0 and so on, and it is impossible to unlock the device (i had to hard reset!)
Do you have an idea of what this could be? And how to correct/bypass!
Thanks
Regards
N.
Well...
After two hours on Google, Microsoft and some good forums... I opened the manual which says "Each time you tap a bad password, the delays gets bigger until the device stops responding".....
Is this feature specific to Qtek 9100 or is it a Windows Mobile 5 feature?
Regards
N.
It may be a newbie question, but I have tried to find it out for a couple of weeks now and failed:
How do I turn the Universal off, apart from taking the battery out? Does Windows Mobile have a menu option that turns the deice off? I can't find the key combination that does it either.
What is the safest way to reset it? If I use the reset button, some recent text messages get lost.
I am using Helmi UNI AKU3.5 ROM. Might it be the rom's fault?
Hi there,
In fact, most PDAs are never "off" because else it wont turn "on" to do the reminders...
That said, few 3rd party tools allows you shutdown your device or restart it.
Like http://ppcsoft.narod.ru/english/
Or GsPocketMagic++
I think VJEschaton can put it into a "deeper" deep sleep. I can't remember if this works on the Universal, it should work on all HTC Xscale devices, but I think it was only tested on the Magician.
The device can be forced into any power state you want. But the OS doesn't support that, so it's OEM specific typically.
V
I had that prob with losing messages..
How you can fix it, is if before you reset you press the power button one (to make it sleep) then press it again (to wake back up) then do the reset.
It will keep that exact state its at then.
I think this is what you mean?
Hi there,
I wondered if anyone knows how to change settings for the two LED's at the top of a Blueangel device?
The Bluetooth is particularly bright, and its a pain flashing when trying to sleep. Even the other [power] LED is a pain when it starts flashing after the device is fully charged.
My ultimate wish would be for a program that kills the LES's when the screen is off between 10pm and 6am but hey I would just be happy to know how to kill them altogether, I am sure I could learn to live without the Bluetooth LED forever (although I can't bring myself to open up, and snip the LES's legs.)
Thanks in advance.
I think you didnt not search posts on the topic, there are number of them available for doing what you need.
Try following:
http://pdaphonehome.com/forums/xda-iii-mda3-pda2k-sx66-qtek9090/44396-turn-off-indicator-lights.html
Yes you can turn off Blueangel LEDs!
Thanks for the responce, the LED Off Util works a treat, dead set simple.
I noticed the link for the other Tweak app failed in the link provided, after a quick search I found the following, and the price has been cut in half, lots more options but the LED Off was free!
http://www.tweaks2k2.com/portal/index.php?topic=Tweaks2K2
Justin.
How about using registry tweak - search wiki and forum?
Kerio, I love the motivation you give people to Search, its great. Just for you when I get some time I will update a page on Wiki, as soon as I find out how to....
LedOff worked great for a while then failed, I uninstalled and then re-installed this time taking the error message at the start seriously. then downloaded the following and installed, I will see how this goes.
http://www.winmobiletech.com/sekalaiset/CF1SP3/netcf.all.wce4.ARMV4.rar
LED Off Reg Edit hack.
Kerio, you were right it was hidden amongst the many hacks.
http://wiki.xda-developers.com/index.php?pagename=BA_Hacks
Using "PHM Registry Editor"
Disable the Flashing Right Side Red/Green LED
1) Go to the HKLM\Drivers\BuiltIn\NLEDMgr key.
2) Rename the "Dll" value to "xDll"
3) Soft reset.
This COMPLETELY disables the right LED for ALL alerts.
The same can be done for the Left Blue LED by renaming the "Dll" value under the BWLEDMgr key.
Still I can't find a way to turn it on and off by time of day, I will keep searching...
You will not find anything - because this is absolutely useless You may write your own program - or try some scripting language (MortScript - I dont remember others name)
It just won't die...
I can't belive this, tried the LEDOff program, tried the reg hack, and it didn't work either. Well it half worked the Bluetooth LED is off, but the power LED is still blinking away.
I have now gone beyond the hack and removed the whole NLedMgr Dll key and also renamed the NLed Dll key to xDll, I will let you know how I go.
Removing the NLEDMgr.dll Reg key didn't work, the dam power LED (Right One) was still flashing all weekend.
I found another thread on the same topic today, looks like others are having the same issues as me. http://forum.xda-developers.com/showthread.php?t=235112&highlight=LEDs
Has anyone been successful turning off both LED's using WM6?
I have just put the NLEDMgr.dll key back, and did a soft boot, the LED is not flashing yet but there is a high probability it will start flashing in the next few minutes.
As per the other thread is says to set the HKLM\Drivers\BuiltIn\NLEDMgr\Index key to 0, mine was already 0 so I will leave the Dll key which is set to nledmgr.dll as it was originally(rather than changing it to xDLL as per earlier posts) and see what happens.
changing the index to 0 for nledmgr worked for me.
Well it is now working however I have made that many changes I don't really know which registry setting was the final one that fixed it.
I now don't have any LED's flashing.
The Power LED (on the right) goes orange when being charged with my charge cable, and solid green when fully charged.
When in the USB sync cradle, or in the car cradle I have no LED's lit at all.
None of the Notifications make the LED's flash.
and this has been working like this for more than 24 hours.
I am using Xplodes WM6 ROM 30/11/07 Version.
Registry settings are
HKLM\Drivers\BuiltIn\NLed\Flags(Dec) = 8
HKLM\Drivers\BuiltIn\NLed\IClass(String) = {CBB4F234-F35F-....really long string that i didn't touch}
HKLM\Drivers\BuiltIn\NLed\Order(Dec) = 0
HKLM\Drivers\BuiltIn\NLed\Prefix(String) = NLD
HKLM\Drivers\BuiltIn\NLed\xDll(string) = nleddrvr.dll [I did change this from Dll to xDll]
HKLM\Drivers\BuiltIn\NLEDMgr\dll(REG_SZ) = nledmgr.dll
HKLM\Drivers\BuiltIn\NLEDMgr\Index(Dec) = 0
HKLM\Drivers\BuiltIn\NLEDMgr\Order(Dec) = 0
HKLM\Drivers\BuiltIn\NLEDMgr\Prefix(REG_SZ) = LED
And the LED on the left, which I was easy to turn off.
HKLM\Drivers\BuiltIn\BWLEDMgr\xDll(String) = BWLEDMgr.dll [I changed this from Dll to xDll]
I have just upgraded my blueangel to WM6.1 so I needed to do this hack again.
The following seems to be the key regestry settings to disable the Right Green LED.
HKLM\Drivers\BuiltIn\NLed\xDll(string) = nleddrvr.dll [I did change this from Dll to xDll]
HKLM\Drivers\BuiltIn\NLEDMgr\Index(Dec) = 0
hello,
i have installed on my HTC wizard (VPA compact 2; G4; Wiza100) with WM5 this HTC home plugin.
After the installation i have saw, that by power-on my device -there where in the HTChome-screen in the top left is showes the provider-network name- is very shortly signaled "home", if i be in my homezone "vodafone home" (de: "Vodafone zu hause"). => first "vodafone.de", than very shortly "home" and than again permanently "vodafone.de"
Now my question:
What can i doing, that the signalisation "home" is displayed for a longer time (examply: 5 secunds) as under 1 second by power-on the Wizard?
Gives there a patch for al longer signalisation (or for a permanently switching the indication between "Vodafone.de" and "Home"-signalisation) if i be in my homezone?
Thanks for help
Frank
fraham said:
hello,
i have installed on my HTC wizard (VPA compact 2; G4; Wiza100) with WM5 this HTC home plugin.
After the installation i have saw, that by power-on my device -there where in the HTChome-screen in the top left is showes the provider-network name- is very shortly signaled "home", if i be in my homezone "vodafone home" (de: "Vodafone zu hause"). => first "vodafone.de", than very shortly "home" and than again permanently "vodafone.de"
Now my question:
What can i doing, that the signalisation "home" is displayed for a longer time (examply: 5 secunds) as under 1 second by power-on the Wizard?
Gives there a patch for al longer signalisation (or for a permanently switching the indication between "Vodafone.de" and "Home"-signalisation) if i be in my homezone?
Thanks for help
Frank
Click to expand...
Click to collapse
Don't know what you mean exactly, but it shows "home" when your signal is not available.
johanromijn said:
Don't know what you mean exactly, but it shows "home" when your signal is not available.
Click to expand...
Click to collapse
i mean: switch on from "standby" (short pressure on power-button for power on/of the device; not: from fly-mode or because the battery was unpluged)
Also is the "home"-signalisation a false presumption? It's no show "home", because i'm in my homezone ... but because it's searching the signal from the provider-network, if the device is switching on?
PS: If i think about... I would like to allege: The latest can't be, because the device was in "standby" and in standby-mode the phone can every time communicate with the provider-network, so that the phone isn't need to additional check the provider-network beside the regular pollings from the network.
A network-check is only needed, if the Phone is switch from fly-mode or the power was break/intermitted or the device gets a reset or the phone shall dial a number or the network doesn't poll for a destined time.
Frank
You install
1.Battey Status
2.add-ons BSHome
3.Soft reset
I hope that´s all what you need.
Hi everyone,
Just got a brand new Lumia 1020 (bought on ebay to a German retailer, so that's some Polish version whereas I'm in France, but whatever), and the camera ain't working. Somehow I can get it to take some pictures sometimes, but most of the time it's just like the camera app just doesn't detect any camera (rear or front).
I guess it's some kind of software failure, since whenever the camera app does actual detect the camera, the picture will freeze at some point exactly when I receive a notification or other kinds of actions (opening some menus, opening another app, ...).
I went through all upgrades, it didn't give any result. Hard reset doesn't work either. So I suspect some kind of corrupt file in the original files. Could happen after all.
My last option is to flash the damn thing, and I followed the tutorial, however when I reach the point to start the actual flashing, the phone isn't detected. I gathered that it should be in "flash mode", which you reach by shutting down the phone and pressing "vol down + power" for a few seconds. I did that, but it will only power up the phone as usual.
The question is : how the **** do I get into that stupid flash mode? Is it even real?
Many thanks
Xowap said:
Hi everyone,
Just got a brand new Lumia 1020 (bought on ebay to a German retailer, so that's some Polish version whereas I'm in France, but whatever), and the camera ain't working. Somehow I can get it to take some pictures sometimes, but most of the time it's just like the camera app just doesn't detect any camera (rear or front).
I guess it's some kind of software failure, since whenever the camera app does actual detect the camera, the picture will freeze at some point exactly when I receive a notification or other kinds of actions (opening some menus, opening another app, ...).
I went through all upgrades, it didn't give any result. Hard reset doesn't work either. So I suspect some kind of corrupt file in the original files. Could happen after all.
My last option is to flash the damn thing, and I followed the tutorial, however when I reach the point to start the actual flashing, the phone isn't detected. I gathered that it should be in "flash mode", which you reach by shutting down the phone and pressing "vol down + power" for a few seconds. I did that, but it will only power up the phone as usual.
The question is : how the **** do I get into that stupid flash mode? Is it even real?
Many thanks
Click to expand...
Click to collapse
make sure the phone is fully booted and all that jazz then you hold the power button and volume down. The second it vibrates click retry on nokia care suite
lolwutwin said:
make sure the phone is fully booted and all that jazz then you hold the power button and volume down. The second it vibrates click retry on nokia care suite
Click to expand...
Click to collapse
Well, if I do that when the phone is booted, it lowers the volume down to "vibrate", then I feel a vibration and the "pull down to shut down" thing.
Hitting "retry" at this time gives no results
Sometimes, I get this error though:
Code:
DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
Exception:
System.Runtime.InteropServices.COMException (0x8400AC35): DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
at FuseLib.DtlConnectionClass.ConnectToMedia()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryConnectionManager..ctor(FuseLoader fuseLoader, IConnection connection, UserInteractionDelegate userInteractionDelegate)
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Xowap said:
Sometimes, I get this error though:
Code:
DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
Exception:
System.Runtime.InteropServices.COMException (0x8400AC35): DTL Connection: Could not connect to media. DTL Back-End error code = 0x8400A403. DTL Back-End: Driver initialization failed. DCM status code = 0x84004416, Common USB DCM: The initialization parameters are wrong. .
at FuseLib.DtlConnectionClass.ConnectToMedia()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryConnectionManager..ctor(FuseLoader fuseLoader, IConnection connection, UserInteractionDelegate userInteractionDelegate)
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__c(Object state)
Click to expand...
Click to collapse
I'm assuming you're using Nokia Care to flash the phone, i would recommend to use Nokia Software Recovery tool, as it does all the work for you, you just press the install button.
If you get errors even then, i'd recommend checking/changing (in case it's not an original one) the USB cable, also if the USB ports are working properly.
VSparxx said:
I'm assuming you're using Nokia Care to flash the phone, i would recommend to use Nokia Software Recovery tool, as it does all the work for you, you just press the install button.
If you get errors even then, i'd recommend checking/changing (in case it's not an original one) the USB cable, also if the USB ports are working properly.
Click to expand...
Click to collapse
Changing the USB cable and the USB ports already has been done, however I did not know about Nokia Software Recovery, thanks for the heads up I'll try that