Related
I have a program called Fred (names have been changed to protect the innocent) which I created in embedded Visual C++ 3.0 targetted for the Pocket PC 2002 platform.
The main dialog is a blank dialog - that is, it contains no controls.
When Fred starts, it shows this dialog for a split second, then executes what I call a Dialog Driver. This is simply some code that decides in what order to show other dialogs.
This driver shows the first dialog proper - the entry screen for the application with various option buttons. Depending on what button the user presses, they are taken through a series of dialogs, entering information as they go.
It is the dialog driver's responsibility to show the correct dialog, let it dismiss itself, then display the next one, so that there are at most two dialogs in existence at one time (the blank dialog and the one the user sees). This is opposed to the other traditional method of making each dialog itself display the next dialog in the sequence, with potentially tens of dialogs all laid on top of each other.
Here is the thing: on the XDA I, Fred works seamlessly. You always get a split-second pause between dismissing one dialog and showing the next. In this split second, you see the underlying blank dialog and the user thinks nothing of it.
On the XDA II however, the pause still occurs between one dialog and the next, but this time it sometimes lasts significantly longer. We're talking several seconds of seeing the blank dialog and there is no pattern to when this occurs.
On one occasion, we spent 4 minutes staring at the blank dialog, waiting for Fred to display the next dialog and in the end decided to interrupt it by tapping the Start button. This magically displayed the next dialog's contents with the Start menu on top, making everything alright again.
Right, I've rambled on for long enough. You probably stopped reading hours ago. If anyone has experienced similar problems or have any idea why this might be happening, I would be very grateful to hear from you.
Specs:
Fred is an embedded Visual C++ 3.0 program targetted for Pocket PC 2002, running on an O2 XDA II running Windows Mobile 2003.
I know, I know... vijay555 just released a similar application earlier today. It seems we were working on the same thing at the same time. After discussing this with him in his thread: http://forum.xda-developers.com/viewtopic.php?t=45851
I've decided to go ahead and release my own version as an alternative.
The program can (and probably should!) be mapped to a hardware button using the Buttons control panel applet. I run mine on Button 4(hold) because I never use the voice recorder. This also prevents locking the device unintentionally.
I have also added two minor features to the application that some might find useful. You can optionally put the device to sleep after it is locked (same as pressing the power button) and you can configure a program to run just before the device is locked. This is useful if you have an application that you may want to look at frequently without unlocking the device. (Contacts, Calendar, a full-screen clock application, etc).
Both of these options are set in a control panel applet System->Device Lock.
NOTE: I know some people have use memmaid to register the lock application to run on wake up. If you do this, DO NOT select the suspend device option!! This will result in not being able to wake your device up for more than a few seconds (Wake up the device, your notification tells the device to lock, the lock process suspends the device, You wake up the device, rinse, repeat)
If you do this, all is not lost, just soft reset your device and uncheck the option to suspend in the control panel.
Here's a link to the installer (Requires WM5 PocketPC edition):
http://www.mr2-power.com/downloads/DeviceLock.CAB
You will likely need to soft-reset to see the new Control Panel applet.
*NEW* The latest version does NOT require the Lock Device today item to be loaded!
Enjoy!
-Matt Armstrong
Tried it on a BA and it works but change the default from suspend when locked since the applet doesnt show till after soft-reset. Thanks.
so you're saying make the default behavior NOT to suspend. Someone in another forum also requested the ability to blank the screen rather than suspend. I'll likely add this option in the next couple of days. I can change the default registry entry now though. A new installer should be up in a couple of minutes.
-Matt
Ok, yet another new CAB file has been uploaded. This new version has the option to suspend the device OR just blank the screen. If you blank the screen your programs will continue to run (and consume more power!). To restore the screen just press the power button. I also changed the default behavior after install to JUST lock the phone (not susped or blank). Everything else is the same.
-Matt
P.S. I appreciate all of the feedback very much. Keep it coming!
Thanks for the changes armstrom, ill download and test again. Thanks
Just installed and it works ok.
I have updated the software one final time for the night.
I have eliminated the requirement that the Lock Device today item be loaded. Now you can go unload that item and free up 20 pixels of screen real-estate For some reason this was a biggie to many people :? So it's finally done.
Keep the bug reports coming as you find them.
-Matt
great version. Without the plugin makes it invaluable. Maybe you can make as an option to hook it to the power button to get it to run when you power off? Or we can use vjkey for that
Well, I can add that option. In fact an early revision of the software did have it. I was just having inconsistent results with it on my MDA. For some reason the MDA wasn't firing the wakeup event if I suspend and then resume with just the power button. (press the power to suspend, then press again to resume). If I programmatically suspend the device, then I get the event every time. I can add it back in though if you want to try it on your device. Maybe you'll have better luck?
Edit: I just installed the new version vj's software and it has the same problem as mine. For some reason my phone does fire the wake-up event properly! I'll add the option back in to my software since it seems to work on other people's hardware just fine.
-Matt
Awesome!!
Man this place is great!
Armstrom, both you and VJ are awesome. This was the biggest single thing I've missed since buying my 8125. Since I use Xpress mail and the device wakes up when a message comes in, and if it's in my holster, and a button is gettind pushed, all sorts of weird things would happen.
So I had to always remember to go to Today, scroll down, hit the lock function...grrr.
But no more. I can't believe the terrific amount of support, hard work and resources you guys all contribute to these cool little gadgets.
Thanks again to both of you.
-JMS
If this can be made wot work reliably with power on events it would be awesome.
Thank you for putting these together.
One quick question...
I would love to have the Today screen as my default app to load on a lock action, however I can't find a way to do it. There is no .lnk file to point your Device Lock to.
I tried installing PHM Keys (as there's a Today .lnk in there) but it won't install in WM5.
Any programatic way to invoke/call the Today screen from a shortcut/lnk file so I can point the Device Lock to that file so Today is always showing when I lock my phone.
Thanks again, you guys are great.
-JMS
(Apologies for multiple entries - posting problems)
(Apologies for multiple entries - posting problems)
(Apologies for multiple entries - posting problems)
Great job Matt.
One quick question for ya - I would like to keep Egress running on the today screen when the device is locked. When I choose NOT to suspend the device or blank the screen, the today screen shows but the egress app is not cycling thru the latest news (it sticks on the last before the lock).
Is there any way to keep Egress at least cycling thru the news it d/l before the lock (if not allowing it to continue to update at egress specified times)?
Thanks again!
Thank you
A very useful app!
jkimrey said:
Great job Matt.
One quick question for ya - I would like to keep Egress running on the today screen when the device is locked. When I choose NOT to suspend the device or blank the screen, the today screen shows but the egress app is not cycling thru the latest news (it sticks on the last before the lock).
Is there any way to keep Egress at least cycling thru the news it d/l before the lock (if not allowing it to continue to update at egress specified times)?
Thanks again!
Click to expand...
Click to collapse
I'm really not sure how to solve that issue. I've never use the application you're talking about. Perhaps it is detecting the device being locked and not updating itself? I'm really not sure.
-Matt
Matt,
I think it must have something to do with the phone being in locked mode. I've found that when the phone is locked, the screen will go black after a couple seconds for both the lock on the today screen as well as when using a hardware button thru your application.
When I use the today screen app, after tapping the screen when black, it will display the today screen with the cycling headlines.
When I use your lock app, however, and tap to get the screen back, it doesn't cycle. If I hold down the power button and then turn it back on after being locked by your app, however, it does cycle.
Not a huge deal, just found it interesting...Wonder what would be different between the included today screen lock and your lock app that would cause this?
Thanks again!
armstrom said:
jkimrey said:
Great job Matt.
One quick question for ya - I would like to keep Egress running on the today screen when the device is locked. When I choose NOT to suspend the device or blank the screen, the today screen shows but the egress app is not cycling thru the latest news (it sticks on the last before the lock).
Is there any way to keep Egress at least cycling thru the news it d/l before the lock (if not allowing it to continue to update at egress specified times)?
Thanks again!
Click to expand...
Click to collapse
I'm really not sure how to solve that issue. I've never use the application you're talking about. Perhaps it is detecting the device being locked and not updating itself? I'm really not sure.
-Matt
Click to expand...
Click to collapse
Ok, I have added the option to lock the device on wake-up. Note: I have not been able to test this because my device does not properly send wake-up notifications. If someone could give this a try and let me know if it works I would appreciate it.
I have also added command line options to override the configuration specified in the control panel applet. The options are as follows:
-o:* Overrides the lock options and takes a number 0-2.
0 = Lock Only
1 = Lock then Suspend
2 = Lock then Blank Screen
-r:* Overrides the application to run after locking. This must have Quotes around it. Specifying -r:"" will prevent the default application from running.
Here are some examples:
Blank the screen and run the calculator.
DeviceLock.exe -o:2 -r:"\Windows\calc.exe"
Just lock and don't run anything
DeviceLock.exe -o:0 -r:""
You do not need these command line options if you just want the device lock to always follow what you have specified in the applet. These are only to optionally override the specified behavior. Some people on another board expressed the desire to have the device lock in two different ways depending on what they were doing. This is the way
Again, please let me know if the lock on wake functionality works or not
The cab is in the usual place.
-Matt
Here are some examples:
DeviceLock.exe -o:2
Hi All,
I've tried various search strings looking for an answer to my issue but found nothing related. Anyone else have an intermittent problem whereby pressing softkey for "Messaging" yields no body or list, only a title bar and softkey menu as normal? When it occurs, I just see the Today Screen where either the message contents or list of messages should be displayed. After some fumbling and clicking around I can usually get the content/list to appear. I only noticed this problem when I first loaded summiter's ROM but now I have the official Cingular ROM loaded and problem still exists.
Thanks in advance for any thoughts or solutions.
can you access the messaging if you go through the start menu or do you have the same problem there??
is your soft key mapped right to the messaging link?
softkey mapped
Thanks for response, yes, softkey is mapped; as I mentioned earlier, when you launch messaging, I get only the top and bottom elements of the program (Title, New, Menu) but the middle content (message, list of) is missing)--you see only the Today Screen in foreground.
It happened to me as well once I started to force 'exit' on all the apps instead of just minimizing them. Part of Pocket Plus close button.
I'm not sure if this is the same case as you are experiencing but it looks like after the Messaging program is completely terminating, the softkey cannot launch the complete program. I was still able to launch it from the start menu with no problems (sounds very strange, I know).
The way I recovered from that is to put the "Messaging" program in the exception list of the close program; this way it stays in memory and I get the messaging complete program every time I press the softkey now.
I *Hope* that helps...
maybe???
interesting thought... well, i don't use that program BUT i am using smartkey and that likely shares the same process SO i will try that from now on after soft-reset and report back...
Thanks for the tip! It's definitely one of those hard to track down the cause kind of issues, how did you come about that as a solution?
MobileMute is a little program that allows you to mute/unmute phone calls via a hardware button. It will also launch any other program of choice if a call is not in progress (that way your hardware button doesn't get wasted). I had searched for this functionality for while without much luck. So, I decided to write a quick little app to do it for me.
For those of you who had used the first version of this, you may have noticed the slight delay when running the program. This was because it was designed to start, do its thing, and then exit. That being said, it took a second for the program to initialize on startup which resulted in a delay.
I have changed this version to try to figure out what button you have it mapped to. If it can figure that out, it will stay active listening for future pushes to that button. If it can't figure out what button is mapped, it will act just like the first version (which is still functional, just with a slight delay).
I have also added a simple configuration utility for changing the settings (located in Program Files/itsallwright/MobileMute).
I originally developed this for my Kaiser, therefore it was originally posted in the Kaiser section. But, since it can work on other devices, I am posting the new version here. The only problem is that different devices have different button IDs. I will post some instructions for getting your button IDs on the devices that the default Kaiser button IDs don't work for.
I didn't test this version for as long as I tested the original. So if you have any weird problems with it, please let me know.
Original version is posted here http://forum.xda-developers.com/showthread.php?t=386810
Edit: Added MobileMute_v2.1 which adds support for more devices and Kaisers with non-standard ROMS.
Enjoy,
Jay
Button IDs
Here are some instructions to help find the button IDs.
If you do not have Visual Studio or another spy program, I saw a post here http://forum.xda-developers.com/showthread.php?t=251955 that might be able to help.
1) Open Spy Program and connect to device
2) Expand "Desktop Window"
3) Expand all child windows titled "Phone" (or whatever your "Phone" title is)
4) Locate the "Phone" window that has a child named "Mute" (or whatever your "Mute" text may be). If you can't find the correct Phone window, it is possible that is hasn't been started since the last reboot. To start it, make a quick call until you get the call status and hang up. Now you should be able to locate the window.
5) The next steps should be made while you are on a call, so make a call to Voicemail, yourself, or a patient friend . After the call is connected, make sure you are on the "Call Status" screen (the one that has the mute button on the screen).
6) Highlight the "Phone" window found previously and click the Messages button to view messages for that window. You will probably see messages continually being posted to the window.
7) Click "Menu" at the bottom and then click "Mute" (Note: do not click the "Mute" button on the screen as that will not give us the information we need.)
8) Click "Menu" at the bottom and then click "Unmute" (Same note as above applies)
9) Disconnect the call. The message window should stop getting messages.
10) In the message window, find all messages titled "WM_COMMAND" (there should only be 2)
11) The WPARAM value of the first WM_COMMAND message is the "Mute" button ID (Put it into a calculator to convert it to a decimal number)
12) The WPARAM value of the second WM_COMMAND message is the "Unmute" button ID
If you do find your IDs and confirm they work, please post them here with your device and ROM info to save others with that device the trouble.
Thanks,
Jay
just use volume up/down to mute incoming calls...
zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.
jhw549 said:
If I'm not mistaken the purpose of this app is not to mute the ringer during an incoming call but to mute the mic during an active call. Also when not in a call it will launch your app of choice so when not in a call you're not occupying an otherwise usable button.
Click to expand...
Click to collapse
That is exactly what it is for. It is very usefull if you have to attend a lot of conference calls where you are not required to participate 100% of the time.
Jay
zuNN said:
just use volume up/down to mute incoming calls...
Click to expand...
Click to collapse
This won´t work with my Kaiser with M-Diamond 1.4 ROM.
MobileMute_v2 with HTC Fuze
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.
HTC Fuze and MobileMute
I have now tested the original with the HTC Fuze with similar unsuccessful results.
sounds like a great app ill give it a go on my hermes tonight. thanks for sharing!
JVH3 said:
I have tried version MobileMute_v2 with the HTC Fuze and it does not appear to work. It will launch the program defined in the settings when not on a call, but will not mute the call, when launched while on a call.
I am launching this from the PTT button through the methods described in another thread. I created a shortcut short_ptt.lnk, which launches this application.
I have also navigated directly to the executable and run it while on a call and get identical results.
I am going to uninstall version 2 and try installing version 1.
Click to expand...
Click to collapse
This is most likely because the Fuze button ID for Mute/Unmute is different then the Kaiser.
Have you tried using the steps above to get your button IDs?
-Jay
Mobile Mute and Fuze
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.
JVH3 said:
I had also tried running the executable directly, not through the remap of the PTT key.
I did that to elliminate the possibility of it being a mapping to a key issue.
This does assume it works when run directly and not from a key.
I suppose it is possible that an exeception is thrown when the program checks what key was pressed to launch it, if there was not key pressed to start it.
As is, with the Fuze, the touch screen has on screen buttons for Mute and Speaker Phone.
I have remapped the long_ptt to Voice Command and the short_ptt to {"\Windows\ctlpnl.exe" cplmain 1} which gives you the lock screen so I can quickly change the timeout. I like it to lock quickly when not running GPS, but not lock at all when running GPS, but this last paragraph is not related to Mobile Mute, other than I no lnger have an available button to map it to.
Click to expand...
Click to collapse
Check in "/Program Files/itsallwright/MobileMute" for an ErrorLog file. If that file exists and has info, post the contents and I will see if I can figure out what went wrong.
Since it does launch the program you have configured when not in a call, the program at least initializes. If it also launches the program when you are in a call then it can't find the "Phone" window or the "ConnectedText" value. If it appears to do nothing while you are in a call, then it is likely that the Button IDs are wrong.
-Jay
Fuze
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?
jhw549 said:
Trying to use this app on my Mogul/Titan without success. I set it up on the button that would normally be conn mgr, went into cfg and set it to \windows\connmgr.exe
When I go to use the button I get a wait icon, the program launches and hides (still visible in Task Mgr). Opening manually works equally well (not at all).
The tools in the 2nd post don't work ("Class not registered" error).
While in a call the application launches (with a massive delay I might add) then performs its functino properly and mutes the call, no delays after initial launch.
There is no error log in the program's folder.
Help?
Click to expand...
Click to collapse
The initial start of MobileMute does have a delay. That is the reason I created v2 that will stay running. If MobileMute shows in task manager after you run it, then it found the hardware button you have it assigned to and is listening for future presses of that button. Since it does Mute/Unmute the calls, the program is functioning as designed.
As for running "\windows\connmgr.exe". I also cannot run that program (even manually). I don't think it is an app to be used that way. Are you sure you don't actually want to run "\windows\CommManager.exe"?
-Jay
Heh.... umm... oops >.<
That's rather embarassing lol... You're completely right, I picked the wrong exe. It works 100% perfectly now.
I just wish it would hide completely and not show up in my tasks list... I have a tendancy to hit that kill all button rather than pick them out one by one.
thanks. this is a good idea... i'll be using it.
v2.1 with Fuze support
itsallwright said:
A friend of mine with a Fuze let me check it out and I determined why it does not work.
The dialer on the Fuze has Mute/Unmute buttons on the screen, but the buttons do not have text (I suspect it uses seperate Mute/Unmute images instead). That being said, MobileMute determines the Mute State of a call based on the text value of the Mute/Unmute buttons. Therefore, it does not know what command to send.
I am trying to figure out a way to work around this, but in the meantime, I am sorry to say the Fuze is unsupported.
Just as a fyi... the Mute/Unmute button IDs for the Fuze are the same as the Kaiser (21408/21409)
I'll keep you posted on my progress with supporting this device.
-Jay
Click to expand...
Click to collapse
Well, it turns out that the Fuze isn't the only device with that dialer. I recently found a ROM (Phoenix v2) that has touch flo and a similar dialer to the Fuze. I put that ROM on my Kaiser to reproduce this issue on my own.
After quite a bit of research and learning, I found a way to detect the Mute state of a call via TAPI. The Mute/Unmute button text is no longer needed.
I have no way to test with an actual Fuze, but I am pretty confident it will work now. I have added the new version to the original post.
-Jay
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
jpn621 said:
I've got v2.1 loaded. Detection on Fuze works, the registry shows mute/unmute id's 21408/21409. I'm using the short_PTT.lnk method. When I press PTT, I can see the titlebar flash 'MoblieMute' text.... but the mic does not mute.
Click to expand...
Click to collapse
When you are not in a call, does it open the configured program (BubbleBreaker by default). Also, if you look in task manager, is MobileMute listed?
-Jay
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Frequently Asked Questions:
Q: Is there a way to disable the program window that pops up after a soft-reset?
A: There is no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
Q: When receiving a call, does the answer button and screen stay locked?
A: The answer button and the screen both unlock when the phone is ringing. If the call is answered/ignored/stops ringing, the screen will be re-locked.
Q: Will it work with my phone?
A: This program has been confirmed to work on a few models. I believe that it should work on pretty much any touchscreen device running Windows Mobile. Please, try it and tell me if it works!
Tested Phones:
Kaiser (ATT Tilt)
Touch Pro (Fuze)
Xperia
racer7 said:
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Click to expand...
Click to collapse
Nice one mate!
I assume you can also use this on a Touch Diamond??
neways, I will give it a shot....
Thanks for your work
Regards
Jeroen
thanks
racer7 said:
I have a Kaiser, and there's nothing more irritating than accidentally bumping a button while having the phone in your pocket, then having random things in your pocket scroll through your address book until it calls someone. Or opens up IE and finds a high-bandwidth website. When you don't have a data plan.
Things like this hurt. I've been trying to find a solution to it, and I happened to stumble upon an olllllld application on another forum. It's called AutoLock. I found it Here.
Anyways, long story short, it uses the built-in Windows Mobile screen lock and turns it on whenever the phone's screen turns on. So hitting the power button is enough to lock your phone. It's super convenient, and for the most part, it's not too buggy.
I've been using this for probably over a month now. It's a lifesaver. I had the .exe on my SD card, and every time I reflashed, I had to make a new shortcut and place it into the startup folder. So tonight, I made a CAB file out of it.
I hope you guys get as much use out of it as I do.
A quick note: It runs in the background. Terminating it will not allow it to function. The CAB will add a shortcut to the startup folder, so a soft reset will start it. Otherwise you can start it from the shortcut in the Programs folder.
Click to expand...
Click to collapse
this is a very usefull program.is there anyway to disable message screen when program start after softreset?thanks a lot in advance
It's unfortunate that I didn't create this program. I only found it through about six months of searching on the internet. Maybe a friendly XDA-Developer could write a similar program and keep it updated with new features!
As far as I know, there's no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
As for if it works on a Diamond... go try it and tell me how it works!
Awesome program! Thanks
Looks interesting. Thx for sharing!
racer7 said:
It's unfortunate that I didn't create this program. I only found it through about six months of searching on the internet. Maybe a friendly XDA-Developer could write a similar program and keep it updated with new features!
As far as I know, there's no way to disable the message screen on startup. Just hit the X in the top right corner, and it should minimize out of sight.
As for if it works on a Diamond... go try it and tell me how it works!
Click to expand...
Click to collapse
yep i am just hitting x .it works in my xperia without problem.thanks again.
So what happens when a call comes? Does it lock the answer button too? And the screen?
kull said:
So what happens when a call comes? Does it lock the answer button too? And the screen?
Click to expand...
Click to collapse
Since it's the inbuilt Windows Mobile locking setup, when a call comes in, the phone is still locked, but the answer skin floats above the lock. So the screen "unlocks" so you can answer or reject the call, but it locks as soon as you answer or ignore it again.
I've discovered, using my Jade, that you can do the same thing by just setting the built-in Windows Mobile device lock to 0 minutes... You'd need to provide a password, though...
First press of the power button puts the phone to sleep... Press it again, it will ask for your password to unlock...