Author Topic: Java/ J2ME mobile orbiter  (Read 111814 times)

nite_man

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1019
  • Want to work with LinuxMCE
    • View Profile
    • Smart Home Blog
Re: Java/ J2ME mobile orbiter
« Reply #195 on: August 12, 2008, 09:00:14 am »
Solved my problem with BD (thanks to Oliver!) and played a bit with JavaMO. With Symbian UI it works fine. I used  numeric keys to navigate. After that I tried Basic Skin with PDA resolution - 240 x 320. I navigated through menu using arrow keys and numeric buttons. But the reaction is very slowly and sometimes it went to wrong direction. Possible that kind of skin is not situated for module Orbiter. Or if there is a way to trace it I'll be happy to do that :)
Michael Stepanov,
My setup: http://wiki.linuxmce.org/index.php/User:Nite_man#New_setup
Russian LinuxMCE community: http://linuxmce.ru

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5495
  • DOES work for LinuxMCE.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #196 on: August 12, 2008, 01:52:55 pm »
that skin ISN'T well situated to the reaction model of the Mobile Orbiter, at all.

-Thom

Cylon7

  • Regular Poster
  • **
  • Posts: 15
    • View Profile
    • Apollo Smart Homes
Can't get it working
« Reply #197 on: August 15, 2008, 09:05:13 am »
I have a Nokia e62. Posde reports the JavaMO working on the e61, which is almost the same phone (only without wi-fi).

I'm using a Kinamax BT adapter, which is listed as Linux compatible, and reviews on NewEgg confirm it works in Linux.
http://www.kinamax.com/product/Item/BT-USB.htm
http://www.newegg.com/Product/Product.aspx?Item=N82E16833206001

LMCE recognizes the phone, and sends the Bluetooth message with the Symbian .sis.

Per the instructions, I transferred the Java MO files (downloaded from vt100) to the phone, and installed it. (And put the new Bluetooth library on the Core.)

