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

posde

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2974
  • Wastes Life On LinuxMCE Since 2007
    • View Profile
    • My Home
Re: Java/ J2ME mobile orbiter
« Reply #315 on: April 10, 2009, 11:41:00 pm »
meh, should have read the logs. 

Quote
+Not starting device 43 Bluetooth Dongle - binary "LaunchBluetooth_Dongle.sh" is not found.
Does this need to be logged as a bug against 8.10?

Yes, it should be filed as a bug. Plugging in a bluetooth USB stick, should automatically install the pluto-bluetooth-dongle. If it does not, it is a bug, imho

ProfFalken

  • Regular Poster
  • **
  • Posts: 26
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #316 on: April 11, 2009, 08:13:37 am »

matrex

  • Veteran
  • ***
  • Posts: 67
  • 16 Years Linux exp.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #317 on: April 11, 2009, 07:30:34 pm »
I got javamo to install on my phone. I am getting can't access JSR082. Where would I look to troubleshoot. If you need more info let me know.
Hybrid core Gigabyte GA-EP45-UD3R m/b 2.8Ghz 2 gig ram. HVR1600 on the core. 2 Orbiter on Android for control 1 phone the other tablet. Running 10.04

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5497
  • DOES work for LinuxMCE.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #318 on: April 11, 2009, 07:35:55 pm »
This means your phone does not have the necessary extensions to allow bluetooth access from your Java Virtual Machine. Sorry, your journey ends here with that phone.

-Thom

ProfFalken

  • Regular Poster
  • **
  • Posts: 26
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #319 on: April 11, 2009, 09:18:09 pm »
I got javamo to install on my phone. I am getting can't access JSR082. Where would I look to troubleshoot. If you need more info let me know.

Which phone are you using? If you check the wiki there is a link to a list of phones that support JSR-082.  My current mobile is a Samsung SGH-U900 SOUL that advertises that it support Bluetooth and Java, yet you can't install 3rd party apps and it doesn't have JSR-082.  I'll never buy Samsung again. 

I've obtained a free SIM from one of the networks here in the UK and I'm using my old SE-K750i as my MO - it works a treat!

PF.

matrex

  • Veteran
  • ***
  • Posts: 67
  • 16 Years Linux exp.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #320 on: April 11, 2009, 11:28:40 pm »
I am using the LG Rumor. It rus java so I said what the hell i'll give it a shot. I figured it would may run it even though it was not in the list. I was thinking maybe I misread something in the wiki or forgot to install something extra that maybe is not included in the wiki. Thats ok i'll just scrap that idea and wait till my contract with my service runs out and get one that is known to work. but at the price they are now, i just cant budget for one of them now. Thanx for the feedback.
Hybrid core Gigabyte GA-EP45-UD3R m/b 2.8Ghz 2 gig ram. HVR1600 on the core. 2 Orbiter on Android for control 1 phone the other tablet. Running 10.04

Purplexus

  • Regular Poster
  • **
  • Posts: 28
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #321 on: April 21, 2009, 08:32:11 am »
To expand further on the Samsung Omnia..

It is a phone which is to be an IPhone killer.
Since the IPhone won't allow for 3rd party apps to be installed easily...
why not focus on the Omnia and get it as not only an orbiter... but also the best way to control linux MCE

Since the FIIRE cheif is no longer available, I have been looking for a way to get a bluetooth gyration remote
for linux and the Omnia seems to have everything required to replace the Cheif with the follow ME option.

The omnia has all of the following built in...   Accelerometer, Bluetooth, Touchscreen,JAVA + FLASH CAPABLE, does it need more to control linux MCE as well as the cheif?

Help me out here if I am wrong.

ProfFalken

  • Regular Poster
  • **
  • Posts: 26
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #322 on: April 21, 2009, 09:49:25 am »
The omnia has all of the following built in...   Accelerometer, Bluetooth, Touchscreen,JAVA + FLASH CAPABLE, does it need more to control linux MCE as well as the cheif?

It needs Java JSR-082.

