Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Ari Börde Kröyer]

Den 08. sep. 2015 16:33, skrev Jim Hodapp:


The result could be worse.

If for example Unity8/Mir crashes, then while apport does
its business
the shell isn't available (obviously, as it's just
crashed) and
doesn't restart until after apport is done. This likely
results in the
user seeing longer periods of "lock up" and will more
likely reboot
the device (the only remedial measure they can take)
almost certainly
resulting in an unusable crash dump, leading to us having
no way to
determine the reason for the initial crash.



I think we should at the very least warn the user that the phone
is uploading crash reports or generating core dumps, so that he at
least knows we're slowing down the system on purpose.


I completely disagree. This is a technical detail that I believe 
should be hidden from the user. Your average user will have no clue 
what a crash report is. I would say that if we can't actually report a 
crash in the background without taking up all of the spare CPU cycles, 
then this process is broken. Perhaps apport just isn't suited for 
mobile yet and needs to be fixed so that it doesn't peg the CPU and to 
popey's feedback, doesn't block the shell from starting again until 
after apport has finished. That would be the ideal user interaction - 
crash reports just happen in the background and the user can't tell 
performance-wise that it's even occurring.


Jim

I agree with Jim.

If Ubuntu phones had not been sold mainly to a community of enthusiasts, 
I am certain that the current performance of the phone would cause users 
to discard it and generate an amount of negative reviews that I fear 
would permanently damage its reputation.


Even with a generally forgiving community of phone owners, I think it 
would be wise to fix this issue very fast.


Keep up the good work! :)

Ari

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Sébastien Villemot]

Le mardi 08 septembre 2015 à 10:58 +0200, Jean-Baptiste Lallement a
écrit :

> Le 07/09/2015 22:38, Sébastien Villemot a écrit :
> > Le vendredi 04 septembre 2015 à 13:52 +0300, Timo Jyrinki a écrit :
> >
> >> You _might_ find something extra if you navigate to Settings ->
> >> Security -> Statistics -> Earlier error reports (sorry, I'm not sure
> >> about the English ones, I'm translating on-the-fly from my Bq) and
> >> check the top most links. The interesting things are Date, Package
> >> etc, plus of course the actual whole error report. It's is easier if
> >> you manage to copy the id link to your desktop browser and do
> >> copy-pasting error report URL:s from there.
> >
> > I am also experiencing general slowness on my BQ 4.5 since the OTA-6
> > upgrade, to the point where my phone is barely usable.
> > If I disable sending crash reports to Canonical, then the slowness
> > disappears. But the setting is quickly and automatically reverted to
> > its old value, without having me touching anything! So after a few
> > seconds/minutes, reports are again sent to Canonical, and my phone
> > becomes again almost unusable. Any idea how to fix this?
> >
> >
> This case may happen when there are lot of crash files to upload and the 
> crash files are large (ie they take a significant time to upload) For 
> example, when there were pending uploads and the device connects to 
> wifi, they're all uploaded.
> 
> I filed https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1493260 to 
> track this issue with a workaround.
> 
> It'll likely not solve all the "slowness" issues, but your description 
> suggests that it might be one of the sources.

Thanks for your feedback. Removing the files in /var/crash has indeed
improved the situation a lot.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jean-Baptiste Lallement]

Le 07/09/2015 10:17, Peter Bittner a écrit :

Salut Jean-Baptiste,

it's pretty easy to reproduce it on my end:

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).


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.


Could you file a bug against "Canonical System Image" 
https://bugs.launchpad.net/canonical-devices-system-image/+filebug ?


For reference the defect found in rc-proposed between OTA5 and 6 was 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483127



Thanks,

JB.



Hope that helps to fix the issue.

If there is an existing bug report I can of course easily add these
details. Otherwise, I can create a bug report (please tell me where).

Kind regard,
Peter


2015-09-07 9:43 GMT+02:00 Jean-Baptiste Lallement
:

Hi Peter,

Le 04/09/2015 19:59, Peter Bittner a écrit :


I can't confirm general slowness on my bq E5, but some other, critical
issues are still present:

1.) Phone app makes screen stays black during call (so you can't hang up).


Could you provide more details about this and how you reproduce it?

Thanks.


JB.

--
Jean-Baptiste Lallement
Canonical Services Ltd.
IRC: jibel



--
Jean-Baptiste Lallement
Canonical Services Ltd.
IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jean-Baptiste Lallement]

Le 07/09/2015 22:38, Sébastien Villemot a écrit :

Le vendredi 04 septembre 2015 à 13:52 +0300, Timo Jyrinki a écrit :


You _might_ find something extra if you navigate to Settings ->
Security -> Statistics -> Earlier error reports (sorry, I'm not sure
about the English ones, I'm translating on-the-fly from my Bq) and
check the top most links. The interesting things are Date, Package
etc, plus of course the actual whole error report. It's is easier if
you manage to copy the id link to your desktop browser and do
copy-pasting error report URL:s from there.


I am also experiencing general slowness on my BQ 4.5 since the OTA-6
upgrade, to the point where my phone is barely usable.
If I disable sending crash reports to Canonical, then the slowness
disappears. But the setting is quickly and automatically reverted to
its old value, without having me touching anything! So after a few
seconds/minutes, reports are again sent to Canonical, and my phone
becomes again almost unusable. Any idea how to fix this?





And 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493281 
is for the auto-reverting setting.


Thanks for reporting these issues.

JB.

--
Jean-Baptiste Lallement
Canonical Services Ltd.
IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jean-Baptiste Lallement]

Hi,

Le 07/09/2015 22:38, Sébastien Villemot a écrit :

Le vendredi 04 septembre 2015 à 13:52 +0300, Timo Jyrinki a écrit :


You _might_ find something extra if you navigate to Settings ->
Security -> Statistics -> Earlier error reports (sorry, I'm not sure
about the English ones, I'm translating on-the-fly from my Bq) and
check the top most links. The interesting things are Date, Package
etc, plus of course the actual whole error report. It's is easier if
you manage to copy the id link to your desktop browser and do
copy-pasting error report URL:s from there.


I am also experiencing general slowness on my BQ 4.5 since the OTA-6
upgrade, to the point where my phone is barely usable.
If I disable sending crash reports to Canonical, then the slowness
disappears. But the setting is quickly and automatically reverted to
its old value, without having me touching anything! So after a few
seconds/minutes, reports are again sent to Canonical, and my phone
becomes again almost unusable. Any idea how to fix this?


This case may happen when there are lot of crash files to upload and the 
crash files are large (ie they take a significant time to upload) For 
example, when there were pending uploads and the device connects to 
wifi, they're all uploaded.


I filed https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1493260 to 
track this issue with a workaround.


It'll likely not solve all the "slowness" issues, but your description 
suggests that it might be one of the sources.


JB.






--
Jean-Baptiste Lallement
Canonical Services Ltd.
IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Alan Pope]

Hi Jim,

On 8 September 2015 at 13:24, Jim Hodapp  wrote:
> Or couldn't we just deprioritize apport as a process so that it can't use up
> all of the CPU and truly make it a background task. Is there any reason why
> apport would need normal priority while running?
>

The result could be worse.

If for example Unity8/Mir crashes, then while apport does its business
the shell isn't available (obviously, as it's just crashed) and
doesn't restart until after apport is done. This likely results in the
user seeing longer periods of "lock up" and will more likely reboot
the device (the only remedial measure they can take) almost certainly
resulting in an unusable crash dump, leading to us having no way to
determine the reason for the initial crash.

Cheers,
-- 
Alan Pope
Community Manager

Canonical - Product Strategy
+44 (0) 7973 620 164
alan.p...@canonical.com
http://ubuntu.com/

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Alan Pope]

On 8 September 2015 at 10:25, Jean-Baptiste Lallement
 wrote:
> And https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493281
> is for the auto-reverting setting.
>
> Thanks for reporting these issues.
>

Marked as dupe of another bug which has been lingering for a while...

-- 
Alan Pope
Community Manager

Canonical - Product Strategy
+44 (0) 7973 620 164
alan.p...@canonical.com
http://ubuntu.com/

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jim Hodapp]

On Fri, Sep 4, 2015 at 8:10 AM, Kevin Gunn  wrote:

> Just thinking wrt "might it be some app/service
> crashing, apport running to collect crash data and freeze happens
> during that"
>
> It's a common enough occurrence should design consider a "system busy"
> notification just before launching apport. Otherwise this is exactly what
> happens, user says "huh, phone just bogged down for no reason, guess it's
> just performance"
>

Or couldn't we just deprioritize apport as a process so that it can't use
up all of the CPU and truly make it a background task. Is there any reason
why apport would need normal priority while running?

Jim


> br,kg
>
> On Fri, Sep 4, 2015 at 5:52 AM, Timo Jyrinki 
> wrote:
>
>> It'd be good to debug this further, although it might be difficult.
>>
>> I haven't noticed anything like described after OTA-6 upgrade two days
>> ago and I'm using apps / scopes on my Bq heavily.
>>
>> Just from technical guesses side, might it be some app/service
>> crashing, apport running to collect crash data and freeze happens
>> during that?
>>
>> You _might_ find something extra if you navigate to Settings ->
>> Security -> Statistics -> Earlier error reports (sorry, I'm not sure
>> about the English ones, I'm translating on-the-fly from my Bq) and
>> check the top most links. The interesting things are Date, Package
>> etc, plus of course the actual whole error report. It's is easier if
>> you manage to copy the id link to your desktop browser and do
>> copy-pasting error report URL:s from there.
>>
>> Not everything is shown there though, if the error report can't be
>> submitted. Due to various factors, not all apport collected issues are
>> actually sent.
>>
>> -Timo
>>
>>
>> On Fri, Sep 4, 2015 at 12:16 PM, Davide Alberelli 
>> wrote:
>> > Hello list,
>> > bq 4.5, r25.
>> > I am experiencing some general slowness after the OTA-6 update.
>> >
>> > This is particularly visible with freezes when scrolling in apps and
>> when
>> > changing between scopes (Apps -> Today <-> Near By <-> News) and when
>> > opening apps (this is _extremely_ slower than OTA-5).
>> >
>> > To reproduce the freeze in apps (webapps like Facebook (unofficial), or
>> > proper apps like browser, it's the same), scroll slowly down the page,
>> then
>> > a bit faster up and then down again to go back where you where.
>> >
>> > To reproduce in scopes just move from one to the other and/or down.
>> >
>> > What happens, in order, is
>> > 1) freeze of the interface for some seconds (no scroll, no swipe from
>> any
>> > direction)
>> > 2) wait, wait...
>> > 3) unfreeze and all what you have tried in 1) is done
>> > 4) if you are on a page in the browser it goes blank, if you are on
>> > everything else (scope, web-apps, ...) usually this results only in a
>> big
>> > jump around with no other harm.
>> >
>> > It is really annoying seeing this huge regressions in user exeprience
>> from
>> > one OTA to the other :S
>> >
>> > Any help investigating?
>> >
>> > Davide
>> >
>> > --
>> > Mailing list: https://launchpad.net/~ubuntu-phone
>> > Post to : ubuntu-phone@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~ubuntu-phone
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Peter Bittner]

Bug report on the issue "screen stays black during phone calls
(doesn't allow to hang up)":
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574


2015-09-08 9:14 GMT+02:00 Jean-Baptiste Lallement
:
> Le 07/09/2015 10:17, Peter Bittner a écrit :
>>
>> Salut Jean-Baptiste,
>>
>> it's pretty easy to reproduce it on my end:
>>
>> 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).
>
>
> 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.
>
> Could you file a bug against "Canonical System Image"
> https://bugs.launchpad.net/canonical-devices-system-image/+filebug ?
>
> For reference the defect found in rc-proposed between OTA5 and 6 was
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1483127
>
>
> Thanks,
>
> JB.
>
>>
>> Hope that helps to fix the issue.
>>
>> If there is an existing bug report I can of course easily add these
>> details. Otherwise, I can create a bug report (please tell me where).
>>
>> Kind regard,
>> Peter
>>
>>
>> 2015-09-07 9:43 GMT+02:00 Jean-Baptiste Lallement
>> :
>>>
>>> Hi Peter,
>>>
>>> Le 04/09/2015 19:59, Peter Bittner a écrit :


 I can't confirm general slowness on my bq E5, but some other, critical
 issues are still present:

 1.) Phone app makes screen stays black during call (so you can't hang
 up).
>>>
>>>
>>> Could you provide more details about this and how you reproduce it?
>>>
>>> Thanks.
>>>
>>>
>>> JB.
>>>
>>> --
>>> Jean-Baptiste Lallement
>>> Canonical Services Ltd.
>>> IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Sergio Schvezov]

On Tue, Sep 8, 2015 at 9:31 AM, Alan Pope  wrote:

> Hi Jim,
>
> On 8 September 2015 at 13:24, Jim Hodapp  wrote:
> > Or couldn't we just deprioritize apport as a process so that it can't
> use up
> > all of the CPU and truly make it a background task. Is there any reason
> why
> > apport would need normal priority while running?
> >
>
> The result could be worse.
>
> If for example Unity8/Mir crashes, then while apport does its business
> the shell isn't available (obviously, as it's just crashed) and
> doesn't restart until after apport is done. This likely results in the
> user seeing longer periods of "lock up" and will more likely reboot
> the device (the only remedial measure they can take) almost certainly
> resulting in an unusable crash dump, leading to us having no way to
> determine the reason for the initial crash.
>
>
I'm going to chime in my usual request of asking if apport could be run
only when plugged in to a power source :-) I currently have it disabled now
since it is a pain when on the go where I ended up manually power cycling
because it was faster and "I needed to make that call".
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Andrea Bernabei]

On Tue, Sep 8, 2015 at 3:17 PM, Sergio Schvezov <
sergio.schve...@canonical.com> wrote:

> On Tue, Sep 8, 2015 at 9:31 AM, Alan Pope  wrote:
>
>> Hi Jim,
>>
>> On 8 September 2015 at 13:24, Jim Hodapp 
>> wrote:
>> > Or couldn't we just deprioritize apport as a process so that it can't
>> use up
>> > all of the CPU and truly make it a background task. Is there any reason
>> why
>> > apport would need normal priority while running?
>> >
>>
>> The result could be worse.
>>
>> If for example Unity8/Mir crashes, then while apport does its business
>> the shell isn't available (obviously, as it's just crashed) and
>> doesn't restart until after apport is done. This likely results in the
>> user seeing longer periods of "lock up" and will more likely reboot
>> the device (the only remedial measure they can take) almost certainly
>> resulting in an unusable crash dump, leading to us having no way to
>> determine the reason for the initial crash.
>>
>>
>
I think we should at the very least warn the user that the phone is
uploading crash reports or generating core dumps, so that he at least knows
we're slowing down the system on purpose.

I would still think, though, that it makes more sense to get a few
corrupted crash dumps than to lock every phone so often just because things
fall apart.


> I'm going to chime in my usual request of asking if apport could be run
> only when plugged in to a power source :-) I currently have it disabled now
> since it is a pain when on the go where I ended up manually power cycling
> because it was faster and "I needed to make that call".
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Andrea Bernabei]

On Tue, Sep 8, 2015 at 3:33 PM, Jim Hodapp  wrote:

>
>
> On Tue, Sep 8, 2015 at 10:26 AM, Andrea Bernabei <
> andrea.berna...@canonical.com> wrote:
>
>>
>> On Tue, Sep 8, 2015 at 3:17 PM, Sergio Schvezov <
>> sergio.schve...@canonical.com> wrote:
>>
>>> On Tue, Sep 8, 2015 at 9:31 AM, Alan Pope 
>>> wrote:
>>>
 Hi Jim,

 On 8 September 2015 at 13:24, Jim Hodapp 
 wrote:
 > Or couldn't we just deprioritize apport as a process so that it can't
 use up
 > all of the CPU and truly make it a background task. Is there any
 reason why
 > apport would need normal priority while running?
 >

 The result could be worse.

 If for example Unity8/Mir crashes, then while apport does its business
 the shell isn't available (obviously, as it's just crashed) and
 doesn't restart until after apport is done. This likely results in the
 user seeing longer periods of "lock up" and will more likely reboot
 the device (the only remedial measure they can take) almost certainly
 resulting in an unusable crash dump, leading to us having no way to
 determine the reason for the initial crash.


>>>
>> I think we should at the very least warn the user that the phone is
>> uploading crash reports or generating core dumps, so that he at least knows
>> we're slowing down the system on purpose.
>>
>
> I completely disagree. This is a technical detail that I believe should be
> hidden from the user. Your average user will have no clue what a crash
> report is. I would say that if we can't actually report a crash in the
> background without taking up all of the spare CPU cycles, then this process
> is broken. Perhaps apport just isn't suited for mobile yet and needs to be
> fixed so that it doesn't peg the CPU and to popey's feedback, doesn't block
> the shell from starting again until after apport has finished. That would
> be the ideal user interaction - crash reports just happen in the background
> and the user can't tell performance-wise that it's even occurring.
>
>
I agree 100%.
Having everything working in background without locking the device up would
be ideal. That's what I meant with "at the very least", as in, if we really
have to lock the device, we should tell the user that it's intentional and
we know what we're doing (and ask for some patience). We have to give
feedback, *if* we really really have to lock his phone (which we shouldn't,
of course).

It doesn't have to be a technical message, as you correctly pointed out.
But having the user look at the device and think "wtf is going on" is bad
UX, imho :) Locking his phone for our debugging pleasure is still bad UX,
but it's a bit better if the user at least gets some kind of feedback on
what's going on.

Andrea

Jim
>
>
>
>>
>> I would still think, though, that it makes more sense to get a few
>> corrupted crash dumps than to lock every phone so often just because things
>> fall apart.
>>
>>
>>> I'm going to chime in my usual request of asking if apport could be run
>>> only when plugged in to a power source :-) I currently have it disabled now
>>> since it is a pain when on the go where I ended up manually power cycling
>>> because it was faster and "I needed to make that call".
>>>
>>> --
>>> Mailing list: https://launchpad.net/~ubuntu-phone
>>> Post to : ubuntu-phone@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jim Hodapp]

On Tue, Sep 8, 2015 at 10:26 AM, Andrea Bernabei <
andrea.berna...@canonical.com> wrote:

>
> On Tue, Sep 8, 2015 at 3:17 PM, Sergio Schvezov <
> sergio.schve...@canonical.com> wrote:
>
>> On Tue, Sep 8, 2015 at 9:31 AM, Alan Pope 
>> wrote:
>>
>>> Hi Jim,
>>>
>>> On 8 September 2015 at 13:24, Jim Hodapp 
>>> wrote:
>>> > Or couldn't we just deprioritize apport as a process so that it can't
>>> use up
>>> > all of the CPU and truly make it a background task. Is there any
>>> reason why
>>> > apport would need normal priority while running?
>>> >
>>>
>>> The result could be worse.
>>>
>>> If for example Unity8/Mir crashes, then while apport does its business
>>> the shell isn't available (obviously, as it's just crashed) and
>>> doesn't restart until after apport is done. This likely results in the
>>> user seeing longer periods of "lock up" and will more likely reboot
>>> the device (the only remedial measure they can take) almost certainly
>>> resulting in an unusable crash dump, leading to us having no way to
>>> determine the reason for the initial crash.
>>>
>>>
>>
> I think we should at the very least warn the user that the phone is
> uploading crash reports or generating core dumps, so that he at least knows
> we're slowing down the system on purpose.
>

I completely disagree. This is a technical detail that I believe should be
hidden from the user. Your average user will have no clue what a crash
report is. I would say that if we can't actually report a crash in the
background without taking up all of the spare CPU cycles, then this process
is broken. Perhaps apport just isn't suited for mobile yet and needs to be
fixed so that it doesn't peg the CPU and to popey's feedback, doesn't block
the shell from starting again until after apport has finished. That would
be the ideal user interaction - crash reports just happen in the background
and the user can't tell performance-wise that it's even occurring.

Jim



>
> I would still think, though, that it makes more sense to get a few
> corrupted crash dumps than to lock every phone so often just because things
> fall apart.
>
>
>> I'm going to chime in my usual request of asking if apport could be run
>> only when plugged in to a power source :-) I currently have it disabled now
>> since it is a pain when on the go where I ended up manually power cycling
>> because it was faster and "I needed to make that call".
>>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jim Hodapp]

Does anyone know if there's a bug filed for this issue and against the
appropriate packages/projects? It'd be nice to know if the right person is
looking into fixing this apport issue.

Jim

On Tue, Sep 8, 2015 at 11:06 AM, Andrea Bernabei <
andrea.berna...@canonical.com> wrote:

>
>
> On Tue, Sep 8, 2015 at 3:33 PM, Jim Hodapp 
> wrote:
>
>>
>>
>> On Tue, Sep 8, 2015 at 10:26 AM, Andrea Bernabei <
>> andrea.berna...@canonical.com> wrote:
>>
>>>
>>> On Tue, Sep 8, 2015 at 3:17 PM, Sergio Schvezov <
>>> sergio.schve...@canonical.com> wrote:
>>>
 On Tue, Sep 8, 2015 at 9:31 AM, Alan Pope 
 wrote:

> Hi Jim,
>
> On 8 September 2015 at 13:24, Jim Hodapp 
> wrote:
> > Or couldn't we just deprioritize apport as a process so that it
> can't use up
> > all of the CPU and truly make it a background task. Is there any
> reason why
> > apport would need normal priority while running?
> >
>
> The result could be worse.
>
> If for example Unity8/Mir crashes, then while apport does its business
> the shell isn't available (obviously, as it's just crashed) and
> doesn't restart until after apport is done. This likely results in the
> user seeing longer periods of "lock up" and will more likely reboot
> the device (the only remedial measure they can take) almost certainly
> resulting in an unusable crash dump, leading to us having no way to
> determine the reason for the initial crash.
>
>

>>> I think we should at the very least warn the user that the phone is
>>> uploading crash reports or generating core dumps, so that he at least knows
>>> we're slowing down the system on purpose.
>>>
>>
>> I completely disagree. This is a technical detail that I believe should
>> be hidden from the user. Your average user will have no clue what a crash
>> report is. I would say that if we can't actually report a crash in the
>> background without taking up all of the spare CPU cycles, then this process
>> is broken. Perhaps apport just isn't suited for mobile yet and needs to be
>> fixed so that it doesn't peg the CPU and to popey's feedback, doesn't block
>> the shell from starting again until after apport has finished. That would
>> be the ideal user interaction - crash reports just happen in the background
>> and the user can't tell performance-wise that it's even occurring.
>>
>>
> I agree 100%.
> Having everything working in background without locking the device up
> would be ideal. That's what I meant with "at the very least", as in, if we
> really have to lock the device, we should tell the user that it's
> intentional and we know what we're doing (and ask for some patience). We
> have to give feedback, *if* we really really have to lock his phone (which
> we shouldn't, of course).
>
> It doesn't have to be a technical message, as you correctly pointed out.
> But having the user look at the device and think "wtf is going on" is bad
> UX, imho :) Locking his phone for our debugging pleasure is still bad UX,
> but it's a bit better if the user at least gets some kind of feedback on
> what's going on.
>
> Andrea
>
> Jim
>>
>>
>>
>>>
>>> I would still think, though, that it makes more sense to get a few
>>> corrupted crash dumps than to lock every phone so often just because things
>>> fall apart.
>>>
>>>
 I'm going to chime in my usual request of asking if apport could be run
 only when plugged in to a power source :-) I currently have it disabled now
 since it is a pain when on the go where I ended up manually power cycling
 because it was faster and "I needed to make that call".

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


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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Peter Bittner]

Salut Jean-Baptiste,

it's pretty easy to reproduce it on my end:

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).

Hope that helps to fix the issue.

If there is an existing bug report I can of course easily add these
details. Otherwise, I can create a bug report (please tell me where).

Kind regard,
Peter


2015-09-07 9:43 GMT+02:00 Jean-Baptiste Lallement
:
> Hi Peter,
>
> Le 04/09/2015 19:59, Peter Bittner a écrit :
>>
>> I can't confirm general slowness on my bq E5, but some other, critical
>> issues are still present:
>>
>> 1.) Phone app makes screen stays black during call (so you can't hang up).
>
> Could you provide more details about this and how you reproduce it?
>
> Thanks.
>
>
> JB.
>
> --
> Jean-Baptiste Lallement
> Canonical Services Ltd.
> IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Jean-Baptiste Lallement]

Hi Peter,

Le 04/09/2015 19:59, Peter Bittner a écrit :

I can't confirm general slowness on my bq E5, but some other, critical
issues are still present:

1.) Phone app makes screen stays black during call (so you can't hang up).

Could you provide more details about this and how you reproduce it?

Thanks.


JB.

--
Jean-Baptiste Lallement
Canonical Services Ltd.
IRC: jibel

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Peter Bittner]

Follow-up on my WiFi (indicator) issue after OTA-6:

> 4.) When I come back into reach of a WiFi network (e.g. when turning
> home) the phone doesn't automatically reconnect. (Makes me continue
> using up mobile broadband traffic.)

I noticed today this could be a network indicator problem, rather than
an actual WiFi reconnection issue: My phone shows an empty WiFi
indicator at the moment (as if WiFi were out of reach), but no mobile
broadband indicator either (usually "H" for HSDPA). I've disabled
mobile traffic in the network settings to be sure, and websites (e.g.
the Skype web app) load normally.

Though I *believe* I also had the "H" indicator (broadband) active,
i.e. WiFi not reconnecting, after getting home last week. This could
of course have been any network issue, maybe not caused by the mobile
device.

Peter

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Sébastien Villemot]

Le vendredi 04 septembre 2015 à 13:52 +0300, Timo Jyrinki a écrit :

> You _might_ find something extra if you navigate to Settings ->
> Security -> Statistics -> Earlier error reports (sorry, I'm not sure
> about the English ones, I'm translating on-the-fly from my Bq) and
> check the top most links. The interesting things are Date, Package
> etc, plus of course the actual whole error report. It's is easier if
> you manage to copy the id link to your desktop browser and do
> copy-pasting error report URL:s from there.

I am also experiencing general slowness on my BQ 4.5 since the OTA-6
upgrade, to the point where my phone is barely usable.
If I disable sending crash reports to Canonical, then the slowness
disappears. But the setting is quickly and automatically reverted to
its old value, without having me touching anything! So after a few
seconds/minutes, reports are again sent to Canonical, and my phone
becomes again almost unusable. Any idea how to fix this?
-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594




signature.asc
Description: This is a digitally signed message part
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Roberto Resoli]

Su venerdì 4 settembre 2015 19:59:51 CEST, Peter Bittner ha scritto:
I can't confirm general slowness on my bq E5, 


I own an E4.5, no general slowness here too.

but some other, critical

issues are still present:

1.) Phone app makes screen stays black during call (so you can't hang up).


Can't confirm. Calls are OK here.


2.) Copy-and-paste still doesn't work neither in a browser nor any web
apps. (I only get the selected area and a "Copy" option.)


As usual. Clipboard management in browser is in my opinion currently one of 
the main issues for the platform, ATM.



3.) Web apps turn into a white screen sometimes.


Yes, happens very rarely here, anyway.


And, what we not a problem before the upgrade:

4.) When I come back into reach of a WiFi network (e.g. when turning
home) the phone doesn't automatically reconnect. (Makes me continue
using up mobile broadband traffic.)


Maybe this is a (missing) feature, not a bug. Not a problem here. Anyway, 
will try.


bye,
rob


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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[cédric bellegarde]

1.) is really annoying, I can't cancel a call easily due to this bug.

Regards,
Cedric

Le vendredi 4 septembre 2015 19:59:51 CEST, Peter Bittner a écrit :

I can't confirm general slowness on my bq E5, but some other, critical
issues are still present:

1.) Phone app makes screen stays black during call (so you can't hang up).
2.) Copy-and-paste still doesn't work neither in a browser nor any web
apps. (I only get the selected area and a "Copy" option.)
3.) Web apps turn into a white screen sometimes.

And, what we not a problem before the upgrade:

4.) When I come back into reach of a WiFi network (e.g. when turning
home) the phone doesn't automatically reconnect. (Makes me continue
using up mobile broadband traffic.)

Anyone else having those too? I guess so.
Which of those do have bugs reports on Launchpad?

Johan, if you have issues with the Facebook web app (which one?) try
Mitchell Reese's web app. That works fine on my bq E5. And that it's
much better than Canonical's implementation (sorry guys!) goes without
saying.

Peter


2015-09-04 11:28 GMT+02:00 Johan Velthuizen :

I didn't notice the slowness but the blank screen in the browser and
Facebook app was already an issue in OTA-5 and we are very 
disappointed that

this still exist in OTA-6

Met vriendelijke groet,
Johan Velthuizen
Velthuizen Webdesign & Media
Christineweg 17
2961 AB Kinderdijk
Tel. 078 6990167
www.velthuizen.nl

Op 04-09-15 om 11:16 schreef Davide Alberelli:

Hello list,
bq 4.5, r25.
I am experiencing some general slowness after the OTA-6 update.

This is particularly visible with freezes when scrolling in apps and when
changing between scopes (Apps -> Today <-> Near By <-> News) and when
opening apps (this is _extremely_ slower than OTA-5).

To reproduce the freeze in apps (webapps like Facebook (unofficial), or
proper apps like browser, it's the same), scroll slowly down 
the page, then

a bit faster up and then down again to go back where you where.

To reproduce in scopes just move from one to the other and/or down.

What happens, in order, is
1) freeze of the interface for some seconds (no scroll, no swipe from any
direction)
2) wait, wait...
3) unfreeze and all what you have tried in 1) is done
4) if you are on a page in the browser it goes blank, if you are on
everything else (scope, web-apps, ...) usually this results only in a big
jump around with no other harm.

It is really annoying seeing this huge regressions in user 
exeprience from

one OTA to the other :S

Any help investigating?

Davide




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






--
Message envoyé via Dekko depuis mon appareil Ubuntu

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Roberto Resoli]

Su sabato 5 settembre 2015 09:31:37 CEST, Roberto Resoli ha scritto:

Su venerdì 4 settembre 2015 19:59:51 CEST, Peter Bittner ha scritto:

...

4.) When I come back into reach of a WiFi network (e.g. when turning
home) the phone doesn't automatically reconnect. (Makes me continue
using up mobile broadband traffic.)


Maybe this is a (missing) feature, not a bug. Not a problem here. Anyway, 
will try.


This is working OK here. Switching from 3g to wifi happens regularly.


bye,
rob






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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Kevin Gunn]

Just thinking wrt "might it be some app/service
crashing, apport running to collect crash data and freeze happens
during that"

It's a common enough occurrence should design consider a "system busy"
notification just before launching apport. Otherwise this is exactly what
happens, user says "huh, phone just bogged down for no reason, guess it's
just performance"

br,kg

On Fri, Sep 4, 2015 at 5:52 AM, Timo Jyrinki 
wrote:

> It'd be good to debug this further, although it might be difficult.
>
> I haven't noticed anything like described after OTA-6 upgrade two days
> ago and I'm using apps / scopes on my Bq heavily.
>
> Just from technical guesses side, might it be some app/service
> crashing, apport running to collect crash data and freeze happens
> during that?
>
> You _might_ find something extra if you navigate to Settings ->
> Security -> Statistics -> Earlier error reports (sorry, I'm not sure
> about the English ones, I'm translating on-the-fly from my Bq) and
> check the top most links. The interesting things are Date, Package
> etc, plus of course the actual whole error report. It's is easier if
> you manage to copy the id link to your desktop browser and do
> copy-pasting error report URL:s from there.
>
> Not everything is shown there though, if the error report can't be
> submitted. Due to various factors, not all apport collected issues are
> actually sent.
>
> -Timo
>
>
> On Fri, Sep 4, 2015 at 12:16 PM, Davide Alberelli 
> wrote:
> > Hello list,
> > bq 4.5, r25.
> > I am experiencing some general slowness after the OTA-6 update.
> >
> > This is particularly visible with freezes when scrolling in apps and when
> > changing between scopes (Apps -> Today <-> Near By <-> News) and when
> > opening apps (this is _extremely_ slower than OTA-5).
> >
> > To reproduce the freeze in apps (webapps like Facebook (unofficial), or
> > proper apps like browser, it's the same), scroll slowly down the page,
> then
> > a bit faster up and then down again to go back where you where.
> >
> > To reproduce in scopes just move from one to the other and/or down.
> >
> > What happens, in order, is
> > 1) freeze of the interface for some seconds (no scroll, no swipe from any
> > direction)
> > 2) wait, wait...
> > 3) unfreeze and all what you have tried in 1) is done
> > 4) if you are on a page in the browser it goes blank, if you are on
> > everything else (scope, web-apps, ...) usually this results only in a big
> > jump around with no other harm.
> >
> > It is really annoying seeing this huge regressions in user exeprience
> from
> > one OTA to the other :S
> >
> > Any help investigating?
> >
> > Davide
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to : ubuntu-phone@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] General Slowness after OTA-6 update

[Davide Alberelli]

Hello list,
bq 4.5, r25.
I am experiencing some general slowness after the OTA-6 update.

This is particularly visible with freezes when scrolling in apps and when
changing between scopes (Apps -> Today <-> Near By <-> News) and when
opening apps (this is _extremely_ slower than OTA-5).

To reproduce the freeze in apps (webapps like Facebook (unofficial), or
proper apps like browser, it's the same), scroll slowly down the page, then
a bit faster up and then down again to go back where you where.

To reproduce in scopes just move from one to the other and/or down.

What happens, in order, is
1) freeze of the interface for some seconds (no scroll, no swipe from any
direction)
2) wait, wait...
3) unfreeze and all what you have tried in 1) is done
4) if you are on a page in the browser it goes blank, if you are on
everything else (scope, web-apps, ...) usually this results only in a big
jump around with no other harm.

It is really annoying seeing this huge regressions in user exeprience from
one OTA to the other :S

Any help investigating?

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Timo Jyrinki]

It'd be good to debug this further, although it might be difficult.

I haven't noticed anything like described after OTA-6 upgrade two days
ago and I'm using apps / scopes on my Bq heavily.

Just from technical guesses side, might it be some app/service
crashing, apport running to collect crash data and freeze happens
during that?

You _might_ find something extra if you navigate to Settings ->
Security -> Statistics -> Earlier error reports (sorry, I'm not sure
about the English ones, I'm translating on-the-fly from my Bq) and
check the top most links. The interesting things are Date, Package
etc, plus of course the actual whole error report. It's is easier if
you manage to copy the id link to your desktop browser and do
copy-pasting error report URL:s from there.

Not everything is shown there though, if the error report can't be
submitted. Due to various factors, not all apport collected issues are
actually sent.

-Timo


On Fri, Sep 4, 2015 at 12:16 PM, Davide Alberelli  wrote:
> Hello list,
> bq 4.5, r25.
> I am experiencing some general slowness after the OTA-6 update.
>
> This is particularly visible with freezes when scrolling in apps and when
> changing between scopes (Apps -> Today <-> Near By <-> News) and when
> opening apps (this is _extremely_ slower than OTA-5).
>
> To reproduce the freeze in apps (webapps like Facebook (unofficial), or
> proper apps like browser, it's the same), scroll slowly down the page, then
> a bit faster up and then down again to go back where you where.
>
> To reproduce in scopes just move from one to the other and/or down.
>
> What happens, in order, is
> 1) freeze of the interface for some seconds (no scroll, no swipe from any
> direction)
> 2) wait, wait...
> 3) unfreeze and all what you have tried in 1) is done
> 4) if you are on a page in the browser it goes blank, if you are on
> everything else (scope, web-apps, ...) usually this results only in a big
> jump around with no other harm.
>
> It is really annoying seeing this huge regressions in user exeprience from
> one OTA to the other :S
>
> Any help investigating?
>
> Davide
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Ari Börde Kröyer]

