I had the wrong IP in the config, probably was right before I changed it. That might have been on the day I stayed up till 7 AM. And I’m pretty sure the already compiled version has WireGuard included, unless somehow it flashed the version I compiled, doubtful. Their docs don’t have enough information to build it, not the newest version anyways.
And the battery probably shouldn’t be draining while doing nothing from 100% to 54% in around 7 hours.
I might have something running causing the problem. Or I need to reflash completely, including wiping userdata. Might be Libertine causing the problem. Or maybe using a VPN does.
No SIM card, WiFi was on, but wasn’t connected when I woke up.
Trying to format TWRP for it now, why not? Got nothing better to do. At least you can mostly find the info needed to do so if you look hard enough. I won’t use an online build system.
If you copy the build.prop or whatever the name of the file was from the dump or phone, and rename to system.prop, you still have to do work. You’ll get a lot of “error: found duplicate sysprop assignments:” errors. Easy solution, remove the lines from system.prop.
I doubt TWRP will boot the first successful compile, I have no idea what I’m doing.
According to this, you don’t need the entire system.prop file. But it’s outdated, cause the vars changed.
ro.product.system.brand=alps
ro.product.system.device=k65v1_64_bsp
ro.product.system.manufacturer=alps
ro.product.system.model=r1
ro.vendor.mediatek.platform=MT6765
ro.system.product.cpu.abilist32=armeabi-v7a,armeabi
Maybe that’ll work for system.prop. And maybe I should reboot my phone, it’s in fastboot, can mess with Libertine, might have an option to make it freeze or something.
Good luck using a firewall in Ubuntu Touch, I just block the internet by doing that. I just set SSH to run on the VPN IP. And no SSH wasn’t running while I was sleeping, stopped it just in case.
Good news, Ubuntu Touch won’t boot. Recovery boots though.
rsync: [sender] link_stat "/home/uranus/mtk/Auto-Twrp-Builder/out/target/product/k65v1_64_bsp/root" failed: No such file or directory (2)
No that folder doesn’t exist. That’s where I’m at with compiling TWRP. And that Auto-Twrp-Builder is crap, no idea what the point of the convert.sh script is. And the other part, you don’t need their python script, you can run with python3 -m twrpdtgen <path to image>.
Might need to use the magic reset button, shutting down from recovery didn’t fix it either. Hmm, might need to wait longer, or reflash it again. And it booted this time, turned it on without plugging in USB, and waited before doing so.
Nothing is using much CPU, so probably not Libertine.
“error: +out/target/product/k65v1_64_bsp/boot.img too large (107126784 > 33484800)”
LOL. I missed a step from this guide, but now it’s way too big.
Damn only around 20 GB free on my laptop’s drive. And my entire folder is 200 MB or so.
Perhaps don’t use the vendor partition to get the vendor folder’s contents. LOL. I got it from the super img.
Hmm one guide says you don’t need the lib64 folder. Trying to find the guide updated for Android 12.
Will leave Vendor folder empty, might mount it anyways.
Added “ro.property_service.version := 2” to the system.prop file, I got the value from adb with Ubuntu Touch recovery, adb shell getprop will tell you. Also changed “PRODUCT_SHIPPING_API_LEVEL” to 32.