this is the concluding part, i split it into two becos of the size...


struct_module
[ 6.597045] isp_mod: Unknown symbol iommu_restore_ctx
[ 6.597503] isp_mod: Unknown symbol iommu_vfree
[ 6.598236] isp_mod: Unknown symbol iommu_put
[ 6.598724] isp_mod: Unknown symbol iommu_save_ctx
[ 6.599151] isp_mod: Unknown symbol iommu_vunmap
[ 6.599670] isp_mod: Unknown symbol iommu_vmalloc
[ 6.608856] isp_mod: Unknown symbol iommu_get
[ 6.609497] isp_mod: Unknown symbol iommu_kmap
[ 6.610015] isp_mod: Unknown symbol da_to_va
[ 6.610565] isp_mod: Unknown symbol iommu_vmap
[ 6.610931] isp_mod: Unknown symbol iommu_kunmap
[ 6.611297] isp_mod: Unknown symbol videobuf_to_dma
[ 6.990417] i2c_omap i2c_omap.2: controller timed out
[ 7.047088] lp5523 2-0032: got interrupt from led chip
[ 7.047637] lp5523 2-0032: interrupt from led chip 4f
[ 7.047668] lp5523 2-0032: all engines configured
[ 7.047729] lp5523 2-0032: disabling engines
[ 7.048309] Registered led device: lp5523:kb1
[ 7.048461] Registered led device: lp5523:kb2
[ 7.048583] Registered led device: lp5523:kb3
[ 7.048736] Registered led device: lp5523:kb4
[ 7.048858] Registered led device: lp5523:b
[ 7.048980] Registered led device: lp5523:g
[ 7.049102] Registered led device: lp5523:r
[ 7.049255] Registered led device: lp5523:kb5
[ 7.049377] Registered led device: lp5523:kb6
[ 7.049957] bq27x00-battery 2-0055: support ver. 1.2.0 enabled
[ 7.103363] TSC2005 driver initializing
[ 7.108001] input: TSC2005 touchscreen as /class/input/input3
[ 7.123168] Bluetooth: Core ver 2.15
[ 7.140136] radio-si4713 2-0063: Detected Si4713 (0x0d) Firmware: 3.0 Patch ID: 00:00 Component: 3.0 Chip Rev.: unknown
[ 7.175781] NET: Registered protocol family 31
[ 7.175842] Bluetooth: HCI device and connection manager initialized
[ 7.175872] Bluetooth: HCI socket layer initialized
[ 7.396697] hci_h4p hci_h4p: Registering HCI H4P device
[ 7.428253] cfg80211: Using static regulatory domain info
[ 7.428283] cfg80211: Regulatory domain: US
[ 7.428283] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 7.428314] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 7.428314] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428344] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428344] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428375] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428375] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 7.428405] cfg80211: Regulatory domain changed to country: US
[ 7.428436] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 7.428436] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 7.428466] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428466] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428497] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428497] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 7.428527] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 7.577697] nokia-av nokia-av: accessory detect module initialized
[ 7.758911] omap_wdt omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec, nowayout is on
[ 7.771728] SSI DRIVER Version 1.1-rc2
[ 7.772247] omap_ssi omap_ssi: SSI Hardware REVISION 1.0
[ 7.778900] smc91x: not found (-19).
[ 8.113250] mmci-omap-hs mmci-omap-hs.0: Failed to get debounce clock
[ 8.113403] mmc0: cover is open, card is now inaccessible
[ 8.132934] phy0: Selected rate control algorithm 'minstrel'
[ 8.139831] CMT speech driver v0.2.0
[ 8.225372] mmci-omap-hs mmci-omap-hs.1: Failed to get debounce clock
[ 8.455352] wl1251: loaded
[ 8.456054] wl1251: initialized
[ 8.458435] NET: Registered protocol family 35
[ 8.492736] SSI McSAAB PROTOCOL Version: 2.0-rc1
[ 8.625366] dspbridge_init: 412800 bytes @ 80600000
[ 8.662475] mmc1: new high speed MMC card at address 0001
[ 8.670166] mmcblk0: mmc1:0001 MMC32G 29.8 GiB
[ 8.670440] mmcblk0: p1 p2 p3
[ 8.895935] omap-iommu omap-iommu.1: isp registered
[ 9.091644] isp_mod: disagrees about version of symbol struct_module
[ 9.170013] omap-iommu omap-iommu.1: isp: version 1.1
[ 9.375946] smia-sensor 2-0010: firmware: requesting smia-sensor-01-022b-04.bin
[ 9.397155] smia_reglist_import: meta_reglist version 2009-07-27
[ 9.397247] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/1502 ptr d0d982a0
[ 9.397247] smia_reglist_import: type 10 w 648 h 488 fmt 30314142 ival 100/3003 ptr d0d98228
[ 9.397277] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 100/0 ptr d0d98090
[ 9.397277] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 100/0 ptr d0d98038
[ 9.413757] et8ek8 3-003e: firmware: requesting et8ek8-0002.bin
[ 9.434265] smia_reglist_import: meta_reglist version V4 alma 10.10.10
[ 9.434326] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314142 ival 100/399 ptr d0d9b464
[ 9.434356] smia_reglist_import: type 10 w 2592 h 1968 fmt 30314442 ival 100/1292 ptr d0d9b204
[ 9.434387] smia_reglist_import: type 10 w 1728 h 1312 fmt 30314142 ival 100/11792 ptr d0d9b884
[ 9.434387] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/13000 ptr d0d9b7ec
[ 9.434417] smia_reglist_import: type 10 w 1296 h 984 fmt 30314142 ival 100/501 ptr d0d9b58c
[ 9.434448] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/3000 ptr d0d9b29c
[ 9.434448] smia_reglist_import: type 10 w 1296 h 984 fmt 30314442 ival 100/2500 ptr d0d9b624
[ 9.434478] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/13584 ptr d0d9b754
[ 9.434478] smia_reglist_import: type 10 w 864 h 656 fmt 30314142 ival 100/2988 ptr d0d9b334
[ 9.434509] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/499 ptr d0d9b4f4
[ 9.434539] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/14779 ptr d0d9b6bc
[ 9.434539] smia_reglist_import: type 10 w 648 h 492 fmt 30314142 ival 100/2993 ptr d0d9b3cc
[ 9.434570] smia_reglist_import: type 1 w 2592 h 1968 fmt 30314142 ival 100/1207 ptr d0d9b05c
[ 10.214050] g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
[ 10.214141] g_file_storage gadget: Number of LUNs=2 Number of buffers=16
[ 10.214172] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 10.216156] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file 'devices'
[ 10.216217] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '001'
[ 10.218261] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 10.218444] usb usb1: default language 0x0409
[ 10.218811] usb usb1: uevent
[ 10.220550] usb usb1: usb_probe_device
[ 10.220581] usb usb1: configuration #1 chosen from 1 choice
[ 10.220672] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 10.220825] usb 1-0:1.0: uevent
[ 10.221984] hub 1-0:1.0: usb_probe_interface
[ 10.222015] hub 1-0:1.0: usb_probe_interface - got id
[ 10.222045] hub 1-0:1.0: USB hub found
[ 10.222167] hub 1-0:1.0: 1 port detected
[ 10.222198] hub 1-0:1.0: standalone hub
[ 10.222198] hub 1-0:1.0: individual port power switching
[ 10.222229] hub 1-0:1.0: no over-current protection
[ 10.222229] hub 1-0:1.0: power on to power good time: 10ms
[ 10.222259] hub 1-0:1.0: local power source is good
[ 10.222290] hub 1-0:1.0: enabling power on all ports
[ 10.225341] /home/builder1/maemo-fremantle-armel-extras-devel/work/kernel-power-2.6.28/drivers/usb/core/inode.c: creating file '001'
[ 10.225708] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.225769] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 10.225830] usb usb1: Product: MUSB HDRC host driver
[ 10.225860] usb usb1: Manufacturer: Linux 2.6.28.10-power47 musb-hcd
[ 10.225891] usb usb1: SerialNumber: musb_hdrc
[ 10.309967] twl4030_usb twl4030_usb: HW_CONDITIONS 0xd0/208; link 2
[ 10.318664] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[ 10.387084] twl4030_usb twl4030_usb: HW_CONDITIONS 0x50/80; link 1
[ 11.013061] NET: Registered protocol family 10
[ 11.013885] lo: Disabled Privacy Extensions
[ 11.014434] ADDRCONF(NETDEV_UP): phonet0: link is not ready
[ 12.319732] hub 1-0:1.0: hub_suspend
[ 12.319763] usb usb1: bus auto-suspend
twl4030_rtc as rtc0
[ 5.985076] twl4030_rtc twl4030_rtc: Power up reset detected.
[ 5.988403] twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
[ 5.993743] lp5523 2-0032: LP5523 Programmable led chip found
[ 5.994110] Linux video capture interface: v2.00
[ 6.082214] I2C driver for Si4713 FM Radio Transmitter
[ 6.396911] isp_mod: disagrees about version of symbol
[ 12.562469] Adding 786424k swap on /dev/mmcblk0p3. Priority:-1 extents:1 across:786424k
[ 12.765136] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
[ 15.854736] EXT3 FS on mmcblk0p2, internal journal
[ 15.854797] EXT3-fs: recovery complete.
[ 15.860900] EXT3-fs: mounted filesystem with writeback data mode.
[ 15.894195] kjournald starting. Commit interval 1 seconds
[ 17.252777] McSAAB: ACWAKE DOWN
[ 17.252807] McSAAB: ACWAKE UP
[ 17.252868] McSAAB: WAKELINES TEST OK
[ 17.253173] ADDRCONF(NETDEV_CHANGE): phonet0: link becomes ready
[ 17.370178] Bluetooth: L2CAP ver 2.13
[ 17.370208] Bluetooth: L2CAP socket layer initialized
[ 17.459289] Bluetooth: SCO (Voice Link) ver 0.6
[ 17.459320] Bluetooth: SCO socket layer initialized
[ 17.507995] hci_h4p hci_h4p: firmware: requesting bcmfw.bin
[ 17.976257] Bluetooth: RFCOMM socket layer initialized
[ 17.976318] Bluetooth: RFCOMM TTY layer initialized
[ 17.976348] Bluetooth: RFCOMM ver 1.11
[ 21.939178] misc iphb: Module registered in 2.6.28.10-power47, built May 3 2011 20:42:30
[ 25.045288] slide (GPIO 71) is now open
[ 30.994293] pvr: osso_startup_wi: cleaning up 97 unfreed resources
[ 46.207611] cfg80211: Regulatory domain changed to country: EU
[ 46.207641] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 46.207641] (2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 46.207641] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 46.207672] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[ 46.207702] (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 47.537567] wl12xx spi4.0: firmware: requesting wl1251-fw.bin
[ 48.856964] SCSI subsystem initialized
[ 48.990997] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[ 49.006195] wl1251: firmware booted (Rev 4.0.4.3.7)
[ 49.232879] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 49.490997] Driver 'sd' needs updating - please use bus_type methods
[ 50.107849] wl1251: down
[ 52.115539] wl1251: 151 tx blocks at 0x3b788, 35 rx blocks at 0x3a780
[ 52.131164] wl1251: firmware booted (Rev 4.0.4.3.7)
[ 52.350097] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 53.225006] wlan0: authenticate with AP 00:03:7f:fe:00:00
[ 53.227600] wlan0: authenticated
[ 53.227630] wlan0: associate with AP 00:03:7f:fe:00:00
[ 53.246246] wlan0: RX AssocResp from 00:03:7f:fe:00:00 (capab=0x411 status=0 aid=2)
[ 53.246276] wlan0: associated
[ 53.303283] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 63.966949] wlan0: no IPv6 routers present

