[android-porting] Failure to mount ext3 partition inside init.rc after loadable module

there is any limitation to that in android environment? Would anybody have any suggestion to solve the issue of installing loadable module and mount at "init" section of the android initialization? -Sean -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.

[android-porting] Where does Android get the screen info from linux device driver in TI OMAP3630?

,because I changed the screen info in driver. So does anybody experience this?? regards, Sean -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

[android-porting] Please let me know the way to change the resolution of Emulator.

Dear all Hello. I've faced a problem. I'm using Android X-86 using virtual box. What I want to do is changing the resolution of emulator to 480x480 size. But after changing the resolution of emulator, Emulator stopped with this message."Unfortunately, Launcher has stopped" So If

[android-porting] Re: Ringtones in last build

You need to read frameworks/base/data/sounds/AudioPackage2.mk. Basically, there are 2 sets of audio files now. One for limited flash devices, one for those that have more room. So you have to include the .mk for the set that fits your environment. This would be done in your vendor/xxx/xxx/Andr

[android-porting] Re: Ringtones in last build

Hi Michael, I'm not certain I follow your issue. What is your device subtype? I've taken out the -fno-short-enums as that is default on the newer baseline. Perhaps you could check "make hide=" and make sure that option is passed to the compiler. Michael Trimarchi wrote: &

[android-porting] Re: GSM Modem

IMHO this would be a really bad feature and a severe security hole. Android should never allow this. This is one reason I've always opposed a separate multiplexer daemon as it would allow more than just the RIL to talk directly to the modem. fgilani wrote: > Is it possible to send AT commands

[android-porting] Time for some additional groups?

those would help as a beginning. Cheers, Sean --~--~-~--~~~---~--~~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~--~~~~--~~--~--~---

[android-porting] Re: bug report: alsa_sound

This is NOT a bug in the alsa code. This is a bug in your alsa kernel driver. We could, however, make this a non-fatal condition. xro wrote: > better with all the method... sorry > > // Stop the transfer when the buffer is full. > err = snd_pcm_sw_params_set_stop_threshold(mHandle, >

[android-porting] Re: ALSA buffer size

there are 2 of these structures defined in hardware/alsa_sound/AudioHardwareALSA.cpp. Look for static StreamDefaults _defaults one is for playback, and one for record. You are interested in the one for playback. There are 2 things that are meaningful for this issue in this structure: latency

[android-porting] Re: We want to port android on FPGA as part of master thesis. Please help

FPGA stands for Field Programmable Gate Array. It is essentially programmable hardware. The answer to such a query is no, Android cannot be ported to an FPGA. You would basically need a 32-bit cpu core placed on the FPGA along with supporting hardware. Then port Linux onto it, then Android. An

[android-porting] Re: We want to port android on FPGA as part of master thesis. Please help

Which OMAP are you using? Are you aware of TIs omapzoom.org? The OpenCore codecs are already ported to the OMAP3 3430 DSP. Elvis Dowson wrote: > Hi Vince, > > On Mon, Aug 3, 2009 at 11:04 PM, Vince > wrote: > > > Please keep me informed on porting Android to X

[android-porting] Re: a problem about ALSA - Not building

The ALSA interface conforms to the master branch. You appear to be building against cupcake. There isn't a cupcake branch of the ALSA interface at this time. Demetris wrote: > > Hi Guys, couldn’t not notice that you are trying to make Alsa work. > > I have done: > > 1. > > git clone git://andro

[android-porting] Re: a problem about ALSA - Not building

