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

Terrible Battery Life on Pixel 2

Scheduled Pinned Locked Moved Google Pixel 2/2 XL
4 Posts 3 Posters 669 Views 2 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.
    • C Offline
      ckrnkfrnchmn
      last edited by 31 Oct 2022, 18:23

      Re: Pixel 2 battery life

      Just installed UBT on my old Pixel 2. I too am getting terrible battery life...maybe half if not less than what I had with Android 11 installed 😞

      UT/Pixel 3a as my daily driver an' lovin' it

      1 Reply Last reply Reply Quote 0
      • D Offline
        domubpkm
        last edited by 31 Oct 2022, 19:29

        See https://forums.ubports.com/topic/6211/howto-alternate-way-of-saving-battery-when-using-4g-lte

        1 Reply Last reply Reply Quote 1
        • S Offline
          ser
          last edited by 10 Jan 2023, 19:30

          I apologize if this is considered necro-bumping.

          Just another data point: I just installed UT on a Pixel 2, which I originally decommissioned because the USB port had become unreliable; the battery was not new when I turned it off for the last time, but not terrible.

          I installed the baseline Android, including flashing the radio image (radio-walleye-blah-blah.img), before using the ubports-installer; the installation went without errors. However, after rebooting I apparently have no wifi device. NetworkManager doesn't see one, and neither does rfkill (although, it does see bluetooth devices hc_power and hci0). I wasn't really expecting much anyway, so I set the phone aside, screen off.

          I came back a couple of hours later to show my wife Linux on a cell phone (!!!), but the phone was off. Odd, I thought, but it informed me of an empty battery, so I plugged it in and started it up again.

          I'd attach a screenshot, except I haven't figured out how to get data onto or off of the phone yet, but I'll use my fantastic art skills to paint what the battery widget showed me:

          100% |         |
               |         \
               |         |
               |         \
               |          |
               |          \
               |           |
               |            \
           0% |               |
               |-----------------------------------------
          

          This is with no WiFi device visible to Ubuntu. Maybe it was on full power madly broadcasting out radiation, and the Linux kernel just couldn't see it; I don't know, but it is funny, mainly because I don't need this device to work. It'd just be nice.

          I suppose if I really cared, I'd start a new post asking how I get the wifi working; I probably will, eventually. OTOH, if there's something I missed that I need to do to get the kernel to see the wifi device, I'd be grateful to know. I should probably look at the dmesg logs and see if anything stands out.

          I'll repeat that I did successfully flash the radio image from the Android Walleye zip prior to the installation.

          1 Reply Last reply Reply Quote 0
          • S Offline
            ser
            last edited by 10 Jan 2023, 20:01

            Update

            The issue for me, at least, is bluebinder. It sits up at the top of top consuming 154% CPU.

            I have bluetooth turned off, not that turning it on does anything.

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