Messages

1

Developers / Re: Preliminary 10.04

« on: October 04, 2011, 04:48:57 pm »

FYI:  I just installed the 10.04 and except for the video card drivers everything went fine.

I have an NVIDIA card and I had to comment out the video card drivers loaded in the script, and then it installed just fine.

Also bluetooth drivers/software is not new enough to bond to my motorola atrix phone.
I have another linux install on another pc(non-linuxmce) with newer drivers and it bonds just fine.
Version 4.96 is current, but it worked with 4.88
LinuxMCE fails to "ask for" or display a code to type in the phone to get a successful bonding.
Tried all the usually choices: 0000,00000,1234, and etc

2

Feature requests & roadmap / Re: Feature Request - Database relocation

« on: May 12, 2008, 10:09:12 pm »

If you can't find the setting, use iptables to generate a NAT rule to foward the traffic.  If you don't know iptables use Firewall builder(30 day trail ediition) from fwbuilder.com to generate the necessary rules yourself the necessary iptable's settings through a nice windows GUI.  Route any "source" with 127.0.0.1 as the destination and 3306 as the service to the ip address of the new database with the original service.  Then save and compile.  You will get a .fw file which you can execute in a terminal window on your LinuxMCE box.  The script will have to be executed upon any reboot of the box.

3

Developers / Re: Setting up new hardware

« on: May 12, 2008, 01:58:08 pm »

PS.

dceroute-0 shows up under hands free, but is unusable.
It also shows up under device history.

I studied the docs and bluetooth_dongle.  If I understand the documentation and source code correctly all the messages the bluetooth fires off are immediately dumped into the dceroute message queue in hopes one of the modules watching the queue knows how to process the data.  The rest of the c++ code seems to be error trapping and a few odds and ends.

4

Developers / Re: Setting up new hardware

« on: May 11, 2008, 06:36:34 am »

The 2 items I said were not the same.
My cell actually dceroute-0 wants create a Voice Gateway with it.
Allow or Deny
dceroute-0 now actually appear under Handsfree devices.

5

Developers / Re: Setting up new hardware

« on: May 10, 2008, 07:54:20 pm »

Completely out of the blue, the system requested a voice gateway with my phone.
Said yes of course.
Did a pin exchange
Requested an OBEX.
I told the cell phone to accept all.
 Now what???

6

Developers / Re: Setting up new hardware

« on: May 09, 2008, 09:13:28 pm »

Research found....

Ok.  I googled and hunt and found hcidump.
hcidump is equilivant to tcpdump but for bluetooth

I have attached said file
Now I have lots of data, how do I use it?

I apologize in advance for dump in the form, but the attachment function does not work.
The file has been trimmed to fit.
==========================================================
HCI sniffer - Bluetooth packet analyzer ver 1.39

