Jump to content

marmistrz

Members
  • Content Count

    58
  • Joined

  • Last visited

  • Days Won

    1

marmistrz last won the day on June 17

marmistrz had the most liked content!

Community Reputation

35 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. tdm, could we possibly have both drivers in the lineage kernel and be able to choose between them without rebuilding the kernel (possibly requiring root)? I'm thinking about a way to adapt the keyboard layout to fit the Polish language and I'll almost certainly will need to somehow remap some fn+something combo. Probably I'd want to use fn+a as altgr+a but keep fn+l as it is. There might be other languages for which a dead fn key causes trouble.
  2. What's the purpose of the changes in the "Add keylogger" commit? https://github.com/tdm/android_kernel_fxtec_msm8998/commit/b03a10e872bc451e7300a1d5ed93204f3c3468b1
  3. @tdm is there a technical reason for that or is it just a bug?
  4. No, but I assumed internal storage should work equally well (when soneone says sdcard in the context of Android, I often think /sdcard, which is often mapped to the internal storage)
  5. Does LineageOS recovery allow flashing zips from sdcard? I didn't see such an option anywhere and I thought only sideload is possible.
  6. I tried OTA with 20200914 and again a softbrick, using the `adb sideload` method unbricked the device. I'm wondering about the root cause. One hypothesis is that I wrote /system. I followed this guide of mine to install the F-Droid Privileged Extension. Touching /system in any way will break OTAs on stock, and I'm wondering if the same may be the case for LineageOS. Saying "just don't write system" is not a solution, because it's impossible to modify /etc/hosts without writing /system 🙂
  7. Is the 20200831 OTA safe to install? there was a lot of trouble with 20200824 (system not booting), wondering if anyone had similar issues with 20200831 Or should I just flash the update with adb sideload?
  8. As for GPS, yesterday I tried to get a cold fix while traveling in a car and it took about 20 minutes, even though there were roughly 12 satellites visible all the time. It was in Poland. Today it was much better and it the fix was almost instant. Looks like under some circumstances the GPS fix is terribly slow.
  9. I tried switching in fastboot and it didn't work. I ended up wiping data 😞
  10. There is certainly a hardware issue with my device. After long time of usage I noticed spontaneous key events for keys that I didn't even touch. Looks like the keyboard is short-circuiting. I'd send it back for warranty, but since people have waited 7 months for the replacement, I'm a little afraid to send it back for warranty until they finish the pre-orders. Btw. I also have issues with the USB-C port disconnecting while moving the cable slightly and suspicions of hardware issues with the camera sensor (remaining glue or other dirt in the camera unit)
  11. Same here, no gapps at all. I tried downgrading (unsupported, I know), but the recovery doesn't accept sideloading in either case (both 20200803 and 20200824). I'm simply getting adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found
  12. As for autocapitalization, it seems to be some high-level mechanism. I noticed that when I'm writing im in the Messaging app, it's automatically corrected to I'm, even when I'm using Polish for both hardware and software keyboard. This doesn't happen in some other apps, such as Conversations. Btw. it appears that on my old OnePlus 3 running LineageOS 14.1 there's an option for autocapitalization when I plug a USB keyboard, however, this option does nothing. There's no such option on LineageOS 16.0 on the Pro1.
  13. Could you please provide instructions for updates from test22 to official in the OP? It was discussed somewhere, but I don't remember what the conclusion was
  14. I managed to fix the problems with GPS by clearing all caches. Now I'm getting a fix within 5-10s, GPS, GLONASS and Beidou is used. # rm -rf /data/cache # rm -rf /data/dalvik-cache
×
×
  • Create New...

Important Information

Terms