Hi
I'm looking every where to solve this problem, how to receive file through bluetooth when the ppc power off?
Could some body help?
If you know software please name it.
Thanks in advance
no electricity, no workee
thezoltar said:
no electricity, no workee
Click to expand...
Click to collapse
As u know
When u use power saving the tel. still on and u can make calls through the blutooth headset
If u r receiving file through blutooth and the power saving close the screen the transmission stops!!!
I used Dr.Yar bluetooth 1.51 software & I used to receive the files even when power saving (when I had wm2003se 2.06).
Is some one have explanation?!!
The_hesham said:
As u know
When u use power saving the tel. still on and u can make calls through the blutooth headset
If u r receiving file through blutooth and the power saving close the screen the transmission stops!!!
I used Dr.Yar bluetooth 1.51 software & I used to receive the files even when power saving (when I had wm2003se 2.06).
Is some one have explanation?!!
Click to expand...
Click to collapse
I'm sure I've received bluetooth files while on power saving. The PPC was woken up for the notifications and I still had to press Yes to accept the file at the end but it was initiated in power saving... As for the original answer you did say when the ppc power off - not power saving. So the original answer was correct in that respect.
Related
In the setting of "telephone"is the opportunity to set the device to automatic answering after 1-15 rings. That would be ideal when you are having a BT headset, because you would not have to press on the headset button. However, this does not work. Is there a setting in the registry to make this work?
press the green phone button then go into tools>options
then click on the more tab and youll see Automatic pickup
if not on your wm2003 then get a registry editor and go to:
HKEY_CURRENT_USER>ControlPanel>AutoPickup
change the Auto Pickups value from 0 to 1
and Ring to what ever you want (mines set to 3)
hope this helps u
gaz
Thanks for your advice. I already performed the actions and in the registry it is all set. However, on my XDA II it does'nt work. I also tried to use the wired headset, because I know from my regular phone that there it only works when you have the headset attached, but nothing , nada.
Any other suggestion?
aint got a clue then mate sorry
As far as I know this option has never worked, its a OS bug.....
It didn't work on my XDA with 2002 and 2003, and it doesn't work on my MDA II with the latest MDA update. Maybe somebody has worked out this thing, in that case I would be very happy to hear about it because I agree, it's a shame we cannot use it.
It seems that an auto pickup is possible ONLY if the wired earphones are plugged in. So maybe it's possible to simulate such situation with some kind of software, or registry changes, but without swiching off the phone speaker and microphone?
Does anyone else have this problem? I answer the call by pressing green handset button but the calling party and myself cannot hear each other for about 3 to 4 seconds....
I ahve ahd some callers who were about to give up just as we were evntualy able to talk. If this is a fault, then I need to get it looked at under warranty.
:?:
bakerk said:
I answer the call by pressing green handset button but the calling party and myself cannot hear each other for about 3 to 4 seconds....
Click to expand...
Click to collapse
Long shot, I know, but - do you have Towa's Bluetooth Tools installed? They can cause such behaviour.
Cheers
Daniel
I have the same issue, the work around is not to answer until the third ring!
The problem only occured for me after loading imates 1.72 rom on my XDAII
ta
Christian
I did have pocket bluetooth tools installed and have now uninstalled it.
I had it installed because it turns on bluetooth on an incoming call and is handy when using the Jabra 250.
However it follows that maybe the delay is causd by this very switching on of BT so I'll report back when it's had a good testing.
The ROM I am running is not the newest one quoted in the second reply and if this is a side effect of installing that rom then I will stay as I am...boy does that delay bug me
thnx all
:roll:
Ok all...problem solved...it was the bluetooth tolls that cause it...uninsatlled ans now no delay.
Thanks all for your help :lol:
I also experience delay, but i cannot uninstall pocket bloutooth tools because then my BT GPS won't work anymore
Is there a way to disable this headset functionality in pocket bluetooth tools because i don't need it, I only need com port for BT GPS... Is there any alternative solution for MDA-II ?
Tnx in advance,
Davor
Hi
Does everyone have this issue of the BT turning off when you hit the power button?
I have the following conifguraiton
ROM 1.72 BB version
Bluetooth Tools
ya i have the same problem...
ratnamg said:
Hi
Does everyone have this issue of the BT turning off when you hit the power button?
I have the following conifguraiton
ROM 1.72 BB version
Bluetooth Tools
Click to expand...
Click to collapse
I wish I could get the Bluetooth to come ON on my PDA2K...
I have the latest Club iMate ROM AND Bluetooth Patch- and am unable to activate bluetooth at all.... every timie it warns of insuffecient driver memory and tells me to soft reset- and regardless of the number of times I soft-reset my device- It give me the same warning-
As for the 802.11 WiFi- it is slightly more stable- but quite often I have trouble getting it to power up as well..... "usually" a single soft-reset solves this issue- but sure is irritating-
I thought the new PDA2K in ALL its names/forms was going to be the answer to my not wanting to carry 3 devices with me... but I think soon I will be carrying a GOOD BLUETOOTH phone and a PPC [NON PHONE] to use with it again...
So far as I can tell, the PDA2K is 'functionaly' one of the WORST PPC's i've ever owned....
well its normal... if you push the off button the phone will go off.. even activesync disconnects because.. well... its off...
Does anyone know why I have virtually no bluetooth services other than headset and modem ?
Even my old Nokia 6680 could OBEX file transfer - Is this locked in the 'Wizard' by O2 ? Can it be tweaked ? I just want to be able to tx/rx files via bluetooth.
Whilst I'm on a rant !! LOL Why can't one activesync via WiFi to the desktop PC ? - Only BT or USB it appears.....D'uh ??
Thanks for any help.
db on cbr100xx said:
Does anyone know why I have virtually no bluetooth services other than headset and modem ?
Even my old Nokia 6680 could OBEX file transfer - Is this locked in the 'Wizard' by O2 ? Can it be tweaked ? I just want to be able to tx/rx files via bluetooth.
Click to expand...
Click to collapse
I found this a couple of days ago via a search for the same issue:
You need to edit the registry.
Enable Bluetooth receive:
HKLM\Software\Microsoft\Obex\IsEnabled = 1 (DWORD decimal)
Click to expand...
Click to collapse
db on cbr100xx said:
Whilst I'm on a rant !! LOL Why can't one activesync via WiFi to the desktop PC ? - Only BT or USB it appears.....D'uh ??
Thanks for any help.
Click to expand...
Click to collapse
Apparently earlier versions of ActiveSync could do this, but MS removed it with later ones for "security reasons".
I found out that that reg tweak does the same as in Start-Settings-Connections-Beam. Tick the box receive all incoming beams and the setting in the registry switches from 0 to 1. I do not advise anyone to change it to a 1 in the registry, since that means that your infrared port is also active all the time, which is battery consuming. For receiving files, just tich the box in the settings-beam menu and you should be able to receive files. After receiving, uncheck it and the infrared port shuts down as well, saving battery power.
re
10x Koksie, I solved my problem. It is very stupid to turn OFF incoming
bluetooth transfers from IrDa control panel !!! I have IPAQ 3715 before with WM2003SE and there are not that stupid ideas ....
Oh, God. I spent months thinking that my BT stack was broken, only to find out that I had to enable OBEX-receive for Bluetooth via the IrDA panel and OBEX-send via the (previously IrDA-specific) "Beam" File Manager option.
Koksie said:
I found out that that reg tweak does the same as in Start-Settings-Connections-Beam. Tick the box receive all incoming beams and the setting in the registry switches from 0 to 1. I do not advise anyone to change it to a 1 in the registry, since that means that your infrared port is also active all the time, which is battery consuming.
Click to expand...
Click to collapse
Well, let me disagree. The additional battery consumption it causes is, in most usage situations, negligable. That is, unless you need to squeeze our every second possible and you can't recharge it for days, you can safely keep it on.
Please see my detailed power consumption tests at http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1184&more=1&c=1&tb=1&pb=1 if interested
Eugenia said:
Oh, God. I spent months thinking that my BT stack was broken, only to find out that I had to enable OBEX-receive for Bluetooth via the IrDA panel and OBEX-send via the (previously IrDA-specific) "Beam" File Manager option.
Click to expand...
Click to collapse
I've discussed this problem & solution a month ago in my blog / articles, see http://www.pocketpcmag.com/blogs/index.php?blog=3&p=1196&more=1&c=1&tb=1&pb=1 for a complete discussion.
Hallo...
I have serious problem and till now I don't know how to fix it. I change the registry to allow the Bluetooth Headset to activate the MS Voice Command, when I click the button on the BT the Voice Command starts fine, but if I want to use it agin, the VC doesn't work anymore, I hear only a "peep" but the programm doesn't respond. I have Qtek 9100 with the last official ROM .
Any idea or solution to fix that ?
I appreciate any comment.
Thomas voicecommand and bluetooth has some issues. Basically, when you use VC the first time it opens the channel with the device, once you have then used it you need to hold the button down on your bluetooth device to close the channel. Then pressing BT again should open voicecommand. There's a number of posst for this problem but hopefully I've given you the basic issue
Thanks for your reply... But no, closing the Voice Channel doesn't solve the problem.. I have tried all that before I post my question, it really works only once and no more, only after restarting my device it will work again for once.
I am starting losing a hope that it can be fixed.
Thomas1234: I started trying to come up with solutions to this a while back but never had time to work on it further yet. Anyways what I came up with so far can be found here. It's not perfect but may work with your headset and make it useable for the most part.
http://forum.xda-developers.com/viewtopic.php?t=49255&highlight=
Note: Scroll down to the bottom of the above thread to get the latest version and you have to be logged in to see the file.
Hi shoey5!
Thanks for trying to help me, but it doesn't work, and it looks like that this file damaged the connection between BT headset and the Voice Command or any Voice calling, even the one by default ( voice calling ) doesn' work anymore now.
I was able before at least to do the voice calling, but now it doesnt work after I changed the registry to default to read from the sddialer.exe file.
Can you please explain me what did the file change so I can change it back if i is possible ?
I did softreset alot, but doesn't help.
Thomas1234: It doesn't modify or change anything, all it does is run resident and resets the Audio Gateway Service after a call has ended if there is a bluetooth device active. Removing it from your startup folder and resetting your device will get rid of it completely.
Are you sure you haven't modifed something else before or after that may have affected your problem. I know this sounds silly but is your volume up, can't tell you how many times I sit there pushing the button and wondering why I don't get anything only to realize my volume is off
BTW, Try this. Leave the program in your startup folder, power off your headset and reset your device, then power on your headset and see if it works from that point on. I've noticed this happens to me with headsets that exhibit this problem the odd time.
Thank you anyway..
I ended up to do a hard reset, because softreset didn't help... It has been worse, I even couldn't dial a number using the BT headset, well I won't say it is 100% because of your file, but I am sure I didn't do anything with the device that can cuse this problems before I applied you file, all this happened just after I installd your file.
I'll use the default Voice dialer then with my BT Headset till maybe Microsoft update its program.
this "ms voice command running only once" happened to me too, with Nokia HS-12W headset.. try using JETware Hands-free Extension for Windows Mobile phones, http://www.jetwaremobile.com/ , and activate ms voice command from its advanced settings.. it worked for me. unfortunately it's not free and it doesn't supply caller names to my hs. hope this helps..
Thanks ozkaya, the program looks useful. I'll try it and see if it does the job correctly.