Jump to content

Wheeljack

Members
  • Content Count

    169
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by Wheeljack

  1. Still not incremental but definitely faster than with LOS 16.
  2. Also worked fine via OTA with GApps and Magisk installed. Had some hopes for the HAL qcom_audio fixes in the changelog, but they don't affect my car/bluetooth issues.
  3. I'm on Lineage and sticky shift works more on an app by app basis. WhatsApp, Messenger, Firefox, Discord... they all work fine with sticky shift. But then I write a mail in GMail and suddenly I have to hold down shift again to get the next keypress to be upper case.
  4. You have an SD card inserted? Is it still recognized? Maybe the missing apps were installed on external storage?
  5. I'm now finally on the waiting list for the next batch of replacement displays heading to London.
  6. When installing GApps it needs to be tailored for the installed Android version. Since MindTheGApps hasn't been updated in a while and there is no package for Android 10, we have to go with OpenGApps. I followed the official upgrade guide (which for some reason uses "adb reboot sideload" to skip that one button press in recovery). After flashing Lineage and rebootinga1g into the new recovery, I flashed OpenGapps Nano - from the package description it sounded the closest to what MTG included. And if you previously had OpenGApps installed, there should be no trouble, if you accidentally cho
  7. OTA update 20201116 installed gracefully and pretty fast.
  8. Step 6 says to reboot to recovery. This is where the slots are switched (active slot is set during LOS sideload but the change takes effect, when the device reboots). And while we're on the subject of not finding settings... on LOS 16 I had deactivated my second SIM card in slot 2. Now I can't find where to activate it and the status bar lists one of the two networks with an X for no connection.
  9. I will probably earn a blacklist entry for all Lineage support but: I did a dirty flash from LOS 16.0 with MindTheGapps to LOS 17.1 with OpenGapps Nano. And the phone still works 😄 Just had to replace the cLock widget with another clock widget (as already mentioned in post #2).
  10. I'm only seeing the 17.1 build in the queue for today. I don't know if there were cases where 16 and 17 builds for the same device were run side by side. On another note... I'm running 16.0 with MindTheGapps. What are my options when upgrading to 17.1 (since OpenGapps is recommended now)?
  11. I've asked in the Lineage reddit, what happened to the monday builds. Something seems to be borked with the scheduler snce there were no builds at all this and last Monday.
  12. Looks like there weren't any builds scheduled for last night on buildkite. So not even a new LOS 16 build today.
  13. No new answer from support yet. I'm starting to wonder if my pictures even arrived. Can't even ask or else I'll move at the end of the queue again.
  14. A friend of mine printed the case and the first version of the bumper for me with 20% infill using PLA+. The bottom fits like a glove. The bumper is a bit too tight and the tension constantly makes it jump off. But you already knew that. 😉 I'll try to shave a bit of material off before I ask him to print one of the updated versions.
  15. I can relate. There seem to be some BT issues especially with cars of the VW group. Both my Audi A1 and my parents' VW Golf act the same with the Pro1. No matter if I connect the phone before or during a call - the audio still goes through the phones speaker and mic (switching the audio source to handset and back to bluetooth doesn't help either). My Sennheiser PXC 550 II BT headset once worked completely fine. At some point though an update must have introduced a new bug though. I have to connect the headset during a call now for it to catch the audio. If it's connected before the call t
  16. Tap "Android-Version 9" in the About phone screen.
  17. Installed lineage-16.0-20201026-nightly-pro1-signed via OTA. Phone still in working condition, nothing unusual to report 😉
  18. Got an answer from support today asking for a couple more pictures of my phone. Was probably overthinking if I should reduce JPEG quality for filesize or send the hires original. Sent the original sizes using several mails anyway. 😅
  19. Yeah, finally got around to send a mail regarding my device their way, video included. That was last wednesday. Aside from the automated Zendesk response I haven't heard from support yet.
  20. Also testing kbd-3 here on my QWERTZ. While button mashing I ran into the issue again where the keyboard completely locks up (save for the Alt key) - so I tried to reproduce it... As far as I see, you can trigger this by pressing two keys at exactly the same time. I managed to lock the keyboard up after just a few tries with X+D or W+S with my big enough left thumb.
  21. Just get the boot image from here. (Just make sure it's the one matching your currently installed version)
  22. I tried it for 10 minutes and it looked responsive to me but I couldn't figure out how to set it to QWERTZ so I went back to the Lineage bootloader. In my case Alt still gives me the emoji popup when that happens.
  23. I once had an issue with my charger that would only charge devices at slow speeds. Turned out I hadn't inserted the USB A connector all the way. Do you have the Pro1 in a case maybe?
×
×
  • Create New...

Important Information

Terms