Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

I have progress to report!  Both ADB and MTP work somewhat better on my 
iMac at work (21.5-inch, Late 2013.  My Macbook is Mid-2010. Both 
running El Capitan.)


The results are quite confusing.  I can consistently use Android File 
Transfer, it pops up automatically every time I plug in the phone.  I 
can transfer photos no problem.


adb devices was working for a while, and I could even use adb shell.  
Then it dropped out.  Replugging allowed me to see adb devices again for 
a while, but now replugging is doing nothing for me.  I would guess that 
rebooting the computer would get it working again but I don't have time 
to do that.  adb version is 1.0.32.  I have developer mode enabled 
throughout this.


None of this is qualitatively different to what I get on my Macbook or 
the Raspberry Pi.  It's just that the iMac drops out rather less often.


I can't really use the computer at work to reflash my phone, and anyway 
if the connection is going to drop out I'd be extremely nervous about 
accidentally bricking the device.  I will be getting a new Macbook Pro 
soon so I can test with that, perhaps that will be reliable enough.  But 
it's all pretty worrying.


On 2016-04-11 23:59, Ondrej Kubik wrote:
for MTP on Mac you should be able to use Android tools from Android 
SDK. It used to bundle mtp client.


// Ondra

On Mon, Apr 11, 2016 at 2:00 PM, > wrote:


On 2016-04-11 17:37 , Ondrej Kubik wrote:
> Most the problems with adb are caused by the flaky usb on MX4, but
> could be others.
>
> 1) can you see MTP interface and transfer files to device?
>  -> no) your USB is flaky, test different port, different USB
cable
>
>  -> yes)  what adb client (host binary) are you using?
>   -> one from Google, aka Android studio): make sure you update
> ~/.android/adb_usb.ini it should contain 0x2a45, without that file,
> adb client will ignore any connected device not blessed by Google.
>   -> one from Ubuntu ppa, you should see device or at least as
> "unauthorised device" otherwise make sure you have developer
mode enabled.
>
> Using old adb client with new adb daemon should still show you as
> minimum unauthorised device.
>
>



-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-11 23:59 , Ondrej Kubik wrote:
> for MTP on Mac you should be able to use Android tools from Android
> SDK. It used to bundle mtp client.
>
I have Android Studio 1.2 installed but I can't find an MTP client.  Is
the binary just called "mtp"?  Can you guess where it's likely to be on
my filesystem?


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-12 24:27 , Dave Morley wrote:
> iirc you will just require https://www.android.com/filetransfer/ for
> macs to transfer via mtp.
>
I just tried that.  It just says "No Android device found".  But then I
tried rebooting the Mac, and then when I plugged in the MX4 it briefly
looked like it was doing something and showed a window.  Then it said it
had a problem communicating with the phone or something and just quit. 
I didn't think to take notes or screenshots.  But it looks very similar
to what I see on the Raspberry Pi: works briefly after rebooting the
host, but not enough to get anything done.

I believe this proves that my computers' USB ports and cables are fine,
and so is the device's USB hardware.  The weak link really seems to be
the design of the MX4 itself.

My ZTE never shows up in Android File Transfer at all, but I can use it
perfectly fine in Android Studio, view logs, install and run apps.  It's
running Android 4.0.4, maybe that's before MTP was introduced?


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[Dave Morley]

On Mon, 11 Apr 2016 16:59:24 +0100
Ondrej Kubik  wrote:

> for MTP on Mac you should be able to use Android tools from Android
> SDK. It used to bundle mtp client.
> 
> // Ondra
> 
> On Mon, Apr 11, 2016 at 2:00 PM,  wrote:
> 
> > On 2016-04-11 17:37 , Ondrej Kubik wrote:  
> > > Most the problems with adb are caused by the flaky usb on MX4, but
> > > could be others.
> > >
> > > 1) can you see MTP interface and transfer files to device?  
> > >  -> no) your USB is flaky, test different port, different USB
> > > cable 
> > >  -> yes)  what adb client (host binary) are you using?
> > >   -> one from Google, aka Android studio): make sure you
> > > update ~/.android/adb_usb.ini it should contain 0x2a45, without
> > > that file, adb client will ignore any connected device not
> > > blessed by Google. -> one from Ubuntu ppa, you should see device
> > > or at least as "unauthorised device" otherwise make sure you have
> > > developer mode  
> > enabled.  
> > >
> > > Using old adb client with new adb daemon should still show you as
> > > minimum unauthorised device.
> > >
> > >  
> > I have very limited options for testing MTP.  Macintoshes do not
> > support MTP.  All I have is a headless Raspberry Pi running
> > Raspbian.
> >
> > So I'm trying "mtp-tools".  mtp-detect gives very intermittent
> > results. Mostly it just says "No raw devices found".  Very rarely
> > it spits out a vast list of stuff.  Other times it says
> > "PTP_ERROR_IO: failed to open session, trying again after resetting
> > USB interface".  Rebooting the Raspberry Pi improves my odds of
> > getting data, but it quickly peters out.  Intermittently my phone
> > asks me if I want to allow the Raspberry Pi to talk to it.  I've
> > tried this with two different ports and two different cables.  And
> > the phones are flat on the table, so it's not like the cable's
> > wiggling or anything.
> >
> > If it was a bad USB *connector* I could understand.  But I'm getting
> > these intermittent results with two different phones, the other
> > being a bog-standard landfill Android.  Neither has ever had any
> > problem charging over USB and both of them show up perfectly fine
> > in lsusb, proving that data is connected too.  So the problem must
> > be either in silicon or in software.  Which surely means someone
> > must have really screwed up the design of something.  I just don't
> > know if it's Meizu, Ubuntu or Google who's to blame.
> >
> > Your other points:
> >
> > * I have adb 1.0.32 on the Macbook and 1.0.31 on the Raspberry Pi.
> > Please if you suggest I might have the wrong version of adb, also
> > tell me which version is correct.  If you are successfully using
> > adb to talk to an MX4, please tell me which version you are using.
> >
> > * I have already set up ~/.android/adb_usb.ini with 0x2a45 on both
> > the Macintosh and the Raspberry Pi.  I have actually successfully
> > used adb on the Macintosh to talk to the MX4 before.  But that was
> > many months ago and I neglected to note which version of everything
> > I was using.
> >
> > * I always have developer mode enabled.
> >
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to : ubuntu-phone@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help   : https://help.launchpad.net/ListHelp
> >  

iirc you will just require https://www.android.com/filetransfer/ for
macs to transfer via mtp.

-- 
You Make It, I'll Break It!

I Love My Job :)

http://www.canonical.com
http://www.ubuntu.com


pgpO_xSFzrhIi.pgp
Description: OpenPGP digital signature
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[Ondrej Kubik]

for MTP on Mac you should be able to use Android tools from Android SDK. It
used to bundle mtp client.

// Ondra

On Mon, Apr 11, 2016 at 2:00 PM,  wrote:

> On 2016-04-11 17:37 , Ondrej Kubik wrote:
> > Most the problems with adb are caused by the flaky usb on MX4, but
> > could be others.
> >
> > 1) can you see MTP interface and transfer files to device?
> >  -> no) your USB is flaky, test different port, different USB cable
> >
> >  -> yes)  what adb client (host binary) are you using?
> >   -> one from Google, aka Android studio): make sure you update
> > ~/.android/adb_usb.ini it should contain 0x2a45, without that file,
> > adb client will ignore any connected device not blessed by Google.
> >   -> one from Ubuntu ppa, you should see device or at least as
> > "unauthorised device" otherwise make sure you have developer mode
> enabled.
> >
> > Using old adb client with new adb daemon should still show you as
> > minimum unauthorised device.
> >
> >
> I have very limited options for testing MTP.  Macintoshes do not support
> MTP.  All I have is a headless Raspberry Pi running Raspbian.
>
> So I'm trying "mtp-tools".  mtp-detect gives very intermittent results.
> Mostly it just says "No raw devices found".  Very rarely it spits out a
> vast list of stuff.  Other times it says "PTP_ERROR_IO: failed to open
> session, trying again after resetting USB interface".  Rebooting the
> Raspberry Pi improves my odds of getting data, but it quickly peters
> out.  Intermittently my phone asks me if I want to allow the Raspberry
> Pi to talk to it.  I've tried this with two different ports and two
> different cables.  And the phones are flat on the table, so it's not
> like the cable's wiggling or anything.
>
> If it was a bad USB *connector* I could understand.  But I'm getting
> these intermittent results with two different phones, the other being a
> bog-standard landfill Android.  Neither has ever had any problem
> charging over USB and both of them show up perfectly fine in lsusb,
> proving that data is connected too.  So the problem must be either in
> silicon or in software.  Which surely means someone must have really
> screwed up the design of something.  I just don't know if it's Meizu,
> Ubuntu or Google who's to blame.
>
> Your other points:
>
> * I have adb 1.0.32 on the Macbook and 1.0.31 on the Raspberry Pi.
> Please if you suggest I might have the wrong version of adb, also tell
> me which version is correct.  If you are successfully using adb to talk
> to an MX4, please tell me which version you are using.
>
> * I have already set up ~/.android/adb_usb.ini with 0x2a45 on both the
> Macintosh and the Raspberry Pi.  I have actually successfully used adb
> on the Macintosh to talk to the MX4 before.  But that was many months
> ago and I neglected to note which version of everything I was using.
>
> * I always have developer mode enabled.
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-11 17:37 , Ondrej Kubik wrote:
> Most the problems with adb are caused by the flaky usb on MX4, but
> could be others.
>
> 1) can you see MTP interface and transfer files to device?
>  -> no) your USB is flaky, test different port, different USB cable
>
>  -> yes)  what adb client (host binary) are you using?
>   -> one from Google, aka Android studio): make sure you update
> ~/.android/adb_usb.ini it should contain 0x2a45, without that file,
> adb client will ignore any connected device not blessed by Google.
>   -> one from Ubuntu ppa, you should see device or at least as
> "unauthorised device" otherwise make sure you have developer mode enabled.
>
> Using old adb client with new adb daemon should still show you as
> minimum unauthorised device.
>
>
I have very limited options for testing MTP.  Macintoshes do not support
MTP.  All I have is a headless Raspberry Pi running Raspbian.

So I'm trying "mtp-tools".  mtp-detect gives very intermittent results. 
Mostly it just says "No raw devices found".  Very rarely it spits out a
vast list of stuff.  Other times it says "PTP_ERROR_IO: failed to open
session, trying again after resetting USB interface".  Rebooting the
Raspberry Pi improves my odds of getting data, but it quickly peters
out.  Intermittently my phone asks me if I want to allow the Raspberry
Pi to talk to it.  I've tried this with two different ports and two
different cables.  And the phones are flat on the table, so it's not
like the cable's wiggling or anything.

If it was a bad USB *connector* I could understand.  But I'm getting
these intermittent results with two different phones, the other being a
bog-standard landfill Android.  Neither has ever had any problem
charging over USB and both of them show up perfectly fine in lsusb,
proving that data is connected too.  So the problem must be either in
silicon or in software.  Which surely means someone must have really
screwed up the design of something.  I just don't know if it's Meizu,
Ubuntu or Google who's to blame.

Your other points:

* I have adb 1.0.32 on the Macbook and 1.0.31 on the Raspberry Pi. 
Please if you suggest I might have the wrong version of adb, also tell
me which version is correct.  If you are successfully using adb to talk
to an MX4, please tell me which version you are using.

* I have already set up ~/.android/adb_usb.ini with 0x2a45 on both the
Macintosh and the Raspberry Pi.  I have actually successfully used adb
on the Macintosh to talk to the MX4 before.  But that was many months
ago and I neglected to note which version of everything I was using.

* I always have developer mode enabled.


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[Ondrej Kubik]

Most the problems with adb are caused by the flaky usb on MX4, but could be
others.

1) can you see MTP interface and transfer files to device?
 -> no) your USB is flaky, test different port, different USB cable

 -> yes)  what adb client (host binary) are you using?
  -> one from Google, aka Android studio): make sure you update
