yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] flyers00:
ADS Magpie 20110224

I used the super wipe multiple times as well as wiping all 5 in AMONRA1.7. I also did a fastboot erase system -w before flashing ADS magpie 201102024 on my G1After booting up the phone and trying to download any application I receive an Insufficent Memory Error Message. I used the GAPPS in the OP
[G1 Android Development] AndDiSa:
can you pls. check free space on /data resp. /sd-ext?

Seems to me, that either your download directory (which is either /data/download or /sd-ext/download, depending on your partition layout) has no space left or you have no access rights on it.
[G1 Android Development] flyers00:
What is the best way to get this information? Be more than happy to get it to you
[G1 Android Development] AndDiSa:
Either in terminal or using adb shell you should enter

df -h
[G1 Android Development] flyers00:
Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

L:\>adb shell

~ # su

su

~ # df -h

df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 55.1M 32.0K 55.1M 0% /dev

tmpfs 55.1M 0 55.1M 0% /mnt/asec

tmpfs 55.1M 0 55.1M 0% /mnt/obb

/dev/block/mtdblock3 90.0M 78.7M 11.3M 87% /system

/dev/block/mtdblock5 117.8M 45.7M 72.0M 39% /data

/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules

/dev/block/loop1 2.5M 2.5M 0 100% /system/fonts

/dev/block/mtdblock5 117.8M 45.7M 72.0M 39% /cache

/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache

/dev/block/vold/179:1

6.9G 318.4M 6.6G 5% /mnt/sdcard

/dev/block/vold/179:1

6.9G 318.4M 6.6G 5% /mnt/secure/asec
[G1 Android Development] AndDiSa:
Hmm, looks good to me ...

Can you post a logcat pls, so I can analyze better, what might be the problem.
[G1 Android Development] crypticc:
Not mounted even on regular kernel or pershoots (with working wireless).

Interestingly comparing my mount | grep with the post above, the loop0 mount is taken by /system/fonts not lib/modules

~ # mount | grep loop
mount | grep loop
/dev/block/loop0 on /system/fonts type squashfs (ro,relatime)

Here's the results of attempted mount.

/dev # for i in /dev/block/loop*
for i in /dev/block/loop*
> do
do
> ln -s $i /dev/`basename $i`
ln -s $i /dev/`basename $i`
> done
done
/dev # busybox mount -t squashfs /system/lib/modules/modules.sqf /system/lib/modules/
busybox mount -t squashfs /system/lib/modules/modules.sqf /system/lib/mod
ules/
mount: mounting /system/lib/modules/modules.sqf on /system/lib/modules/ failed: No such file or dire
ctory
[G1 Android Development] flyers00:
Thanks for taking a look at the information provided. I will run a logcat and attach
[G1 Android Development] farmatito:
New 2.6.37.2 Frankenstein kernel.

USE AT YOUR OWN RISK. NO WARRANTY.

Hope this fixes wifi trouble some people have.

Enjoy.
[G1 Android Development] crypticc:
Thanks farmatito, now trying - will report back.

update:

Nearly there maybe...

~ # mount | grep loop
mount | grep loop
/dev/block/loop0 on /system/lib/modules type squashfs (ro,relatime)
/dev/block/loop1 on /system/fonts type squashfs (ro,relatime)

When I start the wi-fi I get following in logcat.

E/WifiService( 116): Failed to load Wi-Fi driver.

Does there need to be a file in here>

~ # ls /system/lib/modules/modules.sqf
ls /system/lib/modules/modules.sqf
ls: /system/lib/modules/modules.sqf: No such file or directory

~ # busybox mount -t squashfs /system/lib/modules/modules.sqf /system/lib/modules/
busybox mount -t squashfs /system/lib/modules/modules.sqf /system/lib/module
s/
mount: mounting /system/lib/modules/modules.sqf on /system/lib/modules/ failed: No such file or dire
ctory

~ # cd /system/lib/modules
cd /system/lib/modules
/system/lib/modules # ls
ls
2.6.37-cyanogenmod wlan.ko

update 2:

I notice that the modules.sqf is visible if I mount and view /system/lib/modules/ from recovery, so I guess the file is there to be mounted...

i.e. above when booted, below when in recovery:

