fxtec-preorder-47xx

I have exactly the same issue. I changed the screen before and everything was fine. Then, after the next drop, I changed the screen again and got the described behavior. (I am thinking about a big rubber protector around the edge to protect the screen from cracking, now that I cannot use touch in the edge anyway. 😉)

People who have "normal jobs 'n stuff" can pay the normal price. Leave "early bird" offers to the rest! 😜

I would do this! Where would I find the logs? When someone could explain to me, how to get useful log info about focussing... As soon as I have some instructions, I'll start. Another thing that proved interesting for testing: Get OpenCamera-App and switch to CameraApi2 (two!) in the settings. You can then choose 'manual' focus mode and focus with a slider. On BOTH (Stock and LOS) if you slide to 'infinity' the far objects get less sharp. Best result for both is stopping right before infinity, lets say at 1000m. (It's displayed that way.) Even when the object is just 5m away

My only system is a i7-3667U in a ThinkPad with 8GB ram... I could as well build the ROM on the Pro¹ itself 😉

I did not find the App in F-Droid or as APK anywhere, but apparently when you build your own ROM it can be pulled in easily: Anyway, I won't build any ROM for myself, as at the moment my most powerful device is... lets see... possibly my Pro¹ 😉 ...sad but true.

Hmm, when I look at https://download.lineage.microg.org/pro1/lineage-16.0-20200718-microG-pro1.zip there's no match for 't5' in the accompanying plain text files. Might be in payload.bin? How do I make the change (to the assert) you spoke of? EDIT: Oh, damn. I should change QX1000 info t5, not the other way round, got it.

You are right. I used a (secretly? ...by Sean McCreary) released version: https://community.fxtec.com/topic/2479-team-win-recovery-project-twrp/?do=findComment&comment=34151

I tried flashing the "LOS4µG" with TWRP now... it came out like that: I:operation_start: 'Flashing' Installing zip file '/external_sd/lineage-16.0-20200801-microG-pro1.zip' Checking for Digest file... I:MD5 Digest: 1222a9af83ab781d24980e495f7bce0b lineage-16.0-20200801-microG-pro1.zip Digest matched for '/external_sd/lineage-16.0-20200801-microG-pro1.zip'. I:AB zip I:has_legacy_properties: Could not open /tmp/updater: No such file or directory! I:Legacy property environment not used in updater. Failed to parse build number in post-build-incremental=eng.root.20200801.131513. Package is

Well, in my case, I HAVE autofocus. But it only works for near objects. Far objects I cannot focus automatically nor manually. I tried 'Open Camera' app and MANY OTHERS and far objects (infinity focus) do not get sharp. If I change from CameraApi to CameraAPI2 I can focus manually, and the counter goes up to 1000 meter, but actually at like 20 centimeter it is done.. everything else is in the fog. With stock ROM: no such problem.

Yeah, if I just COULD wipe. (Ok, I suppose the fastboot wipe method is as good as the (not working) recovery 'wipe system' method.) MicroG really seems on autopilot... but I thought that was the whole advantage, as you stay updated OTA automatically with LineageOS releases?? You may be right, that my main issue is here, that I don't have a proper boot.img... I am still scared to look into self-building... do u have any good tutorials/methods to recommend? ...and one more thing: As I have you here, running LOS4µG perhaps you can report if you experienced that issue here

