On 08.10.2015 16:32, Pat McGowan wrote:
What does this mean in the converged world where a phone is also a desktop?
That a phone still stays a phone. In the bluetooth world that doesn't
change anything. The device class is just a way to tell other bluetooth
devices which capabilities we have
What does this mean in the converged world where a phone is also a desktop?
On Thu, Oct 8, 2015 at 10:30 AM, Simon Fels
wrote:
> On 08.10.2015 15:08, Michael Zanetti wrote:
>
>>
>>
>> On 08.10.2015 14:57, Simon Fels wrote:
>>
>>> On 08.10.2015 14:30, Michał Sawicz wrote:
>>>
W dniu 08.10.20
On 08.10.2015 15:08, Michael Zanetti wrote:
On 08.10.2015 14:57, Simon Fels wrote:
On 08.10.2015 14:30, Michał Sawicz wrote:
W dniu 08.10.2015 o 14:00, Simon Fels pisze:
A tablet stays a tablet. Having a modem included doesn't make it a
phone. The Bluetooth device class is meant to stay stat
W dniu 08.10.2015 o 15:49, Simon Fels pisze:
> On 08.10.2015 15:03, Michał Sawicz wrote:
>> W dniu 08.10.2015 o 14:57, Simon Fels pisze:
>>> That would a use case, yes, but still really a workaround for a corner
>>> case.
>>>
>>> However that wouldn't work with our implementation playing the role o
On 08.10.2015 15:03, Michał Sawicz wrote:
W dniu 08.10.2015 o 14:57, Simon Fels pisze:
That would a use case, yes, but still really a workaround for a corner
case.
However that wouldn't work with our implementation playing the role of
the audio gateway strictly requires a modem with voice call
On 08.10.2015 14:57, Simon Fels wrote:
> On 08.10.2015 14:30, Michał Sawicz wrote:
>> W dniu 08.10.2015 o 14:00, Simon Fels pisze:
>>> A tablet stays a tablet. Having a modem included doesn't make it a
>>> phone. The Bluetooth device class is meant to stay static for one device
>>> forever. No dy
W dniu 08.10.2015 o 14:57, Simon Fels pisze:
> That would a use case, yes, but still really a workaround for a corner
> case.
>
> However that wouldn't work with our implementation playing the role of
> the audio gateway strictly requires a modem with voice call
> capabilities.. no way to inject y
On 08.10.2015 14:30, Michał Sawicz wrote:
W dniu 08.10.2015 o 14:00, Simon Fels pisze:
A tablet stays a tablet. Having a modem included doesn't make it a
phone. The Bluetooth device class is meant to stay static for one device
forever. No dynamic changes. It is your first point to find out what
W dniu 08.10.2015 o 14:00, Simon Fels pisze:
> A tablet stays a tablet. Having a modem included doesn't make it a
> phone. The Bluetooth device class is meant to stay static for one device
> forever. No dynamic changes. It is your first point to find out what
> kind of Bluetooth device you've found
hi,
Am Donnerstag, den 08.10.2015, 14:04 +0200 schrieb Simon Fels:
> On 08.10.2015 13:49, Oliver Grawert wrote:
> > hi,
> >
> > Am Donnerstag, den 08.10.2015, 12:48 +0200 schrieb Simon Fels:
> >
> >> So what about just extending this one which comes either from the device
> >> tarball (krillin, ar
On 08.10.2015 13:49, Oliver Grawert wrote:
hi,
Am Donnerstag, den 08.10.2015, 12:48 +0200 schrieb Simon Fels:
So what about just extending this one which comes either from the device
tarball (krillin, arale) or from the ubuntu-touch-session package (flo,
mako)?
if anyone works on this, it wo
On 08.10.2015 13:34, Michał Sawicz wrote:
W dniu 08.10.2015 o 12:48, Simon Fels pisze:
On 08.10.2015 12:16, Michał Sawicz wrote:
W dniu 08.10.2015 o 11:54, Michael Zanetti pisze:
Not sure if the Android layer is really the place to go. What happens
when we run on an x86 based tablet which does
hi,
Am Donnerstag, den 08.10.2015, 13:34 +0200 schrieb Michał Sawicz:
> is a 10" tablet
> with GSM a phone or a tablet?).
that must be a phoblet :)
ciao
oli
signature.asc
Description: This is a digitally signed message part
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to
hi,
Am Donnerstag, den 08.10.2015, 12:48 +0200 schrieb Simon Fels:
> So what about just extending this one which comes either from the device
> tarball (krillin, arale) or from the ubuntu-touch-session package (flo,
> mako)?
>
if anyone works on this, it would be nice to unify this (i.e. make
W dniu 08.10.2015 o 12:48, Simon Fels pisze:
> On 08.10.2015 12:16, Michał Sawicz wrote:
>> W dniu 08.10.2015 o 11:54, Michael Zanetti pisze:
>>> Not sure if the Android layer is really the place to go. What happens
>>> when we run on an x86 based tablet which doesn't have the Android bits?
>>> Wil
On 08.10.2015 12:16, Michał Sawicz wrote:
W dniu 08.10.2015 o 11:54, Michael Zanetti pisze:
Not sure if the Android layer is really the place to go. What happens
when we run on an x86 based tablet which doesn't have the Android bits?
Will that always have the DMI interface instead?
x86 based t
W dniu 08.10.2015 o 12:37, Oliver Grawert pisze:
> note that the android layer is equivalent to "device tarball", the
> question is: will installs using this feature exist in a non snappy/non
> touch context, note that in the snappy world *all* installs have a
> device tarball (or soon device/kerne
hi,
Am Donnerstag, den 08.10.2015, 11:54 +0200 schrieb Michael Zanetti:
> Not sure if the Android layer is really the place to go. What happens
> when we run on an x86 based tablet which doesn't have the Android bits?
> Will that always have the DMI interface instead?
note that the android layer
W dniu 08.10.2015 o 11:54, Michael Zanetti pisze:
> Not sure if the Android layer is really the place to go. What happens
> when we run on an x86 based tablet which doesn't have the Android bits?
> Will that always have the DMI interface instead?
I agree, we need to plan for not having Android aro
Hi
On 05.10.2015 18:31, Simon Fels wrote:
> Hey everyone,
>
> while currently working on heading towards BlueZ 5.x in Ubuntu Touch I
> came to the point where we need to expose what type of device we are
> running on. When you start discovering other Bluetooth devices you
> always get the so call
Hey everyone,
while currently working on heading towards BlueZ 5.x in Ubuntu Touch I
came to the point where we need to expose what type of device we are
running on. When you start discovering other Bluetooth devices you
always get the so call "Class of Device" back which describes what kind
21 matches
Mail list logo