My phone has Java and can run all sorts of downloadable apps, but because it doesn't support JSR-082, I can't use it as a MO.

I've just googled the Omnia and I can't find any reference to JSR-082 support, although I did find a comment on one site stating that Samsung do _not_ use JSR-082 so you may be out of luck.

On the up-side, it appears to run Windows Mobile, so you may not need JSR-082 as you caould run the windows MO natively, although you'd need to confirm this.

PF.


hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Java/ J2ME mobile orbiter
« Reply #323 on: April 21, 2009, 12:12:09 pm »
Since the IPhone won't allow for 3rd party apps to be installed easily...
hu? Installing apps from the store is straightforward...
br, Hari
rock your home - http://www.agocontrol.com home automation

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5497
  • DOES work for LinuxMCE.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #324 on: May 30, 2009, 08:25:32 am »
Am running 0810 as you all know,..

I am using a Samsung Behold (TGH-919). App installs and runs, no error messages, but screen is white:

My symbian Nokia N70 works great, and handles just fine until....
 
Bluetooth dongle dies repeatedly with segfault:

--- Relevant Backtrace ---

(gdb) bt
#0  0xb7dfe98f in sdp_gen_tid () from /usr/lib/libbluetooth.so.3
#1  0xb7dfe093 in sdp_service_search_attr_req () from /usr/lib/libbluetooth.so.3
#2  0xb7e1cd9b in sdp_lookup_pluto_rfcomm_channel (target={b = "3\206�220$"}) at sdpbrowse.cpp:50
#3  0xb7e1c872 in BDCommandProcessor_Linux_Bluetooth (this=0xb3253080, sMacAddressPhone=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb5391e54 "�200\215�\224f���$\b\t"}}, sMacAddressDongle=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb5391e58 "\224f���$\b\t"}}, pDevice=0x9b140a8) at BDCommandProcessor_Linux_Bluetooth.cpp:78
#4  0xb7e4b796 in BDCommandProcessor_BluetoothDongle (this=0xb3253080, pBluetooth_Dongle=0x9a7df30, sMacAddressPhone=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb5391fb8 "�200\215�B!9�,�t�@�\t(f�\t�177\215��200\215�\224f��pf�\t\\�t\bf�\t�\220\215�Z\"9��$\b\t"}}, pPhoneDevice=0x9b140a8) at BDCommandProcessor_BluetoothDongle.cpp:39
#5  0x08078b46 in DCE::Bluetooth_Dongle::CMD_Link_with_mobile_orbiter (this=0x9a7df30, sMac_address=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb5392220 "�200\215�\202"}}, sVMC_File=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb539221c "d\220\215��200\215�\202"}}, sConfig_File=
        {static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xb5392218 "�216\215�d\220\215��200\215�\202"}}, sCMD_Result=@0xb53920e4, pMessage=0xb3252920)
    at Bluetooth_Dongle.cpp:755
#6  0x08083806 in DCE::Bluetooth_Dongle_Command::ReceivedMessage (this=0x9a7df30, pMessageOriginal=0xb3252920)
    at ../Gen_Devices/Bluetooth_DongleBase.h:203
#7  0xb7bcbc57 in DCE::HandleRequestSocket::RunThread (this=0x9a7df30) at HandleRequestSocket.cpp:174
#8  0xb7bcb547 in BeginHandleRequestThread (HRqSock=0x9a7df30) at HandleRequestSocket.cpp:31
#9  0xb7ab150f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#10 0xb790aa0e in clone () from /lib/tls/i686/cmov/libc.so.6
(gdb) quit
The program is running.  Exit anyway? (y or n) y

------------------------------------

10   05/30/09 2:19:16.799      Start of scan loop <0xb62b3b90>
10   05/30/09 2:19:16.799      Attached to BT adapter: hci0   20:13:4A:30:40:90
 <0xb62b3b90>