I can't help you with that, maybe you could find someone who knows whats the problem is in this thread:
http://talk.maemo.org/showthread.php?t=73315

I installed nitdroid and it still shuts down when booting!

Red led starts to blink and device shuts down. If I plug the charger while booting nitdroid, the system starts up fine but battery icon shows empty and tells me to connect charger...

It's weird that when charger (or usb) is plugged in, the device "forgets" about low battery (although battery is full).

It's really strange, but i can only assume, that Nitroid got own means of "decision making", working much different than bme.

You can ask about it in Nitroid thread. Apparently, it got nothing to do with getbootstate (in Nitroid)

I would suppose the only moment getbootstate is relevant for NITDroid is the part right before NITDroid is actually loaded (i.e. the part where you boot into multiboot/bootmenu and switch OSs). Although, multiboot has its own /sbin/preinit file, as well as a /sbin/preinit-real file, in its package, so idk what that does - it might just ignore getbootstate until after multiboot menu is skipped.

At any rate, since Android has completely seperate battery monitoring internals, there's no doubt the actual battery problem will manifest in both OSs seperately and will need seperate fixes.

I came on here, though, to say something odd that I found - pali's replacement getbootstate randomly started showing the correct value - "USER" - I just noticed today, but I haven't looked for the last few days when my device was rebooting.

