**** BEGIN LOGGING AT Sat Apr 07 02:59:59 2012 Apr 07 03:00:01 I have, but to answer his questions how to check clocks for example I had to find out for myself about all that shit again. It's already inside guts of hostmode kernel to the ellbows Apr 07 03:00:15 I see. Apr 07 03:00:59 first of all, check the basic things: was it actually highspeed mode? Apr 07 03:01:11 (check) yep. Apr 07 03:01:33 can the attached drive do better when running exactly same test on a linux PC Apr 07 03:01:42 (valid) yep. Apr 07 03:01:52 ~20 MB/s Apr 07 03:02:18 3 devices Apr 07 03:02:20 then I suggest you run a profile against the whole shit, to see where it dumps the time Apr 07 03:02:59 ok... "run a profile" in bright noob friendly language? Apr 07 03:03:02 might be the sda driver, might be USB, might be CPU load at max, dunno Apr 07 03:03:21 CPU load wasn't the case Apr 07 03:03:48 s for sda driver I could connect dvd reader and dump something from it to /dev/null Apr 07 03:03:50 nfc, maybe you could use gdb for that. It's no simple task I just forgot to perform to validate USB h-e-n against highspeed Apr 07 03:03:57 its isnt using sda, yep? Apr 07 03:04:45 I see... at least in overall context ;) Apr 07 03:05:00 dumping sth fron /dev/sda to /dev/null should rule out quite a lot of drivers Apr 07 03:05:33 aye. will perform Apr 07 03:06:06 check h-e-n raher kenel-MUSB syslog, to see what it actually does Apr 07 03:06:14 erm, dd if=/dev/sda of=/dev/null isnt enough to rule out drivers, most of them? Apr 07 03:06:16 raher* Apr 07 03:07:01 well, most of them, yes. obviously Apr 07 03:07:12 so it was actually done Apr 07 03:07:24 same 4.x MB/s Apr 07 03:07:34 where's the syslog? Apr 07 03:07:43 syslog part wasn't done Apr 07 03:07:49 Want to do that Apr 07 03:08:04 yet, how exacdtly filter it rfor H-E-N? I'm lost here Apr 07 03:08:12 meh. so it's absolutely worhless as you can't even guarantee the USB was at highspeed Apr 07 03:08:24 in part "check h-e-n rather than kernel-MUSB syslog" Apr 07 03:08:40 -tahn Apr 07 03:08:47 ok, so lest make it worhty and check that (dmesg said it was highspeed) Apr 07 03:09:10 duh, you've seen that? Apr 07 03:09:14 yep. Apr 07 03:09:24 I doubt you have Apr 07 03:09:27 high-speed device attached etc Apr 07 03:09:35 doesn't mean a thing Apr 07 03:09:36 if we're talking about same thing Apr 07 03:09:40 I see. Apr 07 03:09:50 how to check it properly? Apr 07 03:09:52 attached != connection set up Apr 07 03:10:24 check each single log line, compare to kernel sources what it means Apr 07 03:10:30 whole thing in dmesg from within hen told about high-speed, yet will re-check with pleasure Apr 07 03:10:31 basically Apr 07 03:11:13 also I, for unknown reasons, always thought dmesg is inferior to syslog Apr 07 03:11:26 ok, You think it will allow to find bootleneck in usb kernel implementation? Apr 07 03:11:29 I see Apr 07 03:11:41 how You would check syslog for that particular case? Apr 07 03:11:53 I dunno Apr 07 03:12:23 how would you spot a bug in your app? Apr 07 03:13:03 would check logs vs code under different condition ;) Apr 07 03:13:07 I mean, rather Apr 07 03:13:14 that I havent used syslog over dmesg Apr 07 03:13:24 so it just that I run syslog after operation Apr 07 03:13:29 and check every line? Apr 07 03:13:40 like with dmesg? Apr 07 03:13:43 syslog creates logfile Apr 07 03:13:47 you read that Apr 07 03:14:01 /var/log/syslog Apr 07 03:14:28 the nice thing is: it has realtime timestamps Apr 07 03:14:35 so basically start syslogd (daemon?), do thing, end it Apr 07 03:14:38 check logs? Apr 07 03:14:46 so if you know system time of your actions, you spot them in there Apr 07 03:14:53 nice thing Apr 07 03:15:29 syslog = syslogd? Apr 07 03:15:41 plus I'm not sure if logger(1) will log to dmesg at all Apr 07 03:15:46 yep Apr 07 03:15:50 mine outputs by default to /var/log/messages Apr 07 03:15:51 ok Apr 07 03:16:01 depends Apr 07 03:16:18 on one system it's messages on other one syslog Apr 07 03:16:29 on third maybe kernel Apr 07 03:16:43 depends on syslog.conf Apr 07 03:16:49 on maemo messages Apr 07 03:16:54 ok, wtf is log rotation Apr 07 03:16:56 maybe Apr 07 03:16:57 another file? Apr 07 03:17:21 logrotate tgz's your logfile and moves it outa the way Apr 07 03:17:26 every other week Apr 07 03:17:43 I see. not rellevant here I suppose... Apr 07 03:17:49 not really Apr 07 03:18:13 Ok, will do those tests (not today) and drop results on TMO, then drop here for a small talk... :P Apr 07 03:18:23 YW Apr 07 03:18:35 Thnaks a lot for another hours of Your time Apr 07 03:18:43 really appreciate Your patience :) Apr 07 03:18:55 thanks for helping on brushing out the bugs Apr 07 03:18:59 (if any) Apr 07 03:19:19 will try my best... See ya! and happy chocolate egg Apr 07 03:19:25 haha Apr 07 03:19:41 no choko here, neither eggs nor other Apr 07 03:19:47 :-/ Apr 07 03:20:11 where's that friggin bunny? Apr 07 03:20:19 * DocScrutinizer fetches gun Apr 07 04:13:07 DocScrutinizer: infobot joined! Apr 07 04:17:41 hi Apr 07 08:01:17 uhm Apr 07 10:30:40 wanting to try nitdroid, could anyone tldr tgnt for me? Apr 07 10:31:08 tl;dr The Great Nitdroid Thread Apr 07 10:31:20 * Apr 07 10:32:58 szopeen: wrong channel, they have their own IIRC Apr 07 10:33:20 thx Apr 07 10:34:17 hmm... ammyt doesn't seem to have it as his signature, care to link it or provide reference? Apr 07 10:36:23 got it #nitdroid Apr 07 11:28:45 nitdroid topic is generally a bit of deprecated here Apr 07 11:29:57 not least because it needs multiboot which is a strongly deprecated topic Apr 07 11:31:36 and of course because in the end it's andridiot and we don't really like that either Apr 07 11:32:49 tough I start to respect andridiot since harmattan is ruining our day Apr 07 13:00:12 hm, what's up with there being a gcc-4.6 package in the repositories that is completly empty? Apr 07 13:00:22 and why is it even there Apr 07 13:09:28 http://mynokiablog.com/2012/04/07/nokia-rm-714nokia-311-appears-at-fcc-full-touch-s40meltemi-with-swipe-and-multitouch/ Apr 07 13:09:31 FWIW Apr 07 13:10:00 the meltemi part is ... err... obscure Apr 07 13:10:58 maybe it's a watered down harmattan Apr 07 13:11:12 i really cant imagine nokia dumping another load on symbian Apr 07 13:11:33 S40meltmi is clearly bogus Apr 07 13:12:00 Unless... Apr 07 13:12:12 well, Nokia naming always been bogus, no? Apr 07 13:12:22 Maybe the agreement with microsoft waid no linux phones, but diddn't ention symbian Apr 07 13:12:35 so it's some sort of bastardised system. Apr 07 13:12:43 Due to internal infighting. Apr 07 13:12:44 I'd bet it is Apr 07 13:13:38 after all, symbian been a maemo alike approach once before, according to that history tale? Apr 07 13:14:12 the "osso" times, I guess Apr 07 13:14:24 yeah Apr 07 13:18:39 maybe Flop now faces some backlash from his evil masterplan to kill linux and Nokia even internally Apr 07 13:18:57 i wouldnt be surprised. Apr 07 13:19:03 n900 sometimes charging even from the wallwart means the usb socket is dead? Apr 07 13:19:18 only sometimes* Apr 07 13:19:28 yep, probably Apr 07 13:19:43 dang Apr 07 13:19:54 though it needs furhter investigation to tell for sure Apr 07 13:19:57 it's not even 5 monsths old Apr 07 13:20:02 DocScrutinizer: such as? Apr 07 13:20:04 it's wobbly Apr 07 13:20:08 deal with ti Apr 07 13:21:18 such as connecting it to PC and see if you can establish data connection. check mechanically, check optically all plugs. check syslog, /sys, and bq72k-detail Apr 07 13:22:00 could as well be powerkernel with modprobed bq24150.ko that kills bme, for example Apr 07 13:22:38 or a defect battery, defect cable, whatnot else Apr 07 13:23:03 also PEBKAC is widespread ;-D Apr 07 13:23:52 syslog, what should I see there? Apr 07 13:25:33 one thing you definitely should NOT try: bend the charger USB plug when plugged to see if it is rigid or starts charging Apr 07 13:25:42 I repeat: *NOT* Apr 07 13:26:58 well, in syslog you might see e.g. bme moaning about problems on start Apr 07 13:27:20 or you should see some notice about vbus attached or similar thing Apr 07 13:27:58 I will defenetely won't be touching it, knowing that it has problems Apr 07 13:28:13 I have no syslog Apr 07 13:28:26 /home/user # cat /var/log/syslog Apr 07 13:28:26 cat: can't open '/var/log/syslog': No such file or directory Apr 07 13:28:59 first of all: are you using powerkernel? Apr 07 13:29:04 no Apr 07 13:29:12 good, err bad Apr 07 13:29:21 then that's not the reason Apr 07 13:29:24 DocScrutinizer: should I, then? Apr 07 13:29:28 nope Apr 07 13:29:31 ah, ok Apr 07 13:30:11 does the device switch on from powerdown when you plug in charger or PC via USB? Apr 07 13:30:18 the phone it's mostly pristine, execpt for some soft (marble, a music player) and some fooling aroung with the partitions and the sd Apr 07 13:30:27 lemmesee Apr 07 13:30:49 sometimes it lights the screen (I set it up so, I think) Apr 07 13:30:54 switch on like in "LED shines up" or anything Apr 07 13:30:59 but it doesn't start charging Apr 07 13:31:23 ok, it's switched off Apr 07 13:31:48 watch the LED! Apr 07 13:32:09 does it shine up bright amber for a short moment when plugging in? Apr 07 13:32:30 I plugged in to the wllawart, it showed the faded nokia logo, it blinked once or twice red, and nothing else, black screen, seemingly not powered on Apr 07 13:32:45 blinked RED? Apr 07 13:32:52 s/itblinked/the led blinked/ Apr 07 13:32:56 yeap Apr 07 13:33:04 I can do it again Apr 07 13:33:04 dead battery most likely Apr 07 13:33:14 the battery's fine Apr 07 13:33:19 and I have 3 Apr 07 13:33:26 no, it's not when device blinks red Apr 07 13:33:52 or at very least device doesn't think battery is good Apr 07 13:34:04 that's why red blinking usually Apr 07 13:34:06 sonuva... Apr 07 13:34:11 ok Apr 07 13:34:35 it bribrated and showed the faded nokia logo Apr 07 13:34:46 it slow-blinked the led twice Apr 07 13:35:08 it showed the booting animation once (that's the 5 white dots) Apr 07 13:35:11 and nothing else Apr 07 13:35:12 red blinking means: either your batery is defect, or your device charger&battery-care circuit is defect, *or* the software is defect that manages all that Apr 07 13:35:38 I'm powering it on now Apr 07 13:35:39 it may take a quite long while after the 5 dots Apr 07 13:35:42 minutes Apr 07 13:35:50 it's booting Apr 07 13:35:59 pin code Apr 07 13:36:17 anyway, device isn't supposed to bot completely when just plugged in. Your description is absolutely fine Apr 07 13:36:20 normal boot Apr 07 13:36:29 ! Apr 07 13:36:34 err device behaviour as described by you is fine Apr 07 13:36:39 it think's it's connected to the pc Apr 07 13:36:53 :-/ Apr 07 13:37:01 it askme wether to put it in mass storage mode or pc suite mode Apr 07 13:37:09 I suspect you might have problem with datalines of USB Apr 07 13:37:17 dang Apr 07 13:37:30 good thing I have 3 batts and an external charger Apr 07 13:38:09 almos from the beginning it was a lottery wether it charged from the pc or not Apr 07 13:38:21 then I simply stopped trying Apr 07 13:38:47 connect to PC, see if you get a stable USB "data connection" (i.e. if mass storage mode works fine and without any problems for some 30 min or longer. you may *slightly* tap on the plug, to trigger possible hidden contact problems) Apr 07 13:39:11 ok Apr 07 13:39:22 I'll have to try later, I don't have the cable here Apr 07 13:39:38 thanks so far Apr 07 13:40:04 get bq27k-detail script, run it, once solo, once with parameter "10", pastebin the results Apr 07 13:41:44 StyXman: what makes you think your device doesn't charge? Apr 07 13:41:50 to begin with Apr 07 13:43:12 the LED blink patterns are changeable at your discretion Apr 07 13:43:33 DocScrutinizer: no batt animation, no charging notice, no slow-blinking red in the led and no actual charging Apr 07 13:43:40 I mean, the batt level doesn't go up Apr 07 13:43:50 red? amber! Apr 07 13:43:51 yes, I know, but I hadn't Apr 07 13:44:01 red, it was always red Apr 07 13:44:11 that's odd in itself Apr 07 13:44:11 unless I'm color blind Apr 07 13:44:53 well, you can test proper red Apr 07 13:45:00 lemme find the line for you Apr 07 13:45:02 and I know the RGB leds work because I get red for charging, blue for SMS and green for something else Apr 07 13:45:22 green for charging done Apr 07 13:48:07 please do:: dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternError" Apr 07 13:48:39 is this what you see for charging? is the color the same? Apr 07 13:49:33 yes, the same red, but the pattern it's different Apr 07 13:49:55 after checking, do:: dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:"PatternError" Apr 07 13:50:04 when chargin is more like fade in-fade out, in red Apr 07 13:50:40 maybe yellow led is broken Apr 07 13:50:42 please do:: dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternBatteryCharging" Apr 07 13:50:57 there's no yellow LED Apr 07 13:51:00 jacekowski: yellow led? isnt it the red+green leds? Apr 07 13:51:09 well, green then Apr 07 13:51:45 StyXman: what's the pattern you get with last one? Apr 07 13:52:38 DocScrutinizer: yeap, glowing/slow blinking/fade in-fade out red Apr 07 13:52:45 red? Apr 07 13:52:52 I don't know how to call it Apr 07 13:52:54 yes, red Apr 07 13:53:17 may be I changed, I don't remember Apr 07 13:53:22 please do:: grep "PatternBatteryCharging=50;5;0;rg;" /etc/mce/mce.ini Apr 07 13:54:03 there is no way to do it in the settings, only activate or not Apr 07 13:54:03 does it return a result? Apr 07 13:54:53 even better: http://pastebin.lugmen.org.ar/7380 Apr 07 13:55:08 it seems that I changed it after all Apr 07 13:56:33 no, looks good to me? Apr 07 13:56:53 aaah, FOUR Apr 07 13:57:22 well, that doesn't explain why yours doesn't work, just that I changed mine Apr 07 13:57:57 yours seems to be the original! Apr 07 13:58:04 hah! Apr 07 13:58:07 so you haven't changed anything Apr 07 13:58:19 this should cause amber blinking, not red Apr 07 13:59:08 what's the color of the LED when you push the powerbutton? is it fading in white when power up? Apr 07 13:59:58 are you connected via ssh & wlan? or typing on device? Apr 07 14:01:10 ssh+wlan Apr 07 14:01:32 well, anyway - please deactivate the amber/red charging pattern Apr 07 14:01:36 the led fades in in purple when I turn it on Apr 07 14:01:52 aaah, green LED defect Apr 07 14:01:55 please do Apr 07 14:02:03 dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:"PatternBatteryCharging" Apr 07 14:02:54 dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternBatteryFull" Apr 07 14:04:48 hmm, yes, the green one seems out Apr 07 14:04:50 dang Apr 07 14:05:08 ok, I'll go for the data cables Apr 07 14:05:16 so whan your battery is full, you're definitely missing the green LED indicating that Apr 07 14:05:26 might this be root cause of your problem? Apr 07 14:06:33 ooh, and better scratch all my previous advice, the part that's been based on "red flashing LED" Apr 07 14:08:39 DocScrutinizer: everything? Apr 07 14:08:57 well, we need to start from scratch Apr 07 14:09:08 «No charging, insufficient power» Apr 07 14:09:17 mhm Apr 07 14:09:46 that's an indication (though no proof) that your USB plug or receptacle is broken Apr 07 14:09:58 but it detects the connection ok, asks for mass storage or pc suite modes Apr 07 14:10:12 hmm yeah Apr 07 14:10:22 ... Apr 07 14:10:40 when does that notice show up? PC or wallwart? Apr 07 14:11:19 seems like all the time when I connect it to the PC Apr 07 14:11:34 and with wallwart? Apr 07 14:11:47 with the wallwart I don't get any message, excepts that sometimes it thinks it's connected to the pc Apr 07 14:11:57 (your PC might have a borked USB as well) Apr 07 14:12:04 or maybe just when I boot it connected to the wallwart Apr 07 14:12:31 I tried several pcs, mi NB, my desktop at wor, a coworker's, a coworker's NB... Apr 07 14:12:59 even several usb connectors in my NB Apr 07 14:13:38 ones i know they work with other stuff: usb keys, my mouse's wireless thinguie, external hard disks Apr 07 14:13:41 hmmm. I'd suggest following approach: 1. check your USB receptacle and plug for dirt, bent contacts and the like - use a mgn glass for that and good light. 2. full reflash, just to rule out any sw issues Apr 07 14:14:24 esp check USB cable, use another rcable Apr 07 14:14:41 I have two cables, and tried a third at work Apr 07 14:14:48 :nod: Apr 07 14:15:01 and I guess you're using genuine Nokia wallwart? Apr 07 14:15:06 yeap Apr 07 14:15:15 do as suggested Apr 07 14:16:08 odds are your USB receptacle is about to fail. On the bright side you may fix it easily in that stage, by simply resoldering and enforcing Apr 07 14:16:30 unless it's a contact-bent issue Apr 07 14:16:30 original cable: this time started charging, then said «not charging» Apr 07 14:19:34 StyXman: err, regarding reflashing - it might fail and render your system inoperable when your USB is actually borked Apr 07 14:21:52 also testing with wallwart charger is way clearer setup than charging via PC Apr 07 14:22:28 there are 2 sysnodes you could check. Lemme pick them out for you Apr 07 14:23:50 cat /sys/class/i2c-adapter/i2c-1/1-0048/twl4030_usb/vbus Apr 07 14:24:11 is one, shows "1" when *some* power is attached to USB Apr 07 14:26:24 ~pebkac Apr 07 14:26:25 PEBKAC: Problem Exists Between Keyboard And Chair. Apr 07 14:26:34 ~fud Apr 07 14:26:34 i guess fud is Fear, uncertainty, doubt. Originally invented by IBM, but now used by many others. or YAFA. or Fscking Useless Data or otherwise known as false information or mindless facts with no backup facts or http://www.winntmag.com/Articles/Index.cfm?ArticleID=7420 Apr 07 14:28:47 DocScrutinizer: it's 1 when I plug the wallwart Apr 07 14:29:01 yeah, should Apr 07 14:29:13 might actually be low though Apr 07 14:29:18 or the pc cable Apr 07 14:29:23 and 0 when it's not Apr 07 14:29:28 low on voltage Apr 07 14:29:39 it's 1 even at 3V iirc Apr 07 14:30:03 dang, can't find the other one, for D+/- short Apr 07 14:31:14 anyway, your problem is sufficiently triaged to go ahead check USB recepatcle closely with a magn glass Apr 07 14:33:09 and get (and run) http://enivax.net/jk/n900/bq27200.sh Apr 07 14:33:30 with parameter 5 Apr 07 14:33:40 for a new log every 5s Apr 07 14:33:58 you'll see "realtime" what's going on with battery charging Apr 07 14:34:25 run it *before* plugging in charger Apr 07 14:34:31 so you see the difference Apr 07 14:35:02 preferably have screen dim or locked Apr 07 14:35:22 as it needs quite a bit of power for backlight Apr 07 14:35:23 Need ./i2cget Apr 07 14:35:31 :nod: Apr 07 14:35:43 "...and mentioned his proclivity for ritual territory marking through urination, once relieving himself on a Winnie the Pooh figure at the Disneyland Hotel in Anaheim while saying "This one's for you, Walt."" Apr 07 14:35:56 Farewell. Apr 07 14:35:56 http://enivax.net/jk/n900/bq.tar Apr 07 14:37:32 StyXman: ooh, and you'll need root for that to run Apr 07 14:40:21 I am Apr 07 14:40:38 TTF never changes from 65535 and TTE changes Apr 07 14:40:51 so I guess those are time to full and tme to empty Apr 07 14:41:23 TTF/TTE are rather irrelevant, except that TTF=65535 indicates battery is DIScharging Apr 07 14:41:30 yes Apr 07 14:43:03 StyXman: 1. col (after time) is voltage at battery, 4. is current-in/out Apr 07 14:43:14 DocScrutinizer: http://pastebin.lugmen.org.ar/7381 Apr 07 14:43:38 negative current means discharge Apr 07 14:43:43 yeah, it keeps dischraging Apr 07 14:44:24 that's clearly not charging Apr 07 14:44:37 you attached charger? Apr 07 14:44:43 I plugged it after the few line feeds there Apr 07 14:44:50 mhm Apr 07 14:44:56 no visible change Apr 07 14:45:00 from line 47 Apr 07 14:45:07 no at all Apr 07 14:45:11 dang Apr 07 14:45:43 I'll test the data mode to see if it's stable enough to flash Apr 07 14:45:52 indeed Apr 07 14:45:57 ps bme Apr 07 14:45:59 please Apr 07 14:46:07 hmm Apr 07 14:46:15 ps aux|grep bme Apr 07 14:46:50 coming, I had turned it off to replace the batt, the one it has now is kinda empty Apr 07 14:49:28 738 root 3372 S /usr/sbin/bme_RX-51 Apr 07 14:49:28 909 root 3476 S /usr/lib/hal/hald-addon-bme Apr 07 14:50:13 hmm, loks ok Apr 07 14:50:51 I guess you actually have a hw problem Apr 07 14:51:00 check USB port optically Apr 07 14:51:38 gently try to wiggle the recepatcle with a toothpick or the like, while closely observing Apr 07 14:51:45 DocScrutinizer: looks good, but I don't have a MG Apr 07 14:51:55 MG? Apr 07 14:51:59 aah Apr 07 14:52:02 mag glass Apr 07 14:52:56 well, you're already down to the hells of hw fixing Apr 07 14:53:49 you rang? Apr 07 14:54:05 get a repair shop doing inspection for you and eventually fix (by resoldering), or first investigate further, e.g. by probing connection between USB and testpads under battery Apr 07 14:54:32 you find all 4 relevant signal traces there: D+/D-, vbus, and GND Apr 07 14:54:46 hi mag :-D Apr 07 14:55:27 StyXman: this one will help you no matter what you decide to do next: Apr 07 14:55:29 ~usbfix Apr 07 14:55:30 hmm... usbfix is http://talk.maemo.org/showthread.php?t=75920 - and **NEVER** use epoxy (unless you want to seal your device for underwater) Apr 07 14:55:39 hi DocScrutinizer :D Apr 07 14:55:52 Heya Mohammad Apr 07 14:56:09 moo javispedro Apr 07 14:56:17 DocScrutinizer: nor the port shield nor the data 'film' seems to be loose Apr 07 14:56:20 * RST38h notices we have got a quorum Apr 07 14:56:21 moo Apr 07 14:56:38 and finding a shop doing electronic things here... that would be interesting :| Apr 07 14:56:52 hi javispedro Apr 07 14:57:03 anyways, I don't have the tools to pry it open Apr 07 14:57:24 specially these six-point screws Apr 07 14:57:26 StyXman: if you're feeling comfortable with soldering iron, there's little to worry Apr 07 14:57:45 get a proper torx TX6 Apr 07 14:58:01 DocScrutinizer: not by any definition of confortable and/or confident :) Apr 07 14:58:22 and you should already have a proper soldering iron (no use in getting one and starting to practice) Apr 07 14:58:42 all my successful soldering was with an acid that I don't even know the name of Apr 07 14:58:47 well, then a repair shop or expert friend is your only option Apr 07 14:59:14 reapir shop I guess it's out of question Apr 07 14:59:18 there are none here Apr 07 14:59:26 please do NOT try to fix it yourself! Apr 07 14:59:37 this is the first world, they don't fix shit :-P Apr 07 14:59:51 DocScrutinizer: don't worry, at most I'll open it Apr 07 15:00:02 but again, I don't have the tools Apr 07 15:00:15 already might be a problem when you're not used to delicate electronics Apr 07 15:00:36 the flat ribbon connector from kbd to screen is sometimes quite unforgiving Apr 07 15:00:43 I'm used to delicate things, but electronics and/or soldering, no way Apr 07 15:01:21 then no use in opening the device anyway Apr 07 15:01:23 I was even about to dismantle a broken camera lens to get a MG Apr 07 15:02:02 ok, so I'll keed swapping batteries and using wifi to transfer data Apr 07 15:02:05 yeah, *closely* inspect the contacts in N900 USB receptacle Apr 07 15:03:29 sometimes debris or oxid afects the contacts Apr 07 15:03:41 sometimes one even is bent Apr 07 15:04:22 not that you could probably do much when the contact is bent, other than replacing whole recepacle Apr 07 15:04:28 DocScrutinizer: the contacts in the little piece of plastic in the port? Apr 07 15:04:35 yep Apr 07 15:04:38 wow Apr 07 15:04:41 5 of them Apr 07 15:05:06 two are a bit longer than the other 3 Apr 07 15:05:08 ok, I'll let it pass for now Apr 07 15:05:25 DocScrutinizer: ah, in the plug Apr 07 15:05:25 the longer ones are GND and vbus Apr 07 15:05:31