Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Wheeljack

  1. lineage_pro1-userdebug 14 AP1A.240405.002.A1 55d8b5678d My Pebble is connecting all by itself again!
  2. 21-20240420-NIGHTLY-pro1 installed smoothly via OTA, I've installed Magisk before reboot to make sure it stays rooted. Didn't notice anything new though.
  3. Can confirm. With a bit of fiddling around, putting my Pebble into pairing mode and reconnecting through the Pebble app (or should I call it Rebble app now?) I get a popup for a pairing request every minute or so. Eventually I am lucky and the pairing is successful and stable until I put too much distance between watch and phone. They won't automatically reconnect.
  4. OTA update 20240413 went through without a hitch. First thing I noticed after updating: My preferred SIM card for data, calls, and text is still set. NICE!
  5. According to a reddit thread all LOS21 builds are currently on hold until they get Google's new QPR2 features implemented.
  6. OTA went fine here. I just noticed that Magisk got kicked - on LOS20 it was auto-patching the boot image. Will have to remember to manually patch before rebooting in future OTA updates. When I flashed LOS 21 for the first time last week I noticed the installer had a convenient "reboot to recovery" popup after flashing for other installers like GAPPS that target the currently active system partition.
  7. Yeah, I also keep whipping out that one old laptop where I know I installed the drivers and minimal adb and fastboot properly whenever I want to flash my phone. Did the update yesterday and was busy getting my Pebble watch back running as pretty much anyone who upgraded to Android 14 before me. Since I've pretty much given up hope on every seeing hands-free working with the Pro1 in my car, I wasn't surprised when it still didn't work. I think it actually got worse as the connection now drops and reconnects every 15 seconds or so causing the music in my radio to restart during a call
  8. Kinda reassuring that I'm not alone with this. Had to open up my Pro1 to replace the bulging battery today (screen was already a bit wobbly and no longer flush when closed). While reassembling I ripped the fingerprint cable apart. I don't even know how I'm supposed to put it back in place while also holding both sides of the lower shell. If I get a replacement, I'll probably destroy that one, too. Phone is charging and properly closing again at least. Battery was still at 47% despite having a manufacturing date of mid 2019.
  9. Installed 20-20231216-NIGHTLY-pro1 last night via OTA. Running fine so far.
  10. You ever been in an updating mood and think about to hit the "update all" button in the Google Play Store while the OTA update is running? Yeah, don't do that. Sometimes the Play Store updates cause my UI to crash and restart. And yesterday this happened while I had the OTA update running. The bootloader already pointed to the unfinished system partition and I couldn't start my phone until I switched back to boot_a using fastboot. Other than that.. latest OTA is working fine now after my second attempt 😅
  11. This has been driving me nuts for months now. When I wake up my phone with th fingerprint sensor, it takes a couple of seconds until it responds to further inputs. If I wake it up via power button I can unlock it using finger print and use it right away.
  12. So glad the Pro1 is a A/B device. After OTA updating and applying Magisk-Delta as every week I rebooted and then the touchscreen would no longer accept inputs. I could navigate the reboot menu with the PWR, Tab and Enter buttons, enter my SIM pins, but I couldn't get past my lock screen. Went to fastboot mode and switched to the version from previous week (slot b in y case). Will try again if you guys down't have problems. For reference: fastboot set_active b
  13. OTA update 20230424 is live and installed without problems for me.
  14. Looks like today's build has crashed (log) Unless it's rescheduled, we'll have to wait another week.
  15. According to the buildkite logs, the scheduled build simply crashed and wasn't re-scheduled. This weeks 20230327 update has finished though. Already have it running on my Pro1. OTA went through without issues.
  16. Running the OTA updater right now. Had some issues starting the update because the updater kept crashing when I hit "Install". Fixed it by going to Settings -> Apps -> Show System Apps and deleting the Updater's app data.
  17. This has been annoying me since LOS 16. My Pro1 has never properly worked with my Audi MMI and my parents' VW Golf. Will test ASAP. Edit: Nope. Sadly I still don't get telephone audio though my car stereo.
  18. Dirty flashed the Jan 02 release yesterday. So far everything is still working. I have a feeling that multi-touch isn't working properly in Mario Kart Tour, though I can properly pinch and zoom my photos in the gallery. Launcher is laggy from time to time - sometimes takes a few seconds to react to any input. Pebble users have to reinitialize the app to be able to pair their watch again - but that seems to be a general issue when upgrading to Android 13. Spend most of my time yesterday to get this working again. The SIM pin issue when using two SIMs seems to be fixed. When the screen
  19. Today's build has been cooking for over 12 hours. Guess it's stuck. https://buildkite.com/lineageos/android/builds/50476
  20. Okay, so what I can gather from your replies so far is that the GaN chargers in the wild do at least act differently on the Pro1. So it's not just one board manufacturer supplying all these different brands (despite lots of chargers looking very alike). Gotta charge my Pro1 in tandem with something else for now since even a reboot while plugged in as the only device doesn't help. Haven't tested offline charging yet though.
  21. So I replaced my older charging brick in the charging corner with a new one supporting USB-C PD at up to 65W split to 4 ports (2 USB-C, 2 USB-A). This one to be precise. Now I'm wondering, if anyone else here has one of these newer GaN3-tech chargers and if they have the same issues. I mean that thing charges my laptop, Steam Deck, Switch, Moto G phones without problems. But when I plug in the Pro1 as the only device they agree on the lowest possible charging rate possible - draining the battery further instead of charging (and that's not even the Lineage charging bug - this also happens
  22. Okay... so I'm on my third screen right now and it's still behaving after a few months. I'm starting to suspect the culprit that damaged the first two screens may have been a phone case I've attached to the keyboard half of the device. When closing the phone with a rubber sleeve or a 3d printed hard shell attached to the bottom part (I had both) the screen might not fully close and allow a bit of flex to the screen half when carrying it in a pocket. I've been running the phone naked since installing the third screen and like already mentioned I don't have any problems so far. Ju
  23. This reminded me: whatever happened to split screen since 19.1?
  24. Are your SIMs pin-protected? Like I wrote in a previous post my two SIMs act a little different after boot. When I proceed to enter both pins right when the phone asks they're both active right away. If I let the screen timeout before that, the phone gets stuck until I manually press the power button twice. I also have deactivated WiFi calling for SIM1. SIM1 is my default one for outgoing calls but when I remotely initiate a call using my helmet's hands-free it would go over SIM2 - it finally started using SIM1 when WiFi calling was off (no idea if my provider supports this anyway).
  25. 1. I have an issue with my display. When I restart the Pro1 or press the power key immediately after shutting it down, the display won't come on. Any attempt to "reboot into recovery" results in me flying blind (keyboard is lit and I can still feel the options when pressing vol-up and -down. When rebooting into system I have to tap the power button two or three times until the sim pin screen shows up. Almost send an emergency call once while trying to get the display on. I'll have to see if this is another display firmware issue - I still have the previous defective unit here. 2
  • Create New...

Important Information