Author Topic: Myth backward incompatiblity  (Read 3248 times)

cybernard

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: Myth backward incompatiblity
« Reply #15 on: May 06, 2008, 09:46:06 pm »
Ok, I read all the pages and the pages they linked to.

(All via bluetooth visible from windows)
My cell has a com port
File Transfer(Obex)
Imaging Responder
Object push (Obex)

Downloading all files(via file transfer) and contacts and stuff(through COM9).
The fake headset will have to use one of these protocols.  As long as setting up devices I might as well try my hand at these.  Does LinuxMCE support those protocols??(com, I know is a yes)  Am I correct in guessing that I need to set each one up seperately???

http://www.traud.de/gsm/OBEX.htm

I guess I will have to play with this tonight.

     The virtual speaker/mic the bluetooth device is going to have to periodically broadcast its virtual existance especially when the cell phone wants to find it.  Is this a problem?

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5505
  • DOES work for LinuxMCE.
    • View Profile
Re: Myth backward incompatiblity
« Reply #16 on: May 06, 2008, 09:49:12 pm »
not sure, you're in new territory here. Welcome to research and development.

-Thom

cybernard

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: Myth backward incompatiblity
« Reply #17 on: May 06, 2008, 10:25:53 pm »
Google is our friend
Apparently the answer is yes:  OpenObex
http://dev.zuckschwerdt.org/openobex/

And command line examples on how to do it
http://dev.zuckschwerdt.org/openobex/wiki/ObexFtpExamples

Apparently they have well over 30 different phones that work, Mine is one of them.  However, that would seem to indicate that another a library libopenopex has to be integrated into LinuxMCE.

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5505
  • DOES work for LinuxMCE.
    • View Profile
Re: Myth backward incompatiblity
« Reply #18 on: May 06, 2008, 10:28:18 pm »
we currently do an obex push to upload the mobile orbiter software to the phone.

I highly suggest taking a long look at the source code.

Particularly:

* Telecom Plugin
* Bluetooth Dongle
* BD
* VIPShared

and a few others, just start exploring.

-Thom

-Thom

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2421
    • View Profile
    • ago control
Re: Myth backward incompatiblity
« Reply #19 on: May 07, 2008, 12:50:29 am »
for audio you prolly want to google for "bluez audio sco" and find a page like that:
http://wiki.bluez.org/wiki/Audio

best regards,
Hari
rock your home - http://www.agocontrol.com home automation

cybernard

  • Regular Poster
  • **
  • Posts: 24
    • View Profile
Re: Myth backward incompatiblity
« Reply #20 on: May 07, 2008, 06:35:19 am »
Does the go to Advanced and setup a "Device Template" still hold true??
There are at least 100 device template with secret codes for names, which secret code should I use??
Surely I don't have to go one at a time and hope for the best, do I??

I have examined all the files once you mentioned once. still absorbing it.