Leaderboard

Because shit happens. Just because it didn't until now, it doesn't mean it won't or couldn't. Also, people make mistakes, which, I guess, includes you, too... I completely agree, like others already did, too. Still, I'm afraid there's not much we can do to make Lineage change their policies, and getting our knickers in a twist about it doesn't help us, either. As all of this is an open source thing, I suppose it means taking things in our own hands, and finding a maintainer for continued LOS 16 and 17 updates like the one @Hook mentioned for that Samsung phone. Perhaps there are more p

There must be some way to get the security updates into older releases of Lineage. My old old Samsung Galaxy Tab S is still on unofficial Lineage 14.1, maintained my Dark Existence on XDA and continues to get current security patches. This is obviously not Lineage doing this, but it suggests the patches can be obtained and compiled into the OS. So the question (the answer to which is way beyond my pay grade) is can this be done for Lineage 16? Is there a source for the security patches or is the XDA dev extracting them from later versions of Lineage or... For reference:

I suspect the parts are delayed because it is cheaper to order the parts when they are also ordering them for assembly of the Pro1xs at the factory... volume discount and all that.

OK, look guys, my post was a reaction to @daniel.schaaaf, who I think is fundamentally right in his criticism of some aspects of today's open-source software culture. I tried to provide some examples how us so-called "power users" are simply more affected by major OS upgrades, and are hence left in the rain if Lineage versions are abandoned at every second stop. True. But neither can we change FxTec ways of public communication, IGG policies, or EOLs of QualComm product lines (to name but a few). Did that stop anyone from whining and complaining here? Now it is my turn. 😉 Self-bu

Sorry, forgot the irony tags. I was commenting on the "postponed" aspect there...

Wow, just looked at the photo thinking in a thread of phones with keyboard attachment and thought what a good looking phone attached to a good separate keyboard in a flip case... 😄

That is not true. As I wrote, I had LOS 16 from the point it became official and applied every update until support was dropped. None of the weekly OTA's broke anything related to the chroot set-up. AOSP security fixes do not change system behaviour on that level. Major upgrades, on the other hand, do. That's why they are called major, need to be well prepared, and, therefore, should not be necessary very often. Yes, you can still build LineageOS 16 and 17.1 yourself for the Pro1, which should merge-in the upstream fixes automatically. Retrospectively, I should have learned how to

@claude0001 I guess I have an – if only faint – idea of what you're doing there... And, sure, if that were what I'd need in a phone to be able to use it productively for what I do, I might even try something like it myself. I just wouldn't get my expectations up as to its working in a stable way for a longer period of time. Neither would I rely on such a massively tweaked system as my single phone... Incidentally, after three to four years in productive use, right now I have to upgrade two Linux servers the OS versions of which stop being maintained. Even though it's a fairly normal thing

The case in black.

I could not agree more. What you describe is the reason I am staying on LOS 16. I have plenty of hacks in place, where I cannot predict whether they would still work on LOS 18.1 (or 17.1, for what matters). I use several autostart scripts in /data/local/userinit.d/ for setting up stuff on boot automatically. Those scripts are officially unsupported already in LOS 16, but can be made to work using some third-party apps. Will those still work with LOS 18.1? Obviously, all of those autorun scripts require root access. Will those early-executed shell scripts work with (third-party) Mag

I was hoping that the delivery date was automatically updated for all the perks, and that FxTec would clarify that the screen will be delivered in April or May nevertheless... Unless I hear something different from them, I will go with your explanation: FxTec is keeping costs low. We will see if I experience the problem as well.... In reply to @Rob. S.. Thanks. I respect your choices; myself I am not going to buy a heat gun now that I ordered a screen with frame. This is getting too complex for me. And I am not going to buy another phone to bridge the gap. I would then totally

No idea why the postponement... Perhaps they want to reserve themselves the option to make small changes to the screen should the redesign of the Pro1X require them. (Whether or not that might introduce incompatibilities to existing devices – which would be, of course, bad for those who wanted the screens for existing devices...) On 16 March I asked info@fxtec.com whether they could send me a spare screen for my Pro1, but I have yet to get an answer (or even an acknowledgement of receipt, like the ones I used to get for earlier mails on other topics). That's why, in the meantime, I o

Thanks for keeping us updated. This is interesting. I had ordered a spare display during the latest indiegogo campaign to be able to react without delay to such a situation (I guess I will face the same situation as the others from the batch soon...). I ordered display with frame because I do not feel able to play with a heat gun. Now I see that the delivery date for the display has also been postponed to August 2021. What is the reason for the postponement? I understand the delay for the Pro 1 X due to the Chip issue, but why a delay for the display?? The reason for this post

It'll likely get worse from this point onwards. I'm not seeing that many vendors on Taobao selling replacement screens for Elephone U Pro (same LCD used by the Pro 1), so it could mean it's a discontinued part.