Hi
I have asked this before but I haven't gotten the answer and some things have changed.
My goal is to edit the kernel of my device to include rtl8192cu driver.
I have the sources from http://gitgub.com/puresoul/android_kernel_lge_d605 (I hope I got the link right) I am currently stuck at creating the .config file and getting the right files to include the driver. Could anyone help me out, any links to tutorials that actually tell me how to? The guides online are almost all specific to a certain device or their goal is different.
Related
Hi,
I would like to get involved in the XDAndroid development.
I already set up the working environment according to android hxxp://source.android.com
I know there must be lots of modules and patches to the kernel.
But what is the starting point for porting adroid to TP2?
Is there a guide or wiki, or anything I can start to check out source code and build the kernel?
Thanks.
There's a page on AndroidonHTC, here, which explains how to obtain the source and build the kernel. HTH
Yes, I saw that link.
It doesn't seem for Touch Pro2.
Look under the third section, titled
Building kernel for Diamond, Raphael, Blackstone, Topaz, and Rhodium
Click to expand...
Click to collapse
It's a multi-device kernel, so multiple devices all utilize the same git repository.
I followed the text, downloaded everything, set up the environment.
But the build.sh wont work, lots of errors.
Any detailed tutorial?
Things are constantly changing and I doubt anyone has time to keep an up to date guide. You'll most likely find better help in #htc-linux on freenode
First of all, I'm not a total newbie to this kind of stuff. I've already been creating firmwares for Different mobile Phones, some Linux-running routers and the Sony PSP, but this is my first try on Android.
At first I wanted to start off simply: compile the source on my Ubuntu and flash it - that's how I would start with any open-source 'from the scratch'-project. So I got repo, set it up and synced it, compiled it and created a zip with the rom kitchen to try if it even boots. Well it didn't (this is a bit more complicated than flashing a linux firmware to a router). Then I've taken a look a the update-script and modified it. The rom now installs successfully, but still doesn't boot. Wel my questions are:
1. Are there any guides on properly setting up the update-script? I didn't find anything, but maybe I didn't look in the right places.
2. I probably did everything wrong with the compiling. what are the options I get when I enter 'lunch' for? They should change settings for the compilation right? Am I good with the HTC passion option or do I need anything different?
Finally don't be angry because of my grammar/spelling, I'm from germany and don't get mad because of possibly 'noobish' questions, I promised I searched the forums and giyf.com
CrisisCorE said:
1. Are there any guides on properly setting up the update-script? I didn't find anything, but maybe I didn't look in the right places.
Click to expand...
Click to collapse
I too have searched for this with little to no success, so +1 on this...
Im also in need of a guide how to completely demolish/rebuild the update-script.
Someone who can point a finger?
Nobody? nothing?
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Hey guys!
I just got my serranoltexx and am fairly happy. However, I really would like to try and get AOKP running. Could any devs point me in the direction of where to start, you know, just bootstrap me with some reading? I have a background in Linux and UNIX, have developed some networking stack API projects on windows and have written a ****load of bash, perl etc. scripts in the past. I've also worked on the Matroska container format. Compiling etc. pose no challanges for me. However, I have never fumbled around with Android and I have no idea what drivers and other components might be needed. And how to start finding out what's missing...
I do know how to bootstrap my source repository and sync it... and in theory also how to compile AOKP - for supported devices, that is. What I don't know is: how do I start resolving unmet dependencies, and, you know, generally port a rom to a new device?
Please don't post if you haven't even compiled your own ROM yet. More likely than not, you'd be wasting your time.
I've posted on xda-dev as well, not sure which is the more suitable forum, possibly this one... Link to the other thread:
http://forum.xda-developers.com/showthread.php?t=2501539
And please don't post me to this guide right here as it is only of limited help. As I said, I know how to do it in general... You know, this guide:
http://aokp.co/learn/so-you-want-to-build-aokp-jb-ubuntu-1204
I tried to build it, but many things are missing once i flashed the *.zip.
Maybe i messed up with sources and patches.
Tell us if you have success! :good:
What specifics per device are needed to "match" roms to attempt a port or create cust
I'm pretty new at all this buy the basics of installing already made roms I get my question is when attempting to create new custom roms what information about the device say (cpu, gpu, modem, kernal, etc) need to match up to attempt using or moding those said parts of the dev process in order to build a working tree. Continued below Sidenote........
Sidenote : idk if the terms I used were correct in there placement or meaning but I feel that any who will reply to this thread probably grasp what I'm getting at.
So essentially what I'm attempting to do is figure out what things to change and how to change them in order to figure out what goes into building a rom or the favorable option that I'm shooting for is what to look for to attempt to match up a already built custom rom from another device I need little to no changes in order to use on my device's, reason being, both devices I am currently woking on, which are a Samsung Galaxy Core Prime sm-g360t and a HTC Desire 626s, do not have a official or even, to my knowledge, have an official CM and honestly besides one,the HTC which I have TWRP and it's running now off the AdvancedStock rom I found on this site and it keeps wanting to break or just doesn't work the way I want .
ANY HELP IS GREATLY APPRECIATED