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!
@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?
@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.
@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.
@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
@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
@cas Does that let you recover if you've already got it into the worst recovery mode?
@cas Actually; let me more precise - I mean the qcom boot mode that happens before fastboot.
@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.
@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.