Re: BT Vehicle Profiles
I volunteer to fix this. I just need your car for six months. The vehicle in question is a Range Rover HSE. The car isn't mine, it's > a company car. The phone in question is one of the phones that I have > to support so logically the fact that they won't connect is my problem! > My thinking was, get the OpenMoko to connect, move the user to it, > and be done with this headache! ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: BTW could be the protocolls propritary and with the need to pay licence fees? Re: BT Vehicle Profiles
Some devices don't answer as expected :) Scott ~ # hcitool scan Scanning ... 08:00:28:F3:E1:82 David Ford Scott ~ # sdptool browse 08:00:28:F3:E1:82 Browsing 08:00:28:F3:E1:82 ... Scott ~ # sdptool records 08:00:28:F3:E1:82 | grep Name Service Name: Audio Video Remote Control Profile Service Name: Voice Gateway Service Name: Voice Gateway Service Name: Serial Port Service Name: Dial-up Networking -david Marcin Juszkiewicz wrote: Dnia wtorek, 23 stycznia 2007 18:46, Robert Michel napisał: But does maybe there any propritry protocolls out there which would costs licence fees? Maybe - we will see when we will get 'sdptool browse' output. BTW.. Duncan: please send full output of this command rather - I remind that some devices use misc names for services.. ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: BTW could be the protocolls propritary and with the need to pay licence fees? Re: BT Vehicle Profiles
Dnia wtorek, 23 stycznia 2007 18:46, Robert Michel napisał: > But does maybe there any propritry protocolls out there which would > costs licence fees? Maybe - we will see when we will get 'sdptool browse' output. BTW.. Duncan: please send full output of this command rather - I remind that some devices use misc names for services.. -- JID: hrw-jabber.org OpenEmbedded developer/consultant I don't know. I don't care. And it doesn't make any difference. ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
BTW could be the protocolls propritary and with the need to pay licence fees? Re: BT Vehicle Profiles
Salve Marcin, *! On Tue, 23 Jan 2007, Marcin Juszkiewicz wrote: > Dnia wtorek, 23 stycznia 2007 17:41, Duncan Hudson napisa?: > 1. Get any Linux powered device into car system range. > 2. Run 'hcitool scan' > 3. Identify line which match car system. > 4. Run 'sdptool browse ADDRESS_OF_CAR_SYSTEM|grep "Service Name"' > 5. Send us output > > My sony Ericsson k750i phone reports: > > Service Name: Dial-up Networking > Service Name: Serial Port > Service Name: HF Voice Gateway > Service Name: HS Voice Gateway > Service Name: OBEX Object Push > Service Name: OBEX File Transfer > Service Name: OBEX SyncML Client > Service Name: OBEX IrMC Sync Server > Service Name: Mouse & Keyboard This sounds open and not propritrary. But does maybe there any propritry protocolls out there which would costs licence fees? Greetings, rob ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: BT Vehicle Profiles
Dnia wtorek, 23 stycznia 2007 17:41, Duncan Hudson napisał: > The vehicle in question is a Range Rover HSE. The car isn't mine, it's > a company car. The phone in question is one of the phones that I have > to support so logically the fact that they won't connect is my problem! > My thinking was, get the OpenMoko to connect, move the user to it, > and be done with this headache! 1. Get any Linux powered device into car system range. 2. Run 'hcitool scan' 3. Identify line which match car system. 4. Run 'sdptool browse ADDRESS_OF_CAR_SYSTEM|grep "Service Name"' 5. Send us output My sony Ericsson k750i phone reports: Service Name: Dial-up Networking Service Name: Serial Port Service Name: HF Voice Gateway Service Name: HS Voice Gateway Service Name: OBEX Object Push Service Name: OBEX File Transfer Service Name: OBEX SyncML Client Service Name: OBEX IrMC Sync Server Service Name: Mouse & Keyboard Quite a lot :D -- JID: hrw-jabber.org OpenEmbedded developer/consultant Any smoothly functioning technology will have the appearance of magic. -- Arthur C. Clarke ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: BT Vehicle Profiles
The vehicle in question is a Range Rover HSE. The car isn't mine, it's a company car. The phone in question is one of the phones that I have to support so logically the fact that they won't connect is my problem! My thinking was, get the OpenMoko to connect, move the user to it, and be done with this headache! Andrew Turner wrote: Bluetooth connectivity is usually limited by the protocols that the bluetooth stack supports on the 2-sides. Essentially, are they both going to speak the same protocol? It is sometimes possible to write drivers for hardware (at least open hardware) to add protocol's to the stack. However, what car/system do you have so that it may help identify which protocol's it expects. Here is a good intro to Bluetooth technical aspects: http://developer.apple.com/documentation/DeviceDrivers/Conceptual/Bluetooth/BT_Bluetooth_Basics/chapter_2_section_4.html Andrew On 1/23/07, Duncan Hudson <[EMAIL PROTECTED]> wrote: I have a car that only allows bluetooth connectivity to about 10 Motorola (old) phones. Needless to say that's incredibly frustrating as my phone isn't one of the listed phones. As this is going to be an open phone could I make the OpenMoko emulate one of these old phones so that I can finally connect to my car? I know nothing about Bluetooth - just how involved would this be? Duncan ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
Re: BT Vehicle Profiles
Bluetooth connectivity is usually limited by the protocols that the bluetooth stack supports on the 2-sides. Essentially, are they both going to speak the same protocol? It is sometimes possible to write drivers for hardware (at least open hardware) to add protocol's to the stack. However, what car/system do you have so that it may help identify which protocol's it expects. Here is a good intro to Bluetooth technical aspects: http://developer.apple.com/documentation/DeviceDrivers/Conceptual/Bluetooth/BT_Bluetooth_Basics/chapter_2_section_4.html Andrew On 1/23/07, Duncan Hudson <[EMAIL PROTECTED]> wrote: I have a car that only allows bluetooth connectivity to about 10 Motorola (old) phones. Needless to say that's incredibly frustrating as my phone isn't one of the listed phones. As this is going to be an open phone could I make the OpenMoko emulate one of these old phones so that I can finally connect to my car? I know nothing about Bluetooth - just how involved would this be? Duncan ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community -- Andrew Turner [EMAIL PROTECTED]42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
BT Vehicle Profiles
I have a car that only allows bluetooth connectivity to about 10 Motorola (old) phones. Needless to say that's incredibly frustrating as my phone isn't one of the listed phones. As this is going to be an open phone could I make the OpenMoko emulate one of these old phones so that I can finally connect to my car? I know nothing about Bluetooth - just how involved would this be? Duncan ___ OpenMoko community mailing list community@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/community
