EskeRahn

I think the "just a bit", is a bit of an understatement, but else completely agree.

@arkenoiSee replies to the same text here

Great news, thanks. I will try to find time applying the beta this weekend. 😁

I might understand a clause like this with "alpha-releases", but the point of "beta" in general (as I Understand it) is to reach a wider group that is ready to accept even severe functional flaws, or even to return the device if bricked, but yet the company still honouring warranty, as the risk of a broken device is expected to be very small, and thus the company takes that risk, to gain the feedback from the users. That a beta test is often limited in numbers is obviously to reduce the risk for the company if many fails seriously. I'm a little sad that FxTec don't use beta in this way. A

(merged thread in)

We have another thread on it not working with yubikey, but the reader is close to the camera.

(lineage-20.0-20230313-nightly-pro1-signed.zip on February 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

The only issue with the Beta-program is the clause where you say that we void our warranty if we join. Not the best way to entice people to help. That is why I didn't join....

I have noticed that the Pro1X has more satellites in view than the Pro1, but the actual position is with a worse accuracy.

Unfortunately the Pro1X as well as the campaign for it is very far from flawless. And sure the waiting is frustrating, and we do not even know if the known flaws can be fixed (or even reduced), and if so when. So perhaps a little sarcastic we can hope that this extremely long delivery (see also this) gives them more time to fix what can be fixed, so the agony of the flaws will hit fewer/shorter. And the only constructive thing we can do really is to report any bugs with as much details we can. And for strange bugs not affection all, perhaps see if we can help finding a pattern, to he

I think the worst problem in the judging is our lack of real knowledge of what was known when. In hindsight things look terrible, but that is not the same as saying that they did when the decisions were actually made. But sure their reputation is tarnished no matter if any actual 'guilt' can be placed of them doing stuff they knew were bad. I bet many that would be interested in a Pro2, would wait shelling out till it was actually available, and they hear the user reactions. Some of us feel certain that these are good guys fighting like lions to actually deliver, but I bet we are few

AH That sound great, glad I misinterpreted your comment it sounded rather ominous, I feared it was the same supplier as the main board... How many do we need to buy, and what is the price (roughly)? I for one would like a handful, if they are not too expensive. And importantly with customs paperwork in order so we do not get flogged some £25 'handling fee' by the shipper. What about making a poll and hear how many would be interested in buying spare ports, and how many they want (option 1, 2, 3, 4, 5 over 5 should suffice) The most vulnerable parts for wear/accidents for the Pr

That was very sad news, 😨 Will you get them at a later point? Wasn't The whole idea of the usb on a separate print that it should be easy to swap? If end of service, could you provide diagrams, so some handy persons could produce them, without the need of reverse engineering first? What parts are potentially available for the Pro1? If none/few it would be nice to know if we have to treat a Pro1 with the uttermost care as irreplaceable...

When I have experimented with downgrading a good while back, and it works fine - though you will (almost) always need to wipe the user data in the process, and I always flashed the boot image as well.

The 48MP sensor produces 12MP images after interpolation - I guess it is a sales thing that Sony market it as 48MP, and this is usually just copied by those that use it. e.g. FxTec. We have this difference discussed in another thread somewhere... Interesting with the 662/665, what software are you seeing this on? If I check my Pro1X with "Aida", it says "Qualcomm snapdragon 460/662", "Device Info HW" says "662", but "CPU-Z" says "665". So I guess that the app sort of takes a guess on the cpu based on the info available, rather than get an actual ID back - that could explain discrepan

As can be seen even on the hash of the last four, the boot.img is not identical, and I know from AICP, that a flash can be quite picky on the bootloader selected matching the zip. So at the least when changing major version, I think you should flash the boot-loader first. For LOS I always flash the matching bootloader before booting into the recovery and sideloading the main zip. It might be a superfluous step in general. but I believe @tdm did the same thing in the guide he originally provided for v16, so I just followed that since...

Thanks. So not that easy to extract after all - though possible if needed.

It might be so on other builds, but not on the official builds for LineageOS 16, 17, 18, 19, 20, nor AICP as far as I can see. (It might be inside payload.bin though) Here latest Lineage

We got no real info here, but we do know that many US carriers makes it it hard to do BYOD, so check with you carrier first, or be prepared to look for another carrier. There are some good info in this thread on what various US users have tried.

I have stopped expecting any logic here, though I still expect that I will get it at some point.

What they are now sending is the 8/256GB Blue QWERTY-EN, So those of us with more rare choices (like my Scandinavian keyboard) will have to wait further, despite having a number way below 568.

👍 (nor vice versa)

For those interested, the old: https://web.archive.org/web/20230227093209/https://download.lineageos.org/pro1

They changed the download site (this is Pro1, not Pro1X). As usual practically everywhere on the web these days to poor 'design' with extreme waste of screenspace. (see image below) And the recovery boot image now always have the name boot.img, so you would need to manually rename or move in subfolders to to keep pairs of files for later usage. (previously the recovery image were named e.g. lineage-20.0-yyyymmdd-recovery-pro1.img for 20.0 ) But it works as usual: (lineage-20.0-20230306-nightly-pro1-signed.zip on February 5 security patch installed smoothly using adb sideload and Mi

Sad to hear... But could it be that when it fails, it is actually failing trying to switch to another band? I so not know if it is possible as a user, but could be interesting to see what would happen if we could lock it on a single band only. (Obviously not a solution, but just to help debug the issue, by narrowing it down)