Leaderboard

https://www.thingiverse.com/thing:4562958

I'm sure going to do the opposite when mine arrives. No coffee for me when unpacking it lest I drop it on the floor or break it in some never-before-thought-possible way. Heck, I probably should have some kind of calming drink before getting to unpack..! 😁

It's here but I am too scared to unpack it. Kidding, just finishing my coffee first 😄

Official lineage does OTA updates in the background like stock. No cables needed. But it can take nearly an hour because the updates are full, not incremental. I'm working on incremental support.

Thank you for the answers. They helped me to fix the problem. Now LineageOS works fine. :)

For those using languages other than English and German on LineageOS, it would be possible to create additional keyboard maps in the kernel to match the expected keyboard layout for your language. If anyone is interested, let me know and I can work with you.

As I stated in the other topic. When you used the instructions on Lineage, the unlock command should be fastboot flashing unlock. I just received a Pro1, booted it and it was already unlocked. So there was no need for that. To help you figure 💩 out, I used a different clean laptop. I installed everything as described on https://wiki.lineageos.org/devices/pro1/install. After installation and connection via ADB, I changed the driver manually to "Google Nexus ADB interface". I don't remember which one was selected, but it sure as Hell wasn't Google Nexus ADB interface. So as _DW_ stated, ch

@Alex the stock software has known issues, including the ones you mention. The OTA updater is an app from a company called AdUps. It has known problems. The usual workaround is to clear the app data for it and retry. I believe the latest update (7/7/2020 I think?) fixes at least the WhatsApp issue. And finally, you may want to give LineageOS a shot. Most or all of these issue are fixed and it will be nicer than stock in other ways also.

All things being said, yes haha. Obviously a little confused, but this does mean I don't have to purchase a hotspot or a new router (thank the gods). If anyone has any problems with their wifi connection, feel free to dm me! (I won't help, but I will eat ice cream and sulk with you)

Alright more updates because I kind of find this fascinating (though I do not understand it): 1) Phone does not connect to home network (2.4 or 5), WPA2-PSK [AES] (with an alphanumeric password for all examples) 2) Phone does connect to home network (2.4 and 5) with BOTH WPA-PSK [TKIP] + WPA2-PSK [AES] 3) Phone does connect to an unprotected network (2.4 and 5) Hopefully this detail can enable someone smarter than I to figure out exactly what is going on in the background.

Keep pressing volume down+power and do not let go until you see the Fastboot mode (should take about 10 seconds). After that start all over again. fastboot devices (to check whether it is connected) fastboot flashing unlock (error already unlocked) fastboot flash boot lineage-16.0-20200803-recovery-pro1.img Volume Up + Power Perform a factory reset in Recovery Apply update via ADB sideload adb sideload lineage-16.0-20200803-nightly-pro1-signed.zip Reboot to Recovery if you want to flash gapps adb sideload MindTheGapps-9.0.0-arm64-20190615_0

Oh sorry, yeah. Nightly 16.0. I had a smaller "problem" with Gapps Nano signature not getting validated. But I could install it anyway, Magisk followed afterwords. It's a solid system now. Love it 🙂 Battery is surprisingly long lasting.

Fiddling with the odd opening the first times I recommend a comfy chair or a sofa. So even if it should pop out of your hands, it should be safe.

@Alex You are not supposed to update on such a low charge.. Give it at least 60%.

I would be very happy with half a bumper for just the back tailored to Pro1-spec instead of P20 Pro 😑.

I mean my password is just "password1234letmeinthefrontdoor" so I can't see how that would be a problem haha. But yes I'll have to fiddle with it more. Appreciate all the help and input so far, this community makes the pain a little more bearable haha.

The Lineage keyboard implementation is entirely different from stock. So the FinQwerty data is not really useful. But this should not be hard -- there are likely only a couple of keys that need to be changed. My paypal is https://paypal.me/tdmcode

Then it is most likely a hardware issue. Try different cables and a different USB port, and even a different host PC. Many folks find that host USB-C ports do not work properly, they must use a host USB-A port.

