barry-devel — Development discussion mailing list

[Barry-devel] Android build support patch

[Toby G. <tob...@re...>]

Hi,

I've managed to get Barry building and working on Android. Currently 
it's just libbarry and the tools which only make use of libbarry (e.g. 
not bjdwp as it uses libbarrydp and libarryjdwp).

The changes are in my github repository at:
git://github.com/tobygray/barry.git

They start at b44a645067696424c6c4056e958db767ec1c66e1, and continue 
from there.

To build for Android it's just necessary to change into the Android 
directory and run make, provided that ndk-build (from the Android NDK 
http://developer.android.com/sdk/ndk/index.html) is in the path.

The biggest problem with these patches that the Android build system 
isn't very compatible with autoconf and configure so the build scripts 
are entirely separate. This means that updating Makefile.am or config 
flags might requite changing the Android.mk file.

Does anyone have any comments, suggestions or improvements?

Regards,

Toby

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

On Mon, Oct 31, 2011 at 11:00:01AM +0000, Toby Gray wrote:
> The problem for QNX with AC_FUNC_STRNLEN is that as QNX is a cross 
> compilation environment, the AC_LANG_PROGRAM macro doesn't attempt to 
> compile and run the test for detecting faulty strnlen implementations. 
> The AC_FUNC_STRNLEN macro attempts to guess based on the OS name, with 
> AIX being broken and everything else being working.

Thanks for the explanation!  I don't do much cross compiling, so I must
rely on those who do. :-)


> I've put an updated fix which adds strnlen.c to the AC_LIBOBJs like the 
> AC_FUNC_STRNLEN macro does in c93500984d36395e75454cfebe7cb706dc685151 
> on my github branch. Does that look more suitable?

I like!  Merged.  Thanks.

- Chris

Re: [Barry-devel] Black Berry as a modem

[Chris F. <cd...@fo...>]

On Sat, Oct 29, 2011 at 11:08:57AM -0500, Orion wrote:
> Hello, and install "barry" in Linux, but I can not run the Blackberry as a
> modem.
> You have a reset?
> Thank you.

You'll have to provide some debugging info in order for us to help you.

Are you able to use the modem feature from Windows?  i.e. is tethering
supported by your provider?

What kind of reset are you looking for?  The most reliable one is unplugging
the battery and reinserting it.

If that fails, you'll need to follow the Troubleshooting section on this
page:

	http://www.netdirect.ca/software/packages/barry/modem.php

If your Blackberry is capable of Bluetooth, you might try that as well.

- Chris

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

