Email or username:

Password:

Forgot your password?
caleb

would anyone be interested in remote access to any of the following devices for the purposes of #Linux mainline development and testing? You'd be able to power cycle the device and boot an Android boot.img (kernel + dtb + ramdisk), I'm also open to using these devices in CI

* OnePlus 6/6T - #Qualcomm Snapdragon 845
* OnePlus 7 and/or 7 pro - #Qualcomm #Snapdragon 855 / sm8150
* OnePlus 9 Pro - Snapdragon 888 (sm8350), however i haven't yet found out how/if UART is exposed on this device.
* Google Pixel 2 XL, 3, or 3 XL - Snapdragon 835 (msm8998) or Snapdragon 845 (sdm845). (Only have one usb-cereal adapter so only one of these is viable right now)
* #Fairphone 2 - MSM8974
* #Fairphone 5 - QCM6490
* #LG G6 - msm8996 (if someone can find UART and find a workaround for the "charger wet" detection being stuck on)
* #Samsung j3 (j3xnlte) - some spreadtrum SoC - Only if you can find UART for me

I don't have things fully set up here but I'm trying to figure out what i should prioritise.

If any of these sounds useful to you then please get in touch with me! I'm especially interested in folks from the #LinuxMobile community, #Kernel maintainers, or anyone else with an interest in upstream Linux support on phones. Please have some kind of public presence in a related field and tell me what your usecase is.

* DM me on matrix - @ caleb:postmarketos.org
* Email me - caleb@connolly.tech

Please boost for reach!

#FOSSMobile #postmarketOS #Android #Embedded #BoardFarm #Testing #CI

15 comments
caleb

Just to note, if this interests you but the idea of figuring out how to build a boot.img to test is too much of a headache, I'm working on an (almost complete) feature for @postmarketos for exactly this purpose, so you can quite easily go from your local kernel artifacts to a device specific boot image with a ramdisk containing all the kernel modules, firmware, udev, and run specific scripts or pop a shell on boot.

penguin42

@cas I'm curious how you're driving them; don't the QCM's get upset and fall back into their emergency boot mode after a few failed boots?

caleb

@penguin42 all do yeah, the trick is to run "fastboot set_active a" on every boot, this resets the boot counter.

worth noting that i currently just have the op6/6t hooked up (pic related, details in alt text), and I'm only really confident that i could get the op7, fairphone, and Pixel devices up, the others I'm not quite so sure.

the new home for my device farm, a desk with the control PC to the right (pulling double duty as a gitlab runner). The phones are on the desk attached to a barebones PPPS USB hub, each one has a pi pico and a 4.4v buck regulator for control and power.
penguin42

@cas Oh, that's nice. Yeh I found out that qcom problem on my Find7 (main phone) the hard way when playing with kernels. What's the 4.4v for? Seems an odd value.

caleb

@penguin42 to replace the battery, both for safety and because it makes power cycling a sub 1 second process instead of a 15 second one

caleb

@penguin42 you might be interested in qbootctl if you're running some Linux userspace, it's a port of the Android bootctl HAL to handle slot switching and resetting the retry count from userspace

gitlab.com/sdm845-mainline/qbo

penguin42

@cas Does that let you recover if you've already got it into the worst recovery mode?

penguin42

@cas Actually; let me more precise - I mean the qcom boot mode that happens before fastboot.

caleb

@penguin42 ohh, EDL mode? There's a tool you can find on GitHub, but it requires having some vendor signed "loader" binary, many of these get leaked so you might get lucky..

It can be quite hard to figure out what's causing that, especially without serial access.

penguin42

@cas Yeh I think that's the scary one; I ended up having to reflash via a windows vm running a dodgy chinese reflashing tool; if I can already get to Fastboot I'm not too scared, it's when it doesn't get that far I worry.

Maksym Hazevych

@cas this sounds like a pretty cool service, I hope you'll tell us how you set that up.

caleb

@mks_h planning a writeup v soon. the tl;dr is a pico running this firmware (github.com/calebccff/pts-pico-), a PPPS USB hub and a 4.4v LDO with an enable pin. access is dome through CDBA: github.com/linux-msm/cdba

knuxify

@cas > #Samsung j3 (j3xnlte) - some spreadtrum SoC - Only if you can find UART for me

perhaps the carkit cable from wiki.postmarketos.org/wiki/Ser would work? this device uses the same muic as a few msm8916 devices which should have uart over microusb as seen in this table: wiki.postmarketos.org/wiki/Mic

caleb

@undefined i have this a go before but had no luck, I'm willing to give another try if someone is really eager (although tbh it might be easier to just send them the phone...)

Joshua Aspinall

@cas I wish I was clever enough to need them to work on. Very cool thing, hope you get some interest and some use. 😃

Go Up