/system/lib/modules # ls -ltr /system/lib/modules/
ls -ltr
-rw-r--r-- 1 root root 892928 Aug 1 2008 modules.sqf
[G1 Android Development] crypticc:
Hi farmatito

sorry to spam the thread, but not really knowing what they are I've repeated the steps from BibleBelt>

/system/lib/modules # ls -ltr
ls -ltr
drwxr-xr-x 3 system system 350 Feb 7 21:12 2.6.37-cyanogenmod
-rw-r--r-- 1 system system 640680 Feb 7 21:12 wlan.ko

/system/lib/modules # lsmod
lsmod
ipv6 235960 8 - Live 0xbf000000

/system/lib/modules # insmod wlan.ko
insmod wlan.ko
insmod: init_module 'wlan.ko' failed (No such device)

Thanks again
[G1 Android Development] roalex:
squash support build in kernel ?
[G1 Android Development] farmatito:
CONFIG_SQUASHFS=y
# CONFIG_SQUASHFS_XATTR is not set
# CONFIG_SQUASHFS_LZO is not set
CONFIG_SQUASHFS_EMBEDDED=y
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3

BTW. It does work reliably for me:

insmod /system/lib/modules/wlan.ko

<6>[ 9911.143768] TIWLAN: Driver loading
<4>[ 9911.144409] wifi_probe
<4>[ 9911.144683] trout_wifi_power: 1
<4>[ 9911.344024] trout_wifi_reset: 0
<4>[ 9911.392761] trout_wifi_set_carddetect: 1
<7>[ 9911.393066] mmc0: card_present 1
<6>[ 9911.393341] mmc0: Slot status change detected (0 -> 1)
<4>[ 9913.948150] mmc0: card claims to support voltages below the defined range. These will be ignored.
<6>[ 9913.949951] mmc0: new SDIO card at address 0001
<6>[ 9913.956604] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 9913.963623] TIWLAN: Driver initialized (rc 0)
<4>[ 9913.973144] TIWLAN: 1251 PG 1.2
<6>[ 9913.973602] TIWLAN: Driver loaded

So to be honest I really have no idea what's going on there...
[G1 Android Development] farmatito:
New 2.6.37.2. Frankenstein kernel.

USE AT YOUR OWN RISK. NO WARRANTY.

Missing leds fixed.

The wifi not working on some magics is still a mistery for me...

Enjoy.
[G1 Android Development] Chris41336:
Slight problem: I installed the latest ADS build, but can not install any apps. It keeps saying there is insufficient storage, regardless of the install location, and I have plenty of room on either anyway.

I really only care about setCPU, which is small anyway. Is there any way to fix this?
[G1 Android Development] AndDiSa:
There are *three* possible install locations for your apps:

- internal memory, i.e. /data/app

- sd-ext, i.e. /sd-ext/app

- sdcard

Most likely your /sd-ext partition is not mounted (probably it's ext4, which is actually *not* supported), but the phone tries to download/install to that location ... Check wether your /sd-ext is mounted correctly. If you still can't get it managed, send a logcat, please.
[G1 Android Development] roalex:
You should set up a repo on github so we can take a look too ;) who knows maybe some of the devs can help out with this or that
[G1 Android Development] farmatito:
I doubt that it would be worth the effort as this whole gingerbread stuff will be old and forgotten in a few days

when all will rush to install honeycomb.Would be just one more git repo polluting the web.

I can send the sources if there is some interest
[G1 Android Development] ezterry:
Honeycomb is not an upgrade its a parallel branch to gingerbread..

The core changes are in gingerbread.. the extensions for tablets is in honeycomb as well as some high end 3d interfaces.

As we are not a tablet and we don't have the high end 3d interfaces.. their is no real change in honeycomb to be had. (as opposed to 2.3.3 that I need to complete merging)

Anyway you still need a kernel regardless of the version of android.
[G1 Android Development] crypticc:
I think it is all 32b magics (from that forum). What radio and spl do you have? I am 0013d and 2708.

I tried pulling wlan.ko from pershoots and starting that with insmod but no joy. Different error apart from no device. Someone mentions a strace. How to do that?

Not nagging just keen to help.
[G1 Android Development] farmatito:
Try

strace -o /sdcard/out.txt insmod /system/lib/modules/wlan.ko

