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?

Just gave this a try, looks like they’ve made some changes. I can sometimes get 5G, others it’ll only do 2G/3G/LTE.

@flohack ah thanks for that, I’ll stick to Halium for now then!

@keneda that’s going to be the solution.

I know it doesn’t make sense, but AT&T doesn’t automatically update that you’re using a new device when you swap the SIM to a new phone. If it’s not updated in their system manually it doesn’t change.

I have a OnePlus 7t Pro coming in later this week or early next week and can try it out again (also curious if this will let an unsupported device use 5G).

@keneda said in OnePlus 7/7 Pro/7T/7T Pro with mainline kernel?:

I red somewhere here that native linux devices like Pinephone don't have same device "tree" or something related with partitionning, bootloaders and thing like that, and that those device can't run the same way that "pure Linux" ones do, so question would be rather is it possible to do a halium mainline Linux kernel porting of uTouch.

I thought it was the opposite— mainlining a device allows it to run like a normal Linux device.

@keneda said in OnePlus 7/7 Pro/7T/7T Pro with mainline kernel?:

Anyway problem is hardware device drivers that you must extract from vendor linux kernel and adapt to mainline linux kernel i imagine.

Yeah, that’s the difficult part, but someone has already done it (at least partially, I don’t know how up to date the postmarketOS page for these devices is.

The postmarketOS wiki shows that someone has mainlined OnePlus guacamole and hotdog devices. Could we put UT on top of the mainline kernel rather than using Halium? Would there be any real benefits to doing so?

I think I saw that this is how PinePhone runs UT, and it allowed for wider compatibility with programs?

@cornonthecob if you haven’t already done so, it might be helpful to talk to the team that ported the 3a. It looks like the person that did the kernel is friedldotme on GitHub