Related
There are several threads on Moto's support site with dozens of people asking for 64-bit on the G4 Plus.
Well we can now run 64-bit ROMs on our device.
The 64-bit architecture is much more streamlined, more energy efficient and much faster.
There's an app compatibility benefit i.e some apps are built to run pretty well or only on 64bit processors.
Well currently we have to run app_process (system server) as 32bit, mainly cause of sensors non working actually with a 64bit system server ( Thanks to @vache for pointing this out )
What will you need:
Device Tree : https://github.com/TeamButter/android_device_motorola_athene/tree/lineage-15.1-64
Kernel Tree : https://github.com/TeamButter/android_kernel_motorola_msm8952/tree/lineage-15.1-64
Vendor Tree : https://github.com/TeamButter/proprietary_vendor_motorola/tree/lineage-15.1-64
Downloads Links:
64-bit TWRP 3.1.1-0 : https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download ( Thanks to @tywinlannister7 )
64-bit LineageOS-15.1 : https://drive.google.com/file/d/1NnhMle31msyk1i3_lwE2NVRdP9PYQLRa/view?usp=drivesdk
Got a query? Ask in the thread.
Regards
XDA:DevDB Information
ARM64 Development on athene, ROM for the Moto G4 Plus
Contributors
Nikit, rajatgupta1998
ROM OS Version: 8.x Oreo
Version Information
Status: Alpha
Created 2018-04-09
Last Updated 2018-11-18
Nice work. Seems like sources aren't up yet on GitHub.
Long live Athene...
Nice work. Good for athene users too now.
PS:- @vache ftw
Will the 64 bit TWRP be able to flash 32 bit ROMs?
arm64 8.1 GApps
8.1 arm64 GApps.
Download:
https://drive.google.com/file/d/13S4Oo0RpxB5ox3J-oA2J08C8wEsIbEN4/view?usp=sharing
Courtesy @Dreamstar
---------- Post added at 05:56 PM ---------- Previous post was at 05:52 PM ----------
zeomal said:
Will the 64 bit TWRP be able to flash 32 bit ROMs?
Click to expand...
Click to collapse
yes
zeomal said:
Will the 64 bit TWRP be able to flash 32 bit ROMs?
Click to expand...
Click to collapse
yes. I tested.
I'm new to this 64 bit on Android ROMs...
What differences might I notice?
Thx....
Long live athene
hacker1911 said:
What differences might I notice?
Click to expand...
Click to collapse
HDR+ on Google Camera for instance. Any app that requires ARM64, actually.
Dreamstar said:
There are several threads on Moto's support site with dozens of people asking for 64-bit on the G4 Plus.
Well we can now run 64-bit ROMs on our device.
The 64-bit architecture is much more streamlined, more energy efficient and much faster.
There's an app compatibility benefit i.e some apps are built to run pretty well or only on 64bit processors.
Well currently we have to run app_process (system server) as 32bit, mainly cause of sensors non working actually with a 64bit system server ( Thanks to @vache for pointing this out )
What will you need:
Device Tree : https://github.com/TeamButter/android_device_motorola_athene/tree/lineage-15.1-64
Kernel Tree : https://github.com/TeamButter/android_kernel_motorola_msm8952/tree/lineage-15.1-64
Vendor Tree : https://github.com/TeamButter/proprietary_vendor_motorola/tree/lineage-15.1-64
Downloads Links:
64-bit TWRP 3.1.1-0 : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing ( Recovery Mandatory to flash for 64bit ROM )
64-bit LineageOS-15.1 : https://drive.google.com/file/d/1mXpjp22ds_rs9noDfGZNiUrj5Vn3lRc9/view?usp=sharing
Got a query? Ask in the thread.
Regards
Click to expand...
Click to collapse
Can I flash the TWRP 64-bits in TWRP or I will need a PC?
This is awesome thanks hope to see more 64bit ROMs in future
Sent from my Moto G4 Plus using Tapatalk
Luis FSS said:
Can I flash the TWRP 64-bits in TWRP or I will need a PC?
Click to expand...
Click to collapse
U can flash via twrp or even if u have root and twrp manager theoretically.
So it may work bro
But theoretically, twrp 3.2 should be able restore backups also??
cool_sid said:
U can flash via twrp or even if u have root and twrp manager theoretically.
So it may work bro
But theoretically, twrp 3.2 should be able restore backups also
Click to expand...
Click to collapse
Thank you
Guys, what's all this for? Can someone explain?
Thanks
Didn't got the last para ... Can any one explain it
Sent from my [device_name] using XDA-Developers Legacy app
EmiAndroid said:
Guys, what's all this for? Can someone explain?
Thanks
Click to expand...
Click to collapse
Ideal thread to ask this question is the Q/A thread and not in development forum but since u have asked it here.
There are two architectures for CPU to run on, 32 bit and 64 bit.
SD617 which athene has supports 64bit also but due to some reason, moto made it run 32 bit
Now @Dreamstar has done an awesome job and made rom which is 64 bit.
Now u can u all apps which run only on 64 bit devices like the google camera with HDR+
Hope this helps. For more details, google is your friend. Its great work, try it.
Does 64 bit roms are more battery efficient and faster that 32 bit roms?
Does this ROM have the same bugs as 32 bit lineage 15? Camera, chopchop, etc. ?
webnorka said:
Does this ROM have the same bugs as 32 bit lineage 15? Camera, chopchop, etc. ?
Click to expand...
Click to collapse
Yeah those exist and you can't change RGB values using Kernel Adiutor to prevent screen burn in
Sent from my Moto G (4) using Tapatalk
harshal2234 said:
Does 64 bit roms are more battery efficient and faster that 32 bit roms?
Click to expand...
Click to collapse
Plz ask yourself.... Is this the right thread for such questions? Ask these questions in Q/A thread
And yes 64 bit is obviously theoretically better than 32 bit as it allots 64 exabytes instead of 32 for each program to run
So ur games work better on 64 bit (theoretically)
Ive been enjoying Resurrection Remix [Unofficial] rom and was wondering if they or any other rom for the Xperia Z5 P will support Oreo?
There is no kernel so unfortunately no
tset351 said:
There is no kernel so unfortunately no
Click to expand...
Click to collapse
???
zacharias.maladroit said:
???
Click to expand...
Click to collapse
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.
tset351 said:
Well there are no kernel sources nor binaries, blobs etc. so I guess there will no custom rom be available anytime soon but please correct me if I'm wrong. I would be glad to have Oreo on my Z5P.
Click to expand...
Click to collapse
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).
Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time. And please don't answer questions if you don't know what you're talking about (at least write that you're inexperienced).
Click to expand...
Click to collapse
I am a very inexperienced person.
For MSM8994 platform there is only 3.10 kernel sources available, at least on sony's developer page. On open devices resource list, there are binaries for Z5 premium for 5.1, 6.0, 6.0.1, 7.0 and 7.1 but unfortunately no 8.0 or 8.1. And well, developers can take their time - as long as they want because I don't use that cell phone anymore and I won't expect any custom Rom changes anytime soon especially for a 2015 Device which had very less development going on since its launch.
But once again, I am very inexperienced.
Nik0laTesla said:
The developer seems to be busy so allow me to answer (though I'm not that experienced). I'm pretty sure that Sony always releases it's phone's kernel sources. Phone hardware doesn't change from an update so when the sources are released they can be used to create a kernel for any android version (basically developers need access to unique hardware). Blobs are like closed-source kernel modules. They're provided with the kernel source but the manufacturer doesn't want them to be copyrighted or tampered with. So I'm sure that Oreo will be available on your device, just give the developers some time.
Click to expand...
Click to collapse
Ok, sorry I got a bit mixed up in the devices :laugh:. Either way Snapdragon provides up to date documentation on their SOC's (which is the most important hardware component on the device) so developers should still be able to provide Oreo. And you are right the Z5 premium is an old device and support usually drops as soon as the developer gets rid of that device. But it's weird how much attention different devices get. For example I have a Oneplus X (SD801, I know it's ancient) (didn't even get Nougat) and there are multiple Oreo 8.1 ROMs available.
Any chance we'll see Pie on N7? Even doable?
xenokc said:
Any chance we'll see Pie on N7? Even doable?
Click to expand...
Click to collapse
Let us all hope and Pray....
The way its getting delayed, i doubt pie will come (that too fully stable) for our old device. Last @flex1911 said that Lineage is almost fixed. Maybe be should ask him and motivate more.
abhifx said:
The way its getting delayed, i doubt pie will come (that too fully stable) for our old device. Last @flex1911 said that Lineage is almost fixed. Maybe be should ask him and motivate more.
Click to expand...
Click to collapse
Yeah, I've been working last week on some stuff for Flo, but unable to test since my USB is dead. I got one guy to do it, waiting for him.
I've got no solder now, so can't fix my flo yet. Gonna do it later.
flex1911 said:
Yeah, I've been working last week on some stuff for Flo, but unable to test since my USB is dead. I got one guy to do it, waiting for him.
I've got no solder now, so can't fix my flo yet. Gonna do it later.
Click to expand...
Click to collapse
Apologies for naivete, I just repo sync'd Unlegacy Android Pie thinking that since Flo was in the branch that it was already possible just no one was compiling it.
Again, just a brand-nubian banging my head against obstacles until they give, is it not possible to take say a Marlin P kernel and run it through LazyFlasher to make it Flo friendly?
LazyFlasher is a custom kernel flashing tool designed to make it easy to dynamically modify ramdisks and inject kernel binaries into the current boot image.
It's the swiss army knife of kernel flashing for use in Team Win Recovery Project.
The intent behind it was to allow a 1 custom kernel fits all approach, where your users can flash single zip on any ROM for a particular device,
allowing your kernel to be compatible with the vast majority of custom ROMs already out there. It takes away the pain of building custom boot.img
for each and every variant a user requests and puts it into 1 low maintenance intelligent universal flashable zip.
Click to expand...
Click to collapse
Thank you for persevering and keeping this awesome device awesome.
Here is an android pie ota package for nexus 7 (flo):
https://forum.xda-developers.com/showpost.php?p=78575088&postcount=1811
Dummy question - how to flash that OTA package?
I have that doubt, until today there is no ROM that can be installed on the J2 which includes Android 7 or at least one Android 6 ROM that is based on AOSP?
Right now, there isn't any AOSP or Nougat-based ROM for the j2lte. Tomorrow, who knows?
TBM 13 said:
Right now, there isn't any AOSP or Nougat-based ROM for the j2lte. Tomorrow, who knows?
Click to expand...
Click to collapse
but I wonder why the other model of the J2, the 3G if it has several roms based on Android AOSP or based on Android 7.1.2 if both have the same processor, greatly changes the shape of its code to make it impossible to use with the J2LTE ?
SharkyBeAre said:
but I wonder why the other model of the J2, the 3G if it has several roms based on Android AOSP or based on Android 7.1.2 if both have the same processor, greatly changes the shape of its code to make it impossible to use with the J2LTE ?
Click to expand...
Click to collapse
You mean the J200H? It has a completly different processor.
TBM 13 said:
You mean the J200H? It has a completly different processor.
Click to expand...
Click to collapse
CPU-Z is my phone (J200M) <J2LTE> and the other screenshot is information taken from the internet that says that the J200H has the same processor as the J200M - J2LTE. Who is lying, Cpu-z or the page where I consulted the information
This is another page that says the J200H has the Exynos 3475.
https://www.sammobile.com/samsung/galaxy-j2/specs/SM-J200H/
More Screenshots of my J2LTE
SharkyBeAre said:
This is another page that says the J200H has the Exynos 3475.
https://www.sammobile.com/samsung/galaxy-j2/specs/SM-J200H/
Click to expand...
Click to collapse
Take a look to this, from https://forum.xda-developers.com/galaxy-j2/development/lineageos-samsung-galaxy-j2-t3659657
Will it work on j200g/gu/BT/F??
Naah.. It won't boot as j200h is sprd but others are ****ty Exynos
Click to expand...
Click to collapse
SharkyBeAre said:
More Screenshots of my J2LTE
Click to expand...
Click to collapse
TBM 13 said:
Take a look to this, from https://forum.xda-developers.com/galaxy-j2/development/lineageos-samsung-galaxy-j2-t3659657
Click to expand...
Click to collapse
Its actually only J200H/DD that is based on spreadtrum SC8830. J200H and J200H/DS is Exynos-based.
afaik, J200H/DD is only sold in some countries like India or here at Vietnam. The rest is available worldwide and therefore more recognizable by most people.
e: further info, codename for J200H/DD (Spreadtrum) is j23gdd, whilst J200H(/DS) (Exynos) is j23gxx.
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Prove N. said:
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Click to expand...
Click to collapse
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Prove N. said:
Its actually only J200H/DD that is based on spreadtrum SC8830. J200H and J200H/DS is Exynos-based.
afaik, J200H/DD is only sold in some countries like India or here at Vietnam. The rest is available worldwide and therefore more recognizable by most people.
e: further info, codename for J200H/DD (Spreadtrum) is j23gdd, whilst J200H(/DS) (Exynos) is j23gxx.
e2: I can always try to build blindly, considering on5 pro (on5prolte / same Exynos chipset) has Lineage fully functional.
But, *also* considering the lack of time and the mess of J2 Prime RIL I'm making, I cannot guarantee a fully functional one here :<
Click to expand...
Click to collapse
TBM 13 said:
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Click to expand...
Click to collapse
than? Does that mean they are trying to work on a LOS Custom Rom for the J2LTE? Forgive me that you don't understand your communication language in front of cell phones, but what I understand is that you are working to get AOSP in J2LTE?
SharkyBeAre said:
than? Does that mean they are trying to work on a LOS Custom Rom for the J2LTE?
Click to expand...
Click to collapse
No, they gave up.
SharkyBeAre said:
you are working to get AOSP in J2LTE?
Click to expand...
Click to collapse
I'm trying, but don't expect something, i'm noob at this.
TBM 13 said:
No, they gave up.
I'm trying, but don't expect something, i'm noob at this.
Click to expand...
Click to collapse
I trust that something good will come out of all the tests you can do being a noob, hopefully, because Samsung's system seems to me the worst, and it takes up a lot of space.
Thanks for all
TBM 13 said:
Exynos3475 developers already tried. They never managed to get to the boot animation and make logcats work. When they tried the same j2 tree on the on5prolte, it booted without problems.
Basically, the o5prolte got LOS 14.1 with the j2lte device tree.
I managed to get working logs and boot animation in los 14.1 by replacing the init binary with marshmallow one, from the J1XLTE and doing some init.rc fixes
The problem is that zygote crashes.
If i don't replace the init binary, adb detects the device but if i try to do adb shell or adb logcat, i get this:
Exec '/system/bin/sh' failed: No such file or directory (2)
J1XLTE (J1 2016) seems to have the exact same problem. I'm currently working with a developer of that device, because if it boots on it, it boots on ours, and visce versa.
Somehow it isn't able to mount the system partition.
Now, i'm trying LOS 13. It already got more far than LOS 14.1 (i still need to replace the init binary and do some modifications to init.rc). Sensors service seems to be crashing, and there is no boot animation, just black screen.
Click to expand...
Click to collapse
That is quite weird? are you sure about the partition layout, compatibility of blobs and some stuff and things?
is system defined correctly in fstab? Is its permissions defined correctly in ueventd?
I see that it is common-ized (and stripped down) in exynos3475-common which might be the cause, as j23gxx/j2lte is 1-year older than on5. Have you tried using stock fstab and ueventd for the ROM? (assuming you are building from source)
e:
afaik/if im not wrong: the dev has only On5 T-Mobile, which should explains why only that device tree (on5ltetmo) is well-configured and why the generic on5prolte is empty.
And, I cant seem to find On5 Pro tree (its ROM is on XDA), so I guess its just a port.
Prove N. said:
That is quite weird? are you sure about the partition layout, compatibility of blobs and some stuff and things?
is system defined correctly in fstab? Is its permissions defined correctly in ueventd?
I see that it is common-ized (and stripped down) in exynos3475-common which might be the cause, as j23gxx/j2lte is 1-year older than on5. Have you tried using stock fstab and ueventd for the ROM? (assuming you are building from source)
e:
afaik/if im not wrong: the dev has only On5 T-Mobile, which should explains why only that device tree (on5ltetmo) is well-configured and why the generic on5prolte is empty.
And, I cant seem to find On5 Pro tree (its ROM is on XDA), so I guess its just a port.
Click to expand...
Click to collapse
Actually, the good device tree is the on5prolte one, cm-14.1-20180513 branch (https://github.com/Exynos3475/android_device_samsung_o5prolte/tree/cm-14.1-20180513) (you can even see Device configuration for the Samsung Galaxy J2 (j2lte) WIP for now in the README.md )
The fstab is working fine, i managed to build TWRP from CM-14.1 source, and it uses the same fstab. TWRP works fine, except for MTP but that is probably because i'm using the nougat kernel.
No, i didn't tried the stock ueventd, but i don't see how that will change something, because the problem is on the init binary itself.
Also, the main j2lte developer (Izzy) has the J2.
TBM 13 said:
Actually, the good device tree is the on5prolte one, cm-14.1-20180513 branch (https://github.com/Exynos3475/android_device_samsung_o5prolte/tree/cm-14.1-20180513) (you can even see Device configuration for the Samsung Galaxy J2 (j2lte) WIP for now in the README.md )
The fstab is working fine, i managed to build TWRP from CM-14.1 source, and it uses the same fstab. TWRP works fine, except for MTP but that is probably because i'm using the nougat kernel.
No, i didn't tried the stock ueventd, but i don't see how that will change something, because the problem is on the init binary itself.
Also, the main j2lte developer (Izzy) has the J2.
Click to expand...
Click to collapse
I did not check the branches .
https://github.com/Exynos3475/android_device_samsung_o5prolte/blob/cm-14.1-20180513/BoardConfig.mk
Is it okey with kernel built with this?
Code:
TARGET_KERNEL_CONFIG := lineage-o5lteswa_defconfig
Prove N. said:
I did not check the branches .
https://github.com/Exynos3475/android_device_samsung_o5prolte/blob/cm-14.1-20180513/BoardConfig.mk
Is it okey with kernel built with this?
Click to expand...
Click to collapse
Maybe they share the defconfig
TBM 13 said:
Maybe they share the ramdisk
Click to expand...
Click to collapse
No. I meant, isnt kernel defconfig defines lots of things (including hardware/software and features of that one phone)?
Is it even possible to use defconfig of other device and it still works?
Prove N. said:
Is it even possible to use defconfig of other device and it still works?
Click to expand...
Click to collapse
If the device is very similar, why not?
---------- Post added at 17:53 ---------- Previous post was at 17:51 ----------
Prove N. said:
Is it even possible to use defconfig of other device and it still works?
Click to expand...
Click to collapse
If the device is very similar, why not?
TBM 13 said:
Maybe they share the ramdisk
Click to expand...
Click to collapse
I accidentally typed ramdisk instead of defconfig lol
TBM 13 said:
If the device is very similar, why not?
Click to expand...
Click to collapse
only with the SoC i guess. I thought On5 has 2GB RAM and J2 has 1, for example. Who knows about driver differences too~
I just can't wait anymore
Deemooo said:
I just can't wait anymore
Click to expand...
Click to collapse
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
sorry, i don't understand the system domain, i just a normal xperia user, just want to use native android likes los,dotos,rr etc. I'm sorry i can't help you, All i can do is wait, that's some sad.
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
Yes I see xperia merge fix in sources actually for kernel sources issue compile . I will create custom kernel for start . lineage later
PrzeStaw said:
Just compile AOSP :
- here are sources : https://github.com/sonyxperiadev/device-sony-pdx213
- here are instructions : https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
And please share some thoughts, I do not have the device yet so I could not do this myself
Click to expand...
Click to collapse
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
I guess we can create repo vendor and extract proprietary blobs from stock vendor...
I tested phh gsi lineage and its fully stable guy - in bonus green tint is fixed -
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Kyrimeas said:
Nice
And it's good that there is no green screen in custom roms
I can't wait for DotOS or other roms. XperiaUI is boring.
@ada12 Are you also building recovery?
Click to expand...
Click to collapse
for now no . I run actually gsi phh in daily use for stability . for sources I still work on it I have worked for compile kernel xperia https://github.com/Aarqw12/kernel_PDX213/commits/aosp/LA.UM.9.12.r1 but no luck actually its bootlop only for unknow reason.
Kyrimeas said:
Are you also building recovery?
Click to expand...
Click to collapse
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
zpk787 said:
You can try doing it yourself
[GUIDE]Porting TWRP without source
Yes, I know XDA is filled with such guides. But you can only port a TWRP if you implement parts of all the guides. This guide is a summation of all those guides. NOTE: I would be using AIK-Linux in this tutorial, since I don't recommend Windows...
forum.xda-developers.com
No actual programming required.
Click to expand...
Click to collapse
for stability build-in is very recommanded
vurg_usk said:
I managed to compile the sources but it doesn't seem to be enough.
Sony guide has a step to flash a vendor image:
Build AOSP Android 11.0 - Open Devices - Sony Developer World
developer.sony.com
There are no vendor images for 10 mark III yet.
I guess we need to wait till Sony publishes them. Please correct me if I'm wrong, it's a first time I compile Android
Click to expand...
Click to collapse
no need vendor image, need only flash oem.img xperia give really everything . lena sodp is no completly done for now , new features need to be implemented team sodp work on it. I guess just wait more
now xperia 10 III is officially added to open-source programm
Xperia 10 III added to Sony's Open Devices program - Sony Developer World
developer.sony.com
software binary released now we can compile rom
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
yeah，i also think we can have roms in the furture，im waiting
Kyrimeas said:
At the moment, we do not have lineageOS and recovery. There are only aosp sources that we can build.
Ada12 is currently building a custom kernel.
We will have roms for sure in the future.
Click to expand...
Click to collapse
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
xinniethewuflooh said:
Hello. So is a custom ROM, or Lineageos now available for the Xperia 10 III? I know nothing about programming a phone, so this is something I may not do on my own. I really just need a new phone (still using a 2013 iPhone 5S) but refuse to use Google or Apple's ecosystem (anymore). I also refuse to use a phone made in China, nor lacks a headphone jack and the only other phones that meet these criteria are too large for me (even this one is on the large end). So does anyone have steps to degoogle this phone, as of the near future or so, so I may order this phone asap? I have Windows, Mac, and will be downloading a Devuan-based Linux distro on another computer soon. Otherwise, I know LineageOS has come out for the Xperia 10 II, but how does that one compare to this one?
Click to expand...
Click to collapse
You can check "e foundation" GSI. It's ungoogled phones
ada12 said:
at the moment aosp sony custom rom boot . I have tried and its no booted Haxk20 have confirmed recently its have booted finally and guide compile sony is updated. actually they are no lineage custom rom in this devices ( need adapt trees ) but lineage GSI is already available for this phone. for recovery sources bringup its no finish.
Click to expand...
Click to collapse
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
xinniethewuflooh said:
I'm sorry I have no idea what you're saying. There are already available custom AOSP roms, no? What a "lineage gsi" and how do I compile it (on a Windows)? All I need until a custom rom is released is too remove google from the phone entirely. This is possible?
Click to expand...
Click to collapse
GSI is no a custom rom its a Generic System image , its update only /system ( os framework ) and use blobs,drivers from your /vendor , GSI is universal and run in all devices treble .
They are no custom rom available in public actually for this devices , source for custom rom is availlable but unstable in use ( sound only in headset , ril bug ... )
actually if you want run lineage or other custom android os use PHH GSI , or wait for custom rom ( NO ETA ).