barry-devel — Development discussion mailing list

Re: [Barry-devel] Cross Compiling Barry for android 2.1

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

Hi Ganesh,

Thanks for your feedback!

Your solution of using older versions of Barry is interesting, and I'm glad
you found a version that worked, but it also points to a problem in Barry
itself.

I'd rather have it possible to ./configure Barry for minimal systems.
Could you tell me why the latest Barry was unsatisfactory for your needs?

If you need a way to disable the non-USB libraries, then I should add that
as a configure option.  It shouldn't be too hard, and then you'd be running
the latest USB part of the library, and following our protocol improvements
as well.

- Chris



On Wed, Sep 21, 2011 at 03:09:26PM +0530, ganesh hegde wrote:
> Dear Chris,
> 
> Sorry for delayed reply.
> I have tried to compile barry-0.0.1 version in android since I needed very
> minimal features in barry i.e. to detect blackberry phone.
> But I couldn't  compile it successfully due to some compile time issues.
> 
> It compiles in normal linux pc running over 2.6.28...But btool is unable to
> detect the device
> I even tried barry from 0.0.1 to 0.14...All the packages gave same error...
> 
> Lastly I successfully compiled barry 0.15  on linux PC...and It is able to
> detect the device. So I am thinking to port barry 0.15 for my android
> platform.
> 
> I have ported libusb 0.1.12 on android since barry needs that.
> Now I am cross compiling Barry 0.15 on android
> 
> Thanks for the support,
> 
> Regards,
> Ganesh Hegde
> 
> On Fri, Sep 16, 2011 at 1:43 PM, Chris Frey <cd...@fo...> wrote:
> 
> > Thanks!
> >
> > Is there anything I should add to Barry to make this static compile easier?
> >
> > There's not much I can do about the lack of exception support.
> >
> > - Chris
> >
> >
> > On Fri, Sep 16, 2011 at 09:43:44AM +0200, Nicolas CARRIER wrote:
> > > Hello
> > > Compiling barry for Android is not trivial.
> > > The two main problems we encountered are barry's dependencies and the
> > > lack of some features in Android's C and C++ support (mainly
> > > exceptions). What we had to do was to compile statically the binary we
> > > were interested in, statically linked with another version of the libc
> > > and statically linked with barry's other dependencies. The binary is
> > > bigger (and maybe slower, don't know) but it was the least painful
> > > solution we could think of.
> >  >
> > >
> > > On 09/16/11 09:17, Chris Frey wrote:
> > > > Hi Ganesh,
> > > >
> > > > This is a good question to keep on the mailing list, for future
> > reference,
> > > > so I've CC'd the list as well.
> > > >
> > > > As for cross compiling, I believe it is simply a matter of overriding
> > the
> > > > configure variables for CC and CXX.  I haven't done this myself,
> > though,
> > > > so there are probably details I'm missing.
> > > >
> > > > You shouldn't have to write your own Makefile, unless Android
> > cross-compiling
> > > > cannot use autoconf for some reason.
> > > >
> > > > Please keep us posted on your progress!
> > > >
> > > > - Chris
> > > >
> > > >
> > > > On Fri, Sep 16, 2011 at 12:28:11PM +0530, ganesh hegde wrote:
> > > >> Dear Chris,
> > > >>
> > > >> I am currently working on Barry porting on android.
> > > >> My primary task is to cross compile barry for android 2.1 running over
> > linux
> > > >> 2.6.28 and ARM Processor.
> > > >> Because I have to connect my Blackberry phone to android device
> > through
> > > >> USB. So android device has to detect the my phone.
> > > >>
> > > >> Please suggest me how to write barry make file for android so that it
> > will
> > > >> include all the dependencies for barry.
> > > >> and what is the procedure to cross compile it for android?
> > > >>
> > > >> Regards,
> > > >> Ganesh Hegde
> > > >
> > ------------------------------------------------------------------------------
> > > > BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> > > > http://p.sf.net/sfu/rim-devcon-copy2
> > > > _______________________________________________
> > > > Barry-devel mailing list
> > > > Bar...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/barry-devel
> > > >
> > >
> > >
> > > --
> > > Nicolas CARRIER - 6081 - 2?me centre
> > >
> > >
> > >
> > ------------------------------------------------------------------------------
> > > BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> > > http://p.sf.net/sfu/rim-devcon-copy2
> > > _______________________________________________
> > > Barry-devel mailing list
> > > Bar...@li...
> > > https://lists.sourceforge.net/lists/listinfo/barry-devel
> >

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

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

Hi Keith,

That's odd.  What happens if you cycle power by removing the battery,
and then try again?

- Chris



On Tue, Sep 20, 2011 at 07:42:32PM +0200, Keith Moseley wrote:
> Hello Chris,
> 
> Thanks for the reply.
> 
> Something changed between the time that I sent my e-mail and when you
> asked me to run the btool -t commmand.
> 
> I have (obviously) had the Blackberry disconnected and reconnected in
> between my e-mail and your reply.
> Heres what happens now, when I try and sync and run the btool -t
> command.
> 
> I connect the Blackberry (selecting USB mode on the phone as previously)
> and run the msynctool --sync EvoBarry.
> The result of this is the following:
> ------------------------------------------
> keith@KMLIXPC:~$ msynctool --sync EvoBarry
> Synchronizing group "EvoBarry" 
> Member 2 of type barry-sync had an error while connecting: Controller:
> requested mode not supported
> Member 1 of type evo2-sync just connected
> Member 1 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
> Error while synchronizing: Unable to connect one of the members
> ---------------------------------------
> 
> This did not happen before :-(
> 
> Not surprisingly, when I run the btool -t command, I get the following:
> 
> -------------------------------------
> keith@KMLIXPC:~$ btool -t
> Blackberry devices found:
> Device ID: 0x8211368. PIN: 2795c8e7, Description: RIM BlackBerry Device
> Using device (PIN): 2795c8e7
> Barry::Error caught: Controller: requested mode not supported
> ------------------------------------
> I re-ran the sequence after adding the debug mode and have attached the
> resulting debug files with this e-mail.
> 
> Thanks for your support
> 
> BR
> 
> Keith Moseley





> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

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

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

Hello Chris,

Thanks for the reply.

Something changed between the time that I sent my e-mail and when you
asked me to run the btool -t commmand.

I have (obviously) had the Blackberry disconnected and reconnected in
between my e-mail and your reply.
Heres what happens now, when I try and sync and run the btool -t
command.

I connect the Blackberry (selecting USB mode on the phone as previously)
and run the msynctool --sync EvoBarry.
The result of this is the following:
------------------------------------------
keith@KMLIXPC:~$ msynctool --sync EvoBarry
Synchronizing group "EvoBarry" 
Member 2 of type barry-sync had an error while connecting: Controller:
requested mode not supported
Member 1 of type evo2-sync just connected
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error while synchronizing: Unable to connect one of the members
---------------------------------------

This did not happen before :-(

Not surprisingly, when I run the btool -t command, I get the following:

-------------------------------------
keith@KMLIXPC:~$ btool -t
Blackberry devices found:
Device ID: 0x8211368. PIN: 2795c8e7, Description: RIM BlackBerry Device
Using device (PIN): 2795c8e7
Barry::Error caught: Controller: requested mode not supported
------------------------------------
I re-ran the sequence after adding the debug mode and have attached the
resulting debug files with this e-mail.

Thanks for your support

BR

Keith Moseley

Re: [Barry-devel] Fedora Bug

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

On Mon, Sep 19, 2011 at 10:06:16PM +0200, Nicolas wrote:
> To solve the issues, I have to downgrade the libusb release used.
> Indeed, in fedora, you use libusb-compat and it's different of libusb.
> 
> libusb.x86_64 0:0.1.12-23.fc13 => works well
> libusb-0.1.3-9.fc15.x86_64 => doesn't work.
> 
> But in your case, it seems different...
> 
> For barry team :) we should switch to libusb1.

It would be nice to use the latest, and Barry support both now, but
from the above tests, it sounds like the old libusb is still the most
stable?

Were you able to determine why it was failing?

Thanks for the feedback!
- Chris

Re: [Barry-devel] [Patch] Build RPM

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

On Sat, Sep 17, 2011 at 04:02:18PM +0200, Nicolas wrote:
> Hi Chris,
> 
> For a friend, I have used your opensync/barry git repository to build
> RPM.
> 
> I'm not a RPM expert (I have never worked with the distributions using
> it). But with your build framework, I haven't found the target to build
> each RPM whereas it's possible for deb.
> 
> So you'll find in attachment a patch to add some targets. The spec files
> aren't perfect... but it works.


HUGE thanks, Nicolas!  I've applied it, and added a few tweaks, for
the environment, etc.

Much appreciated!

- Chris

Re: [Barry-devel] Fedora Bug

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

Le samedi 17 septembre 2011 à 09:16 -0600, Nathanael Noblet a écrit :
> Hello,
> 
>   Just received this bug report. Wondering if you have any insights or
> if there is missing information in the
> report. https://bugzilla.redhat.com/show_bug.cgi?id=739303
> 
> 
> Thanks,
> -- 
> Nathanael

Hi,

This week-end, I have to help someone with barry on fedora 64 bits.

To solve the issues, I have to downgrade the libusb release used.
Indeed, in fedora, you use libusb-compat and it's different of libusb.

libusb.x86_64 0:0.1.12-23.fc13 => works well
libusb-0.1.3-9.fc15.x86_64 => doesn't work.

But in your case, it seems different...

For barry team :) we should switch to libusb1.

