Jump to content

marmistrz

Members
  • Content Count

    111
  • Joined

  • Last visited

  • Days Won

    2

marmistrz last won the day on May 21 2021

marmistrz had the most liked content!

Community Reputation

69 Excellent

Recent Profile Visitors

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

  1. I created an issue: https://gitlab.com/LineageOS/issues/android/-/issues/4841
  2. I did a full reflash and I still have trouble with dual SIM. Only one of my SIM is detected by the device after reboot. If I reinsert the SIM tray while the device is running, both cards are detected properly and displayed in the UI. This means that the secondary SIM is always used for mobile data, etc. What's even more interesting, I can receive the calls from the non-detected SIM. Does anyone still have the image lineage-18.1-20220425-nightly-pro1-signed.zip? Dual SIM is currently crucial for me and 19.1 is broken in this aspect.
  3. Does anyone still have a copy of lineage-18.1-20220425-nightly-pro1-signed.zip? Dual SIM support seems to be broken in 19.1, I need to revert to 18.1
  4. Yeah, I guess so. I have more fundamental issues than the broken UI after the upgrade. After the reboot, only my secondary SIM is detected. I need to reinsert the SIM tray so that both SIM cards are detected. Moreover, after I boot the device, there is no information It looks like the system configuration is not properly picked up by the new release. The large UI was due to the system picking some absurd font size. My home screen configuration (widgets and shortcuts) were gone. /edit: clearing the data for phone seems to fix the data issue at the very least - but given the numbe
  5. Sorry for the rant. Oh my goodness, LineageOS 19.1 is such a downgrade compared to 18.1. The whole UI is so gaudy: the icons, the animations. The large UI widgets that are everywhere resemble a UI I'd build (with all due to respect) for an elderly person with a hindered eyesight. This reminds my why I hate Android. On a proper Linux distro, I'd just install a different DE of my choice.
  6. int thanks. I was confused by the fact that their webpage still mentions the IMX363: https://fxtec.com/pro1x
  7. I remember reading somewhere that the Pro1x was supposed to have a massive camera upgrade (to a 48MP sensor) but I can't find it on fxtec.com. Was the plan eventually abandoned?
  8. Sounds plausible. I left the phone overnight at 63% and plugged in (but not really charging) and it remained precisely at 63%
  9. I'm on the Nov 15 update right now, I'm connected to my display using a USB-C hub and an HDMI cable and it works much more reliably than before. I used to get random disconnections and now it works like charm.
  10. Oh my goodness, I didn't realize I had the ACC daemon running! 😄🤦‍♂️ (the app had reported an error while finalizing installation so I thought it wasn't)
  11. I can charge in the LOS recovery, so it's limited to chaging in LOS.
  12. Right now I have a more serious problem: the device stops charging several minutes after a reboot. The only related thing in the logcat is: 08-29 11:49:16.367 1386 1454 I DreamManagerService: Gently waking up from dream. 08-29 11:49:16.367 1386 1419 I DreamManagerService: Performing gentle wake from dream. 08-29 11:49:15.708 0 0 W healthd : battery l=75 v=4135 t=30.0 h=2 st=3 c=429198 fc=2878000 cc=4 chg= 08-29 11:49:15.748 0 0 E i2c-msm-v2 c17a000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:4) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d
  13. /sys/class/power_supply # cat battery/status Not charging
  14. it's definitely done in software as it depends on the app used
  15. I switched to the AOSP keyboard, turned off the autocapitalization. the software keyboard doesn't autocapitalize, the hardware one does (tested by writing an e-mail in k9 mail)
×
×
  • Create New...

Important Information

Terms