Jump to content

EskeRahn

Keymaster
  • Content Count

    5,937
  • Joined

  • Last visited

  • Days Won

    406

Posts posted by EskeRahn

  1. At 03 I finished recharging after installing the 0503 with MTG, with only very few apps, and restricted all I can, and in just 4h11m it has eaten 31%, so there IS an issue - sorry.

    I will flash back to 22.1 (dirty, and if needed with a Factory reset, and recreate)
    I flashed back to 22.1 (0405) with a factory reset and will recreate.
     

    Screenshot_20250512-082725_GSam Battery Monitor Pro.png

    Screenshot_20250512-082753_Trebuchet.png

    • Thanks 1
  2. I HOPE that I sometimes in the following week will have verified that all from the original Pro1 that can be transferred has been, so I can install LineageOS 22.2 on it freshly reset, and I will be sure to install the same 0503 version reported on above, to rule out that anything that had issues has been fixed. (But no promise I will find time for it)

    • Like 1
  3. USUALLY the problems people experiences with fastboot is related to the communication with the watch.
    Either cable, port or driver.
    Silly as it may sound on Windows11, a 'newer' USB3 port might cause problems. On my Lenovo X1 Yoga gen 6 (20XY), I can not get fastboot to work directly. But if I use an old usb2 hub, things works fine. It also works fine if I go via my thunderbolt 4 docking, and a USB3 port on that.

    AFAIK, there are fewer issues if the machine is on LINUX.

    You might also try from an old PC with USB2 ports only.

    Usually it is not super picky on the cable, but try swapping that also if a different port does not help. And then finally the more complex is that not all drivers works equally well, and that can be a hassle.

    (Note that on my pc, a direct cable works fine with ADB or with file-transfer, it is fastboot that is quite picky) - my guess would be a handshaking issue in fastboot for Windows, where it fails if it gets the answer too fast)

    • Like 2
  4. Hmm, not in my case. It worked fine on 22.1, and now works fine back on latest stock android.

    Though I will not rule out if Lineage got the calibration wrong, and thought it was at 100% when it was not, and thus did not use the full span - I highly doubt it though.

    Much more likely that 'something' in the system got confused on the dirty flashing from 22.1 to 22.2 (or maybe rudiments from earlier dirty flashing, that kicked in going to 22.2) I really ought to have made a factory reset while on 22.2, to test before going to stock, but well I did not....
    But anyone else seeing the bug, I would strongly recommend to try a factory reset (after suitable backups obviously)

    • Thanks 2
  5. Well I'm now off the LineageOS wagon for a while, at the least until I get all transferred, a lot is omitted by google on transfer. Several important apps .... 😠

    Note that I did NOT do a factory reset going from 22.1 to 22.2, so that MIGHT be the issue, and obviously would be the first to try for a support ticket.....

    • Like 1
  6. (lineage-22.2-20250503-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511)

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.
    I have no idea whether the draining issue has been improved/fixed.
    Add: The draining issue is still there. From 100% to 18% in 11h, idle screen off, will recharge and turn off...

    • Like 2
  7. ...tried again with both long press Power+VolDown hold to recovery menu and very-long-power press deep boot.
    And yet it is down from 100% to 90% in less than an hour...

    ADD:
    F
    rom 100% to 50% in ten hours. So horrible, but at the least slightly flattening out from the initial worse than 10% per hour....

    ADD II:
    From 100% to 20% in 14 hours. 🙄

    • Like 1
    • Thanks 1
  8. 3 hours ago, Hook said:

    However, now I need to try it with my Pro 1, which I haven't used much for a couple of weeks.

    Hmm I already did a very-long-power press deep boot, to no avail. I did not try the Power+VolDown hold, but did that just now, so will report back with any difference, though I highly doubt it. It seems like something with the significant motion detection not being deactivated when locked. Maybe some silly fitness crap that I forgot to disable, or the upgrade enabled??

    • Like 1
    • Thanks 1
  9. 23 hours ago, EskeRahn said:

    Unfortunately I see no entries in the changelog that seems to address the power-wasting issue. But keep my fingers crossed...🤞

    I can confirm the issue is their with yesterdays version also. 95% to 65% in just 4½h idle, screen off 'all' apps killed
    According to GSAM, it kept the Significant Motion Detector active for the full period, and I got no raise-to-wake or the like activated.

    ADD: 95% to 15% in just 13h !!! idle, screen off 'all' apps killed. When it has been recharged, I will turn it off and hope for better luck with next update... 😢

  10. (lineage-22.2-20250426-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511)

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

    Unfortunately I see no entries in the changelog that seems to address the power-wasting issue. But keep my fingers crossed...🤞

    • Like 2
  11. 15 hours ago, EskeRahn said:

    ...And today download.lineageos.org/ seems down...

    Interestingly, all reports OK here status.lineageos.org but still both manual download and OTA seems down??
    Their recent history reports short bursts of outage, but is seems to have been continuously down for about a day.
    ...But strictly speaking you could say that it is not an outage as the page technically is answering It is just that it is not working and all direct device references go to the same page:
    Unable to contact upstream API

    ADD: They are back up 🙂

    • Thanks 1
  12. I see a VERY horrible stamina after the 22.2 updates!!!
    It usually last for about four days on a charge, now it depletes over night (95% to 23% in 14 hours while idle on a table with display off, AND all user apps killed with Greenify as usual)
    It MIGHT be related to "Significant motion detector", But I would strongly recommend to avoid upgrading currently.

    • Thanks 1
  13. 13 hours ago, Hook said:

    I don't really understand what mirrorbits is or what it's advantages are (even after reading their Github, lol), but Saturday's Pro1 update downloads just fine from the official Lineage download sites. Just FYI for folks.

    Maybe they use different regional mirrors, but it does not work here from their official site, that points to
    https://mirrorbits.lineageos.org/full/pro1/20250419/lineage-22.2-20250419-nightly-pro1-signed.zip
    that then reroutes to thepage that is (still) down

×
×
  • Create New...

Important Information

Terms