On 20.08.2015 23:20, Steve Langasek wrote:
Hi all,
I've been taking care of a backlog of packages that have been removed in
Debian but not removed in Ubuntu. One of the packages that's shown up on
the list as having reverse-dependencies in Ubuntu is obexd, whose packages
(obexd-client and obexd
On 23.08.2015 04:44, XiaoGuo Liu wrote:
Hi,
I am now trying to help a developer to get Bluetooth API. On our phone
platform, do we have any open API for the purpose? I cannot find any such
info at: http://developer.ubuntu.com/api/apps/qml/sdk-15.04/.
From what I know we currently don't expose
On 27.08.2015 13:17, Thomas A. Moulton wrote:
From watching the various updates my Tablet (flo) has received, aren't
the OTA updates deltas? If so, then would it be expected to have >500MB
of changes between updates often? In the most recent update I think I
saw about 148MB downloaded.
Think a
On 27.08.2015 13:56, Sergio Schvezov wrote:
On Thu, Aug 27, 2015 at 7:14 AM, John McAleely
wrote:
As we begin to prepare for new features associated with converged devices,
it seems likely that some image configurations will be *much* larger than
our current phone images on system-image.ubuntu
On 29.08.2015 16:26, Ricardo Salveti de Araujo wrote:
On Aug 28, 2015 20:20, "Steve Langasek"
wrote:
On Fri, Aug 28, 2015 at 08:06:24PM -0300, Ricardo Salveti de Araujo wrote:
On Aug 21, 2015 14:17, "Tony Espy" wrote:
On 08/20/2015 05:20 PM, Steve Langasek wrote:
I've been taking care
On 07.09.2015 17:21, Oliver Grawert wrote:
Am Montag, den 07.09.2015, 14:57 +0100 schrieb John McAleely:
Are these the two options we have? What pros and cons are there for
each?
do you actually know (did anyone test) if hybris would get along with
running in 32bit on the ubuntu side while t
On 07.09.2015 15:57, John McAleely wrote:
Folks,
More and more Android devices are shipping in 64bit form. As such, I think
Ubuntu needs a plan to use the drivers from such a system sooner rather
than later.
We have a choice, I think. We can either attempt to build a 64bit Ubuntu
image for phon
On 08.09.2015 09:14, Vicamo Yang wrote:
On Tue, Sep 8, 2015 at 12:54 PM, Simon Fels
wrote:
On 07.09.2015 17:21, Oliver Grawert wrote:
Am Montag, den 07.09.2015, 14:57 +0100 schrieb John McAleely:
Are these the two options we have? What pros and cons are there for
each?
do you actually
On 08.09.2015 09:14, Vicamo Yang wrote:
On Tue, Sep 8, 2015 at 12:54 PM, Simon Fels
wrote:
On 07.09.2015 17:21, Oliver Grawert wrote:
Am Montag, den 07.09.2015, 14:57 +0100 schrieb John McAleely:
Are these the two options we have? What pros and cons are there for
each?
do you actually
Hey everyone,
as some might know we're currently in the transition period to BlueZ 5.x
on Ubuntu Touch. Until now we're still using version 4.101 which dates
back to 2012. BlueZ 5 is a rework of the former version with a changed
DBus API and a lot of improvements/refactorings across the whole
On 14.09.2015 13:12, John McAleely wrote:
I like the sound of multiarch for two reasons:
- It trivially guarantees compatibility for all the apps in the store today
- It allows us to make use of 64 bit whenever it is useful
If we forgo the second advantage, we could just boot the kernel & a
On 14.09.2015 14:26, Alfonso Sanchez-Beato wrote:
On Mon, Sep 14, 2015 at 1:55 PM, Simon Fels
wrote:
On 14.09.2015 13:12, John McAleely wrote:
I like the sound of multiarch for two reasons:
- It trivially guarantees compatibility for all the apps in the store
today
- It allows us to
On 30.08.2015 20:21, Gran PC wrote:
media-hub wouldn't work for Spotify because that'd require them to put a
non-encrypted version of the music somewhere on the disk. There's a
third-party Spotify app on the store right now called CuteSpotify which
demonstrates the issue nicely.
That isn't true
On 23.09.2015 17:44, Gran PC wrote:
But third-party apps can't actually extend media-hub, right? As I
understand it, this is something that would need to be distributed with the
OS.
No. It would be just another executable your click package would ship
and would be exposed to media-hub at runti
On 23.09.2015 18:42, Gran PC wrote:
That's a pretty cool approach! Has anyone started working on it?
As far as I know no one did. I was interested in doing that but didn't
had any spare free time yet.
regards,
Simon
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-
On 24.09.2015 07:46, Steve Langasek wrote:
On Thu, Sep 24, 2015 at 08:12:22AM +1000, Michi Henning wrote:
I'm seeing this on Vivid plus overlay on my desktop as well as on my Nexus
4 when using citrain device-upgrade.
Are you sure you're seeing the same issue on a Nexus 4? The ps output shows
On 24.09.2015 20:34, Robert Park wrote:
On Wed, Sep 23, 2015 at 11:56 PM, Simon Fels wrote:
The reason for this isn't clear yet however I modified the citrain utility
to do an device upgrade without service restart and then directly reboot the
device recently. See
https://code.launchpa
On 01.10.2015 14:22, Pat McGowan wrote:
On Thu, Oct 1, 2015 at 4:36 AM, sturmflut wrote:
Good morning dear list,
I agree that SIM Tookit support is crucial for many countries. As far as
I know, ofono has a D-Bus API for it and the functionality is very
simple, so we might "just" have to build
On 02.10.2015 09:36, Alberto Mardegan wrote:
On 02.10.2015 10:29, Yann wrote:
If I can add my insight ... I think some applications (not all) should
be able to run on background like Facebook for example ... everybody has
Facebook Messenger on other platforms, and they write messages only
throug
On 02.10.2015 12:54, Niklas Wenzel wrote:
Hi!
Am Freitag, 2. Oktober 2015 schrieb Bry Wilson :
Hi,
Apologies for posting to the list for this but had noticed two bugs I
wanted to report was unsure where to on Launchpad - so some pointers would
be wonderful!
launchpad.net/webbrowser-app would
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
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
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
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
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
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
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
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
On 10.10.2015 13:02, Simos Xenitellis wrote:
On Sat, Oct 10, 2015 at 1:22 PM, Ionut Negru wrote:
Hello,
I wonder if there is anyone that has tried to use the phone with external
keyboard, mouse and display all together. Is mhl support working yet? What
accessories did you use?
I run ubuntu o
On 23.10.2015 12:15, Andrew Hayzen wrote:
Hey,
Currently the next and previous buttons do not function as we have not
landed this support yet.
We are currently working [0] with upstream (media-hub and indicator-sound)
to complete the remaining issues, which will then allow for the platform to
i
Hey everyone,
it finally happened: We are switching to BlueZ 5.x on our Touch images
on all supported devices. To make this happen a huge amount of work
through the last five months from different people was needed. Thank you
all for the great work and support to make this happen!
QA approve
On 21.11.2015 01:47, Robert Park wrote:
On Nov 20, 2015 8:29 AM, "Simon Fels" wrote:
Hey everyone,
it finally happened: We are switching to BlueZ 5.x on our Touch images on
all supported devices. To make this happen a huge amount of work through
the last five months from differ
Can you check if the following file is still present on your Nexus 4?
phablet@ubuntu-phablet:~$ sudo ls -alh /persist/wifi/.macaddr
-rw-r--r--. 1 root root 13 Jan 3 1970 /persist/wifi/.macaddr
regards,
Simon
On 23.11.2015 14:29, Heroldich Robin wrote:
Hey,
As I see this is not the same bu
On 24.11.2015 15:25, Dmytryi Fedorov wrote:
It is car speakers. Everything is fine with them, Samsung Galaxy Nexus
on Android works fine. But on my Meizu MX4 (r185) music stutters. But
not always, ~90% of times. I must connect\reconnect about 10 times to
play music normally
It would be awesome
On 25.11.2015 12:19, Dmytryi Fedorov wrote:
I will do it tomorrow when the car (Chevrolet Sonic (or Aveo T300)) will
be available.
On what package I need to fill this bug?
Against https://bugs.launchpad.net/ubuntu/+source/bluez
But please check first if there isn't a bug already which describ
Hey everyone,
as we introduced a backported bluetooth stack on the kernel side for all
our devices and have to do that for all other ports too to make sure
we're running the same stack across all of our devices I documented the
basic steps to do at [1]. I've included links to two reference ker
On 26.12.2015 22:28, Gareth France wrote:
On 26/12/15 00:17, Michael Zanetti wrote:
And will it work with my generic
>watch?
No.
>If not is there anything that can be done to encourage two way
>communication between the watch and phone?
I would require writing something like Rockwork, suited
On 04.01.2016 20:10, Daniel Wood wrote:
I've been having issues with bluetooth on a nexus 7 running RC proposed.
I have filed a bug here:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1530807
Can anyone advice if bluetooth connectivity is logged anywhere or if
there is any furth
On 05.01.2016 19:43, Randall Ross wrote:
On 01/04/2016 09:58 PM, Simon Fels wrote:
On 04.01.2016 20:10, Daniel Wood wrote:
I've been having issues with bluetooth on a nexus 7 running RC proposed.
I have filed a bug here:
https://bugs.launchpad.net/canonical-devices-system-image
On 28.02.2016 19:32, Marco Graziotti wrote:
> Hi Robin,
>
> I'm interested in "aethercast" because my MX4 don't support wired
> connection.
> Can you indicate the correct procedure to install and try aethercast?
We already have code in place which does proper display streaming but
this is current
On 29.02.2016 09:57, Heroldich Robin wrote:
> Thanks everybody for your answers.
>
> Maybe a stupid question. But why don't you rebase all phones to Android 5.x?
> Is it possible?
Possible is everything but time and business wise that doesn't make
sense and would just open the gate for a lot mor
> Does this mean that DisplayCast will be available soon for krillin and
> vegeta?.If this specific API works for Android devices based on 5.x,
> krillin and vegeta are right now on Android 5.0, could be this API used
> for them too?.
Its just API functionality we use to make things easier and get
On 14.03.2016 12:36, Krzysztof Tataradziński wrote:
> In /var/lib/bluetooth I can see one folder with some MAC address (maybe)
> 38:BC:1A:..., but it's empty (but I cannot go inside; clicking on it (in file
> manager) does do nothing).
You need to be root to do that. For other users than root th
On 13.03.2016 14:29, Krzysztof Tataradziński wrote:
> Hello,
> I've got two bluetooth devices I'm using with my phone:
> (1) headphones with mic (I think that is called headset in english)
> (2) Bluetooth transmitter with mic also.
>
> (1) is recognized in Ubuntu System Settings, bluetooth part as
On 04.04.2016 11:48, Filip Dorosz wrote:
> How do you get around dependcies?
>
> owncloud-client-cmd depens on some libs that are not installed.
Either by building a static binary which includes all necessary
libraries or a wrapper script which adjusts LD_LIBRARY_PATH to include a
path where you
On 12.04.2016 14:31, Marco Graziotti wrote:
> So, you think it's possible to developing the Miracast support for Meizu MX4?
It is possible for sure. The actual part we're talking about here is the
hardware encoding we're reusing from Android. Android 5.x introduced a
small layer around the actual
On 19.04.2016 09:37, Wayne Ward wrote:
> Im just setting up a new draytek VigorAP AP900
> The wireless access point is running in 5G and available from all
> devices apart from the ubuntu touch phone
> Does the device not support that connection ?
> If not i could add a 2.4G access point
Which U
On 12.04.2016 14:52, Simon Fels wrote:
> On 12.04.2016 14:31, Marco Graziotti wrote:
>> So, you think it's possible to developing the Miracast support for Meizu MX4?
>
> It is possible for sure. The actual part we're talking about here is the
> hardware encodin
Hey everyone,
we've just landed a big update for NetworkManager, our central network
managing component, and all bits to enable Wireless Display support in
Ubuntu Touch. All of these changes will be available in an image build
over the weekend and published to rc-proposed.
As we had to get everyt
On 30.04.2016 23:14, Francisco Mulas Caracuel wrote:
> Im running rc-proposed channel and not have this feature.
The only supported device for Wireless Display support so far is the
Meizu MX Pro 5. Even if the Ubuntu rootfs on each phone is identical we
disable the option for Wireless Display in u
On 01.06.2016 18:50, Krzysztof Tataradziński wrote:
> Hello,
>
> I just want to sum up what we know about wireless display support. For now,
> theoretically we've two options to get it working on Meizu MX4:
> (1) Change Android BSP from 4.x to 5.x.
> (2) Backport MediaCodecSource class (and maybe
On 13.08.2016 22:50, Kristijan wrote:
> Hi,
>
> Has anybody tested an Ubuntu Phone that has working Aethercast
> capability with Microsoft Wireless Display Adapter V2? I only know that
> devs are developing with MWDA V1.
> I'm looking to buy one of those so I want to be sure that it works with
> A
On 14.08.2016 05:15, Radics Geza wrote:
> Hi!
> It works and the range is quite good.
Awesome!
regards,
Simon
>> Original Message
>> Subject: Re: [Ubuntu-phone] Aethercast and MWDA v2
>> Local Time: August 14, 2016 5:45 AM
>> UTC Time: August 13, 2016 9:45 PM
>> From: simon.f..
This is awesome!!! Great work!
On Wed, Aug 31, 2016 at 9:44 AM, Lukasz Zemczak <
lukasz.zemc...@canonical.com> wrote:
> Sweet!
>
> On 30 August 2016 at 21:45, Robert Park wrote:
> > Hi all,
> >
> > I've just rolled experimental git support into production Bileto. This
> > means it's now possible
16 at 11:22 AM, Konrad Zapałowicz <
konrad.zapalow...@canonical.com> wrote:
> Awesome!
>
> On Wed, Aug 31, 2016 at 11:10 AM, Simon Fels
> wrote:
>
>> This is awesome!!! Great work!
>>
>> On Wed, Aug 31, 2016 at 9:44 AM, Lukasz Zemczak <
>> lukasz.zemc
On 29.09.2016 12:34, M G wrote:
> Hi list,
>
> how MX4 users can contribute to develop aethercast?
>
> I remember that there are two way to reach this goal:
>
> 1. Changing Android BSP from 4 to 5 (with OTA-13 this process is
> completed, right?)
No. The MX4 still runs the 4.x based BSP and will n
56 matches
Mail list logo