The application loads on the phone but just says "Waiting for Connection"; meanwhile the Media Director UI keeps showing in the upper left corner that the Bluetooth dongle keeps reloading. The log says this, over and over again (where XX:XX etc. is my phone's actual Mac address):

Code: [Select]
========== NEW LOG SECTION ==========
1       08/15/08 01:51:39       44 (spawning-device)    Starting... 30
1       08/15/08 01:51:39       44 (spawning-device)    Found /usr/pluto/bin/LaunchBluetooth_Dongle.sh
05      08/15/08 1:51:44.788            Inquiry started <0xb6790b90>
05      08/15/08 1:52:00.918            Inquiry complete
 <0xb6790b90>
05      08/15/08 1:52:00.918            Inquiry started <0xb6790b90>
05      08/15/08 1:52:00.918            Detected device mac: XX:XX:XX:XX:XX:XX link quality: 0 <0xb4dffb90>
05      08/15/08 1:52:00.920            About to connect to PlutoMO. We'll suspend scanning... <0xb578eb90>
05      08/15/08 1:52:00.921            Suspending scanning... <0xb578eb90>
Return code: 139
3       08/15/08 01:52:01       44 (spawning-device)    Device died... count=30/50 dev=44
Fri Aug 15 01:52:01 CDT 2008 died

sdptool browse gives me:
Code: [Select]
Inquiring ...
Browsing XX:XX:XX:XX:XX:XX ...
Service Name: AVRCP Target
Service Description: Audio Video Remote Control
Service Provider: Symbian Software Ltd.
Service RecHandle: 0x10000
Service Class ID List:
  "AV Remote" (0x110e)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x100
    uint16: 0xf00

Service Name: Hands-Free Audio Gateway
Service RecHandle: 0x1000b
Service Class ID List:
  "Handfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 28
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Handfree Audio Gateway" (0x111f)
    Version: 0x0101

Service Name: Headset Audio Gateway
Service RecHandle: 0x1000c
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 29
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Headset" (0x1108)
    Version: 0x0100

Service Name: SyncMLClient
Service RecHandle: 0x1000d
Service Class ID List:
  UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 10
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "" (0x00000002-0000-1000-8000-0002ee000002)
    Version: 0x0100

Service Name: OBEX File Transfer
Service RecHandle: 0x1000e
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 11
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

Service Name: Nokia OBEX PC Suite Services
Service RecHandle: 0x1000f
Service Class ID List:
  UUID 128: 00005005-0000-1000-8000-0002ee000001
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 12
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "" (0x00005005-0000-1000-8000-0002ee000001)
    Version: 0x0100

Service Name: SyncML DM Client
Service RecHandle: 0x10010
Service Class ID List:
  UUID 128: 00000004-0000-1000-8000-0002ee000002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 13
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "" (0x00000004-0000-1000-8000-0002ee000002)
    Version: 0x0100

Service Name: Nokia SyncML Server
Service RecHandle: 0x10011
Service Class ID List:
  UUID 128: 00005601-0000-1000-8000-0002ee000001
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 14
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "" (0x00005601-0000-1000-8000-0002ee000001)
    Version: 0x0100

Service Name: OBEX Object Push
Service RecHandle: 0x10012
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 9
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

Service Name: Dial-Up Networking
Service RecHandle: 0x10013
Service Class ID List:
  "Dialup Networking" (0x1103)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Dialup Networking" (0x1103)
    Version: 0x0100

Service Name: Imaging
Service RecHandle: 0x10014
Service Class ID List:
  "Imaging Responder" (0x111b)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 15
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Imaging" (0x111a)
    Version: 0x0100


Someone earlier in this thread says they solved a similar problem by using another adapter, but I'd rather not do that - I already have these & they're listed as Linux compatible.

I went into KDE desktop, and manually got the phone paired. For a short while I was getting this, also repeating:

Code: [Select]
  5286  05      08/15/08 4:53:28.714            BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb5799b90>
  5287  05      08/15/08 4:53:28.714            Failed to connect to PlutoMO. We'll resume scanning <0xb5799b90>
  5288  05      08/15/08 4:53:28.714            Resuming scanning... <0xb5799b90>
  5289  05      08/15/08 4:53:28.767            Inquiry started <0xb679bb90>
  5290  05      08/15/08 4:53:29.630            Detected device mac: 00:18:C5:2B:3E:F5 link quality: 0 <0xb4f98b90>
  5291  05      08/15/08 4:53:29.635            About to connect to PlutoMO. We'll suspend scanning... <0xb5799b90>
  5292  05      08/15/08 4:53:29.635            Suspending scanning... <0xb5799b90>
  5293  01      08/15/08 4:53:29.940            received channel: 19
  5294   <0xb5799b90>
  5295  05      08/15/08 4:53:30.114            Can't connect RFCOMM socket XX:XX:XX:XX:XX:XX, channel 19 <0xb5799b90>
  5296  05      08/15/08 4:53:30.114            Waiting any operation with the socket to finish... <0xb5799b90>
  5297  05      08/15/08 4:53:30.114            BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb5799b90>
  5298  05      08/15/08 4:53:30.114            Failed to connect to PlutoMO. We'll resume scanning <0xb5799b90>

And in KDE Desktop - the Bluetooth connection icon will never stay blue for very long, sometimes only a half-second at a time.

Anyone have any ideas? Does anyone know what return code 139 is?
« Last Edit: August 15, 2008, 12:03:30 pm by Cylon7 »
“True words aren't charming,
   Charming words aren't true.
People who know aren't learned,
   Learned people don't know."
--Lao Tzu, Tao Te Ching, 81

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Java/ J2ME mobile orbiter
« Reply #198 on: August 15, 2008, 06:29:33 pm »
the sdptool does not show the PlutoMO service. I'd assume you have no proper bluetooth access on the phone. The Bluetooth_Dongle then dies as there is nothing to connect to, when it finds the phone while scanning for the bluetooth address.

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

Cylon7

  • Regular Poster
  • **
  • Posts: 15
    • View Profile
    • Apollo Smart Homes
Re: Java/ J2ME mobile orbiter
« Reply #199 on: August 16, 2008, 12:15:33 am »
Yup you are right hari, I didn't notice that obvious missing entry in the sdptool browse after my late night last night.

It turns out that Cingular/AT&T put proprietary firmware on the e62, which prevents unsigned midlet applets from accessing the BT stack. Only Cingular can provide a proper unlock code, but all you have to do is call them & request it. It should arrive via email within 3-5 days. I'll update this posting to let people know. The e62's a good phone so I'm eager to get it working.

Thanks all,
7
“True words aren't charming,
   Charming words aren't true.
People who know aren't learned,
   Learned people don't know."
--Lao Tzu, Tao Te Ching, 81

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #200 on: August 29, 2008, 06:45:20 am »
Still struggling to get the JavaMO working on my Blackberry. I have the app installed and it starts, and then just waits for a connection indefinitely. The core sees it and I go through the motions of letting the orbiter set up, regen, reload. But I then get the same thing, with the bluetooth repeatedly attempting to connect and failing. When I do sdptool, there is no PlutoMO service either:
Code: [Select]
linuxmce@dcerouter:~$ sudo sdptool browse
Inquiring ...
Browsing 00:1C:CC:4C:73:E5 ...
Service Name: AUDIO Gateway
Service RecHandle: 0x10001
Service Class ID List:
  "Headset Audio Gateway" (0x1112)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 2
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100

Service Name: Voice Gateway
Service RecHandle: 0x10002
Service Class ID List:
  "Handfree Audio Gateway" (0x111f)
  "Generic Audio" (0x1203)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 3
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Handsfree" (0x111e)
    Version: 0x0105

Service Name: Advanced Audio
Service Provider: BlackBerry
Service RecHandle: 0x10003
Service Class ID List:
  "Audio Source" (0x110a)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 25
  "AVDTP" (0x0019)
    uint16: 0x100
Profile Descriptor List:
  "Advanced Audio" (0x110d)
    Version: 0x0100

Service RecHandle: 0x10004
Service Class ID List:
  "AV Remote Target" (0x110c)
Protocol Descriptor List:
  "L2CAP" (0x0100)
    PSM: 23
  "AVCTP" (0x0017)
    uint16: 0x100
Profile Descriptor List:
  "AV Remote" (0x110e)
    Version: 0x0100

Service Name: Phonebook Access PSE
Service RecHandle: 0x10005
Service Class ID List:
  "Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Phonebook Access" (0x1130)
    Version: 0x0100

linuxmce@dcerouter:~$

But the application permissions for the JavaMO applet say bluetooth is allowed... I seem to be able to pair in KDE desktop... any thoughts on what I'm doing wrong?

Cylon7

  • Regular Poster
  • **
  • Posts: 15
    • View Profile
    • Apollo Smart Homes
Re: Java/ J2ME mobile orbiter
« Reply #201 on: August 29, 2008, 06:53:21 am »
An update on my e62 for those interested...

I got the unlock code from Cingular - but apparently, fully functional, uncrippled unbranded US firmware for this phone does not exist. Nokia removed the phone from their online software updating application, due to contractual agreements with AT&T. People in NYC and Chicago report being able to take their phones to the Nokia flagship stores there, but apparently I'm S.O.L. with this phone. Thanks AT&T for crippling an open source phone. I'm switching to TMobile (and I swear AT&T's service has gotten worse since I called to ask what day my plan ends, hurry up October 25th).

& colinjones - what kind of Blackberry do you have? Just curious, I've ordered a Curve, which has built-in wifi. I'm hoping it will work. (The e62 also has built-in wifi, which of course was also crippled in AT&T firmware.)
« Last Edit: August 29, 2008, 06:55:56 am by Cylon7 »
“True words aren't charming,
   Charming words aren't true.
People who know aren't learned,
   Learned people don't know."
--Lao Tzu, Tao Te Ching, 81

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #202 on: August 29, 2008, 07:13:16 am »
Its an 8310 Curve (no wifi).... just after I posted it suddenly started "working" kind of... sdptool browse now shows a Pluto service.. No idea what I did to get that, but I was force reloading and rebooting, and tinkering generally.. At that point the JavaMO suddenly sprang to life and I could see an Orbiter on the Blackberry. Much too small as I hadn't modified the Orbiter settings at that point and it appeared to hang the Blackberry, keys not responding etc. So I modified the screen size and orientation, regen'd/reloaded and restarted the phone.

Now i can see the Pluto service, but the log file indicates I am back to the continually dying device even though it can see the MAC address of my phone. Reboot my phone and core again, and still the same, return code 139 and the device keeps dying.... no idea why, it obviously can work, but I just don't seem to be able to keep it going... wish I knew what caused it to work briefly, 10 mins ago!

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #203 on: August 29, 2008, 07:20:13 am »
arrgh! just did it again, seems to be when I execute the sdptool browse command! Suddently the blackberry prompts me that the dce router is trying to connect (both times it works, haven't seen this message any other time) and then the orbiter comes up...

Screen the right size this time, but can't really control it - changed screen once, but then seems to have locked up again, and lots of errors in the log again....

Code: [Select]
05      08/29/08 15:16:16.526           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:16.526           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:16.549           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:16.812           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:16.816           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:16.816           Suspending scanning... <0xb57b6b90>
05      08/29/08 15:16:16.872           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
01      08/29/08 15:16:16.962           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:17.026           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:17.026           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:17.026           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:17.026           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:17.026           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:17.027           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:17.027           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:17.139           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:17.200           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:17.200           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:17.200           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:17.200           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:17.200           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:17.269           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:18.194           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:18.198           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:18.198           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:18.426           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:18.484           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:18.484           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:18.484           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:18.484           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:18.484           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:18.493           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:18.724           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:18.727           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:18.727           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:18.964           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:19.025           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:19.025           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:19.025           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:19.025           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:19.025           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:19.121           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:20.176           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:20.179           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:20.179           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:20.407           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:20.465           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:20.465           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:20.465           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:20.465           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:20.465           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:20.473           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:20.587           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:20.590           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:20.590           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:20.757           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:20.817           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:20.817           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:20.817           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:20.817           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:20.817           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:20.885           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:20.928           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:20.931           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:20.931           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:21.143           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:21.206           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:21.206           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:21.206           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:21.206           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:21.206           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:21.225           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:23.960           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:23.963           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:23.963           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:37.562           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:37.626           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:37.626           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:37.626           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:37.626           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:37.626           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:37.665           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:37.987           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:37.990           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:37.990           Suspending scanning... <0xb57b6b90>
01      08/29/08 15:16:38.227           received channel: 19
 <0xb57b6b90>
05      08/29/08 15:16:38.285           Can't connect RFCOMM socket 00:1C:CC:4C:73:E5, channel 19 <0xb57b6b90>
05      08/29/08 15:16:38.285           Waiting any operation with the socket to finish... <0xb57b6b90>
05      08/29/08 15:16:38.285           BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb57b6b90>
05      08/29/08 15:16:38.285           Failed to connect to PlutoMO. We'll resume scanning <0xb57b6b90>
05      08/29/08 15:16:38.286           Resuming scanning... <0xb57b6b90>
05      08/29/08 15:16:38.385           Inquiry started <0xb67b8b90>
05      08/29/08 15:16:40.348           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>
05      08/29/08 15:16:40.351           About to connect to PlutoMO. We'll suspend scanning... <0xb57b6b90>
05      08/29/08 15:16:40.351           Suspending scanning... <0xb57b6b90>
05      08/29/08 15:16:40.379           Detected device mac: 00:1C:CC:4C:73:E5 link quality: 0 <0xae7a8b90>

Cylon7

  • Regular Poster
  • **
  • Posts: 15
    • View Profile
    • Apollo Smart Homes
Re: Java/ J2ME mobile orbiter
« Reply #204 on: August 29, 2008, 07:33:06 am »
colinjones Who is your cell phone carrier? That log and those symptoms are pretty much the same as mine. Your phone may not allow the midlet to access the Bluetooth stack. I tried it on my roommate's AT&T Blackberry & also got the same result.
“True words aren't charming,
   Charming words aren't true.
People who know aren't learned,
   Learned people don't know."
--Lao Tzu, Tao Te Ching, 81

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #205 on: August 29, 2008, 09:28:55 am »
As I say, twice now it has connected and gotten the first couple or orbiter screens, just doesn't seem to last. The provider is an Australian one, they don't lock or restrict the handset, so something else seems to be influencing it here.... hmmm...

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #206 on: September 05, 2008, 11:59:38 pm »
OK, I've gotten further now - I can tail the BT dongle log and see it communicating with the mobile phone, sending screens and receiving keys.

I had to manually pair the device in KDE Desktop otherwise the phone just kept prompting for the dcerouter-0 pairing pin. But although the javamo screen comes up with the UI, and I can choose a screen like video, the initial screen and subsequent screen takes a very long time to display, and then the java applet just seems to crash and stop responding, and the log stops indicating any activity. I can't stop the applet, and in the end I have to turn the phone off and on again. Then it indicates there was an unhandled exception in the java applet and allows me to start it again. But the same behaviour.

The other thing is that the orbiter seem to stay permanently in **RUN_CONFIG** mode, and the device never registers. Is that right? I tried forcing it by setting the controlled by, room and entertainment area, turning off the reconfigure tick box and the resend VMC tick box then reloaded. Now it creates a device log file, but is obviously trying to start the Symbian pluto .sis file and failing... is this device even supposed to register and run that code when it is being used as the javamo?

JimmyGosling

  • Veteran
  • ***
  • Posts: 105
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #207 on: September 17, 2008, 08:48:51 pm »
Very interesting, I had the Nokia e62, which I hated, mostly due to the AT&T cripple.  I was actually kind of happy when it was run over.
Then I picked up the BB Curve 8310, which I love.  I have not been able to hook it up to LMCE yet though.  Obviously still some issues to get through.  I'll keep my eye on this thread though and most likely try it out on my phone to see if I get the same results.

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Java/ J2ME mobile orbiter
« Reply #208 on: September 17, 2008, 11:51:49 pm »
Code: [Select]
Core was generated by `./Bluetooth_Dongle -d 26'.
Program terminated with signal 11, Segmentation fault.
#0  0xb7d131f6 in sdp_gen_tid () from /usr/lib/libbluetooth.so.2
(gdb) bt
#0  0xb7d131f6 in sdp_gen_tid () from /usr/lib/libbluetooth.so.2
#1  0xb7d181c8 in sdp_service_search_attr_req () from /usr/lib/libbluetooth.so.2
#2  0xb7d360f0 in sdp_lookup_pluto_rfcomm_channel (target={b = "\204\026=�\030"}) at sdpbrowse.cpp:50
#3  0xb7d35c0e in BDCommandProcessor_Linux_Bluetooth (this=0x8252840, sMacAddressPhone=@0xb5602e2c, sMacAddressDongle=@0xb5602e28, pDevice=0x824eb80) at BDCommandProcessor_Linux_Bluetooth.cpp:78
#4  0xb7d63eb9 in BDCommandProcessor_BluetoothDongle (this=0x8252840, pBluetooth_Dongle=0x8248b78, sMacAddressPhone=@0xb5602f9c, pPhoneDevice=0x824eb80) at BDCommandProcessor_BluetoothDongle.cpp:39
#5  0x08078f7f in DCE::Bluetooth_Dongle::CMD_Link_with_mobile_orbiter (this=0x8248b78, sMac_address=@0xb5603108, sVMC_File=@0xb5603104, sConfig_File=@0xb5603100, sCMD_Result=@0xb56030e0, pMessage=0x82526c0)
    at Bluetooth_Dongle.cpp:755
#6  0x080836f5 in DCE::Bluetooth_Dongle_Command::ReceivedMessage (this=0x8248b78, pMessageOriginal=0x82526c0) at ../Gen_Devices/Bluetooth_DongleBase.h:203
#7  0xb7aed655 in DCE::HandleRequestSocket::RunThread (this=0x8248b78) at HandleRequestSocket.cpp:174
#8  0xb7aed9b2 in BeginHandleRequestThread (HRqSock=0x8248b78) at HandleRequestSocket.cpp:31
#9  0xb79d646b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb783673e in clone () from /lib/tls/i686/cmov/libc.so.6
(gdb) disassemble
Dump of assembler code for function sdp_gen_tid:
0xb7d131f0 <sdp_gen_tid+0>: push   %ebp
0xb7d131f1 <sdp_gen_tid+1>: mov    %esp,%ebp
0xb7d131f3 <sdp_gen_tid+3>: mov    0x8(%ebp),%edx
0xb7d131f6 <sdp_gen_tid+6>: movzwl 0x10(%edx),%eax
0xb7d131fa <sdp_gen_tid+10>: lea    0x1(%eax),%ecx
0xb7d131fd <sdp_gen_tid+13>: mov    %cx,0x10(%edx)
0xb7d13201 <sdp_gen_tid+17>: pop    %ebp
0xb7d13202 <sdp_gen_tid+18>: ret   
End of assembler dump.
rock your home - http://www.agocontrol.com home automation

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #209 on: September 18, 2008, 12:14:48 am »
Hari, was that post directed at me? And if so, are you saying I should run that command?