claude0001

2.1.5-GMS-less also here. And the problem is definitely there. So whatever fix they prepare, it's not in that ROM.

Well, let's say they are not "apparent" during normal usage. But @Rob. S. is specifically using advanced tools to monitor the charging process. I guess, otherwise he would also not notice this. Might be somethign else in the end, but especially the fact that the current decreases towards the end of the charge is pretty normal, I think. I see that also when charging my Pro1 using my solar-panel charger (which includes a built-in current gauge).

As far as I know, there is a switch from current-control (i.e. constant charging current) to voltage-control (constant charging voltage) at some point during the charge, which leads to a decreasing current as the charge reaches its maximum value. I thought that was standard for any Li-ion battery.

There is an unofficial website that keeps track of all LOS versions no longer available at lineageos.org: https://lineageosroms.com/pro1/ Haven't used it and don't know how reliable they are. But if the code is signed ...

Before we tear our phones apart any further it would be good to know whether F(x)tec are indeed aware of this problem and are planning a fix via firmware update. The (initial) October update can be interpreted in that way, but the wording is quite vague ...

I use my Pro1 as daily driver with my self-built LineageOS 16.0 and a Debian 10 (actually Devuan 3) desktop GNU/Linux system running permanently in a chroot. For me this is the optimal combination of an Android(-like) environment with the option to do serious (desktop) work from the GNU chroot. Of course, running a more native GNU/Linux system (if we agree on calling libhybris-based hacks "native" 😉 ) like UbuntuTouch, Sailfish, or Droidian is tempting, but -- realistically -- I cannot make it through the day without some Android apps I would not know how to replace (Firefox, Zoom, Öffi,

@IMD seems to be absolutely right. The speaker failures occur only when /sys/class/power_supply/battery/voltage_now exceeds approx. 4100000 µV. This explains naturally why the phenomenon is more apparent when connected to a charger. The question remains whether F(x)tec will indeed be able to fix this by a firmware update, or not ... 😞

So I did open the phone yesterday and could not fix the issue using @spam71's recipe. I fiddled a lot with the spring contacts to the speaker, even while playing music through it: The problem seems to be independent of the electrical contact. The popping does seem to come and go also in my case. Sometimes the speaker works at all volume levels, sometimes only at highest gain. I will test if there is a correlation with the level of the battery charge. Thanks for the hint @IMD.

Consider that, concerning non-working sensors, the recommendation to do a full backup of the original Android system is largely obsoleted by the latest edit of the OP of this thread: Concerning your connection troubles, I can only recommend to try different (USB) hardware. I ended up doing all my adb/fastboot business from a Raspberry Pi3 as my Thinkpads are seemingly to "advanced" for the purpose ...

I think it is unlikely you damaged anything. As you probably know, the A and B slots are a kind of safety net that (among others) allows the device to keep the previously running OS "in reserve" whenever an update is installed. The active slot basically flips between A and B everytime a new ROM is flashed. So whether A or B is the "right" one for installing Magisk simply depends on the number of previous flashings being even or odd.

For the record: @Casey's instructions did work for me. It automagically flashed the right slot, which I think was "b" in my case.

Well, the OP wonders why, obviously, the PSU and the Pro1 cannot agree on any charging protocol, which is strange indeed. Depending on the power source, my Pro1 seems to distinguish between three different charging modes: "charging slowly", "charging", and "charging rapidly". The last is probably chosen only if the PSU explicitly supports Qualcomm QC. Electrically, one of the lower two modes should always be possible. I've been charging my Pro1 with solar panels ... 😎

If you look again at the OP of this thread, the behaviour you observe is exactly as described for a screen having not reveived the "Stock-firmware-magic": The outer ~7 mm are insensitive to tapping but still correctly register dragging your finger form the central area outwards. I had understood stock Android 9 does its touch-calibration thing only on first boot. So just connecting the screen to an already-installed stock-Pro1 might not be enough. I would try to facory-reset the "calibrating" device first.

I guess @Tommi69preordered an original Pro1 via the f(x)tec website and was later "upgraded" to a Pro1X. As such he is eligible for refund while IGG backers are not.

Exactly, that's what I mean and what I tried to swap among my Pro1 and Pro1X. I also thought that was the unit you can obtain from f(x)tec as "replacement screen". Thanks for clarifying.

Sorry, I'm getting confused. I thought the replacement "screen" you ship as spare part includes the upper housing. I.e. replacment using your part does not involve glueing? So are you saying the top assemblys of Pro1 and Pro1X were already known to be different parts, and in addition you found out that even the screens themselves are incompatible? Wouldn't this mean that also the Elephone U/U Pro screens from Aliexpress people have successfully used for repairing their Pro1s would no longer work with the Pro1X?

Interesting. Just to be sure: When you say "screen" do you mean the entire top unit (detachable by 5 screws from the mechanism) or just the display (as available from e.g. Aliexpress) that is glued to the rest of the top unit? As reported above, I tried operating the Pro1X top unit on the Pro1. The display and digitizer seemed to work fine in recovery, but the Pro1 wouldn't boot into the full OS.

I guess you might be right. I was firmly assuming they had kept that unit identical to keep development cost low. But then, the different SoC on the other side may have dictated some modifications ... Retrospectively, I consider myself lucky not to have damaged anything with my bold move two days ago 😆. For those owning both a Pro1 and a Pro1X it would be good to know for sure, though.

The problem is that security issues in the binary blobs owned by Qualcomm are not going to be fixed. Even LineageOS 19.1 is still on the "vendor security" level of April 2020.

As @Hook wrote, there will be no more official updates of Android 9 for the Pro1, let alone upgrades to newer major releases. While there are several options to get your Pro1 an up-to-date OS, LineageOS is certainly the least obscure and, combined with a suitable distribution of the Google Apps, will give you the most "Android-like" experience. Installing LineageOS on the Pro1 is easy if you follow the instructions in the Wiki: https://wiki.lineageos.org/devices/pro1/. Presently, the officially supported release is LineageOS 19.1, which is based on the Android 12 Open Source Projec

Venerable 835-Pro1 just got another updated build of LineageOS 16.0. At http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 head for the ROM dated 20221026. This build includes backported patches from the Android Security Bulletins up to patchlevel "5 October 2022". I bumped the security string in the ROM accordingly. As noted already in the last update, since May 2022, the ASB backports for Pie lack upstream code-review and are no longer merged into the official LOS-16.0 branch. I see no problems with the build on my device, but please be aware of that before yo

The full top unit - i.e. what you hold in hand after removing the 5 screws and disconnecting the ribbon cable leading to the phone. The digitizer also worked btw. as I could navigate through Lineage recovery using touch. Could the front camera be different?

Hmm ... Just tried to replace the screen unit of my Pro1 by that of the Pro1-X: While the display does seem to work, the Pro1 goes into a boot loop (Lineage 16.0). So something does seem to be different (firmware?) Before you ask why the hell I tried this: The Pro1-X's screen has much better colour fidelity (no green tint at low brightness) than my Pro1. And as the latter will still be my daily driver for some time, I thought I could pimp it a bit by swapping the screens ... 😎

Thanks for making the GMS-less beta-build available. Installed it via fastboot/adb as described above and rooted following the official guide (thanks for that, too!) - works fine. I won't use the Pro1X productively before a somewhat mature LineageOS becomes available. But until then, this is a good way to play around with the device without big G watching too much. Dumb question: Is it normal that in GMS-less 2.1.5 available WiFi networks are not automatically detected or listed in the quick-settings panel? In stock 2.1.2 (as in LineageOS) I get a list of all networks in range by tap

@Casey, thanks for explaining / confirming what I thought. The flashing of the GMS-free 2.1.5 via adb as in your other post worked fine for me btw. thanks!