DieBruine

You could try these: [Android 11] Download GApps for Android 11 (Google Apps) (cyanogenmods.org) I am still waiting for my twooooooo repairs 😢 otherwise I would have tested it before posting.

Can someone explain to me if and why LoS 18 will ever achieve official status? I'm thinking of flashing my wife's phone with 18 if it can/will achieve official status in the future. And if I had a Pro1 myself I would open a LoS 18 topic myself 🥴. Otherwise I'll just update to 17.1. But when official LoS 18 is just a matter of time, I'll just go straight to 18.

So let me do the math. Mine were received by FxTec on the 24th of September and the 11th of November. So I would have to add five months 🙈🙉🙊. Hopefully my phone will be back in March. The second one in April? So I can sell that one as new, one year old (replaced by now with a different phone). I wonder, is my warranty extended for the 9 months it was in for repairs 🤔?

If this version doesn't have the keyboard issues, I will flash both phones. But that will probably have to wait until 2021 🤕...

I haven't heard 💩 from FxTec 😡.

11 business days later, not even a response on my request for an RMA. Let alone an update on my pending warranty claim. So I have a broken unused Pro1 on my desk for over 4 weeks now. Waiting to be shipped back. And another one not working, and I'm pretty sure, that's still unpacked @ headquarters. I bought my son another phone. We'll just have to see how much I can get for a 2 month used, one year old Pro1. If it ever gets repaired 😡. Business continuity is important, I get that. But not responding to support requests for over two weeks is just ridiculous. All the while referring to

Did you receive an answer yet SHiSH? My phone is still @ FxTec and I am still waiting on an answer/RMA for a second device lying here. My son for one gave up on FxTec. First his screen crapped out, now his camera. Still waiting for a response (6 business days ago) what to do with the phone. Yeah send it back, but not without an RMA. Which is why I'm curious if you're also still waiting.

Fast forward five months and it seems that this phone never had a working USB-C video out. And just now I finished restoring my son's Pro1 back to stock using Unfortunately that did not help with reviving the rear camera. So I just put in for another support request. Just to sum it up: Phone A had a bad display (stopped working) and USB C video out not working. Phone B had a bad display (glue issue I presume) and the rear camera does not work. Hardware breaks down, I get that. But having to wait a minimum of four weeks just to get my phone inspected 🥴. So, my afternoon will be

This is what the http://files.nwwn.com/android/pro1/boot-stock-kbd-3.img is for...

😅😂🤣😭 Well, the argument holds. Due to restrictions they have a limited workforce to assess all the RMA's.

I contacted FxTec two weeks after I sent my phone in. Reaction to my request took double the time I'm used to. On top of that they told me that due to COVID-19 restrictions it would take at least four weeks before they would / could even take a look at my phone. So, I assume it is a possibility I won't see my phone back this year. And I'm sure as Hell not sending the other one in (possible hardware camera issue).

Also take a look at the PD rating. In general, the higher the rating, the higher the quality / price / speed transfer. A 40W PD cable (that for example came with a 40W charger) will not deliver 60W even if the charger is capable of higher power and voltage. PD cables have the correct resistors or chips to negotiate their capabilities. Higher end non-PD cables are built the same way but just don't advertise it. That's why sometimes they work and sometimes they don't.

How about Casper the keyboard? 👻

Just curious... Any news on this front?

@tdm Fortunately I didn't revert my son's Pro1 back to stock. So I flashed the second boot.img hoping his camera would be fixed. But that didn't help. So I flashed the latest nightly both recovery and LoS. Camera still doesn't work. The rear camera times out on unknown error, black screen and then quits. One time it showed cannot start media recorder while trying out video recording. I also installed Open Camera, that just shows a black screen. The front camera does work in both apps. Anyway, I can't just reset the damned phone hoping his camera will work. Maybe tomorrow I will give it a

@tdm My son hasn't had any keyboard issues since flashing modified boot. Opposed to having issues everyday almost every minute. Yesterday he told me his rear camera doesn't work anymore and that the Pro1 has been suffering from reboots. So later on today I will probably flash both phones to stock (daughter already on it). I hope Wheeljack and I have convinced you to assume the problem has got to do something with the keyboard driver... I can't get them to hand over their Pro1 to me while mine is still in for repair. So, for now, I cannot continue help/investigation until mine re

Nope, it was crystal clear. Do not let get any amount of moisture get near the Pro1. It is very prone to damage-by-moisture. I think my lenses were either not aligned properly or just shifted slightly. That in combination with the f/1.8 aperture. Of which I am not sure if it's a LoS or general algorithm issue.

This is not due to a hardware defect. At least, not in general. The issue in my case is the fact that the software chooses an aperture of f/1.8. An this seems to be almost like a default. For those who don't know what this does, it limits the depth of field. If you work that out in distance, only those objects that are between 2.5m~2.8m/7.5f-7.9f will be in sharp focus. This is just an example. Focal length and sensor size matter a lot. But in general, f/1.8 limits DoF a lot! That being said, I have an example which makes me think there is a hardware issue with the lens. This picture was tak

My phone is back @ FxTec. But I will flash the other two still in this house this evening and let you know the results tomorrow or the day after that.

Doe your car have front window heating? If so this could be actively interfering with gps. And it could explain why it sometimes does or does not work. My gps only acts up after first boot. First fix can take way too much time, as in minutes. But after that initial fix (after a flash) the craziest thing I have experienced was inaccuracy. This was on both stock and LoS.

I have done this several times now by simple means of copy and paste in CMD/Shell. Hasn't gone wrong a single time. Just select the text in de OP and past it. Everything will run just fine. Do not forget that the package is still missing a file as tdm pointed out! You can find it on his site (link included below).

I think, given current global conditions, waiting 10 weeks is not that bad. FxTec is still a start-up, at least that's how I see it. This is a niche product, hand assembled craftmenship 🤣. It still hurts, but I am anxiously waiting for my Pro1 to be returned 🥰 .

I received a screen last Monday. this was two weeks later than expected. I would assume my screen was sent from the same new batch. So surely some people should have received their phone by now, right!?! 🙃

I just sent mine in on Monday. Should be delivered on Friday. So not looking forward to beg for my phone back 🤔. And all that for a working USB-C video out.

Take your time and enjoy life. I'm guessing it will be months before I have my phone back 😪😇