05   05/30/09 2:19:16.799      Inquiry started <0xb62b3b90>
10   05/30/09 2:19:17.011      Sending Have nothing command <0xb4ab0b90>
10   05/30/09 2:19:17.142      Analyzing device 00:24:90:C0:86:33. Existing 0x93e2f50, connected 0  <0xb62b3b90>
10   05/30/09 2:19:17.142      Bluetooth dongle intercepted new device.  We're not connected.  Proceeding like normal. <0xb62b3b90>
10   05/30/09 2:19:17.142      Adding device to map1: N/A m_mapPhoneDevice_Detected size is now: 2 <0xb62b3b90>
10   05/30/09 2:19:17.142      NewDeviceThread started <0xb20ffb90>
05   05/30/09 2:19:17.142      Detected device mac: 00:24:90:C0:86:33 link quality: -72 <0xb20ffb90>
10   05/30/09 2:19:17.142      Socket::SendMessage type 2 id 4 from 84 to -1001 <0xb20ffb90>
10   05/30/09 2:19:17.144      pthread_create returned with 0 <0xb62b3b90>
10   05/30/09 2:19:17.155      Receive string: MESSAGE 155            <0xb52b1b90>
10   05/30/09 2:19:17.155      Received MESSAGE 155            0x9143478 device: 84 <0xb52b1b90>
10   05/30/09 2:19:17.155      Received Message type 1 ID 60 from 9 to 84 (device: 84) resp 0 <0xb52b1b90>
05   05/30/09 2:19:17.155      About to connect to PlutoMO. We'll suspend scanning... <0xb52b1b90>
05   05/30/09 2:19:17.155      Suspending scanning... <0xb52b1b90>
10   05/30/09 2:19:17.155      start of const 00:24:90:C0:86:33 <0xb52b1b90>
10   05/30/09 2:19:17.247      The scanning is suspended. We'll ignore the results of this scan <0xb62b3b90>
01   05/30/09 2:19:17.317      received channel: 19
 <0xb52b1b90>
05   05/30/09 2:19:17.342      Can't connect RFCOMM socket 00:24:90:C0:86:33, channel 19 <0xb52b1b90>
05   05/30/09 2:19:17.342      Waiting any operation with the socket to finish... <0xb52b1b90>
05   05/30/09 2:19:17.342      BDCommandProcessor_Linux_Bluetooth is destroyed. <0xb52b1b90>
05   05/30/09 2:19:17.342      Failed to connect to PlutoMO. We'll resume scanning <0xb52b1b90>
05   05/30/09 2:19:17.342      Resuming scanning... <0xb52b1b90>
10   05/30/09 2:19:17.346      Start of scan loop <0xb62b3b90>
10   05/30/09 2:19:17.347      Attached to BT adapter: hci0   20:13:4A:30:40:90
 <0xb62b3b90>
05   05/30/09 2:19:17.347      Inquiry started <0xb62b3b90>
10   05/30/09 2:19:18.036      Sending Have nothing command <0xb4ab0b90>
10   05/30/09 2:19:18.503      Analyzing device 00:24:90:C0:86:33. Existing 0x93e3408, connected 0  <0xb62b3b90>
10   05/30/09 2:19:18.504      Bluetooth dongle intercepted new device.  We're not connected.  Proceeding like normal. <0xb62b3b90>
10   05/30/09 2:19:18.504      Adding device to map1: N/A m_mapPhoneDevice_Detected size is now: 2 <0xb62b3b90>
10   05/30/09 2:19:18.504      NewDeviceThread started <0xb20ffb90>
05   05/30/09 2:19:18.504      Detected device mac: 00:24:90:C0:86:33 link quality: -74 <0xb20ffb90>
10   05/30/09 2:19:18.504      Socket::SendMessage type 2 id 4 from 84 to -1001 <0xb20ffb90>
10   05/30/09 2:19:18.507      pthread_create returned with 0 <0xb62b3b90>
10   05/30/09 2:19:18.527      Receive string: MESSAGE 155            <0xb52b1b90>
10   05/30/09 2:19:18.527      Received MESSAGE 155            0x9143478 device: 84 <0xb52b1b90>
10   05/30/09 2:19:18.527      Received Message type 1 ID 60 from 9 to 84 (device: 84) resp 0 <0xb52b1b90>
05   05/30/09 2:19:18.527      About to connect to PlutoMO. We'll suspend scanning... <0xb52b1b90>
05   05/30/09 2:19:18.527      Suspending scanning... <0xb52b1b90>
10   05/30/09 2:19:18.527      start of const 00:24:90:C0:86:33 <0xb52b1b90>
10   05/30/09 2:19:18.611      The scanning is suspended. We'll ignore the results of this scan <0xb62b3b90>
Return code: 139
3   05/30/09 02:19:18   84 (spawning-device)   Device died... count=2/50 dev=84
Sat May 30 02:19:18 EDT 2009 died

