EskeRahn

I did a macro shot to show how close it goes: https://community.fxtec.com/topic/2498-slow-motion-video/?do=findComment&comment=34777 (Not exactly an interesting motive or anything)

Or all the dots we see in the image, are them testing the flash LED of the next batch of Pro1... 😂

An interesting question. But remember that under any F(x)tec modifications for the Pro1 are some code for supporting the hardware, and THAT might well be protected by some copyrights, so it might not be up to F(x)tec to disclose the source, no matter if they would like to do so or not....

It seems awfully fast yes, but maybe this is synthetic by changing some other parameters. I tried to put it right next to a large LED-pane in my ceiling, turned to max, requesting -2EV at ISO 800, And It actually gave me something not just 'white' but dim. But could be synthetic, by darkening the 'real' image captured. I do not know.

Let me join the thanks. Especially to @Waxberry and all the crew for giving us what I have been waiting for, for so many years. But also thank you to the community for all the -mostly- sensible input, to keep this an informative and fun place. and for reporting on the spammers to keep things clean. I hope you all soon will get your devices too, and will help tracking down the last bugs when you do, so the Pro1 can become even better. And maybe even with some user requested features added.

Well I think the problem lies with the driver for the camera. but if that is FxTec or someone else I do not know. For the narcissistic camera we CAN get very dark images in manual mode, but some automation is kicking in here also, though I'm not exactly sure how. And attempts that would require longer exposures than 1/7 s are truncated to 1/7 s (for the front, 1/8 for the rear) Here is a table of the used exposure times for the 12 images you see in the collage above, and except for Iso 800 and +2EV it looks well: Odd (And even for Iso800 it is not entirely OK, as +2EV should h

They already supports the Pro1 http://android.onse.fi/finqwerty/pro1.html So it definitely would be a nice option to have. 🙂

Nice, and interestingly the copy of frames is good for the compression, so the resulting video is not huge. 0:20 in it does look a bit odd in the border between the display and the keys. So this only works when things are not moving fast, But could still be used to see details of fluid motion

As I understand it, This is allowed for tablets & PCs, but not for phones&phablets. Yes I know, this does not make any sense! But neither does their lacking landscape support of the homepage grid on a phone&phablet. Must be some strange 'political' decision some crazed cheif UI architecht had made at some point, trying to force us to use our devices not like we prefer but as he in his dictatorial mind wishes.... Google's variant of aPple's "You are holding it wrong"...

Please note that we (oddly) are (still?) allowed to do this through ADB. I use this to clean up a Samsung S8- somewhat, see this.

Craig, you are TOTALLY wrong, he NEVER said he was willing to pay $3k, he said he was willing to pay OVER $3k.... 🤪

Interesting idea, but in principle that would only be a further level or security, or a complication, as you previous method could be used twice. Of course that is a serious complication so would certainly make it more secure. But from an academic standpoint it is not. But talking academic it would most likely be easier to open the phone and insert something that logs every display and touch,

That was god news! Thanks.

Yes but we started in the last millenium, so then we would have ended in version 102.1 ...

We had a similar system with some database-system once, bumping the major version every year. We got to version 19.1 in 2002 (still using that version, most likely the last user!)

Please do not try to here repeat the extremely long thread on their communication of estimates that did not hold.

Touché 😁 Glad I wrote "consider".

There might be, but sort of would be sad if people that had that much money to waste did not use them for some better stuff like charity. (Splitting sticks 20 would be a digit behind, in front could be a 1 to 12)

Well if people got a broken device, and the alternative is to buy an intermediate device, for use while waiting only, well then an overprice could make sense. But personally I would not even sell it for $2000. If one added a digit in front, I would consider it....

Try adding more digits... 🤪🤣

Please read the thread.... They can not use Paypal before they can guarantee to ship to consumer within 20 days. PayPal policy

It is like saying you would want to buy an old painting slightly over the price it was sold for originally... As the price has gone up, people can not even get back in queue for a new one with a substantial profit, so realistically the only ones that would find your offer interesting would be any disliking the Pro1 and regretting having bought it. And sure it is likely that some will feel that way, but hardly among the most eager ones that are in the first batch....

From older SonyEricsson Xperia's I remember one of the Staff suggesting a user to attach the device to a SLOW charging port, like e.g. an old 0.5A 5V charger or a PC, and leave it overnight. Could be worth a try, 🙂

My guess above was wrong, this seems to be related to some automatic system that ensures a minimum mean brightness, that they forget to turn off, when not in Auto. Have a look at this overview of images taken with manual mode in the Qualcomm app The rows are Iso 100, 200, 400, 800 and columns are -2, 0, +2 EV And clearly the EV is ignored/overruled for ISO100 and -2EV looks all too equal. My guess is that something is boosting too dark images brighter. A functionality that can be quite handy in Auto, but should be turned off when the API get explicit parameters, and th

But as I said before, what is suggested is REALLY close to what we can get using a black marker on a qwertZ: And then just use it with FinQWERTY, as I currently do.