[Interest] [ Android ] Bluetooth Obex Object Push Profile (OPP) implementation?

[Edward Sutton]

Hi Alex,

Sorry for my Android ignorance, where may I browse the Android Bluetooth API?

>It is my understand that existing apps provide their own obex implementation on top of Androids RFCOMM/SPP profile.

I think that is what I need to research.

Hopefully I can find a non-GPL source code example of how push a file from Android to my device.

It sounds like maybe if I just set the header correctly, the rest *might* not be that complicated.

Unless there is some type of flow control involved?

Thanks!

-Ed


> On Jun 19, 2015, at 3:31 AM, Blasche Alexander <alexander.blasche at theqtcompany.com> wrote:
>
> Hi,
>
> >Not supported because Qt does not support it?  Or because Android does not support it?
> >How do 3rd party Android apps implement Obex?  Any ideas?  Java source code?
>
> To the best of my knowledge there is no Android API to achieve that. There are some comments about private API's but they are not consistent.
>
> It's been a while since I checked last but most of the new Andoird APIs in the area of Bluetooth are related to Bluetooth Low Energy.
> I'd be happy to fix this if you know of an API that exists Android wide (not just on devices from manufacturer X).
>
> It is my understand that existing apps provide their own obex implementation on top of Androids RFCOMM/SPP profile.
>
> >By the way Qt 5.5 Bluetooth SPP profile works great under both OS X and Android.
>
> Great to hear.
>
> --
> Alex

This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.