This Patch is compatible on the Blueangel and Himalaya
This will fix the tiny issue when receiving SMS while the Device is in the suspends or off MODE.
Problem occurs when the device is turned off and a sms arrives.
Following are the two cases than can occur when the Device is in the suspends MODE when the TEXT Message had arrive.
On most occasion, the device will vibrate but it will not turn the device on and it leaves them unaware of the new SMS especially for other who disable the vibrate for New Text Notification.
On worst cases, the SMS is not receive until the device is turned on.
This little program attempts to fix this two possible issue by turning the DEVICE ON when it receives a SMS.
And for the Second case, it happened when the tmail.exe(Inbox/Messaging) is close by other program that closes an Application when the "x" or "ok" button is tapped like SPB Pocket Plus, Magic Button, Vbar, Wisbar etc..
If you are using SPB Pocket Plus or Wisbar it is always recommended to include \Windows\tmail.exe in your Close Exception.
PS.. This is just an attempt and probably not the best solution. Use this tool on your own risk.
Written by Toenaild
Orginal link Here!
i've downloaded the files... now how do i use them?
thanks!
It just work by it self, after you install it )
it's working. great fix.
Sorry to ask the same question again, i've downloaded the files (4 files)
but my computer doesn't seem to recognize the files and can't be open or install.
Pls help!
TQ!!!
ramram said:
It just work by it self, after you install it )
Click to expand...
Click to collapse
I've successfully installed it, but the problem continues.
Same here..installed the cab...problem still there
I've been playing with different ROMs now for the past couple of weeks, and am very impressed - they all seem far less prone to the lock-ups I experienced with my OEM WM2003.
But I can't get NotifyLink (used by my company to push emails) to work with *any* of the pre-made ROMs I've been using. I've not been able to complete the registration process - although I'm told that my authentication string has been accepted, I never successfully receive the "registration messages" that are then sent. These are needed to create an account on my PDA, without which I'm unable to proceed. [I've always wondered what form these registration messages are - when received on a WM2003 device the icon is similar, but clearly distinct from the standard SMS icon]. The application seems to die after approx. 10 seconds, with no error message, and certainly no indication of the expected messages being received.
I have a working GPRS connection - I can load pages using Mobile IE.
I'm hoping that someone may be able to help, although I've not seen much mention of NotifyLink in these forums! I don't want to have to go back to Wm2003 ;-(
Further information - I originally got error messages from the application on attempting to find calls from Microsoft.WindowsMobile.Status. I found a ZIP containing this DLL within another thread - having dumped these DLLs in the same application as the executable, these errors disappeared. I also have found that the application and the MS SQL database have to be installed on the Device rather than on RAMdisk. I'd investigate this more should I be able to get a working system.
Many thanks for *any* help!
Resolved by move to WM6
matkinson said:
But I can't get NotifyLink (used by my company to push emails) to work with *any* of the pre-made ROMs I've been using. I've not been able to complete the registration process - although I'm told that my authentication string has been accepted, I never successfully receive the "registration messages" that are then sent.
Click to expand...
Click to collapse
Just in case anyone ever suffers the same fate...
Never did get this fixed with any WM2005 ROM, but I don't suffer this problem with helmi_c's Tofclock dedicated WM6 ROM. I don't claim to understand why - one notable difference is that the .Net CF calls were resolved, so I didn't have to supply the DLLs.
All now working well, if I could stop my battery losing 60% over night!
Circumvent Device Lock in Blackberry Connect for Windows Mobile
---------------------------------------------------------------
Description:
------------
BBC features a security module that, if configured and activated, locks the device after a specific amount of time.
In a corporate environment this is usually set up by a security policy which is pushed to the device via Blackberry Enterprise Server (BES).
If the device is locked the user has to enter a password to unlock the device again.
There are two ways a user can compromise the security implied with the BBC security service.
1) Using a task manager a user can deactivate the BB security service (bbsecurity.dll) which is responsible for enforcing the security policy. The BB service itself is not affected by stopping the security service as long as the device is not rebooted. Thus the security policy is no longer enforced but the user is still able to use all other BB features.
2) The BB security service does not block all user actions during device lock. Only the screen overlay is enforced but applications might still be started using hardware keys. There are several ways to misuse this flaw. One for example is if a voice command software is installed, the user can still send voice commands to the device. If Microsoft Voice Vommand is installed and bound to a hardware key and the device gets lost or stolen a malicious person can press the voice command hardware key and ask for upcoming appointments, dial numbers etc. which leads to information leakage.
Affected:
---------
Blackberry Connect (BBC) for Windows Mobile PocketPC 4.0.0.97 (only version tested, but suspectable all currently available 4.x versions)
Not Affected:
-------------
Blackberry Connect (BBC) for Windows Mobile PocketPC 2.x
Workaround / Fixes:
-------------------
None
Vendor Contacted:
-----------------
14.05.2008
Vendor Response:
----------------
None
How to deactivate it?
Hi,
I am looking for long time how to deactivate this security feature and would be interrested how to schedule with a task scheduler the dll??
Could you please advise how to do this?
Thanks
jsimpson said:
Hi,
I am looking for long time how to deactivate this security feature and would be interrested how to schedule with a task scheduler the dll??
Could you please advise how to do this?
Thanks
Click to expand...
Click to collapse
You cannot deactivate it completely since the policy is enforced after each softreset. As I wrote you can use a task manager to stop the service, but you should under no circumstances stop it permanently because your device will not come up anymore if the service is completely disabled.
So to get back to your question; No, I cannot tell you how to do it with a task scheduler as the only way I know is using a task manager.
One can write a small utility to stop the service and after a softreset one can run this program to avoid using a task manager for that, but AFAIK there is no such program.
mmm After being happy when I put the WWE HTC rom on my TMO Vario IV and after managed to install and initialize Blackberry Connect .103 I got disappointed when the BB security lock came in the first time.
I cannot set the lock-timer higher than 15 min.
Its extremely nasty when I am driving using Tom Tom navigator.....have to type the password every now and then (I have the feeling not exact 15min's!).
I tried the stop-service trick, but that one appears non working with (at least) BBC version .103 and .104 on my device.... Without running BB security service the device wont wake up or soft-reset itself.
Has anyone encountered these new issues with BBC 4 security lock and has anyone found a solution yet???
Was thinking to let the security lock active (preventing my device from locking up or soft-resetting spontaneously) and to build a script that runs in the background checking whether or not the security lock screen is present. And once it is...pastes the security code in the box and pushes OK.
Does this sound do-abe?
edsub said:
Was thinking to let the security lock active (preventing my device from locking up or soft-resetting spontaneously) and to build a script that runs in the background checking whether or not the security lock screen is present. And once it is...pastes the security code in the box and pushes OK.
Does this sound do-abe?
Click to expand...
Click to collapse
Do the same for GOODLINK and you got a deal!
Well I managed to fix this like I mentioned.
Attached are 2 Mortscripts that to run in background from \Program Files\Mortscript
(I have a shortcut in \Windows\StartUp to make sure it is run when my devices is reset, so i do not have to start it myself after every reset, but thats optional)
The 1st script is for general purpose: It just makes sure you will not be bothered again by the BBC security screen
The 2nd script only works when TomTom navigator is active.
You simply choose which script suits your needs best. Both can be run at he same time also I suppose.
The 1st script, BBCUnlock.mscr, simply waits for the security screen, sends the appropriate keystrokes (leftsoftkey, password, leftsoftkey) and restarts itself (to wait for the next security screen popup).
Beware:
1. Enter your own password in the right placxe in the script before using it.
2. Comment-out the last line until you are absolutely sure the script works (remember: 10 wrong passwords deletes all BBC data on your device!!)
It runs in a couple of seconds (which you see happening)
The 2nd script, NoLockTTNVGA.mscr, only works when TomTom Navigator is running: Every 10 minutes it taps the zoom-in and zoom-out hot-spots in TomTom's 3D view (based on VGA resolution!!), before re-launching itself again. This makes the security time-out will never happen as long as TomTom is running.
Update:
The NoLockTTNVGA script works flawlessly, but only fixes the issue when TTN is active
The BBCUnLock script has some glitches. Apparently it locks up my device when
- a reminder 'stays active' for some reason.
- TomTom Navigator is active (but that can be fixed whith the other script!)
The script can be run simultaneously. And when you have TTN: for now they must!
Not sure how to make the BBCUnLock script more stable, any help appreciated.
Hi edsub,
Thanks for your efforts so far. Up to now I have used MemMaid in my startup files so that after a soft reset, I have to firstly unlock the Blackberry and secondly the MemMaid then kicks in and I disable Blackberry Security in Startup Services. This means the security is overridden until my next soft reset as you already know. Therefore, I don't need to install the mortscript for TomTom.
However, I am particularly interested in the other mortscript you have given. I want to be able to simply soft reset my Diamond and then just leave it, without having to (1) input my password and then (2) disable the Blackberry Security in MemMaid.
I think your mortscript is possibly the answer to my prayers.
However, I have installed it to my device and also installed MortScript v4.3.0.2 Beta. I am concerned that (1) I am a beginner & this is too advanced for me and (2) running mortscript will eat up my battery.
I have renamed the extention on your file with .doc and input my password overwriting the appropriate parts) on my desktop and then renamed the extention back to .mscr and then installed in the MortScript folder back on my Diamond.
In MemMaid, I have put the Mortscript and Autorun .exe's into the Startup Items section, so this should run after a soft reset.
However, my Diamond does not unlock itself. What am I doing wrong?
I really appreciate any help you can give me. I am very much a newbie with this program!
I am persevering with this, but cannot get it working. I have put a shortcut for Mortscript.exe and the BBCUnlock.mscr into my Windows Startup folder using MemMaid. I have also tried to change the order of the programs starting on MemMaid, but this does not seem to have any effect on inputting the password. I have obviously changed the word "secret" to "mypassword" in the BBCUnlock.mscr file. I have also tried just putting the BBCUnlock.mscr (without the Mortscript.exe) in the Startup folder.....
I would appreciate your help edsub...
Update:
I have managed to get the BBCUnlock.mscr work during normal operation, but it does not work for the password immediately following a soft reset (it does work thereafter).
This is already a huge improvement as I don't need to then disable the Blackberry Security from MemMaid following a soft reset. However, how can I get it to work for the password immediately following a soft reset?
Please help edsub!!! This is the final ingredient to my perfert Diamond!!!
I think the Mortscript does not run until AFTER the Blackberry Security has been unlocked for the first time following a soft reset. I have tried to change the order of the shortcuts on MemMaid, but haven't managed to succeed. Can anyone offer any help PLEASE???
I have tried some more things too:
Added in a sleep timer of 5 seconds from sensing the "owner information" to pressing the left soft key and also increased the time from pressing the left soft key to inputting the password. It works great in normal mode, but still doesn't work for the single password required immediately following a soft reset.
Also I have tried to put not just a shortcut into the startup folder, but the actual mortscript itself. Plus the shortcut!
I can't believe there aren't more people with this problem. Edsub has certainly created a wonderful mortscript here. It is nearly perfect and I'm sure others would want it if it worked for ALL password inputs required.
Can anyone please help????
I guess Mortscript is not running before the password is given for the first time. I have this behaviour too. So i have to give the password myself right after reset. After that the Mortscript takes good care of it.
edsub said:
I guess Mortscript is not running before the password is given for the first time. I have this behaviour too. So i have to give the password myself right after reset. After that the Mortscript takes good care of it.
Click to expand...
Click to collapse
Hi Edsub, nice to see you back! Thanks for the reply & PM. Your Mortscript programme is still the most important programme on my device! I did try to re-order the start up processes on SK Tools so that the mortscript would start before the Blackberry security, but I couldn't get it to be more important in this way!! Now I have a Diamond 2 and am hoping not to have to soft reset at all. I have another problem now - I can't seem to get BBC working at all on this phone, but that's another story.....
EdSub, as you are my hero for getting the Blackberry security to sort itself out via your Mortscript programme, I wonder if you can write another Mortscript programme for this: http://forum.xda-developers.com/showpost.php?p=4381321&postcount=89?
I would be very grateful!! I think other Blackberry users would be too.
Hi,
Maybe the question is idiot, but reading the first post, I was wondering why not create a small script which would simply deactivate bbsecurity.dll on startup... If I read it well, doing this once would be enough, and have no impact on the BB service itself...
Using a small sleep, it would be easy to put this script directly in the windows startup folder so that the sleep leaves enough time for the dll to start, and then deactivate it...
Isn't this possible?
Thanks
bbdoc said:
Hi,
Maybe the question is idiot, but reading the first post, I was wondering why not create a small script which would simply deactivate bbsecurity.dll on startup... If I read it well, doing this once would be enough, and have no impact on the BB service itself...
Using a small sleep, it would be easy to put this script directly in the windows startup folder so that the sleep leaves enough time for the dll to start, and then deactivate it...
Isn't this possible?
Thanks
Click to expand...
Click to collapse
Edsub already did this with Mortscript. It doesn't de-activate it completely, just senses when the code is required and then enters the code. I would like a script which does what you are suggesting.
mitsi said:
Edsub already did this with Mortscript. It doesn't de-activate it completely, just senses when the code is required and then enters the code. I would like a script which does what you are suggesting.
Click to expand...
Click to collapse
Yes, I know this script, and I'm using it... It's working quite good, even if it sometimes misses the code, don't know why... but I'm a bit worried about battery consumption linked to the fact a script is constantly running only for typing this password every 20 minutes... Deactivating the dll would probably be a more efficient solution, but maybe this is not possible using mortscript...
bbdoc said:
Deactivating the dll would probably be a more efficient solution, but maybe this is not possible using mortscript...
Click to expand...
Click to collapse
You can use the attached program to stop the service. Just execute it and the service will be stopped. However, you have to do this after each softreset. I recommend to wait until the connection is established to the RIM network and then use BBStopSec.exe
Hope this is what you were looking for.
That's indeed what I was looking for... I'm just surprised it's an .exe and not .mscr...
Is it something you compiled yourself? The idea I had with the mortscript was to add a sleep before stopping the service, because this way, I can simply put it in my startup folder and it will launch automatically after a soft reset... As far as the first lock screen will only come after 20 minutes, I could even put a sleep of 10 or 15 minutes before stopping the service and I would never get my screen locked...
Hi all... I have exchange set up with push mail at work (a few if us are testing it instead of using expensive Blackberry licences).
So far it works really well (if a little battery sucking!) apart form the annoying password that constantly pops up after a few minutes. Our IT guy has tried to lengthen this to no avail! None of the Blackberry's do it so why on earth do our WM devices have to do it? I can understand it happening once the phone had been switched off, as if it's knicked then when the thief switches it on they ned apassword, but every fgew minutes? Boy is that tedious!
Any help would be greatly appreciated!
adamelphick said:
Hi all... I have exchange set up with push mail at work (a few if us are testing it instead of using expensive Blackberry licences).
So far it works really well (if a little battery sucking!) apart form the annoying password that constantly pops up after a few minutes. Our IT guy has tried to lengthen this to no avail! None of the Blackberry's do it so why on earth do our WM devices have to do it? I can understand it happening once the phone had been switched off, as if it's knicked then when the thief switches it on they ned apassword, but every fgew minutes? Boy is that tedious!
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I use Direct Push to connect to an Exchange account (both on a TP and on the Diamond). No Rom I have installed on them has had this problem - I only ever put in my password once and it remembers it and never asks for it again. I have also used Direct Push on several previous WM phones (5, 6 and 6.1) and have not had this problem on those, either!
This may be a silly question, but did you tick "save password" when setting up the exchange account on the phone?
The PIN requirements are set on the server side (i.e. Exchange) so you need to have your IT guys look there. It's easy enough to setup. Your 'blow away' device settings are also defined there.
We run about 600 WinMo devices with Direct Push on our private APN and have the password timeout set to 30mins accross the board (as defined by our security policy, auitors would really like 15 mins or less ). This has been running for several years and over many generations of device (inc. several Raphael's now) and the PIN timeout has always worked as expected.
Remember you CAN override the timeout on the device to lower the value (15min lock rather then 30 etc., the server just defines the MAXIMUM time that the device will remain unlocked without requireing the PIN and what the constraints of that PIN are). You configure that like you would expect from the Lock control panel.
You have to use SSL connection
Maybe you need more postage
Thanks, I will talk to IT again as they said 15 was maximum they could do! Even though it didn't seem to reset once set previously.... I think its a silly system anyway though. If I wanted a password I would set one up... if not then I should be able to have my phone set up so that only the email needs that lockout password added so sync not the whole blasted phone!
adamelphick said:
I think its a silly system anyway though. If I wanted a password I would set one up... if not then I should be able to have my phone set up so that only the email needs that lockout password added so sync not the whole blasted phone!
Click to expand...
Click to collapse
I'm sure your IT department have a totally different answer to that!
You're walking round with potentially confidential company information in your pocket. Personally I think it's perfectly reasonable that they insist that you have to password protect your device so that if it is lost or stolen, no-one can get at the sensitive company information that you may have on the device, even if it is only out of your sight for a couple of minutes!
As it is an Operating System on our phones there's no reason MS couldn't have passworded EMAIL separately from other functions - makes sense to me. They give you the option to PW your phone or not (personal choice) but I agree that company information should be safeguarded.
Do blackberry's have this same password stuff that locks the phone completely? I don't see my boss having to type in passwords to unlock his blackberry every five minutes!
adamelphick said:
As it is an Operating System on our phones there's no reason MS couldn't have passworded EMAIL separately from other functions - makes sense to me. They give you the option to PW your phone or not (personal choice) but I agree that company information should be safeguarded.
Do blackberry's have this same password stuff that locks the phone completely? I don't see my boss having to type in passwords to unlock his blackberry every five minutes!
Click to expand...
Click to collapse
Yes, Blackberries do this as well. It depends on your corporate security polcies. We cannot connect iPhones or Nokia mail for exchange phones, as our IT group cannot broadcast the security policy to the device. These security policies are the main reason why BB and WinMo own the enterprise market in the US.
Hello together, I am new here (well, at least as poster)
I've got a used XDA Diamond Pro (aka Touch Pro, german O2 branding) and try to "move in" form my old Prophet.
The new thingy can soooo much more, but the actual reason to change was the shiny look and the hardware keyboard - from both I am a bit disappointed in the last four weeks I try to get used to the new device...
But my actual problem is this:
On the Prophet I use ozBT 0.76 to automatically switch on Bluetooth when a call comes in and I drive in the car and the hands-free setup should take over. Works great there.
Now I want to move this over to the Touch Pro. ozBT 0.76 runs. Fine. It starts the BT when I start the telephone app to start an outgoing call. Fine. But the other way (which is the more important one) does not work: Incoming call does not start the BT. When checking this, I found, that the WM 6.1 does not start the full telephone app (german window title "Telefon"), but only a notification dialog with a accept and a deny button.
Now - how do I tell ozBT (or any other program which needs a program name or window title to ask the task manager process whether something is running or not) what to watch out for? i.e. what is the name of the process behind that notification dialog?
Hi again,
the problem is solved - and a little bit more tricky, than I had expected:
(1) The phone app is cprog.exe and it runs as long as the phone is booked into a network - so that is not the right solution...
(2) The first line in the notification window is "Eing.Anr." (german for inc. call) - et voila ozBT switches the BT on for "#bEing.;" in the "title begins with" section. So I can continue to get used to the touch pro now...
(3) General startegy next time someone needs a prog. name for ozBT:
most likely, the window title starts with a letter. So try in "starting with..." with "A", "B", etc. until you have the first letter, then continue with the second letter, most of the time that is anyway enough...
TS