[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

I did the same thing, and it works!  Thanks very much for that!  Below
is the diff in my config.  One thing I notice is the different
KnownSims.  I switched from one Chinese SIM card to a different Chinese
SIM card and also moved to Hong Kong (i.e. roamed) at the same time.  So
I guess that's a fairly obscure scenario.

--- .config/connectivity-service_2016-09-30/config.ini  2016-08-06 
14:43:34.92427 +0800
+++ .config/connectivity-service/config.ini 2016-09-30 15:02:47.44002 
+0800
@@ -1,18 +1,12 @@
 [General]
-KnownSims=89860112038102930001, 89860115628100057703
+KnownSims=89860113228100167651
 MobileDataEnabled=true
-SimForMobileData=89860112038102930001
+SimForMobileData=89860113228100167651
 
 [Sims]
-89860112038102930001\DataRoamingEnabled=false
-89860112038102930001\Imsi=
-89860112038102930001\Mcc=460
-89860112038102930001\Mnc=01
-89860112038102930001\PreferredLanguages=zh, en
-89860112038102930001\PrimaryPhoneNumber=
-89860115628100057703\DataRoamingEnabled=false
-89860115628100057703\Imsi=
-89860115628100057703\Mcc=460
-89860115628100057703\Mnc=01
-89860115628100057703\PreferredLanguages=zh, en
-89860115628100057703\PrimaryPhoneNumber=
+89860113228100167651\DataRoamingEnabled=false
+89860113228100167651\Imsi=46001820662
+89860113228100167651\Mcc=460
+89860113228100167651\Mnc=01
+89860113228100167651\PreferredLanguages=zh, en
+89860113228100167651\PrimaryPhoneNumber=+8613219019856

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

I'll have a go at organising a time on IRC.  I don't have much free time
this week, but I also don't use my Ubuntu Touch phone for anything, so I
don't mind taking my time over this.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

There's been a reboot in the meantime by the way...

phablet@ubuntu-phablet:~$ status indicator-network
indicator-network start/running, process 2642

More stuff that may be useful, or just to keep in sync with all of the
above...

phablet@ubuntu-phablet:~$ ps auxww | grep 2642
phablet   2642  0.1  0.3  54024  6952 ?Ssl  23:09   0:00 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service
phablet   4400  0.0  0.0   4852   676 pts/16   S+   23:12   0:00 grep 
--color=auto 2642
phablet@ubuntu-phablet:~$ dbus-send --print-reply 
--dest=com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus 
org.freedesktop.DBus.Properties.Get 
string:com.ubuntu.connectivity1.NetworkingStatus string:Status
Error org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.ubuntu.connectivity1 was not provided by any .service files
phablet@ubuntu-phablet:~$ dbus-send --print-reply 
--dest=com.canonical.indicator.network /com/canonical/indicator/network/phone 
org.gtk.Menus.Start array:uint32:0
phablet@ubuntu-phablet:~$ cat .cache/upstart/indicator-network.log
cat: .cache/upstart/indicator-network.log: No such file or directory
phablet@ubuntu-phablet:~$ stop indicator-network
indicator-network stop/waiting
phablet@ubuntu-phablet:~$ ps auxww | grep indicator-network
phablet   4450  0.0  0.0   4848   676 pts/16   S+   23:15   0:00 grep 
--color=auto indicator-network
phablet@ubuntu-phablet:~$ start indicator-network
indicator-network start/running, process 4454
phablet@ubuntu-phablet:~$ ps auxww | grep indicator-network
phablet   4452  0.6  0.1  40192  3772 ?Ss   23:15   0:00 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-secret-agent
phablet   4454 11.0  0.3  54040  6836 ?Ssl  23:15   0:00 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service
phablet   4457  0.0  0.0   4848   676 pts/16   S+   23:15   0:00 grep 
--color=auto indicator-network
phablet@ubuntu-phablet:~$ cat .cache/upstart/indicator-network.log
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/3" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/4" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/5" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/6" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/7" ((null):0, 
(null))

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

phablet@ubuntu-phablet:~$ dbus-send --print-reply 
--dest=com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus 
org.freedesktop.DBus.Properties.Get 
string:com.ubuntu.connectivity1.NetworkingStatus string:Status
Error org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.ubuntu.connectivity1 was not provided by any .service files
phablet@ubuntu-phablet:~$ dbus-send --print-reply 
--dest=com.canonical.indicator.network /com/canonical/indicator/network/phone 
org.gtk.Menus.Start array:uint32:0
Error org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.canonical.indicator.network was not provided by any .service files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

Me too, this didn't allow me to check for updates:

phablet@ubuntu-phablet:~$ stop indicator-network
indicator-network stop/waiting

Here I went to System Settings.  It still said "Connect to the Internet
to check for updates".

phablet@ubuntu-phablet:~$ rm .cache/upstart/indicator-network*
phablet@ubuntu-phablet:~$ start indicator-network
indicator-network start/running, process 12648
phablet@ubuntu-phablet:~$ cat .cache/upstart/indicator-network.log 
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/0" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/1" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/2" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/3" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/4" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/5" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/6" ((null):0, 
(null))
Debug: Device Added: "/org/freedesktop/NetworkManager/Devices/7" ((null):0, 
(null))
phablet@ubuntu-phablet:~$

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Matthew Exon]

Hey Antti, that worked!  Thanks a lot for that!  I even forgot to add
the password keyword and it just prompted me for the password on screen.

Now when I try to check for software updates it says "Connect to the
Internet to check for updates", which isn't so good.  But oh well,
progress :-)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Wifi networking no longer possible, network indicator broken

[Matthew Exon]

Hi Alejandro, sorry I only just noticed your reply.

It's a little hard to get data off my phone at the moment.  But
indicator network is running:

2479 ? Ssl 0:00 
/usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-secret-agent
2539 ? Ssl 0:07 
/usr/lib/arm-linux-dnueabihf/indicator-network/indicator-network-service

I've been trying to use wpa_supplicant as you suggested but it
continually fails to connect, complaining about authentication timeouts.
I'm not sure if I'e got the right device driver.  I'm running:

sudo wpa_supplicant -Dwext -iwlan0 -cwpa.conf

It does understand the network's MAC and frequency, so I guess it's
talking to the driver OK.  This is with two different access points.

Also, wpa_supplicant is already running.  I can kill it but it just
comes back.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Wifi networking no longer possible, network indicator broken

[Matthew Exon]

Ah, I was just able to confirm that 3G does work.  I don't know if that
would provide a way to download a fixed system image or something - but
it'd be expensive and unreliable.

Also, there is a wlan0 device when I run ifconfig.  Is there a way to
configure a new wifi network on the command line?  Unfortunately this is
happening just when I've moved to a new city and I don't have any of my
previously configured wifi networks to connect to.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1615474] Re: Wifi networking no longer possible, network indicator broken

[Matthew Exon]

Also, correct me if I'm wrong, but it seems if a bug in a system update
prevents the phone connecting to wifi, that effectively bricks the
device, right?  Because there's no way to update the system software
without USB or wifi (and MX4s have broken USB hardware).  There should
be a way to download and install OTA updates via wget or rsync.  It
wouldn't be a problem if the wifi code was stable and reliable, but as
this and Bug #1588126 show, that's not the case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1615474

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+subscriptions

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

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

[Matthew Exon]

Is there some way to force media-hub to get stuck in this way?  Or even
better, perhaps write a test application that observes telepathy and
deliberately fails to confirm.  Then I could check that the results are
the same as what I was seeing.

"telepathy by design won't forward the incoming call to the approver ...
until all observers confirm receiving the incoming channel"

This means that a rogue application can block incoming calls by simply
observing telepathy?  That doesn't seem like a good design.  In
particular, media-hub is a very complicated piece of engineering with
innumerable dependencies on other software and the wider network, and
whose requirements are constantly in flux.  Answering phone calls is so
important, media hub should be treated as if it was actively malicious
rather than depended on for cooperation.

That said though, in my case I did see the approver (I assume that means
the green/red slider answer call widget), and there was one ring, which
sounds like it could rule out your guess.

Anyway, thanks very much for your investigations!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

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

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

[Matthew Exon]

