Changing the linker in build/core/combo/TARGET_linux-x86.mk
from:
-Wl,-dynamic-linker,/system/bin/linker \
to:
-Wl,-dynamic-linker,/lib/ld-linux.so.2 \
solved the problem.
Kind regards,
Vinaya
On Nov 16, 8:35 pm, Devaraj Rangasamy wrote:
> Not sure why ldd system_server shows
On Dec 29, 12:54 pm, Shashank wrote:
> One of the example is, we run a perl script that install/uninstall
> multiple apks on device using adb. As install process adb daemon
> (adbd) on the device forks another child process to handle this new
> install request. In the failure case I saw that th
1. I'm not aware of any.
2. A few things to try:
- can you repeat the bug with same software running on another
(released) device with different chipset?
This would help show whether the bug is likely portable or specific
to this device/chipset.
- try a different kernel version
- try disabli
We've run into an issue where a CTS test case is failing because seeks
do not happen immediately. I think the test case should be updated,
but how do I go about that?
Details...
This is the test case:
run cts -c android.media.cts.MediaPlayerTest -m
testVideoSurfaceResetting
After playing
try http://www.android-x86.org/
On Dec 27, 9:48 pm, Daniel Strand wrote:
> Ok fellas, this is what i have going on here, im a long time linux
> user about two years ago i got into android hacking and fell in love
> with android. i have too many questions to put into a single post.
> Basically wh
Maybe I misunderstood your question... but couldnt you use one of the
pre-existing android x86 distros?
http://www.android-x86.org/
There has been a ton of progress and development into that project,
and if nothing else you could use the source for that as a base,
swapping out kernel video drivers
I think this file is no longer used in Android 3.0 and later, at least
for the devices I checked.
It may have been used earlier to configure audio for devices where the
Audio HAL called ALSA kernel.
Which devices do you see it being used in, and for which Android
versions?
On Dec 27, 7:20 am, Chai
We are facing some random issues with futex while porting ICS on our
devices.
Issue description:
-
We are seeing random futex deadlock issues on ICS with different
processes on Android.
One of the example is, we run a perl script that install/uninstall
multiple apks on devic
I Thought that this posted this morning but I guess not.
Can you build for the emulator device?
This will ensure that you have a working build environment prior to porting
to another device.
also what is the device your trying to port from gb to ics?
can we please have more information like your
sir you have not really provided any information as to the steps
performed to get to this result.
can you successfully build a emulator image and use it in the
emulator?
this to verify that you have a complete and successful build
environment prior to attempting a port.
I would start their and then
Hi,
I have ported Android ICS 4.0 in to EVM (ARM Cortex A8). But I could
not find the telephony and SMS features.
"By default product characteristics are configured for tablet.
Check /device/ti/beagleboard/device.mk file
(PRODUCT_CHARACTERISTICS variable)
Replace "PRODUCT_CHARACTERISTICS := t
To have a module added to your build from packages/apps you would add
something like this to a mk file that your device(s) would inherit:
PRODUCT_PACKAGES += \
Where 'LOCAL_PACKAGE_NAME' would be something like 'Launcher2'.
As far as what tells the build to include it in system/app, I'm no
Hi,
I have been trying to port Android 4.0.3 to our SoC but encountered a
booting failure with the following log message.
E/BatteryService( 977): Could not open /sys/class/power_supply
E/BatteryService( 977): acOnlinePath not found
E/BatteryService
Hi,
I have been trying to port Android 4.0.3 to our SoC but encountered a
booting failure with the attached log message. As I can see in these error
logs, it looks to have some issues,
1. Cannot open power supply device. As for this issue, I have worked around
it in BatteryService.java to assign fa
Ok fellas, this is what i have going on here, im a long time linux
user about two years ago i got into android hacking and fell in love
with android. i have too many questions to put into a single post.
Basically what i want/need is specifics on compiling/porting x86
android so i can build a workin
do a logcat through adb and post the log via pastebin.
On Dec 26, 10:53 pm, Devindrappa Handraki
wrote:
> Hi Maxime,
>
> Thanks for your suggestion, now i am able to port the 7" LCD to
> devkit8000. now devkit8000 is booting with Android gingerbread, but touch
> screen is not working, please hel
16 matches
Mail list logo
