Please do. I'll be happy to use it..I will be compiling AOSP 12L, not Arrow OS, but I think it is without GApps.
Well, you can build AOSP, there is a guide on the Sony developer world website, but you have to have Ubuntu on your PC. But also @Sjll has a great starting point with his config file. I did find some guides, but for a normal user it's probably way too much. TWRP is easier though.Please do. I'll be happy to use it..
Also, where can I learn how to compile a custom ROM for devices without official support myself? The guides I found myself when searching were all either extremely outdated or lied about the "non-official" part.
Can you give me more detailed information about your problem? I might run into it as well.Hello, i am sorry to say, i was unable to build AOSP beacuse of a Java bug, but you can give it a try. You literally copy and paste commands from the Sony developer world website.
Couldn't you enlarge your swapfile to fix this?Yeah, Java has set a bad heap size, so Java is running out of memory, even though I have 32 GB of RAM. Tried every fix, didn't work.
Yeah, i made the swap file 120 GB...
Christ
No, you select the device XQ-AU52 (or 51) at i think step 5.Christ
Is the built AOSP image a GSI? The sony developer world guide doesn't seem to ever mention the codename of the device to build for anywhere
Edit: I say that as I read the very step that picks the name ...
Is it feasible to use a virtual machine for compilation considering ram limitations? I am likely going to screw up dependencies on my main PC since i'm using arch-based and my laptop doesn't have enough ramYeah, Java has set a bad heap size, so Java is running out of memory, even though I have 32 GB of RAM. Tried every fix, didn't work.
Yeah, it should be fine the compile speed will be a little bit slower, but you can pass the -j flag.Is it feasible to use a virtual machine for compilation considering ram limitations? I am likely going to screw up dependencies on my main PC since i'm using arch-based and my laptop doesn't have enough ram
i ended up hosting an ec2 instance on aws and built 12.0 however i forgot AOSP has very little features out of the boxYeah, it should be fine the compile speed will be a little bit slower, but you can pass the -j flag.
Yeah.i ended up hosting an ec2 instance on aws and built 12.0 however i forgot AOSP has very little features out of the box
I'm going to try building lineage 19, do you have any use for the system images if you couldn't build them yourself?
i will upload it to sourceforge
There is a guide on fat-tire.github.io, but you can take a look at Sjll's version of the manifests and see if there are any differences (it's in the main thread at the botton).i will upload it to sourceforge
is there a ""known good"" guide for building unofficial los devices? i found a few on google and my current plan is to sync the 19.1 branch for the los repo and combine it with device sources found in sonyxperiadev/local_manifests. i'm unsure if it's going to work.
Ok, thank you very much.sourceforge didn't like the size so i uploaded to drive insteadxq-au52-archive.tar.gz
drive.google.com
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot recovery
adb sideload <PATH OF GAPPS>
if you can donate me a 10 III