e Android 1.5? > > Thanks. > > > > On Aug 18, 11:36 pm, "Demetris" wrote: > >> Tnx. Really appreciate the help. >> >> -Original Message- >> From: android-porting@googlegroups.com >> >> [mailto:android-port...@googlegroups.c

Re: a2dp (WAS Re: [android-porting] fix alsa compilation problem Eclair)

None of these changes will be accepted. The ALSA code has already been submitted against Eclair and master branches by Wind River which has significant changes. Jim Ancona wrote: > Michael, > > I'll try your patches this weekend. Since I assume you're willing to > contribute your patches back to t

Re: [android-porting] Re: eclair patch for arm920 s3c244x family

low and drawing is slow, then waiting on sync could very well be the issue. Cheers, Sean Alexey Roslyakov wrote: > Michael, > I tried to implement page flipping in s3c2410fb. No luck. Performance > is worse than in case without flipping. > I suppose SurfaceFlinger uses memcpy (or

Re: [android-porting] Re: Error Building Eclair for a generic ARM target w/ ALSA

t branch sources are being used to compile for eclair. Some minor bugs still exist for the latest code, but they are being addressed. It all certainly compiles and works on a number of platforms when the appropriate branch is used. Cheers, Sean > On Dec 1, 11:59 pm, whiplash wrote: > >&

Re: [android-porting] Re: Error Building Eclair for a generic ARM target w/ ALSA

Yes, that is what I am saying. It is in the korg repo under both the eclair and master branches. zp wrote: > Hi Sean: > > Are you saying that ALSA is working with Eclair now? no major > problems? > Where should I get the ALSA package? > > On Dec 11, 1:13 am, Sean McNeil

Re: [android-porting] Re: Error Building Eclair for a generic ARM target w/ ALSA

Fasil wrote: > Hi Sean, > > you are right I found out the correct version of Alsa for donut and > took the snapshot from the gitweb of android.. > > http://android.git.kernel.org/?p=platform/external/alsa-lib.git;a=tree;h=refs/heads/donut;hb=donut > > I took the snapshot

Re: [android-porting] Re: ALSA mixer,re-sampling code Vs Android Mixer,re-sampling code

On 01/18/2010 05:27 PM, ani wrote: The pcm_dmix.c is not compiled in the Android alsa lib. I have compiled this c file and DMIX is working for me. My questions are still the same: a.Can we use the ALSA mixer(DMIX-i enabled in my system) for mixing streams instead of android mixer?If yes

Re: [android-porting] Re: alsa_aplay error

It would have been a lot easier to just run stop media before alsa_aplay. Cheers, Sean On 01/29/2010 01:56 PM, Srikant wrote: Hi, I modified the permissions of the /system folder in the init.rc, then I could able to kill the mediaserver process and able to run the alsa_aplay. thanks

Re: [android-porting] [Kernel 2.6.31 + Eclair 2.1 porting] init.rc commands not interpreted

/init.rc is not a bash script. It is an init script and it is interpreted by the init process. On 06/28/2010 05:01 PM, fpirou wrote: Hi, I am newbies at android porting. I compiled 2.6.31 linux kernel and Android 2.1 (eclair) for an iMX25 (ARM926EJ-S) target. But, when I mount Android file sy

[android-porting] opencore test apps are broken

Are there any plans to support these apps anymore? Try adding BUILD_PV_TEST_APPS := 1 to your BuildConfig.mk and you'll see that they don't compile. Sean -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

Re: [android-porting] Re: [Kernel 2.6.31 + Eclair 2.1 porting] init.rc commands not interpreted

My guess would be something regarding nfs options that make the file not interpreted as a unix file. Either that, or the init.rc is improperly formed. On 06/29/2010 10:32 PM, fpirou wrote: Do you have any idea why the init process does not interpret the init.rc command file (invalid option)?

Re: [android-porting] Emulator display magic?

Take a look at the system property ro.sf.lcd_density. For a QVGA screen, you want to set it as ro.sf.lcd_density = 120 to get the proper scaling. IMHO, the density should not be necessary and scaling could be done via the dpi. But for some reason it isn't done. Sean On 9/14/2010 4:

[android-porting] Opencore version 2.50 issues

eed solve my problem with MP4 software codec playback. Sean -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting diff --git a/android/playerdriver.cpp b/android/playerdriver.cpp index 6f7c03d..fe407a5 100644 --- a/android/

Re: [android-porting] Mechanism for working with new hardware after docking

This is all handled by the init program. Check it out. It even loads binary blobs. On 10/4/2010 11:02 PM, Great White Pin Geek wrote: I'm wondering what the proper way is to dynamically load/integrate device drivers for hardware that becomes available when a device is docked. For example, say

Re: [android-porting] Re: Opencore version 2.50 issues

don't know if tremor is necessary if you do. There will be an error of an undefined method locale(). Just comment out the line that calls it. Cheers, Sean On 10/14/2010 11:03 PM, samy wrote: Hi, i have big confusion with your patch. because andorid 2.1 update 1 , this code comes with

Re: [android-porting] How to run insmod during boot-up?

Most likely, you are attempting to do them in the init.rc before the /system volume is mounted. On 3/4/2011 3:23 PM, Amit Pundir wrote: On Fri, Mar 4, 2011 at 11:48 AM, Lay wrote: Hi Android Porters, I would like to insmod 2 driver modules during boot-up. I tried adding the following lines t

Re: [android-porting] Re: how to integrate s/w codec like h/w codec (omx plugin) into stagefright

On 3/9/2011 8:57 AM, kismeter wrote: On Mar 8, 10:44 pm, Joerie de Gram wrote: You can use c++filt to demangle C++ symbol names. The method you're looking for is android::createOMXPlugin(). Joerie thanks but why add "_ZN7*" or when add "_ZN" You should never be declaring anything in such a

Re: [android-porting] Re: IDE for Android

I use eclipse to compile Android. It works pretty well, but I've never found a means to get the parser to work with both C/C++ and Java. I use a C/C++ project. On 3/9/2011 11:25 AM, RD wrote: Thanks for your reply. I have already built android for ARM and for X86 using the command line. I just

[android-porting] Re: Porting to a new product (preffered directory structure)

Are Android's porting websites down? http://source.android.com/porting/ Gives me an error 404 On Apr 7, 1:25 pm, freakingtux wrote: > Hello > > I would like some information about porting to  a new product. I am mainly > interested in understanding the preferred directory layout > to perform mo

[android-porting] Re: Where Google Android porting is unreachable

On Apr 11, 7:15 am, Nikita Kozlov wrote: > Hello Folks, > > Somebody have a clue why the google porting guide is unreachable (404 > not found) ? > I believe it's not necessary to remind (to google people) how much > useful it was for us (developers). This site has been down for me for two days.

[android-porting] touchScreen port

Hi, Where does one configure the input for a port? In order for me to make touchscreen work I had to hard code mParameters.deviceType to Parameters::DEVICE_TYPE_TOUCH_SCREEN; Where am I supposed to set the “touch.deviceType” property for a port? Sean -- unsubscribe: android-porting+unsubscr

[android-porting] Kernel configuration for CGROUPS, recommended settings

ce virtual servers and checkpoint/restart jobs. Beyond that are there specific recommended CGROUP configs that should be set? Thanks, Sean -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

[android-porting] external/guava not compiling

It looks like the new JB branch of external/guava does not compile for me with the sun java on Ubuntu 12.04. I get the following error: external/guava/guava/src/com/google/common/collect/Maps.java:542: incompatible types; no instance(s) of type variable(s) K,V exist so that java.util.TreeMap c

Re: [android-porting] Re: external/guava not compiling

<https://github.com/CyanogenMod/android_external_guava/commit/c8b97210aa31c9b80b5fd136d8617ebe4e731e09> On Tuesday, 10 July 2012 13:12:23 UTC+5:30, Sean McNeil wrote: It looks like the new JB branch of external/guava does not compile for me with the sun java on Ubuntu 12.04.

[android-porting] LCD , Camera and Battery porting

Hi I am a beginner for Android platform development. Should I get IHV Linux driver open source for LCD Camera and Battery porting ? Can these devices use generic drivers ? If we do not have IHV battery driver , can Android power management use generic battery driver ? Thank for your guid

[android-porting] Need help on Android 6.0 on : how to enable the ip forward functionalityvia adb on Android 6.0

In a recent project , I have enabled 2 network cards on the Android 6.0(1 for internal networks and 2 for external internet, the client can ping its own gateway by now )---now I want to enable the ip forward for these 2 networks so that intranet client also can access internet via network 2, bu

[android-porting] Re: graphics initialize failed?

The /dev/pmem and libhgl.so errors are fine. They relate to optional capabilities you don't have. You should, however, have the Android devices in your kernel. The Android binder and power devices are quite essential. 宇江 wrote: > Hi, > > I have a arm926ej-s board which has a 800x600 LCD. > I h

[android-porting] Re: Android on OMAP35x ?

Wind River has used the TI OMAP Zoom platform as a reference target for a long time. They even showed it at the Barcelona conference early this year. Nishanth Menon wrote: > 伊泽 said the following on 11/09/2008 10:50 AM: > >> Beagle Board? >> >> > No, it is zoom MDK[1] > >> ==

[android-porting] Re: About android touchscreen

I have submitted patches to Google which adds support of a /system/etc/pointercal (aka. tslib) file for translating coordinates. I didn't add ts_calibrate into the phone, however. That would be nice to have so you can calibrate the screen on 1st install. Anson wrote: > Hi all: > > We use a res

[android-porting] Re: Filesystems (yaffs2, jffs2 and nfs)

mvniekerk wrote: > Well, I can help you with this much - jffs2 + Android = No Go. It will > Not true. Android runs perfectly on the Openmoko Freerunner using JFFS2 for root and system. You need to qualify your statement as the only real partition that needs mmap is the /data partition. What

[android-porting] Re: Audio support

Hi Maxime, Wind River is in the process of submitting an ALSA audio implementation. That is what I use on the Openmoko Freerunner and what has been successfully used on the TI OMAP Zoom reference platform. Maxime Petazzoni wrote: > Hi, > > I believe most of the porting efforts on the various h

[android-porting] Re: Can't run Android's executables...

The results below do not indicate armv5 support. It could and most likely is not generating armv5 instructions for a simple "hello world" program. You would have to do something more elaborate and check the assembly. Wang Mac wrote: > I believe 8250 can run armv5 code generated by android tool

[android-porting] Re: Can't run Android's executables...

Hi Rupesh, I guess a simple program that uses __builtin_clz() would be enough. Rupesh Gujare wrote: > Can you explain what test, we can do ? I am ready to to send back results. > > Regards, > Rupesh > > The results below do not indicate armv5 support. It could and most > likely is not ge

[android-porting] Property name too long

The maximum property name length is 32 (including the null), but there is the following property that causes the location provider to crash: ro.com.google.enable_google_location_features What is the correct solution: increase max name len, or change the property name? --~--~-~--

[android-porting] Re: Can't run Android's executables...

__builtin_clz() is a built in function understood by the compiler that generates the assembly instruction "clz". The error you reported seems to indicate your compiler isn't complete. Rupesh Gujare wrote: > Sean, > I am new to toolchain arena, can you tell what is mean

[android-porting] Re: Can't run Android's executables...

ction instead, or you can configure your kernel to use the high-mem address instead of register. Wang Mac wrote: > Hi Sean, > > I tried __builtin_clz() test. It can be run and the results are > correct on my QCOM8250 board. > > Basically QCOM8250 supports armv7 instruction set, it&#

[android-porting] Re: Can't run Android's executables...

> could you please tell me where is your main patches resource. > (openmoko? or where?). I'll try it... > > Thanks, > Mac > > 2008/11/13 Sean McNeil <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > > Oh, I see... > > Does your target h

[android-porting] Re: Can't run Android's executables...

atches (I googled), > could you please tell me where is your main patches resource. > (openmoko? or where?). I'll try it... > > Thanks, > > Mac > > 2008/11/13 Sean McNeil <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > > >

[android-porting] Re: Is GSM Modem multiplexer necessary to use GPRS in Android ?

Hi, Yes, it is somewhat essential when there is only one interface channel to the modem. I have already developed a multiplexed GSM RIL for Wind River. We are working on gprs issues at the moment and intend to open source it when done. Wang Xiaoguang wrote: > I am working on GPRS in Android.

[android-porting] Re: Is GSM Modem multiplexer necessary to use GPRS in Android ?

Wang Xiaoguang wrote: > Does a GSM Modem with multiplexer always creates two devices in /dev/ ? > > If I have only one device in /dev/ for modem, does it mean that this > modem have no multiplexer ? > > On Fri, Nov 14, 2008 at 12:44 PM, Sean McNeil <[EMAIL PROTECTED]

[android-porting] Re: page flipping

Benno wrote: > On Nov 4, 1:01 pm, Mathias Agopian <[EMAIL PROTECTED]> wrote: > >> Hi Ben, >> >> On Nov 1, 8:11 pm, "Ben Leslie" <[EMAIL PROTECTED]> wrote: >> >> >> >> >>> The current documentation implies that everything should work on >>> devices where double buffering (panning) isn't sup

[android-porting] Re: Android on Freerunner image and some instructions

page: ADBHOST=neo ./adb logcat Sean AndersHedberg wrote: > Hi, I'm out of luck trying to get the Freerunner displaying anything > but the sudden white splash and then the black screen right after > having unpacked the kernel. I've followed every single instruction I > could fi

[android-porting] Re: Filesystems (yaffs2, jffs2 and nfs)

e: Filesystems (yaffs2, jffs2 and nfs) >>>>> >>>>> >>>>>> I may have a similar problem here. I'm trying to run Android entirely >>>>>> off the SD card (actually, microSD, on the Zoom). I made t

[android-porting] Re: Filesystems (yaffs2, jffs2 and nfs)

Android >>>>> root filesystem >>>>> >>>>> Using the following bootargs : 'console=ttyS2,115200n8 ip=none rw >>>>> rootwait root=/dev/mmcblk0p3 init=/init' and the following bootcmd : >>>>> 'mmcinit;fatload mm

[android-porting] Re: Filesystems (yaffs2, jffs2 and nfs)

: > Thanks. That is exactly the patch that I submitted and linked to, and is > what I meant by "Removing lines 257-259". If this is a well known problem, > btw, why wasn't it already fixed? ;P -J > > -- > From: "Se

[android-porting] Re: After executed /init, VM is not running...

It is most likely that you do not have the Android device drivers enabled in your kernel. You really need them to be present. Another possibility is you are using a newer kernel which places devices in a different location in the /sys tree. In that case, you'll need to add an option to your .c

[android-porting] Re: android jffs2 missing for freerunner

The jffs2 image has been temporarily removed because of licensing issues with MP3 and other audio/video codecs. It will be restored once I have eliminated the problem. I do not have a timeframe for this to happen at the moment. Sean [EMAIL PROTECTED] wrote: > Hi, > > I want to f

[android-porting] Re: Help to port android on openmoko

tree to an NFS mountable directory and create a jffs2 image. So, as you can see our ultimate goal is to do just as you suggest. Sean Davide wrote: > Very thanks for your very complete and clear explanation. > > To install android on freerunner it was very nice to > have a setup scri

[android-porting] Re: use of inbuilt video codecs

You've already figured most of it out. You'll need to check pv.com and how Packet Video does things. I think they have an SDK to develop hardware codecs. Then you'll want to modify external/opencore accordingly to use your hardware codecs. Pivotian wrote: > I suppose that Android uses the OPEN

[android-porting] Re: Android make

To get a different compiler, you'll need to set in some place like your build/target/product the location of your compiler: override TARGET_TOOLS_PREFIX := $(TOPDIR)../cross/bin/arm-eabi- Then you'll need to use different compiler settings in build/core/combo/linux-arm.mk. I don't know if my p

[android-porting] Re: Help to port android on openmoko

needs to be open sourced by the owners (which they fully intend to do). And then there are non-Android commitments I have... Sean Davide wrote: > If you like, I can help you with code > or some other stuff if you wish ... > > > 2008/11/26 Sean McNeil <[EMAIL PROTECTED

[android-porting] Re: Audio support

There are a few things you can check: 1) Make sure you have an ALSA audio device enabled in your kernel. 2) Check from a shell if the directory /dev/snd is created and if there is anything in it. 3) Provide your /system/etc/asound.conf file that you are using to describe the audio devices. Sean