Nicolas

Re: [Barry-devel] Fedora Bug

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

On Sat, Sep 17, 2011 at 09:16:33AM -0600, Nathanael Noblet wrote:
> Hello,
> 
>   Just received this bug report. Wondering if you have any insights or if
> there is missing information in the report.
> https://bugzilla.redhat.com/show_bug.cgi?id=739303

According to the trace log, it appears that he also pressed the Backup
button, and it was in the process of preparing to do a backup when it crashed.

As far as I can tell, m_desktop was null, or invalid, when it crashed,
and that should only happen if the device is in the disconnected state.
So far, I'm unable to find a way to get to the backup stage in the
disconnected state.  The code should block that, and as far as I can
tell, it does.

Does he still have the core dump file?  If he is able to use gdb
to examine the value of m_desktop at backtrace #1, I'd like to know if
it is null or some other value.  That might be asking a lot though. :-)

He says that he ran barrybackup in debug mode (-d)... it would be useful
if he posted that output as well.

Thanks,
- Chris

[Barry-devel] Fedora Bug

[Nathanael N. <nat...@gm...>]

Hello,

  Just received this bug report. Wondering if you have any insights or if
there is missing information in the report.
https://bugzilla.redhat.com/show_bug.cgi?id=739303

Thanks,
-- 
Nathanael

