EskeRahn

I think what you experiencing is the deliberately added delay to reduce the dreaded "Too many retries" that is quite common on stock. The delay after an error, reduce the risk of the (from a human perspective) 'same' press of an accidental touch, to be registered as a series of failed retries. Note that a case or shell practically eliminates accidental triggering the fingerprint reader.

Did not read all the latest activity here, but generally keeping a battery in good condition is a bit of a science. If you turn off a phone, so only the circuit waiting for a power-button press is active, a phone can last for ages. It is not unusual that it is still well above 90% after half a year. So if that is what is meant by "kept at 100%", it is clearly harmless. But if it is plugged in and applied a high voltage constant trying to pull it up, it is not a good idea. So if kept plugged in it is clearly a good idea to stop at roughly 80-90%, as it is the last part that is hardest,

It has been reported that at low light the image has a green tint. But if video only it sounds like a different issue. Have you tried transferring the video to a PC?

Normally only a light touch is needed on the Pro1 too, so you could have a hardware issue...

The limit has a time-out, and if I remember right there has already been added a fix so that multiple attempts in very short succession does not count, that is basically what would would happen if you held the device on/close to the sensor.

Thanks! it downloaded and installed smoothly (flashing).😎 Please also update the "Current build: 2020-11-02" in the OP. 😉 Add: And for those wondering it is on the January 05 Security update.

The point was the larger memory, reducing the need for in inserted SD-card

You mean if the sensor allows the data to read in an arbitrary direction? I doubt it. But perhaps the helper chip creating the jpg files from the sensor output could be requested to do it in a selectable direction. Would be clever if it did,

As commented elsewhere not all viewers respects the orientation flag, and only display the native image. This is a viewer bug, not a bug in the app generating the images. Even big ones like WordPress messes up when they create thumbs, If android displays it correctly, the flag is set correctly. We do NOT want the camera app to reprocess the image in the resulting direction, it takes time, and comes at a potential quality loss. That is the whole purpose of the EXIF flag telling how many times 90 degrees the image should be rotated for display. Sure decades ago before this flag, we DID r

Others have repotred that they are to add an update on that soon. The main difference is the colour, and you can select between two models, where the more expensive has more memory and storage

To order, yes, but not to delivery before the period they suggested.

Welcome to the wonders of Brexit.... as @netman already posted. And as March is approaching the demand is not as high as a few months ago. (obviously we do not know if the pending will be sent out in March as planned) Also some might prefer the non-shifted qwerty-keyboard of the Pro1X, and finally the scuff-marks could put some off too, if people do not plan to use it in a case.

@Hook Already answered most. I do understand your frustration. But on the "serving first", please remember that we are talking selling a mere ten(!) units of a small batch made for promoting the Pro1X. Sure they could have directly asked some in line for the regular Pro1, if they were interested to get one of these blue ones instead. AND they actually kind-of did that by giving those registered earlier access by mail than the public. But we do not know if the ten lucky buyers were in line for a Pro1 or some bought an additional one.

...And we are most likely back to the original mentioned issue of HDR with third party camera apps

OH I looked the wrong place on he figure, not the background, I see it now:

I'm not seeing that in the above image.... Edit: see below It is an image with (at the least) two light source roughly in the direction from the top right and top left corner. Where neither cover we see a darker triangular area. The sources are carefully placed so no area of the background are lit directly from both sources (the point of the darker triangle reaches the object). Had the object been moved down, a washed out area over could be expected, and if moved up, part of it would be ill lit. Below the figure we have a shadow as the area is not lit from either of the two. And agai

(lineage-17.1-20210201-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload)

1) It is not the camera.... The HDR in the build in app works, as well as pictures in both high and low lights. 2) BUT they do not seem to adhere correctly with the "Camera2 API" protocol, so IF a third party app tries to access the camera through that, stitching images to get HDR, the app will not output the correct result. I have tried to report this several times, (until now without it resulting in a fix), it is clearly a pure software issue of not adhering to the Camera2 API protocol, and NOT a hardware issue, and will affect third party apps only. I see it with "Open Camera". (BTW

I do NOT see this with 2021-01-25. Mine is set for password, and shows it the normal way.

It is not that the idea is bad as such, the main problem is that it s non-standard. Had they shifted the numbers along with the letters it would have been substantially better. BUT things are NOT really centred this way! The centre of letters is between the G and H as also acknowledged by the F and J markers. On the shifted keyboard the G is on the key almost exactly at the physical centre, on the standard layout that is the H. So the layout is half a key off center to either side on both layouts.... For the lengthy story see this

Indeed, and much can be gained (as others have said) by adding this or that to fix stuff, or change the entire OS. It is such a shame that it could be so much better out of the box.

Tjännare AFAIK The bands used in Sweden are the same as the rest of Europe. But it depends a bit on the carrier what they use, some might still be using the 2G bands, others (like "3") are limited to 3G and 4G. For "3" in Denmark "LTE/WCDMA" will suffice. I do not know if there are any substantial overhead by selecting a wider range, or the SIM/operator tells the device which bands that they support? If not and you are in an area with poor coverage, there might be an overhead, scanning a broader rage of bands for better signals.

It is not one led but three close together. R,G,B

I agree. It was my clear understanding that the ten devices were ordinary Pro1s in the blue Pro1x shell.

I bet not many will be surprised to hear that I love mine too. 😍 I would like to see some software fixes (and a new security update) soon though....