Was this the only time this occurred?  As I said in the original report,
it also happened a week previously when the same person in New York
tried to phone me.  I don't have logs from that time, but there was
certainly a reboot in between.  Apart from that, I believe I have seen
this before but I can't be sure.  Those would have been local calls and
I would simply have called the person back.  But my SIM card doesn't
allow international outgoing calls so that wasn't an option in the New
York cases.

"Certain apps": I typically use gallery, dekko, terminal (which is set
to never be terminated using tweakgeek), browser, camera, settings,
contacts, messaging, phone, so those were probably "running" (although
apart from terminal probably terminated by the OS).  I was not using any
of them immediately prior to taking the call: I was expecting the call
and it was important, so all I did with the phone was check that it was
alive, running smoothly, and that the volume was turned up.

I attached two media hub log files.  Since they don't include datestamps
I couldn't be sure which covers the period of the calls.  It's almost
certainly the 2 Jun one though.  The DBus log file I'm pretty sure is
right.

Note that this phone has been switched off for a week.  I encountered
the problems.  Then I made a test call.  This failed, so I tried
rebooting the phone.  After that a test call worked.  At that point I
decided this phone was too unreliable to use and I switched to my
iPhone, which I've been using since.  After that it wasn't switched on
again until just now.

I can't use adb shell over USB.  As many people have been reporting with
MX4s, the USB port is too unreliable to use for more than a few seconds
at a time.  This is another reason I've concluded this phone is more
trouble than it's worth.  Please suggest an alternative.  I can ssh into
the phone no problems.

I've put a different SIM card in the phone and I'll leave it running for
a while.  Right now I can phone it no problem, consistent with me
finding that it temporarily fixes itself with a reboot.  The software
version is the same as it was, and I will avoid upgrading anything to
minimise the variables.  I'll try phoning again after a few days and
report back with the status.  However it's not really a comparable
environment.  As my main phone it travels with me, connects to various
wifi and cellular networks.  Also, I frequently turn on and off wifi,
bluetooth, and airplane mode as a work-around to other bugs.  And the
camera frequently mysteriously freezes so I have to terminate that.
Sitting on my desk doing nothing, I wouldn't be surprised if it works
fine.

Bear in mind that "this problem disappears after I upgrade to a newer
version" isn't really a happy ending to this story.  I need to be
reliably contactable, I can't take risks there.  If critical bugs are
creeping into a feature so fundamental to the purpose of a phone then
there's a problem with Ubuntu's development process, regardless of this
particular bug.  If you guys can show me how it was my mistake, or of my
carrier, or even of Meizu, then that's different, but at the moment I
consider Ubuntu Touch too unstable to use.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

[Matthew Exon]

** Attachment added: "DBus log, file modified date 2 Jun 09:53"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+attachment/4680093/+files/dbus.log.2.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

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

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

[Matthew Exon]

** Attachment added: "Media hub log, file modified date 9 Jun 08:31"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+attachment/4680092/+files/media-hub.log.1.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

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

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

[Matthew Exon]

** Attachment added: "Media hub log, file modified date 2 Jun 09:52"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+attachment/4680091/+files/media-hub.log.2.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1588127

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

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

[Touch-packages] [Bug 1518332] Re: FileManager should have option for viewing rather than exporting

[Matthew Exon]

Is this bug going to be closed because importing is now an option?  If
so does there need to be a new bug for opening via URL?

Importing a multi-gigabyte video from an SD card isn't going to work, of
course there's not enough space on the phone's internal memory for that,
not to mention the amount of time it takes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1518332

Title:
  FileManager should have option for viewing rather than exporting

Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  In Progress
Status in Ubuntu File Manager App:
  New
Status in mediaplayer-app package in Ubuntu:
  Fix Released
Status in ubuntu-filemanager-app package in Ubuntu:
  Confirmed

Bug description:
  I would expect to be able to open a .MP4 video from the file manager,
  and have it play in Media Player... but the it seems that Media Player
  is not an option for playback, only Gallery, which is not terribly
  suitable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518332/+subscriptions

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

[Touch-packages] [Bug 1512063] Re: Can't open photo from file manager

[Matthew Exon]

The behaviour now seems to be that if you open a photo, it makes a copy
of it.  Since this is the most recent image, it bubbles to the top in
Gallery, so it's reasonably easy to then open it.

But this means that every time you tap on a photo in file manager, it
makes a copy.  Tap on the same image three times, you now have four
copies of the same file.  This is pretty crazy.

Presumably this is related to Bug #1518332 and I guess the solution is
similar, open via URL.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512063

Title:
  Can't open photo from file manager

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  * Open File Manager
  * Open Pictures/com.ubuntu.camera
  * Tap on an image, for example image20151027_19343262.jpg
  * System asks what I want to open it with, Notes, Dekko, Tagger or Gallery
  * Tap Gallery

  Expected result

  * Gallery opens showing the picture in full-screen mode

  Actual result:

  * Gallery opens showing the "Events" page

  If I try this with a file from somewhere else other than
  com.ubuntu.camera, the result is that I can't view the file at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1512063/+subscriptions

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

[Touch-packages] [Bug 1563214] Re: Can’t browse and view local HTML files in home folder

[Matthew Exon]

My suggestion is more of a generic solution to the app confinement
problem.

Assume I start at the file manager and I tap on a file.  It presents an
"Open with" dialog showing the apps that can open that type of file.
The dialog should show all apps that can handle that file type,
regardless of whether they have permission to see that particular file.

Somewhere on that dialog should be a checkbox saying "permanently allow
app to view files in this directory" and a drop-down that by default has
the current directory selected, but allows you to select any parent
directory instead (yea even unto the very root).  Then you select the
app you want to open it with.  Apparmor is automatically reconfigured
appropriately, and the app opens to show the file.

It should then be possible to revoke these permissions somewhere in
System Settings / Security & Privacy / App permissions.

This is the closest I can think of to a "I don't care about your stupid
confinement model, just get the hell out of my way and never bother me
again" button, which is precisely what I say (often out loud) when
encountering app confinement issues in the present system.  But it still
allows reasonably tight security, especially if you make the effort to
organise your files.

It would also allow apps to do things that aren't realistically feasible
with a centralised file broker, such as custom "open file" dialogs,
watching directories and automatically indexing new files, using named
pipes, creating soft links, and all the other millions of things
developers might think up that you couldn't possibly predict while
designing an app confinement model.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1563214

Title:
  Can’t browse and view local HTML files in home folder

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  (initially reported on the ubuntu-phone mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg19168.html)

  With the apparmor confinement, it is impossible for a phone user to browse 
and view local HTML files stored in their home folder.
  This security policy was initially put in place to avoid disclosing sensitive 
information stored on the filesystem. It would be good to find a middle-ground 
solution that allows browsing and viewing "legitimate" files in one’s home 
folder, while preserving a good security level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1563214/+subscriptions

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

[Touch-packages] [Bug 1553431] [NEW] Feature: clip video

[Matthew Exon]

Public bug reported:

The gallery currently allows editing photos by cropping them or rotating
them.  By analogy, it should be possible to extract a short portion of a
video clip and save it as a new video.  Note that saving as a new video
is critical, do not overwrite the original.  This is because you might
want to extract multiple clips from a single video.

Justification for why this is important enough to add to a core app:

A phone is a communications device.  The reason for adding a video
camera to a phone is so that you can quickly share a moment with your
friends, on the spot, immediately.  It's not really so that you can
shoot footage for the feature film you're developing in your studio.

You don't want to waste data and you don't want to waste your friends'
time.  You want to send as short a clip as possible, normally just a few
seconds.  But you have to shoot a fairly long video, several minutes, to
be sure of capturing the right moment.  So without the ability to clip
the video it's almost impossible to capture something worth sharing.

Mucking around with a specialised video editing app is complicated and
loses the spontaneity.  There is definitely a role for a feature-rich,
sophisticated video-editing app.  I would certainly want this for more
interesting cases.  But I would only resort to that on rare occasions.

It could be argued that this is the responsibility of individual social
media apps.  But if you use multiple social media apps that wastes time.
It also wastes developer time and increases the UI surface area.