On Mon, Oct 31, 2011 at 10:46:11AM +0000, Toby Gray wrote:
> On 28/10/11 23:19, Chris Frey wrote:
> > Also, wouldn't this change be more accurate?
> >
> > --- a/configure.ac
> > +++ b/configure.ac
> > @@ -344,7 +344,7 @@ AM_CONDITIONAL([WITH_FUSE], [test "$FUSE_FOUND" = "1"])
> >   AM_CONDITIONAL([WITH_SDL],  [test "$SDL_FOUND" = "1"])
> >   AM_CONDITIONAL([WITH_SYNC], [test "$GLIB2_FOUND" = "1" -a "$SYNC_ENABLED" = "yes"])
> >
> > -AC_CHECK_LIB([pthread], [main], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
> > +AC_CHECK_LIB([pthread], [pthread_create], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
> >   THREAD_LIBRARY_LIBS=
> >   if test "$HAVE_LIBPTHREAD" = "1"; then
> >      THREAD_LIBRARY_LIBS="-lpthread"
> 
> Yes, that's a good point. I was just in the mindset of "need to check 
> for if libpthread.so exists", rather than checking it's got a useful 
> function.

Actually, when I looked closer, the [main] part was in the original code,
before your change, so that wasn't yours. :-)  Sorry.  I changed it anyhow
and ran my tests, and it didn't seem to break anything, so I'll
keep the [pthread_create] style.

- Chris

Re: [Barry-devel] QNX build support patch

[Toby G. <tob...@re...>]

On 28/10/11 22:55, Chris Frey wrote:
>
> Cool. :-)  I'm told that I'll be given a Playbook to test with shortly.
> I'm assuming you're building on plain QNX on a desktop of some kind?

Yes, currently just building and running on QNX 6.5.0. I'll post 
something if/when I try it on a Playbook, although I'm currently 
distracted by trying to get Barry working on Android.

> Do you think it is portable enough that it could also run on the Playbook,
> or do you think some things will be changing now that it is owned by RIM?

I can't see any reason why it shouldn't work on a Playbook. I would 
imagine that the only issues will be due to changes made to the QNX SDK 
when making the Playbook SDK, but hopefully those won't be major issues 
and will be similarly minor configure script fixes.

Regards,

Toby

Re: [Barry-devel] QNX build support patch

[Toby G. <tob...@re...>]

On 29/10/11 00:10, Chris Frey wrote:
> On Fri, Oct 28, 2011 at 12:59:33PM +0100, Toby Gray wrote:
>> The changes are all on the master branch of my github repository:
>> git://github.com/tobygray/barry.git
> I've pulled in all your changes except the strnlen ones, since I want
> to give them a bit more thought.  I just don't fully understand the
> logic path on QNX, and I'm a bit worried with both AC_FUNC_STRNLEN
> including strnlen.c and us doing it manually yet as well.

That's a good point, I'd not appreciated that AC_FUNC_STRNLEN added 
strnlen.c to AC_LIBOBJ.

The problem for QNX with AC_FUNC_STRNLEN is that as QNX is a cross 
compilation environment, the AC_LANG_PROGRAM macro doesn't attempt to 
compile and run the test for detecting faulty strnlen implementations. 
The AC_FUNC_STRNLEN macro attempts to guess based on the OS name, with 
AIX being broken and everything else being working.

I've put an updated fix which adds strnlen.c to the AC_LIBOBJs like the 
AC_FUNC_STRNLEN macro does in c93500984d36395e75454cfebe7cb706dc685151 
on my github branch. Does that look more suitable?

Regards,

Toby

Re: [Barry-devel] QNX build support patch

[Toby G. <tob...@re...>]

On 28/10/11 23:19, Chris Frey wrote:
> Also, wouldn't this change be more accurate?
>
> --- a/configure.ac
> +++ b/configure.ac
> @@ -344,7 +344,7 @@ AM_CONDITIONAL([WITH_FUSE], [test "$FUSE_FOUND" = "1"])
>   AM_CONDITIONAL([WITH_SDL],  [test "$SDL_FOUND" = "1"])
>   AM_CONDITIONAL([WITH_SYNC], [test "$GLIB2_FOUND" = "1" -a "$SYNC_ENABLED" = "yes"])
>
> -AC_CHECK_LIB([pthread], [main], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
> +AC_CHECK_LIB([pthread], [pthread_create], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
>   THREAD_LIBRARY_LIBS=
>   if test "$HAVE_LIBPTHREAD" = "1"; then
>      THREAD_LIBRARY_LIBS="-lpthread"

Yes, that's a good point. I was just in the mindset of "need to check 
for if libpthread.so exists", rather than checking it's got a useful 
function.

Regards,

Toby

Re: [Barry-devel] QNX build support patch

[Nicolas <pr...@fr...>]

Indeed, it seems to be a new feature with OS 2.

Regards,

Nicolas

Le samedi 29 octobre 2011 à 19:01 +0000, Vincent Ardern a écrit :
> While not answering your question, the PlayBook most definitely does have a micro-usb port.
>  
> --
> Kind Regards,
> Vincent Ardern
> 
> -----Original Message-----
> From: Nicolas <pr...@fr...>
> Date: Sat, 29 Oct 2011 14:21:38 
> To: Barry project development discussion<bar...@li...>
> Reply-To: Barry project development discussion
> 	<bar...@li...>
> Subject: Re: [Barry-devel] QNX build support patch
> 
> Le vendredi 28 octobre 2011 à 12:59 +0100, Toby Gray a écrit :
> > Hi,
> > 
> > I've made a few changes to the barry configure scripts and a couple of 
> > source files to allow building of barry on QNX 
> > (http://en.wikipedia.org/wiki/QNX). It's mostly just getting configure 
> > to detect which libraries to use; e.g. QNX has all it's networking APIs 
> > in libsocket.so but doesn't have libpthread.so, all it's pthread stuff 
> > is in it's standard libraries.
> > 
> > I've not given this any detailed testing and I've not even attempted to 
> > run it on a BlackBerry Playbook yet.
> > 
> > The changes are all on the master branch of my github repository:
> > git://github.com/tobygray/barry.git
> > 
> > Any review comments or suggested improvements welcome.
> > 
> > Regards,
> > 
> > Toby
> 
> Hi,
> 
> Great... But I don't understand how to use barry on Playbook.
> 
> Playbook hasn't get an USB port ?
> 
> How do you use it ?
> 
> Regards,
> 
> Nicolas
> 
> 
> 
> ------------------------------------------------------------------------------
> Get your Android app more play: Bring it to the BlackBerry PlayBook 
> in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
> for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
> it is! http://p.sf.net/sfu/android-dev2dev
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
> ------------------------------------------------------------------------------
> Get your Android app more play: Bring it to the BlackBerry PlayBook 
> in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
> for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
> it is! http://p.sf.net/sfu/android-dev2dev
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] QNX build support patch

[Vincent A. <v.a...@gm...>]

While not answering your question, the PlayBook most definitely does have a micro-usb port.
 
--
Kind Regards,
Vincent Ardern

-----Original Message-----
From: Nicolas <pr...@fr...>
Date: Sat, 29 Oct 2011 14:21:38 
To: Barry project development discussion<bar...@li...>
Reply-To: Barry project development discussion
	<bar...@li...>
Subject: Re: [Barry-devel] QNX build support patch

Le vendredi 28 octobre 2011 à 12:59 +0100, Toby Gray a écrit :
> Hi,
> 
> I've made a few changes to the barry configure scripts and a couple of 
> source files to allow building of barry on QNX 
> (http://en.wikipedia.org/wiki/QNX). It's mostly just getting configure 
> to detect which libraries to use; e.g. QNX has all it's networking APIs 
> in libsocket.so but doesn't have libpthread.so, all it's pthread stuff 
> is in it's standard libraries.
> 
> I've not given this any detailed testing and I've not even attempted to 
> run it on a BlackBerry Playbook yet.
> 
> The changes are all on the master branch of my github repository:
> git://github.com/tobygray/barry.git
> 
> Any review comments or suggested improvements welcome.
> 
> Regards,
> 
> Toby

Hi,

Great... But I don't understand how to use barry on Playbook.

Playbook hasn't get an USB port ?

How do you use it ?

Regards,

Nicolas



------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Barry-devel mailing list
Bar...@li...
https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] Black Berry as a modem

[Orion <ori...@gm...>]

Hello, and install "barry" in Linux, but I can not run the Blackberry as a
modem.
You have a reset?
Thank you.


-- 
--------------------------------------------------
                       ____                 ____
  /\   |\  | \    / | |  __    /\     /\   | [] |
 /__\  | \ |  \  /  | | |  |  /__\   /__\  |    \
/    \ |  \|   \/   | |____| /    \ /    \ | /\  \
                                       ______
                                     °|      |°°°°
ANDRÉS  VICENTE  GALVIS  ARCINIEGAS  °|   ___|°°°°
INGENIERO ELECTRÓNICO                °\   \     /°
UNIVERSIDAD DEL VALLE                °°\___\   /°°
anv...@gm...                    °°°°°°°\ /°°°
Tel:4018525--Cel:3117264854          °°°°°°°°/°°°°
CALI-COLOMBIA                         Universidad
                                       del Valle
--------------------------------------------------

Re: [Barry-devel] QNX build support patch

[Nicolas <pr...@fr...>]

Le vendredi 28 octobre 2011 à 12:59 +0100, Toby Gray a écrit :
> Hi,
> 
> I've made a few changes to the barry configure scripts and a couple of 
> source files to allow building of barry on QNX 
> (http://en.wikipedia.org/wiki/QNX). It's mostly just getting configure 
> to detect which libraries to use; e.g. QNX has all it's networking APIs 
> in libsocket.so but doesn't have libpthread.so, all it's pthread stuff 
> is in it's standard libraries.
> 
> I've not given this any detailed testing and I've not even attempted to 
> run it on a BlackBerry Playbook yet.
> 
> The changes are all on the master branch of my github repository:
> git://github.com/tobygray/barry.git
> 
> Any review comments or suggested improvements welcome.
> 
> Regards,
> 
> Toby

Hi,

Great... But I don't understand how to use barry on Playbook.

Playbook hasn't get an USB port ?

How do you use it ?

Regards,

Nicolas

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

On Fri, Oct 28, 2011 at 12:59:33PM +0100, Toby Gray wrote:
> The changes are all on the master branch of my github repository:
> git://github.com/tobygray/barry.git

I've pulled in all your changes except the strnlen ones, since I want
to give them a bit more thought.  I just don't fully understand the
logic path on QNX, and I'm a bit worried with both AC_FUNC_STRNLEN
including strnlen.c and us doing it manually yet as well.

Thanks again!
- Chris

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

Also, wouldn't this change be more accurate?

--- a/configure.ac
+++ b/configure.ac
@@ -344,7 +344,7 @@ AM_CONDITIONAL([WITH_FUSE], [test "$FUSE_FOUND" = "1"])
 AM_CONDITIONAL([WITH_SDL],  [test "$SDL_FOUND" = "1"])
 AM_CONDITIONAL([WITH_SYNC], [test "$GLIB2_FOUND" = "1" -a "$SYNC_ENABLED" = "yes"])
 
-AC_CHECK_LIB([pthread], [main], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
+AC_CHECK_LIB([pthread], [pthread_create], [HAVE_LIBPTHREAD=1], [HAVE_LIBPTHREAD=0])
 THREAD_LIBRARY_LIBS=
 if test "$HAVE_LIBPTHREAD" = "1"; then
    THREAD_LIBRARY_LIBS="-lpthread"


- Chris

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

On Fri, Oct 28, 2011 at 05:55:21PM -0400, Chris Frey wrote:
> I'm curious how AC_FUNC_STRNLEN succeeds if AC_CHECK_FUNC([strnlen]...
> fails?  Can you give some background on what happened during your
> testing?

Rephrasing: how does AC_FUNC_STRNLEN succeed at all, if AC_CHECK_FUNC([strnlen]
fails? :-)

And if AC_FUNC_STRNLEN succeeds, is there some way that we can make it work
natively?

- Chris

Re: [Barry-devel] QNX build support patch

[Chris F. <cd...@fo...>]

On Fri, Oct 28, 2011 at 12:59:33PM +0100, Toby Gray wrote:
> Hi,
> 
> I've made a few changes to the barry configure scripts and a couple of 
> source files to allow building of barry on QNX 
> (http://en.wikipedia.org/wiki/QNX). It's mostly just getting configure 
> to detect which libraries to use; e.g. QNX has all it's networking APIs 
> in libsocket.so but doesn't have libpthread.so, all it's pthread stuff 
> is in it's standard libraries.

Thanks very much!  I'm just going through your commits now.

I'm curious how AC_FUNC_STRNLEN succeeds if AC_CHECK_FUNC([strnlen]...
fails?  Can you give some background on what happened during your
testing?


> I've not given this any detailed testing and I've not even attempted to 
> run it on a BlackBerry Playbook yet.

Cool. :-)  I'm told that I'll be given a Playbook to test with shortly.
I'm assuming you're building on plain QNX on a desktop of some kind?
Do you think it is portable enough that it could also run on the Playbook,
or do you think some things will be changing now that it is owned by RIM?

Thanks again for your patches,
- Chris

[Barry-devel] QNX build support patch

[Toby G. <tob...@re...>]

Hi,

I've made a few changes to the barry configure scripts and a couple of 
source files to allow building of barry on QNX 
(http://en.wikipedia.org/wiki/QNX). It's mostly just getting configure 
to detect which libraries to use; e.g. QNX has all it's networking APIs 
in libsocket.so but doesn't have libpthread.so, all it's pthread stuff 
is in it's standard libraries.

I've not given this any detailed testing and I've not even attempted to 
run it on a BlackBerry Playbook yet.

The changes are all on the master branch of my github repository:
git://github.com/tobygray/barry.git

Any review comments or suggested improvements welcome.

Regards,

Toby

Re: [Barry-devel] Just to say that barry work with new BB OS 7

[Chris F. <cd...@fo...>]

On Sat, Oct 08, 2011 at 09:45:59AM +0200, Nicolas wrote:
> Hi,
> 
> all is in the subject :)

Good to know!  Thanks for testing, and for reporting!

- Chris

[Barry-devel] Just to say that barry work with new BB OS 7

[Nicolas <pr...@fr...>]

Hi,

all is in the subject :)

Regards,

Nicolas

Re: [Barry-devel] Problem syncing with Bold, database name not found: Calendar

[Chris F. <cd...@fo...>]

On Tue, Oct 04, 2011 at 06:46:02PM +0200, Keith Moseley wrote:
> Hi Chris,
> 
> I tried taking out the battery and restarting the phone, but it still
> gives the same result.

Hi Keith,

The previous error you reported (requested mode not supported) is fairly
fundamental, and means that it can't enter the "RIM Desktop" mode, which
is needed to access the address book and contact databases.

I haven't seen this error much, so I wonder if it is a newer firmware.
Could you tell me your current firmware version and model number?
Is this one of the very latest Bolds?

Thanks,
- Chris

Re: [Barry-devel] Problem syncing with Bold, database name not found: Calendar

[Keith M. <ke...@sm...>]

Hi Chris,

I tried taking out the battery and restarting the phone, but it still
gives the same result.

Best Regards

Keith Moseley

Re: [Barry-devel] replaying javaloader deviceinfo with raw commands

[Chris F. <cd...@fo...>]

On Thu, Sep 29, 2011 at 09:13:42PM -0400, Chris Frey wrote:
> In version 0.18...

To clarify, version 0.18 isn't officially released yet, but is the
current git tree.  I try to keep the git tree as stable as possible,
so that it is safe to use at any time.

- Chris

Re: [Barry-devel] replaying javaloader deviceinfo with raw commands

[Chris F. <cd...@fo...>]

On Thu, Sep 29, 2011 at 11:44:10AM +0200, nks escher wrote:
> I am trying to do a RIM_JavaLoader deviceinfo with just raw commands. In
> order to to this quick and dirty I changed the Controller::SelectMode
> function, present in src/controller.cc, while using brawchannel as a base.

Is this for personal research, or are you working around some limitation
in the library?  If the latter, please tell me, so I can fix the library. :-)


> I tried to use "m_zero.Receive(response);" here and there, maybe multiple
> responses interfere with the communication. However, no success. With using
> the -v option the following output is generated:
> 
> BulkWrite to endpoint 0x2:
>     00000000: 00 00 18 00 07 ff 00 07 52 49 4d 5f 4a 61 76 61
>  ........RIM_Java
>     00000010: 4c 6f 61 64 65 72 00 00                          Loader..

Mode open packet.


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 00 00 30 00 08 03 00 07 52 49 4d 5f 4a 61 76 61
>  ..0.....RIM_Java
>     00000010: 4c 6f 61 64 65 72 00 00 00 00 00 00 01 00 08 00
>  Loader..........
>     00000020: 02 00 08 00 03 01 00 00 04 01 00 00 05 10 03 00
>  ................

Mode response packet.


> BulkWrite to endpoint 0x2:
>     00000000: 00 00 08 00 0a 03 00 08                          ........
> 
> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 00 00 08 00 10 03 00 08                          ........

Socket open and success.


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 00 00 0c 00 13 03 01 00 00 00 00 00              ............

Sequence packet.


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 03 00 05 00 01                                   .....

Javaloader junk packet.  (we don't know exactly what this means, but doesn't
hurt to throw it away)


> BulkWrite to endpoint 0x2:
>     00000000: 03 00 08 00 64 00 00 00                          ....d...

Javaloader HELLO, simple command, no data.


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 00 00 0c 00 13 03 01 00 01 00 00 00              ............

Sequence packet.


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 03 00 08 00 65 00 00 00                          ....e...

Javaloader HELLO ACK from device.


> BulkWrite to endpoint 0x2:
>     00000000: 03 00 08 00 70 00 01 00                          ....p...

Javaloader UNKNOWN1 command (used to start stream)


> SocketZero::RawReceive: Endpoint 82
> Received:
>     00000000: 00 00 0c 00 13 03 01 00 02 00 00 00              ............

Sequence packet.

So the device is waiting for you to request the next javaloader response.
And probably because you haven't been reading all the sequence packets,
you've been writing commands way ahead of the device, and the handshaking
is out of whack.

Since it looks like you're using SocketZero, all the sequence packet
handling is up to you.  Since you're also using version 0.17.x, then
even at the non-zero socket level, the sequence packet handling is
somewhat up to you.  In version 0.18, I've tried to hide this sequence
packet handling inside the socket layer, so that the API is closer to
the Windows COM routines.  That's what the "SyncSend()" stuff is for
in 0.18.

Note that Javaloader commands are in the form of (cmd + size) + data.
Some commands are only commands and have no data packets.  Others have
data packets along behind.

You can see some of the logic in m_javaloader.cc.  It uses packet.cc
to create the raw data packets in memory.

Hope that helps,
- Chris

Re: [Barry-devel] NVSTORE_DUMP command

[Chris F. <cd...@fo...>]

On Thu, Sep 29, 2011 at 11:47:28AM +0200, nks escher wrote:
> Hi *,
> 
> Hardware: Blackberry 9700 bold
> Barry version: 0.17.3
> 
> While reverse engineering blackberry update files I found references to a
> command named NVSTORE_DUMP (and several others). This command is not
> supported by the original JavaLoader.exe or Barry. Do you know what this
> command does and if it is still possible to execute this command via an USB
> channel?

Hi Niek,

I have no knowledge what the NVSTORE_DUMP command may do.  There's only
brief mention in some of the contributed logs, but not enough to really
know what they do.

- Chris

[Barry-devel] NVSTORE_DUMP command

[nks e. <nks...@gm...>]

Hi *,

Hardware: Blackberry 9700 bold
Barry version: 0.17.3

While reverse engineering blackberry update files I found references to a
command named NVSTORE_DUMP (and several others). This command is not
supported by the original JavaLoader.exe or Barry. Do you know what this
command does and if it is still possible to execute this command via an USB
channel?

Regards,

Niek

[Barry-devel] replaying javaloader deviceinfo with raw commands

[nks e. <nks...@gm...>]

Hi *,

Hardware: Blackberry 9700 bold (OS6.0)
Barry version: 0.17.1

I am trying to do a RIM_JavaLoader deviceinfo with just raw commands. In
order to to this quick and dirty I changed the Controller::SelectMode
function, present in src/controller.cc, while using brawchannel as a base.
It is a dirty hack, I know, but it will be sufficient for my needs. It seems
that this will work but for some reason the communication gets stuck at a
certain point. I both sniffed the traffic of the bjavaloader and original
javaloader. The traffic is a bit different, but replaying both results in
the communication getting stuck at the same point. I send the following
commands:

try {

/* open USB channel: RIM_JavaLoader */
        unsigned char command[] = { 0x00, 0x00, 0x18, 0x00, 0x07, 0xff,
0x00, 0x07, 0x52, 0x49, 0x4d, 0x5f, 0x4a, 0x61, 0x76, 0x61, 0x4c, 0x6f,
0x61, 0x64, 0x65, 0x72, 0x00, 0x00 };
        Data toWrite(command, 24);
        m_zero.Send(toWrite, response);

        command = { 0x00, 0x00, 0x08, 0x00, 0x0a, 0x03, 0x00, 0x08 };
        toWrite = Data(command, 8);
        m_zero.Send(toWrite, response);

        command = { 0x03, 0x00, 0x08, 0x00, 0x64, 0x00, 0x00, 0x00 };
        toWrite = Data(command, 8);
        m_zero.Send(toWrite, response);

        command = { 0x03, 0x00, 0x08, 0x00, 0x70, 0x00, 0x01, 0x00 };
        toWrite = Data(command, 8);
        m_zero.Send(toWrite, response);

        command = { 0x03, 0x00, 0x05, 0x00, 0x00 };
        toWrite = Data(command, 5);
        m_zero.Send(toWrite, response);
}

I tried to use "m_zero.Receive(response);" here and there, maybe multiple
responses interfere with the communication. However, no success. With using
the -v option the following output is generated:

BulkWrite to endpoint 0x2:
    00000000: 00 00 18 00 07 ff 00 07 52 49 4d 5f 4a 61 76 61
 ........RIM_Java
    00000010: 4c 6f 61 64 65 72 00 00                          Loader..

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 00 00 30 00 08 03 00 07 52 49 4d 5f 4a 61 76 61
 ..0.....RIM_Java
    00000010: 4c 6f 61 64 65 72 00 00 00 00 00 00 01 00 08 00
 Loader..........
    00000020: 02 00 08 00 03 01 00 00 04 01 00 00 05 10 03 00
 ................

BulkWrite to endpoint 0x2:
    00000000: 00 00 08 00 0a 03 00 08                          ........

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 00 00 08 00 10 03 00 08                          ........

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 00 00 0c 00 13 03 01 00 00 00 00 00              ............

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 03 00 05 00 01                                   .....

BulkWrite to endpoint 0x2:
    00000000: 03 00 08 00 64 00 00 00                          ....d...

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 00 00 0c 00 13 03 01 00 01 00 00 00              ............

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 03 00 08 00 65 00 00 00                          ....e...

BulkWrite to endpoint 0x2:
    00000000: 03 00 08 00 70 00 01 00                          ....p...

SocketZero::RawReceive: Endpoint 82
Received:
    00000000: 00 00 0c 00 13 03 01 00 02 00 00 00              ............


And that is where it gets stuck. It does not even write the last command
defined. Anybody has an idea what the problem here is or what I could try?

Regards,

Nks