> ACL data: handle 11 flags 0x02 dlen 120
    L2CAP(d): cid 0x0040 len 116 [psm 1]
        SDP SSA Rsp: tid 0x4 len 0x6f
          count 108
          record #0
              aid 0x0000 (SrvRecHndl)
                 uint 0x0
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1000 (SDServer) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0001 (SDP) > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1000 (SDServer) uint 0x100 > >
              aid 0x0200 (VersionNumList)
                 < uint 0x1000 >
              aid 0x0201 (SrvDBState)
                 uint 0x1
          record #1
              aid 0x0000 (SrvRecHndl)
                 uint 0x10001
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1103 (DUN) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x1 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1103 (DUN) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "Dialup Networking Gateway"
              aid 0x0101 (SrvDesc)
                 str "Dialup Networking Gateway"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0x0201 (SrvDBState)
                 < uint 0x3002 >
              aid 0x0202 (unknown)
                 < uint 0x22b8 >
              aid 0xc800 (unknown)
                 str 50 61 73 73 65 72 65 6c 6c 65 20 64 27 61 63 63 c3 a8 73 20 72 c3 a9 73 65 61 75 20 c3 a0 20 64 69 73 74 61 6e
              aid 0xc801 (unknown)
                 str 50 61 73 73 65 72 65 6c 6c 65 20 64 27 61 63 63 c3 a8 73 20 72 c3 a9 73 65 61 75 20 c3 a0 20 64 69 73 74 61 6e
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "Portal de acceso a red"
              aid 0xc804 (unknown)
                 str "Portal de acceso a red"
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str "Discagem de Rede Gateway"
              aid 0xc807 (unknown)
                 str "Discagem de Rede Gateway"
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          record #2
              aid 0x0000 (SrvRecHndl)
                 uint 0x10003
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1112 (Headset AG) uuid-16 0x1203 (Audio) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x3 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1108 (Headset) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "Voice Gateway"
              aid 0x0101 (SrvDesc)
                 str "Headset Audio Gateway"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0xc800 (unknown)
                 str "Passerelle vocale"
              aid 0xc801 (unknown)
                 str "Passerelle casque audio"
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "Portal de voz"
              aid 0xc804 (unknown)
                 str 50 6f 72 74 61 6c 20 61 75 64 c3 ad 66 6f 6e 6f
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str "Gateway de Voz"
              aid 0xc807 (unknown)
                 str "Audio fone de ouvido Gateway"
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          record #3
              aid 0x0000 (SrvRecHndl)
                 uint 0x10007
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x111f (Handsfree AG) uuid-16 0x1203 (Audio) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x7 > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x111e (Handsfree) uint 0x101 > >
              aid 0x0100 (SrvName)
                 str "Handsfree Voice Gateway"
              aid 0x0101 (SrvDesc)
                 str "Handsfree Voice Gateway"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0x0301 (SuppDataStoresList)
                 uint 0x1
              aid 0x0311 (SuppFeatures)
                 uint 0x1f
              aid 0xc800 (unknown)
                 str "Passerelle vocale mains libres"
              aid 0xc801 (unknown)
                 str "Passerelle vocale mains libres"
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "Portal de voz a manos libres"
              aid 0xc804 (unknown)
                 str "Portal de voz a manos libres"
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str "Gateway Viva Voz"
              aid 0xc807 (unknown)
                 str "Gateway Viva Voz"
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          record #4
              aid 0x0000 (SrvRecHndl)
                 uint 0x10008
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1105 (OBEXObjPush) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x8 > <
                 uuid-16 0x0008 (OBEX) > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1105 (OBEXObjPush) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "OBEX Object Push"
              aid 0x0101 (SrvDesc)
                 str "OBEX Object Push"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0x0303 (SuppFormatsList)
                 < uint 0xff >
              aid 0xc800 (unknown)
                 str "OBEX Object Push"
              aid 0xc801 (unknown)
                 str "OBEX Object Push"
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "OBEX Object Push"
              aid 0xc804 (unknown)
                 str "OBEX Object Push"
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str "OBEX Object Push"
              aid 0xc807 (unknown)
                 str "OBEX Object Push"
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          record #5
              aid 0x0000 (SrvRecHndl)
                 uint 0x10009
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x1106 (OBEXObjTrnsf) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0x9 > <
                 uuid-16 0x0008 (OBEX) > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x1106 (OBEXObjTrnsf) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "OBEX File Transfer"
              aid 0x0101 (SrvDesc)
                 str "OBEX File Transfer"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0xc800 (unknown)
                 str "Transfert de fichier OBEX"
              aid 0xc801 (unknown)
                 str "Transfert de fichier OBEX"
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "Transferencia de archivo OBEX "
              aid 0xc804 (unknown)
                 str "Transferencia de archivo OBEX "
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str 4f 42 45 58 20 54 72 61 6e 73 66 65 72 c3 aa 6e 63 69 61 20 64 65 20 61 72 71 75 69 76 6f
              aid 0xc807 (unknown)
                 str 4f 42 45 58 20 54 72 61 6e 73 66 65 72 c3 aa 6e 63 69 61 20 64 65 20 61 72 71 75 69 76 6f
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          record #6
              aid 0x0000 (SrvRecHndl)
                 uint 0x1000a
              aid 0x0001 (SrvClassIDList)
                 < uuid-16 0x111b (ImagingResp) >
              aid 0x0002 (SrvRecState)
                 uint 0x1
              aid 0x0004 (ProtocolDescList)
                 < < uuid-16 0x0100 (L2CAP) > <
                 uuid-16 0x0003 (RFCOMM) uint 0xa > <
                 uuid-16 0x0008 (OBEX) > >
              aid 0x0005 (BrwGrpList)
                 < uuid-16 0x1002 (PubBrwsGrp) >
              aid 0x0006 (LangBaseAttrIDList)
                 < uint 0x656e uint 0x6a uint 0x100 uint 0x6672 uint 0x6a uint 0xc800 uint 0x6573 uint 0x6a uint 0xc803 uint 0x7074 uint 0x6a uint 0xc806 >
              aid 0x0009 (BTProfileDescList)
                 < < uuid-16 0x111a (Imaging) uint 0x100 > >
              aid 0x0100 (SrvName)
                 str "Image Push"
              aid 0x0101 (SrvDesc)
                 str "Image Push"
              aid 0x0102 (ProviderName)
                 str "/a/mobile/system/cl.gif"
              aid 0x0310 (SuppCapabilities)
                 uint 0x1
              aid 0x0311 (SuppFeatures)
                 uint 0x1
              aid 0x0312 (SuppFunctions)
                 uint 0xb
              aid 0x0313 (SuppTotalCapacity)
                 uint 0x5000000001000a
              aid 0xc800 (unknown)
                 str 49 6d 61 67 65 20 c3 a0 20 63 68 61 72 67 65 6d 65 6e 74 20 64 69 72 65 63 74
              aid 0xc801 (unknown)
                 str 49 6d 61 67 65 20 c3 a0 20 63 68 61 72 67 65 6d 65 6e 74 20 64 69 72 65 63 74
              aid 0xc802 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc803 (unknown)
                 str "Imagen push"
              aid 0xc804 (unknown)
                 str "Imagen push"
              aid 0xc805 (unknown)
                 str "/a/mobile/system/cl.gif"
              aid 0xc806 (unknown)
                 str "Transf. de Imagem"
              aid 0xc807 (unknown)
                 str "Transf. de Imagem"
              aid 0xc808 (unknown)
                 str "/a/mobile/system/cl.gif"
          cont 00
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 3 scid 0x0041
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
      Connection successful
< ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 1013
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
      MTU 1506
< ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
      Success
      MTU 1506
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
      Success
      MTU 1013
< ACL data: handle 11 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c
> ACL data: handle 11 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7
< ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(d): cid 0x0041 len 14 [psm 3]
      RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8
      dlci 38 frame_type 0 credit_flow 15 pri 7 ack_timer 0
      frame_size 1008 max_retrans 0 credits 7
> ACL data: handle 11 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): DM: cr 1 dlci 38 pf 1 ilen 0 fcs 0x2f
< ACL data: handle 11 flags 0x02 dlen 8
    L2CAP(d): cid 0x0041 len 4 [psm 3]
      RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> HCI Event: Number of Completed Packets (0x13) plen 5
> ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
> ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(s): Command rej: reason 2 dcid 0x0041 scid 0x0041
      Invalid CID in request
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Number of Completed Packets (0x13) plen 5
< HCI Command: Disconnect (0x01|0x0006) plen 3
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Disconn Complete (0x05) plen 4
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
> HCI Event: Inquiry Complete (0x01) plen 1
< HCI Command: Inquiry (0x01|0x0001) plen 5
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: Inquiry Result with RSSI (0x22) plen 15
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Inquiry Cancel (0x01|0x0002) plen 0
> HCI Event: Command Complete (0x0e) plen 4
> HCI Event: Connect Complete (0x03) plen 11
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
> HCI Event: Read Remote Supported Features (0x0b) plen 11
> HCI Event: Command Complete (0x0e) plen 6
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
> HCI Event: Command Status (0x0f) plen 4
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Max Slots Change (0x1b) plen 3
> HCI Event: Command Complete (0x0e) plen 252
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Remote Name Req Complete (0x07) plen 255
> HCI Event: Command Complete (0x0e) plen 252
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
      Connection successful
< ACL data: handle 11 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
      MTU 1024
< ACL data: handle 11 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
      Success
      MTU 1024
> ACL data: handle 11 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
< ACL data: handle 11 flags 0x02 dlen 24
    L2CAP(d): cid 0x0040 len 20 [psm 1]
        SDP SSA Req: tid 0x0 len 0xf
          pat uuid-16 0x1002 (PubBrwsGrp)
          max 65535
          aid(s) 0x0000 - 0xffff
          cont 00

7

Developers / Re: Setting up new hardware

« on: May 09, 2008, 08:26:30 pm »

Did the up to the DCEGen part.

Went to Device template screen
Selected Motorola
and the Generic serial device

Then pick device and a new screen open up!!!

Ok, so far how horribly have I screwed up???

The phone has:

com port
File Transfer(Obex)
Imaging Responder
Object push (Obex)
Audio port (of some kind)

Am I supposed to create a motorola cell phone device and then create 4 or more children??
Am I supposed to create a new device template for each of what I call children???

For the manufacture am I supposed to use Motorola or some determine the manufacture of each sub-device.
Please help me answer some of these questions on the "edit device template screen".

Or what programs do I run to get the neccary info?

8

Developers / Re: Setting up new hardware

« on: May 09, 2008, 03:35:28 pm »

Read the main page working on the subpages.
DCEGen can not find its templates or output directory
I also tried -u root -p <password>

9

Developers / Re: Setting up new hardware

« on: May 09, 2008, 03:03:07 pm »

I went to the device template screen.
I selected bluetooth, hit filter and it said 13 choice remain.  I hit the other drop down and only 1 choice actually remains. Is this correct?
Should I have selected "Phones" because the bridge device is the phone??
Should I have selected "Generic Serial Device" or some silimiliar designation because the final device is a serial port?
Also "Soft Phones" and "Softphones" also look like possiblilities.  Maybe even a "Virtual Device"??
After examining the choices "Soft Phones" and bluetooth seem to be the best options.
Do I want Bluetooth because its attach bluetooth, or "Soft Phones" because the device is a phone??  The bluetooth dongle its self seems already configured, am I right???

