android is not booting with yaffs2 filesystem

by jack » Wed, 11 Nov 2009 03:12:42 GMT


Sponsored Links
 I am trying to port android on custom board ARM CORTEX-A8 based with
128MB of onenand device.
I can see "android" text coming up on the LCD screen but after that
nothing is coming. I am using YAFFS2 filesystem. Below is log last few
lines:

***************** log start ***********************

Freeing init memory: 152K
init: cannot open '/initlogo.rle'
yaffs: dev is 32505860 name is "mtdblock4"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.4, "mtdblock4"
block 363 is bad
yaffs: dev is 32505862 name is "mtdblock6"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.6, "mtdblock6"
yaffs_read_super: isCheckpointed 0
yaffs: dev is 32505861 name is "mtdblock5"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.5, "mtdblock5"
yaffs_read_super: isCheckpointed 0
android_usb gadget: high speed config #1: UMS Only (Not debugging
mode)
init: cannot find '/system/bin/sh', disabling 'console'
init: cannot find '/system/bin/servicemanager', disabling
'servicemanager'
init: cannot find '/system/bin/vold', disabling 'vold'
init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
init: cannot find '/system/bin/app_process', disabling 'zygote'
init: cannot find '/system/bin/mediaserver', disabling 'media'
init: cannot find '/system/bin/playmp3', disabling 'bootsound'
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/bin/installd', disabling 'installd'
init: cannot find '/system/bin/flash_image', disabling
'flash_recovery'
init: cannot find '/system/bin/keystore', disabling 'keystore'
enabling adb
android_usb gadget: high speed config #1: UMS + ADB (Debugging mode)
************************* End of log ******************************
please advise what could be the reason for this.
any help will be appreciated.

Regards,
Jack.

-- 



android is not booting with yaffs2 filesystem

by Alim Akhtar » Wed, 11 Nov 2009 11:09:50 GMT


 Ok I got it. My onenand device is if 2Kb page side and in the mkyaffs2 utils
4KB page support was enabled.
Now the board boots till prompt but still i cann't see the Android coming up
on the LCD and text is there.
Any idea whats still wrong with it?

Regards,
Jack.




> website: 


Sponsored Links


android is not booting with yaffs2 filesystem

by jack » Wed, 11 Nov 2009 20:21:21 GMT


 i all,
more info in the below problem...
here i am sending the logcat massages..its seems these massages are
getting repeated..
Any help will be appreciated..

************ logcat massage start ****************

