tomtetobe / remuco

Automatically exported from code.google.com/p/remuco
0 stars 0 forks source link

Remuco android client crash on bluetooth connect #139

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What is your environment?
* OS: Ubuntu 10.10
* Remuco version: pulled the source on 24/02/2011, 0.9.3
* Client device: Nexus One
* Player: Audacious on desktop

What steps will reproduce the problem?
1. Make sure you have paired between desktop and nexus one
2. Connect > bluetooth > Ok
3. Crash

What is the expected behavior? What happens instead?
Connect to remuco server on desktop, but it crashes

Additional information:
- Did a bluetooth file transfer, so bluetooth it is working
- Checked if there is access for apps to bluetooth, there is (SPAN if I 
remember well)

USB debug log Nexus One:
I/ActivityManager(   81): Starting activity: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
flg=0x10100000 cmp=remuco.client.android/.Remuco }
I/ActivityManager(   81): Start proc remuco.client.android for activity 
remuco.client.android/.Remuco: pid=28421 uid=10096 gids={3002, 3003, 1015}
W/InputManagerService(   81): Window already focused, ignoring focus gain of: 
com.android.internal.view.IInputMethodClient$Stub$Proxy@450e8cb0
I/System.out(28421): --- remuco.client.android.Remuco.onCreate()
I/Remuco  (28421): screensize: 320x533
I/Remuco  (28421): preferred image size: 320
I/Remuco  (28421): running on : Nexus One
I/Remuco  (28421): --- remuco.client.android.Remuco.onResume()
V/RenderScript_jni( 7715): surfaceDestroyed
I/Remuco  (28421): [PA] waking up connection
I/Remuco  (28421): [PA] cannot resume connection: not connected
I/Remuco  (28421): [PA] adding handler: Handler{44aa8160}
W/KeyCharacterMap(28421): No keyboard for id 65540
W/KeyCharacterMap(28421): Using default keymap: 
/system/usr/keychars/qwerty.kcm.bin
I/ActivityManager(   81): Displayed activity remuco.client.android/.Remuco: 
2182 ms (total 2182 ms)
I/Remuco  (28421): [CT] trying to connect 1 to  0
W/dalvikvm(28421): threadid=8: thread exiting with uncaught exception 
(group=0x4001d7e0)
E/AndroidRuntime(28421): FATAL EXCEPTION: Timer-0
E/AndroidRuntime(28421): java.lang.IllegalArgumentException:  is not a valid 
Bluetooth address
E/AndroidRuntime(28421):    at 
android.bluetooth.BluetoothDevice.<init>(BluetoothDevice.java:371)
E/AndroidRuntime(28421):    at 
android.bluetooth.BluetoothAdapter.getRemoteDevice(BluetoothAdapter.java:336)
E/AndroidRuntime(28421):    at 
remuco.client.android.io.BluetoothSocket.<init>(BluetoothSocket.java:69)
E/AndroidRuntime(28421):    at 
remuco.client.android.util.ConnectTask.run(ConnectTask.java:98)
E/AndroidRuntime(28421):    at java.util.Timer$TimerImpl.run(Timer.java:289)
W/ActivityManager(   81):   Force finishing activity 
remuco.client.android/.Remuco
W/InputManagerService(   81): Starting input on non-focused client 
com.android.internal.view.IInputMethodClient$Stub$Proxy@450853b8 (uid=10096 
pid=28421)
W/ActivityManager(   81): Activity pause timeout for HistoryRecord{44cffdb0 
remuco.client.android/.Remuco}
I/Remuco  (28421): --- remuco.client.android.Remuco.onPause()
I/Remuco  (28421): [PA] clear handler
I/Remuco  (28421): [PA] pausing connection
I/Remuco  (28421): [PA] cannot pause connection: not connected

Original issue reported on code.google.com by chrizz...@gmail.com on 24 Feb 2011 at 12:42

GoogleCodeExporter commented 9 years ago
Hmmm.. Just thought: I use 0.9.2.1 as server, 0.9.3.0 as android client. But it 
shouldn't matter, right?

Original comment by chrizz...@gmail.com on 24 Feb 2011 at 12:46

GoogleCodeExporter commented 9 years ago
Indeed 0.9.2/3 does not matter here. Looking that traceback, the problem seems 
to be that the Bluetooth address gets lost somewhere 
('java.lang.IllegalArgumentException: <empty string> is not a valid Bluetooth 
address'). I'll point Fabien on this issue (he currently works on the Android 
client).

Original comment by obensonne@googlemail.com on 24 Feb 2011 at 7:59

GoogleCodeExporter commented 9 years ago

Original comment by obensonne@googlemail.com on 8 Mar 2011 at 6:55

GoogleCodeExporter commented 9 years ago
Please try again with the Android client contained in the latest release 
(0.9.4).

Original comment by obensonne@googlemail.com on 17 Mar 2011 at 7:21