Related
Hello, I have been looking to port Android 4.4 from the nexus 5 factory image, is this do-able? Thanks guys
Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk
FabC87 said:
Nope, completely different devices. Aside from some of the APKs and some other minor things found in the image, the rest of it would be of no use to getting 4.4 running on the S3. You would have to port the 4.4 code from AOSP to be compatible with this hardware. I would wait for CM11.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
CM11 source is now out. Some things need worked on though like CM Launcher, lock screen, etc.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Porting the kit kat ROM from the nexus 4 should work though a lot of our specs are the same. I've been trying to work on that.
There's no need to "port" kitkat to this device as Google has released source for kitkat. Just setup your device trees and make sure you have all the hardware repos necessary for this device. Then compile from source.
Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.
joemommasfat said:
Task, would you be able to link to some more walkthrough-like instructions to do this? I would like to try to compile AOSP for this device from source.
Click to expand...
Click to collapse
You'll need some knowledge on compiling and messing with AOSP.
There's already a developer working on 4.4 for the i747. The Dev manages Quantum for the S3. It would be a little bit easier to build from CM11 but the code is very rough but it just did get released last night.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.
joemommasfat said:
I do have some knowledge of compiling and messing with AOSP. What I don't know how to do is set up a new device tree a get the necessary hardware repos. I have synced the CM-11.0 source, but they also do not have a d2att device tree.
My question is if anyone can help me to do that.
Even if someone else is already on it, perhaps I would just like to learn how.
Click to expand...
Click to collapse
This may help you building from CM. This may also help too.
A tutorial may not give you all the information you're looking for either. Its all about researching the device.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
i read something in the net while i was surfing yesterday, you can look here: http://www.androidcentral.com/motorola-atrix-hd-gets-official-cyanogenmod-support
and then reading these lines made me surprised(maybe getting official cyanogenmod support for ancora is impossible after this moment but who kowns?)
If an Android device has enough of a following, and there are developer(s) willing to commit (no pun intended) to maintaining the device in the official CyanogenMod source tree, this device becomes officially supported -- and receives official builds of the CyanogenMod ROM.
if someone be maintainer for our device can we get official support from CyanogenMod?
is this really possible?
ı mean our device source code are available in github(kernel source device source and vendor files)
maybe forking our device source into CyanogenMod source tree can make this possible or am ı wrong??
maybe this is a bulsh*it after this moment but just wondering
for example galaxy s is getting official support from Cyanogenmod still if im not mistaken mr. pawit is their maintainer and developer
ım waiting your answers brothers what do you think about that? @arco68 @arsradu @LeroViten @honeyx and all ancora devs
with my best regards :good:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
honeyx said:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
Click to expand...
Click to collapse
ı understood bro but is there any hope for galaxy w? return of ancora :good: and also ı understood that from your comment : technically this is possible,galaxy w can get official support from CM Team but this is unnecessary for this dead device isnt it?
I simply don´t think this will happen because you have to look from their point of view.
1. this device is a low activity device in Amercian terms. 2. So never was that popular to get their attention. 3. is already old and not up to date. 4. It´s hype time is almost over and many earlier SGW users are going to replace it. 5. CM is going a different route now and will be focusing on their "device" they are going to launch soon. And finally 6. Why should they change this now after already 3 years?
So if I were CM I would look for the future not looking back to the past with it´s outdated devices and not even waste a single tought about devices like the SGW.
Is this bad for the SGW owners? As long we are having Devs like Radu who are porting the latest ROMs to this device it really doesn´t matter CM is supporting it officially or not supporting it.
So what do you expect from being supported by CM? You only would be able to install the latest nightlys launched by the CM team with all the bugs in the CM code included and maybe some day fixed. A Dev who is porting their CM sources of course has to fight with these bugs too, but also cares to fix the most important ones.
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
SGWUser said:
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
auhh thats true sir arne is right as always anyway thanx man for informing us
regards :good:
I don't think so...anyway, we already have the stable n smooth ROM so far. Without Officail, it's does not matter at all.
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
hack4er said:
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
Click to expand...
Click to collapse
That would be so f... Awesome *-*
Please we need someone who knows how to do this
Is there anyone, who is able to port firefox os/ubuntu touch or sailfish os to lg g3? Could be nice to see it.
firefox os and ubuntu touch are 4.4.2 kitkat and not all repository are downloadable (this make them unbuildable) sailfish os is not open source, (if you find the source code i could take a look)
manups4e said:
firefox os and ubuntu touch are 4.4.2 kitkat and not all repository are downloadable (this make them unbuildable) sailfish os is not open source, (if you find the source code i could take a look)
Click to expand...
Click to collapse
Here you go mate, https://sailfishos.org/hadk would be amazing if you could build it!
Hey @manup4e nice to see you around these parts, I remember you from the HTC One L porting stuff. I just wanted to throw you this link: https://wiki.ubuntu.com/Touch/DeprecatedPorting for Ubuntu Touch, it is older and there is a new guide being written. Anyway I know it's possible, I had a "working" build for my HTC One m7 like a year ago. I'd be up to work on an Ubuntu port with you.
manups4e said:
firefox os and ubuntu touch are 4.4.2 kitkat and not all repository are downloadable (this make them unbuildable) sailfish os is not open source, (if you find the source code i could take a look)
Click to expand...
Click to collapse
Hey manups4e,
The link that theonlykamph posted takes you directly a page with great info on porting Sailfish to other devices, but the actual source files are kind of buried (at least when I went looking for it). I had downloaded them a few days ago and have them uploaded on my dropbox here if you want to grab it:
https://www.dropbox.com/sh/8bxxwj2h3lil0nb/AADnwQh_8EFoG4AEnt3xibRva?dl=0
This is the source and MD5sum for the ARMv7 chipset.
manups4e said:
firefox os and ubuntu touch are 4.4.2 kitkat and not all repository are downloadable (this make them unbuildable) sailfish os is not open source, (if you find the source code i could take a look)
Click to expand...
Click to collapse
I think this is the source code right? https://github.com/sailfishos
skiman10 said:
Hey @manup4e nice to see you around these parts, I remember you from the HTC One L porting stuff. I just wanted to throw you this link: https://wiki.ubuntu.com/Touch/DeprecatedPorting for Ubuntu Touch, it is older and there is a new guide being written. Anyway I know it's possible, I had a "working" build for my HTC One m7 like a year ago. I'd be up to work on an Ubuntu port with you.
Click to expand...
Click to collapse
i tried downloading sources a few times but some repos were undownloadable... both firefox and ubuntu sources use some aosp sources (stock aosp google sources) that make it unbuildable for g3.. if you build vanilla aosp for g3 you'll get lots of errors because some g3 drivers are not supported by google
---------- Post added at 09:48 AM ---------- Previous post was at 09:30 AM ----------
https://wiki.merproject.org/wiki/Adaptations/libhybris
are still sure you want it?
manups4e said:
i tried downloading sources a few times but some repos were undownloadable... both firefox and ubuntu sources use some aosp sources (stock aosp google sources) that make it unbuildable for g3.. if you build vanilla aosp for g3 you'll get lots of errors because some g3 drivers are not supported by google
---------- Post added at 09:48 AM ---------- Previous post was at 09:30 AM ----------
https://wiki.merproject.org/wiki/Adaptations/libhybris
are still sure you want it?
Click to expand...
Click to collapse
I see. But we don't know how sailfish os will be on lg g3, i mean if you look at nexus 4 they have a close to stable sailfish os. I have read a lot about portings roms. But i think, i found out that the rom you want to port, needs to come from a phone with the same specs right?
manups4e said:
i tried downloading sources a few times but some repos were undownloadable... both firefox and ubuntu sources use some aosp sources (stock aosp google sources) that make it unbuildable for g3.. if you build vanilla aosp for g3 you'll get lots of errors because some g3 drivers are not supported by google
---------- Post added at 09:48 AM ---------- Previous post was at 09:30 AM ----------
https://wiki.merproject.org/wiki/Adaptations/libhybris
are still sure you want it?
Click to expand...
Click to collapse
Right but if we build off a, I hate to say it, stable cm11 base like I did with the m7, it should work.
Sent from my Nexus 7 using Tapatalk
skiman10 said:
Right but if we build off a, I hate to say it, stable cm11 base like I did with the m7, it should work.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Mate are you able to do it? Would be amazing!
As we now have the source anybody able to build it?
Sent from my LG-D855 using XDA Free mobile app
theonlykamph said:
Mate are you able to do it? Would be amazing!
Click to expand...
Click to collapse
Ahh gosh. It'll take a lot of time. It's a very time consuming process. And I'm a high school senior just trying to finish up school. Honestly I don't know if it'll be worth the work I put into it if only a couple people want it.
skiman10 said:
Ahh gosh. It'll take a lot of time. It's a very time consuming process. And I'm a high school senior just trying to finish up school. Honestly I don't know if it'll be worth the work I put into it if only a couple people want it.
Click to expand...
Click to collapse
I get you mate. But i think we are more than a couple of people that want it. People always wanna try something new. So why not give it to them?
theonlykamph said:
I get you mate. But i think we are more than a couple of people that want it. People always wanna try something new. So why not give it to them?
Click to expand...
Click to collapse
I would very much like to see this os on g3 i have been keeping up with their hadk from v1.02 to v1.3. and setting up the mer sdk and chroot is not hard to do but. getting the respitory for your target device is the hassle and trying to get the hybrid libs to compile is not as easy as they make it sound i have tried multiple time for my secondary phone which had the same specs exact to the nexus 4. I know this can be done with each update they provide
xoLEOox said:
I would very much like to see this os on g3 i have been keeping up with their hadk from v1.02 to v1.3. and setting up the mer sdk and chroot is not hard to do but. getting the respitory for your target device is the hassle and trying to get the hybrid libs to compile is not as easy as they make it sound i have tried multiple time for my secondary phone which had the same specs exact to the nexus 4. I know this can be done with each update they provide
Click to expand...
Click to collapse
Knewed i wasn't the only one who wanted sailfish
Sailfish?! That sounds nice
Galaxysm said:
Sailfish?! That sounds nice
Click to expand...
Click to collapse
Amazing rom!
This is an FYI.
This forum is only for high-level discussion about LG G3 development (kernel modification, coding, building ROMs, etc). **Please do not post here if you are not a developer or your post will be deleted.* (Redirect)"]This forum is only for high-level discussion about LG G3 development (kernel modification, coding, building ROMs, etc). **Please do not post here if you are not a developer or your post will be deleted.*
Click to expand...
Click to collapse
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Click to expand...
Click to collapse
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
I meant combination UB+Stock. That UB alone is required is clear
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB
shoey63 said:
The link says to first install generic software on your device, so yes when released, UB+Stock will work.
But obviously, it will be different to the android concept scenario which (by my reckoning), is just a test by Sony on how to prevent people from rooting their phones on locked bootloader under the guise of providing a minimalistic Sony AOSP like experience. It is my opinion that they will implement it in their future devices.
Edit: I misread you post. Quite clear you were talking about UB [emoji14]
Click to expand...
Click to collapse
Anyway, if Sony would mean it seriously with security restrictions in Concept, then we have to go on at least with custom kernels. As soon as Z3 will be in Open devices, majority of problems like fish-eye camera problem may disappear. I think unified kernel sources for 3.10 are already online.
Sent from my D6603 using Tapatalk
Built it, flashed it, bootloops on kernel splash screen
shoey63 said:
Built it, flashed it, bootloops on kernel splash screen
Click to expand...
Click to collapse
With which fw you use it?
Sent from my D6603 using Tapatalk
Flashed back to pure stock. Version doesn't matter I think. Fastbooted the images and got stuck in an hypnotic bootloop. Kernel splash screen over and over...
Sent from my C6603 using XDA Free mobile app
ondrejvaroscak said:
Will Open Devices recovery work with unlocked bootloader and Stock ROM? Or is it intended for Custom ROMs only? I ask because Stock ROMs are using recovery partition for FOTA and the only Stock that brings new partitioning scheme - the new Concept UI ROM - uses nasty security measures against changing either recovery or system partition...
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
recovery is intened for unlocked bootlaoder and custom roms only
br
J
shoey63 said:
I think this link would indicate that it is meant for UB at this stage.
However I am building the AOSP android M preview, and will report back with my findings.
Click to expand...
Click to collapse
i will update build guide for m-preview1 and publish new zip soon
the old blobs from m-preview are incompatible with new m-preview1!
br
J
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
LeParkour012 said:
I'm interested in building an AOSP (5.1.1) firmware for myself. However I lack the knowledge to do so. So bear with me as I ask a few stupid questions while I'm trying to learn something new.
First of all, if I were to follow the instructions on the link on the OP, does that mean that I'm able to build a perfectly working AOSP (5.1.1) firmware?
Secondly, I'm assuming that I need Ubuntu or Linux?
Thirdly, I don't quite understand how does one flash the firmware once it's built. I mean does it provide a kernel with a recovery or do I have to use the unified kernel?
Lastly, is root possible? (Not important)
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
jerpelea said:
recovery is intened for unlocked bootlaoder and custom roms only
br
J
Click to expand...
Click to collapse
Hi, I would paraphrase the Apollo 13 - "It is not important what it is intended for, but what it actually can do"
ondrejvaroscak said:
For the second question.. You need any environment that supports git and compiling. The instructions are given for Ubuntu and I would stick with that. Ubuntu or compatible Debian based distro.
You get kernel, system and data images at the end. Those you flash in fastboot mode. See instructions. So far it doesn't provide recovery, but recovery may already be available for supported Open Devices. Once you flash recovery, it's kept in separate partition so you can boot it regardless of kernel.
As for rooting, you can do it with recovery or you can include su in your aosp system.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
LeParkour012 said:
I tried following the instructions to setup Ubuntu. Used VMWare since for some reason I can't install it on a different partition on my Hard Drive (it gets stuck at login and black screen and loops). I get errors. I give up. Maybe I can use my other PC for Ubuntu.
Click to expand...
Click to collapse
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
ondrejvaroscak said:
Nobody can help you or provide you with any guidance if you write just "I get errors" ... Compiling AOSP is not for newbies, it expects you to have profound knowledge of Linux kernel based systems, working with source code, compiling and cross-compiling and not least Linux administration. There is no such thing like a spoon feeding / cook book for compiling own system.
Click to expand...
Click to collapse
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
LeParkour012 said:
I think you misunderstood me here. I'm not asking for help. That's why I wasn't specific on the errors. I wanted to try on my other PC later on. To be honest I have no idea why I replied to you but I guess that's my mistake. Sorry
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
ondrejvaroscak said:
OK, I was bit referring to your first post, it seemed you expect step-by-step instructions to get "perfectly working" AOSP. Such thing doesn't exist.
When setting up building environment, be sure to provide generous space, not less than 200 GB.
Click to expand...
Click to collapse
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
LeParkour012 said:
Ah I thought Sony released a fully functioning AOSP firmware. My bad.
200gb? That's huge. I guess using my other PC for Ubuntu is a good choice.
Sent from my D6653 using Tapatalk
Click to expand...
Click to collapse
Sony releases support files for building AOSP, and yes, if you build from Sony sources, you will get pure Sony AOSP. However, the main intention of AOSP is customization, it is not intended as general purpose daiy use system.
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 ).