I/DEBUG ( 1701): debuggerd: Nov 3 2009 18:39:21
I/vold ( 1700): Android Volume Daemon version 2.0
D/vold ( 1700): Bootstrapping complete
E/flash_image( 1709): error opening /system/recovery.img: No such file
or directory
D/DHCP ( 1724): failed to set ip addr for eth0 to 0.0.0.0: No such
device
D/AndroidRuntime( 1703):
D/AndroidRuntime( 1703): >>>>>>>>>>>>>> AndroidRuntime START
<<<<<<<<<<<<<<
D/AndroidRuntime( 1703): CheckJNI is ON
D/dalvikvm( 1703): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1703): Stale deps in cache file; removing and retrying
I/ ( 1704): ServiceManager: 0xad18
D/AudioHardwareALSA( 1704): Mixer: element name: 'DAC1'
D/AudioHardwareALSA( 1704): Mixer: element name: 'DAC2'
D/AudioHardwareALSA( 1704): Mixer: element name: 'DAC3'
D/AudioHardwareALSA( 1704): Mixer: master 'PCM' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Earpiece' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Speaker' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Bluetooth' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Headphone' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Bluetooth A2DP' not found.
D/AudioHardwareALSA( 1704): Mixer: master 'Capture' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Capture' not found.
D/AudioHardwareALSA( 1704): Mixer: route '' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Bluetooth Capture' not
found.
D/AudioHardwareALSA( 1704): Mixer: route 'Capture' not found.
D/AudioHardwareALSA( 1704): Mixer: route 'Bluetooth A2DP Capture' not
found.
D/AudioHardwareALSA( 1704): mixer initialized.
D/AudioHardwareInterface( 1704): setMode(NORMAL)
I/CameraService( 1704): CameraService started: pid=1704
V/AudioHardwareALSA( 1704): virtual android::AudioStreamOut*
android::AudioHardwareALSA::openOutputStream(uint32_t, int*,
uint32_t*, uint32_t*, android::status_t*) - format = 0, channels = 0,
sampleRate = 0
V/AudioHardwareALSA( 1704): ALSAStreamOps - input - format = 0,
channels = 0, rate = 0
V/AudioHardwareALSA( 1704): ALSAStreamOps - default - format = 2,
channels = 2, rate = 44100
E/ALSALib ( 1704): external/alsa-lib/src/control/setup.c:555:
(add_elem) Cannot obtain info for CTL elem (MIXER,'Playback Path',
0,0,0): No such file or directory
E/ALSALib ( 1704): external/alsa-lib/src/control/setup.c:555:
(add_elem) Cannot obtain info for CTL elem (MIXER,'Playback Path',
0,0,0): No such file or directory
I/AudioHardwareALSA( 1704): Initialized ALSA PLAYBACK device
AndroidPlayback
D/AudioHardwareALSA( 1704): Set PLAYBACK PCM format to S16_LE (Signed
16 bit Little Endian)
I/AudioHardwareALSA( 1704):
I/AudioHardwareALSA( 1704): android::status_t
android::ALSAStreamOps::channelCount(int)::671
D/AudioHardwareALSA( 1704): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 1704): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 1704): Buffer size: 4096
D/AudioHardwareALSA( 1704): Latency: 92879
I/AudioFlinger( 1704): openOutput() created mixer output: ID 1 thread
0x26178
I/AudioFlinger( 1704): AudioFlinger's thread 0x26178 ready to run
W/dalvikvm( 1703): partial write in inflate (20440 v



android is not booting with yaffs2 filesystem

by mvniekerk » Wed, 11 Nov 2009 22:49:42 GMT


 ave you've checked for read only partitions?

What Android does upon initial bootup it will extract the apk files
into the /data/ folder. If it doesn't have write access it will fail.
Also, if there is no space on the device to extract these it also
won't work.

On Nov 11, 1:21pm, jack <alim.akh...@gmail.com> wrote:

--



android is not booting with yaffs2 filesystem

by jack » Wed, 11 Nov 2009 23:10:36 GMT


  have given full permissions to /data
chmod 0777 /data
even after booting, i deleted the contains of data folder and rebooted
the system, its still the same.
One thing, some time i can see only 24kb space is left on data
partition and some time its show 2345kb free space, after i run df
command.
any other clue?

Regards,
Jack

On Nov 11, 7:49pm, mvniekerk <mvniek...@gmail.com> wrote:

--



android is not booting with yaffs2 filesystem

by jack » Thu, 12 Nov 2009 12:59:54 GMT


 ello again,
i changed my data partition from 11MB to 31MB. Now the logcat massages
has changed as below, please give some pointer if any one have face
similar problem:

************* logcat start *******************
D/AndroidRuntime( 1766): CheckJNI is ON
D/dalvikvm( 1766): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 1766): Stale deps in cache file; removing and retrying
D/dalvikvm( 1766): DexOpt: --- BEGIN 'framework.jar' (bootstrap=1) ---
I/DEBUG ( 1701): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG ( 1701): pid: 1767, tid: 1767 >>> /system/bin/dexopt <<<
I/DEBUG ( 1701): signal 11 (SIGSEGV), fault addr 456d1abc
I/DEBUG ( 1701): r0 4223a008 r1 000162b0 r2 04000a24 r3 00000001
I/DEBUG ( 1701): r4 400aa4c8 r5 41a290f2 r6 416d1098 r7 4174584c
I/DEBUG ( 1701): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 1701): ip becc5580 sp becc5620 lr afe0eca8 pc
ad057486 cpsr 00000030
I/DEBUG ( 1701): #00 pc 00057486 /system/lib/libdvm.so
I/DEBUG ( 1701): #01 pc 00057afe /system/lib/libdvm.so
I/DEBUG ( 1701): #02 pc 0005828a /system/lib/libdvm.so
I/DEBUG ( 1701): #03 pc 0005849a /system/lib/libdvm.so
I/DEBUG ( 1701): #04 pc 00057d84 /system/lib/libdvm.so
I/DEBUG ( 1701): #05 pc 00059602 /system/lib/libdvm.so
I/DEBUG ( 1701): #06 pc 00058530 /system/lib/libdvm.so
I/DEBUG ( 1701): #07 pc 000582e2 /system/lib/libdvm.so
I/DEBUG ( 1701): #08 pc 0005849a /system/lib/libdvm.so
I/DEBUG ( 1701): #09 pc 00057d84 /system/lib/libdvm.so
I/DEBUG ( 1701): #10 pc 00059602 /system/lib/libdvm.so
I/DEBUG ( 1701): #11 pc 00058530 /system/lib/libdvm.so
I/DEBUG ( 1701): #12 pc 000582e2 /system/lib/libdvm.so
I/DEBUG ( 1701): #13 pc 0005849a /system/lib/libdvm.so
I/DEBUG ( 1701): #14 pc 00057d84 /system/lib/libdvm.so
I/DEBUG ( 1701): #15 pc 000492f4 /system/lib/libdvm.so
I/DEBUG ( 1701): #16 pc 00045a88 /system/lib/libdvm.so
I/DEBUG ( 1701): #17 pc 0004683e /system/lib/libdvm.so
I/DEBUG ( 1701): #18 pc 00048ffc /system/lib/libdvm.so
I/DEBUG ( 1701): #19 pc 0004923a /system/lib/libdvm.so
I/DEBUG ( 1701): #20 pc 0004b678 /system/lib/libdvm.so
I/DEBUG ( 1701): #21 pc 0004b6fa /system/lib/libdvm.so
I/DEBUG ( 1701): #22 pc 0004b7a0 /system/lib/libdvm.so
I/DEBUG ( 1701): #23 pc 0004a74c /system/lib/libdvm.so
I/DEBUG ( 1701): #24 pc 0004a8fe /system/lib/libdvm.so
I/DEBUG ( 1701): #25 pc 00008e1c /system/bin/dexopt
I/DEBUG ( 1701): #26 pc 00008ed2 /system/bin/dexopt
I/DEBUG ( 1701): #27 pc 0000bf66 /system/lib/libc.so
I/DEBUG ( 1701): #28 pc b00016d0 /system/bin/linker
I/DEBUG ( 1701): stack:
I/DEBUG ( 1701): becc55e0 400aa4c8 /dev/ashmem/mspace/dalvik-
heap/0 (deleted)
I/DEBUG ( 1701): becc55e4 ad0428f1 /system/lib/libdvm.so
I/DEBUG ( 1701): becc55e8 00000000
I/DEBUG ( 1701): becc55ec ad080be8 /system/lib/libdvm.so
I/DEBUG ( 1701): becc55f0 00000000
I/DEBUG ( 1701): becc55f4 ad080be8 /system/lib/libdvm.so
I/DEBUG ( 1701): becc55f8 0000034c
I/DEBUG ( 1701): becc55fc 00010008 [heap]
I/DEB