Adding a video clip feature would take the video recording functionality
from a "maybe I would use that sometimes" to a "something I couldn't
live without" level of usefulness.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1553431

Title:
  Feature: clip video

Status in gallery-app package in Ubuntu:
  New

Bug description:
  The gallery currently allows editing photos by cropping them or
  rotating them.  By analogy, it should be possible to extract a short
  portion of a video clip and save it as a new video.  Note that saving
  as a new video is critical, do not overwrite the original.  This is
  because you might want to extract multiple clips from a single video.

  Justification for why this is important enough to add to a core app:

  A phone is a communications device.  The reason for adding a video
  camera to a phone is so that you can quickly share a moment with your
  friends, on the spot, immediately.  It's not really so that you can
  shoot footage for the feature film you're developing in your studio.

  You don't want to waste data and you don't want to waste your friends'
  time.  You want to send as short a clip as possible, normally just a
  few seconds.  But you have to shoot a fairly long video, several
  minutes, to be sure of capturing the right moment.  So without the
  ability to clip the video it's almost impossible to capture something
  worth sharing.

  Mucking around with a specialised video editing app is complicated and
  loses the spontaneity.  There is definitely a role for a feature-rich,
  sophisticated video-editing app.  I would certainly want this for more
  interesting cases.  But I would only resort to that on rare occasions.

  It could be argued that this is the responsibility of individual
  social media apps.  But if you use multiple social media apps that
  wastes time.  It also wastes developer time and increases the UI
  surface area.

  Adding a video clip feature would take the video recording
  functionality from a "maybe I would use that sometimes" to a
  "something I couldn't live without" level of usefulness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1553431/+subscriptions

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

[Touch-packages] [Bug 1438162] Re: [osk] Touching "world" icon on the keyboard should cycle through all active keyboard layouts

[Matthew Exon]

I speak three languages and yes I would find it useful if it would
simply toggle between the last-used two languages, so English/German
when I'm in Germany, English/Chinese otherwise.  But the problem is
Emoji.  English, German, Chinese, I always need Emoji, and that
completely ruins the usefulness of switching between the two last-used
languages.  Either put Emoji on a dedicated button or change to cycling
among all available languages, I don't care.  But the way it is now just
doesn't work when I'm trying to chat in two languages at once while also
inserting the occasional Emoji.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1438162

Title:
  [osk] Touching "world" icon on the keyboard should cycle through all
  active keyboard layouts

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  I have 3 keyboard layouts active: English, Polish, Emoji. Now let's
  say the current layout is English. When I touch on the "world" icon
  the keyboard, the layout changes to Emoji. When I touch the icon
  again, the layout changes back to English. Then I touch it again, I
  get Emoji and so on. There's no way to change to the third layout
  without longpressing on the "world" icon and selecting the right
  layout there. I would expect the layout change to go through all
  active layouts, in my example English->Polish->Emoji->English and so
  on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1438162/+subscriptions

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

[Touch-packages] [Bug 1512211] Re: Charging from USB battery, phone stops charging, switches on screen, and discharges

[Matthew Exon]

@pat-mcgowan:

"The battery then decides that charging is over and automatically
switches off."

This model of battery pack tries to figure out when the plugged-in
device has got to 100% charge, and when it detects that situation it
switches itself off and stops supplying power.  It then won't supply any
more current until I switch it back on by pressing a button on the
front.  Presumably the idea is to save power by switching off both the
battery pack's and the device's charging circuits.

In this case I have a phone at 60% charge and I want to top it up.  I
plug it into the battery and it starts drawing current.  Then I go to
sleep.  After a couple of hours the phone is at 100% and it stops
drawing current from the USB battery.  The battery detects this drop in
current and switches itself off.  But the phone's screen stays on.
After a while it would like to top itself up again, but the battery is
switched off and won't supply current until I press the button.  So the
phone just keeps draining itself until I wake up, by which time it's
back to 60%.

This is a fairly normal USB power bank, brand name Anker (but likely a
fake).  I'm pretty sure I've seen this behaviour in other battery packs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1512211

Title:
  Charging from USB battery, phone stops charging, switches on screen,
  and discharges

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Fix Committed
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  When I was travelling recently I found that if I plugged into a USB
  battery overnight to charge my phone, when I got up the next morning
  the phone didn't have any more power than when I started.

  Turns out the reason is: when the phone decides the battery is full,
  it stops drawing current.  The battery then decides that charging is
  over and automatically switches off.  The phone then decides that it's
  been unplugged and turns the screen on.  I had set the phone to not
  automatically switch the screen off, so it just left the screen on all
  night.  The next morning it was as if it had never charged.

  So I have the following suggestions:

  1) Just don't turn the screen on when the user unplugs the charger
  2) If the intention is to let the user know that the charger has been 
unplugged, pop up a message.  Just turning the screen on isn't very useful 
feedback.
  3) If you are turning the screen on automatically it "doesn't count" wrt the 
user's "automatically turn off screen after..." setting.  This should always be 
just a few seconds.
  4) If the user has configured the phone to not automatically switch off the 
screen, don't automatically turn it on either
  5) Give me a few more options for automatically switching off the screen - 1, 
2, 3, 4, 5 and 10 is a lot of resolution at the low end.  Where is 30mins and 
1hour?

  P.S. this has nothing to do with webbrowser-app but I still can't
  figure out how to search launchpad for Ubuntu touch packages.

  
  ===UX comment===
  I will try to address all the points raised in the bug description.

  1) is invalid, we should turn on the screen when the user unplugs
  the charger and possibly show a message reminding the user to unplug
  the charger from the wall socket (if any).

  I agree with 2), the system should show a system message as well. This is 
already specified as one of the usecases of the new notifications system UX 
(which hasn't been implemented yet). 
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I 
(private link)

  I agree with 3) and this behaviour is already specified in the Screen 
blanking policy, that means it is on the plan to implement it (if it's not 
already)
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0 
(private link)

  4) is taken care of by implementing 3)

  Point 5) is valid but requires a new bug which should also specify the 
usecases when those longer values would be needed, so that UX designers can 
better understand the needs and the reasons behind a UX suggestion :)
  Matthew, could you please file that bug? :)

  Point 6) (the one presented in comment #1) is valid but requires a new bug, 
mentioning the usecases, just like 5). I have to say I am not really into that 
feature, because the screen backlight of devices like the Meizu MX4 probably 
consumes more power than a USB port provides (which is usually 500mA). So it 
needs special care and convincing usecases :)
  Matthew, could you please file that bug, specifying some usecases when this 
feature would be really handy? :) I can't promise we will implement it, but we 
can discuss it ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices

[Touch-packages] [Bug 1512211] Re: Charging from USB battery, phone stops charging, switches on screen, and discharges

[Matthew Exon]

I only just noticed the new description above with the invitation to
submit new bugs.  I've submitted Bug #1534565 for keeping the screen on
while charging, and Bug #1534563 for providing longer blank intervals.

I'd say that neither of these bugs is at all important and in fact I
might not even use them anyway.  The stuff confirmed as "valid" above
are the important things for me.  Still, use cases submitted for your
viewing pleasure...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1512211

Title:
  Charging from USB battery, phone stops charging, switches on screen,
  and discharges

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  New

Bug description:
  When I was travelling recently I found that if I plugged into a USB
  battery overnight to charge my phone, when I got up the next morning
  the phone didn't have any more power than when I started.

  Turns out the reason is: when the phone decides the battery is full,
  it stops drawing current.  The battery then decides that charging is
  over and automatically switches off.  The phone then decides that it's
  been unplugged and turns the screen on.  I had set the phone to not
  automatically switch the screen off, so it just left the screen on all
  night.  The next morning it was as if it had never charged.

  So I have the following suggestions:

  1) Just don't turn the screen on when the user unplugs the charger
  2) If the intention is to let the user know that the charger has been 
unplugged, pop up a message.  Just turning the screen on isn't very useful 
feedback.
  3) If you are turning the screen on automatically it "doesn't count" wrt the 
user's "automatically turn off screen after..." setting.  This should always be 
just a few seconds.
  4) If the user has configured the phone to not automatically switch off the 
screen, don't automatically turn it on either
  5) Give me a few more options for automatically switching off the screen - 1, 