Hey there, one of the first things I noticed when I flashed LineageOS was, that the camera does not focus anymore to infinity. (While it did work before, with stock ROM.) (So you actually can't take sharp pictures on anything that is not right in front of the cam.) I flashed back to stock ROM and the focus worked again. As I like to use LineageOS I wonder what tweaks there are in stock ROM to cope with the Pro1's main camera. Perhaps someone can commit those tweaks to LineageOS as a patch? If that is the problem at all? Anyone experienced the same? Edit: Dirty lens is NOT

I switched from @tdm fine builds to official LIneageOS builds now. It worked. But what I really want to have, is the "LineageOS for MicroG version". I cannot flash that!!?! The downloads are at: https://download.lineage.microg.org/pro1/ Instructions at: https://lineage.microg.org/ But I have trouble following the instructions. I use LineageOS-Recovery but I also tried TWRP (which is not perfectly supported for an A/B device like Pro1. Anyway, from either recovery tool I cannot wipe 'system'. It has trouble finding /system. I did a 'fastboot erase system' or 'fastboot format sy

Bump! F(x)tec is advertising the Pro¹ with "LineageOS"-Support. Well, ok, I flashed the test build of LineageOS, but F(x)tec should _really_ open source their launcher!! (...and publish it at F-Droid or submit some code to Lineage's Trebuchet, if they want to adopt those features.) Damn it, what's wrong guys?!

Aha, I just tried my last idea: reboot. I needed a reboot to get the sdcard recognized. Strange but working.

I see, this thread is long and confusing. I got one request: Can someone please post a proved working configuration for mircoSD cards! Containing: Manufacturer/Model/Specs of card. Partitioning and which types of partitions. Formatting (filesystem) Thank you. I had no luck with otherwise working cards... the Pro¹ did not seem to take notice it's something in that slot or not. Or do I need to reboot?

My phone arrived yesterday though FedEx initially scheduled for 27th. I am happily busy now! 😛 Thanks to everyone at FxTec for making this come true!

Update: Now (11:16 UTC) I got the update by email from fxtec. My order is completed. And on the web: "Your order was shipped on 22/01/2020 via FedEx. To track shipment, please follow the link of shipment ID(s) xxx" And a link: "Order Again" ... well, I need to rest. PS: No Invoice anywhere to download, unfortunately... 🧐

Me, (preorder 47xx, no IGG, QWERTY to Germany) just (at 10 UTC) got a text message (SMS) from FedEx that was followed by an email, both containing a tracking number, saying: 21/01/2020, 04:17: Shipment information sent to FedEx 22/01/2020,16:45: Picked up (YUEN LONG HK) Scheduled Delivery: Monday 27/01/2020 by 18:00 From: KWAI CHUNG HK To: Me 😄 I think someone from Hong Kong is sending me a cobblestone... ?! PS: fxtec account still saying: Order #47xx was placed on February 27, 2019 and is currently Processing.

Me, preorder 47xx (qwertY to Germany) from February 27th 2019 (NO coupon etc..) just (11:43 UTC) got the stock assigned email. "We will be back in touch with your tracking details shortly." it says... (Order information on "my account" has not changed yet though...)

Ah, ok, payment.... I received an email back on July 31st... at 10:30 (am), and I paid by CC immediately.

Yes, I learned that recently (well, some years, but still late), but anyway, it's more or less the same result. It's my postfix anyway and I catch-all. Some really bad addresses, I do block totally. I did'nt try that, but blocking probably also works with the "+"-notation... Anyway, this gets OT. 😉 I just want my phone! Please!! My current PhotonQ starts falling apart!!!

Ah, now I get it. 🙂 ... the joke, not the phone, unfortunately. (I should choose a name, this is the first part of my <random-company>@<my-domain> email address. Like that, I get a hint, who "lost" my data to some spammers.)

I'm preorder #47xx (fourthousandsomething), no backer, QWERTY, Germany. Still 'processing', no stock assigned. 😢

I'm from Germany and I am german native speaker. But I do not like the QWERTZ layout. Even on a notebook or desktop keyboard. It is because I really enjoy using the curly and square brackets etc... on those keys that are otherwise used up by ü,ä,ö umlauts. It's so much better when doing shell scripting, programming and other technical stuff. For the umlauts I prefer the dead key layout. That is - unfortunately - not very common. It means, when you type a " (double quote) nothing appears at first (hence 'dead key'), but when you type an a, u or o afterwards you'll get your umlaut. If you