Editing User:Kotczarny

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

== few tips/notes ==

=== 5 dot syndrome (no boot to desktop), possible reasons ===

1/ missing /home/user

2/ initscripts fail for hildon-desktop (happened to me when there was an error in /home/user/.profile *doh*)

=== stuck orange ===
stop mce; sleep 10; start mce

=== stuck usb status bar plugin ===
ke-recv-test p; sleep 1; ke-recv-test c

=== battery calibration ===
The Valid Discharge Flag (VDQ) in the FLAGS register is set when
this condition occurs and remains set until the learning discharge cycle completes or an event
occurs that disqualifies the learning cycle. A learning cycle can be disqualified by
any of the following conditions:
1. Cold temperature: Temperature â¤ TCOMP[3:0] (°C) when the EDV1 threshold voltage is reached. 
2. Light load: A capacity learning cycle is disqualified if average current is less than
or equal to 2 times the initial standby load when the EDV1 threshold voltage is reached.
3. Fast voltage drop: VOLT (EDV1 256 mV) before EDV1 is set.
4. Excessive charging: Cumulative Charge >255 NAC counts (910 *Vh) during a learning discharge
cycle (alternating discharge/charge/discharge before EDV1 is set)

This boils down to: don't charge during learning cycle (self evident), do discharge with 
a moderate load that's not too low but also not too high particularly don't cause load bursts
when batt voltage is about to reach EDV1 ideally you keep backlight lit, this will warrant
a proper calibration.

=== battery charging current check/set ===
to get 500 mA from a 500 mA charger after plugging in:
* echo 500 >/sys/class/power_supply/bq24150a-0/charge_limit
you can also read that file to see how much it's willing to draw; will probably say 100 after plugging it into unsupported charger

=== disable 'telephony functions' popup (for those with broken modem) ===
sed -i s/start on started dbus/# start on started dbus/ /etc/event.d/sscd

(thanks to peterleinchen https://talk.maemo.org/showthread.php?t=93158 )

=== make n900 with broken screen boot and display proper image on av cable ===
put 'fbset -g 800 480 800 480 16' right before X server start in /etc/event.d/xomap (or /etc/event.replace.d/xomap )

=== misc links ===
[[N900_shortcuts_and_gestures]]

=== scratchbox/sdk ===
[[Documentation/Maemo_5_Final_SDK_Installation]]
http://repository.maemo.org/stable/fremantle/

=== rescueOS ===
http://n900.quitesimple.org/rescueOS/
https://n900.quitesimple.org/rescueOS/rescueOS-1.2/documentation.txt

=== irc wisdom ===

==== ~flatbatrecover ====
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)

==== ~flashing ====
[[Updating_the_tablet_firmware]], or (on linux PC) download&extract  http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh

win7 64bit: http://talk.maemo.org/showpost.php?p=849980&postcount=20

==== ~usbnetworking ====
[[USB_networking]], [[N900_USB_networking]]

==== ~jrtools ====
[[User:Joerg_rw/tools]]  (some tips and hacks)

==== ~keyremap ====
[[Remapping_keyboard]]

== bookmarks ==
* [[N900_Hardware_Power_Consumption]]

== devel shortcuts ==
* [[Developer_FAQ]]
* [[Documentation/Maemo_5_Developer_Guide]], [[Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain]]
* [[Packaging]]
* [[Uploading_to_Extras-devel]]
* [[Desktop_file_format]]
* [https://wiki.maemo.org/Category:Development category:development]
* [[Repository#List_of_Maemo_repositories]]
* [http://bigbob.fun.free.fr/for-freemangordon/adding-ramzswap-driver.diff ramzswap for 2.6.28]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "http://wiki.maemo.org/User:Kotczarny"

Personal tools

Navigation

Views

Editing User:Kotczarny

@@ Line 62: / Line 62: @@
   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)
-==== ~bootloop ====
-bootloop is 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.
 ==== ~flashing ====