Update for the community (though I haven't heard of anyone with the same problem): With help from @tdm, I ran a logcat of the phone attempting to connect to my internet and received the following error: 08-03 12:07:47.526 4404 5042 D WifiService: recentFailure: Association Rejection code: 0 To the best of our understanding, we think this means the phone cannot associate with my router. After looking around online it seems someone else has had the same/similar (?) issue with their Android phone, though not a Pro1. Here is the link for anyone interested: https://android.stackex

Yeah, well with less than 2000 devices out there, we won't get any cases soon. Which is pretty strange since I'm pretty sure the factory should have some shells they could hand-off to the any of the manufacturers within a square mile...

Just for data purposes, my Pro1 does fine on my Netgear router, connected to 5Ghz. My router is model number R6400 v2, one of the Nighthawk line. So it doesn't appear to be the brand of router.

Thanks for your answers! Yeah, what confused me was that it was already unlocked. As most tutorials seemed to require you to unlock it first. Ive tried to flash LineageOS anyway and it worked well. Have the newest testing version running. 🙂

Try booting into recovery and wiping your data. Especially if you forgot to do this before.

Old farts like me that had a Nokia N97mini many years ago, opened it immediately. BUT I remember having trouble back then too. The problem is that we intuitively want to do an even horizontal push, like a simple slider. But that wont work, It has to be a down and up arc. Or just lift the back edge. Either alone or in combination. I most often lift the back with the index finger after triggering the fingerprint, while the thumb grabs the front of the screen. Like this

If you order and use a bumper case, for a P20 Pro, you just have to touch it gently and it will slide open...

Delivered 45 min before time, perfect condition. Thanks FedEx. I just unboxed it and I definitely like the amount of force that is required to open it so it doesn't slide open by itself when in your cargo pants. The trick is that you shouldn't try to slide it open horizontally with your thumbs on the screen (what may at first seem intuitive and was built into e.g. the Blackberry Priv) but instead by applying just a bit of force from the side on the edge of the screen in a slightly upwards manner. It just took me like 15 sec to figure out how to do it with one Hand only. So keep trying and

Try different cables and ports. Also try reinstalled the ADB driver.

Add another $200 for not being Google and getting a huge discount for selling millions of devices

(Well it "works" as such for qwertZ too, but have some quirks, as it is made for Stock Android)

I would try fiddling with the router settings, and see if the Pro1 is more happy with something else, E.g. what channel it is using. I once had a problem with an internet radio, that did not connect, and it proved to be a character that I could select, but did not work in passwords with that device... (It was something ordinary like ! or $ forgot what it was). So many small quirks with WiFi.

Hey, so my phone arrived. But I can't seem to run the update. My last version is QX1000_EEA_20200306124530_20200306-1247, security level patch 5. Sep. 2019. Checking on updates just throws me an error that it can't reach fota server::443. I do have a functional WiFi connection. How do I update my phone now? After retrying 10 times, it works now.. 😄 The other issue still remains. Also I have enabled development mode, but I can't enable OEM-Unlock. It's greyed out, already "activated" and is saying that the bootloader is already unlocked. Running fastboo

Yeah that's expected @tdm says why in another post somewhere. Glad you got it sorted lineage is way better than stock 😉

That would be great😃 Can you just copy the FinQwerty Finnish/Swedish on qwertz layout? I'm gonna flash my phone to LOS tomorrow or the following days, is there a donate button somewhere for your awsome work on LOS build?

What security option are you using on your router? I'm assuming WPA@-PSK [AES]. I don't know what the Pro 1 does with the other options. Just grasping at straws. 😉

For users other than English and German, note... https://community.fxtec.com/topic/3050-yellow-arrow-key-different-usage-in-stock-and-lineageos/?do=findComment&comment=51003

Got my phone today 😍 But i'm at work the whole evening ☹️ It was in chinese when i started the phone... Ok, gonna try the Finnish/Swedish layout on LOS to see how well it works.

My bad... I hope. I forgot to run adb root 😅. Now I will reboot and hope everything is fine... Give me a couple of minutes. After a reboot my fingerprints are gone again. Unable to find nor delete /persist/data/fingerprint. Which was completely my mistake. I forgot to run adb root 🥴 rm * /persist/data/fingerprint did the trick for me... Thanks anyway for the response. By the way, are there plans to enable unlocking before boot back in LOS? I think it was removed in 14.x.

For a device being viable, the manufacturer needs to cover both unit costs and fixed costs. The more units you sell, the less are the fixed costs noticable per unit. The fixed costs include: * R&D costs * Certification costs * Manufacturing preparation costs – if you want to mass-produce PCBs, plastic components etc., you need to produce some masks, which also isn't cheap. Once this is done, I see some effects: * More SKUs. There are at least 2 different (QWERTY and QWERTZ), which can make the logistics more complex. After all, F(x)rec has reportedly p

Yessir, I certainly did. But I don't think it does what you expect. I have no way to correlate the system fingerprints with the vendor fingerprints. All the script does is check if the system data has been wiped. If so, it wipes the persist data. Note that removing all fingerprints does not (currently) count -- the script only checks for the presence of the system fingerprint file, not that it is empty. But you still have the issue of the vendor HAL never deleting fingerprints. So, if you enroll more than ten fingerprints without deleting the persist data, you will always run

When mine went through the Memphis Hub it landed in Alaska first and I'm pretty sure it went through customs there and not Memphis. Memphis is the main routing super-hub for FedEx, but mine was there mere hours before getting to me in VA the next day. But that was December 2019, a whole different world. Hope it is just delayed due to processing/manning issues and not having trouble with customs.

Well I'd be curious if its a quirk with your router, or a problem with phone. So I'd go test some public wifi, wherever you go, work friends/family library fastfood walmart etc. And if those work, get a new wifi router, some are super cheap. But I assume other things work with it so weird, more likely your phone is broken.

If you want FinQWERTY layouts for Lineage, you could probably ask the author, in the past he was quite responsive when developing layouts for stock.

You did not tell your router to reject new/unknown MAC adresses? Just asking...

Since our phones are on the way I took the liberty of unpacking the Snakehive wallets as suggested (by Slion) in this topic. Pffff those bumpers are a real piece of 💩. First of all, the phone doesn't fit very well. Apart from that, it's the lowest quality silicone I have ever dealt with. I started modding all the current and required holes with a Dremel. These bumpers have some flex! It took me hours to mod them. But, I still don't trust them. The phones come out to easily. So, I've ordered the Ebay bumper noted earlier by EskeRahn, which I also purchased previously. For the time being I

Possibly failure to get a DHCP lease. Can you tcpdump on the router?

To do a full nandroid backup. I like to change some settings, icons, play with some apps and a backup will help me to do that, to be on the safety side. TWRP + Tasker are the main reasons why I use Android. Backup and modify/automate 🙂

Being able to do a Nandroid Backup (which is not so much a new reason as the result of having decrypt).

Exactly. All devices are made with a number of decisions / compromises. Different people got different usage patterns, different hand size, More or less sharp vision.... etc So we will never have a single device that is optimal for everyone. But hopefully a wide range of products fitting a wide range of people.

Sound being borderline unhearable. I installed LineageOS and very briefly tried the camera: WOW WTF, it's miles ahead of the factory camera!

some frogs are green