[android-porting] Re: Audio support

Maxime Petazzoni wrote: > Hi Sean, > > On Nov 27, 11:01 am, Sean McNeil <[EMAIL PROTECTED]> wrote: > >> There are a few things you can check: >> >> 1) Make sure you have an ALSA audio device enabled in your kernel. >> 2) Check from a shell if the

[android-porting] Re: ARMv4, different file systems, and other patches.

]> wrote: > >> I haven't had time to clean up my patches sufficently to submit them >> for formal review, but I'm going away for two weeks tomorrow, and I >> don't want people unnecessarily re-inventing the wheel (although Sean >> and I seem to have gone

[android-porting] Re: Audio support

asound.conf should go in /system/etc/asound.conf, not /etc. Most of the time /etc is a symlink, so it doesn't matter. You will probably have to go through your complete asound.conf to see if it is correct for your hardware and kernel. The best suggestion I have is to use something like "alsact

[android-porting] media player without PV

odecs that require the patent disclaimer. It looks like some of the media scanning might also include code with questionable patent claims (mp4?), so I'd want to eliminate that as well. Sean --~--~-~--~~~---~--~~ unsubscribe: [EMAIL PROTECTED] website: http://gr

[android-porting] Re: Help to port android on openmoko

want to do. I'd love to get everything cleaned up and accepted, however. Can you share them with us? Sean frma wrote: > Hello, I've updated Sean:s orignal patches for armv4t support in > bionic according to the comments of the reviewes, what is the proper > procedure for me