2, 3, 4, 5 and 10 is a lot of resolution at the low end.  Where is 30mins and 
1hour?

  P.S. this has nothing to do with webbrowser-app but I still can't
  figure out how to search launchpad for Ubuntu touch packages.

  
  ===UX comment===
  I will try to address all the points raised in the bug description.

  1) is invalid, we should turn on the screen when the user unplugs
  the charger and possibly show a message reminding the user to unplug
  the charger from the wall socket (if any).

  I agree with 2), the system should show a system message as well. This is 
already specified as one of the usecases of the new notifications system UX 
(which hasn't been implemented yet). 
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I 
(private link)

  I agree with 3) and this behaviour is already specified in the Screen 
blanking policy, that means it is on the plan to implement it (if it's not 
already)
  
https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0 
(private link)

  4) is taken care of by implementing 3)

  Point 5) is valid but requires a new bug which should also specify the 
usecases when those longer values would be needed, so that UX designers can 
better understand the needs and the reasons behind a UX suggestion :)
  Matthew, could you please file that bug? :)

  Point 6) (the one presented in comment #1) is valid but requires a new bug, 
mentioning the usecases, just like 5). I have to say I am not really into that 
feature, because the screen backlight of devices like the Meizu MX4 probably 
consumes more power than a USB port provides (which is usually 500mA). So it 
needs special care and convincing usecases :)
  Matthew, could you please file that bug, specifying some usecases when this 
feature would be really handy? :) I can't promise we will implement it, but we 
can discuss it ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512211/+subscriptions

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

[Touch-packages] [Bug 1500633] Re: orientation sensor "last vertical" seems to be remembered and applied

[Matthew Exon]

Sorry to write so much about this: this bug has literally cost me that
much time.  Here's me trying to boil down the logic to point form:

1. The UI can be in one of two states: A or B
2. The accelerometer can be in an infinite number of states, some combination 
of acceleration in three dimensions
3. There is a thing called "System X" which tries to determine the user's 
current desired orientation from the accelerometer
4. System X's output can be one of three states: A, B or UNKNOWN (i.e. flat)
5. Apps (lock screen counts as an app) can support being in state A, or state 
B, or both
6. The shell has to be in the same state as the current app
7. If the current app only supports one state, ignore System X and switch UI to 
that state
8. If the current app supports both states, and System X indicates A or B, 
switch UI to that state
9. But if System X indicates UNKNOWN, do not switch

Bonus point:

10. Whenever the UI changes from A to B or vice versa, switch all
background apps that support both states, not just the current app

This bug is basically saying the system hasn't implemented point 9.  I
guess that's because System X, whatever that is, currently only supports
two states rather than three.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1500633

Title:
  orientation sensor "last vertical" seems to be remembered and applied

Status in QtMir:
  Incomplete
Status in Ubuntu UX:
  In Progress
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  latest rc-image

  1. download and install machines vs machines
  2. open machines vs machines
  3. open browser, rotate to landscape
  4. lay flat on table so that browser is still in landscape
  5. switch back to machines vs machines with launcher
  6. raise top of phone as to make the phone vertical in portrait, lay back 
down flat
  7. switch to browser

  expected: browser would be in landscape
  actual: browser rotates

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1500633/+subscriptions

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

[Touch-packages] [Bug 1500633] Re: orientation sensor "last vertical" seems to be remembered and applied

[Matthew Exon]

Here's another example: it also does it if you turn off the rotation
lock.

* Open the browser
* Hold the phone long edge perpendicular to the table
* Wait until it switches to portrait mode
* Put phone flat on the table
* Turn on rotation lock
* Hold phone short edge perpendicular to the table for a few seconds
* Put phone flat on the table
* Turn off rotation lock
* Browser rotates

This just happened to me yesterday.  I was happily reading some news in
portrait mode when it occurred to me that the rotation lock was on and I
normally keep it turned off.  So I turned it off - and got an
incomprehensible rotation.

Since it's locked in portrait mode, turning off the rotation lock
happens while the UI is in portrait mode.  At that time there's no
accelerometer data to indicate that the phone is really in landscape.
There is only historical accelerometer data indicating that once upon a
time the phone was in landscape.  But it rotates anyway.  This is why
I'm saying you should only ever rotate the phone to landscape if the
accelerometer says it's in landscape right now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1500633

Title:
  orientation sensor "last vertical" seems to be remembered and applied

Status in QtMir:
  Incomplete
Status in Ubuntu UX:
  In Progress
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  latest rc-image

  1. download and install machines vs machines
  2. open machines vs machines
  3. open browser, rotate to landscape
  4. lay flat on table so that browser is still in landscape
  5. switch back to machines vs machines with launcher
  6. raise top of phone as to make the phone vertical in portrait, lay back 
down flat
  7. switch to browser

  expected: browser would be in landscape
  actual: browser rotates

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1500633/+subscriptions

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

[Touch-packages] [Bug 1500633] Re: orientation sensor "last vertical" seems to be remembered and applied

[Matthew Exon]

...and another thing.  The rotation animation doesn't actually do its
job.  It's supposed to provide a smooth transition from one state to the
next.  But instead it takes a snapshot of state A, squishes it into the
shape of state B, and then afterwards shuffles everything around to a
good layout for the new screen.  "Squished A" is a lie, showing me a
bunch of buttons that don't really exist and I can't actually press.
This is something that the iPhone also gets wrong.

My suggestion for fade out/fade in is exactly for this reason.  That's
an easy way to animate from an old state, that can no longer be used, to
a new state that really can.  This gives me a chance during the
animation to predict where to put my finger - and move my finger away in
time if it's about to press a button I don't want to press.

I can imagine two other options.  One is to animate every UI element
separately, with each button simultaneously rotating and floating over
to its new position.  That sounds like it could be a complete mess
though.  The other option is to continuously resize the window as it
rotates, as if I were dragging the bottom right corner of the window on
a desktop machine.  That would probably lead to a sequence of "big bang"
state changes that might be confusing, but it would give me a much
better chance to predict the final location of the button I'm after.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1500633

Title:
  orientation sensor "last vertical" seems to be remembered and applied

Status in QtMir:
  Incomplete
Status in Ubuntu UX:
  In Progress
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  latest rc-image

  1. download and install machines vs machines
  2. open machines vs machines
  3. open browser, rotate to landscape
  4. lay flat on table so that browser is still in landscape
  5. switch back to machines vs machines with launcher
  6. raise top of phone as to make the phone vertical in portrait, lay back 
down flat
  7. switch to browser

  expected: browser would be in landscape
  actual: browser rotates

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1500633/+subscriptions

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

[Touch-packages] [Bug 1500633] Re: orientation sensor "last vertical" seems to be remembered and applied

[Matthew Exon]

I have a bunch of comments :-)  I have constant problems with rotation
on my phone and I really want them fixed.  Exactly which changes need to
be made I'm not sure, and I don't know if this bug in particular is
valid or not.  But it seems close enough that submitting a new bug
doesn't seem right.

I find that mostly I hold the phone flattish, with it tilted up at the
top-left or top-right corner depending on which hand I'm using.  This is
because it is low down at a comfortable holding level, and off to the
side so it doesn't interfere with what I'm actually doing.  So it's
normally sitting right on the boundary between landscape and portrait.
If the accelerometer is made very sensitive it'll constantly flip
between them.  But if the accelerometer is made relatively insensitive
then getting the phone to display the correct orientation requires
holding it at an unnatural angle.  The rotation animation is also far
too slow, and once it's decided to rotate the entire interface locks up
until it's finished.  So while the "how to reproduce" instructions might
sound unlikely, that's just because they've been made extreme.  In
practice this happens to me all the time, just at much shallower angles.

Making things worse is that the lock screen doesn't rotate at all.  So
typically what happens to me is I turn on my phone, enter my PIN, move
to press the button I want to press... but then everything starts
flipping and the button I want zips away from under my finger.  This
even if I thought I was holding the phone in landscape mode while I
unlocked it: I wasn't holding it at a steep enough angle.  So I have to
rotate the phone to an unnatural angle, wait for the phone to decide
it's time to rotate, wait for the rotation animation to complete, then
bring it back down and again find the button I want to press.  As far as
responsive UI design is concerned, it's pretty disastrous.

