Re: [GSOC-UDPATE](17.08) Impress Remote
On 08/20/2012 05:00 PM, Michael Meeks wrote: One issue is powering up bluetooth on Android: documentation insists that you ask the user to switch on bluetooth: one option is to add an item Search for Bluetooth devices on the selection screen which does this, or alternatively to just ask the user every single time the app is started. I -imagine- that UX wise, enabling bluetooth during a pairing flow, and disabling it again if we don't connect is perhaps the best plan from a UX battery perspective ? Yes, as far as I know, you have to ask the user to turn on Bluetooth. You could create an Intent to show the Settings page for the user to do it. On the battery side: powering the radio down or going to lower power modes is handled by the lower stack, at least for the first round we shouldn't be too concerned about this, I guess (?) Regards, Muthu Subramanian ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [GSOC-UDPATE](17.08) Impress Remote
On Wed, 2012-08-22 at 08:36 +0300, Tor Lillqvist wrote: If it's ok with everyone I'm going to include cleaned bluetooth headers, from android, in the source tree to avoid the need for installing a library which isn't actually linked or used. (Headers viewable ... Sorry for replying late, but I am a bit unsure about this. Is it really a good idea to have these cleaned header copies in our tree? For licensing reasons - yes, if only of perception not reality. If Google has cleaned them, it makes me happier. ATB, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [GSOC-UDPATE](17.08) Impress Remote
On 08/22/2012 08:49 AM, Muthu Subramanian K wrote: On 08/20/2012 05:00 PM, Michael Meeks wrote: One issue is powering up bluetooth on Android: documentation insists that you ask the user to switch on bluetooth: one option is to add an item Search for Bluetooth devices on the selection screen which does this, or alternatively to just ask the user every single time the app is started. I -imagine- that UX wise, enabling bluetooth during a pairing flow, and disabling it again if we don't connect is perhaps the best plan from a UX battery perspective ? Yes, as far as I know, you have to ask the user to turn on Bluetooth. You could create an Intent to show the Settings page for the user to do it. On the battery side: powering the radio down or going to lower power modes is handled by the lower stack, at least for the first round we shouldn't be too concerned about this, I guess (?) It isn't strictly necessary to ask the user -- there is a BluetoothAdapter.enable() method which controls the power, without asking the user, although the documentation says that shouldn't be used without asking. It would however be possible to ask the user every time the app is started Switch on Bluetooth to find Bluetooth devices? along with a Don't ask again option to make that permanent? (And then the app can remember whether bluetooth was on beforehand, and switch it off again if necessary.) (In my experience having bluetooth on doesn't cause considerable drain unless discoverable, so it seems like low power modes are automatic.) Cheers, Andrzej ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [GSOC-UDPATE](17.08) Impress Remote
If it's ok with everyone I'm going to include cleaned bluetooth headers, from android, in the source tree to avoid the need for installing a library which isn't actually linked or used. (Headers viewable http://gitorious.org/0xdroid/system_bluetooth/trees/59ca0be6dc8ef3f30f8f863d8fb805a55bf12fe5/bluez-clean-headers/bluetooth ). Sorry for replying late, but I am a bit unsure about this. Is it really a good idea to have these cleaned header copies in our tree? I mean, one more package to depend on (bluez-devel in the SUSE case, libbluetooth-dev in Debian), what's the big deal with that? If some of the distro versions we want to support don't have any such, we just need to make the Bluetooth remote server code optional with a configure switch and some ifdefs, right? --tml ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [GSOC-UDPATE](17.08) Impress Remote
Hi Andrzej, On Fri, 2012-08-17 at 21:33 +0200, Andrzej J. R. Hunt wrote: I finally managed to get dbus control of bluetooth working today, and started working on the actual communication Nice :-) One issue is powering up bluetooth on Android: documentation insists that you ask the user to switch on bluetooth: one option is to add an item Search for Bluetooth devices on the selection screen which does this, or alternatively to just ask the user every single time the app is started. I -imagine- that UX wise, enabling bluetooth during a pairing flow, and disabling it again if we don't connect is perhaps the best plan from a UX battery perspective ? On a related note, I assume it's worth adding an Add computer manually item to the same screen for cases where server discovery doesn't work (e.g. if the router doesn't pass on multicast packets). Yep - I guess so; type your IP address here or whatever ? If it's ok with everyone I'm going to include cleaned bluetooth headers, from android, in the source tree to avoid the need for installing a library which isn't actually linked or used. (Headers viewable Makes perfect sense; it'd be good to ensure that these are in a top-level directory, with a link to where they came from (as below). Assuming tests on my home network go fine I should publish a first apk this coming Monday, when I'll do the last bits of transitioning to ABS. Perhaps the best thing to do is to get a 'make' in android/ to compile the .apk inside our build tree, and work with Tor to get them building up-loading automatically from the new Android tinderboxen :-) Nice work though, Michael. -- michael.me...@suse.com , Pseudo Engineer, itinerant idiot ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: [GSOC-UDPATE](17.08) Impress Remote
Hi Michael, On 08/20/2012 01:30 PM, Michael Meeks wrote: One issue is powering up bluetooth on Android: documentation insists that you ask the user to switch on bluetooth: one option is to add an item Search for Bluetooth devices on the selection screen which does this, or alternatively to just ask the user every single time the app is started. I -imagine- that UX wise, enabling bluetooth during a pairing flow, and disabling it again if we don't connect is perhaps the best plan from a UX battery perspective ? Yes, I think that's probably best, and easiest to implement. On a related note, I assume it's worth adding an Add computer manually item to the same screen for cases where server discovery doesn't work (e.g. if the router doesn't pass on multicast packets). Yep - I guess so; type your IP address here or whatever ? Ok. I'll probably also implement some form of emulator detection (i.e. if 10.0.2.2 exists then add an Entry Emulator host to the list of servers) to simplify testing since server discovery doesn't work (and neither does bluetooth) when on the emulator. If it's ok with everyone I'm going to include cleaned bluetooth headers, from android, in the source tree to avoid the need for installing a library which isn't actually linked or used. (Headers viewable Makes perfect sense; it'd be good to ensure that these are in a top-level directory, with a link to where they came from (as below). Would it be appropriate to place these in external, or do you mean a top level bluetooth folder? (I'd already put them into the remote folder, where I use them, but I can change that fairly simply.) Assuming tests on my home network go fine I should publish a first apk this coming Monday, when I'll do the last bits of transitioning to ABS. Perhaps the best thing to do is to get a 'make' in android/ to compile the .apk inside our build tree, and work with Tor to get them building up-loading automatically from the new Android tinderboxen :-) I'll try and add that. (For now I can upload them manually though.) Nice work though, Michael. Thanks, Andrzej ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