10

Developers / Setting up new hardware

« on: May 08, 2008, 03:58:15 pm »

The process of setting up new hardware seems particularly difficult, especially considering how easy everything else is configure.  I am trying to setup a cell phone over bluetooth.  The system seems to know its there, but I can tell how it configured it and what parts of the phone it recognized.  Using windows I know the phone has at least 4, if not 5, child devices.  However, I can't tell if LinuxMCE has found any of these devices.

I have gone through ALL the web configure screens, and end up on the one with device piping on it.  I can't decided whether I should pipe "Bluetooth Dongle" directly to "phone", or whether I should ignore the phone and map "Bluetooth Donlge" to each one the the child device separately.  For example, the phone has a direct bluetooth serial port that support the standard AT command set plus additional command set that allow sync of other phone data such as contacts.  It also allows remote dialing.  (ATDT)  On another screen when I select Bluetooth the only choices it offers are Audio and Video and I don't want either of those right now.  Do I map "bluetooth dongle" to "serial port" completely ignoring the cell's phones modem??  Should I be doing device piping at all??

My gut instinct is that all the choice I made were wrong and I am completely on the wrong track and just don't know it.

There should be a screen where I can say USB connects to bluetooth dongle connects to cell phone and has these child devices.  It would be even better if it was plug and play, if windows and enumerate child devices automatically, it can be emulated on another OS.

help??

Also when windows shares are detected they just say windows share instead of what the share name is and what server they are on.  Therefore I can not provide valid credentials without using trail and error method.

11

Feature requests & roadmap / Re: Feature Request - Database relocation

« on: May 07, 2008, 06:12:38 pm »

*****Before dumping bring the database offline so no one can use it.*****
Otherwise you may have doom and disaster
I recommend unplugging the cable from all NIC(s) during the mysqldump process.
I assume NO LIABILITY of any kind, but I have done this before for other programs.

LinuxMCE PC

mysqldump -c -u <username> -p <database name>  >/path-of output/linuxmce-backup.sql
Obviously you need to supply valid credentials including password.

There is a command line switch to dump all databases, but I forgot what that was try mysqldump --help.
(something like --all-databases)

You may/or may not have to add "connect <database name>;" as the first line of code.  If you use the all switch you won't have to, but if you use the "all" you could wipe out existing username and passwords if your not careful.  ***If both systems have a user joe some of the data could be overlayed especially the password.**
***Other bad things can occur****

copy linuxmce-backup.sql to your other machine.

I also recommend(strongly!!) using the same procedure to back up your other database in case something goes horribly wrong.

You need to find and use the "all database" switch for your original database, on the destination pc, because that will backup usernames,passwords, and permissions.

Destination PC

EITHER
mysqldump -c -u <username> -p <database name>  >/path-of output/orginal-db-on-destination-pc.sql
OR (better)
mysqldump -c -u <username> -p --all-databases  >/path-of output/orginal-db-on-destination-pc.sql

Using the same steps with a different filename.


Now hopefully you backed up both of them in case of disaster.
No backup=No recovery



mysql -u <username> -p <database name> /path-to existing file/linuxmce-backup.sql
If your doing all you omitted the database name.

Specify credentials and wait for the process to complete.

If something goes horribly wrong you'll be glad you backed up.
---In case of doom as disaster:----------
mysql -u root -p
delete each affect database one at a time
commit;
exit or bye I forget which.
mysql -u root -p <database name> </path-of output/orginal-db-on-destination-pc.sql
Specify credentials and wait for the process to complete.
You are now restored
---End of doom and disaster---------------

I have no idea where the setting is located, but all thats left is to change the IP address that LinuxMCE is trying to connect to from localhost to the ip address of your other machine and your done.
Assuming you found this location you and now migrated.

12

Developers / Re: Myth backward incompatiblity

« 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.

13

Developers / Re: Myth backward incompatiblity

« 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.

14

Developers / Re: Myth backward incompatiblity

« 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?

15

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 08:14:48 pm »

Basically, you create a new device.
-------------------------------
Is there an automated script, or which files do I edit, or make copies of and rename for my purpose.  It would seem that I would use another device as a template and make copies of the code and retool it for my device.  Most devices LinuxMCE reaches out and pnps it, but this one would be the device reaching out to find my virtual speaker does this cause any additional complexities?  Do I download and compile everything, or can I pull the necessary parts out for individual compile?? 

I probably could figure it out eventually, but it would be faster if you just told me.