Related
can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
hi
I am looking for the source code of 4.1.B.0.431's application framework (source code of jar files in /system/framework ). I have got CM9's framework's source code but could not find Stock Rom's source.
Can someone help me in finding it please ?
U wont find it. Oem never give source for their rom, or else we would see sense running on xperia or touchwiz running on lg
an0nym0us_ said:
U wont find it. Oem never give source for their rom, or else we would see sense running on xperia or touchwiz running on lg
Click to expand...
Click to collapse
Agree :highfive:
Well, I only need framework.jar's source code.
(Bytecode injection and java class decompiling would not work in all cases.
)
I am looking for it since I found out that Sony has released the source code of Xperia S kernel
I am sure that someone could find it
@[email protected] said:
Well, I only need framework.jar's source code.
(Bytecode injection and java class decompiling would not work in all cases.
)
I am looking for it since I found out that Sony has released the source code of Xperia S kernel
I am sure that someone could find it
Click to expand...
Click to collapse
You can't find it. it's not public released. Android open source in OEM's meaning is releasing kernel, and maybe some libraries source code. You can't expect that big company, like Sony, can release something that makes their phones another than pure AOSP, that costed a lot of their employers effort.
I don't think that Sony has made huge changes (like changing classes names and methods) in the original framework. So, they won't loose that much in releasing the source code. Android isn't their own operating system. Anyway, if someone can get it that would be great.
Hi all,
i'm a noob to android, but i have nit of experience on other unix based systems.
I was wondering, why there is no custom roms for GT-S5690?
What's the problem?
Is bootloader locked some other way or is it somehow different from example Gio/GT-S5660?
There is a bunch of roms for gio..
I have one xcover, wich has no screen and covers, i thought i could use it for testing.
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
xkawer said:
I think there are too less people who have a xcover, and I was actually pretty disappointed when I say there is a successor to the xcover available only in the US (Rugby Smart / Pro <-- with ICS!).
From the technical side, I don't know. Even the source code of the firmware is available at opensource.samsung.com. The Bootloader seems pretty much unlocked.
For me, the xcover is the best phone ever, it takes so much abuse. Maybe someday someone will port a newer ROM from the Ace/Gio/idk. It's a shame Samsung abandons their old phones :crying:
Click to expand...
Click to collapse
I didn't were aware of successor models, now i'm very dissappointed.
I'm downloading these source codes at the moment, i'll check these out.
I'm not a developer, atleast YET..
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
jonezy82 said:
AFAIK, hardware of s5690 is way different from any other samsung phones,
correct me if i'm wrong..
Click to expand...
Click to collapse
Seems like it's the only one with a Marvell MG2.
Let me know if you do anything interesting with the sources
Just flashed my xcover to XXLJ2 yesterday. At least it seems a bit faster now, but I have a weird bug when scrolling. If I give a list (for example settings) momentum, it doesn't stop when I put my finger on it again. But it does stop if I release the finger the second time.
jonezy82 said:
I'm downloading these source codes at the moment, i'll check these out.
Click to expand...
Click to collapse
Did the same. The GT-S5690_Platform.txt says:
Code:
How to build platform
1. Get android open source.
: version info - Android gingerbread 2.3.6
( Download site : http://source.android.com )
2. Remove external\webkit module in android open source which you got.
And then execute "clean build"
2. Copy files and modules to original Gingerbread source tree (overwrite)
3. build
- ./build.sh user
So wouldn't it be possible to download the JB sources, and compile them with the original kernel? Would be so cool.
Edit: It seems you need device specific binaries (drivers) since ICS. see: http://www.freeyourandroid.com/guide/compile-ics
Found a git https://github.com/manakeri/android_device_samsung_xcover, there is a
Code:
cyanogen_xcover.mk
file, this seems interesting. Apparently someone is trying to port it.
Edit2: In this git, there is also a "extract-files.sh"-file, which is neccessary to pull the proprietary files from the phone! With this I think we actually have everything we need to compile ICS/JB, like in the "freeyourandroid" tutorial.
I have never done this before, but someone must try it lol.
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:
xkawer said:
Oh look, there are more people who care about it!
http://www.droidevelopers.com/f338/14412-gt-s5690-opensource-kernel-available.html
Someone discovered my link and made a overclock kernel from the sources! This is so cool.
I hope we are going to see more :good:[/QUOTE
I own an xcover too a developer on another forum looked at some files i pulled using adb to try to port clockworkmod but no success. Told me the files i sent weren't standard android img but he would continue to look into it. Apparently the teamhacksungs goal is to port cyanogenmod for every Samsung device surely they can get it done. I've been waiting a long time to see some development for the awesome xcover
Click to expand...
Click to collapse
If its possible on the galaxy mini its got to be possible on xcover!. Ive tried to get involved and learn to port cyanogenmod but when it comes to git, repo, source tree, source code e.t.c e.t.c its a bit behond me for now.
Step in the right direction it seems. Fingers crossed
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
kieran_buffet said:
hi peeps. thank u for stopping by
i want to get into android development and make personal touches and changes to my phone. i quite like oxygenOS so i would like to stick with this and modify that slowly. but i cant figure out how to begin specifically with oxygenos? it doesnt appear as if they release their source code anymore. could anyone please point me in the right direction? thank you
Click to expand...
Click to collapse
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Raiz said:
Hi,
First of all, OnePlus do release their source code. But if you want to modify your phone and keep OxygenOS, you don't look it the right place.
With root you can have a lot more possibilities for customization, so I'll advice you to check Magisk (a root manager/ customization tool with which you can install modules).
If you want to theme your device you can use Substratum, and install themes from the Play Store.
Search about them and give them a try if you want to
Click to expand...
Click to collapse
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
kieran_buffet said:
thank u for getting back to me! i took a look at their github page but it said they stopped releasing the source code because it can be found elsewhere, and i cant find where exactly that is. i dont want to modify the OS as is (root it and customise that way), i mean getting the source code, changing, removing and adding things and then flash my own custom flavour of oxygenOS onto my phone. i figure going with what comes with my phone is best when getting into android development so that there are as few compatibility issues as possible. would you be able to point me exactly how i might obtain the source code? it would be very cool my dude
Click to expand...
Click to collapse
I hope you're familiar with git. I believe this is what you're looking for. https://github.com/OnePlusOSS
Spaceminer said:
I hope you're familiar with git. I believe this is what you're looking for.
Click to expand...
Click to collapse
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
kieran_buffet said:
i am indeed familiar with git, but i dont exactly understand what i am wanting from that page. i want the full source code to oxygenos and the kernal/binary specific packages for my phone. i previously found this site before but to my knowledge what is on there doesnt get me the source code. am i missing something? thank you for your helps
Click to expand...
Click to collapse
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Spaceminer said:
Check under the Android section on that page. Which specific OnePlus device do you have? There are many of them. I can help you find it if I know your model.
Click to expand...
Click to collapse
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
kieran_buffet said:
i see where you mean. but it seems like they stopped doing these releases. on their latest release (11 months ago) they said; "based on conversations we had with our dev community and the fact that we have only made few changes on AOSP(Qualcomm BSP) device tree, we will not be releasing AOSP device trees for future devices, the community can get the baseline from our device and get the source code from Qualcomm."
"the community can get the baseline from our device and get the source code from Qualcomm." i have no idea where to get what they are talking about.
i have the oneplus 8 pro
Click to expand...
Click to collapse
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Spaceminer said:
They're probably referring to CAF sources for the Qualcomm bit. The baseline part is probably a reference to the script that's in the Android section. This is the closest thing to what you're after that I can find.
https://github.com/AndroidBlobs/device_oneplus_OnePlus8Pro
https://github.com/AndroidBlobs/vendor_oneplus_OnePlus8Pro
https://github.com/codeauroraforum (CAF)
Click to expand...
Click to collapse
ah yes. my brain has clicked with the baseline part, i would plug my phone in and it would use adb to extract the "baseline"? i understand this process. is what i am asking for difficult? perhaps i am better off taking the kernal files for my phone and integrating it with stock android that i would build and practicing with that? i really appreciate your effort but this "android blobs" is apparantly for reference only, i have no idea what android blobs is. i went into this knowing oneplus isnt extremely AOSP friendly compared to Sony for example, but i am going to push on. do you have any advice? this doesnt appear to be a friendly introduction into existing OS modification by sticking with OxygenOS