[Barry-devel] [Patch] Build RPM

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

Hi Chris,

For a friend, I have used your opensync/barry git repository to build
RPM.

I'm not a RPM expert (I have never worked with the distributions using
it). But with your build framework, I haven't found the target to build
each RPM whereas it's possible for deb.

So you'll find in attachment a patch to add some targets. The spec files
aren't perfect... but it works.

Nicolas

Re: [Barry-devel] Cross Compiling Barry for android 2.1

[Nicolas C. <nic...@pa...>]

On 09/16/11 10:13, Chris Frey wrote:
> Thanks!
>
> Is there anything I should add to Barry to make this static compile easier?
I don't think so. It involves compilation with another toolchain, and 
linking with previously pre-compiled libraries (libusb...). So I think 
it's rather dependent on the needs and the tools.
But I'm not the specialist of the question, I wasn't myself in charge of 
pppob's compilation under android.

Maybe the simplest would be to provide pre-compiled binaries, but I fear 
it would be too much time-consuming.
> There's not much I can do about the lack of exception support.
>
> - Chris
>
>
> On Fri, Sep 16, 2011 at 09:43:44AM +0200, Nicolas CARRIER wrote:
>> Hello
>> Compiling barry for Android is not trivial.
>> The two main problems we encountered are barry's dependencies and the
>> lack of some features in Android's C and C++ support (mainly
>> exceptions). What we had to do was to compile statically the binary we
>> were interested in, statically linked with another version of the libc
>> and statically linked with barry's other dependencies. The binary is
>> bigger (and maybe slower, don't know) but it was the least painful
>> solution we could think of.
>>
>>
>> On 09/16/11 09:17, Chris Frey wrote:
>>> Hi Ganesh,
>>>
>>> This is a good question to keep on the mailing list, for future reference,
>>> so I've CC'd the list as well.
>>>
>>> As for cross compiling, I believe it is simply a matter of overriding the
>>> configure variables for CC and CXX.  I haven't done this myself, though,
>>> so there are probably details I'm missing.
>>>
>>> You shouldn't have to write your own Makefile, unless Android cross-compiling
>>> cannot use autoconf for some reason.
>>>
>>> Please keep us posted on your progress!
>>>
>>> - Chris
>>>
>>>
>>> On Fri, Sep 16, 2011 at 12:28:11PM +0530, ganesh hegde wrote:
>>>> Dear Chris,
>>>>
>>>> I am currently working on Barry porting on android.
>>>> My primary task is to cross compile barry for android 2.1 running over linux
>>>> 2.6.28 and ARM Processor.
>>>> Because I have to connect my Blackberry phone to android device through
>>>> USB. So android device has to detect the my phone.
>>>>
>>>> Please suggest me how to write barry make file for android so that it will
>>>> include all the dependencies for barry.
>>>> and what is the procedure to cross compile it for android?
>>>>
>>>> Regards,
>>>> Ganesh Hegde
>>> ------------------------------------------------------------------------------
>>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>>> http://p.sf.net/sfu/rim-devcon-copy2
>>> _______________________________________________
>>> Barry-devel mailing list
>>> Bar...@li...
>>> https://lists.sourceforge.net/lists/listinfo/barry-devel
>>>
>>
>> -- 
>> Nicolas CARRIER - 6081 - 2?me centre
>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
>> http://p.sf.net/sfu/rim-devcon-copy2
>> _______________________________________________
>> Barry-devel mailing list
>> Bar...@li...
>> https://lists.sourceforge.net/lists/listinfo/barry-devel
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
> .
>


-- 
Nicolas CARRIER - 6081 - 2ème centre

Re: [Barry-devel] Cross Compiling Barry for android 2.1

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

Thanks!

Is there anything I should add to Barry to make this static compile easier?

There's not much I can do about the lack of exception support.

- Chris


On Fri, Sep 16, 2011 at 09:43:44AM +0200, Nicolas CARRIER wrote:
> Hello
> Compiling barry for Android is not trivial.
> The two main problems we encountered are barry's dependencies and the 
> lack of some features in Android's C and C++ support (mainly 
> exceptions). What we had to do was to compile statically the binary we 
> were interested in, statically linked with another version of the libc 
> and statically linked with barry's other dependencies. The binary is 
> bigger (and maybe slower, don't know) but it was the least painful 
> solution we could think of.
> 
> 
> On 09/16/11 09:17, Chris Frey wrote:
> > Hi Ganesh,
> >
> > This is a good question to keep on the mailing list, for future reference,
> > so I've CC'd the list as well.
> >
> > As for cross compiling, I believe it is simply a matter of overriding the
> > configure variables for CC and CXX.  I haven't done this myself, though,
> > so there are probably details I'm missing.
> >
> > You shouldn't have to write your own Makefile, unless Android cross-compiling
> > cannot use autoconf for some reason.
> >
> > Please keep us posted on your progress!
> >
> > - Chris
> >
> >
> > On Fri, Sep 16, 2011 at 12:28:11PM +0530, ganesh hegde wrote:
> >> Dear Chris,
> >>
> >> I am currently working on Barry porting on android.
> >> My primary task is to cross compile barry for android 2.1 running over linux
> >> 2.6.28 and ARM Processor.
> >> Because I have to connect my Blackberry phone to android device through
> >> USB. So android device has to detect the my phone.
> >>
> >> Please suggest me how to write barry make file for android so that it will
> >> include all the dependencies for barry.
> >> and what is the procedure to cross compile it for android?
> >>
> >> Regards,
> >> Ganesh Hegde
> > ------------------------------------------------------------------------------
> > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> > http://p.sf.net/sfu/rim-devcon-copy2
> > _______________________________________________
> > Barry-devel mailing list
> > Bar...@li...
> > https://lists.sourceforge.net/lists/listinfo/barry-devel
> >
> 
> 
> -- 
> Nicolas CARRIER - 6081 - 2?me centre
> 
> 
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Cross Compiling Barry for android 2.1

[Nicolas C. <nic...@pa...>]

Hello
Compiling barry for Android is not trivial.
The two main problems we encountered are barry's dependencies and the 
lack of some features in Android's C and C++ support (mainly 
exceptions). What we had to do was to compile statically the binary we 
were interested in, statically linked with another version of the libc 
and statically linked with barry's other dependencies. The binary is 
bigger (and maybe slower, don't know) but it was the least painful 
solution we could think of.


On 09/16/11 09:17, Chris Frey wrote:
> Hi Ganesh,
>
> This is a good question to keep on the mailing list, for future reference,
> so I've CC'd the list as well.
>
> As for cross compiling, I believe it is simply a matter of overriding the
> configure variables for CC and CXX.  I haven't done this myself, though,
> so there are probably details I'm missing.
>
> You shouldn't have to write your own Makefile, unless Android cross-compiling
> cannot use autoconf for some reason.
>
> Please keep us posted on your progress!
>
> - Chris
>
>
> On Fri, Sep 16, 2011 at 12:28:11PM +0530, ganesh hegde wrote:
>> Dear Chris,
>>
>> I am currently working on Barry porting on android.
>> My primary task is to cross compile barry for android 2.1 running over linux
>> 2.6.28 and ARM Processor.
>> Because I have to connect my Blackberry phone to android device through
>> USB. So android device has to detect the my phone.
>>
>> Please suggest me how to write barry make file for android so that it will
>> include all the dependencies for barry.
>> and what is the procedure to cross compile it for android?
>>
>> Regards,
>> Ganesh Hegde
> ------------------------------------------------------------------------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>


-- 
Nicolas CARRIER - 6081 - 2ème centre

Re: [Barry-devel] Cross Compiling Barry for android 2.1

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

Hi Ganesh,

This is a good question to keep on the mailing list, for future reference,
so I've CC'd the list as well.

As for cross compiling, I believe it is simply a matter of overriding the
configure variables for CC and CXX.  I haven't done this myself, though,
so there are probably details I'm missing.

You shouldn't have to write your own Makefile, unless Android cross-compiling
cannot use autoconf for some reason.

Please keep us posted on your progress!

- Chris


On Fri, Sep 16, 2011 at 12:28:11PM +0530, ganesh hegde wrote:
> Dear Chris,
> 
> I am currently working on Barry porting on android.
> My primary task is to cross compile barry for android 2.1 running over linux
> 2.6.28 and ARM Processor.
> Because I have to connect my Blackberry phone to android device through
> USB. So android device has to detect the my phone.
> 
> Please suggest me how to write barry make file for android so that it will
> include all the dependencies for barry.
> and what is the procedure to cross compile it for android?
> 
> Regards,
> Ganesh Hegde

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

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

Hi Keith,

Can you run 'btool -t' on your device, to see what kind of databases are
available?

Thanks,
- Chris


On Mon, Sep 05, 2011 at 08:17:30PM +0200, Keith Moseley wrote:
> Hello,
> 
> I have installed and configured Barry version 017 on my Ubuntu 10.10 (32
> bit) as per the instructions on the 
> website.
> 
> I have a Blackberry Bold that I am trying to sync the calendar of, with
> the 
> Evolution Calendar on my Ubuntu.
> 
> I have configured the applications opensync and Barry, being careful to
> add the PIN Number for my device as well
> as the password for it.
> 
> This is the result I obtain when I try to sync with the msync command:
> 
> keith@KMLIXPC:~$ msynctool --sync EvoBarry
> Synchronizing group "EvoBarry" 
> Member 1 of type evo2-sync just connected
> Member 2 of type barry-sync had an error while connecting: Desktop:
> database name not found: Calendar
> Member 1 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
> Error while synchronizing: Unable to connect one of the members
> 
> I therefore exported the OSYNC_TRACE variable, re-ran the msync, after
> disconnecting and reconnecting the phone via the
> usb cable. I have a number of trace files from that execution that
> basically say the same thing as the error message.
> When Barry attempts to read from the Blackberry, it is unable to find
> the database Calendar. I have enclosed those
> files with this e-mail for your information.
> 
> Is the problem simply due to the fact that the Bold is not supported ?
> How can I get support for the Bold - could you for example point me in
> the right direction? I would be willing to 
> experiment/code/test.
> 
> Best Regards
> 
> Keith Moseley





> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better 
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

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

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

Hello,

I have installed and configured Barry version 017 on my Ubuntu 10.10 (32
bit) as per the instructions on the 
website.

I have a Blackberry Bold that I am trying to sync the calendar of, with
the 
Evolution Calendar on my Ubuntu.

I have configured the applications opensync and Barry, being careful to
add the PIN Number for my device as well
as the password for it.

This is the result I obtain when I try to sync with the msync command:

keith@KMLIXPC:~$ msynctool --sync EvoBarry
Synchronizing group "EvoBarry" 
Member 1 of type evo2-sync just connected
Member 2 of type barry-sync had an error while connecting: Desktop:
database name not found: Calendar
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error while synchronizing: Unable to connect one of the members

I therefore exported the OSYNC_TRACE variable, re-ran the msync, after
disconnecting and reconnecting the phone via the
usb cable. I have a number of trace files from that execution that
basically say the same thing as the error message.
When Barry attempts to read from the Blackberry, it is unable to find
the database Calendar. I have enclosed those
files with this e-mail for your information.

Is the problem simply due to the fact that the Bold is not supported ?
How can I get support for the Bold - could you for example point me in
the right direction? I would be willing to 
experiment/code/test.

Best Regards

Keith Moseley

Re: [Barry-devel] New tool based on libbarry

[<al...@ma...>]

> On Wed, Aug 31, 2011 at 01:27:37PM -0400, Chris Frey wrote:
>> > I'm happy you added it to git, and I like your
>> > improvements (you did all the boring part for me :-) ). I think there
>> is
>> > just one problem left, that the buffer is hard-coded to 1000000 bytes,
>> so
>> > it might overflow if it is used with high resolution devices
>> (tablets?).
>> > What do you think?
>> > Alberto
>>
>> Good catch.  I missed that one. :-)
>
> Ok, that's fixed now, along with some low level sequence packet stuff
> that I found along the way. :-)
>
> Also, there is a new library API call, which can be used to do 24bit or
> 32bit
> bitmap conversions, instead of having to do it in the app.
>
> Enjoy,
> - Chris
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>

