Rob. S.

Good question... Any new information on that, perhaps? [Edit] Earlier, someone reported success with black screws (black in order to make the stickers superfluous) from a Nokia E7 repair kit, which I gather must be the smallest of the few sizes Nokia had used in that phone, which would be M1.0x1.9 ? [Edit: No, it isn't. See followups...]

The location has changed, the teardown guide is now here: https://github.com/imax9000/fxtec-pro1-teardown

Theoretically, ACC/AccA has that function, it's called "charging power control" and it lets you set limits for both voltage and current. Problem is, so informs us the app, "unfortunately not all devices/kernels support this feature", and unfortunately I've had no luck getting this to work on the Pro1, either. Within the app, there's also no way to find out whether the device or the kernel is to blame... Another cool feature doesn't work with the Pro1, either: "prioritize battery idle mode": "This allows supported device to draw power directly from the external power supply when charging i

My Pro1 hasn't seen much use as of late due to my habit of breaking the screen, still charging has had a few hiccups here and there – though nothing as drastic as having to reboot to start charging again, if I remember correctly. That said, I'm running LineageOS 18.1 with Magisk and I have the ACC (Advanced Charging Controller) daemon installed as a Magisk module (plus the AccA app), which I had thought to be the culprit here. Whether it was or wasn't, whenever the phone wasn't charging although it should, I opened the AccA app and that usually made charging start again...

Its purpose is to bring the tap-insensitive display borders back from too wide to normal after a display replacement. If you need a display replacement and you get one from any other source than Fxtec (and Fxtec has been out of replacement units for some months now, also they're expensive as they include casing and front camera and other electronics), those replacement units will come with significantly wider tap-insensitive borders – to the extent of making it difficult to impossible to use some functions in some apps, even with the margin settings provided by LineageOS reduced to zero.

Thanks @EskeRahn. Doesn't help me in flashing the display IC, though, which it seems requires a running LOS 17.1 or 16.1 or stock Android...

Hmm... Is it possible to downgrade from LineageOS 18.1 to 17.1 without data loss (before upgrading to 18.1 again)?

Thinking about it, the first time I had the screen replaced I could indeed still have been on LOS 16. That would explain it. (I would hate having to admit being too stupid to perform that relatively simple procedure 😉)

It never asked for root permissions, as far as I can remember, so I couldn't grant any? About the updates, there were a few weekly security/bugfix updates for LOS 18.1, but nothing big... For what it's worth, I noticed in the adb root shell that the filesystem was mounted read-only, but remounting it as read/write – while letting me delete those two files I wanted to delete – didn't help with the display IC flash procedure, either. While I attempted the update once more today I noticed something else: a few seconds after starting, the flash tool showed a notice for one or to sec

Now I have a new situation – I've got a repaired phone with a new replacement screen, only the driver flashing process to set the margins to a usable width doesn't work anymore. Tapping the app's 'update' button, the button stays orange for two or three seconds – but instead of starting the flashing process, the phone just cold-boots, with the margins staying as they were. (Yes, I double-checked everything, tried different PCs and stuff, but the connection isn't the problem this time, it's the part of the process that happens on the phone itself...) The big question now is, do I go a

Things are getting more and more complicated in that regard. A number of apps don't work on a rooted device, and I fear they're getting more. Now some of them will work with MagiskHide, but some won't. On the other hand, some apps don't even work on an unrooted, alternative Android like LineageOS. They might explicitly check for a non-stock ROM, or they might check for an unlocked bootloader. Depending on how they do it, you might be out of luck whether you're rooted or not. With one important app (VPN identity token) which didn't run on the unrooted LOS that I had been using I was l

From what I've read here, the driver does get updated with a stock reflash plus going through all OTA stock updates, as one of them includes the driver update. It would seem that Fxtec needed to apply the changes themselves because from some point on the displays they received (whether in production or for their repair units) were of the variation that needed them...

Even in the EU, at least in Germany, those two years warranty are really only half a year, because after that it's the purchaser's obligation to prove that a defect was the manufacturer's fault. So a full year of real manufacturer's warranty may actually be an improvement to what the law requires.

I can't believe it, another screen broken – I just tried to swipe a fly from the display, and what I did was swiping the phone from the table, because the EFFING SCREEN PROTECTOR I'm now using since my last accident is sticky to the touch! So it's back to @EvilDragon's repair service...

True, if you don't count the keyboard... Still, my impression – not just from what I myself do (hardly any of which needs more than a low-end SoC) , but also what I read about SoCs and their real-world performance – is that 3 or 4 years old high-end chips like the SD 835 we have in our Pro1 hardly show any lack of real-world performance even today. And the more current, but also more lowly SD 662 shows similar CPU benchmarks, it's just the GPU that comes with a potentially noticeable drop of performance. Any real world applications which don't heavily rely on GPU performance will work jus

I guess the interesting part of this is the "expect shipping to begin between October and November" part. The interesting question now is whether my 2019 order will still succeed in its 3rd attempt to arrive at Christmas! All good things come in threes, or so they say?

With Fxtec's track record, even though I still don't doubt their best intentions, I'd rather expect the first batch to be sent out around 31th Aug...

LTE but no GSM? That's gross, but it doesn't surprise me in Germany. Just today there were reports that Telekom's process switching off 3G networks in favour of 4G and preparing for 5G has left some regions to GPRS and EDGE only... So when you disable "4G calling" under "network and internet" -> your provider, you cannot take/make any calls at all? I fear you might be out of luck then with regard to using the phone by itself with its mic and speaker. The only workaround I could think of would be using a headset (cable or bluetooth, while bluetooth sometimes seems to have its own

This is an ancient thread, but I might just as well add that this thread: and my recent update for LineageOS 18.1: ... details a relatively easy way to install and configure Pro¹ devices to use AICP or LineageOS so that Netflix and Disney Plus apps do appear in the Play Store and can be installed normally; also Google Pay works for contactless payment with the smartphone at the supermarket counter (which over here is the only real method to make sure you don't need to touch that keypad)...

Success here with OTA update, too, which kept Magisk and MindThe Gapps as they were.

@Noob @VaZso Bummer. Now in yesterday's conference call, audio suffered badly from distortion and dropouts in both what I said and what I heard. Switching the headset off and using only the phone itself improved things only slightly, though. (I hung up and dialed in with the landline phone.)

@Noob No problem here with two different 'Jabra Talk' in-ear/on-ear headsets, I'm using them regularly for conference calls.

BTW, no more than 1200x900 px for me anymore, either...