~/.android/adb_usb.ini it should contain 0x2a45, without that file, adb
client will ignore any connected device not blessed by Google.
  -> one from Ubuntu ppa, you should see device or at least as
"unauthorised device" otherwise make sure you have developer mode enabled.

Using old adb client with new adb daemon should still show you as minimum
unauthorised device.

cheers
// Ondra




On Sun, Apr 10, 2016 at 2:06 AM,  wrote:

> On 2016-04-10 04:39 , Sergio Schvezov wrote:
> >
> > Using adb is the most depressing thing from the mx4. I only started to
> > noticed after I got a new laptop; on usb2 ports it is not as noticeable.
> >
> Is this a software problem or a hardware problem?  I don't even know how
> it's possible for a phone manufacturer to get their USB port
> implementation wrong, it's all in the SoC surely?
>
> If it's a firmware problem I can understand.  I'm learning a lot about
> the quality of Android phone manufacturers' design decisions, and I'm
> not learning anything that makes me happy.
>
> If it's a system software problem... any chance of getting it fixed?
>
> BTW my Macbook is a 2010 model and doesn't hold with any of this
> new-fangled USB 3 nonsense.  My Raspberry Pi is a Raspberry Pi and is
> definitely USB 2 only.
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-10 04:39 , Sergio Schvezov wrote:
>
> Using adb is the most depressing thing from the mx4. I only started to
> noticed after I got a new laptop; on usb2 ports it is not as noticeable.
>
Is this a software problem or a hardware problem?  I don't even know how
it's possible for a phone manufacturer to get their USB port
implementation wrong, it's all in the SoC surely?

If it's a firmware problem I can understand.  I'm learning a lot about
the quality of Android phone manufacturers' design decisions, and I'm
not learning anything that makes me happy.

If it's a system software problem... any chance of getting it fixed?

BTW my Macbook is a 2010 model and doesn't hold with any of this
new-fangled USB 3 nonsense.  My Raspberry Pi is a Raspberry Pi and is
definitely USB 2 only.


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-10 04:32 , Sergio Schvezov wrote:
>
> Certain versions of adb servers (generally on devices) require
> specific versions of adb clients (generally on hosts). This means that
> you might need to check the adb version you are using on the host. One
> feature that comes to mind is the addition of host keys used for
> authentication that the client needs to support for the server to
> respond back.

OK then, here's the big question: Which specific version of adb do I
need in order to talk to my MX4?  I have 1.0.32 on the Macbook and
1.0.31 on the Raspberry Pi.
>
> Another thing that needs to be known to the clients are the device
> id's that adb can talk to; the client will only try and talk to the
> devices it knows about, you can manually add these ids fwiw
>
>
How do I add device IDs?  I already added the vendor ID to adb_usb.ini.

mat@pi:~$ cat .android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2a45
mat@pi:~$ lsusb
Bus 001 Device 010: ID 2a45:0c02 
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

