batteries discharge faster when its hot...

---

Added on July 18, 2010, 2:43 ammake sure your PC's bluetooth is set to "available" and not hidden or invisible.

This post has been edited by jananan: Jul 18 2010, 02:43 AM

OTG is sort of dumbed-down hostmode...

for dumb devices. but our n900 is far from dumb.

not yet, they are working on it. not nokia, but the community.

in simple words, our n900 has the hardware but not the software/drivers for it

you should check out the front page, of this thread.

you should also check out talk.maemo.org

you can delve into mce... i only tried disabling keyboard light, and it works perfectly. haven't looked into screen brightness yet.

---

Added on July 20, 2010, 11:23 amPS : anyone tried disabling start-up scripts from event.d ?

i tried disabling about 5 items, mostly phone / sms / packet-data related stuff, because i only use it as a tablet (minus phone func) but i didnt notice any improvement in memory / cpu usage.

haven't tried looking into init.d yet.

This post has been edited by jananan: Jul 20 2010, 11:23 AM

n900 uses this instead...

http://upstart.ubuntu.com/

---

Added on July 20, 2010, 2:02 pmhttp://forums.precentral.net/webos-internals/255538-sr71-blackbird-kernel.html

they have done it again. 1.2 Ghz. similar processor as our baby if i am not mistaken....

---

Added on July 20, 2010, 2:11 pmwth.... these dumb***es never heard of 3G video calling is it ?

http://www.youtube.com/watch?v=-NlIiEGjC1g...player_embedded

This post has been edited by jananan: Jul 20 2010, 02:39 PM

i am just using mac filtering with the SSID i use with n900, faster connection start-up. cos i always connect and disconnect. WEP/WAP/WAP2 just makes it slower...

who wanna capture my packet go ahead la...

V4 was exterminated...

most 2mm and 3mm charger is below 800mA rating. for e.g. a 2mm 500mA charger will take forever to charge your n900.

charge up your battery in another phone, or use a freshly charged BL-5J. try flashing with that.

what the n900 does is a semi boot before it starts charging. if the battery is too low, you wont be able to flash.

or try leaving it connected to the charger for a while - like 20-30 minutes before trying to flash.

because connecting to usb locks the dev @ 500Mhz and it might use more power than what the usb supplies while connected to PC.

it might not be enough to flash.

give it a try, it might work.

even though some articles / posts say that the n900 can charge from completely dead, without booting the OS, i find it somewhat hard to believe. because it acts funny when charging a dead n900, even with the original charger.

it receives charges, suddenly stops, then unplug-replug charges again. keeps doing this sometimes when u charge a completely dead phone.

it does not do this when you charge to a certain level and boot up the phone and leave it in desktop. it plays nice when the charger is connected when its on the hildon-desktop.

funny.

---

Added on July 21, 2010, 12:25 pmhaha...

just wait... i've had the boot loading indicator which is " . . . . " running for a solid 5 minutes one time when it crashed running very low voltage. i just left it there... and it still went to desktop...

its running a forced fsck on the whole damn thing, trust me. fsck is something like chkdsk, same thing when u did not shutdown your windows properly...

This post has been edited by jananan: Jul 21 2010, 12:25 PM

i think i was running at least 3 browser windows, some with flash some now. conky was running in background and angry birds minimized.

maximum stress u can guess. and my 750:42,430 did not hold it in... *poof* rebooted...

next thing, the loading ". . . ." ran for 5 minutes. and then went to desktop.

---

Added on July 21, 2010, 12:28 pmeasier with ssh and winscp if you want to see the "rest" of the filesystem from windows. without that you can only see the "home/mydocs" folder...

This post has been edited by jananan: Jul 21 2010, 12:29 PM

i've seen strange things with low voltage.

files getting corrupted. sometimes i've got some text file open, and contents from some other files, for example microb preferences files ends up inside the text file i was viewing.

i had microb open but not the microb prefs file.

so whatever is loaded in memory, it just dumps to whatever files are still open and does a reboot...

they have to fix this and let it dump memory contents to a dump file when crashing, like windows. rather than mixing up all the data...

---

Added on July 21, 2010, 12:45 pmthe tracker process not indexing memory card contents. might need a reboot. and connect to charger first and reboot. if still cannot, open up tracker-cfg file and enable indexing on external media...

