compiling your own roms - Nexus S General

so... here's what i'm thinking.
how about setting up a vmware machine with all the source code for android on it, so that when a new version comes out, you can compile your own rather than waiting and then flash it to your phone. you could add your own modifications and any others that are out there.
this is a win / win situation as you get your own compilation, your own custom build and can screw about with the code it as much as you want as it's on a virtual machine.
you could update the android source code by pulling it online. and because it's a virtual machine, you don't need to worry about compilation issues across different machines.
i'm thinking about doing it - who'd be interested?

That's what I'm doing. It's FUN but to be honest it's quite a pain in the a$$ when you sync the master branch, compile, flash, and found out that the resulted ROM does not working properly and can't find any information about how to fix it.
BTW, I can hardly find the info on modifications -- most topics here are ready-to-flash ROM releases but no info on development. I did found some useful information in Nexus One forums, though.
Any suggestions on where can we find the resources regarding compilation and modification of AOSP?

well, my instincts tell me the modifications are "closed-source", hidden away from you. who knows what sorts of nasties are in the actual rom that's sitting on your phone. logging your every move, grabbing every site you visit, logging everything you type etc.
so, what's needed for a more successful dev community as far as i'm concerned is to allow the users to pick and choose what mods they want. this is an adp after all, and is one of the easiest phones to compile for.
so, if there's an active community compiling their own roms, then mods will perhaps become more open source with diffs / additions to the android source, which in itself will be better for users, developers and heck, who knows who might actually add it to the android source?
as for info for building:
http://source.android.com/source/building.html

Related

How to cook ROM for Galaxy S