So my first thing is: a rotation animation doesn't make sense at all
unless the phone is actually moving from one state to another.  When the
phone is switched on, make a decision whether it's in landscape or
portrait and display the lock screen accordingly.  If the app underneath
the lock screen is in the wrong orientation, pre-rotate it, don't make
me wait for a rotation animation that makes no sense in context.  If the
lock screen only supports portrait mode, then the app will have to be
put in portrait mode - unless it's absolutely clear that I am really am
unlocking the phone while holding it sideways, which doesn't sound
likely.

I think fixing the lock screen so it rotates will probably help me a
bit.  But hopefully you can see that it won't solve the fundamental
problem.

There's a second problem which might have already been filed in a
separate bug, but is related.  When I swipe to flip between apps it
shows snapshots from whatever orientation they were in when they were
last active.  When I select one, that snapshot occupies the screen, and
I go to press a button.  But then the button slides away from me.
Instead, if the phone has rotated, all suspended apps need to be brought
back to life, repaint their screen in the background, be snapshotted,
and then put back to sleep in their new orientation.  Then the
concertina effect can show the apps as they will really be displayed if
I want to use them.

And since rotation is so slow and jerky (I'm using an MX4), I think it
would be really nice if there was an option to turn off the animation
entirely, or replace it with a very quick fade-out/fade-in or something.

Trying out an iPhone it seems that it's better mostly because it's just
much less sensitive to rotation.  Another possibility is to make this a
user setting.

Perhaps yet another idea would be when the phone is close to deciding to
rotate, some other UI element could show up alerting the user to that
fact.  At least then whatever else is wrong the rotation wouldn't come
as so much of a surprise.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1500633

Title:
  orientation sensor "last vertical" seems to be remembered and applied

Status in QtMir:
  Incomplete
Status in Ubuntu UX:
  In Progress
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  latest rc-image

  1. download and install machines vs machines
  2. open machines vs machines
  3. open browser, rotate to landscape
  4. lay flat on table so that browser is still in landscape
  5. switch back to machines vs machines with launcher
  6. raise top of phone as to make the phone vertical in portrait, lay back 
down flat
  7. switch to browser

  expected: browser would be in landscape
  actual: browser rotates

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1500633/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call

[Matthew Exon]

OK I get what the problem is: it's the proximity sensor.  I have a flip-
case for my phone that covers the proximity sensor.  If the flip-case is
closed the phone thinks it's next to my ear and switches off the screen.

So there are two things wrong here.  First (IMO) it doesn't make sense
to use the proximity sensor to control the screen when the phone call
hasn't been answered yet.  Second, the phone should at least switch the
screen on when I open the flip case, but it doesn't.

I tested it with four phone calls just now:

1) Flip-case closed.  Didn't switch on screen.
2) Flip-case open.  Screen turned on fine
3) Flip-case closed, then opened once it started ringing.  Still didn't switch 
on screen.
4) Flip-case open.  Screen turned on fine.

syslog attached.

** Attachment added: "syslog.gz"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524648/+attachment/4535610/+files/syslog.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1524648

Title:
  Display doesn't turn on for incoming phone call

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524648/+subscriptions

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call

[Matthew Exon]

Presumably not this one?

phablet@ubuntu-phablet:~$ ls -lh /var/crash
total 40K
-rw-rw-r-- 1 phablet whoopsie 37K Dec  7 10:27 
_usr_bin_content-hub-service.32011.crash

Not sure where the crash logs are kept...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1524648

Title:
  Display doesn't turn on for incoming phone call

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524648/+subscriptions

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call

[Matthew Exon]

OTA-8 and MX4 respectively.  I haven't put the phone in r/w mode or
installed anything apart from the app store, but I have got various
services running in a chroot - MySQL, Apache, and Mnemosyne.

I've had other problems that might be related.  For the past day or two
incoming texts have made the phone vibrate but not play a sound, even
though the volume was turned right up.  I went to the setting where the
sound plays and changed it, which proved that the phone was making
noise, but it didn't fix the problem.  Rebooting, however, did fix it.
If I have the same incoming call problem again I'll add more info.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1524648

Title:
  Display doesn't turn on for incoming phone call

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524648/+subscriptions

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