Great! I think I have discovered what was the problem with the mailing
list: if the address is in the form "Barry mailing list"
<barry-devel@blabla> the message is ignored. If I put only the address, it
is correctly sent. Weird!
Alberto

Re: [Barry-devel] New tool based on libbarry

[<al...@ma...>]

> On Wed, Aug 31, 2011 at 07:42:42PM +0200, al...@ma... wrote:
>> No, nothing, the message seems correctly sent but it never appears on
>> the
>> list. I'm trying again this time CCing the list...
>> Alberto
>
> That seemed to work.  I've set your subscription to send ack messages
> when you post.  Please try again with a reply just to the list and see
> what
> happens.
>
> - Chris

Thank you! Let's see...
Alberto
>
>
> ------------------------------------------------------------------------------
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
> price-free! And you'll get a free "Love Thy Logs" t-shirt when you
> download Logger. Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>

Re: [Barry-devel] New tool based on libbarry

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

On Wed, Aug 31, 2011 at 01:27:37PM -0400, Chris Frey wrote:
> > I'm happy you added it to git, and I like your
> > improvements (you did all the boring part for me :-) ). I think there is
> > just one problem left, that the buffer is hard-coded to 1000000 bytes, so
> > it might overflow if it is used with high resolution devices (tablets?).
> > What do you think?
> > Alberto
> 
> Good catch.  I missed that one. :-)