and then post out.txt, also

dmesg

ls -la /system/lib/modules/

md5sum /system/lib/modules/wlan.ko

df -h

could help.
[G1 Android Development] farmatito:
After last repo sync I did build is broken.

I've tried make clobber and deleted most of the dirs

and resynced them again, but errors still are there.

Can the repo gurus take a look at it?

target thumb C: liba2dp <= external/bluetooth/bluez/audio/liba2dp.c
In file included from hardware/msm7k/libaudio/AudioHardware.h:26,
from hardware/msm7k/libaudio/AudioHardware.cpp:34:
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareBase.h: In member function 'virtual bool android::AudioHardwareBase::isModeInCall(int)':
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareBase.h:56: error: 'MODE_IN_COMMUNICATION' is not a member of 'android::AudioSystem'
make: *** [out/target/product/sapphire/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardware.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from frameworks/base/services/audioflinger/A2dpAudioInterface.h:25,
from frameworks/base/services/audioflinger/AudioFlinger.cpp:47:
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareBase.h: In member function 'virtual bool android::AudioHardwareBase::isModeInCall(int)':
hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareBase.h:56: error: 'MODE_IN_COMMUNICATION' is not a member of 'android::AudioSystem'
external/bluetooth/bluez/audio/liba2dp.c: In function 'a2dp_write':
external/bluetooth/bluez/audio/liba2dp.c:1204: warning: passing argument 6 of 'sbc_encode' from incompatible pointer type
external/bluetooth/bluez/audio/../sbc/sbc.h:94: note: expected 'ssize_t *' but argument is of type 'unsigned int *'
make: *** [out/target/product/sapphire/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/AudioFlinger.o] Error 1
[G1 Android Development] s14evil:
Is there a better kernal that give better battery like? At less 8 hours of using time. It seems that my phone is alway on the charger. Even when I'm not using the the phone. I check battery usage and cell standby is using a lot. I am curently using ADS MAGPIE .0220.
[G1 Android Development] crypticc:
Cell standby is good. Means nothing else is using it.

There's whole threads on battery usage, suggest you swot up on battery recalibration, try it out and then repost there what you find. Also visually inspect for a swollen or shrunken battery about to give up the ghost
[G1 Android Development] AndDiSa:
Noticed it yesterday, too. Seems to me that there was some modifications which require api-level 10 (honeycomp). I don't know if this was a mistake ...
[G1 Android Development] id242:
API Level 10 is 2.3.3... Gingerbread

API Level 11 is 3.0... Honeycomb

See here: http://developer.android.com/sdk/android-2.3.3.html

A full list of API Levels can be found here http://developer.android.com/guide/appendix/api-levels.html#intro
[G1 Android Development] AndDiSa:
You are right ... I mixed that up, but nevertheless MODE_IN_COMMUNICATION was introduced with honeycomp and is not available on gingerbread.
[G1 Android Development] jdb78:
I don't think this was a mistake since API 10 ist Gingerbread 2.3.3. And eZTerry wanted to merge this:

EDIT: id242 was faster :]
[G1 Android Development] ezterry:
Over the weekend the "gingerbread" head was still 2.3.2 ish...

"gingerbread-release" has been pointing to 2.3.3 since shortly after the OTA announcement for 2.3.3 on the Nexus 1/S

Seems that pulled gingerbread up to the release level.. and we find one of my problems with android's repo.. there is no good way to lock it at a build..

..

Here is a list of all the commits pre-2.3.3 that gingerbread was pointing at:

http://android.pastebin.com/CcwNMXcc

(all lines are <project> <korg-commit>)

if a line is missing a commit its one of our github cloned projects.

for each of the project commit pairs you want to:

(cd <project>;git reset <commit>;git clean -f;git checkout -f)

That will return you to the 2.3.2 level until the project has a 2.3.3 build.. I was also busy with some other things but the merge won't take long. (but may need a weekend)
[G1 Android Development] AndDiSa:
There is something I do not understand: If "gingerbread-release" is pointing to 2.3.3 level, why we get the problem with the MODE_IN_COMMUNICATION of android::AudioSystem? If I read the api documentation correctly, this element was introduced with honeycomp (API level 11), so "gingerbread-release" is on 3.0, isn't it?
[G1 Android Development] ezterry:
My guess is it was added or back ported to 2.3.3 as a clean way to implement some internal functionality. However was not added in time to make the official API thus is not to be used and may not 100% work with external 3rd party apks.

