UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Mysteriously powered off

    Scheduled Pinned Locked Moved Google Nexus 5
    3 Posts 2 Posters 278 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • ? Offline
        A Former User
        last edited by

        I've had no problems with my Nexus 5 (bought new three years ago), but recently I've found it powered off on a few occasions. I see that the last line in /var/log/syslog each time was for a weekly cron job, e.g.:

        Mar 7 06:47:01 ubuntu-phablet CRON[25666]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))

        /usr/sbin/anacron does not exist. /etc/cron.weekly/ contains a single script, fstrim, which invokes /sbin/fstrim.

        Does this mean there are problems with the SSD? There are 21GB free.

        Could it be something run after the cron job for which there are no syslog entries?

        I'm running OTA-13 (stable).

        Thanks.

        AppLeeA 1 Reply Last reply Reply Quote 0
        • AppLeeA Offline
          AppLee @Guest
          last edited by

          Hi @boogaloo

          If it is a recent issue with OTA13, then it's hardware related because the soft didn't change.
          It could be the battery showing end-of-life signs or a problem with the flash memory.
          Dead memory can lead to strange software crashes or behavior.

          I would say try and upgrade to OTA15, a fresh install could temporarily fix corrupted memory until new corruption arise...

          If the problem is still there it's probably the battery.

          Just my 2 cents

          ? 1 Reply Last reply Reply Quote 0
          • ? Offline
            A Former User @AppLee
            last edited by

            Thanks for the suggestions, @applee
            I hope an upgrade will solve it 🙂

            1 Reply Last reply Reply Quote 0
            • First post
              Last post