HI,
I am a developer and have allot of experiance to contribute here (and i'm inrested in that ) i have saw that current latst source code is here:
http://developer.sonyericsson.com/wportal/devworld/downloads/download/402a058tarbz2?cc=gb&lc=en
i wanted to know if is there a tutrial/guid for getting started compiling the code for a specific device and understanding the source hierarchy/top level desing etc.
Thanks,
LaBBa.
There is a tutorial for compiling the kernel, it's in the dev website for sure, but I don't know if it had its own thread here.
labbala said:
HI,
I am a developer and have allot of experiance to contribute here (and i'm inrested in that ) i have saw that current latst source code is here:
http://developer.sonyericsson.com/wportal/devworld/downloads/download/402a058tarbz2?cc=gb&lc=en
i wanted to know if is there a tutrial/guid for getting started compiling the code for a specific device and understanding the source hierarchy/top level desing etc.
Thanks,
LaBBa.
Click to expand...
Click to collapse
Just so you know mow. There is no good tutorial for compiling source. I searched for weeks for a reliable guide but never found one. I only had help from another Dec who explained it all to me.!
Sent from my LT18i using xda premium
Read through the cm wiki and android x86 they both have good tutorials
\.|.. -_- ..|./ I am chuck ****in norris \.|.. -_- ..|./
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
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.
Yeah i know you cant port MIUI but i am asking is it possible to build?
There's some x86 tablets work on MIUI; in theory it's okay. But you need to find sources for x86 and you need to develop it to work on ZF5 afaik.
Technically it is possible, but practically it probably cannot be compiled as easily as you think.
But there's a way to know, try it.
MIUI has a lot of effort from its opensource community.. It should be possible even with x86
Sent from my ASUS_T00F using XDA-Developers mobile app
romngenie said:
Yeah i know you cant port MIUI but i am asking is it possible to build?
Click to expand...
Click to collapse
teoreticaly yes, but only 4.4, so you need 4.4 zenfone device tree,
device tree(have some faults) https://github.com/shakalaca/android_device_asus_a500cg
and you will need miui source code: (maybe this im not sure) https://github.com/MiCode/patchrom_miui/tree/v7-android-4.4.4
I want to be able to port or compile my own LineageOS. First of all, I have experience with programming/coding. Second of all, I have no experience of porting or compiling roms because I started my Android journey right before Cyanogenmod died. Their wiki is down so I don't have access to their resources. Third of all, can someone give me a good guide to making my own LineageOS so that I can either create from scratch, port, or compile? Thanks.
Start here: https://wiki.lineageos.org/pages.html
Sent from my MI 3W using Tapatalk
Maybe I'm missing something but that had nothing to do with building an unofficial Lineage ROM. I'd appreciate the info as well. The Samsung On5 has been poorly represented and while I'm no dev I know my way around a phone up to a point.
You can also try https://web.archive.org/web/20161225121729/https://wiki.cyanogenmod.org/w/Main_Page