android is not booting with yaffs2 filesystem

by jack » Thu, 12 Nov 2009 14:12:02 GMT


 ello again,
at last i got it working..android home page is coming up..
after increasing the size of data partition to 31MB and deleting the /
data folder contains, i rebooted the system and android booted.

Hope this will help to other people who are facing (might face)
similar problem.

Regards,
Jack

On Nov 12, 9:59am, jack <alim.akh...@gmail.com> wrote:

--



Other Threads

1. SIGSTKFLT from DefaultHttpClient

I run a set of AsyncTasks that are using the DefaultHttpClient to
access a server. From time to time, I'm seeing the following error,
which appears to be due to some sort of lock contention. This only
happens when I'm driving the system hard (>15 AsyncTasks at once). Is
it possible that the client is timing out waiting for a lock? Do I
need to parcel out the work in batches or is there a system setting I
can adjust to have it done for me?

01-20 17:11:26.321: INFO/dalvikvm(12090): "Binder Thread #1" prio=5
tid=6 NATIVE
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="main" sCount=1
dsCount=0 s=Y obj=0x4476a440 self=0x11e5a0
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12095 nice=0
sched=0/0 cgrp=default handle=1178872
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 304260238
317352301 809 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "Compiler" daemon prio=5
tid=5 VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x44765348 self=0x11fb70
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12094 nice=0
sched=0/0 cgrp=default handle=1172656
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 1851837165
854217465 10038 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "JDWP" daemon prio=5 tid=4
VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x447652a0 self=0x124880
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12093 nice=0
sched=0/0 cgrp=default handle=1172384
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 4089356
2716063 18 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "Signal Catcher" daemon
prio=5 tid=3 VMWAIT
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x447651e8 self=0x125b80
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12092 nice=0
sched=0/0 cgrp=default handle=1152504
01-20 17:11:26.321: INFO/dalvikvm(12090):   | schedstat=( 518799
5676269 2 )
01-20 17:11:26.321: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.321: INFO/dalvikvm(12090): "HeapWorker" daemon prio=5
tid=2 MONITOR
01-20 17:11:26.321: INFO/dalvikvm(12090):   | group="system" sCount=1
dsCount=0 s=N obj=0x431a9d80 self=0x126f18
01-20 17:11:26.321: INFO/dalvikvm(12090):   | sysTid=12091 nice=0
sched=0/0 cgrp=default handle=1251760
01-20 17:11:26.329: INFO/dalvikvm(12090):   | schedstat=( 441986082
367523194 238 )
01-20 17:11:26.329: INFO/dalvikvm(12090):   at
org.apache.harmony.xnet.provider.jsse.OpenSSLSessionImpl.finalize(OpenSSLSessionImpl.java:~460)
01-20 17:11:26.329: INFO/dalvikvm(12090):   - waiting to lock
<0x40012550> (a java.lang.Class) held by threadid=46 (AsyncTask #37)
01-20 17:11:26.329: INFO/dalvikvm(12090):   at
dalvik.system.NativeStart.run(Native Method)
01-20 17:11:26.329: DEBUG/dalvikvm(12090): threadid=32: sending two
SIGSTKFLTs to threadid=2 (tid=12091) to cause de{*filter*}d dump
01-20 17:11:28.337: DEBUG/dalvikvm(12090): Sent, pausing to let
de{*filter*}d run
01-20 17:11:28.344: INFO/DEBUG(1003): *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
01-20 17:11:28.344: INFO/DEBUG(1003): Build fingerprint: 'verizon/
voles/sholes/sholes:2.2.1/FRG83D/75603:user/release-keys'
01-20 17:11:28.344: INFO/DEBUG(1003): pid: 12090, tid: 12091  >>>
com.quickdroid <<<
01-20 17:11:28.344: INFO/DEBUG(1003): signal 16 (SIGSTKFLT), fault
addr 00002f3a
01-20 17:11:28.344: INFO/DEBUG(1003):  r0 fffffe00  r1 00000080  r2
00000002  r3 00000000
01-20 17:11:28.344: INFO/DEBUG(1003):  r4 002a1ac0  r5 00000002  r6
00000000  r7 000000f0
01-20 17:11:28.344: INFO/DEBUG(1003):  r8 00000002  r9 00000000  10
00126f18  fp 100ffe30
01-20 17:11:28.344: INFO/DEBUG(1003):  ip 805a24c8  sp 100ffaa0  lr
afd103bc  pc afd0eb68  cpsr 80000010
01-20 17:11:28.344: INFO/DEBUG(1003):  d0  643a64696f72646e  d1
6472656767756265
01-20 17:11:28.344: INFO/DEBUG(1003):  d2  448cf948448cf703  d3
448358184478c701
01-20 17:11:28.344: INFO/DEBUG(1003):  d4  448cf7f0448f73d0  d5
4478c758448cf948
01-20 17:11:28.352: INFO/DEBUG(1003):  d6  448132c0447a4ba0  d7
448b4a30447ba858
01-20 17:11:28.352: INFO/DEBUG(1003):  d8  0000000000000000  d9
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d10 0000000000000000  d11
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d12 0000000000000000  d13
0000000000000000
01-20 17:11:28.352: INFO/DEBUG(1003):  d14 0000000000000000  d15
0000000000000000
01-20 17:11:28.360: INFO/DEBUG(1003):  d16 000000000b0407ba  d17
3fe999999999999a
01-20 17:11:28.360: INFO/DEBUG(1003):  d18 42eccefa43de3400  d19
3fe00000000000b4
01-20 17:11:28.360: INFO/DEBUG(1003):  d20 4008000000000000  d21
3fd99a27ad32ddf5
01-20 17:11:28.360: INFO/DEBUG(1003):  d22 3fd24998d6307188  d23
3fcc7288e957b53b
01-20 17:11:28.360: INFO/DEBUG(1003):  d24 3fc74721cad6b0ed  d25
3fc39a09d078c69f
01-20 17:11:28.368: INFO/DEBUG(1003):  d26 0000000000000000  d27
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  d28 0000000000000000  d29
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  d30 0000000000000000  d31
0000000000000000
01-20 17:11:28.368: INFO/DEBUG(1003):  scr 80000012
01-20 17:11:28.516: INFO/DEBUG(1003):          #00  pc 0000eb68  /
system/lib/libc.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #01  pc 000103b8  /
system/lib/libc.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #02  pc 0004d096  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #03  pc 0004d856  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #04  pc 0001775c  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #05  pc 00022794  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #06  pc 00021634  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #07  pc 0005c5cc  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #08  pc 0005c7fc  /
system/lib/libdvm.so
01-20 17:11:28.516: INFO/DEBUG(1003):          #09  pc 0005203e  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #10  pc 000520ca  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #11  pc 000525a0  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #12  pc 0004f9ec  /
system/lib/libdvm.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #13  pc 00010ed4  /
system/lib/libc.so
01-20 17:11:28.524: INFO/DEBUG(1003):          #14  pc 000109c0  /
system/lib/libc.so
01-20 17:11:28.524: INFO/DEBUG(1003): code around pc:
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb48 0afffff7 e8bd4010
e12fff1e e1010090
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb58 e12fff1e e92d0090
e3a070f0 ef000000
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb68 e8bd0090 e12fff1e
e92d0090 e1a03002
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb78 e1a02001 e3a01000
e3a070f0 ef000000
01-20 17:11:28.524: INFO/DEBUG(1003): afd0eb88 e8bd0090 e12fff1e
e92d0090 e1a02001
01-20 17:11:28.524: INFO/DEBUG(1003): code around lr:
01-20 17:11:28.524: INFO/DEBUG(1003): afd1039c e3500000 0a00000e
e3560000 e3865002
01-20 17:11:28.524: INFO/DEBUG(1003): afd103ac 03a07080 13a07000
ea000000 ebfff9fb
01-20 17:11:28.524: INFO/DEBUG(1003): afd103bc e1a01004 e1a00005
ebfff9e2 e1a01007
01-20 17:11:28.524: INFO/DEBUG(1003): afd103cc e1a02005 e3a03000
e1560000 e1a00004
01-20 17:11:28.524: INFO/DEBUG(1003): afd103dc 1afffff5 e3a00000
e8bd87f0 ebfffc8a
01-20 17:11:28.524: INFO/DEBUG(1003): stack:
01-20 17:11:28.524: INFO/DEBUG(1003):     100ffa60  afd43724  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa64  10420e6c
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa68  00000001
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa6c  afd43760  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa70  100ffad0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa74  4184ff88
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa78  4184ff74
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa7c  afd0be0d  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa80  100ffad0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa84  4184ffa0
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa88  00000018
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa8c  afd43850  /system/
lib/libc.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa90  00126f18  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa94  af0943ac  /system/
lib/libcrypto.so
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa98  df002777
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffa9c  e3a070ad
01-20 17:11:28.532: INFO/DEBUG(1003): #00 100ffaa0  002a1ac0  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffaa4  00000080
01-20 17:11:28.532: INFO/DEBUG(1003): #01 100ffaa8  002a1ab0  [heap]
01-20 17:11:28.532: INFO/DEBUG(1003):     100ffaac  00000000
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab0  00126f18  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab4  002a1ac0  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffab8  80517000  /system/
lib/libdvm.so
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffabc  00000000
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffac0  00126f18  [heap]
01-20 17:11:28.539: INFO/DEBUG(1003):     100ffac4  8054d099  /system/
lib/libdvm.so
01-20 17:11:29.657: INFO/DEBUG(1003): de{*filter*}d committing suicide to
free the zombie!
01-20 17:11:29.680: INFO/BootReceiver(1085): Copying /data/tombstones/
tombstone_00 to DropBox (SYSTEM_TOMBSTONE)

-- 

2. What to use for user feedback?

Hello everyone,

I'm currently providing user support through email, and I'm thinking about using
a more community-aware web solution. I've known GetSatisfaction for a long time,
never used, but always found it quite smart, although it can get a bit pricey if
you need any advanced features such as moderation.

In an Android blog post, Tim Bray does mention Google Groups, Zoho Discussions,
GetSatisfaction and UserVoice:
http://android-developers.blogspot.com/2010/10/improving-app-quality.html

Google Groups doesn't really fit the job IMO, it's not very practical from a
phone, and it's not as user-frienly as the other solutions. But even with
GetSatisfaction, I'm not sure that it's very practical on a phone.

But what do you guys use for user feedback?

Any open source web app optimized for both phone and standard browsers? Anything
with something as intuitive as the Question/Idea/Problem system in 
GetSatisfaction?

I have looked at OpenMind (RoR), but it seems a bit technical, not adequate for
an average user.

I've also considered vBulletin or similar forums, which seem quite popular,
considering the success of android forums website out there. And there is this
nice Tapatalk app, which is compatible with several forums systems, but Tapatalk
is a paid app, and that's a bit of overhead for simple user feedback.

TIA for your ideas

--
  Olivier



-- 
.

3. newbie - contact journey td sync?

4. Solved - Error install aplikSi

5. Build.SERIAL deprecated?

6. ListAdapter design advice

7. Does Any one Building Android source code in Mac