Your build problem however is /build /framework and parts of /system are level 9 (2.3.2) not level 10
[G1 Android Development] muldy:
Hi!

Just caught on of those random reboots.

I got the logcat:

On wallpaper change: ( about 20h uptime )

Seems like a soft reboot, it dind't display the htc logo

running: GINGERBREAD-DS-Alpha-20110208-1.zip (no addons)

I'm using swap on sdcard

After reboot I changed to the same image with no problems.

Seems that it ran out of memory, a couple of minutes before launcher app was very unresponsive.

Just posting for information
[G1 Android Development] crypticc:
Hi - I hope this helps...

Chris

~ # strace -o /sdcard/insmodout.txt insmod /system/lib/modules/wlan.ko
strace -o /sdcard/insmodout.txt insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (No such device)

and then post out.txt, also

dmesg

/mnt/sdcard # ls -la /system/lib/modules/
ls -la /system/lib/modules/
drwxr-xr-x 3 system system 58 Mar 1 00:45 .
drwxr-xr-x 1 root root 2048 Feb 9 21:33 ..
drwxr-xr-x 3 system system 323 Mar 1 00:45 2.6.37.2-cyanogenmod
-rw-r--r-- 1 system system 690993 Mar 1 00:45 wlan.ko

/mnt/sdcard # md5sum /system/lib/modules/wlan.ko
md5sum /system/lib/modules/wlan.ko
ee86a7f057cc93f1d15d7ce509969c6e /system/lib/modules/wlan.ko

~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 44.0K 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
tmpfs 55.0M 0 55.0M 0% /mnt/obb
/dev/block/mtdblock3 90.0M 83.1M 6.9M 92% /system
/dev/block/mtdblock5 295.8M 252.0M 43.7M 85% /data
/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache
/dev/block/loop0 1.0M 1.0M 0 100% /system/lib/modules
/dev/block/loop1 2.5M 2.5M 0 100% /system/fonts

could help
[G1 Android Development] stevendeb25:
i am getting phone sleeping and not waking up until removable of battery, 4 times in 8hrs its happened. swapped back to previous kernel
[G1 Android Development] farmatito:
Hi,

hope to have time to take a look at it tomorrow after

i have fixed my ezG source tree.
[G1 Android Development] farmatito:
To bad. Hope next version will do better.
[G1 Android Development] farmatito:
To fix source tree:

repo forall -c "git checkout android-2.3.2_r1"
repo sync ezterry/GB-build
repo sync ezterry/GB-platform_dalvik
repo sync ezterry/GB-device_htc_dream-sapphire
repo sync ezterry/GB-device_htc_sapphire
repo sync ezterry/GB-external_clearsilver
repo sync ezterry/GB-android_external_skia
repo sync ezterry/GB-external_webkit
repo sync ezterry/GB-framework_base
repo sync ezterry/GB-hardware_qcom_gpsshim
repo sync ezterry/GB-hardware_qcom_media
repo sync ezterry/GB-packages_inputmethods_LatinIME
repo sync ezterry/GB-system_core
repo sync ezterry/GB-system_extras

Then:

make clobber

Now it builds again...

USE AT YOUR OWN RISK.:D
[G1 Android Development] crypticc:
Whatever works best mate :)
[G1 Android Development] ezterry:
At best that is the same as the commits I posted yesterday.. but in some cases its older than those commits..

As the ones I posted yesterday was the gingerbread branch before the 2.3.3 merge

..

Anyway if you are going to do that just change the default revision in .repo/manifest.xml on your local copy to 'android-2.3.2_r1' and run repo sync
[G1 Android Development] farmatito:
I needed this alternative solution because after rolling

back the commits as you suggested build was still broken

for me. Will resync to the latest and greatest when you are

ready for 2.3.3. Meanwhile I'm able to play with my toys again.... :D
[G1 Android Development] farmatito:
New 2.6.37.2 Frankenstein kernel.

Minor changes.

Still investigating Magic wifi issue.... (possible culprit msm_sdcc)