------------------------------

00:24:90:C0:86:33 is the samsung phone.

This seems to happen regardless of whether the phone is running JavaMO or NOT... wtf?!

am scratching my head on this one.. wth?

Any thoughts ?

-Thom

hari

  • Administrator
  • LinuxMCE God
  • *****
  • Posts: 2420
    • View Profile
    • ago control
Re: Java/ J2ME mobile orbiter
« Reply #325 on: May 30, 2009, 01:01:46 pm »
did you pair phone and dongle?

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

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5497
  • DOES work for LinuxMCE.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #326 on: May 30, 2009, 05:10:43 pm »
how? every time i do a scan, it never finds the computer. *scratch-head*

-Thom

Aletha Emmy

  • Making baby steps
  • Posts: 3
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #327 on: July 04, 2009, 12:15:49 am »
As you may know LinuxMCE supports smartphones under Symbian OS 1st edition, Windows Mobile 2003 and Treo as mobile Orbiters to control your home. It uses Bluetooth to communicate with smarthome system. So, it’s too difficult port every time the code to the new version of mobile OS.
newbielink:http://voipsipsdk.com/ [nonactive]

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5497
  • DOES work for LinuxMCE.
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #328 on: July 04, 2009, 06:39:08 am »
Althea, if I may correct you,

Speaking as one of the developers actually working on the code:

The Mobile orbiter itself, is a very simple program that grabs images from the server, and transmits a simple packet format representing button presses and touch coordinates. The packet format is called BD, and is transmitted over an RFCOMM channel (up until the JavaMO, this was a hard-coded channel # 9, with the JavaMO, Hari patched the BD comms library to do SDP lookups to ask the phone for a free channel and negotiate this on a per-phone basis.), as such the client itself is very simple, and all of the processing is done by the DCE device Bluetooth_Dongle, which is in itself a subclass of Orbiter.)

For Symbian and Windows Smartphone, the code is built as an amalgam of code in src/PlutoMO, and src/VIPShared. src/PlutoMO provides the basic mobile orbiter shell, while VIPShared provides BDcommon and the VMC (VIP Menu Container) decoding which allows the phone to be used in offline mode.

The Windows Smartphone versions run atop the SMARTPHONE_2003 and SMARTPHONE_2005 variants, which are the only two SDKs of this type that microsoft has released. Porting this to new versions of Windows Mobile basically would entail #ifdefs to most commonly work around differences in core API (as the Windows CE core in these systems change like crazy from release to release), while it's not dead easy, it's not difficult, either. I am working on a port to WM5 and WM6 for the standard Orbiter. But I need hardware to test the results of the code.

Your comments about the Symbian variant were also incorrect, in that Hari has revamped the code to work on Symbian v2 (sis) and Symbian v3 (sisx). It took Hari roughly a weekend to do this, which makes me more mad that someone else didn't step up and do this sooner. Given the utter simplicity of the code, and the fact that Symbian's SDK is pretty consistent below, other ports to UIQ and other variants of Symbian are very possible. People, step up and do it! :)

-Thom

massabuntu

  • Veteran
  • ***
  • Posts: 97
    • View Profile
Re: Java/ J2ME mobile orbiter
« Reply #329 on: August 26, 2009, 10:45:19 pm »
Here the keymap of my Nokia6233