Can someone explain me how to cook a Galaxy S' ROM?
I'm pretty good with computer, and i have a lot of time, if someone can help me i'm sure that i will work hard on it.
Thanks for any help!
Iacopo91 said:
Can someone explain me how to cook a Galaxy S' ROM?
I'm pretty good with computer, and i have a lot of time, if someone can help me i'm sure that i will work hard on it.
Thanks for any help!
Click to expand...
Click to collapse
if it would be that easy, everybody would do it
what do you mean by "good with computers"? do you know how to write code (C/C++)? are you yet experienced with running linux? have you ever compiled a kernel before? do you want to make a source-(AOSP)-rom (then you can get the source here: http://source.android.com/ and here: http://opensource.samsung.com/) or do you want to just theme and customize a stock firmware?
i think there are already some tutorials around which will help you in the beginning. just google for them!
i haven't done custom rom development myself but i would really like to get some (clean) aosp goodness on this phone. i am experienced with linux (use it since 6 years as primary os) and i can code c/c++/asm. so if you are in fact serious and able to go all the way. i would appreciate to help!
jodue said:
if it would be that easy, everybody would do it
what do you mean by "good with computers"? do you know how to write code (C/C++)? are you yet experienced with running linux? have you ever compiled a kernel before? do you want to make a source-(AOSP)-rom (then you can get the source here: http://source.android.com/ and here: http://opensource.samsung.com/) or do you want to just theme and customize a stock firmware?
i think there are already some tutorials around which will help you in the beginning. just google for them!
i haven't done custom rom development myself but i would really like to get some (clean) aosp goodness on this phone. i am experienced with linux (use it since 6 years as primary os) and i can code c/c++/asm. so if you are in fact serious and able to go all the way. i would appreciate to help!
Click to expand...
Click to collapse
I'm pretty able to develop with Eclipse, so android sdk. Linux quite good, i prefer to use windows, but i know linux is necessary. First of all i'd like to know how to customize GALAXY fw and then i'll study how to compile a kernel, no one during my life helps me, and it's difficult for me because i'm not good with english and all tutorials are in english!
I'll try to work on it! Thank you
Can someone explain me how to cook a Galaxy S Froyo ROM with AOSP as the base and samsung drivers?
Could someone please explain to me how to flash the Korean firmware onto the European phone? Really need the native "record call" feature
I saw some instructions posted here
http://forum.androidcentral.com/hacking/40130-100-stock-captivate-rom-aosp-source.html
It's not difficult if you're comfortable with linux, shell scripts, custom kernels, and cross compiling.
Basically that's pretty much all it needs, Android systems are very similiar to a running linux system.
Boot off a bootloader (usually closed sourced) into kernel and initrd, then init loads the drivers, system and configs, after which is pretty much to your taste and likings.
Source code of android, samsung kernel source, are available online, google is your friend.

[Q] sm-t230(nu) Device Tree For Compiling Custom Rom

As the title suggests... i have looked all over the web for a device tree to be able to compile android with but all i have found is a basic dev tree for building twrp...
could someone please point me in the right direction or even advise me on how i would compile android from source for the sm-t230/t230nu
thanks in advance...
I've also been looking into this. I want rid of TW in the worst way.
Inside 4ndroid said:
As the title suggests... i have looked all over the web for a device tree to be able to compile android with but all i have found is a basic dev tree for building twrp...
could someone please point me in the right direction or even advise me on how i would compile android from source for the sm-t230/t230nu
thanks in advance...
Click to expand...
Click to collapse
We don't have a complete dev-tree yet. Samsung dosen't really want to release a lot of source code and so, there are lots of missing parts like driver sources and incomplete kernel sources etc. We also don't have a proper cousin device yet so it is very hard to build a tree for us.

Lollipop Source Code 915F/FY

HI just had email from Samsung to say source is now out... roll on some custom kernels .... please
..well as it looks like we don't have any kernel devs I thought I try to compile my self as the guides look easy enough.. but even a straight build from the Samsung source fails at the first hurdle.
Make clean report an error of a missing file being referenced in drivers fc3150 or something like.. on checking it is certainly not there and if I remove the reference as there is also a fc3200 which is there it simply complains that the make file is incorrect in some way.
If some one with experience could have a look and assist or point me in the right direction I would be grateful thanks

REQ rooted kernel 5.1.1 for Sm-t235 (source was published a month or two back)

sometime back this was posted
http://forum.xda-developers.com/showpost.php?p=63556533&postcount=135
unfortunately moonbutt closed his thread just when I and another member posted boot image etc on the board..understand he may have moved on to better things
not knowledgeable here but appreciate if someone can take this up or redirect this to some dev who can make a rooted kernel since the source has been published
thanks
SM-T237P
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.
OKAY so now I know my posts were getting deleted when I asked for T235 kernel root
zitomd said:
Would love to root my 5.1.1 tab , so I too would be begging for another developer to step in to fill this need. I need a kernel with UVC video support.
Click to expand...
Click to collapse
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)
mac231us said:
yesterday or may have been on Sat night, on the T533 thread I tried to catch moonbutt's attention by pointing to the T235 source (when apparently he was saying the T533 had no source but was addressing that kernel) and now that post has gone like on his closed thread (just when it seemed he was taking an interest thanking me for providing boot.img and other files)
anyway...need some dev who can volunteer to work on this and at least someone who would respond yes or no (deleting posts maybe to avoid a side conversation)
I pulled the source started to look it up and looked up on how to modify kernel..looked doable to a point but this is from a total novice (all i know is to mod some apk, compile/re-compile but no building stuff)
Click to expand...
Click to collapse
mac,
i had your post removed because it was interfering in H's thread. I tried with this device a little while ago but testers seem to think they are at liberty to not follow instruction, or just change their minds mid-stream like they haven't just wasted my time and resources. . The upside would be if you have the source and the setup to compile it and thereby test your own work then, i can absolutely run you through what you need to do, The tricky part is knowing which tools you need for the packing/unpacking of the ramdisk.
If this is a qcom/msm device you will need AIK which is the best solution.
If this is a marvell variant you will need ketut's degas bootimg toolkit which is the best solution.
You need [likely] to apply the patch mentioned in my thread to security/selinux/selinuxfs.c
Be aware that samsung's source releases are usually incredibly sloppy and the defconfigs for devices are usually somewhat off, missing config settings.
Check for sdcardfs xattrs, virtual xattrs, etc . you need to make sure those are selected in order for your internal and external storage to mount.
Find the correct defconfig for your device and post it as a zipped attachment. or check my thread and look at my sources on git, specifically the commit history [msm devices mostly] to get an idea of what you need. You can get a linux os running in a virtual machine and compile just fine as long as you have all the pre-requisites installed. The getting started link in my signature is a rough/general guide to help get you up and running.
m
ps, my thread is just locked, not closed, i was getting too many OT/non-dev postings. I open it when/if i have something new and then close it again.
thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)
mac231us said:
thanks moonbutt74...totally understand...appreciate the links in your signature and other resources...will start looking into it (long long journey but gotta try)
Click to expand...
Click to collapse
mac,
no prob, recommended step 1, get your linux distro set up, stongly recoommend kali/debian 2.0, either in vm or better as 2nd os in a dual boot scenario.
m

Need help wrapping my head around building AOSP for HTC One M9

Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!

Categories

Resources