USE AT YOUR OWN RISK. NO WARRANTY.

Enjoy.
[G1 Android Development] AndDiSa:
Only compiling the Nfc-app gave errors, (at least for me, until now). That app you can delete without any restrictions ... ;)
[G1 Android Development] roccoadam32:
i need something new to flash to meet my modding adiction lol
[G1 Android Development] s14evil:
So it looks like gingerbread is almost a daily rom for me. Except for some bugs like unable to send MM MESSAGE and Not so good battery life.(and yes I have a new battery).... no Fc. I am using ADS .0220
[G1 Android Development] muldy:
Are your APn settings correct?

I have to add them after flashing the rom...
[G1 Android Development] ZilverZurfarn:
Almost? I've been running ADS_Magpie for a month now, and to me, it's faster, more stable and less power hungry than last CM for G1
[G1 Android Development] ezterry:
GINGERBREAD-DS-CheckPoint-20110304.zip

Hi all,

I'm going to start checkpoint releases: These are points of interest such as a major change in the code base (such as the 2.3.3 upgrade we will have prob. by the end of the weekend) And future Release candidates/Releases

The difference here is rather than just making a build off the HEAD of the default manifest; I'll be making a special manifest locked to the actual individual git commits in all the git repos. (really the output of 'repo manifest -o <checkpoint.xml> -r')

This means you can always rebuild with the exact same source the checkpoint builds.

---

CheckPoint-20110304 -- this is the last 2.3.2 build; and uses a prebuilt kernel exp20110109 in anykernel format.

This contains no significant changes from the 20110208-1 build however may contain some upstream google updates. Related GApps package: gapps-mdpi-gb-20110205_S.zip

To get the source tree:

in a new checkpoint 20110304 directory

repo init -u git://github.com/ezterry/manifest-gingerbread-DS.git -b gingerbread -m checkpoints/manifest-20110304.xml

Then continue with repo sync as usual; Remember its wise to use the proprietary files from the same checkpoint that you are building.

Details on building ezGingerbread are in the Op post of this thread.
[G1 Android Development] conorkickass:
Battery Drain

To those experiencing battery drain issues, this has come up previously in the thread, but try restarting your phone everytime you unplug it. It is inconvenient but this seems to prolong battery life significantly. I also find that if I keep GPS disabled on the power control widget (restart after toggling) I have improved battery life.

Finally, I have not been able to get a GPS lock on any of the ADS builds. Does anyone else experience this? (GPS worked fine on Cyan6.1 and (as far as I can remember) on the ezTerry ezGB build.)
[G1 Android Development] psilofx:
ezterry,

would it be possible to ad Czech language to the next build?

Thanks!
[G1 Android Development] ezterry:
The launguages included match that of the gapps package recommended. I have no intention of supporting more as this seems on the edge of not using too much storage/ram while still covering nearly all users world wide.

That said you or others are welcome to make a build with czech, maybe even removing some other languages to keep the resulting rom from growing and posting it to an czech android forum.

To do this after syncing the repo edit device/htc/full_sapphire.mk and comment out line 28, and change line 31 to:

PRODUCT_LOCALES += cs_CZ

You may also wish to add to the file

PRODUCT_DEFAULT_LANGUAGE := cs

PRODUCT_DEFAULT_REGION := CZ
[G1 Android Development] AndDiSa:
It's not really a news, since almost all 2.6.35.x kernels have this bug.

I cannot confirm you bug-report: GPS is working fine here, probably you have to wait a bit longer, until sufficient satellite data are available. You could try to check the GPS-status with an apropriate application.

Edit: just to mention: a new ADS magpie build is available ;)
[G1 Android Development] BibleBelt:
Today I installed ezterry's biffmod 2.6.34.8 kernel and this one. I ran strace insmod wlan.ko with both kernels and compared the output. Unfortunately I don't see anything there, both traces are very similar (only pids and stuff like this are different) until the error is reported that the device was not found.

I also run dmesg shortly after the device booted up. Here the output is very similar as well. I attach it anyhow, maybe it helps you a little step further.
[G1 Android Development] BibleBelt:
Giving the term "flash mob" a whole new meaning.

SCNR
[G1 Android Development] psilofx:
Sure, I understand your arguments, that's reasonable.

