I have downloaded a stock rom to play with and figure out. I checked it out in a kitchen and was looking over the file layout (2.67.651.4). I also download a kernel source from HTC DEV (2.6.32) to have a look at.
I would like to have a look at how the side volume buttons function. Does this need to be at the kernel source level or can that be seen in a ROM?
If someone could point me where to start looking I would greatly appreciate.
Related
Hi Forum Members,
I am trying to access the clock application that comes on the Samsung captivate. I noticed that its different than the stock clock application in the Android 2.1 source. The widget used to to type in numbers looks like its custom and not the phone widget used in the stock application. I downloaded and extracted the source but I don't see any of the custom samsung app implementations?? I also tried opening the captivate source using eclipse but there is no project file. Could someone point me in the right direction in getting a project created in eclipse using samsung source and accessing the samsung application. I am new to development on the captivate. Thanks.
The Samsung apps have not been open sourced. The things they've made open are the kernel (only the parts they had to, so even some custom stuff is not present) and the mods to the stock eclair tree that are required to build stock eclair. Look at the readme files for instructions on how to build that - there is no Eclipse project because there are no apps in the source and the method for building the kernel and stock eclair is all command line make based.
If you want to build a clock app, this isn't the level you should be working at. If you want to modify the Samsung clock itself, then you're out of luck because that is not open-sourced.
Thanks for the reply - you're right after doing some digging (and finding the README.txt) I realized that I wasn't going to find what I was looking for. Now I am currently building a stock samsung eclair build....
thanks again.
I am new to android development and started messing around and building the example source in Eclipse Helios. When I do new project > existing source and open up the Mms.apk source (stock, from android's git hub, it says the source has errors and they need to be fixed before I can build.
I tried this on my Ubuntu 10.10 machine and used repo to get the entire android source, thinking maybe having the entire platform source would help. I'm still unable to build the source so any edits I do are useless.
Can someone tell me what I'm missing? I know I'm doing something wrong or skipping something, but I can't figure it out.
Thanks
Sent from my Droid using XDA App
sorry to double post but i'm not sure why it says "Resolved", i think the app made me add it in or something. anyways the status is still currently unresolved. any help much appreciated.
bump??? i hate that it says resolved there...
Hi every one I dont know where to start i want to make my own rom from source,build it,modify it etc.But i dont know where to start.I know how to build rom from source(learned it from the tutorial on source.android) but i dont know what do those codes mean.i searched on google but cant find an easy tutorial.If i build rom from source how do i make it work on my phone.How do i FIX bugs on my roms,modify it Help please
Check out the chef central section under android. There are a lot of great people working on making development accessible.
For a pure AOSP ROM you are going to have a bit more work, but be rewarded in the end. There is also cyanogenmod and other custom distributions you can build from source and modify.
If you are familiar with C and Java programming you can dig into the actual development more by writing apps or changing source code. If you don't you may want to start on that road. Other wise you will be basically cutting and pasting from everyone else, which doesn't get you any credit.
Themes are also a good place to start. There are lots of good guides in the theme section and people are willing to help if you ask nicely and appropriately.
I have done a bit of this foot work and come to the conclusion, I need to learn programming then come back to source. It is overwhelming to take on an entire operating system in a foreign language, especially when that language has to be perfect to function!
Good luck in your endeavors. Feel free to hit me up for the little knowledge I have!
Sent from my PC36100 using xda premium
But! where to learn
First i want to learn the basics of Rom
are you familiar with Java, C and C++? These are going to be very useful in understanding the "codes" as that is what they are written in. You are also going to have to build AOSP specific for your device, which will require adding your device to the device tree and extracting the necessary drivers and files that are specific to your device. Cyanogenmod has many devices already added to their github and you would simply clone the folder for your device, then build AOSP source and issue make using the device specific folder.
THIS is a helpful tool, and yes it will compile pure AOSP as well.
THIS is also a very helpful tutorial, and you can modify instructions to work for Gingerbread.
If you just want to learn to build and modify the source start with Cyanogenmod build from their source first. You can also build the kernel if you choose but that is a bit more complicated. After you have both of those building without errors then start making changes that you want to see.
The CM Wiki has some good info http://wiki.cyanogenmod.com/wiki/Building_from_source
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book
hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD
My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?
hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
I've been trying to find the best way to compile. I found a guide on youtube "http://www.youtube.com/watch?v=IV4jhXWc7AE", but it is a little outdated and I'm having some trouble following him. The kernel source that he has has a lot of folders and the only kernel source I've found for the N5 has 2 files. So I'm missing something in finding the kernel source it seems.
It would be awesome if I could get some help and maybe pointed in the right direction. The only problem is that I'm a auditory and kinesthetic learner.
I have Ubuntu installed and ready to go, I also have the lastest NDK, and I have the AnyKernel.zip.