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
Related
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
Hi, I would like to learn how to build a vanilla AOSP ROM with ubuntu.
Is the first time for me, so I need a complete guide. :angel:
thanks
Or someone can compile it for me... Pure Aosp without any tweak or mod...
And of course future update of aosp.
There are several guides, no this isn't a LMGTFY link, but it is a Google link. The first two are good guides.
Point being, you may need to refer to more than one guide until you have your build environment set up properly, and all the other variables in place. Might take you some time before you've built successfully, but it's a worthwhile experience.
Edit: obviously the links above point to some 4.2.1 resources, you can work your way around that with additional Google Ninja stuff. Seriously, go for it, it's fun.
No one is going to write you a personalized step-by-step guide on how to do it you need to read up and learn to do it yourself.
Start here:
http://source.android.com/
This section will tell you how to set up you pc to run it
http://source.android.com/source/building.html
As an example here is a guide to setting up an AOSP build environment, yes its for another device but it will give you an idea of what is involved in setting it up.
http://androidforums.com/optimus-m-all-things-root/619804-guide-building-aosp-more.html
Hi!
Just wanted to know if someone has started, or is thinking about starting, a Github account for Huawei U8800 (non-pro).
It looks like U8800Pro is starting to get somewhere: https://github.com/U8800Pro
So, if someone wants to do this then they can. And if they do want to do it, make sure you include trees for different android versions that are available. And no, there is no need to include trees that are not fully functional and will not be updated anymore.
Thanks. :good:
OK. I have taken up this task myself. Our github is here: http://github.com/U8800
Please give me suggestions as to which repositories should be added. I will start forking repositories from CyanogenMod.
For anyone that doesn't know why I want this done then it is only to make things much easier. It will be easier to download the whole source code for our phone from one github account. This will also give people a chance of downloading source code for what ever android they want and then build it.
Who ever wants to help me with this in any way then please let me know.
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.
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