Ok, that's fixed now, along with some low level sequence packet stuff
that I found along the way. :-)

Also, there is a new library API call, which can be used to do 24bit or 32bit
bitmap conversions, instead of having to do it in the app.

Enjoy,
- Chris

Re: [Barry-devel] New tool based on libbarry

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

On Wed, Aug 31, 2011 at 07:42:42PM +0200, al...@ma... wrote:
> No, nothing, the message seems correctly sent but it never appears on the
> list. I'm trying again this time CCing the list...
> Alberto

That seemed to work.  I've set your subscription to send ack messages
when you post.  Please try again with a reply just to the list and see what
happens.

- Chris

Re: [Barry-devel] New tool based on libbarry

[<al...@ma...>]

> On Wed, Aug 31, 2011 at 06:00:40PM +0200, al...@ma... wrote:
>> Hi Chris, I write directly to you since the mailing list software seems
>> to
>> be eating all my replies.
>
> That's odd... do you get any bounceback messages or errors?

No, nothing, the message seems correctly sent but it never appears on the
list. I'm trying again this time CCing the list...
Alberto

>
>
>> I'm happy you added it to git, and I like your
>> improvements (you did all the boring part for me :-) ). I think there is
>> just one problem left, that the buffer is hard-coded to 1000000 bytes,
>> so
>> it might overflow if it is used with high resolution devices (tablets?).
>> What do you think?
>> Alberto
>
> Good catch.  I missed that one. :-)
>
> Thanks,
> - Chris
>
>

Re: [Barry-devel] New tool based on libbarry

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

On Mon, Aug 29, 2011 at 04:53:46PM -0400, Chris Frey wrote:
> On Fri, Aug 26, 2011 at 07:09:53PM +0200, al...@ma... wrote:
> > Hi, I have written a small tool that uses libbarry and SDL to display a
> > (sort of) video of your blackberry screen. I'd like to share it here in
> > case it is useful to someone. Feedback is appreciated!
> > 
> > To compile: g++ scr.cc -lSDL -lbarry -o scr
> > 
> > Note: currently refresh rate is set to 2fps in order to keep the device
> > responsive. If you need higher fps, change the commented line in the
> > source file (from 500 to something like 100).
> 
> Thanks very much!  Do you mind if I include it in the official Barry tree?


I've actually added this to the Barry tree, under tools.

The configure script checks for the SDL library, and builds bwatch if
available.

I've added the usual -p -P and -v command line switches.

I added a -d switch to specify the delay interval between screen updates.

I changed the code to resize the screen, in case the screenshot dimensions
change.  This happens on devices like the Storm, when you tilt it and it
goes into landscape mode.

I moved the Probe code out of the main loop.

I added it to the binary packages, along with a man page.

Thanks again!  This is a neat little utility.

- Chris

Re: [Barry-devel] New tool based on libbarry

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

