Related
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.
I have just got an XDAIIi and have tried both of my bluetooth headsets with it.
The Jabra 250 works but is inconsistent with it's pickup of the call. It sometimes takes 2 presses of the button to answer.
This could create the problem of dropping the call with the 2nd press if you've got the call but think you haven't.
The Motorola HS801 however works fine every time.
Point of interest... it appears to suffer from the yellow screen when viewed from an angle but it doesn't present a problem for me as I usually look at it head on.
The screen is certainly much brighter than the old XDAII I have.
It's a great machine marred only by the clunkey O2 active interface.
However I don't intend to mess with it yet and remove it.
Xda IIi Extended ROM
Bro anyway to extract the Extended ROM from your Xda IIi please?
TIA.
I have tried the unlock tools that worked on my XDA2s for unlocking and unhiding the extended rom, but they dont work on my XDA2s. i did not get ant errors, but it did not show up.
the screen on my XDA2i is good same as original XDA2, far better than the orange tint on the 2s screen
John
I'l try and extract ExtRom when I get some time ....
I have temporarily solved the active interface issue by removing it from the startup folder and speed increase is incredible...
I'l try and extract ExtRom when I get some time ....
I have temporarily solved the active interface issue by removing it from the startup folder and speed increase is incredible...
Bakerk
what did you remove from the startup menu to stop the o2 interface loading.
I have installed the v1.5 of o2 Plus (running with the small icon mode to make it quicker) but what do i remove to stop the main o2 screen from loading
all i have in that folder is
camera_detect
CheckAutoRun
Connections
IA_CID_Startup
o2 plus for XDA ( i nstalled this)
poutlook
RunBT
stk
thanks
John
applecom said:
Bakerk
what did you remove from the startup menu to stop the o2 interface loading.
I have installed the v1.5 of o2 Plus (running with the small icon mode to make it quicker) but what do i remove to stop the main o2 screen from loading
all i have in that folder is
camera_detect
CheckAutoRun
Connections
IA_CID_Startup
o2 plus for XDA ( i nstalled this)
poutlook
RunBT
stk
thanks
John
Click to expand...
Click to collapse
Remove "Connections" then soft reset.
JD
Just upgraded to WM 6 Official. But found that the bluetooth cann't receive and send files to other devices. is there any registry that I missed?
or cab for fixing the bluetooth?
Greatdane said:
Just upgraded to WM 6 Official. But found that the bluetooth cann't receive and send files to other devices. is there any registry that I missed?
or cab for fixing the bluetooth?
Click to expand...
Click to collapse
I am facing the same problem after upgrade to WM6 official. Previously in WM5, transferring file was flawless. Anybody have a workaround?
-Red-
On my T-Mobile Ameo, I had to return it as faulty as I couldn't activate the bluetooth radio after I upgraded to WM6... I've heard that there may be a batch of T-Mobile devices with problems with the Microdrives and bluetooth radio...
Luckily, I got mine replaced under warranty... thought they might kick up a stink about the OS...
I don't think its a hardware problem.
its a software problem i think....
Dear seniors.. need help here..
I have the same pb with my P3600. It is impossible to have any bluetooth services associated to it... HELP ??
Greatdane said:
I don't think its a hardware problem.
its a software problem i think....
Dear seniors.. need help here..
Click to expand...
Click to collapse
Which device do you have? Ameo, x7500, x7501, u1000?
Can you use BT headsets with it?
Have you tried to use a BT mouse?
I know it's probably a silly question, but have you gone into Start...Settings...Connections...Beam and ticked the box that says Receive all incoming beams?
I wasn't able to receive files until I ticked that box.
I am, using Dopod U 1000.
I can use bluetooth handsfree without any problem.
just file sharing make me headache. and my desktop computer also can easily send file to my U1000. but just won't receive from "himalaya" ( xdaII).
and won't sent any file out of it.
To all seniors, don't you have any prob. with WM6 in Dopod U1000?
WM6 And Bluetooth Problem
Hi all
I had the same problem sending and receiving files after upgrade. Now i resolved the problems with following steps
1. Pair those devices
To send a file
1. Set to accept without confirmation on receiving device.
2. then send the file from athena
Receive a file
1. In beam accept all incoming beams
2. In bluetooth settings>> Mode tick on Make this device visible to other devices ( if you use a BT headset this option untick itself, May be on mine)
3. Then send the file from other device it works
Make sure the send device paired with athena as "active device(OBEX)" not the "Audio enhancement"
I hope this may resolve the problem sending and receiving. May be something else contributed to this solution. If this not works then remove the today plugin which is associates with bluetooth and try send and receive.
Good luck
Thanks mate!
Indeed I faced this problem accidentally yesterday after flashing a new rom on my trinity!
The problem with me was that I had turned the beam off - which i thought was only for infrared!!!
To add my two cents let me say that there's also in the registry a place where the key says 'obexenabled' or something similar. check for that (there is found in two places) and set it to 1. If you search for 'obex' you cannot miss it.
cheers and thnx for the assistance.
sabes143 said:
Hi all
I had the same problem sending and receiving files after upgrade. Now i resolved the problems with following steps
1. Pair those devices
To send a file
1. Set to accept without confirmation on receiving device.
2. then send the file from athena
Receive a file
1. In beam accept all incoming beams
2. In bluetooth settings>> Mode tick on Make this device visible to other devices ( if you use a BT headset this option untick itself, May be on mine)
3. Then send the file from other device it works
Make sure the send device paired with athena as "active device(OBEX)" not the "Audio enhancement"
I hope this may resolve the problem sending and receiving. May be something else contributed to this solution. If this not works then remove the today plugin which is associates with bluetooth and try send and receive.
Good luck
Click to expand...
Click to collapse
inspectorgadjet said:
I know it's probably a silly question, but have you gone into Start...Settings...Connections...Beam and ticked the box that says Receive all incoming beams?
I wasn't able to receive files until I ticked that box.
Click to expand...
Click to collapse
thought this was for IR only !!!!
file transfer via BT is working now !!!
thanks
Just want to know if there is any Cab for
Mouse Mode in WM6
i saw a video - HERE
hi everyone, I'm using O2 XDA Atom Pure, and the ROM is AKU 0.3 CHT(0.7CHT stable version hasn't release)
I have a problem, when I use pushmail, after serveral hours the actvieSync would stop and shows "Waiting for network", even though I press the "Sync" button, it still shows "Waiting for network", and mail also cannot be push to my cellphone.I have to soft reset to make activeSync work,but this problem still occurs after a period time.
I've already check my GPRS netwwork settings, it's all fine and setting are all correct,and I did not install any software that will affect ActiveSync,so anyone could help me to solve this problem? otherwise the pushmail function is not useful for me....
verseaucus said:
hi everyone, I'm using O2 XDA Atom Pure, and the ROM is AKU 0.3 CHT(0.7CHT stable version hasn't release)
I have a problem, when I use pushmail, after serveral hours the actvieSync would stop and shows "Waiting for network", even though I press the "Sync" button, it still shows "Waiting for network", and mail also cannot be push to my cellphone.I have to soft reset to make activeSync work,but this problem still occurs after a period time.
I've already check my GPRS netwwork settings, it's all fine and setting are all correct,and I did not install any software that will affect ActiveSync,so anyone could help me to solve this problem? otherwise the pushmail function is not useful for me....
Click to expand...
Click to collapse
did you launch the hand writing pad (small) ad may I know which version you are using?
dcoloane said:
did you launch the hand writing pad (small) ad may I know which version you are using?
Click to expand...
Click to collapse
I'm using 0.3 CHT fixed By Jiggs,not dcoloane version.
I didn't launch small hand writing pad but in SIP menu, small hand writing pad is in the list, should I disable this hand writing pad?(how?)
I also see there is a dcoloane version which is made by you, but I found you write:"Sunglobe.ttf is used instead of mingliu.ac3, wince.nls is 1.5MB from CE-Star". I don't know if mingliu is instead by sunglobe will made system fonts unclear or not?
verseaucus said:
I'm using 0.3 CHT fixed By Jiggs,not dcoloane version.
I didn't launch small hand writing pad but in SIP menu, small hand writing pad is in the list, should I disable this hand writing pad?(how?)
I also see there is a dcoloane version which is made by you, but I found you write:"Sunglobe.ttf is used instead of mingliu.ac3, wince.nls is 1.5MB from CE-Star". I don't know if mingliu is instead by sunglobe will made system fonts unclear or not?
Click to expand...
Click to collapse
no it won't, I subsitide the font because I will receive Simplify Chinese SMS and it seems that sunglobe is a better font for both CHT & CHS.
The FIXED version had problems (unstability) on Active SYNC because of the SIP's not really PORT from the same version of the original ROM. Some SIP's are from AKU2.2 WM5 while some from dll's from other devices. The final one is one package get from WM5 AKU2.2 which should minize the impact on system stability. Although I still did not figure out why the small hand writing pad still causing problems. If you really want to use Push Mail often, i suggest you use back AKU2.2 or the final ROM by me, before flashing the new ROM, just use PCBckBackup your SMS, Contacts, Tasks and Calendar stuff to the SD Card. But if you don't want to flash again, Use only Chanjie as SIP instead of the HandWriting.
Well, although this post is pretty old...
I've always been having that problem. Even after some years I still can't tell the reason.
The solution I've been using since then is to restart ActiveSync on the phone using the task manager (which probably does the same than a complete soft reset, but is a lot faster).
Since I've upgraded my Diamond with a new firmware ActiveSync is displayed in the list of active tasks. Using another task manager I killed the process which still didn't help. In another post here I read that disconnecting your Gprs/3g connection might help. So it did.
Using Google you can find a lot of board posting from users with that problem. Noone has found a real solution and Microsoft doesn't seem to care about it.
What I am curious about is: Does your Exchange server have a dynamic IP?
Mine does. And PushMail is only active during the day. The daily disconnect of my provider is somewhen in the night. So when Active Sync starts again the following morning it's beeing confronted with another server ip. Maybe that's a possible reason?!
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.