I can confirm issues 2, 3 and 4 below.

I also still have trouble waking the phone with the "on" button. I most 
often have to press it 3 times to get the display to wake up properly.


Ari

Den 04. sep. 2015 19:59, skrev Peter Bittner:

1.) Phone app makes screen stays black during call (so you can't hang up).
2.) Copy-and-paste still doesn't work neither in a browser nor any web
apps. (I only get the selected area and a "Copy" option.)
3.) Web apps turn into a white screen sometimes.

And, what we not a problem before the upgrade:

4.) When I come back into reach of a WiFi network (e.g. when turning
home) the phone doesn't automatically reconnect. (Makes me continue
using up mobile broadband traffic.)



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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Davide Alberelli]

Su venerdì 4 settembre 2015 12:52:53 CEST, Timo Jyrinki ha scritto:

It'd be good to debug this further, although it might be difficult.

I haven't noticed anything like described after OTA-6 upgrade two days
ago and I'm using apps / scopes on my Bq heavily.

Just from technical guesses side, might it be some app/service
crashing, apport running to collect crash data and freeze happens
during that?

You _might_ find something extra if you navigate to Settings ->
Security -> Statistics -> Earlier error reports (sorry, I'm not sure
about the English ones, I'm translating on-the-fly from my Bq) and
check the top most links. The interesting things are Date, Package
etc, plus of course the actual whole error report. It's is easier if
you manage to copy the id link to your desktop browser and do
copy-pasting error report URL:s from there.

Not everything is shown there though, if the error report can't be
submitted. Due to various factors, not all apport collected issues are
actually sent.

-Timo


I don't have access to these report,since I'm not a developer...
Can someone have a look? Because the phone is becoming unusable (even the 
keyboard is slowed down, not to talk about games and such...).


Davide




On Fri, Sep 4, 2015 at 12:16 PM, Davide Alberelli 
 wrote:

Hello list,
bq 4.5, r25.
I am experiencing some general slowness after the OTA-6 update.

This is particularly visible with freezes when scrolling in apps and when
changing between scopes (Apps -> Today <-> Near By <-> News) and when
opening apps (this is _extremely_ slower than OTA-5).

To reproduce the freeze in apps (webapps like Facebook (unofficial), or
proper apps like browser, it's the same), scroll slowly down 
the page, then

a bit faster up and then down again to go back where you where.

To reproduce in scopes just move from one to the other and/or down.

What happens, in order, is
1) freeze of the interface for some seconds (no scroll, no swipe from any
direction)
2) wait, wait...
3) unfreeze and all what you have tried in 1) is done
4) if you are on a page in the browser it goes blank, if you are on
everything else (scope, web-apps, ...) usually this results only in a big
jump around with no other harm.

It is really annoying seeing this huge regressions in user 
exeprience from

one OTA to the other :S

Any help investigating?

Davide

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








--
Inviato dal mio dispositivo Ubuntu usando Dekko

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

Re: [Ubuntu-phone] General Slowness after OTA-6 update

[Ari Börde Kröyer]

Hi

I have a BQ 4.5 upgraded to r25 two days ago and I am experiencing the 
same thing, but not affecting the exact same apps/services.


In my case it is the messaging service that is hopelessly slow. When I 
start it it takes longer than before to display the latest threads and 
additionally, I have to wait up to 10 s before the phone numbers are 
replaced by the corresponding names from the contact list.


When I tap a thread it takes at least 3 times longer than previously to 
display its contents and often the screen is blank for a few seconds first.


Every action undertaken (except typing the message) takes several 
seconds to complete!


Best regards,
Ari

Den 04. sep. 2015 11:16, skrev Davide Alberelli:

Hello list,
bq 4.5, r25.

This is particularly visible with freezes when scrolling in apps and 
when changing between scopes (Apps -> Today <-> Near By <-> News) and 
when opening apps (this is _extremely_ slower than OTA-5).


To reproduce the freeze in apps (webapps like Facebook (unofficial), 
or proper apps like browser, it's the same), scroll slowly down the 
page, then a bit faster up and then down again to go back where you where.


To reproduce in scopes just move from one to the other and/or down.

What happens, in order, is
1) freeze of the interface for some seconds (no scroll, no swipe from 
any direction)

2) wait, wait...
3) unfreeze and all what you have tried in 1) is done
4) if you are on a page in the browser it goes blank, if you are on 
everything else (scope, web-apps, ...) usually this results only in a 
big jump around with no other harm.


It is really annoying seeing this huge regressions in user exeprience 
from one OTA to the other :S


Any help investigating?

Davide




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