Hi people.
Just wondering
1) is there a way of getting rid of the default Bluetooth icon/software from the xda after installing the Widcomm drivers? I dont like the 2 icons at the bottom.
2) is there any way of stopping the message "bluetooth could not be correctly initialized" when the xda goes to sleep.. this occurs seemingly randomly and even when BT is switched off.
thanks
Hi,
You can remove the standard BT icon by using a registry editor and removing the following key:
[HKEY_LOCAL_MACHINE\Services\BTIcon]
I'm afraid I don't know how to prevent the annoying error message though
How to turn off default Bluetooth icon
For question 1, just use any Registry Editor and go to [HKEY_LOCAL_MACHINE\Services\BTIcon] and change the key "Keep" from 1 to 0, then reset your device. The icon should be gone. I've attached the registry file here if you want to use it.
For second question, I need someone to upload BTPWR.DLL which is from HP device. I believe this is the power managment file for bluetooth.
Oops, forgot to attach file... :lol:
I found that when I changed "Keep" from 1 to 0 in the key HKEY_LOCAL_MACHINE\Services\BTIcon], after reset my device ran VERY slowly, at one point I thought it was stuck on the first flash image that appears. I found that if I deleted the whole of the key, my device performed as normal.
excellent. thanks guys. i'll give that a shot. I'll keep waiting for a solution for the errror message
Bluetooth Error-Message at Startup/Boot
The Error-Messages appear, when the "old" Bluetooth App is active. The XDA-Standart-BT-Stack offers 3 options: ON/OFF and available (in German: Erkennbar). I've hab the same problem. I installed the new Widcomm-Stack as described and got those Error-Messages. After deactivating the old BT-App (select BT OFF - described above) I could restart the XDA without any Errors. After that you might change the registry-key, so that the old BT-Icon disappears.
By the way, in my experience the new Widcomm-Stack has more functionality (FileTransfer, etc.) but is very unstable. For example: ActiveSync-Connections often break down, etc.
stopping the message "bluetooth could not be correctly
dcs is right, changing "keep" from 1 to 0 in the key [HKEY_LOCAL_MACHINE\Services\BTIcon] sometimes make the device starts very slow. Instead you can either set "dll" to "" or delete the whole registry key (someone told me on his XDAII deleting that key also make the device run very slow I don't know whether that is the case or not...).
To stop the message "bluetooth could not be correctly initialized", try to change "InquiryDuration" from 8 to 4 (or less) in the key [HKEY_LOCAL_MACHINE\SOFTWARE\WidComm\BTConfig\General]. I did that and the message seemed to go away...
how do u disable the ms stack completely, as mine starts automatically, and refuses to stop...the icon refuses to allow me to stop it?
You can disable the bluetooth by turning on the flight mode, as sometimes the widcomm drivers go out of bonds and they loose control over the BT.
If that happens and you cant disable it, just turn on flight mode.
Related
Over the past couple of months I've noted a few bugs with my O2 XDAII running Windows Mobile 2003. Are all these bugs well known and have they been fixed by the ROM upgrade 1.60?
- XDAII crashes occasionally when asking for a password just after being switched on, showing a blank white screen or flickering password entry screen even after the password has been entered. I have my password set to a 4 digit code and 5 minute delay. This seems to happen when a reminder or call wakes the device up.
- XDAII sometimes doesn't wake up for reminders (the XDA also suffered from this problem)
- when the GPRS connection is active, there is no option to "disconnect GPRS" within the radio menu pop-up box (which opens up when you tap the signal strength indicator). The only way to close the GPRS connection seems to be by holding down the red "end call" hardware button for 1-2 seconds.
- no "x" at the top right of the phone skin sometimes, when a call comes in that wakes the device up. This means you have to open another program to be able to go ack to the phone skin and close it.
- sometimes XDAII device doesn't switch off after 3 minutes, although the screen does dim after 1 minutes (the 3 minutes and 1 minute are what I have set in my power settings). This seems to happen after GPRS use or Bluetooth being switched back on?
- the phone skin doesn't always recognise the caller from the contacts list and just shows the number, even if the contact is in the contacts list.
- when looking up a name in contacts for sending an SMS message you need to add "+" in front of 44.... as this doesn't seem to get included, which prevents messages from getting sent properly
- the bluetooth headset does not interact properly with the XDA II, it sometimes doesn't connect or disconnect the headset properly, you cannot flip out the bluetooth boom to answer a call, you cannot voicedial (this is a big disadvantage, is there any software available which makes this possible?) and you cannot long-press to reject a call. Although I use a Motorola HS810 headset the problem is with the XDAII headset profile.
I am aware that the bluetooth headset and SMS "+" problem have been discussed in this forum but have the others been noticed and fixed in the new ROM?
Regards,
Rafil.
Hi everybody.
I recently installed Pocket Bluetooth Tools on my M1000 and overall I find the utility excellent. I sync my M1000 at both home and work so removing the necessity to rebond everytime is excellent. Additionally, enabling a 60 sec Bluetooth period before switching off is also a handy facility.
However, I have one query.
The developper describes a Profile 1 and Profile 2, both of which are visible on the Today plugin screen, which can be user-defined to such options as "bluetooth always on" or "bluetooth switches off after 60 seconds" etc.
This would be handy to use however to date, I have found no method of actually accessing a "profile editor tool" or something similar. There's no Pocket Bluetooth Tools icon in either Programs or System, I can find no executable file on m M1000 anywhere so I now find myself in a position where I cannot turn Bluetooth on for more than 60 seconds unless it's doing something.
Any ideas? I've tried emailing the developper but with no response to date.
F
Just put it on #1 then adjust the power settings for the screen etc, and click on the little clock on the Today screen. This will make the bluetooth stay on when the clock is greyed out.
Switch to number two and adjust the power settings for the screen etc and you will have two different power settings.
dewild1 said:
Just put it on #1 then adjust the power settings for the screen etc, and click on the little clock on the Today screen. This will make the bluetooth stay on when the clock is greyed out.
Switch to number two and adjust the power settings for the screen etc and you will have two different power settings.
Click to expand...
Click to collapse
Cheers for that. It really is that simple. My mind works too technically sometimes!
F
Okay so I think I know at least A solution but I'm hoping that someone here will be able to suggest something besides a hard reset.
I've got a Cingular 8125 a couple of weeks ago. Flashed it to the latest imate rom. I kept it from installing the custom imate stuff but did install some of the Cingular cabs.
Now I'm having a few problems with the phone. It's quite a list.
A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.
B) the phone HAS been locking up. It will just sort of freeze and stop responding. Sometimes I'm able to get to the memory settings in control panel and still have available memory (it's usually been around 16 MB of program memory when this has occured) but even so closing everything will often not help. Even if it unfreezes then it will usually do so not much later and often it just won't unfreeze.
C) sometimes I can't close out the phone application. This seems to happen when Magic Button is running. I click to close it and it goes from the phone to my call history. Closing that goes back to the phone again. I can't get to the Today screen. Pressing the red hangup button would sometimes fix it but usually not.
D) voice command is REALLY wonky using my BT headset (Scala 500). Okay, I know it doesn't officially work with BT headsets and I could live with that. But why does it have to be so damned random?
1) Sometimes pressing the button once will get me the chime. Usually it just gets me a lower pitched tone. If the first press doesn't get it then typically a second within a short time will. Sometimes it takes three though.
2) At one point the phone would usually play my selected ringtone and announce the incoming call over the headset. Other times I would only get the default incoming call sound on the headset and the phone and voice command announcement are over the phone speakers instead. In the last couple of days I've ONLY been getting them from the phone.
3) While typically when I'm using the headset with voice command the feedback DOES come over the headset, sometimes it gives me the confirmations from the phone instead
I think there were a few other flaky issues too but this is the majority of them. Also many of them were present before the rom upgrade so I don't think it's responsible for most of it.
edit: oh, one other thing is that after the ROM upgrade I can't get the default input to stay on anything but keyboard. Even if I change it, I turn around and it's back to keyboard again. I'm thinking, though, that there's a reghack for this?
*bump*
===A) I can't enable wifi at all. At one point I could but the phone locked up on me while I was trying to resetup my connection. I had no choice but to soft reset it. Now I can't enable wifi at all. If I click on it in the comm manager to turn it on it will sit there with the spinning wheel like it's enabling then go back to the same icon with the x on it. I've tried turning flight mode on and off, etc but nothing seems to help it.==
I have the same problem with you. Can anybody help?
any solutions i have the same problem
Try this: back up your PIM, then flash phone back to OEM ROM (cingular, t-mobile, whatever it is for your model). Then unlock it again (if needed), and flash the ROM again. If it's still garbage, try reading the thread for the ROM you loaded (chances are you're not the first to experience this problem, and the other testers of that ROM may offer solutions). If it's still garbage after all that, consider using a different ROM altogether. CRacing's CR86 Touch HD and SVI's ANGEL are both quite nice, and VERY reliable for functionality.
hi
when i goto settings and set it to the time out i want i press ok fully come out it works fine, but when i turn the phone off then back on they go back to the original settings not the ones i changed
help
Hi please tell us the make and model of your phone and what rom you are using and if you have done any mods.
Also check the registry at HKCU\control panel\backlight - settings are there for battery and ac timeout etc..
Hi, I've got the same probs.
I have an i-Mate K-Jam with AKU2.
When I set the backlight timeout on battery to 1min, and put it in standby, it constantly reverts to 10 seconds. :evil:
Ever tried that? It sucks.
Also tried the registrykey mentioned above, but that does not work.
When I set the timeout via the GUI, I can see the change in the registry, so far so good.
But when the KJam goes in standby, it reverts back to 10secs.
The only way it does work is to disable the timeout completely
The backlight won't go out that way, but is draining your battery.
Especially when listening to MP3's and don't need any backlight.
PS: I don't want to do a hard-reset (yet), I want to wait until aku2.2, then I have to install the KJam again anyhow.
Hi,
since a couple of days I'm facing the following strange bug:
- I start a call, get connection, screen goes out: all okay for now
- I end the call, I loose network connection (an "x" is next to the antenna symbol)
- I can perfectly start a new call or receive one!!
- As sms can't get through (outgoing) because "no radio connected"
- the phone dialer screen says "phone off"
- when I check the Connection Manager it says "airplane mode"
- switching of the "airplane mode" is not possible
- when I press the power button (into sleep mode), and press it again (even immediately), unlock my S2U2, everything is back to normal. Very briefly I see (on the S2U2 screen) a switch from: network name => no service => network name. I don't even need to enter my PIN.
Side note: when I end the call before it gets connected (AND the connection vibrate), nothing happens...
I first encoutered this behaviour after installing SmartLock 1.7E (http://forum.xda-developers.com/showthread.php?t=505032).
I removed it shortly after. Searched the registry, but couldn't find anything.
Problem of course remains.
Anyone has a solution, hints, things to try...?
Thanks for reading!
BartV
try this.. uninstall everything new. clear all cache. Soft reset. See if it returns to normal. If unsuccessful.. try hard reset.