[android-porting] Re: Help to port android on openmoko

er comments. Once those are accepted, yea, Sean is going to get > rebase conflicts during "repo sync", unless he abandons the branch the > patches were done on. That's the price he pays for publishing his > work and letting someone else handle getting them through the revie

[android-porting] Re: Problems with PPP on Android - Omapzoom

Hi Mikkel, For issue 1 we took a slightly different approach and used the attached patch. Sean Mikkel Christensen wrote: > Hi all, > > Sorry for the long post, but thought this might also help others > trying to get PPP over GPRS running on Android! > > We are trying to get

[android-porting] Re: problem when using gcc-4.3.2

Don't use 4.3.x. Use gcc 4.2.4 or older. Damwid wrote: > Hi all, > > I'm trying to use gcc-4.3.2 from codesourcery to compile android, and got > the following error when compiling: > > target Prelink: libdl > (out/target/product/zoom_mdk/symbols/system/lib/libdl.so) > external/elfcopy/elfcopy.c

[android-porting] Re: problem when using gcc-4.3.2

As far as I can tell, it is external/elfcopy that is the only issue preventing newer versions of gcc from working. I'm sure this will eventually be updated to work with them. Yang Xiaopeng wrote: > Thanks Sean, > > I wonder whether android will support newer version gcc so t

