EskeRahn

I'm confused, do you by that mean the Pro1 (without the X) ?

Are you sure the commands does not require the device to be rooted, or similar? PS, they can be entered with ADB shell: adb shell setprop persist.dbg.ims_volte_enable 1; setprop persist.dbg.volte_avail_ovr 1; setprop persist.dbg.vt_avail_ovr 1; setprop persist.dbg.wfc_avail_ovr 1 (from here) (If I run the commands on AICP on the Pro1 (non-x) they are accepted, but not on the other variants I tried it )

Ah! This description reminds a lot of AISP-S that after install goes into a boot loop, and only on the seventh(!) boot actually boots, and needed TWO sort of factory reset....

(moved your post over here)

Try to make a clean installation without connecting to WiFi, and turn off WiFi as soon as you can. If it helps, at the least we know were the bug is. You could also try a clean install at a friend with a different WiFi, and see if things works better there. If so, we know that for some odd reason it does not work with your Access Point.... And you could try to fiddle with what bands it uses,

Try putting it en aeroplane mode. Some of us see issues with spontaneous reboots when the WiFi signal gets out of reach - not always but sometimes. If Aeroplane mode helps, try with only WiFi off (obviously not a solution, but to narrow it down, also use it without restoring your apps, again to narrow it down - it might be an updated app that somehow made it crash.)

This is a user-to-user forum, so the chance that your message is spotted by staff here is slim to none. Sorry.

The missing preview is because it also works from the lock-screen, where you for security reasons are not allowed to access recent photos. But indeed the auto-shoot does not seem like a very good idea, in theory it could catch a moment fast, but in practise very likely to take useless photos out of focus. Had there been an option I would turn this feature off.

Click on the user-icon and send a personal message 🙂

Install something like GSAM or 3C All-In-One Toolbox, to find what app is the culprit. The LOS by it self is pretty lean on the battery. About 0.5%/h when idle. ADD, And when in Aeroplane mode it falls to about 8%/day (And this is on a preproduction unit from the the spring 2019, with original battery)

I'm not too happy about messing with the system files, and as the numbers are the same when charging the battery works and when it does not, it is unlikely to be relevant.

It looks this way no matter if charging is working or not. So not an indicator as such. And do not get fooled by the sign. Some phones reports charging as negative (e.g. Pro1 and Samsung S8-) other reports usage as negative (e.g. Titan Slim). I see this in "3C All-In-One Toolbox", that there is disagreement on the sign between different models..

Flashed aicp_pro1_s-17.1-WEEKLY-20220907.zip on security update 2022-03-05 Seems much the same. Still initial boot-loop after flash, But that aside things seem to work.

When the bug is present: C:\Util\ADB>adb shell "grep '.*' /sys/class/power_supply/battery/*" /sys/class/power_supply/battery/capacity:85 /sys/class/power_supply/battery/charge_counter:2491300 /sys/class/power_supply/battery/charge_done:0 /sys/class/power_supply/battery/charge_full:2906000 /sys/class/power_supply/battery/charge_type:N/A /sys/class/power_supply/battery/charger_temp:296 /sys/class/power_supply/battery/charger_temp_max:812 /sys/class/power_supply/battery/constant_charge_current_max:-22000 /sys/class/power_supply/battery/current_now:-3417 /sys/class/power_supply/battery

You want to see this when the issue is there I assume? On AICP and LOS, Rooting is not needed as such. adb root adb shell "grep '.*' /sys/class/power_supply/battery/voltage_*" adb unroot returns something /sys/class/power_supply/battery/voltage_max:4400000 /sys/class/power_supply/battery/voltage_now:4204334 /sys/class/power_supply/battery/voltage_qnovo:-22 and /sys/class/power_supply/battery/voltage_max:4400000 /sys/class/power_supply/battery/voltage_now:3819082 /sys/class/power_supply/battery/voltage_qnovo:-22 on two different Pro1 The bug is not present at this m

With the dot it would be a hell of a bargain 🤣

(merged the thread https://community.fxtec.com/topic/3689-is-the-lineage-os-out-yet-for-the-x/ )

And if you look at the size of the grid the keys are in (that is including the space between the keys) it is roughly 6x9.6mm They Slim's keys are neck to neck sidewise. They are 6x6.2mm in a 7x6.2mm grid, so slightly higher grid, though the width is 35-36% less on the Slim. The typing experience is quite different though. On one Hand you can write a-z and space text with one hand on the Slim, with no punctuation or national letters or other symbols. The Pro1/Pro1X gives a much more 'normal' typing experience, BUT is really awkward to type on with one hand only, while keeping some sort of

Pro1X, not the old Pro1 I deduce from the memory numbers 🙂 Too bad it is not for you. Hope it will find a new owner soon.

Try "Fastboot devices". If the phone is in fastboot mode it should return an Id Fastboot is generally more 'picky' on the port&cable combination. Does ADB work? (slightly less picky) If not, it could be driver, could be port, could be cable.... When I got a new PC, it did not work at all, with any port or any cable I had. but going through a hub things worked....

Here they are next to each other.... (sorry for the dust, and sloppy focussing)

Indeed, thanks, forgot that aspect, it can be really slow for the initial fix.

Assuming it is not some software interfering with the functionality, my guess would be the connection to the antenna. So first guess would be a factory reset, and if the bug is still there, you would need to contact FxTec.

It would be nice for other readers if the title included Pro1X or Pro1

I have been requesting that as well....