http://toothing.proboards28.com/index.cgi?board=tchat&action=display&num=1078412493
technology only ever make it if somebody decide to make people relate it with sex somehow
just think about vcr, internet .......
heck these days the 3g company called 3 run comercials which border on sugesting that their video phone could be used for advanced phoneSex
lol crazy old world
Hmmm, after reading the article I now understand 'toothing' is an abbreviation of BlueToothing, but the term sounds rather disgusting to anyone not familiar with the term :?
yeah sounds like something hanibal lector would consider foreplay
Slightly offtopic, but coming from this article I found two applications designated for Bluetooth Messaging/Chat, Bluechat and ProximityMail, both are non-working on my MDA-II
BlueChat seems to incorporate a hard-coded port, and ProximityMail says it can't find a Bluetooth Stack...
So, no proper toothing for me hahaha
Is there any toothing SW working with XDAII?
Have you tried BuZZone from Handango?
Or have you found anything working on your own?
Thanks!
Chris
BuZZone
By the way...
Hello Chris,
Yes, we plan to support Microsoft Bluetooth stack software in future versions. Your XDA II Bluetooth works with this software. Current BuZZone version supports only WIDCOMM's stacks on devices like HP iPAQ, Dell Axim, Asus, Fujitsu-Siemens, etc.
Kind Regards,
BuZZone Team
Related
Hi all
Don't know how many of you guys are ipaq transferees like myself, but there is one piece of software on the ipaq that has not been adopted in the XDA series handhelds, namely REVO - the remote control tool.
Anybody into gadgets in the way that we are will have too many remote controls lying about. This tool allowed me to put them on a shelf, and use them very rarely.
So.....
Does anybody have a clue how to extract it from the ipaq ready to be placed on the XDA II. NAturally, owning both devices, one would assume that providing I use it with either one or the other, you can provide this useful information conscience clear!!!!
Look forward to any thoughts
JJ
jjcodex said:
Does anybody have a clue how to extract it from the ipaq ready to be placed on the XDA II.
Click to expand...
Click to collapse
Unfortunately, the Himalaya infrared hardware is not capable of communicating with customer devices like TV sets. There is nothing any software could do about this - only some hardware change can help.
Cheers
Daniel
Also some Ipaq's Irda are just very powerfull made..have a range of 10-15 meters.
Normally pda Irda's have a range of 2-3 meters.
not sure why the ir would be 100% incompatible with the tv
if special software written for it was used
about the range issue
http://www.smarthome.com/8220A.html
http://www.homeautomationnet.com/Shopping/remote-control-accessories.asp
http://www.pdawin.com/irtranceiver.html
suppose one of these would inc the range
i had
http://www.pdawin.com/
this software running on my xda1
too bad the range was only 30cm
Thanks for the feedback guys.
I am surprised that the range is so different between devices. I understood that the infra red transmit distance was usually further than the receive. Would this be applicable to the XDA II I wonder. I will run some experiments with a phone to see if I can assess distances.
Had a look at the PDA Win software, looks quite functional, perhaps not as slick as the built ipaq version. 30cm range... doh!
They seem to have specifically excluded the XDA II. I wonder if this is a range issue as you guys have suggested.
Hmmm......
Sounds like an excuse to spend money on a very very very posh do-all remote control!!!!!!!!! (LOL)
Thanks for your thoughts anyway.
Cheers guys
Rudegar said:
not sure why the ir would be 100% incompatible with the tv if special software written for it was used
Click to expand...
Click to collapse
Well, TVs use "consumer" infrared, while PDAs use "IrDA". See here for a more detailed explanation. It has nothing to do with the power or the range of the IR LEDs and phototransistors.
Cheers
Daniel
Well, TVs use "consumer" infrared, while PDAs use "IrDA". See here for a more detailed explanation. It has nothing to do with the power or the range of the IR LEDs and phototransistors.
Click to expand...
Click to collapse
and yet i had pdawinøs software working ok on my xda1
and also used it to comm with my laptop so some infrared classify as
both IrDA and consumer
if the range is ok then the only difference i can think of is protocol and that should be possible to work out so that software would work on the xda2
i also had my trusting old hp48 calc working as a remote at a time
prob still have the software somewhere
Well, TVs use "consumer" infrared, while PDAs use "IrDA". See here for a more detailed explanation. It has nothing to do with the power or the range of the IR LEDs and phototransistors.
Click to expand...
Click to collapse
I would have to side with Rudegar on this one, as I have not only used the Ipaq for several consumer devices but the extremely fundamental Palm III (aahhhh those were the days, when a calculator was considered to be a posh option.
I would say, however, that neither successfully worked with a sky remote, which I wonder may be due to two-way data transfer. I wonder if this is the IrDA vs Consumer difference.
I read the link to the Irda page, which as you suggest states that the two are different. I would agree that the two standards are different, but unless built-in hardware compatability is provided to the majority of pda's, there must be a way of emulating the consumer device within the IrDa protocols.
Hmmm... A little out of my depth on this one. Hopefully somebody else can explain!!
Cheers
JJ
The xda 1 I have works fine as a remote control for my tv and dvd etc, I use "learning2 mode to program the xda using the original remote handset. The xda 2 however is total crap as a remote, however if you wish to use it from one position, for instance the couch in your living room, there is a device called an infra red repeater, this allows you to operate an infra red device from a greater distance, I will see if I can find a name for manufacturer but I am sure this device exists, its selling point was enabling you to operate your cable/sattelite box from upstairs even when you had no line of sight to the box. It was a money saver because you could connect your cable/satellite to your upstairs tv instead of having to purchase a second box from the provider and be able to change channels from upstairs.
Guys,
I wouldlike to get inside the discusion because I have almost the same problem and I would like some help.
I also found the hard way that the XDA II does not work as a remote control, then I found this Total Remote software and module that really got myself impressed, I bought it and also the adaptor for the audio output.
Now I am able to output the signals without problem, the software works very fine and control the eletronic equipments without any problem.
But then I got to test the learning mode and then my problems started. The XDA II canot learn nothing! It wont recognize any kind of command that comes from any remote controler. To make sure it was not a problem of the software I tested to more diferent remote controler softwares and they also does not learn. What really make me disapointed is that even touching the controler IR led with the XDAII IRda port, the XDA II can´t learn anything.
I already tried to disable the "receive all incoming beans" and do a soft reset, but this also does not worked.
I am writing this in the hope I am forgetting something and one of you give me any more idea.
OR
To also ask for the more experts, if it is possible to substitute the IRda port with a common IR led found on any remote controler (of course doing some soldering). If there is compactibility between them, I think I will give it a go, since I really whant a remote control on my XDA II.
Thanks a lot
Felipe
thats what i've been saying all along
the xda2's ir modules is not the default ir module which all the remote software is written for
the remote applications would have to be written directly for the modules ir in the xda2 for it to work
i've come across no such applications as of yet
hi guys, i couldnt help noticing that when i previously used nokia 6600 (symbian s60) they had few 3rd party that is able to make use of their audio mechanism during callls. for example, one software can make selected background noise for opposite callers so they think that u are at a train station for example when infact u r silently at home. another software is an on board answering machine, which after the phone rang for a few times it answer the fonecall with your automated recorded voice and recorded a msg left by the caller on the fone. this is convenient for us so we dont need to call back our voicemail and reduce cost as well as some telco charge to use their voicemail service. im surprised these kind of software have not came out for our windows mobile device when its already available for symbian. im sure it shouldnt be that hard to make it. any coder expert wanna give it a go??
cutefox, what kind of searches have you made for this software on this board? Did you have much luck?
V
i already tried commercial such as handango and pocket gear.. even freeware sites also no luck.. jus dun understand why no 1 made one yet.. shouldnt b too hard to make one.. it will be a big market to sell such a software for our ppc phone device now that more devices is coming out..
Cutefox: have you tried searching this board? Let me save you the effort, but it'll be a good idea next time. It's not generally considered possible, at least on WM2003 devices because of both hardware and software limitations. It's not that no one has thought of it before: someone seems to think of it approximately every two days... but there are many many threads on this issue.
V
Look at what I said here...
http://forum.xda-developers.com/viewtopic.php?t=9761
That sums up why we can't do it using the api's available to us now. The funny thing is the way bluetooth sends the audio stream to a headset. Obviously the data is getting there somehow but I suspect it is not (directly) via windows. Dose anyone know if the radio hardware for bluetooth is connected to the radio hardware for the phone? My guess is that if you could write a program that windows "sees" as a headset then you could get the audio that way. But thats a problem in itself.
I would love this kind of program myself. How is it that such usefull devices with so many capeabilities can be kept secret from us. We can't use the camera, we can't get the cell id on towers, we can't programatically controll the partnerships in blutooth, we cant get the audio stream of our own phone, the events on some ppc's that control brightness are secret..... the list goes on. This kind of #@!!$$ is going to hurt the future of these devices which I otherwise love.
OdeeanRDeathshead: I had read your previous posts, and as ever, very interesting and informative reading. I had the same idea regarding a "dummy" bluetooth device a while back, but mamaich put me in my place!
http://forum.xda-developers.com/viewtopic.php?p=179839#179839
V
thanks vijay555, thats what I have suspected about the hardware. What I want to do is a bit different. The bluetooth can communicate to many devices at once. If your program could appear to be a headset to the os, then the phone bluetooth hardware could transmit the audio to the headset at the same time your program uses bluetooth to receive it. Kind of like a loop out of the box to bridge the lack of functionality. This shifts the problem to how dose a hardware bluetooth headset communicate. Emulate this and we are on a winner. I don't think I have the willingness to pull my devices appart. I also do not have the money for some of the hardware (eg good digital oscilliscope) that I would need to measure whats going on. I did read that microsoft are about to expose some new api to allow control over the pairing process (but not the audio stream). I hope that we get some soon.
Is there going to be any new (for 2005) free development tools like the evc versions used today?
OdeeanRDeathshead: re eVC, I don't think so. The "express editions" are free, but they specifically omit the functionality to develop "mobile solutions".
Re the loop back. That's a good idea. I think mamaich is our best bet on schematics, I think that would be very helpful. As you "rave", it's mindboggling that Microsoft still haven't revealed or implemented a way to interact with the audio channels. It must have been one of the first things one could imagine doing once you develop a PDA with a phone stuck on the back of it.
Any idea if the bluetooth stacks could support transmitting and receiving simultaneously in this manner? I know some of the boys are working on alternative bluetooth support for the stereo headset profiles, so they might be able to shed some light on the issues involved. I guess the processor overhead could be hefty, but for the benefit it would be beneficial.
V
Bit of a noob question here, but is there a way to use SAP to utilise my cellphone's SIM contacts and network so that when I'm indoors I can text and call on the AMEO and then disconnect when I'm out and about. Currently I have to SIM swap as I don't like making calls on the Ameo in public.
Basically I want my Ameo to act a bit like a RSAP car kit....utilizing my phone's SIM list and transmitter when needed. This would not only be very convenient but would I think make the Ameo's battery last a hell of a lot longer as in my experience GSM/3G drains a lot more power than BT.
could the Ameo do this?
Or is it possible to develop a programme to do this?
I trust that someone out there knows.....
(Both handsets support SAP)
is that a no then?! Surprised noone else has thought of this considering the size of the ameo. Does anyone even know if it's possible to 'trick' the ameo's bluetooth stack into thinking it can act as a handsfree car kit? Or would this fall down to the capabilities of microsoft's stack? Come on people.
leoni1980 said:
is that a no then?! Surprised noone else has thought of this considering the size of the ameo. Does anyone even know if it's possible to 'trick' the ameo's bluetooth stack into thinking it can act as a handsfree car kit? Or would this fall down to the capabilities of microsoft's stack? Come on people.
Click to expand...
Click to collapse
I seem to remember this has been asked before about 3 or 4 months ago and not reply was received then, either (sorry!)
apd said:
I seem to remember this has been asked before about 3 or 4 months ago and not reply was received then, either (sorry!)
Click to expand...
Click to collapse
That's a real shame.
Would be nice to develop a little app to allow this, after all it's manipulability and flexibility like this which has allowed the bluetooth protocol to develop the way it has.
Surely someone out there knows whether it is AT LEAST possible. This sort of development would perhaps also form the possibility of using the HTC shift for voice calls if a similar SAP mod can be developed - as this is the only feature the device lacks!
Come on - I'm gagging for someone who knows about this to give an answer.
leoni1980 said:
That's a real shame.
Would be nice to develop a little app to allow this, after all it's manipulability and flexibility like this which has allowed the bluetooth protocol to develop the way it has.
Surely someone out there knows whether it is AT LEAST possible. This sort of development would perhaps also form the possibility of using the HTC shift for voice calls if a similar SAP mod can be developed - as this is the only feature the device lacks!
Come on - I'm gagging for someone who knows about this to give an answer.
Click to expand...
Click to collapse
SAP? You mean the software SAP? I use it with remote desktop. I dont think the software is meant for windows mobile. Also I message my clients using Outlook so there is no real problem. I can be logged into SAP as Admin 24/7 via HSDPA or GPRS.
it was i who created that post about using a SAP profile as a remote phone...
and not a single person chimed in then...
i have done soem extensive research on this subject...
i have found that you need teh development kit for a sim access server (as our phone already has a license)
basicly if someone has a nice car (dump the os) =p
but if we dont have as im access server its not possible...
if someone can get their hands on a sim access server this could very well be a possibility
nuclear said:
SAP? You mean the software SAP? T0I use it with remote desktop. I dont think the software is meant for windows mobile. Also I message my clients using Outlook so there is no real problem. I can be logged into SAP as Admin 24/7 via HSDPA or GPRS.
Click to expand...
Click to collapse
No sap in this case means sim access profile. It is the same protocol used by bluetooth car kits which basically allows you to remotely view your contacts and call them or text them remotely. Such a utility would i think be brilliant with the ameo as one could connect to, say a nokia n95 and use its transmitter and phonebook whilst at work or static to make and receive calls and browse the internet, then disconnect when out and about. This would be worlds apart from using a bluetooth headset i think.
Hi all.
I am new to this forum and have spent a few hours looking at some of the the threads here and reading about kitchens and baking, flashing ROMs, etc, and have become a bit scared to venture in.
All I am after is a SIP VoIP client to install on my HTC Touch Cruise (running WM6).
Can anybody help point me in the right direction and what cab file/s I need to install.
I want to steer clear of flashing ROMs.
Thanks.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=299950&highlight=voip
Not free, but way better than the MS implementation: How about giving our AGEphone Mobile a try?
Falk said:
Not free, but way better than the MS implementation: How about giving our AGEphone Mobile a try?
Click to expand...
Click to collapse
Hum, just a question: does you software provide voip audio from the right ear front speaker? If so you've found a new customer!
I (and probably everyone else making VoIP apps) wish it did - That would sure be a killer feature! We made the earphone speaker run on a few Sharp WM devices in Japan in the past because Sharp let us know the "DeviceIOControl" address of those devices. HTC on the other hand is as silent as can be and doesn't even react to our inquiries. But even if we knew the address it would result in a different version for each device as the address is very likely always a different one. So unless the phone supports switching in hardware (like a very few do) to begin with there is nothing that we (or anybody else) can do about the situation. We are working on proper bluetooth support though and hope that this can at least remedy the situation a little.
Falk said:
I (and probably everyone else making VoIP apps) wish it did - That would sure be a killer feature! We made the earphone speaker run on a few Sharp WM devices in Japan in the past because Sharp let us know the "DeviceIOControl" address of those devices. HTC on the other hand is as silent as can be and doesn't even react to our inquiries. But even if we knew the address it would result in a different version for each device as the address is very likely always a different one. So unless the phone supports switching in hardware (like a very few do) to begin with there is nothing that we (or anybody else) can do about the situation. We are working on proper bluetooth support though and hope that this can at least remedy the situation a little.
Click to expand...
Click to collapse
Your first sentence was very odd. Maybe it's an XDA joke, but I'm sorry, I didn't get it.
One thing from your website about the software, does it support G729 codec?
No joke intended.. blame my non native English for any oddities ;-) As for G.729 - yes, it can be integrated into the softphone and no, you can't use it without license rights and fees as the consortium holding the codec rights is not a merciful one.
Can anyone tell me if any of the available VoIP solutions available for WM6 will allow me to make and receive calls using my existing cell number? I know TMobile has this ability on a few of there phones.
Thanks,
mr.ellsworth
No solution to the last problem, but going back to the initial question: We have just released AGEphone Mobile 2.5 Speakerphone Edition which supports the internal speaker on some select models (more to follow!).
Bluetooth has been available on mobile phones for almost 10 years
My shiny new Hero which I consider to be an excellent piece of work is pretty useless in this department....file transfers hands free connection etc
If a phone that costs £30 from tescos can do this why cant the £400 quid hero?
Why is android incapable of this extremely basic functionality? Why are android phones on sale at all? the OS is not finished and will not be untill Bluetooth just works.
I have pissed off several friends by recomending this phone pre release assuming that the bluetooth profiles had been fixed on the hero. But if they cant send mates in the pub a photo of a friend falling over or use their hands free kits how can I blame them?
Is there a timescale for adding working bluetooth to android?
Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?
rhedgehog said:
Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?
Click to expand...
Click to collapse
Don't just blame Google tho... Android is open source and the Hero's version is a seperate dev branch to the cupcake 1.5 thats on standard 'Google' phones. I mean they must have fiddled with it anyway as some things that worked on the standard 1.5 build don't work on the Hero.
So HTC are just as much to blame for this... what can we call it... oversight...
Ovek said:
So HTC are just as much to blame for this... what can we call it... oversight...
Click to expand...
Click to collapse
No they are not! The reason that this functionality is not available is because the Bluetooth APIs have not be finalized. Whilst potentially HTC could have added their own, this would have fragmented Android as an OS and this is definitely not the way forward.
Unfortunately, Apple showed that the market will accept reduced functionality in devices, when they shipped the original iPhone.
However, with respect to Google, I fully agree that nearly a year down the line since the G1 was launched, they should've got further than they have with Bluetooth support.
Regards,
Dave
foxmeister said:
No they are not! The reason that this functionality is not available is because the Bluetooth APIs have not be finalized. Whilst potentially HTC could have added their own, this would have fragmented Android as an OS and this is definitely not the way forward.
Click to expand...
Click to collapse
The Android OS will become fragmented, Android is designed that way it's supposed to be a base on which mobile phone manufactures can build upon. It's also the reason you get "with Google" phones, if you want a pure Android OS those are the phones you buy.
HTC should have seized the opportunity to fix some of the glaring ommisions from Android, epecially considering that there is no indication that any more bluetooth profiles are included in donut.
rhedgehog said:
Ask Google. They're the ones that only programmed handsfree profiles in. Apparently it's supposed to be fairly soon.
Also, you know what they say about assuming.....
but yeah, it's a bit of a glaring omission. but then didn't the iphone do exactly the same when it first came out?
Click to expand...
Click to collapse
I say assume, but HTC posted bluetooth profiles on the android community as GAP SPP HSP HFP A2DP and AVRCP profile, so where are they?
I admiit I should have checked for OBEX, I was probably caught up in the hype, and the oooos and arghhs of the reviews, perhaps the reveiwers should have started with..... erm this phone does not work before we parted with our hard earned. Shame on you engadget
puckoon said:
I say assume, but HTC posted bluetooth profiles on the android community as GAP SPP HSP HFP A2DP and AVRCP profile, so where are they?
I admiit I should have checked for OBEX, I was probably caught up in the hype, and the oooos and arghhs of the reviews, perhaps the reveiwers should have started with..... erm this phone does not work before we parted with our hard earned. Shame on you engadget
Click to expand...
Click to collapse
Just get BlueX and use one of the many methods to root the phone, then you'll have full send/receive bluetooth capabilities. It's very easy.
does bluex actually work on the hero? and is it one of the ones that seems to be hidden on some hero devices?
Didn't know that HTC had put those profiles out there...but if they're just in beta or being tested, then i am sure they'll be here soon.
and besides, the base android build on the hero is the same as on the magic, it's just had a few kernel changes for any hero specific hardware, it's still running 1.5.
i personally knew the device had no obex, and still got it. I suppose it's each to their own really. Millions of people got the iphone and were rabid about how wonderful it was even though it was missing some basic features. i bet hero will have the same kinda people, on both sides of the argument.
i like it and am happy, but am certainly not going to defend the missing features, i just rely on the fact that as i am happy with it as it is, anything extra is a bonus.....
rhedgehog said:
does bluex actually work on the hero? and is it one of the ones that seems to be hidden on some hero devices?
Didn't know that HTC had put those profiles out there...but if they're just in beta or being tested, then i am sure they'll be here soon.
and besides, the base android build on the hero is the same as on the magic, it's just had a few kernel changes for any hero specific hardware, it's still running 1.5.
i personally knew the device had no obex, and still got it. I suppose it's each to their own really. Millions of people got the iphone and were rabid about how wonderful it was even though it was missing some basic features. i bet hero will have the same kinda people, on both sides of the argument.
i like it and am happy, but am certainly not going to defend the missing features, i just rely on the fact that as i am happy with it as it is, anything extra is a bonus.....
Click to expand...
Click to collapse
I for one have not beeen able to get Bluex to work on Hero neither Root explorer????
Ok (Grits teeth)
Still love the phone would still buy it (friends probably wont till bluetooth fixed) would have liked a choice on the bluetooth though.
If the reviewers were paying more attention to the bluetooth deficiency I am sure google would be urgently fixing it!
Guess will have to wait. Please dont hesitate to let us all know when you find out they've fixed it
Ovek said:
The Android OS will become fragmented, Android is designed that way it's supposed to be a base on which mobile phone manufactures can build upon.
Click to expand...
Click to collapse
Yes it is - and the bluetooth APIs are part of that base!
Google were very specific about why they chose not to ship Android with broken APIs (see http://android-developers.blogspot.com/2008/08/some-information-on-apis-removed-in.html ). If HTC had "done their own thing" they too would have been committed to support this for years to come.
As a developer, personally I'd be happy to wait for a single fit-for-purpose API to come to Android, than support a wide variety of vendor-specific extensions.
If Android wants to gain serious traction in the Smartphone market, they need to look at Apple and the iPhone. Here you've a single software and hardware platform which is going to make application development far simpler.
It is ok to build on top of the Android platform (as you said yourself), but if each handset vendor goes about changing the underlying nuts and bolts differently this will adversely affect market acceptance of the platform.
Regards,
Dave
so bluetooth does not work on shipped devices?
it works on the htcmagic hero rom but not on the dream hero rom. hack
i wonder why
bluetooth works, but only for headsets.
maybe the magic rom has bluex installed, as i know bluex works on the magic, but not on the hero
rhedgehog said:
bluetooth works, but only for headsets.
maybe the magic rom has bluex installed, as i know bluex works on the magic, but not on the hero
Click to expand...
Click to collapse
Hero supports a few more profiles than just headsets.
From the HTC website:
Q.
What Bluetooth profiles are supported?
The phone supports Bluetooth Headset, Handsfree, A2DP, and AVRCP profiles. You can connect your phone to a Bluetooth hands-free headset or a Bluetooth car kit and use those devices to listen to music and send and/or receive calls. Transferring files between your phone and PC using Bluetooth is not yet supported.
Click to expand...
Click to collapse
We won't see file transfer or OBEX until Google finalize the bluetooth APIs.
Regards,
Dave
puckoon said:
I have pissed off several friends by recomending this phone pre release assuming that the bluetooth profiles had been fixed on the hero. But if they cant send mates in the pub a photo of a friend falling over or use their hands free kits how can I blame them?
Is there a timescale for adding working bluetooth to android?
Click to expand...
Click to collapse
Agree about the file transfer (although its a smartphone so use flikr/twitter)
As for handsfree I am using just fine with my Parrot MKi9200 car kit. Full handsfree and A2DP Stereo support with controls. Full address book sync etc.
So apart from file transfer its got a full set of useful features.
Russ
RussST24 said:
Agree about the file transfer (although its a smartphone so use flikr/twitter)
As for handsfree I am using just fine with my Parrot MKi9200 car kit. Full handsfree and A2DP Stereo support with controls. Full address book sync etc.
So apart from file transfer its got a full set of useful features.
Russ
Click to expand...
Click to collapse
How did you get the address book to sync, I thought this didn't work, and it doesn't seem to with my Alpine kit. Did you install bluex?
The Bluetooth kit in my Land Rover Discovery 3 can pull the contacts list off my Hero and also notify me of who is calling in the head unit.
Pretty sure its not been pulled off my Nokia N85 when I used that as there is no storage in the kit as far as I am aware.
Its also just to note - a Nokia kit sourced / OEM'd by Land Rover and is the standard Bluetooth PTI they factory build.
ewans said:
How did you get the address book to sync, I thought this didn't work, and it doesn't seem to with my Alpine kit. Did you install bluex?
Click to expand...
Click to collapse
No, I have the same car kit, it just works as is from the box.
Hi,
I was a bit confused by this thread and all the bluetooth problems. At the moment I have a Touch Diamond but I am up for an upgrade in the next month so I am looking at either the Diamond 2 or the Hero. I have a Sony BTNX20 stereo BT headset that i use for everything, Will I still be able to use this headset for stereo music on the Hero? Also what video files can it play? Or is there something like Core Player available that will play everything? A bit off topic but i thought id ask since i had a bluetooth question!
mightycaz said:
Hi,
I was a bit confused by this thread and all the bluetooth problems. At the moment I have a Touch Diamond but I am up for an upgrade in the next month so I am looking at either the Diamond 2 or the Hero. I have a Sony BTNX20 stereo BT headset that i use for everything, Will I still be able to use this headset for stereo music on the Hero? Also what video files can it play? Or is there something like Core Player available that will play everything? A bit off topic but i thought id ask since i had a bluetooth question!
Click to expand...
Click to collapse
Your BT headset should be fine, as for video play back... well it's poor. And as for Core player it won't be out for long time (if ever!).