[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

[Matthew Exon]

I added them as separate bugs, bug #1523946 for PPTP and bug #1523948
for L2TP.  The implementation and user interface changes will be
different in each case and the priority may well be different as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1495553

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495553/+subscriptions

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

[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

[Matthew Exon]

Looking at the updated spec:

“Type:” should contain those VPN types currently implemented, currently
“OpenVPN”, and eventually “L2TP” and “PPTP”. While only one is
implemented, the menu should be present but disabled

Presumably then ww08-2016 will allow me to configure OpenVPN, but not
PPTP and L2TP.  Should I submit separate bugs for those?  Because those
are the ones I'm actually affected by.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1495553

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495553/+subscriptions

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

[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

[Matthew Exon]

Openvpn is blocked in China.  The protocol itself is detected and
automatically blocked.  So this isn't a solution for me, although I'm
sure it's good enough for lots of people.  PPTP and L2TP are allowed,
presumably because they tend to be used by companies rather than
individuals.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1495553

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495553/+subscriptions

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Matthew Exon]

I submitted Bug #1523308 which is probably a duplicate of this.
Happened earlier today on my MX4 (one SIM card), first time I've noticed
it.  There's a syslog attached to that bug.  I don't seem to have a
powerd log though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1493574

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions

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

[Touch-packages] [Bug 1506836] Re: LastPass bookmarklet not supported in ubuntu-touch browser

[Matthew Exon]

This method doesn't seem to work for me.  I select one of the links as
instructed.  It doesn't generate an error page, rather it just shows a
blank page.  When I go to the address bar it looks like most of the
javascript has been deleted, it just says
"ref);document.body.appendChild(_LP_);".

I think the address bar on this browser is too short to accept all that
javascript.  Only long-pressing on a link and selecting "Bookmark link"
works.

So I don't think this bug is ready to be closed as Invalid yet.

There really should be some way of inspecting and manually editing
bookmarks, not just adding or removing them.  If that was implemented,
this bug could be closed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506836

Title:
  LastPass bookmarklet not supported in ubuntu-touch browser

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  LastPass offers a bookmarklet feature, a little piece of javascript
  you can run from the address bar which fills in passwords for you.
  This is the only convenient way to use a password manager like this on
  a device that isn't natively supported by their plugins.  I used to
  use this feature all the time on my Nokia N900.

  The way it should work is:

  * Log in to the LastPass website, and in the "Tools" menu select 
"Bookmarklets"
  * Long press on "LastPass Fill!" and tap "Bookmark link"
  * Navigate to a website to log in to
  * On the address bar, clear the address and type "lastpass"
  * Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
  * Tap that bookmark
  * It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

  In fact after tapping the bookmark it does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506836/+subscriptions

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

[Touch-packages] [Bug 1520502] Re: Feature: resize image

[Matthew Exon]

Related is Bug #1455594, which requests this feature in the camera app
or the media centre.  Regardless, I still feel this function should be
added to gallery, although if it's added to media centre the importance
might be lower.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1520502

Title:
  Feature: resize image

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Gallery includes a crop feature, which is nice.  The other standard
  feature people need is resize.  This is especially true since the
  camera takes rather large photos unsuitable for sharing, but there's
  no way to shrink the files down.  See also Bug #1512651 to implement
  this in Dekko, but regardless of whether that's fixed this should be a
  feature in Gallery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520502/+subscriptions

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

[Touch-packages] [Bug 1520526] [NEW] Image filename and other meta data should be available

[Matthew Exon]

Public bug reported:

It's normal to be able to get metadata about a photo by some method or
other.  File name, file size, directory, resolution, codec would
normally be expected, but if you're going to have any metadata at all,
might as well put the full EXIF data.

For the moment, not being able to find out the file name is driving me
crazy because the file manager doesn't show the thumbnail, so there's no
way to figure out what photo is what.  But even if the file manager
thumbnails gets implemented, this is still an expected feature in the
gallery.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1520526

Title:
  Image filename and other meta data should be available

Status in gallery-app package in Ubuntu:
  New

Bug description:
  It's normal to be able to get metadata about a photo by some method or
  other.  File name, file size, directory, resolution, codec would
  normally be expected, but if you're going to have any metadata at all,
  might as well put the full EXIF data.

  For the moment, not being able to find out the file name is driving me
  crazy because the file manager doesn't show the thumbnail, so there's
  no way to figure out what photo is what.  But even if the file manager
  thumbnails gets implemented, this is still an expected feature in the
  gallery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520526/+subscriptions

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

[Touch-packages] [Bug 1520512] [NEW] Feature: lighten image

[Matthew Exon]

Public bug reported:

This is probably not as important as Bug #1520502 but after crop it's
probably the most common thing people need to adjust in their photos.
Should be possible to lighten an image.  Normally this is when you have
a photo of someone that's backlit, you need to lighten the image until
you can make out their faces.

I imagine there's clever things that can be done to improve the dynamic
range across the photo, and that would be great, but straightforward
"make everything lighter" is most important.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1520512

Title:
  Feature: lighten image

Status in gallery-app package in Ubuntu:
  New

Bug description:
  This is probably not as important as Bug #1520502 but after crop it's
  probably the most common thing people need to adjust in their photos.
  Should be possible to lighten an image.  Normally this is when you
  have a photo of someone that's backlit, you need to lighten the image
  until you can make out their faces.

  I imagine there's clever things that can be done to improve the
  dynamic range across the photo, and that would be great, but
  straightforward "make everything lighter" is most important.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520512/+subscriptions

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

[Touch-packages] [Bug 1520502] [NEW] Feature: resize image

[Matthew Exon]

Public bug reported:

Gallery includes a crop feature, which is nice.  The other standard
feature people need is resize.  This is especially true since the camera
takes rather large photos unsuitable for sharing, but there's no way to
shrink the files down.  See also Bug #1512651 to implement this in
Dekko, but regardless of whether that's fixed this should be a feature
in Gallery.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1520502

Title:
  Feature: resize image

Status in gallery-app package in Ubuntu:
  New

Bug description:
  Gallery includes a crop feature, which is nice.  The other standard
  feature people need is resize.  This is especially true since the
  camera takes rather large photos unsuitable for sharing, but there's
  no way to shrink the files down.  See also Bug #1512651 to implement
  this in Dekko, but regardless of whether that's fixed this should be a
  feature in Gallery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1520502/+subscriptions

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

[Touch-packages] [Bug 1520500] [NEW] Feature: save or cache page

[Matthew Exon]

Public bug reported:

Browsers normally include some way to save a page, including all CSS,
JavaScript and images necessary to show the page correctly.  This would
be good in the Touch web browser.

Justification:

I would argue that saving web pages for later viewing is even more
important on a mobile device than a computer.  On a computer you can
reasonably just leave the browser open if you want to do something else
and come back to it later.  On a phone the browser risks being closed
for lack of memory, and you have no control over that.

Furthermore, on a computer you normally have continuous internet access,
so it's easy to go back to the page later.  On a phone you are
frequently drifting in and out of good reception, so you may not be able
to reload the page precisely when you need it most.

For example, there's a webpage with a map showing an address, but when
you get there you're in a notspot.  Open your browser to where you left
it and you briefly get to see a fuzzy version of the map, which then
immediately gets yanked away from you!

My personal need is when I'm travelling.  I like to save
wikitravel/wikipedia pages of the place I'm going, hotel pages, booking
receipts and so on.  It is normal that when I first arrive in a city I
have no SIM card, let alone 3G.  At the moment my solution is to use
wget --page-requisites in a terminal to download the page, then run
Apache in a chroot to serve the pages back to the browser.  This is
fiddly and unpleasant.

A traditional save/load style interface with a file chooser dialog might
be nice.  I think better would be an option in the hamburger menu to
"cache" the page, similar to bookmarking but it keeps a copy of the
entire page.  Or you could save on UI surface area by always keeping an
entire copy of any page that's bookmarked.

My fantasy solution would be the above plus a dbus interface.  That
would allow, for example, an itinerary app to automatically figure out
which country/province/city I'm going to and pre-download relevant
pages.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1520500

Title:
  Feature: save or cache page

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Browsers normally include some way to save a page, including all CSS,
  JavaScript and images necessary to show the page correctly.  This
  would be good in the Touch web browser.

  Justification:

  I would argue that saving web pages for later viewing is even more
  important on a mobile device than a computer.  On a computer you can
  reasonably just leave the browser open if you want to do something
  else and come back to it later.  On a phone the browser risks being
  closed for lack of memory, and you have no control over that.

  Furthermore, on a computer you normally have continuous internet
  access, so it's easy to go back to the page later.  On a phone you are
  frequently drifting in and out of good reception, so you may not be
  able to reload the page precisely when you need it most.

  For example, there's a webpage with a map showing an address, but when
  you get there you're in a notspot.  Open your browser to where you
  left it and you briefly get to see a fuzzy version of the map, which
  then immediately gets yanked away from you!

  My personal need is when I'm travelling.  I like to save
  wikitravel/wikipedia pages of the place I'm going, hotel pages,
  booking receipts and so on.  It is normal that when I first arrive in
  a city I have no SIM card, let alone 3G.  At the moment my solution is
  to use wget --page-requisites in a terminal to download the page, then
  run Apache in a chroot to serve the pages back to the browser.  This
  is fiddly and unpleasant.

  A traditional save/load style interface with a file chooser dialog
  might be nice.  I think better would be an option in the hamburger
  menu to "cache" the page, similar to bookmarking but it keeps a copy
  of the entire page.  Or you could save on UI surface area by always
  keeping an entire copy of any page that's bookmarked.

  My fantasy solution would be the above plus a dbus interface.  That
  would allow, for example, an itinerary app to automatically figure out
  which country/province/city I'm going to and pre-download relevant
  pages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1520500/+subscriptions

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

[Touch-packages] [Bug 1512383] [NEW] Automatically rotate to best orientation for photo

[Matthew Exon]

Public bug reported:

The orientation of a photo displayed in full-screen mode should have
nothing to do with the accelerometer.  Photos should always be displayed
with their short axis at the short axis of the phone's screen, thus
maximising the viewable area.  When switching between landscape and
portrait photos it is easier and more natural to rotate the phone 90
degrees as if it was a paper photo rather than trying to shake the phone
until its accelerometer takes the hint, and then balancing the phone so
that the accelerometer never changes its mind.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512383

Title:
  Automatically rotate to best orientation for photo

Status in gallery-app package in Ubuntu:
  New

Bug description:
  The orientation of a photo displayed in full-screen mode should have
  nothing to do with the accelerometer.  Photos should always be
  displayed with their short axis at the short axis of the phone's
  screen, thus maximising the viewable area.  When switching between
  landscape and portrait photos it is easier and more natural to rotate
  the phone 90 degrees as if it was a paper photo rather than trying to
  shake the phone until its accelerometer takes the hint, and then
  balancing the phone so that the accelerometer never changes its mind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1512383/+subscriptions

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

[Touch-packages] [Bug 1512211] Re: Charging from USB battery, phone stops charging, switches on screen, and discharges

[Matthew Exon]

Oh, another option:

* Provide a "do not automatically switch off screen when connected to
charger" option.  That would also avoid the need for me to configure it
to never switch off.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512211

Title:
  Charging from USB battery, phone stops charging, switches on screen,
  and discharges

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When I was travelling recently I found that if I plugged into a USB
  battery overnight to charge my phone, when I got up the next morning
  the phone didn't have any more power than when I started.

  Turns out the reason is: when the phone decides the battery is full,
  it stops drawing current.  The battery then decides that charging is
  over and automatically switches off.  The phone then decides that it's
  been unplugged and turns the screen on.  I had set the phone to not
  automatically switch the screen off, so it just left the screen on all
  night.  The next morning it was as if it had never charged.

  So I have the following suggestions:

  * Just don't turn the screen on when the user unplugs the charger
  * If the intention is to let the user know that the charger has been 
unplugged, pop up a message.  Just turning the screen on isn't very useful 
feedback.
  * If you are turning the screen on automatically it "doesn't count" wrt the 
user's "automatically turn off screen after..." setting.  This should always be 
just a few seconds.
  * If the user has configured the phone to not automatically switch off the 
screen, don't automatically turn it on either
  * Give me a few more options for automatically switching off the screen - 1, 
2, 3, 4, 5 and 10 is a lot of resolution at the low end.  Where is 30mins and 
1hour?

  P.S. this has nothing to do with webbrowser-app but I still can't
  figure out how to search launchpad for Ubuntu touch packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1512211/+subscriptions

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

[Touch-packages] [Bug 1512211] [NEW] Charging from USB battery, phone stops charging, switches on screen, and discharges

[Matthew Exon]

Public bug reported:

When I was travelling recently I found that if I plugged into a USB
battery overnight to charge my phone, when I got up the next morning the
phone didn't have any more power than when I started.

Turns out the reason is: when the phone decides the battery is full, it
stops drawing current.  The battery then decides that charging is over
and automatically switches off.  The phone then decides that it's been
unplugged and turns the screen on.  I had set the phone to not
automatically switch the screen off, so it just left the screen on all
night.  The next morning it was as if it had never charged.

So I have the following suggestions:

* Just don't turn the screen on when the user unplugs the charger
* If the intention is to let the user know that the charger has been unplugged, 
pop up a message.  Just turning the screen on isn't very useful feedback.
* If you are turning the screen on automatically it "doesn't count" wrt the 
user's "automatically turn off screen after..." setting.  This should always be 
just a few seconds.
* If the user has configured the phone to not automatically switch off the 
screen, don't automatically turn it on either
* Give me a few more options for automatically switching off the screen - 1, 2, 
3, 4, 5 and 10 is a lot of resolution at the low end.  Where is 30mins and 
1hour?

P.S. this has nothing to do with webbrowser-app but I still can't figure
out how to search launchpad for Ubuntu touch packages.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512211

Title:
  Charging from USB battery, phone stops charging, switches on screen,
  and discharges

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When I was travelling recently I found that if I plugged into a USB
  battery overnight to charge my phone, when I got up the next morning
  the phone didn't have any more power than when I started.

  Turns out the reason is: when the phone decides the battery is full,
  it stops drawing current.  The battery then decides that charging is
  over and automatically switches off.  The phone then decides that it's
  been unplugged and turns the screen on.  I had set the phone to not
  automatically switch the screen off, so it just left the screen on all
  night.  The next morning it was as if it had never charged.

  So I have the following suggestions:

  * Just don't turn the screen on when the user unplugs the charger
  * If the intention is to let the user know that the charger has been 
unplugged, pop up a message.  Just turning the screen on isn't very useful 
feedback.
  * If you are turning the screen on automatically it "doesn't count" wrt the 
user's "automatically turn off screen after..." setting.  This should always be 
just a few seconds.
  * If the user has configured the phone to not automatically switch off the 
screen, don't automatically turn it on either
  * Give me a few more options for automatically switching off the screen - 1, 
2, 3, 4, 5 and 10 is a lot of resolution at the low end.  Where is 30mins and 
1hour?

  P.S. this has nothing to do with webbrowser-app but I still can't
  figure out how to search launchpad for Ubuntu touch packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1512211/+subscriptions

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

[Touch-packages] [Bug 1512063] [NEW] Can't open photo from file manager

[Matthew Exon]

Public bug reported:

* Open File Manager
* Open Pictures/com.ubuntu.camera
* Tap on an image, for example image20151027_19343262.jpg
* System asks what I want to open it with, Notes, Dekko, Tagger or Gallery
* Tap Gallery

Expected result

* Gallery opens showing the picture in full-screen mode

Actual result:

* Gallery opens showing the "Events" page

If I try this with a file from somewhere else other than
com.ubuntu.camera, the result is that I can't view the file at all.

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512063

Title:
  Can't open photo from file manager

Status in gallery-app package in Ubuntu:
  New

Bug description:
  * Open File Manager
  * Open Pictures/com.ubuntu.camera
  * Tap on an image, for example image20151027_19343262.jpg
  * System asks what I want to open it with, Notes, Dekko, Tagger or Gallery
  * Tap Gallery

  Expected result

  * Gallery opens showing the picture in full-screen mode

  Actual result:

  * Gallery opens showing the "Events" page

  If I try this with a file from somewhere else other than
  com.ubuntu.camera, the result is that I can't view the file at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1512063/+subscriptions

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

[Touch-packages] [Bug 1511892] [NEW] calendar-app unresponsive if I click on "Add online calendar"

[Matthew Exon]

Public bug reported:

I just finished setting up a DAViCal instance for sharing my calendar
between devices.  I want to set it up on my MX4.

* I go to the Calendar app
* Tap on the hamburger menu top right
* Tap on "Calendars"
* Three rows are displayed, "Personal", "Birthdays & Anniversaries", and "Add 
online Calendar"
* I can select/deselect "Personal" and "Birthdays & Anniversaries"
* Tap on "Add online Calendar"
* The row very briefly flashes slightly grey
* The whole page is now unresponsive - I can't select/deselect "Personal" and 
"Birthdays & Anniversaries" or tap the back button top left.

I thought at first that it might be due to being in China and google.com
being unavailable - the Google logo implies it's a google-only thing and
many western systems assume Google is available.  But I also tried it on
a VPN and got the same result.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1511892

Title:
  calendar-app unresponsive if I click on "Add online calendar"

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  I just finished setting up a DAViCal instance for sharing my calendar
  between devices.  I want to set it up on my MX4.

  * I go to the Calendar app
  * Tap on the hamburger menu top right
  * Tap on "Calendars"
  * Three rows are displayed, "Personal", "Birthdays & Anniversaries", and "Add 
online Calendar"
  * I can select/deselect "Personal" and "Birthdays & Anniversaries"
  * Tap on "Add online Calendar"
  * The row very briefly flashes slightly grey
  * The whole page is now unresponsive - I can't select/deselect "Personal" and 
"Birthdays & Anniversaries" or tap the back button top left.

  I thought at first that it might be due to being in China and
  google.com being unavailable - the Google logo implies it's a google-
  only thing and many western systems assume Google is available.  But I
  also tried it on a VPN and got the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1511892/+subscriptions

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

[Touch-packages] [Bug 1328183] Re: User-Agent string results in poor UX on web

[Matthew Exon]

Thanks for the discussion of this issue.  I came here from Bug #1506836,
learned something, and now I've just finished fixing the code on my own
site to handle "mobi" and "like android" tokens correctly :-)  I've also
submitted a feature request to LastPass.

To broaden the discussion slightly, could anyone comment on the
likelihood of any of the following things being implemented?  They would
all provide a (perhaps unfriendly) workaround in the situation where a
particular website refuses to play ball but a user has a desperate need
for it to work correctly:

* Provide a button or something in the browser to explicitly switch UA string 
(like Sogou does to handle Chinese websites that require IE6 brokenness)
* Support an "about:debug" page or similar that allows a custom UA string to be 
typed in
* Allow the user to edit the override list on their phone (even just a text 
file editable in the terminal would do)
* Support plugins in the browser that would allow third-party developers to fix 
the problem for you

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1328183

Title:
  User-Agent string results in poor UX on web

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The User-Agent string for the browser is similar enough to the Android
  browser User-Agent, that it creates a poor experience when browsing
  the web on an Ubuntu phone. An inordinately large number of web sites
  persistently advertise to "install our app" instead of providing the
  best web experience; an app which cannot be installed.

  This is exacerbated by the pervasiveness of webapps on Ubuntu phone,
  which simply embed the mobile web site with webapp-container, and
  still result in seeing such advertisements, despite the fact that the
  "app" on Ubuntu is already installed, and the Android apps being
  advertised are simply not installable.

  Having all the big web sites telling users of Ubuntu that they should
  be using Android instead, is not very good for the user experience at
  all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1328183/+subscriptions

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

[Touch-packages] [Bug 1506836] Re: LastPass bookmarklet not supported in ubuntu-touch browser

[Matthew Exon]

(Also it's kinda late here, I didn't read carefully, and I now realise
that all of the above is exactly what you said in your comment.  Sorry!
I still kinda think that the UA string is a bit misleading though.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506836

Title:
  LastPass bookmarklet not supported in ubuntu-touch browser

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  LastPass offers a bookmarklet feature, a little piece of javascript
  you can run from the address bar which fills in passwords for you.
  This is the only convenient way to use a password manager like this on
  a device that isn't natively supported by their plugins.  I used to
  use this feature all the time on my Nokia N900.

  The way it should work is:

  * Log in to the LastPass website, and in the "Tools" menu select 
"Bookmarklets"
  * Long press on "LastPass Fill!" and tap "Bookmark link"
  * Navigate to a website to log in to
  * On the address bar, clear the address and type "lastpass"
  * Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
  * Tap that bookmark
  * It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

  In fact after tapping the bookmark it does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506836/+subscriptions

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

[Touch-packages] [Bug 1506836] Re: LastPass bookmarklet not supported in ubuntu-touch browser

[Matthew Exon]

Ah right, so I just checked my own server logs and the user agent string
in the Ubuntu browser is "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android
4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36".  I
don't think I can realistically blame LastPass for treating it like an
Android phone!

I'd say that if you don't support "android:"-style links then you're not
"like Android 4.4" at all.  That's gonna break all kinds of stuff I'll
bet.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506836

Title:
  LastPass bookmarklet not supported in ubuntu-touch browser

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  LastPass offers a bookmarklet feature, a little piece of javascript
  you can run from the address bar which fills in passwords for you.
  This is the only convenient way to use a password manager like this on
  a device that isn't natively supported by their plugins.  I used to
  use this feature all the time on my Nokia N900.

  The way it should work is:

  * Log in to the LastPass website, and in the "Tools" menu select 
"Bookmarklets"
  * Long press on "LastPass Fill!" and tap "Bookmark link"
  * Navigate to a website to log in to
  * On the address bar, clear the address and type "lastpass"
  * Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
  * Tap that bookmark
  * It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

  In fact after tapping the bookmark it does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506836/+subscriptions

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

[Touch-packages] [Bug 1506836] Re: LastPass bookmarklet not supported in ubuntu-touch browser

[Matthew Exon]

Wow, that is interesting.  It turns out that using the Ubuntu browser
Lastpass's website returns that "android:" string as the bookmarklet,
whereas using a normal webbrowser it returns a much longer "javascript:"
string.  Seems like this is some kind of optimisation introduced on
LastPass's end and it's mistakenly identified the Ubuntu browser as an
Android browser.

I think this means that if I copied the correct "javascript:" string
from my computer into a bookmark, it'd probably work.  But I can't
figure out how I'd do that.  Any suggestions?

Meanwhile I guess I'll complain to LastPass...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506836

Title:
  LastPass bookmarklet not supported in ubuntu-touch browser

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  LastPass offers a bookmarklet feature, a little piece of javascript
  you can run from the address bar which fills in passwords for you.
  This is the only convenient way to use a password manager like this on
  a device that isn't natively supported by their plugins.  I used to
  use this feature all the time on my Nokia N900.

  The way it should work is:

  * Log in to the LastPass website, and in the "Tools" menu select 
"Bookmarklets"
  * Long press on "LastPass Fill!" and tap "Bookmark link"
  * Navigate to a website to log in to
  * On the address bar, clear the address and type "lastpass"
  * Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
  * Tap that bookmark
  * It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

  In fact after tapping the bookmark it does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506836/+subscriptions

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

[Touch-packages] [Bug 1506836] [NEW] LastPass bookmarklet not supported in ubuntu-touch browser

[Matthew Exon]

Public bug reported:

LastPass offers a bookmarklet feature, a little piece of javascript you
can run from the address bar which fills in passwords for you.  This is
the only convenient way to use a password manager like this on a device
that isn't natively supported by their plugins.  I used to use this
feature all the time on my Nokia N900.

The way it should work is:

* Log in to the LastPass website, and in the "Tools" menu select "Bookmarklets"
* Long press on "LastPass Fill!" and tap "Bookmark link"
* Navigate to a website to log in to
* On the address bar, clear the address and type "lastpass"
* Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
* Tap that bookmark
* It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

In fact after tapping the bookmark it does nothing.

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: messaging-app (Ubuntu) => webbrowser-app (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506836

Title:
  LastPass bookmarklet not supported in ubuntu-touch browser

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  LastPass offers a bookmarklet feature, a little piece of javascript
  you can run from the address bar which fills in passwords for you.
  This is the only convenient way to use a password manager like this on
  a device that isn't natively supported by their plugins.  I used to
  use this feature all the time on my Nokia N900.

  The way it should work is:

  * Log in to the LastPass website, and in the "Tools" menu select 
"Bookmarklets"
  * Long press on "LastPass Fill!" and tap "Bookmark link"
  * Navigate to a website to log in to
  * On the address bar, clear the address and type "lastpass"
  * Bookmarklet will be suggested as a bookmark with a star icon (it starts 
"android:lpfill...")
  * Tap that bookmark
  * It should execute the javascript and fill in username and password (after 
authenticating with LastPass)

  In fact after tapping the bookmark it does nothing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506836/+subscriptions

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

[Touch-packages] [Bug 1506784] [NEW] URLs in messages not recognised when prefixed with colon

[Matthew Exon]

Public bug reported:

I received an automated SMS which said "pick up your ticket
here:http://...";.  The URL is not recognised as a URL unless there is a
space before "http".  This works fine on Android and iOS, but is broken
in Ubuntu.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1506784

Title:
  URLs in messages not recognised when prefixed with colon

Status in messaging-app package in Ubuntu:
  New

Bug description:
  I received an automated SMS which said "pick up your ticket
  here:http://...";.  The URL is not recognised as a URL unless there is
  a space before "http".  This works fine on Android and iOS, but is
  broken in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1506784/+subscriptions

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

[Touch-packages] [Bug 1488705] [NEW] Chinese keyboard ignores input past current word

[Matthew Exon]

Public bug reported:

In Language & Text enable Zh 中文.  I have spell checking, auto
correction, and word suggestions turned off.

In messaging app, tap on the bottom bar to compose a message.  Select
"Chinese - Pinyin".

Type the letters "w" "o" "z" "a" "i" "l" "u" "s" "h" "a" "n" "g"
intending to write "我在路上" ("I'm on my way")

Keyboard displays the following options: "wozailushang", "我在", "我“, "沃"
etc

Select "我在".

Keyboard enters "我在" and returns to its waiting state.  It has forgotten
about the "lushang" so I have to re-type it.

Every other Chinese keyboard remembers the additional typing and allows
you to continue selecting characters.

Most other Chinese keyboards use the extra context to make a better
guess as to the overall meaning.  For example, on OSX, when I type
"yiju" the first option is "一句".  But if I type "yijuliangde" it is
ready with "一举两得".  This conditions users to type quite a lot of pinyin
in one go, delaying making a selection until they've completed the
current thought.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1488705

Title:
  Chinese keyboard ignores input past current word

Status in messaging-app package in Ubuntu:
  New

Bug description:
  In Language & Text enable Zh 中文.  I have spell checking, auto
  correction, and word suggestions turned off.

  In messaging app, tap on the bottom bar to compose a message.  Select
  "Chinese - Pinyin".

  Type the letters "w" "o" "z" "a" "i" "l" "u" "s" "h" "a" "n" "g"
  intending to write "我在路上" ("I'm on my way")

  Keyboard displays the following options: "wozailushang", "我在", "我“,
  "沃" etc

  Select "我在".

  Keyboard enters "我在" and returns to its waiting state.  It has
  forgotten about the "lushang" so I have to re-type it.

  Every other Chinese keyboard remembers the additional typing and
  allows you to continue selecting characters.

  Most other Chinese keyboards use the extra context to make a better
  guess as to the overall meaning.  For example, on OSX, when I type
  "yiju" the first option is "一句".  But if I type "yijuliangde" it is
  ready with "一举两得".  This conditions users to type quite a lot of
  pinyin in one go, delaying making a selection until they've completed
  the current thought.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1488705/+subscriptions

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