(And what is "android update adb"?  Doesn't work on either machine.)


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[ubuntu . mexon]

On 2016-04-10 04:14 , DawnDIY wrote:
> I have the same problem about connect MX4 using adb via usb port. And
> I tried so many way to connect my MX4 using adb like change adb with
> different version, change usb cable and change OS. I found that MX4's
> usb port is very unstable to connect some computer. And then I found
> this answer http://askubuntu.com/a/643814 , then I tried and some
> times it's working for me, but it is just some time. Now I give up to
> connect my MX4 using adb, and using ssh instead. 
>
I was the one who asked that question on askubuntu!  I'd forgotten about
that.  It's not working for me now though.  I think I've upgraded
Android Studio since then, but I'm not sure.

I ended up just using ssh too.  But now I want to flash it with Flyme
and that's not possible over ssh.


-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[Sergio Schvezov]

El sábado, 9 de abril de 2016 17h'14:51 ART, DawnDIY 
 escribió:

I have the same problem about connect MX4 using adb via usb port. And I
tried so many way to connect my MX4 using adb like change adb with
different version, change usb cable and change OS. I found that MX4's usb
port is very unstable to connect some computer. And then I found this
answer http://askubuntu.com/a/643814 , then I tried and some times it's
working for me, but it is just some time. Now I give up to connect my MX4
using adb, and using ssh instead.


Using adb is the most depressing thing from the mx4. I only started to 
noticed after I got a new laptop; on usb2 ports it is not as noticeable.



--
Enviado con Dekko desde mi dispositivo Ubuntu

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[Sergio Schvezov]

El sábado, 9 de abril de 2016 10h'47:05 ART, ubuntu.me...@spamgourmet.com 
escribió:

On 2016-04-09 20:53 , Krzysztof Tataradziński - ktatar...@gmail.com wrote:

Try that one:
http://forum.xda-developers.com/meizu-mx/general/tutorial-ubuntu-touch-cyanongen-to-flyme-t3240088
I'm on Arch linux with android-tools installed and works great! ;)


Does that link add anything to help me get adb working?  If adb can't
see the phone I can't even get through the "adb reboot-bootloader" step.

Installing a whole different Linux just to get one tool working seems a
bit over-the-top.  Is there reason to believe it's a difference between
Arch Linux and Raspbian that's the problem?  A different version of
android-tools, or a different USB driver, or something?  It would be a
shame to waste effort installing Arch Linux just to find out that my USB
port is hardware-incompatible with the MX4 for some reason.

A possibly interesting fact is that on my Macbook running adb 1.0.32 I
can see (and command "adb reboot-bootloader") my ZTE Android phone,
whereas on the Raspberry Pi running adb 1.0.31 I can't see that phone
either.  But then, that's not really a *very* interesting fact, since it
doesn't help me get the MX4 working.

Can someone give me some insight into why this is a hard problem?  I
really thought the whole point of adb and USB was to provide standard
protocols across different hardware and host OSs.


Certain versions of adb servers (generally on devices) require specific 
versions of adb clients (generally on hosts). This means that you might 
need to check the adb version you are using on the host. One feature that 
comes to mind is the addition of host keys used for authentication that the 
client needs to support for the server to respond back.


Another thing that needs to be known to the clients are the device id's 
that adb can talk to; the client will only try and talk to the devices it 
knows about, you can manually add these ids fwiw



--
Enviado con Dekko desde mi dispositivo Ubuntu

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 + adb

[DawnDIY]

I have the same problem about connect MX4 using adb via usb port. And I
tried so many way to connect my MX4 using adb like change adb with
different version, change usb cable and change OS. I found that MX4's usb
port is very unstable to connect some computer. And then I found this
answer http://askubuntu.com/a/643814 , then I tried and some times it's
working for me, but it is just some time. Now I give up to connect my MX4
using adb, and using ssh instead.

2016-04-09 21:47 GMT+08:00 :

> On 2016-04-09 20:53 , Krzysztof Tataradziński - ktatar...@gmail.com wrote:
> > Try that one:
> >
> http://forum.xda-developers.com/meizu-mx/general/tutorial-ubuntu-touch-cyanongen-to-flyme-t3240088
> > I'm on Arch linux with android-tools installed and works great! ;)
> >
> Does that link add anything to help me get adb working?  If adb can't
> see the phone I can't even get through the "adb reboot-bootloader" step.
>
> Installing a whole different Linux just to get one tool working seems a
> bit over-the-top.  Is there reason to believe it's a difference between
> Arch Linux and Raspbian that's the problem?  A different version of
> android-tools, or a different USB driver, or something?  It would be a
> shame to waste effort installing Arch Linux just to find out that my USB
> port is hardware-incompatible with the MX4 for some reason.
>
> A possibly interesting fact is that on my Macbook running adb 1.0.32 I
> can see (and command "adb reboot-bootloader") my ZTE Android phone,
> whereas on the Raspberry Pi running adb 1.0.31 I can't see that phone
> either.  But then, that's not really a *very* interesting fact, since it
> doesn't help me get the MX4 working.
>
> Can someone give me some insight into why this is a hard problem?  I
> really thought the whole point of adb and USB was to provide standard
> protocols across different hardware and host OSs.
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Best,
DawnDIY
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp