W dniu 03.11.2015 o 22:21, Eric Holmi pisze:
I have the same issue with the Nexus 7 2013. Could it be a hardware flaw or design for some reason?

On Tuesday, November 3, 2015, Brendan Donegan <[email protected] <mailto:[email protected]>> wrote:

    I think it's worth noting that this is a problem I have observed
    on the Nexus 4, even when it's running Android. I will find it
    off, but then be able to turn it on with plenty of battery left.
    This is probably some kind of hardware issue, the same thing could
    be happening on the BQ, maybe it shuts itself down to protect
    itself from serious faults?

    On Tue, 3 Nov 2015 at 20:09 Pat McGowan <[email protected]
    <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:

        I would just add your krillin info, suspecting its maybe an
        mtk related issue

        On Tue, Nov 3, 2015 at 2:02 PM, Olivier Tilloy
        <[email protected]
        <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:

                    I think I just saw something like that happen.
                    My phone was sitting idle at ~40% battery. Next
                    thing I know, it had turned off and I couldn’t
                    turn it back on. I plugged it into my laptop, and
                    it wouldn’t turn on immediately as if the battery
                    was too low, but the charge screen indicated that
                    it had 23% left.
                    After charging for a bit, I managed to switch it
                    on, and this is how the battery usage graph looks
                    like:


                    ​
                    Shortly before 5pm, the battery level dropped from
                    ~40% to ~20% and the phone turned off, as if it
                    had run completely out of battery. It looks like
                    something is not reporting correctly the charge level.

                    Should I file a new bug, or do we already have a
                    bug tracking this issue?


                There are a couple existing bugs, see
                
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471913
                and
                
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511977


            Both bugs seem to be arale-specific. Should I file a new
            one for krillin?


        --
        Mailing list: https://launchpad.net/~ubuntu-phone
        <https://launchpad.net/%7Eubuntu-phone>
        Post to     : [email protected]
        <javascript:_e(%7B%7D,'cvml','[email protected]');>
        Unsubscribe : https://launchpad.net/~ubuntu-phone
        <https://launchpad.net/%7Eubuntu-phone>
        More help   : https://help.launchpad.net/ListHelp



I get this all the time on the bq E5. It seems to hold its charge forever (not even decreasing 1% over hours and hours) and then drops like a stone.

The other day I picked up the phone, it quickly showed 10% charge remaining and within a minute it was through 5% remaining and turned off.

--
Dominik Wnęk

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Reply via email to