well, a few days before sony released aosp for e3 as much as i know it is android open source project but i don know what exactly it is and after watching this post http://forum.xda-developers.com/xperia-e3/general/wonder-cyanogenmod-make-roms-xperia-e3-t2974048 <I can compile it if u guys want..
http://developer.sonymobile.com/2014...pported-video/>
i can,t understand what to compile,what compile gonna do,what it means is he mean by fixing problem,s that sony told we can,t make call this is not for daily use.
please explain fully.
is thare any aosp fixed version for e3 daily base use. so i can understand more about aosp.
android-vinay said:
well, a few days before sony released aosp for e3 as much as i know it is android open source project but i don know what exactly it is and after watching this post http://forum.xda-developers.com/xperia-e3/general/wonder-cyanogenmod-make-roms-xperia-e3-t2974048 <I can compile it if u guys want..
http://developer.sonymobile.com/2014...pported-video/>
i can,t understand what to compile,what compile gonna do,what it means is he mean by fixing problem,s that sony told we can,t make call this is not for daily use.
please explain fully.
is thare any aosp fixed version for e3 daily base use. so i can understand more about aosp.
Click to expand...
Click to collapse
https://android.googlesource.com/
This is source code for AOSP ("pure android"). That what Sony released is device source folders for E3, M2... and proprietary precompiled binaries. That's needed, so compiled AOSP will run on the device. Devs can set up their own device folder, but Sony did it for them first. The source might be incoplete or buggy, so devs have to fix it.
More here
Vynikal said:
https://android.googlesource.com/
This is source code for AOSP ("pure android"). That what Sony released is device source folders for E3, M2... and proprietary precompiled binaries. That's needed, so compiled AOSP will run on the device. Devs can set up their own device folder, but Sony did it for them first. The source might be incoplete or buggy, so devs have to fix it.
More here
Click to expand...
Click to collapse
Thanks now i undersand what is aosp.
Related
Nearly days I get an open souce code of i5800 and I just a new one in the compling world,so I hope someone can help me find something useful in configuring the code or some books useful.
If you have a qq number and our time are not rushed ,we can communicate in this way.(No facebook or twitter in china....How big the wall!)
My QQ number is 361180509
not sure I understood what you mean, do you have access to newer (froyo) kernel sources for I5800? if so, please do share
eclair kernel source is on opensource.samsung.com, and they compile just fine with the official Android toolkit, but Samsung's changes for Froyo are nowhere to be found (a few modules missing, touchscreen and accelerometer being the most notable), and the kernel doesn't compile anyway.
ze-m0n5t3r said:
not sure I understood what you mean, do you have access to newer (froyo) kernel sources for I5800? if so, please do share
eclair kernel source is on opensource.samsung.com, and they compile just fine with the official Android toolkit, but Samsung's changes for Froyo are nowhere to be found (a few modules missing, touchscreen and accelerometer being the most notable), and the kernel doesn't compile anyway.
Click to expand...
Click to collapse
Not sure if i get you right, do you say it does, or it does not compile? If not, we should request propper sources from Samsung.
sorry,I just don't find the offical source code website before posting this.Cause I just a freshman and I haven't got my PC....
maybe I'll compile the source code later.Sorry to make these mistakes.And I'm chnese.So my english is poor.....
Sent from my GT-I5800 using XDA App
FadeFx said:
Not sure if i get you right, do you say it does, or it does not compile? If not, we should request propper sources from Samsung.
Click to expand...
Click to collapse
eclair sources compile just fine, both with my system cross-compiling toolkit (arm-android-linux-gnueabi managed on gentoo by crossdev) and with the prebuilt one that comes with the Android platform
I might give it a try to actually boot it (but I would need to construct an initramfs, and it's a lot of work, and I kinda need to get back to "proper" work, I was consumed by Android during the last 3 weeks since I got the phone )
ze-m0n5t3r said:
eclair sources compile just fine, both with my system cross-compiling toolkit (arm-android-linux-gnueabi managed on gentoo by crossdev) and with the prebuilt one that comes with the Android platform
I might give it a try to actually boot it (but I would need to construct an initramfs, and it's a lot of work, and I kinda need to get back to "proper" work, I was consumed by Android during the last 3 weeks since I got the phone )
Click to expand...
Click to collapse
You can use the initramfs from Eclair.. I'm assuming you're talking about 2.1.. since 2.2 sources aren't out yet for this phone.
Link for the initramfs for Eclair is here: http://www.multiupload.com/U6GB5BB3HI
This is the JK1 I think - or whatever eclair rom I posted up previously
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
LewisD94 said:
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
Click to expand...
Click to collapse
It's advisable that you create your own tree from the CAF MSM8974 using CM GPS and other drivers and build CAF AOSP. Otherwise, it's close to impossible/very difficult. Pure AOSP is again near impossible/very difficult for non nexus devices.
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
LewisD94 said:
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
Click to expand...
Click to collapse
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
rudi_j7 said:
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
Click to expand...
Click to collapse
Ah yes, I see what you're saying now. Thanks for clearing this up for me! I just noticed when I looked at the VanirAOSP ROM thread that it states CM for it's credits, haha. I apologize for my ignorance.
Hello
I would like to create my first rom for oneplus one but without modification from OMNI or CM, basically vanilla rom. but I have some doubts.
Can I create a rom based on AOSP with device tree from OMNI/CM right?
Thanks!
Hey people!
I was trying to learn how to build AOSP ROMs for my E8, for which HTC has released the kernel source on the HTCDev website.
I feel kind of lost right now.. I have uploaded the kernel source for the device on to GitHub: [LINK] There are two archives within the source archive, where one says "platform" and the other is the kernel source.
Now, I'm syncing the AOSP source as they tell you to in the Sony Developer Portal (from HERE) to my Ubuntu VM (which is a huge download). What do I do next? Will this be enough to build the ROM or will I need other resources as well?
Sorry, I've never really done this before. So, I have some really noobish questions.
Thanks!
* BUMP *
Anyone? Please help!!
Hi guys, after 1 year,XZP still don't have LOS or other rom based los, just hava a Carbon ROM…
So can someone explain?
I really hope that XZP will have LOS…:crying::crying:
In theory(Not sure), on Carbon's maple open source code, a little modification can compile lineageos, but currently no one is doing it, maybe using Sony's third-party ROM and too few third-party developers, leading to the development of the original Android development slow.
(By the way, I had an idea last year, syncing some open source projects back, building a third-party ROM for my Xperia Z5 at the time, intending to use Carbon's already open source sumire code to compile other ROMs. Since I don't have any knowledge about modifying the code, I just want to try the fun of building ROM. Finally, because of the problems of the Chinese network, I gave up. .
I want to build my unofficial build for my phone, HTC Desire 816. But I have a limited data plan, and I worried I will running out of my data by downloading a huge source code with unnecessary files for other architectures, phones etc. And I'm just need the ARM and important files.
Also I got these repos from Tarkzim's forum at LineageOS unofficial for HTC Desire 816:
Device tree
Kernel
Vendor
Well, I didn't have any experience at Android development. So maybe can someone give me a guide too?
I'm just know the preparations on the documentation and it's ready, but the steps are confusing for me.
Or maybe if peoples are have their time maybe can someone make the official build?
Maybe it such out of BlissROMs, but I really want to Blissify my phone. Because LineageOS are too plain, no good features like smart charging etc. It just looks a normal Android build from AOSP source.