I'd say that's even more evidence that pali's getbootstate works correctly, although the odd "SHUTDOWN" state 'bug' from earlier may still have to do with it.

If nitdroid has completely different monitoring system, i guess that the battery status chip is really damaged.
Correct me if I'm wrong, but even if I mod my n900 to use different batteries, nitdroid won't boot because it would also give "low battery" warning. If this is the case I think I will have to stay using maemo or look for a possible/similar solution with nitdroids boot state....

Mentalist: Just to know, have you tried to use Estel's getbootstate?

I would try to find someone who can help with the latter - kinda how Estel modified Pali's getbootstate to make it always return the right boot state.

No, I haven't as of yet. No need for me personally, since all Estel's mod did was make it report the "USER" state all the time. I was going to test it to confirm his mod still worked on a normally functioning device, but I haven't had the time to do so.

Also, as jvollmann already managed to boot device in USER state with my ugly hack, testing it on working device is quite pointless, as we already know it works. I would go for Mentalist suggestion, to ask someone used to Nitroid (nitroid thread?), is similar ugly hack can be done to some nitroid script.

I thought I remembered you or someone else being interested in seeing if I got it working on my device - may have been before jvollmann confirmed it worked for him though...

Yep, as a totally unbiased third party I agree with you agreeing with me.

I'd actually suggest going to the NITDroid forums and seeing what you can get over there from the NITDroid devs in terms of help. That's who'll know the NITDroid boot-up code the best.

After reading through the massive amount of work done here by everyone regarding this problem i think i better stick my oar in and SUGGEST you check the fuze in the charging circuit and also for any dry joints on the usb port ??.

It does sound consistent given all the circumstances and i got the clue from the post that said Nokia flashed using the data pads under the battery.

Please this is only a suggestion do not take it i am correct here in any way or form.