claude0001

Well, LineageOS is community driven. How long it supports a given device is up to the port maintainers, not the manufacturer. The maintainers can usually support only a device they own themselves, so probably nothing will change as long as there are only original Pro1's in the wild. As far as I understand -- distinct ports for the original and new Pro1 will be necessary, so development for the 662 can start only after Fxtec provides a willing dev with a preproduction device. Updates of official Android 9 may be a different story. But is there really any reason to use that (honest que

I do understand that. My point is that this change involves much of the overhead of a "real" upgrade without any benefit to either the customer or Fxtec themselves. The natural way to react to obsolescence would be to switch to the designated successor product -- typically bringing better perfomance and more features. However, Fxtec cannot go that way as it would involve updating the entire phone, which they cannot afford. They are effectively driven into a platform downgrade they did never intend. Sadly, there is no denying that.

I appreciate you guys trying to be optimistic, but I must say this news scares me quite a bit. Having to downgrade to an inferior SoC is a devastating blow. So much development work (and time!) will be spent for nothing but getting an even more outdated phone even later onto the market. That is brutal. Even as an enthusiastic Pro1 owner, I must admit that I can understand anyone who decides to draw back from the project at this point. Let me stress that I think Fxtec are a good people. They are not trying to betray us. They themselves obviously believed they would get those boards.

Let's hope for the best ... The number of pixels of the camera has been my least concern up to now. I could think of many other things to improve there ... 😉 I am most worried of the 3rd-party OS'es. LineageOS is IMHO the most advanced operating system for the Pro1 in terms of usability. However it is community-driven and did take some time to take off. If its development is to re-start from scratch, that is a serious set-back.

Wow. This confirms what I wrote above in a way even I did not expect. They admit that this will involve a re-implementation of all operating systems and eventually result in a perfomance loss. That sounds like a serious blow. Also, based on past experience, I would not trust the promised start of shipping in August one second ... I am sorry for everyone waiting for their phones. 😞

Well, according to initial estimates, I should have had the phone within three months ... Their estimates on delivery times have always been off by an insane factor. The reasons have always been issues with their suppliers they could not control. I honestly think that situation has not changed since the initial production phase. I believe Fxtec is simply too small a fish in the ocean to make pressure on their upstream suppliers regarding delivery deadlines in the present pandemic situation. This is probably something we have to accept.

I believe @Rob. S. is right: Fxtec can neither risk massive order cancellations nor a sudden decrease in the rate of new orders coming in, as they are running on the money from those orders. Hence they are trapped in a situation where they cannot suddenly start admitting that no one can at present predict delivery times reliably. I waited for my preorder (more or less patiently 🙂 ) for approximately a year. I was in the comfortable position of having another working phone I liked and of not urgently needing that money for other things. I could affort the wait, but I understand the frustra

Thanks for the heads-up, @tdm and @DieBruine . Not using Gapps (et al.), I constantly forget about the importance of this step ...

Did you try to simply re-flash the same nightly via sideload? That preserves userdata, right? So it should not destroy anything that isn't broken already ...

Not according to the review paper I have linked above. Charging of cold batteries seems to be especially problematic. E.g., as charging heats the battery from within, aggressive cooling from outside leads to thermal gradients that seem to cause their own problems. For these reasons, batteries of electric cars are actually warmed up using dedicated heating systems during (and prior to) charging in winter ...

Turns out you are right: now, at 85% charge level, upower already reports 4.13 V battery voltage. With the above 12.6632 Wh this would already correspond to 3066 mAh design charge. I'll keep monitoring the reported voltage as it discharges, and will calculate some approximate average. I can now easily imagine that we end up very close to the expected 3200 mAh.

I can confirm that using emacs with the Pro1's keyboard is quite pleasant thanks to its two Ctrl-keys. I was an emacs user once, but the N900 made me switch to vi for CLI-editing. The reason was that the N900's single Ctrl-key is at the left, so that the most popular emacs key presses (think C-x C-s ...) required to move both thumbs to the extreme left of the keyboard, which was uncomfortable in the long term (even though the N900 had a very small form-factor). PlanetComputers made the same choice of having only a single Ctrl at the left. In table-top use, this may be less relevant,

I see your point, but I cannot remember seeing a much different value reported by upower. Maybe it is even some average already? However, I also do not recall ever looking the numbers at deep charge level. Will report.

