marmistrz

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.

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

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

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.

int thanks. I was confused by the fact that their webpage still mentions the IMX363: https://fxtec.com/pro1x

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?

Sounds plausible. I left the phone overnight at 63% and plugged in (but not really charging) and it remained precisely at 63%

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.

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)

I can charge in the LOS recovery, so it's limited to chaging in LOS.

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

/sys/class/power_supply # cat battery/status Not charging

it's definitely done in software as it depends on the app used

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)

Thanks. My point is that while I want sticky modifiers, i don't want autocapitalization 🙂 so switching back to full doesn't do the trick

There is but it doesn't provide any autocapitalization setting

I'm using anysoftkeyboard as my virtual kbd and have autocapitalization turned off there. sentences are not autocapitalized when using the virtual kbd but the are while using the hw kbd

For me, the biggest annoyance of the Pro1 keyboard is that it's impossible to turn off autocapitalization. Some time ago I took a quick look at the sources but I didn't find the root cause. This seems to be done by the Android userspace. Did anyone find a root cause or a workaround?

I agree, PLA is completely unsuitable for printing the case. My PLA case broke after a month of usage without taking any large hits.

I can no longer notice this issue after the latest update, however, I have never let my battery discharge below 42%.

Since recently I have a problem with charging: the device doesn't charge until rebooted. More precisely, when I plug the device to a wall charger, the current used stays around 0A, as reported by BatteryBot Pro. When I reboot, I properly get 1.5A-3A of current from the charger, depending on the actual charger used (I tested using the official charger and an Anker charger)

Oh, so it looks like they backported the screenshot tile. But I must admit I prefer the power menu from 17.0, or actually the one from Nougat! 😉 Looks like waiting a couple of weeks before they backport all the stuff is a good heuristic! Thanks for sharing!

It looks like bottom v4 already contains the fix that I wanted to do. I'll print it within several weeks and report. Meanwhile, these are the photos of my previous print. Because the mini-jack socket was partially covered by the case, I used some pliers to cut out the covering surface. Another thing that didn't go quite well is the upper part of the bottom case - I only used supports on the build plate and I should've also used them inside, so the upper rim is a little frayed - but it holds well enough. The case was also battle-tested for the first time, the phone once fell screen do

I mean the editable model. For instance if you're using Autodesk Fusion, it would be the .f3d file

Would you mind sharing the sources? I have issues with the shape of the headphones holes, which is partially covering the mini jack socket, and I'd like to tinker with it and try to fix it myself. Thanks! I'll upload my photos in a while btw.