Re: [android-porting] omapevm3530 kernel panic --- gingerbread

2010-12-27 Thread Srinidhi K V
Hi Deepak, When I start to make a generic build for ginger bread, I get the following output r...@srinidhi-desktop:/home/srinidhi/GingerBread_source# make -j4 PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=2.3 TARGET_PRODUCT=generic TARGET_BUILD_VARIAN

Re: [android-porting] omapevm3530 kernel panic --- gingerbread

2010-12-27 Thread deepak singal
I am also getting the same messages - r...@gingerbread# make PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=2.3.1 TARGET_PRODUCT=generic TARGET_BUILD_VARIANT=eng TARGET_SIMULATOR= TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm HOST_ARCH=x8

[android-porting] Re: Which platform manifest for android-2.6.37-rc7?

2010-12-27 Thread Joerie
Hi, > I've built the android-2.6.37-rc7 kernel already, but android-2.2 > platform manifest crashes at the init process. Are you sure you're running into a kernel issue? Assuming you've got the kernel config right, have you tried increasing the debug verbosity in init.rc? Joerie -- unsubscribe

Re: [android-porting] omapevm3530 kernel panic --- gingerbread

2010-12-27 Thread Hemanth
Hi, Since you have a shell, it is likely to be a framework initialization problem rather than a kernel problem. Try running logcat in the shell to see if it has some errors. The large number of untracked pid exit messages is also worrying. You can try increasing the init loglevel to see what was

Re: [android-porting] Re: Which platform manifest for android-2.6.37-rc7?

2010-12-27 Thread hedwin
Android 2.2 uses kernel 2.6.32. If you want to use another kernel some changes in bionic are/might be required. On Mon, Dec 27, 2010 at 3:06 PM, Joerie wrote: > Hi, > >> I've built the android-2.6.37-rc7 kernel already, but android-2.2 >> platform manifest crashes at the init process. > > Are you

[android-porting] LatinIME container height too small

2010-12-27 Thread Joerie
Hi, I'm having some trouble with the (revamped) LatinIME keyboard on 2.3 - it's height is somehow incorrect. In both portrait and landscape mode, it displays at roughly 1/5th of the screen height (whereas I'd expect it to be ~50%). The width is fine, spanning the full width of either portait or la

[android-porting] Re: Problem building opensles

2010-12-27 Thread Glenn Kasten
I am not aware of any ARM architecture assumptions, but I also have not tried building for other architectures such as x86. It sounds like the problem may be due to compiler toolchain version rather than the target architecture. If you do see any ARM architecture dependencies, please post here. On

[android-porting] x86 Creating filesystem error

2010-12-27 Thread wallace
I am building android for x86,when creating system.img,appear the follow error. Can anybody know how to fix it. make_ext4fs -l 128M -a system out/target/product/generic_x86/obj/ PACKAGING/systemimage_intermediates/system.img out/target/product/ generic_x86/system Creating filesystem with parameter

[android-porting] implement keypad and touchscreen driver on emulator

2010-12-27 Thread bryan
Hi All, I have a stupid question need you guys' help Is it possible to simulate the touch screen event on android emulator? Since I do not have real device to do this, I want to simulate the event on emulator first. If yes, how do I get started? I tried to hook kernel image when runnig emulator. B

[android-porting] Adding library to reference-ril

2010-12-27 Thread yellown1nja
I have a problem with adding a library to reference ril. I've created a library libtest.so which has few simple functions (socket connections). I added the source code of the library to / external/libtest. Android.mk is configured so that shared library is built. Building goes as follows: o...@ot

Re: [android-porting] problems with ALSA

2010-12-27 Thread srinath ramini
Hi Murali, In your asound.conf file AndroidPlayback pcm configuration details are not avilable. Replace your asound.conf with the following content and try it. ## ## Mixer Devices ## ctl.AndroidPlayback { type hw card 1 device 0 } ctl.AndroidCapture { type hw card 1 device 0 } ## #

[android-porting] init: critical process Service Manager exited 4 times in 4 minutes

2010-12-27 Thread Raghu N.B
Hi, Im porting android on Ti DM355 platform. I have applied the required android patches on kernel and build the RFS from android source. Im using TFTP for loading kernel and NFS for android RFS. The problem is when the init started executing, it is complaining "init: critical process Service Mana

[android-porting] IA Bring-up in the master branch: Instructions

2010-12-27 Thread Bruce Beare
I have uploaded the required changes to bring up IA in the master branch as well as the virtual box installer image. The changes are in queue and will likely take a little time to get into the master branch (no doubt, some will be re-factored along the way). The script below will pull in the requi