| 01:01.15 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 02:31.43 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 04:56.39 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 07:51.13 | *** join/#maemo peetah (~peetah@cha92-9-82-236-202-86.fbx.proxad.net) |
| 11:00.46 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 11:30.44 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 11:38.06 | *** join/#maemo grinsekatze (~andreas@unaffiliated/grinsekatze) |
| 12:38.32 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 14:12.29 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 14:28.55 | sunshavi | how could I use the PULSE_SERVER var with the fmradio? |
| 17:10.33 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 17:56.24 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 18:21.11 | *** join/#maemo cyteen (~cyteen@static-84-9-179-245.vodafonexdsl.co.uk) |
| 19:19.17 | *** join/#maemo valeriusN (~valerius@osfree.org) |
| 19:21.26 | *** join/#maemo nslu2-log (~nslu2-log@milla.nas-admin.org) |
| 19:33.38 | *** join/#maemo akossh (~akossh@unaffiliated/akossh) |
| 19:41.29 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 21:20.28 | *** join/#maemo infobot (ibot@96-86-209-99-static.hfc.comcastbusiness.net) |
| 21:20.28 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog http://maemo.cloud-7.de/irclogs/freenode/_maemo/latest.log.html | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 21:20.29 | *** mode/#maemo [+v infobot] by ChanServ |
| 21:21.42 | sixwheeledbeast | try charging it for a while first |
| 21:22.18 | sixwheeledbeast | third party charger may take longer. |
| 21:24.21 | pere | it has been charged for a while before I got it. will leave it plugged in over night. :) |
| 21:26.13 | sixwheeledbeast | ~flatbatrecover |
| 21:26.14 | infobot | Remove battery for 1 minute. Insert battery. Plug powered ***NOKIA WALLCHARGER*** to device. Watch steady amber. Let sit and charge. Do NOT try to boot. After 30 min, you got either a) a booted up N900, b) flashing amber which means you can boot, c) steady amber shut off -> start over again with ~flatbatrecover while already searching for a new battery. CAVEAT! Only works when ~rootfs OK (no ~bootloop) |
| 21:26.29 | sixwheeledbeast | ~bootloop |
| 21:26.29 | infobot | bootloop is probably when your device has broken rootfilesystem, so during reboot it fails on some service startup or kernel module load and thus reboots. This *drains* battery! And you can't reflash to stop bootloop when battery is drained. Recharge your battery by other means before reflashing. E.g. using ~rescueOS. Or external charger or BL-5J compatible other device. |
| 21:29.46 | pere | what if I do not have a nokia wallcharger? |
| 21:35.31 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 21:35.49 | sixwheeledbeast | I suppose you have to take your chances, a charger would be better than say a usb port with data like a pc |
| 21:36.50 | pere | after disconnecting the battery, inserting it and inserting the usb plug, I first got a weak nokia logo, then the screen lighted up and gave me some dots, then it went black. the led is blinking. |
| 21:38.39 | sixwheeledbeast | possible bootloop then? |
| 21:39.00 | pere | could be. expected some looping, then, not just black... |
| 21:40.45 | sixwheeledbeast | even when the screen is off the device maybe powered "actdead" |
| 21:41.17 | sixwheeledbeast | ~bootprocess |
| 21:43.37 | sixwheeledbeast | five dots is trying to boot anyway, so I would say it's either broken rootfs or exhausted battery |
| 21:47.53 | akossh | The nokia charger had a connection from D+ or D- to GND or VCC, I do not remember, probably one of them to GND |
| 21:48.52 | akossh | So the charger does not communicate, the phone knows that it is connected to a charger if it detects this "short" |
| 21:49.33 | akossh | If you have a third party charger and a cable with this "short", it can work |
| 21:49.37 | sicelo | D+ shorted to D- (not GND/VCC) |
| 21:50.44 | akossh | sicelo: thanks |
| 21:52.36 | akossh | If this short is missing, the phone will not take as mutch power from the USB socket, and it can not recover from a flat battery |
| 21:56.23 | akossh | Connecting to a USB port via a normal USB cable, my N900 does the following (in case of a flat battery): charges a little, tries to boot, runs flat and resets, then this repeats |
| 21:57.13 | akossh | however, using a third party charger with a "powerbank cable" works fine |
| 21:57.35 | akossh | It boots up successfully for the first or second try. |
| 22:06.25 | *** join/#maemo xmn (~xmn@user-0cdft0l.cable.mindspring.com) |
| 22:08.23 | pere | moving to a usb charger instead of a pc usb port, got the boot going. :) |
| 22:10.26 | sicelo | :) |
| 22:19.01 | *** join/#maemo nslu2-log_ (~nslu2-log@milla.nas-admin.org) |
| 22:37.23 | *** join/#maemo nslu2-log_ (~nslu2-log@milla.nas-admin.org) |
| 22:40.18 | *** join/#maemo nslu2-log (~nslu2-log@milla.nas-admin.org) |
| 23:19.40 | pere | is there a 'factory reset' option? would like to get rid of all the trases of the previous owner. |
| 23:34.32 | sicelo | reflashing is the surest way |