Can someone create a subforum for these devices? I'll have one in a couple weeks and would like to work on getting docs updated and need a place to discuss them. Thanks!

I've had a couple hours to play around with it and the maturity seems accurate. Most features work, currently just having issues with GPS, flashlight, and data/mms, but I think data/mms is an issue with my APN settings as the SIM in slot 1 is recognized and I can do calls and sms without issue (haven't tried slot 2).

There's a couple really annoying issues though. First, the keyboard backlight doesn't work. The LED for capslock works fine, but only a couple keys by it are lit if it's on and everything else is off. Second, the on screen keyboard doesn't disable if the phone is open to expose the hardware keyboard, and it blocks almost all of the screen if you're in landscape. I'm having to manually enable/disable the on screen keyboard when I don't want to use the physical keyboard. If there's a sensor that can act as a trigger to toggle both of these I think it'd be a really solid device.

I'm going to work on getting the device page updated either tonight or later this week.

I had the same problem; many sellers were just straight up lying about items and saying they were factory unlocked when they were really sim unlocked VZW models. I recommend finding listings of single devices that have the IMEI listed and putting the IMEI into Verizon’s BYOD tool which will specify if it’s a non-VZW pixel.

looks like android-tools is also gone

simg-tools was deleted from the AUR on Dec 31, 2021. This has lead to halium-devel AUR package failing.
It looks like simg-tools is a combo of simg2img, append2simg, img2simg, and simg2simg. Are all of these needed, or can I just compile some of them?

I've had a couple hours to play around with it and the maturity seems accurate. Most features work, currently just having issues with GPS, flashlight, and data/mms, but I think data/mms is an issue with my APN settings as the SIM in slot 1 is recognized and I can do calls and sms without issue (haven't tried slot 2).

There's a couple really annoying issues though. First, the keyboard backlight doesn't work. The LED for capslock works fine, but only a couple keys by it are lit if it's on and everything else is off. Second, the on screen keyboard doesn't disable if the phone is open to expose the hardware keyboard, and it blocks almost all of the screen if you're in landscape. I'm having to manually enable/disable the on screen keyboard when I don't want to use the physical keyboard. If there's a sensor that can act as a trigger to toggle both of these I think it'd be a really solid device.

I'm going to work on getting the device page updated either tonight or later this week.

@lakotaubp thanks! The x can definitely wait, it's supposed to be out in a couple weeks but that's been the case for around a year now. They've been doing monthly indiegogo updates and the last one was at the end of December so I imagine one will be up soon that may provide some answers.

My Pro 1 is out for delivery and I've got the installer downloaded and ready to go. I plan on installing right away, and will get to testing all the features and getting the status updated. Hopefully that progress bar is accurate.

Can someone create a subforum for these devices? I'll have one in a couple weeks and would like to work on getting docs updated and need a place to discuss them. Thanks!

I had the same problem; many sellers were just straight up lying about items and saying they were factory unlocked when they were really sim unlocked VZW models. I recommend finding listings of single devices that have the IMEI listed and putting the IMEI into Verizon’s BYOD tool which will specify if it’s a non-VZW pixel.

@flohack would it be possible to do this with another aosp based rom that has android 10 support, or is there something about lineage that makes it a necessity?

@totalsonic have you tried relocking the boot loader? If you have a branded version, keep the token somewhere safe so it can be used later if needed, then boot into fast boot and run

fastboot oem lock

@flohack thanks, will do. I don’t have a ton of experience with this but will gladly help out as much as I can with Halium 11 when y’all are ready to get that going.

I want to build Halium 10 for the OnePlus 8 (instantnoodle). It was released with android 10.5 and there’s an unofficial TWRP image available that’s working mostly fine, but lineageOS support wasn’t added until 18.1 (android 11). Is this going to be an issue?