El jueves, 2 de julio de 2015 18:48:49 (CEST), Andrea Bernabei escribió:
Have you tried entering recovery mode (upvol + pwr then select recovery on
BQ), and then rebooting to normal mode?
Give it a spin
I pressed Vol- & power, Vol+ & power and Vol-+ & power; no reaction
People should at le
Have you tried entering recovery mode (upvol + pwr then select recovery on
BQ), and then rebooting to normal mode?
Give it a spin
On Wed, Jul 1, 2015 at 8:29 PM, Christian Dywan <
christian.dy...@canonical.com> wrote:
> As I just experienced this I can confirm there's a chance you get stuck
> lo
As I just experienced this I can confirm there's a chance you get stuck
looking at an Ubuntu logo and keeping power and down pressed far longer
than you would deem sensible did get me out of it eventually.
Whatever caused it I don't know, as I'm still fighting to make my phone
boot again when
hi,
Am Montag, den 22.06.2015, 22:06 +0200 schrieb Marco F:
>
> >> Who decided that collection of debug information is the task with highest
> >> priority on a phone which wishes to be used by the public?
> >>
> > i think it already runs at a very low prio (obviously still to high for
> > the pho
> From: o...@ubuntu.com
> To: ubuntu-phone@lists.launchpad.net
> Date: Mon, 22 Jun 2015 14:39:04 +0200
> Subject: Re: [Ubuntu-phone] BQ r23 total off and unwilling to react
>
> hi,
> Am Montag, den 22.06.2015, 14:28 +0200 schrieb Marc
On Mon, 22 Jun 2015, Oliver Grawert wrote:
Am Montag, den 22.06.2015, 20:21 +0200 schrieb Torsten Sachse:
On Mon, 22 Jun 2015, Steve Langasek wrote:
> The only part that should be running when not on wifi is the crash
> collection. We certainly *should* be running that when not on
> wifi; you d
hi,
Am Montag, den 22.06.2015, 11:44 -0700 schrieb Steve Langasek:
>
> > Thanks for the explanation. To me, this is just all the more reason to
> > have an option to disable it, maybe only for a day or a couple. Imagine
> > being somewhere and urgently needing your phone which then hangs becaus
hi,
Am Montag, den 22.06.2015, 20:21 +0200 schrieb Torsten Sachse:
> On Mon, 22 Jun 2015, Steve Langasek wrote:
> > The only part that should be running when not on wifi is the crash
> > collection. We certainly *should* be running that when not on wifi; you
> > don't get a second chance to run t
On Mon, Jun 22, 2015 at 08:21:44PM +0200, Torsten Sachse wrote:
> On Mon, 22 Jun 2015, Steve Langasek wrote:
> >The only part that should be running when not on wifi is the crash
> >collection. We certainly *should* be running that when not on wifi; you
> >don't get a second chance to run the kern
On Mon, 22 Jun 2015, Steve Langasek wrote:
The only part that should be running when not on wifi is the crash
collection. We certainly *should* be running that when not on wifi; you
don't get a second chance to run the kernel crash handler, and we want to
know about crashes that only happen when
On Mon, Jun 22, 2015 at 02:48:01PM +0200, Oliver Grawert wrote:
> seems that whoopsie refuses to send your report because you are not on
> wifi, perhaps it should check for this earlier and not even run the
> collection, not sure ...
The only part that should be running when not on wifi is the cr
El día Monday, June 22, 2015 a las 02:19:10PM +0100, Alan Pope escribió:
> On 22 June 2015 at 13:57, Matthias Apitz wrote:
> > And btw: I already switched off this sending to Canonical, but magic: it
> > turns on again from time to time.
> >
>
> That sounds like this bug:-
> https://bugs.launchp
On 22.06.2015 14:57, Matthias Apitz wrote:
> As I said, the beast came up again to life after connecting it to USB.
> Let's say, I do not have any netbook in such a moment, what is the
> procedure to do a reset-reboot?
Keep the power button pressed for > 10 secs. Usually that makes it turn
off
El día Monday, June 22, 2015 a las 03:05:33PM +0200, Michael Zanetti escribió:
> Keep the power button pressed for > 10 secs. Usually that makes it turn
> off and you should be able to turn it on again.
I did this for more than 20 secs - no reaction;
>
> However, I do have seen a state once whe
On 22 June 2015 at 13:57, Matthias Apitz wrote:
> And btw: I already switched off this sending to Canonical, but magic: it
> turns on again from time to time.
>
That sounds like this bug:-
https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1437633
Also, related to the discussion
On Mon, Jun 22, 2015 at 02:57:38PM +0200, Matthias Apitz wrote:
> El día Monday, June 22, 2015 a las 02:48:01PM +0200, Oliver Grawert escribió:
> > seems that whoopsie refuses to send your report because you are not on
> > wifi, perhaps it should check for this earlier and not even run the
> > coll
El día Monday, June 22, 2015 a las 02:48:01PM +0200, Oliver Grawert escribió:
> > # cat /var/log/upstart/whoopsie.log
> > ...
> > [13:16:10] Network connection may be a paid data plan:
> > /org/freedesktop/NetworkManager/Devices/8
> ...
> > I was highly concerned about the bricket phone.
> >
> >
hi,
Am Montag, den 22.06.2015, 14:36 +0200 schrieb Matthias Apitz:
>
> root@ubuntu-phablet:/var/crash# ls -ltr /var/log/apport.log*
...
> ERROR: apport (pid 6061) Mon Jun 22 13:06:25 2015: apport: report
> /var/crash/_opt_click.ubuntu.com_dekko.dekkoproject_0.5.2_lib_arm-linux-gnueabihf_bin_dekk
hi,
Am Montag, den 22.06.2015, 14:28 +0200 schrieb Marco F:
> Who decided that collection of debug information is the task with highest
> priority on a phone which wishes to be used by the public?
>
i think it already runs at a very low prio (obviously still to high for
the phone though ... )
yo
El día Monday, June 22, 2015 a las 01:49:36PM +0200, Oliver Grawert escribió:
> hi,
> Am Montag, den 22.06.2015, 13:29 +0200 schrieb Oliver Grawert:
> > an unresponsive UI is often the result of the system collecting crash
> > info, have a look in /var/crash if you find .crash files matching the
>
> - the UI was not responsive anymore
> - I pressed long (10++ secs) the power button, phone went dark without asking
> the normal question if I really want to shutdown
> - after this, it did not react anymore on any press, also not
> on volume+ and power-button
>
> I connected the phone to USB and
hi,
Am Montag, den 22.06.2015, 13:29 +0200 schrieb Oliver Grawert:
> an unresponsive UI is often the result of the system collecting crash
> info, have a look in /var/crash if you find .crash files matching the
> time of the incident ...
oh, and i forgot to mention, the crash collection logs what
hi,
Am Montag, den 22.06.2015, 13:22 +0200 schrieb Matthias Apitz:
> Hello,
>
> I have had today the following situation:
>
> - I started Dekko and its screen came up
> - the UI was not responsive anymore
> - I pressed long (10++ secs) the power button, phone went dark without asking
> the norm
23 matches
Mail list logo