On Fri, Aug 26, 2011 at 07:09:53PM +0200, al...@ma... wrote:
> Hi, I have written a small tool that uses libbarry and SDL to display a
> (sort of) video of your blackberry screen. I'd like to share it here in
> case it is useful to someone. Feedback is appreciated!
> 
> To compile: g++ scr.cc -lSDL -lbarry -o scr
> 
> Note: currently refresh rate is set to 2fps in order to keep the device
> responsive. If you need higher fps, change the commented line in the
> source file (from 500 to something like 100).

Thanks very much!  Do you mind if I include it in the official Barry tree?

- Chris

[Barry-devel] New tool based on libbarry

[<al...@ma...>]

Hi, I have written a small tool that uses libbarry and SDL to display a
(sort of) video of your blackberry screen. I'd like to share it here in
case it is useful to someone. Feedback is appreciated!

To compile: g++ scr.cc -lSDL -lbarry -o scr

Note: currently refresh rate is set to 2fps in order to keep the device
responsive. If you need higher fps, change the commented line in the
source file (from 500 to something like 100).

Re: [Barry-devel] Fw: BlackBerry Curve Backup Error

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

Hi John,

Sorry for the delay in resonding.

Are you able to build binary packages yourself?

In order to further debug this issue, I'll need to add some logging
around the usb_bulk_read call.

Thanks,
- Chris