[android-porting] Re: Android on freerunner

Suspend/resume is a known issue. It is actively being worked on. In the meantime, change the setting/display screen timeout to never. Davide wrote: > Hi, > > after some time that android on freerunner is in stand by, > then the screen is locked. Pressing the power button will > make it wake up,

[android-porting] Re: Android1.0 on to s3c6400 + Home sceen Lock

Hi Ajay, If you see that the initial screen is all gray instead of just a portion of it containing the information below, then you are missing some changes for either armv4 support or TLS. I can't remember which one causes the sizing issue with that dialog. A dump of logcat would be very help

[android-porting] Re: Porting to DaVinci EVM

I don't think it is going to work that way. You have a different linker/loader and all that which has to be in specific directories from root. I think you'll have to do a chroot. That is what I do: chroot /root /sbin/init (I've moved init to the more appropriate /sbin directory). Either that,

[android-porting] Re: Porting to DaVinci EVM

result from a linker problem? I am pretty > much a beginner and feel lost. Some more clues would be welcome. > > Thanks a lot, > Francois Minaud > > I tried the changes you suggested but pretty akwardly I guess as I > come up with the same strace result. > > On Dec 11, 5:08

[android-porting] Re: Porting to DaVinci EVM

-gnueabi toolchain > to build the Android source code and compile the kernel for my board, > gcc version is 4.1.0 (got some warnings during kernel compilation). > > > Francois Minaud > > > > On Dec 11, 5:58 pm, Sean McNeil <[EMAIL PROTECTED]> wrote: > >> An

[android-porting] Re: Porting to DaVinci EVM

gt;>> but in my case when I directly boot on the Android file system, >>> nothing is displayed... init always crashes and if I try to boot >>> without the init=/init defined then I get a kernel panic. >>> >>> How may I check the loader? >>> >

[android-porting] Re: Porting to DaVinci EVM

ned then I get a kernel panic. > > How may I check the loader? > > Thanks for your fast replies and advices. I really appreciate > > Francois Minaud > > > > On Dec 11, 6:45 pm, Sean McNeil <[EMAIL PROTECTED]> wrote: > >> You could try to kick android of

[android-porting] Re: wpa_supplicaent

Are you even certain you have the wpa_supplicant binary? Can you run the command from the shell? Richard Zhao wrote: > It still don't work. > > 2008/12/10 nagamatu <[EMAIL PROTECTED]>: > >> Can you start wpa_supplicant by start command like: >># start wpa_supplicant >> This start command j

[android-porting] Re: how to use the rild on OMAP2430

librild.so is the wrong library. I'm amazed you didn't get an error. You should be using the ril implementation library such as /system/lib/libreference-ril.so. teju wrote: > hi, > > my modem is connected to ttyS2 port, ttyS0 is used as console, > > /system/bin/rild -l /system/lib/librild.so --

[android-porting] Re: about android charging detect and battery level detect

Hi, Android uses the standard power interface, but it expects that uevents are generated when the values change. It does not poll the values, but listens for the uevents instead. zhqzh1982 wrote: > hi all: > >is anyone know the android charging detect and battery level > detect interface

[android-porting] Re: AudioTrack(): obtainBuffer timed out

There is a version of the WindRiver ALSA audio that uses unblocked I/O and will kick-start the audio if this happens. The real problem is that the ALSA driver usually doesn't survive well over a suspend/resume. The way to reproduce the problem is if: 1) Play something. 2) Stop play. 3) Suspend

[android-porting] Re: AudioTrack(): obtainBuffer timed out

naveenkrishna.ch wrote: > > > On Wed, Jan 7, 2009 at 12:18 PM, Sean McNeil <mailto:seanmcne...@gmail.com>> wrote: > > > There is a version of the WindRiver ALSA audio that uses unblocked I/O > and will kick-start the audio if this happens. The real proble

[android-porting] Re: AudioTrack(): obtainBuffer timed out

naveenkrishna.ch wrote: > > > On Wed, Jan 7, 2009 at 12:35 PM, Sean McNeil <mailto:seanmcne...@gmail.com>> wrote: > > > naveenkrishna.ch wrote: > > > > > > On Wed, Jan 7, 2009 at 12:18 PM, Sean McNeil > mailto:seanmcne...@

[android-porting] Re: about android charging detect and battery level detect

going on when it tries to read the initial battery values and starts watching for uevents. Sean Qingzhan Zhang wrote: > hi: > > when the battery value changed i kobject_event(kobject,KOBJ_CHANGE) > and when the charge plug in or plug out ,i also > kobject_event(kobject,KOBJ_CHAN

[android-porting] Re: Problem in alsa code

Google has made some minor changes to the audio interface and Wind River is aware of them. There is a patch pending and it will hopefully be committed soon. Sorry for the inconvenience, Sean Praveen wrote: > Hi Vandy, > > I am also getting the same error while compiling. Were yo

[android-porting] Re: Problem in alsa code

Attached is an unofficial patch that should help. We still need to go through our review process, so things will take time. Vandana Vuthoo wrote: > Hi Sean, > > When will the patch be available ? I am in a total fix,please help,Can > I get some workaround it for it? > > Rgds

[android-porting] Re: Problem in alsa code

open. Finally, they made the AudioHardwareInterface class a pure template class and made AudioHardwareBase what used to be AudioHardwareInterface. All these changes appear to be helpful and desirable. Sean Praveen wrote: > Hi sean, > > Do you know about changes to the audio interfac

[android-porting] Re: Problem in alsa code

You are probably missing external/alsa-lib. You have to have both. Vandana Vuthoo wrote: > Hi Sean/Rupesh, > I applied the same patch but got the foll errorrs > ow when I build I am getting the following error > target arm C++: libaudio <= hardware/alsa_sound/ > AudioHardw

[android-porting] Re: Sensors

What you are trying to do cannot be done. Accelerometers give you a vector to GC whereas the G1 has a compass which gives you yaw/pitch/roll to north. 伊泽 wrote: > hi pramod gurav, > > I think we have the same problem,the lis302/lis331 sensor cannot provide > yaw/pitch/roll data while we feel hard

[android-porting] Re: Backlight adjustment on Eee PC and other platforms

t; BrightnessPreference.java". While it should be from 0 - 7 for Eee PC. > > For 1), we can use a property to set the value for the LCD_BACKLIGHT, > instead of hard code it. > For 2), we can check sysfs file "max_brightness" to get the

[android-porting] Re: Problem in alsa code

Yes, I noticed this as well. Seems like the patch I sent you was a little messed up. Just copy over the files from ./frameworks/base/libs/audioflinger/AudioHardwareStub.* and you should be OK. Sean Marco Trevisan (Treviño) wrote: > On 8 Gen, 06:33, Sean McNeil wrote: > >> At

[android-porting] hardware_legacy and generic interfaces

It looks like pretty much everything is currently thrown over into libhardware_legacy that used to be in libhardware. This includes things like the power management locking interface. Is this just an interim thing? I should think something like acquiring a suspend lock wouldn't be a legacy int

[android-porting] Re: Size of data type "enum"

Herb wrote: > Hi All: > > I meet a similar issue in ppp handshaking~ > I got correct IP/DNS settings and ppp0 interface is up. > But data didn't go through ppp0 interface (no matter using ping or > launch browser)... > I tried "-fno-short-enums" in ppp make file, but result is the same. > Any sugg

[android-porting] Re: android DNS fail to resolve website IP adddres

eth1 isn't a valid device for tracking. Take a look at frameworks/base/core/java/android/net/MobileDataStateTracker.java. You'll see that it really only looks at rmnet0, eth0, and gprs. For DNS to work, the net.dns# properties need to get set. You'll either have to add eth1 into the MobileData

[android-porting] Re: ADB over TCP IP

Huh? I do this all the time. I setup ethernet over USB and then connect to the phone with: ADBHOST=192.168.0.202 adb kill-server ADBHOST=192.168.0.202 adb command I don't know what you mean that it isn't possible. I guess I'm doing the impossible, then. ;) David Turner wrote: > This is not cu

[android-porting] cupcake minor issues

The soft keypad in cupcake is a great step in supporting keypad-less phones like the Openmoko. I've found the following minor issues that I don't know if Google engineers have seen: 1) At times, the cursor will remain in front of a character that is typed. It happens to me mostly when typing U

[android-porting] network defaultroute

How does Android deal with multiple network sources and the default route? I've seen how to get the appropriate DNS entries through the connection manager, but nothing that appears to work the routing. For instance, if I have GPRS up and then initiate a WiFi connection then the default route s

  1   2   >