cant remember the exact line... but there is such an option...

i totally disabled all indexing on internal and external media. indexing is something you dont run on mobile devices... even on desktops... vista and windows 7 indexing slows down the machine and hogs i/o ... unless you got a spanking new i7...

---

Added on July 21, 2010, 12:53 pmif i am not mistaken, flasher-3.5 will see the entire n900 internal memory as a drive, so whether contents there is corrupted or not... you can still flash it...

unless of course overclocking really bricked your device, which i think not since you can still get to the ". . . ." loading screen...

a bricked device will remain blank, you can just barely see the backlight on the display and thats it. nothing at all... blank.

anyway, the n900 has some scripts running to push down the clock Mhz when the temperature reaches certain level. i have seen the config file somewhere but i cant remember where... so its kinda very very impossible to totally brick it...

those ppl at pre central, palm pre that is... have a new kernel... 1.2Ghz. same processor as our n900.

even if something locks the processor at 1150Mhz which is max for the OC kernel, if its running on the battery, the battery will run out first before there is permanent damage on the processor.

unless of course you hook it up to the charger, and some process locks it at 1150Mhz and you leave it on charger for 2 days charging...

haha... u might smell something burning then...

---

Added on July 21, 2010, 12:55 pmeven then, i have seen some config in one of the files... can't remember as well... that reboots the system when some process locks the processor for a long time...

so its kinda hard to burn it completely by overclocking...

PS : i have to keep track of the changes i make to my n900. now if i had to reflash it, i would not remember what i changed...

---

Added on July 21, 2010, 1:29 pmwhat the...

http://www.youtube.com/watch?v=-b-aoZNv-q0...player_embedded

Steve just can't stop... can he ?

This post has been edited by jananan: Jul 21 2010, 01:29 PM

dont use the -R when flashing fiasco. meaning dont reboot between fiasco flash and emmc flash.

flasher-3.5 -F <fiasco-image> -f -R

just take out the last -R

then continue flash the eMMC as usual. this will prevent a reboot in between.

look at this

http://discussions.europe.nokia.com/t5/Mae...ing/td-p/678373

---

Added on July 21, 2010, 2:45 pmhave you dropped or knocked your n900 really hard ? eMMC dislodged ?

This post has been edited by jananan: Jul 21 2010, 02:45 PM

or you can try this if you think its the eMMC dislodged

http://forum.gsmhosting.com/vbb/f148/n900-...olution-986005/

---

Added on July 21, 2010, 2:48 pmyou can see "banding" on photos and graphics with smooth color transition...

http://en.wikipedia.org/wiki/Colour_banding

---

Added on July 21, 2010, 2:57 pmafter flashing fiasco without -R, disconnect the usb cable and try this

flasher-3.5.exe -i

remove the battery, put battery back in, plug in USB cable

see if it detects...

This post has been edited by jananan: Jul 21 2010, 02:57 PM

after flashing fiasco without -R, disconnect the usb cable and try this

run this command first, with the phone disconnected

flasher-3.5.exe -i

remove the battery, put battery back in, plug in back to the computer

see if it automatically detects... (flasher-3.5.exe -i causes it to wait for usb connectivity)

you might need to close the flasher app, using Ctrl+C to go back to dos prompt

if it had detected in the previous command, then flash the eMMC image using normal method

because if it detects the phone so that you can flash fiasco, then it should allow you to flash your eMMC as well.

as long the eMMC is not really damaged/dislodged that is...

---

Added on July 21, 2010, 3:09 pmdepends on what you do and how often you do it. for me...

continously online using wifi - maybe 3 - 4 hours on a full battery and 2 bars brightness.

online with flash heavy sites and youtube - maybe 2-3 hours only.

just using to play mp3 - more than 8 -12 hours, with the screen not activated of course

using a normal phone - without connecting to wifi/3G - can last more than a day of course...

if very less calls and sms and just left on standby most of the time - 2 days or more...

if heavy calls and sms - without wifi/3G - 7-8 hours usually

* results may vary...

but now i am using it a tablet only, no sim card inside... can last much longer...
(but not much different when i am online using wifi of course)

---

Added on July 21, 2010, 3:15 pmor try NSU (Nokia Software Updater)... it has an option to re-install firmware for the n900...

This post has been edited by jananan: Jul 21 2010, 03:15 PM