Thanks for the advices, I'll try that :)
[G1 Android Development] foronour:
this rom have arabic lang or not
[G1 Android Development] R3N0V4D0:
why dont u flash and find out..

thx ezterry for all your hard work :)
[G1 Android Development] tnpapadakos:
+1

thats what i would do
[G1 Android Development] radioactiveman:
I just tried to update my version 20110130 to 20110305.

this is my output

- waiting for device -
--------- beginning of /dev/log/main
I/PP ( 73):
I/PP ( 73): _/ _/
I/PP ( 73): _/_/_/ _/ _/_/ _/ _/_/ _/_/ _/ _/ _/_/_/
I/PP ( 73): _/ _/ _/ _/ _/ _/_/ _/ _/ _/ _/ _/ _/_/
I/PP ( 73): _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/
I/PP ( 73): _/_/_/ _/ _/_/ _/ _/ _/_/ _/_/_/ _/_/_/
I/PP ( 73): _/
I/PP ( 73): _/_/
I/PP ( 73):
I/PP ( 73): _/_/_/ _/ _/ _/_/
I/PP ( 73): _/ _/_/_/ _/_/_/ _/_/_/ _/_/_/ _/ _/
I/PP ( 73): _/ _/_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/
I/PP ( 73): _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
I/PP ( 73): _/_/_/ _/_/_/ _/ _/ _/_/_/ _/_/_/ _/ _/
I/PP ( 73):
I/PP ( 73):
I/PP ( 73):
I/mountsd ( 81): /dev/block/mmcblk0p2 = linux partition
I/mountsd ( 82): Checking filesystems..
I//system/xbin/run-parts( 70): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 70): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/run-parts( 70): /dev/block/mmcblk0p2: clean, 232/500856 files, 226003/1000000 blocks
I/logwrapper( 87): busybox terminated by exit(0)
I/logwrapper( 91): busybox terminated by exit(0)
I/logwrapper( 93): busybox terminated by exit(0)
I/mountsd ( 95): /sd-ext successfully mounted
I//system/xbin/run-parts( 70): system dex to be kept on /data
I/a2sd ( 152): Apps2SD successfully activated
I/busybox ( 154): rm: can't remove '/data/dalvik-cache/*': No such file or directory
I/logwrapper( 154): busybox terminated by exit(0)
I/logwrapper( 70): /system/xbin/run-parts terminated by exit(0)
I/DEBUG ( 180): debuggerd: Mar 3 2011 21:03:12
D/AKMD ( 187): akmd 1.6.6 START
D/AKMD ( 187): library version: 1.2.1.1129
--------- beginning of /dev/log/system
I/Vold ( 178): Vold 2.1 (the revenge) firing up
I/Netd ( 179): Netd 1.0 starting
D/Vold ( 178): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 178): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 178): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Netd ( 201): Netd 1.0 starting
W/Vold ( 178): Ignoring unknown switch 'usb_mass_storage'
I/Netd ( 223): Netd 1.0 starting
I/Netd ( 230): Netd 1.0 starting
I/Netd ( 237): Netd 1.0 starting
I/Netd ( 244): Netd 1.0 starting
I/Netd ( 251): Netd 1.0 starting
I/Netd ( 258): Netd 1.0 starting
I/Netd ( 265): Netd 1.0 starting
I/Netd ( 272): Netd 1.0 starting
I/Netd ( 279): Netd 1.0 starting
I/Netd ( 286): Netd 1.0 starting
I/Netd ( 293): Netd 1.0 starting
I/Netd ( 300): Netd 1.0 starting
I/Netd ( 306): Netd 1.0 starting
I/Netd ( 313): Netd 1.0 starting
I/Netd ( 320): Netd 1.0 starting
I/Netd ( 327): Netd 1.0 starting
I/Netd ( 334): Netd 1.0 starting
I/Netd ( 341): Netd 1.0 starting
I/Netd ( 348): Netd 1.0 starting

netd starting would go on forever.

do you know whats wrong?
[G1 Android Development] AndDiSa:
No, never happened to me, probably a bad flash. Try to look at available space on /system. If there is enough space, you can also try to rm /data/dalvik-cache/* and rm /sd-ext/dalvik-cache/* before rebooting. Eventually a mix-up with old *.dex files.