Yes, as I wrote (and never disputed), it is well-known that not using a battery to its full cell capacity saves lifetime. Also, please do not get me wrong: feel free to experiment with your devices as much as you want. Limiting the maximum charge will probably never hurt anything. That said, let me add that I believe the Pro1's battery management system already limits the maximum charge to 90% nominal cell capacity anyway. The Pro1 spec sheet advertises a battery capacity of "3200 mAh", which likely corresponds to the maximum cell capacity that could theoretically be used. However, t

While I am no expert in Li-ion batteries, restricting the discussion to the question what is the maximum "healthy" charge of the battery seems like over-simplifying the problem to me. Indeed, it seems evident that consistently keeping the charge of a battery close to some intermediate fraction (around 50%) of its nominal capacity does slow down degradation of that nominal capacity. See e.g. Grolleau et al. (2013) [doi: 10.3390/wevj6030549]. However, the downside of that strategy is just as obvious: this way, you will never take advantage of the full capacity in the first place! Essentiall

I can only support what has been written already: unless you really like that blue colour or have to use two SIMs, I see no reason to cancel your Pro1 order for a Pro1-X. The Pro1-X only upgrades RAM and internal storage, which are the figures of least concern regarding the Pro1. The SoC itself is the same in both phones. The 6 GiB of RAM of the original Pro1 are enough for about everything today. On mine, I constantly run two operating systems in parallel (LineageOS and Debian/Devuan) and have never run into RAM issues. Also, 128 GB of internal storage are just fine if you can use S

I've always only used Linux for flashing (fastboot as well as adb). In Debian (and probably Ubuntu, too), do: sudo apt install adb fastboot and you should have everything you need ...

https://download.lineage.microg.org/pro1/ ? Note that I have never used the MicroG-Port of LineageOS, so I cannot help further if you run into troubles ...

These are nice pictures (and I like your cat and dog 🙂 ). I am not saying that the camera is physically incapable of taking good pictures. I have taken many pictures that I am perfectly happy with. The point is that the camera works unreliably, which makes its use frustrating. I often have to shoot the same scene three times to get one nicely-focused picture. Also, as I wrote above, automatic exposure is failing me quite often, so that I have to manually intervene. The behaviour and picture quality was pretty bad with the stock camera app (as you seem to agree). With OpenCamera (wit

You are somewhat contradicting your enthusiastic post from above where you claimed that your Pro1 took "amazing pictures, all the time" ... 😉 But I can agree with your main point. The camera is not best-in-class, let alone "semi-professional". It works well enough for taking casual pictures, albeit having some bugs that I accept for the greater good of having a keyboard. If the Pro1's price tag was attached to a Samsung, I would expect a much better camera. However, that is an unfair comparison. The Pro1 is produced in very small volume, and the camera is clearly not its central feature.

Multiple light sources cannot explain the bright halos around dark(er) features. That is a signature of "overprocessing" of the picture. Probably overshooting in the contrast or sharpness enhancement algorithms.

I believe that, in trying to speak in favour of the Pro1, you actually showcase some of the problems of its camera. What is that triangular blurry shade at the top of your picture? That looks unphysical to me, especially as, within that shade, there is again a brighter halo around the top-central red ribbon in the background. A similar bright halo is visible around the ribbon at the bottom, which actually lies within the hard shadow of the figure. The Pro1's camera has been reported to generate such artifacts under some circumstances (in HDR mode at least, see this thread). Not sure

I'm still on LineageOS 16 (without Gapps). As the kernel and (I think) the camera driver are always the same, I wonder whether the OS makes any difference, though. I restrict myself to FOSS apps as far as possible. Of those, I found OpenCamera to work best with the double-action shutter button. That said, and even after a few months of training, I am still not as confident with the shutter button than I was with the one of my old phone (N900). Many pictures still come out defocused when I use the hardware shutter button. I'm not sure if its the mechanics of the button, software issue

In case you are still interested: I've got a local backup of the last official Lineage 16 build (20201026), including the recovery image. Just send me a pm if I should make it available for download.

You have ordered your phone preloaded with UbuntuTouch, which is not identical to the Ubuntu distribution for the PC. UbuntuTouch is based on Android in large parts. It does not use systemd as process 1, and probably won't anytime soon. The choice of (native) Apps is more limited in UbuntuTouch compared to Android. But as you describe your (quite basic) requirements, UbuntuTouch will probably provide everythig you need. If you insist on Devuan for philosophical reasons: it runs nicely in one of the various chroot/proot solutions for Android/LineageOS. I have it in a (rooted) Chroot o