Has anyone successfully compiled the android kernel and tested it in the Android emulator, and if so is there anything that special that needs to be done? Documentation for the SDK is excellent, however documentation for compiling the kernel and setting up a custom machine in the emulator has been hard for me to find.
I am needing to make a kernel for a certain device. There aren't any source codes available for that device but there are for multiple clones out there. I am running Linux Mint Debian edition and i cant find a guide for compiling a kernel on debian.
I'm trying to compile kernel for A10 Aurora i have a couple of questions.I'm using this guide for make a custom kernel.Compiled allwinner-v3.0-android-v2.Btw my laptop is running ubuntu 32 bit 2 cores 30gb hdd on VMware workstation.
I made zImage, uImage and modules without getting any errors but how to flash them to the device?Using adb? making boot.img making cwm zip how to pack them?
Code: OBJCOPY arch/arm/boot/Image Kernel: arch/arm/boot/Image is ready[code]....
Last week, I played around with getting a custom recovery built for INQ Cloud Touch..
After compiling - flashing recompiling re-flashing for almost a week and on the verge of giving up ...
I realized, searched and found flash_image ... come to find out custom compile of recovery was fine, fastboot did not like my device and wasn't flashing it properly.
So flash_image got the custom recovery working as suppose to, able to backup/restore ... Flash roms.. however there are no roms.. best i could do was try roms from devices close to this one, with no luck!
So i decided i would try my hand at making a 2.3.7 gingerbread rom. Of course stock is froyo 2.2.1 and before i can make the rom.. i need a kernel for gingerbread. So I got the cm-kernel source using this guide:
[EDIT] pulled my .config file using both /proc/config.tgz and the included script to pull it from the boot.img [/EDIT]
Now, i been trying to get kernel compiled for the last 5 days.. and like i said, no lack of searching and reading... Had first error, forgot what it was now, but i got it fixed and compile went on.
Code: LD .tmp_vmlinux1 arm-eabi-ld: no machine record defined arm-eabi-ld: no machine record defined arch/arm/mach-msm/built-in.o: In function `parse_tag_msm_partition':
I have a notepad full of things i have enabled/disabled and restored to original trying to find what is missing or shouldn't be there!
I am trying to compile a kernel for LGE-P690 from CM ICS source but i don't have the device in my hand i searched all over the net for vendor files but i was unsuccessful in finding vendor files for ics but i found one for gingerbread so is there anyway i could perform ./extract-files.sh without device or can i convert gingerbread vendor files to ics if so how elaborate.
Code: make: /home/dm47021/Android/toolchains/arm-unknown-linux-gnueabi-linaro_4.8.2-2013.08/bin/arm-unknown-linux-gnueabi-gcc: Command not found /bin/bash: /scripts/gcc-version.sh: No such file or directory
when I compile android (http://source.android.com/download) it does not compile some source files. For example there is external/bluetooth/bluez/sbc/sbc.c which is not compiled. There are also other such files.
It's possible those files need not to be compiled. Or it might be that I need some special configuration to compile them.
Either way, if it is possible, I'd like to compile them. Is there some way to do it? Maybe some "compile_all" make target? (I believe the reason why I want to compile all source files is not important)
I just went through the process of compiling a custom ROM and they used a stock kernel. I would like to incorporate a different kernel when I compile and instead of the stock. I know I could compile them separately and have them flash together but I want one zip to flash. Just would like to go through the process to learn.
I have vanilla linux kernel version 2.6.27. I want to apply android specific patches and convert it to android linux kernel 2.6.27. Where can a user find the patches to convert a normal vanilla kernel into android kernel?
1. I updated to stock 2.1 using the sprint update tool. 2. I followed the video tutorial to root the phone 3. then i used joey's page (http://www.joeyconway.com/sdx/custom/index.php) to install the his kernel (joeykrim-SDX-kernel v2.0.4 (includes root)).
I have done nothing else to the phone but this and removing a couple of bloatware apps (i checked the list of permitted deletions before i removed anything.) I have not installed a new recovery..at least i dont think that I did as part of one of the other operations I performed (as an aside, i am not really sure what the custom recovery is or what it is used for, so i didnt install it...i guess i need to read up more...)
So that is where I am..but i have a couple of questions.
1) i am now having issues with my wifi connection - the signal reception is very spotty in areas where i should have atleast 2 bars of reception, and the wifi often cuts out completely....Is there any know corellation between joey's kernel and this wifi issue? I have searched the forums and have found nothing that answers this.
2) Is there an easy way to get back to the stock kernel? I have read that i can get back to stock everything by using the sprint download center where I did my original 2.1 update. But is there a way to get back to just the stock kernel without wiping the phone?
I currently have bekit 1ghz kernet installed, but I was interested in trying out some other kernels. Can I just install them via Rom Manager over the first kernel? Or is there some kind of uninstall process I should use first?
I'm working for Freescale Semiconductor on the i.MX series linux BSP. Now we have android running well on i.MX515 platform, and hope to push android kernel repo into android.git.kernel.org. Then what's the process need us to follow? How reviews will be done? And what we should provide?
I want to make some changes to the stock Mms Android application and install it on my device. However, I have problems with compiling the code checkout obtained from git. I have created a new Eclipse Android project with "use existing sources", setting the target framework to 2.1. However, Eclipse does not find some needed framework classes, e.g. android.telephony.SmsManager.
I have the whole Android toolchain set up and working (make finished without errors), Eclipse is running on Sun Jdk 1.5.
Perhaps my mistake was that I did not copy the .classpath file into the new project, I will check this. Never the less, should I succeed, will I be able to install this .apk into a non-rooted device?
I am working on windows with JDK, Android SDK and eclipse set successfully. I download the com.android.sdk package from: http://android.git.kernel.org/?p=platform/packages/apps/Stk.git;a=summary
But when I import the project to the eclipse, errors happen everywhere. Mostly is about the com.android.internal.telephony.gsm.stk.something cannot be imported. I googled to find the reason. It only says because of the these packages is internal package and cannot import with standard SDK. So the question is: How can I compile this project? Should I make a linux environment and get the whole android source code to do this?
I'm going through a tutorial here: http://mobile.tutsplus.com/tutorials/android/android-sdk-development/.
I have finished the tutorial and I've set up my debug configuration. When I actually try to run the debugger I see a popup that says: "Your project contains errors. Please fix them before running your application."
In the "Problems" tab of eclipse, It says Errors 1 Item: Unparsed aapt error(s)! Check the Console for output. The location of the error is listed as unknown. When i switch to console, this is what's in there:
I'm not sure what to do about this. Where would i get those files/What's the next step?
I updated to 1.5 SDK pre, together with the ADT. I followed the instruction to select Android 1.5 as target by right clicking on the project, Preferences>Android. In this window there are 3 options, Android 1.1 Android 1.5 Google APIs
I selected Android 1.5 and Apply, clicked OK. Application compiled nicely.
If I go back to the same Preferences and select Android 1.1, Apply, I can no longer compile my application successfully. I get hundreds of the same error R cannot be resolved
Then I try to open this project in another computer that I have not updated the SDK yet. I get the same error. I'm trapped until the new SDK is out.
I am following the instructions on code signing on the Android Developer site, and it mentions that if you specify that you want to compile in Debug mode, it automatically signs the resulting file with a debug key. It also says that if you specify that Eclipse should compile in Release mode, that you can use the Export Wizard to generate a private key and handle the distribution signing.
Can someone point me to the setting in Eclipse for Release vs. Debug compiling. When I use the Export Wizard, I am only given the option to export unsigned. I am pretty sure I am stuck in Debug mode, since my app has no problem running in the emulator or my tethered G1.
I downloaded the HEAD revision of the Voice Dialer from GIT (used the web interface) but there are so many errors and I have no idea how to fix them.I did the same thing for the 3D Gallery and that turned out fine. But the Voice Dialer is a completely different story.
I am trying to compile and run the Android Camera for sdk 1.6 (also called API level 4 or Donut release). While there is no minSdkVersion in the AndroidManifest, it clearly does not run on a donut device. In fact, if compiled with sdk 2.2 the camera will crash with a NoSuchMethodError execption on an avd or a G1 with sdk 1.6. I tried also checking out the [donut-release] tag, but, strangely, it won't even compile giving many errors like:
[javac] /home/mrucci/camtest2/src/com/android/camera/ImageManager.java:41: cannot find symbol [javac] symbol : class DrmStore [javac] location: package android.provider [javac] import android.provider.DrmStore; [javac] ^ [javac] /home/mrucci/camtest2/src/com/android/camera/Util.java:32: cannot find symbol [javac] symbol : class MediaMetadataRetriever [javac] location: package android.media [javac] import android.media.MediaMetadataRetriever; [javac] ^ [javac] /home/mrucci/camtest2/src/com/android/camera/MenuHelper.java:29: cannot find symbol [javac] symbol : class ExifInterface [javac] location: package android.media [javac] import android.media.ExifInterface; ... [javac] ^ [javac] /home/mrucci/camtest2/src/com/android/camera/ActionMenuButton.java:81: cannot find symbol [javac] symbol : variable mScrollX [javac] location: class com.android.camera.ActionMenuButton [javac] mScrollX + mRight - mLeft), [javac] ^ [javac] /home/mrucci/camtest2/src/com/android/camera/ActionMenuButton.java:81: cannot find symbol [javac] symbol : variable mRight [javac] location: class com.android.camera.ActionMenuButton [javac] mScrollX + mRight - mLeft),
In particular, I really do not understand why ExifInterface is used in the "donut" tag when it has been introduced since API level 5.
I have a jar that I need to reference from my Android project. I also have the src of the jar, so I could include it in the project itself. I was wondering if referencing a jar vs. compiling it in with the project using Dalvik makes any difference in terms of final Dalvik package size that gets generated.
My app requires that devices are running at least Android 2.0 OS. Would it make more sense for me to compile my project with the 2.0 SDK or does it make more sense to always compile my project using the latest SDK, even if it's well beyond 2.0...?
The problem with compiling against 2.1 for example would be that I don't know if an Android 2.0 device would even run an app compiled with 2.1...?