I encountered another problem when init starting its life.
The following is the output of logcat:
I/DEBUG ( 1557): debuggerd: Nov 19 2009 18:56:41
I/vold( 1556): Android Volume Daemon version 2.0
E/vold( 1556): Unable to open '/sys/class/mmc_host' (No such file
or directory)
D/vold
Hi,
I am facing a similar issue with Donut release using kernel 2.6.27.
Even when I run A2DP at 921Kbps, I am getting write blocked for %ms
error. See this log snippet below. I have tried changing the bitpool
down to 35, but that hasn't helped.
Earlier, when I used Cupcake build, I could
Hello Experts,
I´ve found a problem, I don´t know if that is a bug.
I´ve downloaded the mips-cupcake project:
repo init -u git://public.mipsandroid.com/platform/manifest.git -b
mips-cupcake
And I´ve compiled it with the options: TARGET_ARCH=mips and
TARGET_ARCH_VERSION=mips32r2
Some of the
The Android-x86 project is glad to release the new stable version 1.6
to the public. The live cd iso and usb image are available from our
site, as usual:
* http://www.android-x86.org/download
* http://code.google.com/p/android-x86/downloads/list
Test reports (success or fail) are welcome
Hi all,
I have see the same symptom while brining up 2.0 on an ARM926EJS based
(virtual) platform. 1.5 was working fine and my kernel remained
unchanged. In my analysis tools, I see that in my case the boot gets
stuck in a pthread_mutex_lock. After that the CPU is just idle. The
lock is called
On Fri, Nov 20, 2009 at 7:00 AM, AchimNohl achim.n...@coware.com wrote:
Hi all,
I have see the same symptom while brining up 2.0 on an ARM926EJS based
(virtual) platform. 1.5 was working fine and my kernel remained
unchanged. In my analysis tools, I see that in my case the boot gets
stuck
Hi,
I am trying to build donut sdk on fedoro with java 1.5 and I am
getting the following errors.
Install: out/host/linux-x86/bin/atree
host C++: bb2sym = development/emulator/qtools/bb2sym.cpp
host C++: bb2sym = development/emulator/qtools/trace_reader.cpp
On Fri, Nov 20, 2009 at 12:07 PM, Porting beginner
porting.begin...@gmail.com wrote:
On Fri, Nov 20, 2009 at 7:00 AM, AchimNohl achim.n...@coware.com wrote:
Hi all,
I have see the same symptom while brining up 2.0 on an ARM926EJS based
(virtual) platform. 1.5 was working fine and my
Hi,
Is there any detail on what changes/new feature required from kernel and
driver when migrating to eclair from donut ?
Is that mandatory have to some feature/modification in kernel ( i.e fb
driver ) to make eclair works along with kernel which is currently working
for donut. kernel 2.6.27 +
Hi,
Alexey Roslyakov wrote:
Can you share your diff and/or logcat output?
sorry, I will try to send tomorow. I would like to restart and merge the
two patches
Michael
On Nov 20, 12:22 am, Michael Trimarchi trimar...@gandalf.sssup.it
wrote:
Hi,
Alexey Roslyakov wrote:
I added
solution is simple: just remove lockunlock of mutex.
it is locked before (in the same thread), so deadlock occurs.
And probably next problem appears:(
I/gralloc ( 710): refresh rate = 53.04 Hz
I/gralloc ( 710): fb_device_open res: 0
E/gralloc ( 710): couldn't open pmem (Unknown error: -2)
On Fri, Nov 20, 2009 at 2:47 PM, Alexey Roslyakov
alexey.roslya...@gmail.com wrote:
solution is simple: just remove lockunlock of mutex.
it is locked before (in the same thread), so deadlock occurs.
And probably next problem appears:(
I/gralloc ( 710): refresh rate = 53.04 Hz
I/gralloc (
This would not represent an android compatible device (the screen is smaller
than we support, and it sounds like you may remove things that are required
in the sdk), so I'm not sure how much help you can expect to get. You do
have the full source code to play with, and changing the basic size of
No - BUS is arrived:)
It seems PMEM now is required in kernel.
On 21 ноя, 01:54, Porting beginner porting.begin...@gmail.com wrote:
On Fri, Nov 20, 2009 at 2:47 PM, Alexey Roslyakov
alexey.roslya...@gmail.com wrote:
solution is simple: just remove lockunlock of mutex.
it is locked
On Fri, Nov 20, 2009 at 6:19 PM, Alexey Roslyakov
alexey.roslya...@gmail.com wrote:
No - BUS is arrived:)
It seems PMEM now is required in kernel.
PMEM ? but its already enabled , CONFIG_ANDROID_PMEM=y in my kernel.
I talk to one more developer same here on android-porting, he said he
Is /dev/pmem present on target? Just compiled-in module is not enough.
Take a look on gralloc.cpp. If /dev/pmem is not available buffers
couldn't be allocated, gralloc's functions fails.
On 21 ноя, 05:27, Porting beginner porting.begin...@gmail.com wrote:
On Fri, Nov 20, 2009 at 6:19 PM, Alexey
16 matches
Mail list logo
