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

I guess, Yay, you got it working! 😄

For what it's worth, I have been using TP-Link for several years. They have always treated me well and usually are able to run OpenWRT. I bought an Archer C7 a few months ago because my ancient Netgear router died, and it has been fantastic. Currently on Evil Amazon for $65 or Office Depot for $69.

Have you installed all updates?

I believe holding volume-down while powering on the device will bring up the fastboot menu. In there, you can use the volume keys to select recovery and then press power to boot. Note that if you see stock recovery instead of Lineage recovery, you are booting to the wrong slot. So switch slots using fastboot and then boot into Lineage recovery, wipe data, and reboot.

I am still kinda sad there is no official silicone case (or third party) and we have to DIY from Huawei P20 Pro cases. lmao

Just thought I'd resurrect my solution for all the newcomers. I hate cases and, going back to my Palm PDAs, have never used cases. However, the back of the Pro1 is pretty slick. So I put a black matte textured skin on and it gives it just enough grip that I never drop the phone in the first place (haha famous last words. 😄 ) The skin is very snug and months later shows no wear or coming loose at the edges. Perfect solution for me, YMMV.

Good idea. I'll follow your suggestion while also making sure i put a soft thick rug under the sofa!

I've done the same thing. I've found that a strip of Duct tape across the back and one side works wonders in solving this issue.

I have NOT had fingerprint issues on Lineage since a much earlier test-version. I have the sort of 'opposite' phenomena on Stock: Sometimes it forgets the fingerprints, but a restart and enter of the password and they are back. (this was improved with the July update).

Sorry didn't explain properly 😄 but as @DieBruine said sometimes its using the wrong driver just ensures it's using the Google one. I noticed windows sometimes finds a driver and it's not compatible.

Ordered in September last year; shipped Jun 5th from HK, then was stuck at Zollamt for two weeks before being delivered by FedEx finally.

(FYI I see no fingerprint issues here on 20200803 Lineage)

Delivery scheduled for Wednesday before 12:00 (to Normandy, France).

Mine arrived, yay! 🙂

It is used for collecting depth information. It can not be used to actually take a picture. Depth sensors usually has a little effect to the picture quality now days.

The FinQWERTY layouts are made for Stock. They will work somewhat on LOS too, but with some minor quirks. E.g some of the added stuff like half and Mu will not work (or at the least I has not guessed how to...)

Ich würde dir das Pro1 abkaufen.

If it's a DHCP issue, you could try fixed IP. Under WIFI settings on the phone apply the IP, subnet mask, gateway and DNS you used for the reservation. If you don't know what that is and/or cannot find it. Just use the IP, subnet mask and use the router's IP address as default gateway. For DNS use 1.1.1.1. That's an easy way to rule out DHCP issues. You can change these settings when you modify a known/saved WiFi network on your phone. BTW, your basic logging on the router should at least show password incorrect/rejected and a DHCP request from your phone...

I can try to investigate. Send me a logcat in PM. Also, if you have root access, a kernel dmesg would be good.

For the record, I don't seem to have this problem on LOS either:

QWERTY 2043 (just arrived today)

Careful with that. Some in here had locked it and could not unlock without help. Only re-lock if you are sure that it is the official stuff that is running, and it might not be after the failed attempts.