On Fri, Jul 29, 2011 at 06:42:24PM -0700, John Heffington wrote:
> Couldn't figure out how to respond to the message in this thread.? The original 
> message is at the end.? Chris responded below.? My response to Chris is:
> 
> I sent you the full information that was displayed.? The message is consistently 
> displayed at 25%.? Sometimes more than 25% is backed up, but ultimately, I get 
> the same message and the backuup process stops.
> 
> On Sun, Jul 24, 2011 at 01:53:14PM -0700, John Heffington wrote:
> > Error Message:
> > 
> > Backup ... error (-34, Numerical result out of range):
> > Error in usb_bulk_read
> 
> Was that the full error message?
> 
> 
> > It is suspected that due to international characters in these records,
> > the BlackBerry uses a different low-level protocol which Barry Backup
> > does not support yet.? Alternatively, there may be records that cannot
> > be edited in your device.? If this occurs in a database such as Address
> > Book, sometimes a restore of just that database may fix the issue.
> 
> The above numerical error does not seem to match this particular
> warning.? We probably shouldn't assume it has to do with international
> characters yet.? I added that warning for a different error, but it seems
> like it popped up too liberally.
> 
> Do you get the "out of range" error consistently?? Does it usually happen
> at the same point of the backup?? Perhaps a particular database?
> What happens if you disable that database in the configuration?
> 
> Thanks,
> - Chris
> 
> 
> 
> 
> 
> ----- Forwarded Message ----
> From: John Heffington <jm....@ya...>
> To: bar...@li...
> Cc: me <jm....@ya...>
> Sent: Sun, July 24, 2011 4:53:14 PM
> Subject: BlackBerry Curve Backup Error
> 
> 
> The problem occurred while backing up:
> 
> a BlackBerry Curve 8530
> v5.0.0.1030 (Bundle 1675 Platform 4.2.0.451)
> 
> Operating System: Fedora 15/Gnome 3
> 
> Barry version 0.17
> 
> Installed Barry with Fedora Add/Remove Program
> 
> Error Message:
> 
> Backup ... error (-34, Numerical result out of range):
> Error in usb_bulk_read
> 
> It is suspected that due to international characters in these records,
> the BlackBerry uses a different low-level protocol which Barry Backup
> does not support yet.? Alternatively, there may be records that cannot
> be edited in your device.? If this occurs in a database such as Address
> Book, sometimes a restore of just that database may fix the issue.
> 
> 
> Please let me know how I can track the progress on fixing this problem.
> 
> Thank you
> 
> Mark Heffington

> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

[Barry-devel] Fw: BlackBerry Curve Backup Error

[John H. <jm....@ya...>]

Couldn't figure out how to respond to the message in this thread.  The original 
message is at the end.  Chris responded below.  My response to Chris is:

I sent you the full information that was displayed.  The message is consistently 
displayed at 25%.  Sometimes more than 25% is backed up, but ultimately, I get 
the same message and the backuup process stops.

On Sun, Jul 24, 2011 at 01:53:14PM -0700, John Heffington wrote:
> Error Message:
> 
> Backup ... error (-34, Numerical result out of range):
> Error in usb_bulk_read

Was that the full error message?


> It is suspected that due to international characters in these records,
> the BlackBerry uses a different low-level protocol which Barry Backup
> does not support yet.  Alternatively, there may be records that cannot
> be edited in your device.  If this occurs in a database such as Address
> Book, sometimes a restore of just that database may fix the issue.

The above numerical error does not seem to match this particular
warning.  We probably shouldn't assume it has to do with international
characters yet.  I added that warning for a different error, but it seems
like it popped up too liberally.

Do you get the "out of range" error consistently?  Does it usually happen
at the same point of the backup?  Perhaps a particular database?
What happens if you disable that database in the configuration?

Thanks,
- Chris





----- Forwarded Message ----
From: John Heffington <jm....@ya...>
To: bar...@li...
Cc: me <jm....@ya...>
Sent: Sun, July 24, 2011 4:53:14 PM
Subject: BlackBerry Curve Backup Error


The problem occurred while backing up:

a BlackBerry Curve 8530
v5.0.0.1030 (Bundle 1675 Platform 4.2.0.451)

Operating System: Fedora 15/Gnome 3

Barry version 0.17

Installed Barry with Fedora Add/Remove Program

Error Message:

Backup ... error (-34, Numerical result out of range):
Error in usb_bulk_read

It is suspected that due to international characters in these records,
the BlackBerry uses a different low-level protocol which Barry Backup
does not support yet.  Alternatively, there may be records that cannot
be edited in your device.  If this occurs in a database such as Address
Book, sometimes a restore of just that database may fix the issue.


Please let me know how I can track the progress on fixing this problem.

Thank you

Mark Heffington