Can somebody tell me how to beam a Word file from one XDA to another XDA? I have set all settings on both device correctly. However, nothing happens. The sender just shows a screen were it says that I have to align ports, which I do ofcourse. Please help
Goto Start, File Explorer, open My Documents and tap&hold on the file you
want to beam and select Beam File.
If the receiving party has "Receive all incoming beams" turned off under Start, Settings, Connections, they'll have to use the "Receive an infrared beam" under "Programs".
HTH
Thanks, but your suggested procedure I have already tried. I have tried all possible possible combinations. Nothing works. Also when I activate "Receive an infrared beam" the receiving XDA doesn't give any reply. It is almost if a XDA can't send to another XDA; if the IR doesn't work at all. I still hope somebody explain the trick to me. It is important for me to know how it works.
does the infrared works with other devices like a laptop or a pc with a usb->infrared ?
somebody said at once point that hvaing stuff connected like a keyboard would disable infrared support
That's right. The Keyboard driver seems to disable the IR port. Uninstall the driver and it should work.
I haven't installed a keyboard. So there is nothing to uninstall. Or do you refer to the preinstalled standard keyboards? They are in ROM so I can't unistall them. Is there another trick?
Thanks
If you installed the folding keyboard driver from the kitchen rom, it will initialise every boot and grab the com 1 port, I know because I couldnt get my gps working even with the beams setting turned off, however you can disable the driver, bearing in mind it will initialise again after a reset. I cant remember where to do this as I got rid 2003 and the problem was when I had it installed, I am pretty sure the option is there somewhere to disable it.
Related
After upgrading to ROMKitchen 3.17, the infrared port has stopped working. It does not send or receive anything. Why could it happen? It was working very well before upgrading. If any application that involves IR, that is beam file, ActiveSync by IR causes the XDA to hang. IR Receive gives message "Unable to establish an infrared connection while mobile device is connected to the desktop"
"Unable to establish an infrared connection while mobile device is connected to the desktop"
Click to expand...
Click to collapse
Dear,
I had a similar problem once and for long until I realized that some of my other softwares were interfering with the IR Port. If you have any software that requires all-time active connectivity status of any kind (i.e. keyboard driver), disable it before using the infrared.
HTH
Dear Ken,
I guess that is where I went wrong! There was a foldable keyboard software that was creating problem!
Thanks
I have similar problem with AT&T PPC2002 (XDA developers Special Edition ROM v1.2). The phone was bought with this ROM, so I didn’t try with other versions.
When I run ‘infrared receive’ application or try to beam any file my phone simply hung till I soft-reset it. It may be the conflict with other programs but I not sure. How to check who else uses IRDA and how to remove those programs/conflicts?
Help please and thanks in advance
Please tell me how did you end the problem because it seems that i have the same thing with my XDA II
I wish I could end up with this problem... but I still not. It does not vitally critical since I don’t need IRDA functionality so far. But having feature (IRDA) and knowing it does not work for unknown reason driving me mad. PROBLEM STILL EXISTS AND I HAVE NO CLUE WHAT TO DO.
hello everyone
i need help to connect my infrared keyboard to my o2 xda atom exec
after the installation of o2 xm-02 keyboard i went to it i ticked active keyboard and error message cam up " can't open infrared port. please close the application infrared port using or reset your device "
can anyone help me to resolve this issue and thanks in advance
Hicham
easy
in phone settings uncheck the receive incoming beams and it will work
drjumanji said:
in phone settings uncheck the receive incoming beams and it will work
Click to expand...
Click to collapse
if that is infrared tools , it should be check NOT UNCHECKED or else u cannot use any device for infrared.
thank you
drjumanji thank you very much
Has anyone had success beaming contacts or appointments to another XV6800 after the DCD 2.3.2 upgrade? I can not connect with my wife's XV6800 - her's has the stock ROM still.
IF IR is hosed - is there a way to do this with Bluetooth?
SOLUTION - The only change I made to the 3.0.0 ROM was to modify (thanks azclown) as follows:
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
Then I found out that Pocket Informant 8 was the rest of my issue. I can beam now and send contacts or appointments via bluetooth. The option to send via bluetooth is no longer displayed on the PI8 menues, but just select beam - then when the beaming dialog comes up it will first try to find a IR beaming partner - wait and it will start selecting bluetooth devices next - pick the one you want and voila!
j-squared said:
Has anyone had success beaming contacts or appointments to another XV6800 after the DCD 2.3.2 upgrade? I can not connect with my wife's XV6800 - her's has the stock ROM still.
IF IR is hosed - is there a way to do this with Bluetooth?
Click to expand...
Click to collapse
When stock, I was able to beam files from my laptop to my phone using the laptop's send-file-over-BT utility. I can no longer do this under DCD 2.3.2. Perhaps our issues are related. The radio itself works (BT headset functions fine), so it's something in the new software.
Guys, I think he has IR Beam disabled....
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
this should enable beaming and IR.... I'm not 100 percent on this so if someone else knows better please speak up.... All I know is that I can xfer files using Beam..... edit this using any standard reg editor....
No dice...
azclown said:
Guys, I think he has IR Beam disabled....
; ***** Disable IR Beam *****
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Obex]
"IsEnabled"=dword:00000000 <--------- change to 00000001
this should enable beaming and IR.... I'm not 100 percent on this so if someone else knows better please speak up.... All I know is that I can xfer files using Beam..... edit this using any standard reg editor....
Click to expand...
Click to collapse
I made this change, recooked the Rom in the kitchen and no dice. My souped up XV6800 can't connect with my wife's standard ROM XV6800 (no small amount of teasing going on over this!)
Any other ideas?
im dealing with this same thing. just wondering if anyone else had any more insight
Same issue in DCD 3.0.0
I'm using the kitchen almost stock from DCD, I switched to Verizon, anded the HTC X key and adobe reader, but that was it. The only other change I made was that listed in my previous post to enable beaming. That does not seem to do it. Is there, perhaps, some other item in the kitchen that DCD removed that further disables beaming?
i am just using the base image that dcd compiled the time before the kitchen came out. i think its 2.3.2. when i went into that registry setting, my enable was already set to 1. i hate to say this (never thought i would) but i really need my IR haha
Had this same problem but finally got it to work out last night. I'm using DCDs 3.0 rom. 1st make sure under HKLM\software\microsoft\obex IsEnabled is set to 1. Next make sure under comm manager settings ---> bluetooth ---> mode tab ---> turn on bluetooth and "make this device visible to other devices" are both checked. Also check and make sure under settings ---> connections tab --->beam ---> receive all incoming beams is checked. That should do it. I got it working fine last night on 2 different moguls.
liemydude said:
Had this same problem but finally got it to work out last night. I'm using DCDs 3.0 rom. 1st make sure under HKLM\software\microsoft\obex IsEnabled is set to 1. Next make sure under comm manager settings ---> bluetooth ---> mode tab ---> turn on bluetooth and "make this device visible to other devices" are both checked. Also check and make sure under settings ---> connections tab --->beam ---> receive all incoming beams is checked. That should do it. I got it working fine last night on 2 different moguls.
Click to expand...
Click to collapse
Using 3.0.0 also - I tried that change to the obex IsEnabled key - and still nothing.... did you include anything else in the 3.0.0 kitchen?
Guys you do not need to mess with the registry to enable OBEX. Just go to the comm manager and enable Beam and also go to the connection settings and enable the beam from there. Make sure you able visible in bluetooth also.
I did this and was able to send files using the OBEX through bluetooth.
Try it out.
edit. you will notice that once you do this that you check the settings in the registry that obex will go from 0 to 1 in the registry.
my bluetooth works perfect. what i need is the ability to IR. any insight on the IR problem specifically?
Mills00013 said:
my bluetooth works perfect. what i need is the ability to IR. any insight on the IR problem specifically?
Click to expand...
Click to collapse
IR uses OBEX i believe. And when you want to send something through OBEX it uses the same protocol for bluetooth and IR. (Beam Feature)
What exactly is wrong with your IR. Because I tested mine and it works when i sent a document to my old Moto Q.
[email protected]$ said:
IR uses OBEX i believe. And when you want to send something through OBEX it uses the same protocol for bluetooth and IR. (Beam Feature)
What exactly is wrong with your IR. Because I tested mine and it works when i sent a document to my old Moto Q.
Click to expand...
Click to collapse
Carlos - did you include the enterprise section or some other section from the kitchen - maybe that is helping you because I do have all of those settings as you described and still can not beam or set up for obex bluetooth transfer.
j-squared said:
Carlos - did you include the enterprise section or some other section from the kitchen - maybe that is helping you because I do have all of those settings as you described and still can not beam or set up for obex bluetooth transfer.
Click to expand...
Click to collapse
No I did not include the Enterprise Settings, but I will on my next ROM (other reasons)
So you made sure that you enabled beam on the Comm Manager and on the connections settings for "beam" turned on bluetooth and made your device discoverable?
From there where you able to pair with a bluetooth device? such as you enabled the required authentication tab on security and connected to another bluetooth device?
P.S. What exactly are you trying to OBEX to? Are you sure that the computer or phone has OBEX enabled or that the settings are set the same to yours?
From there when you try to beam a file or receive a file what errors do you get?
I dont get any. I just right click an object select beam and make sure that the other device is visible and i send it to the device.
I think I found the problem....
I have beaming and bluetooth working now. The settings didn't change from my previous post, but I wnet back to my old Ipaq 4350 and beamed and sent appointments to my xv6800. Then it occured to me - the Ipaq is running on Pocket Informant 7 not the new version 8 in my xv6800.
I tried sending files via bluetooth and IR beaming from Resco file explorer and it works fine - so I think my issues are with PI8. I'll head over to the web-is forums for that....
solved
See first post - I added solution there.
Hi guys
could any one please be so kind as to help me with a problem im having.
i have a spv m5000 on orange which i have change the mother board over with a o2 exec mother board running windows mobile 6.1 seems to be working fine no issues however i have tried to pair both my gps units with it but to no avail, i have a Holox BT-541 and a navicore BT-GPS-32354D i have tried both of them and have same problem,
my xda see's them and adds them fine but when i try to connect to one in the xda it says unable to connect or wrong passkey i have used 0000 for holox which thats what it says in the holox pdf but have also tried 1234 but i think this is a com port problem i have tried all com ports some will go in ok but still cant connect to gps i also tried this "go into TomTom and use the NMEA devices with baud rate of 38400" this did not work, before i changed mother board i had these working fine on older tomtom and original spv m5000 mother board so i dont know if this is a win mobile 6.1 problem or not i see quite a few people with same problem but no solution that worked for me any way.
i have seen thred taking about pairing before tomtom installation but not sure that will fix my issue as i think i tried to pair before i installed any way.
has any one any ideas on this any help would be really appreciated this is getting to be a pain in the rear!.
also there is an icon in the system tab "external gps" can any one tell me the correct settings in there ie for program tab and hardware tab what com port and baud rate should be and whether the manage gps auto should be ticked
many Thanks in avance for any help you can give here.
Kind regards
Daz
Ok found solution,
after spending way too much time on this crap! I finally found the issue as I stated I thought
it was a mobile 6.1 issue and I was right, in mobile 6.1 they have added a external GPS shortcut
in system tab it is here the problem exists.
my problem was resolved by the following procedure.
On your XDA go to Start/Settings/Connections click on Bluetooth short then add new device once it has found it
enter passkey 0000 or whatever yours is once it has made the first connection then do the following,
1. Under "device tab" click on your unit and make sure the serial port is "UNCHECKED" disabled then click save.
2. Under "Mode tab" make sure (Turn on blue tooth) and (Make this device visible to other devices) are "CHECKED" enable them.
3. Under "COM ports" select a port, I chose 0 don't think it matters but if so chose another but remember what one you choose.
4. Under "Security tab" Authentication (passkey) required "CHECK" enable it click ok to come out of Bluetooth.
5. Under "System tab" click on "External GPS short cut.
6 Under "Programs tab" select (None) for GPS program port.
7. Under "Hardware tab" select port 0 or same as you gave your Bluetooth com port and issue the "Baud rate" 115200 or lower rate.
8. Under "Access tab" Manage GPS automatically (recommended) "CHECK" enable
9. Finally check your xda is blinking a blue light and turn on your tom-tom software it should now pick it up, all done.
Final note it seems that Microsoft have made one more buggy operating system, no change there then LOL
and as a result you can't seem to use the blue tooth pairing process as intended so this is a working work around
one more thing there is a 2nd bug found and that is when you turn off your GPS unit and try to use your xda you might
find that your last page froze up here you will have to mess around with it i.e. try turning off your tom-tom software first
and then your GPS, Thanks to bill gates for yet another windows operating system that doesn't work as advertised.
Well we had Hendrix king of rock, Marley king of reggae, Elvis king of rock'n'role then there's you bill gates king of crap!
Long live the king!!!!! LOVL
A big thank you goes' out markanthonypr on xda-developers for pointing this out, nice one m8
http://forum.xda-developers.com/archive/index.php/t-476940.html
hope this comes in handy for others "knowledge is the real king give it freely"
regards to all
Muzz
I was able to use the interface of the Blueinput.apk (from Teksoft) by installing it under the alternative keyboard method of moving the apk from data/apps to system/aps and then reboot. You should be able to select this "keyboard" on long press. Assuming you have already run the program with BT on and your keyboard paired and connected, (and in my case my Mogo BT mouse) you can type with your bluetooth keyboard.
The mouse has no cursor and is a bit jittery, but it works. My mouse functions as a three button mouse and the center button backs you out of a program to the home screen.
BlueInput force closes
Sorry to revive a slightly old thread, but I figured it would be better than starting a new one.
I tried to do this with my gtab on TnT Lite 3.1.1, but BlueInput force closes on me when I try to launch it, press the pairing button at the bottom when an input box is active, or access the keyboard settings in the settings menu.
These are the exact steps I performed:
Downloaded BlueInput version 1.7.202 from www .teksoftco. com/index.php?section=blueinputandroid&tab=download
Copied the blueinputandroid_signed_1.7.202.apk to my /sdcard/
Opened Root Explorer
Copied /sdcard/blueinputandroid_signed_1.7.202.apk
Navigated to /system/app
Mount R/W
Pasted blueinputandroid_signed_1.7.202.apk
Longpressed blueinputandroid_signed_1.7.202.apk
Permissions
Checked: User Read+Write, Group Read, Others Read
Mount R/O
Restarted gtab
Opened a text input field (Google Search widget)
Longpressed text boxt -> Input Method
Selected BlueInput
Pressed the pairing button on the bottom left (BlueInput icon)
Force Close
I've tried this with bluetooth off, bluetooth on but not paired, and bluetooth on and paired but not connected (Apple Wireless Keyboard).
Would anyone happen to have any tips as to what I've done incorrectly?
Thanks in advance.
Hello
I just installed 3.1.1 for the first time last night. I also just installed Blueinput from my saved APK. I ran it.. it loads fine. I then did the fix by moving the apk to /system. Ran it fine. Turned on Blue tooth. Paired my Mogo mouse just now. Went into a dialog box. Long press and select Blueinput as the keyboard (it does not render a dot in the box, but it activates it as the keyboard). Mouse works fine. I assume my keyboard will work as well. Not sure why you are getting FC. perhaps is is an old version or something. I am running BlueInput 1.6.131
@joncwchao
Did you also install the ap? I got the fc folling your steps, then i installed the app...
Did you try to install it normally first to see that this new version runs? If not, try to get the previous version install it normally, make sure it runs, then move it to /SYSTEM/APPS. Then reboot.
EDIT: I downloaded the new version 1.7 and confirm it works. I am typing with it now.
What Bluetooth Keyboard are you using? I had the Microsoft 6000, but it would not work. It would show up and act like it was working, but would only make a clicking noise. No letters would show up. Now I am using a USB keyboard which works pretty well. Thanks!
I am using a DEALEXTREME apple BT clone. Works great. Small enough but not miniture either.
Whoops
Yeah ok that was my mistake, I was moving the installer .apk instead of the installed app .apk.
Both the 1.7 and 1.6 versions work.
I'm using the official Apple Wireless Keyboard, which I got for 65.99 (WOO $4 savings on boxing day sigh).
Is there any way to make it so that it DOESN'T come up with the text input box taking up the entire screen every time I press on a text input field? I know that this BlueInput fix is (hopefully) temporary since bluetooth will be rolled into the custom firmwares eventually, but it's a little annoying lol.
[email protected] said:
What Bluetooth Keyboard are you using? I had the Microsoft 6000, but it would not work. It would show up and act like it was working, but would only make a clicking noise. No letters would show up. Now I am using a USB keyboard which works pretty well. Thanks!
Click to expand...
Click to collapse
USB keyboard along with Blueinput???? Do you mean you are using USB keyboard with your android?
[email protected] said:
What Bluetooth Keyboard are you using? I had the Microsoft 6000, but it would not work. It would show up and act like it was working, but would only make a clicking noise. No letters would show up. Now I am using a USB keyboard which works pretty well. Thanks!
Click to expand...
Click to collapse
go and send a text to someone and hold down in the text area for a few seconds then select input method. choose blueinput make sure you have it enabled under keyboards/languages.
program works great cept they want $20 for the serial #