| 00:08.12 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0d9de3.pool.mediaWays.net) |
| 00:14.11 | *** join/#maemo RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net) |
| 00:18.55 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 00:24.36 | *** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au) |
| 00:25.13 | *** join/#maemo johnsu01 (johns@gateway/shell/gnu/x-nebjrnkpyvkmjxdg) |
| 00:26.44 | *** join/#maemo Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 00:32.17 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 00:47.01 | *** join/#maemo xes_ (~xes@unaffiliated/xes) |
| 01:00.23 | *** join/#maemo RES401 (Elite9109@gateway/shell/elitebnc/x-oghwwztkmevmanvq) |
| 01:17.50 | *** join/#maemo lool (~lool@debian/developer/lool) |
| 01:21.08 | *** join/#maemo florentia (~florentia@kraken.insecable.net) |
| 01:21.21 | *** join/#maemo ALoGeNo (~alogeno@198.Red-79-155-15.dynamicIP.rima-tde.net) |
| 01:21.31 | *** join/#maemo ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 01:23.18 | *** join/#maemo Mike11 (~Mike@unaffiliated/mike11) |
| 01:23.26 | Mike11 | hi everybody :) |
| 01:25.25 | Mike11 | I have a Nokia n900 which was not able to read its IMEI, and displays "All telephony functions disabled . . ." error on every boot |
| 01:25.50 | Mike11 | and when I reflash the device I used to get CMT flashing failed |
| 01:26.21 | Hurrian | Mike11: your baseband has probably fallen off the board, you can use a small spring from a ball pen to push it down |
| 01:26.33 | Mike11 | while searching for a solution , I saw something about putting springs on some ICs |
| 01:27.13 | Mike11 | yes Hurrian , but I used some papers instead if springs because I didn't expect it to work |
| 01:27.31 | Mike11 | surprisingly my phone is now able to read its IMEI |
| 01:28.53 | Mike11 | first of all, should I now remove the paper and put springs, or do you think it does not matter? |
| 01:29.34 | Mike11 | the problem now is that every boot it says "Unable to establish network connection. Contact service" |
| 01:29.47 | Hurrian | try springs, but remember it'll always be a stopgap solution |
| 01:30.04 | Mike11 | and I can't dial any number of course |
| 01:30.58 | Mike11 | when I go to settings -> phone , it freezes for a while and then displays "Cellular network not available" |
| 01:31.11 | Mike11 | I thought the software needs a reflash |
| 01:31.49 | Mike11 | so I reflashed and for the first the time it was able to erase and program the CMT |
| 01:32.05 | Mike11 | but the problem isn't gone :( |
| 01:32.08 | Mike11 | any ideas? |
| 01:32.23 | Mike11 | I feel I 'm getting close to fix my n900 |
| 01:33.01 | Mike11 | too bad if it does not get fixed after I erased everything now with the flash :( |
| 01:35.16 | *** join/#maemo tanty (~agomez@cs78210056.pp.htv.fi) |
| 01:35.29 | *** join/#maemo valeriusL (~valerius@85.26.180.176) |
| 01:36.06 | Hurrian | the problem isn't in a corrupt CMT, it's a /disconnected/ CMT |
| 01:36.42 | Mike11 | Hurrian, I don't think it is disconnected anymore |
| 01:36.56 | Mike11 | the flasher says it flashed cmt successfuly |
| 01:37.10 | Mike11 | so it was able to communicate with the CMT |
| 01:37.16 | Hurrian | if you're getting communication errors, that means your shim has loosened up, and needs to be tightened again |
| 01:37.39 | Mike11 | another thing is that I can see my IMEI when typing *#06# |
| 01:37.49 | chainsawbike | Mike11, if pressing the baseband chip down with paper "fixed" it (even partially) i would assume that it has been partially broken off the pcb, and the phone can never be relied on again for cellular communications... |
| 01:38.09 | *** join/#maemo robbiethe1st (~robbiethe@50-52-28-176.cral.id.frontiernet.net) |
| 01:38.36 | Mike11 | chainsawbike , shit ! :( |
| 01:38.48 | chainsawbike | Mike11, you may get it to work, but do not rely on it staying that way |
| 01:39.07 | robbiethe1st | What happened? |
| 01:39.11 | Mike11 | how can you tell it is broken, while it was flashed successfuly ?? |
| 01:39.24 | *** join/#maemo valerius (~user@85.26.180.176) |
| 01:39.32 | Mike11 | its memory and communications with the main board are ok |
| 01:39.46 | Mike11 | since the flasher programmed the CMT |
| 01:39.51 | Mike11 | is that right? |
| 01:39.59 | Mike11 | or I am messing things up? |
| 01:40.34 | chainsawbike | Mike11, its memory and communications with the main board partially work for now because the chip is pressed against the contacts on the pcb with the paper |
| 01:41.54 | Mike11 | so I broke my phone thinking I've fixed it :( |
| 01:42.23 | Mike11 | chainsawbike, are you sure this cannot be software only related? |
| 01:42.39 | Mike11 | maybe the flash version |
| 01:43.25 | chainsawbike | Mike11, it is a known problem probably caused by flexing of the pcb from pressing keys too hard |
| 01:44.33 | Mike11 | chainsawbike , any way to fix it? |
| 01:48.07 | chainsawbike | Mike11, not easily ( reflow? ), the paper/spring fixes should only be considered a temp fix |
| 01:51.38 | Mike11 | can't that be software related at all!?! |
| 01:52.17 | Mike11 | please anybody with any opinion about that help me , thanks for your help chainsaw :'( |
| 01:52.36 | chainsawbike | from what you have said i doubt it but a full reflash does not take that long so... |
| 01:53.20 | Mike11 | I already have did a full reflash |
| 01:53.40 | Mike11 | but thinking it might br firmware related |
| 01:53.52 | Mike11 | firmware version** |
| 01:55.14 | chainsawbike | Mike11, i assume you use the latest version? |
| 02:13.07 | *** join/#maemo qwazix (~qwazix@Maemo/community/council/qwazix) |
| 02:26.23 | *** join/#maemo amonk (~amonk@unaffiliated/amonk) |
| 02:26.48 | *** join/#maemo Defiant (erik@f054021139.adsl.alicedsl.de) |
| 02:58.55 | *** join/#maemo mschlens (~mschlens@p54936681.dip0.t-ipconnect.de) |
| 02:59.58 | *** join/#maemo paulo_ (~paulo@190.55.87.182) |
| 03:01.47 | *** join/#maemo silviof2 (~silviof@ppp-188-174-135-138.dynamic.mnet-online.de) |
| 03:14.17 | *** join/#maemo johnsu01 (johns@fsf/staff/johnsu01) |
| 03:33.27 | *** join/#maemo SAiFu (7aa6417e@gateway/web/freenode/ip.122.166.65.126) |
| 03:36.50 | *** join/#maemo ebzzry (~ebzzry@112.204.28.168) |
| 04:00.52 | *** join/#maemo lxp (~lxp@188-22-220-231.adsl.highway.telekom.at) |
| 04:02.44 | *** join/#maemo uen| (~uen@p50842914.dip0.t-ipconnect.de) |
| 04:11.51 | *** join/#maemo alien2003 (~alien@37.58.52.30) |
| 04:21.41 | *** join/#maemo amonk (~amonk@unaffiliated/amonk) |
| 04:23.51 | *** join/#maemo fortytwo (~thomas@who.let.this.bloody.dropbear.in) |
| 04:26.23 | Maxdamantus | How is touchscreen vibration normally handled? |
| 04:26.40 | Maxdamantus | is there a process that reads /dev/input/ts and emits vibrations? |
| 04:28.00 | *** join/#maemo t3st3r (~t3st3r@gateway/tor-sasl/t3st3r) |
| 04:30.03 | *** join/#maemo RES401 (Elite9109@gateway/shell/elitebnc/x-nvilwnrrrudahges) |
| 04:31.18 | *** join/#maemo maybeWTF (~cl@p5B1616D6.dip0.t-ipconnect.de) |
| 04:59.24 | *** join/#maemo fortytwo (~thomas@who.let.this.bloody.dropbear.in) |
| 05:06.16 | *** join/#maemo Psi (~Psi@49-50-247-217.a.hd.net.nz) |
| 05:18.25 | *** join/#maemo bef0rd_ (~bef0rd@186.154.137.106) |
| 05:50.48 | *** join/#maemo beford (~frod@unaffiliated/beford) |
| 05:56.43 | hxka | hildon-plugins-notify-sv, maybe? |
| 05:57.04 | hxka | Descriptions says "This package contains the sound and vibra plugins for hildon desktop notification system." |
| 05:57.20 | hxka | Maxdamantus: ^ |
| 05:58.13 | hxka | Uh, no, that's probably not related to touchscreen, sorry |
| 06:00.34 | *** join/#maemo HylianSavior (hyliandesk@HYLIANDESKTOP.RES.CMU.EDU) |
| 06:02.06 | hxka | My N900's vibrator got broken recently =| |
| 06:04.34 | *** join/#maemo protem (~protem@unaffiliated/protem) |
| 06:21.27 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 06:25.15 | *** join/#maemo LauRoman (~LauRoman@5-14-192-20.residential.rdsnet.ro) |
| 06:29.32 | *** join/#maemo jaxson (~henry@213.23.120.114) |
| 06:41.18 | hxka | Hmm, I disassebled it, found nothing wrong, and after assembling it vabators works again |
| 06:41.47 | hxka | It was wery dusty after 4 years though, maybe cleaning helped |
| 06:42.47 | hxka | And now it spopped working again |
| 06:43.00 | hxka | stopped even |
| 06:43.58 | hxka | Hmm, but when I'm swithchong N900 on, vibrator works always |
| 06:44.19 | hxka | So maybe it's something software related, strange |
| 06:45.28 | hxka | Yeah, it works a few times after boot and then stops |
| 06:48.03 | hxka | After restarting mce it works again |
| 06:50.48 | *** join/#maemo VDVsx (~VDVsx@192.194.199.34) |
| 06:57.05 | *** join/#maemo Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 06:57.09 | *** join/#maemo mvp_ (~mvp@h152.natout.aau.dk) |
| 06:59.01 | hxka | Maxdamantus: vibrate on touch is controlled by /system/osso/dsm/touchscreen_vibra_enabled gconf entry |
| 06:59.22 | hxka | Maxdamantus: which is handled by mce |
| 07:01.41 | Maxdamantus | so mce uses gconf? |
| 07:01.47 | hxka | sure |
| 07:02.19 | hxka | http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/System_Software#Mode_Control_Entity_.28MCE.29 |
| 07:02.30 | hxka | > Provides DSM gconf API for controlling display and security. |
| 07:03.10 | Maxdamantus | ") interface="com.nokia.mce.request" member="req_vibrator_pattern_activate" error name="(uns Feb 27 20:02:07 Nokia-N900 auth.notice dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=29999 pid=1043 comm="/usr/bin/maemo-xinput-sounds |
| 07:04.13 | Maxdamantus | wonders how to interpret these dbus messages in syslog |
| 07:06.27 | Maxdamantus | I think mce receives the request to vibrate from something else. |
| 07:08.32 | hxka | I can reproduce it: after boot vibrator works only for a short period of time, after which it stops until I restart mce, then it works fine until next boot |
| 07:10.21 | hxka | I missed a call a couple of times because of that |
| 07:12.31 | Maxdamantus | # echo 255 80 > /sys/class/i2c-adapter/i2c-1/1-0048/twl4030_vibra/pulse |
| 07:12.52 | Maxdamantus | can see mce doing that when something successfully makes it vibrate. |
| 07:13.33 | Maxdamantus | so it must be something else that's trying to send those messages to mce, but failing for some reason. |
| 07:13.38 | Maxdamantus | (being rejected) |
| 07:14.20 | *** join/#maemo LauRoman (~LauRoman@5-14-192-20.residential.rdsnet.ro) |
| 07:14.36 | Maxdamantus | ah, it's maemo-xinput-sounds |
| 07:15.20 | Maxdamantus | works on restarting that. |
| 07:15.38 | Maxdamantus | doesn't know much about dbus or gconf. |
| 07:17.13 | Maxdamantus | and yeah, regarding your thing, I've heard of people removing the lint from the vibrator to get it to work again. |
| 07:17.41 | Maxdamantus | wonder if my (second-hand) device's vibrator is weak because of that. |
| 07:18.28 | Maxdamantus | if I've got it constantly pulsing, it will skip a few sometimes if I move it. |
| 07:18.32 | hxka | Maxdamantus: it works flawlessly after I restart mce |
| 07:18.36 | Maxdamantus | and overall, I find it really difficult to notice in my pocket. |
| 07:18.56 | Maxdamantus | but maybe it's just naturally weak. |
| 07:22.42 | *** join/#maemo tanty (~agomez@cs78210056.pp.htv.fi) |
| 07:33.06 | hxka | It seems like yandexmail is causing my problem |
| 07:36.02 | hxka | http://maemo.su/forum/viewtopic.php?pid=73390#p73390 Yeah |
| 07:36.14 | hxka | Removing that crap |
| 07:45.07 | *** join/#maemo MikaT (~mtapoja@projects.sse.fi) |
| 07:56.13 | *** join/#maemo fortytwo (~thomas@who.let.this.bloody.dropbear.in) |
| 08:02.57 | *** join/#maemo norayr (~noch@212.73.74.28) |
| 08:05.27 | *** join/#maemo Milhouse (~Milhouse@Maemo/community/contributor/Milhouse) |
| 08:10.39 | Mike11 | is the latest official firmware for nokia n900 "RX-51_2009SE_20.2010.36-2.003_PR_COMBINED_003_ARM" |
| 08:10.43 | Mike11 | ??? |
| 08:10.43 | *** join/#maemo saif (~saif@117.217.130.196) |
| 08:11.37 | hxka | Yeah, officially |
| 08:12.16 | hxka | Though yours is fo '003' region |
| 08:13.13 | hxka | There is RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin, which exists on Nokia servers but wasn't officially released |
| 08:14.06 | Mike11 | hxka, here is my situation, any help is really appreciated :( |
| 08:14.34 | Mike11 | my nokia n900 was having the error "all telephony functions . . ." |
| 08:15.06 | Mike11 | and when I flash, it used to say "CMT flashing failed" |
| 08:15.41 | Mike11 | until yesterday, I saw that spring fix, and put some paper where I should put the springs |
| 08:15.44 | hxka | I've read about your problem, no need to rehearse |
| 08:16.10 | Mike11 | hxka sorry for re-posting I thought you weren't here |
| 08:16.12 | hxka | If you need to put paper, that means cmt is not connected properly anymore |
| 08:17.00 | hxka | That it flashes correctly now doesn't mean it will work correctly as well |
| 08:17.21 | Mike11 | why springs connect CMT better than paper, isn't it about pressure only? |
| 08:18.36 | hxka | Maybe spring applies more pressure, I don't know? have you tried it? |
| 08:18.58 | hxka | Maybe applying pressure is not enough in your case |
| 08:19.17 | Mike11 | hxka, actually no, brcause I am afraid I've broken the whole PCB, as someone here suggested |
| 08:20.26 | Mike11 | but I saw people having the error I'm talking about because of installing a firmware older than a firmware that was installed |
| 08:21.02 | Mike11 | that's why I am thinking of installing that latest unofficial firmware |
| 08:21.04 | hxka | "RX-51_2009SE_20.2010.36-2.003_PR_COMBINED_003_ARM" contains latest cmt |
| 08:21.45 | hxka | That update contains only ssl security fix, no cmt flash update |
| 08:21.51 | Mike11 | hxka, so you think there is no sense in trying "RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin" ?? |
| 08:22.13 | hxka | Yeah, I don't think it'll help |
| 08:32.43 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:35.45 | *** join/#maemo RES401 (Elite9109@gateway/shell/elitebnc/x-vflrinfyyjbxlaxa) |
| 08:42.52 | *** join/#maemo Ariadeno (~Ariadeno@145.93.64.219) |
| 08:48.13 | *** join/#maemo jmlich (jmlich@nat/redhat/x-xykakwcaokiikdot) |
| 08:52.12 | *** join/#maemo jas4711 (~jas@2001:16d8:cca1:0:f2de:f1ff:fe16:509b) |
| 09:00.38 | *** join/#maemo Kabouik (~quassel@147.99.218.243) |
| 09:03.45 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 09:19.32 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 09:21.27 | *** join/#maemo OkropNick (~OkropNick@host-n2-75-80.telpol.net.pl) |
| 09:24.27 | DocScrutinizer05 | I think flashing global version won't hurt. It's a known effect that some rare instances a certain localized variant won't flash |
| 09:32.44 | *** join/#maemo ccxN (~ccxCZ@asterix.te2000.cz) |
| 09:41.21 | DocScrutinizer05 | Mike11: when your modem chipset is able to talk to Application Processor Environment (APE, aka linux) then you maybe can readout IMEI and flash new firmware etc, but it still may suffer from further contact problems on RF aka antenna side. Does it ask for PIN and accept the PIN you enter? |
| 09:43.11 | *** join/#maemo norayr (~noch@212.73.74.28) |
| 09:43.40 | *** join/#maemo Gatta_Negra (~SailCat@89.190.196.121) |
| 09:45.15 | DocScrutinizer05 | modem chipset consists of several (at least 3) chips, one of them for RF and TX amps, while the hugest one is mainly so called baseband chip that talks to APE, and second hugest one is "the power supply" that also might be partially detached from PCB and thus not powering the TX amps in 3rd chip. When baseband works but RF side has a problem, you will see exactly the symptom you described |
| 09:45.42 | DocScrutinizer05 | your paper fix might have worked for hugest chip but failed for smaller one |
| 09:45.49 | *** join/#maemo N-Mi (~nicolas@78.205.5.80) |
| 09:45.49 | *** join/#maemo N-Mi (~nicolas@calvix/staff/N-Mi) |
| 09:49.33 | DocScrutinizer05 | dang, some user in this channel planned to do a reflow in baking oven, to fix cmt. I wonder what became of that plan |
| 09:51.43 | peetah | DocScrutinizer05: you mean put the board in a classic oven ? if it may reconnect some connections, can't it also disconnect others ? |
| 09:51.59 | peetah | it seems very risky to me |
| 09:53.48 | DocScrutinizer05 | yes, this is risky |
| 09:53.59 | peetah | my n900 also has this problem, but I'd rather keep a computer without a modem waiting for neo900 than a definitive brick |
| 09:54.11 | DocScrutinizer05 | sure |
| 09:54.35 | DocScrutinizer05 | I didn't recommend doing that oven reflow thing |
| 09:55.32 | DocScrutinizer05 | there's a number of "manually" soldered parts on N900 PCB which possibly don't tolerate reflow process |
| 09:55.42 | DocScrutinizer05 | at least could be |
| 09:55.57 | *** join/#maemo valeriusL (~valerius@85.26.180.135) |
| 09:57.08 | DocScrutinizer05 | and the process temperature margin between successful reflow of lead-free solder and max allowable temperature for chips is quite small |
| 09:58.11 | DocScrutinizer05 | something in the range 240°C .. 280°C. Below that the leadfree solder won't melt, above the chips will die |
| 10:01.56 | peetah | I wanted to try the springs, but I was not able to safely open the 'metal cage' surrounding the chips: to afraid to break something important |
| 10:02.46 | *** join/#maemo valerius (~user@85.26.180.135) |
| 10:03.47 | DocScrutinizer05 | opening the cans is difficult but not really dangerous. Just make sure you don't apply forces to components nearby outside the cans |
| 10:04.31 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 10:04.32 | DocScrutinizer05 | I wonder how industry/commercial does it |
| 10:05.03 | DocScrutinizer05 | probably there must be a special tool for opening can / lifting the lid |
| 10:06.26 | peetah | but do these cans have to be closed for the modem to be functional, because as you say, once opened, I don't see how to put them back nicely |
| 10:06.51 | DocScrutinizer05 | they are not extremely critical |
| 10:07.09 | peetah | is this some kind of faraday cage ? |
| 10:07.11 | DocScrutinizer05 | IOW your device will work without lids on cans |
| 10:07.16 | DocScrutinizer05 | yes |
| 10:08.34 | DocScrutinizer05 | ut putting lids back on is not difficult at all |
| 10:09.07 | DocScrutinizer05 | when you haven't destroyed the lids completely during removal |
| 10:09.57 | DocScrutinizer05 | the lifting is pure ZEN and takes maybe 10 to 20 minutes for first lid you are lifting |
| 10:10.30 | DocScrutinizer05 | like building a house of cards |
| 10:13.13 | peetah | so patience and precision ... I should definitely stay away from them :) |
| 10:14.08 | *** join/#maemo ArGGu^^ (~ArGGu^^@85-76-174-155-nat.elisa-mobile.fi) |
| 10:15.28 | DocScrutinizer05 | you start at one corner, ideally one with long sides left and right, and lift 1. dent left, 1. r, 2.l, 2.r, 1.l again since it snapped closed again, 2.l, 2.r, 3.r, 2.l, 3.r, 1.l, 1.r, 1+2.l, 1..3.r, and so on and on, 10 minutes, until finally the one corner comes off visibly a 0.2mm and on maybe 5mm distance left and right from corner. Then you've won the battle |
| 10:18.13 | DocScrutinizer05 | you need a pretty sturdy pinpoint instrument for that, like a tiny knife, dentist tool, very small screwdriver with sharp blade... |
| 10:18.52 | DocScrutinizer05 | I'm sure there are more easy ways to open lids, but I don't know of them (yet?) |
| 10:21.23 | *** join/#maemo qwazix (~qwazix@Maemo/community/council/qwazix) |
| 10:30.48 | DocScrutinizer05 | the latches/dents go down to the PCB rather close, so to gut under them, you need a really pinpointed tool. For me small knife of a tiny swiss army knife (~3cm length) worked best |
| 10:33.46 | DocScrutinizer05 | I bet nokia service manual suggests something like a can opener and then discarding the lids and use new spare parts |
| 10:33.56 | DocScrutinizer05 | ;-) |
| 10:34.12 | jaska | like for the screws and such |
| 10:34.31 | DocScrutinizer05 | yep |
| 10:37.12 | DocScrutinizer05 | alas those tiny cheesy metal parts are terribly expensive to produce, regarding initial tooling expense etc. Once you got all tooling, the lid costs a cent or less |
| 10:39.33 | DocScrutinizer05 | again exactly like the screws |
| 10:40.01 | DocScrutinizer05 | figure you'd want to build a screw by yurself, DIY |
| 10:42.23 | DocScrutinizer05 | most people don't understand such aspects of building a device. They only see 5g plastic when they look at e.g. Jolla TOH and say "duh, this can't cost more than 5ct! it#s just a tiny amount of plastic" |
| 10:43.40 | DocScrutinizer05 | or "there are 10 screws holding that part, can't cost more than 1ct to replace them" - yeah sure, IF the scres are standard size somebody builds by the billion qty |
| 10:44.07 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 10:44.24 | *** join/#maemo sledges (~sledges@unaffiliated/sledgeas) |
| 10:44.49 | DocScrutinizer05 | they can't imagine that building 100 matching screws might cost you 1000bucks |
| 10:45.30 | DocScrutinizer05 | or more |
| 10:46.31 | DocScrutinizer05 | building 10 screws might not be significantly cheaper |
| 10:46.42 | DocScrutinizer05 | maybe 500 |
| 10:47.16 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 10:54.22 | ShadowJK_ | occasionally makes own screws |
| 10:54.37 | DocScrutinizer05 | now for building prototypes this becomes "interesting" question: do you build 10 screws for one proto, costs you 500. Or do you expend 1000 bucks for 100 screws, and maybe find that you bought 90 "lemons" worth 500 bucks and just ready to discard them right away |
| 10:55.59 | DocScrutinizer05 | ShadowJK_: for sure a funny exercise |
| 10:56.04 | ShadowJK_ | but not small ones. and they don't have to look good or have exactly shaped head |
| 10:56.22 | DocScrutinizer05 | how do you make the thread? |
| 10:56.54 | DocScrutinizer05 | making thread is a really demanding task |
| 10:57.35 | DocScrutinizer05 | nowadays you can do that with CNC maybe |
| 11:03.10 | *** join/#maemo lizardo (lizardo@nat/indt/x-qycviyfczmttiewj) |
| 11:12.43 | DocScrutinizer05 | commonly used large scale method is to roll the thread into the screw with two plates of hardened steel |
| 11:13.51 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 11:14.46 | DocScrutinizer05 | or you already cold-deform raw steel rods in a mold that has the thread and all except the slot(s) in head |
| 11:15.41 | DocScrutinizer05 | I think spax and wood screws are made like this |
| 11:17.55 | DocScrutinizer05 | http://www.spaxi.de/2_entstehung.php?mainClick=2&subClick=1&subChild=2#mainWindow |
| 11:19.57 | DocScrutinizer05 | ooh, they are rolled as well: http://www.spaxi.de/4_entstehung.php?mainClick=2&subClick=1&subChild=4 |
| 11:21.33 | DocScrutinizer05 | https://www.youtube.com/watch?v=7DgqA3GKFog |
| 11:24.46 | r00t|d430 | i have a "spax" at home which has the slots but the thread is missing |
| 11:27.08 | *** join/#maemo pcfe (~pcfe@29-227.197-178.cust.bluewin.ch) |
| 11:27.20 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 11:28.02 | DocScrutinizer05 | hehe |
| 11:29.27 | DocScrutinizer05 | r00t|d430: did you consider grabbing your files and file a thread into it manually? ;-) |
| 11:30.10 | r00t|d430 | DocScrutinizer05: filing won't do... the diameter is too small, at least for getting the thread it would normally have |
| 11:30.19 | DocScrutinizer05 | yeah |
| 11:31.01 | DocScrutinizer05 | cold-deforming moves the material from inside the thread to beyond the diameter of the wire |
| 11:31.53 | DocScrutinizer05 | no material gets lost in rolling/cold-forming. So filing is doomed to fail, you remove material you would need |
| 11:32.16 | r00t|d430 | well, could still make a smaller thread that way |
| 11:32.38 | DocScrutinizer05 | yes, during 2 years of weekend leisure work ;-) |
| 11:33.18 | r00t|d430 | production errors are always fun... i also found a dowel screw at a shop once that was missing the metric thread... http://en.wikipedia.org/wiki/File:Stockschraube.jpg |
| 11:33.38 | DocScrutinizer05 | there arre guys who build whole steam engines 20mm max dimension |
| 11:34.13 | DocScrutinizer05 | well, there are also clockworkers |
| 11:34.22 | DocScrutinizer05 | makers? |
| 11:36.53 | DocScrutinizer05 | bottom line: you can build incredibly cheap yet sophisticated stuff, when you get incredibly expensive and sophisticated "tools" (aka machines) for doing so |
| 11:37.40 | DocScrutinizer05 | bottom line 2: even something as "simple2 as a screw is suprisingly hard to build DIY |
| 11:38.42 | r00t|d430 | could still avoid using non-standard parts |
| 11:38.51 | *** join/#maemo vi__ (~psleggs@146.255.2.70) |
| 11:39.04 | vi__ | freemangordon: hello? |
| 11:39.05 | DocScrutinizer05 | always giggles when somebody boldly demands FOSS chip manufacturing |
| 11:39.10 | r00t|d430 | http://blogs.theguardian.com/technology/sony_screw.jpg |
| 11:39.37 | vi__ | DocScrutinizer05: No Problem, I will just fire up the semi conductor fab in my garage. |
| 11:40.15 | DocScrutinizer05 | r00t|d430: dang, what currency? |
| 11:40.35 | vi__ | r00t|home: It does say it is a special screw. Perhaps it has a really wacky non standard thread or is made from a special material./ |
| 11:40.38 | r00t|d430 | dunno... the picture is old... http://www.theguardian.com/technology/blog/2007/may/28/sonyuserscrew |
| 11:40.38 | DocScrutinizer05 | vi__: exactly |
| 11:41.11 | vi__ | Where is FMG at? |
| 11:41.30 | DocScrutinizer05 | dunno. Dayjob? |
| 11:41.39 | *** join/#maemo jormungandr (~xxx@213.23.120.114) |
| 11:42.32 | DocScrutinizer05 | 61 EURO!!!! GODDAMN! |
| 11:43.28 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 11:44.00 | vi__ | It is a *SPECIAL* screw. |
| 11:44.32 | vi__ | Although the fact it is a self tapping screw implies you could be quite liberal with the specs on a replacement part. |
| 11:44.57 | r00t|d430 | they had to custom-make it on a cnc-mill... 61eur is CHEAP! |
| 11:45.25 | vi__ | I heard it was cast from NASA grade bitcoins. |
| 11:47.09 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 11:49.19 | *** join/#maemo shentey (~shentey@141.23.77.78) |
| 11:56.06 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 11:57.34 | *** join/#maemo t3st3r (~t3st3r@gateway/tor-sasl/t3st3r) |
| 12:01.51 | jaska | hammered with hassium-core hammers |
| 12:03.39 | *** join/#maemo triggerhappy (~quassel@112.209.84.234) |
| 12:07.11 | *** join/#maemo norayr (~noch@212.73.74.28) |
| 12:08.42 | *** join/#maemo jon_y (~enforcer@2001:e68:4052:eb7d:e01f:8e6d:cdca:d0e5) |
| 12:20.57 | *** join/#maemo xjiujiu (~xjiujiu@218.77.14.202) |
| 12:29.31 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 12:36.37 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 12:41.35 | *** join/#maemo shentey (~shentey@141.23.77.78) |
| 12:49.10 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 12:50.03 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 12:53.15 | *** join/#maemo cypherc (~user@static.ip-80-255-245-177.signet.nl) |
| 12:57.52 | *** join/#maemo Anz_ (~Anz_@korn92.bitnet.nu) |
| 12:58.01 | Maxdamantus | wonders what normally makes dbus allow user's applications to talk to mce in Maemo. |
| 12:58.45 | Maxdamantus | when partially starting up stuff myself, they're rejected, which seems to make sense based on /etc/dbus-1/system.d/mce.conf |
| 12:59.23 | Maxdamantus | if I modify that file to say "user" is allowed to send messages to the mce interface, it works. |
| 12:59.51 | Maxdamantus | but why does it work normally without that rule? |
| 13:01.50 | *** join/#maemo Elleo (~Elleo@libre.fm/hacker/elleo) |
| 13:03.43 | *** join/#maemo ArGGu^^ (~ArGGu^^@85-76-42-161-nat.elisa-mobile.fi) |
| 13:07.01 | *** join/#maemo shentey_ (~shentey@wlan-141-23-77-78.tubit.tu-berlin.de) |
| 13:22.06 | *** join/#maemo LjL (~ljl@93-32-49-69.ip32.fastwebnet.it) |
| 13:22.23 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 13:28.30 | *** join/#maemo esaym153 (~esaym153@216-45-91-132.gvec.net) |
| 13:32.24 | *** join/#maemo Venusaur (~wdwrf@wikipedia/Antonio-Lopez) |
| 13:47.47 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 13:52.16 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 14:08.46 | *** join/#maemo wmarone_ (~wmarone@c-24-10-24-149.hsd1.ca.comcast.net) |
| 14:11.18 | DocScrutinizer05 | system vs session bus? run-standalone.sh? |
| 14:11.59 | DocScrutinizer05 | I don't think I heard about any problems of userland apps talking to mce |
| 14:13.23 | *** join/#maemo saif (~saif@117.217.134.105) |
| 14:13.54 | *** join/#maemo MMN-o (~mmn@ip3-179.bon.riksnet.se) |
| 14:19.19 | DocScrutinizer05 | or maybe userland processes escalate permissions via sudo prior to sending stuff to mce? |
| 14:19.49 | *** join/#maemo alien2003 (~alien@37.58.52.30) |
| 14:20.33 | DocScrutinizer05 | thinking about it, user "user" sjould only have write access on session buss, not on system bus, no? |
| 14:21.54 | DocScrutinizer05 | since system bus affects all system (as the name implies), it should be restricted to superusers. Otherwise one user could cause havoc for other concurrent user |
| 14:22.41 | DocScrutinizer05 | same rationale applies to file permissions in /dev/ and /sys/ |
| 14:27.55 | DocScrutinizer05 | so, depending on the particular function and the way it's implemented in mce or whatever, the function should either be systembus and exclusively for root/superuser, or mce implements arbitrating and offers e.g. a "I'm fine with shutdown" function on session buss(es) where real system shutdown only happens when all users allowed it. You can come up with arbitrary number of similar designs to rule who may do what, the principle stays the |
| 14:27.57 | DocScrutinizer05 | same |
| 14:29.51 | DocScrutinizer05 | basically this all are partial aspects of "resource arbitration" topic |
| 14:31.43 | DocScrutinizer05 | mce is a classicla "middleware" that's responsible of arbitrating/allocating/distributing/assigning resources of all kinds |
| 14:31.53 | DocScrutinizer05 | classical* even |
| 14:34.07 | DocScrutinizer05 | simple example: diable scree dimming. When one task is asking mce to keep screen active, then a 2nd task does same, then 1, tasks says "ok i'm done, you may dim screen now"... MCE shall know about second task still needing screen undimmed |
| 14:35.52 | DocScrutinizer05 | actually currently this is implemented in a even smarter way, where every task has a lease in screen backlight resource, and that lease needs renewal every few seconds. Only when all tasks stop renewing their leases, a few seconds later screen dims |
| 14:41.26 | *** join/#maemo qwazix (~qwazix@78-14-177.static.cyta.gr) |
| 14:41.33 | *** join/#maemo qwazix (~qwazix@Maemo/community/council/qwazix) |
| 14:52.06 | DocScrutinizer05 | (system shutdown) you could argue that a user who wants to shutdown the system first should shutdown own session. Thus any such system-shutdown would most likely get implemented into the session bus itself and the tear-down of that particular session bus. When all session busses are stopped/terminated, mce knows there's no more user session running and thus can consider whether or not system should get shut down. Depending on info the |
| 14:52.07 | DocScrutinizer05 | sessions told mce before terminating. A session might just want to restart itself. Anyway such function would obviously best get integrated into hildon desktop since HD basically establishes the user session |
| 14:56.58 | DocScrutinizer05 | btw same principle also applies to sensors. Particularly those who have different operation modes and maybe even triggers. Think accelerometer. Think liblocation. |
| 14:58.04 | DocScrutinizer05 | modem is a very special case, since it's not clearly defined if e.g. an imbound call belongs to system, to currently active user session, or even to all user sessions. |
| 14:59.44 | DocScrutinizer05 | other exclusive resurces like e.g. camera are simpler, since you basically can handle them on a first-come-first-serve basis |
| 15:00.51 | DocScrutinizer05 | for that often a devnode or sysnode has sufficient "arbitration" simply by locking |
| 15:11.22 | DocScrutinizer05 | ideally all sys and dev nodes (where needed) would come in a user exclusive namespace, and the drivers would do arbitration. Thus every user session could behave like it was the only one on that machine, and when a resource is not available, then the according device node (or sysnode) would reject an open() with an appropriate -Error |
| 15:12.20 | *** join/#maemo LinuxCode (~LinuxCode@fedora/LinuxCode) |
| 15:12.35 | *** join/#maemo fortytwo (~thomas@who.let.this.bloody.dropbear.in) |
| 15:12.35 | DocScrutinizer05 | sometimes not the open() but a write() - when e.g a write to a configuration node collides with something another concurrent user already had configured |
| 15:13.32 | DocScrutinizer05 | but afaik none of the mainline kernel drives is designed that way |
| 15:14.39 | DocScrutinizer05 | maybe in plan9 ;-) |
| 15:15.00 | *** join/#maemo Mek_ (~quassel@kde/mkruisselbrink) |
| 15:15.08 | DocScrutinizer05 | (haven't looked into it regarding this detail) |
| 15:16.07 | DocScrutinizer05 | so for "standard linux" we're back to proper middleware |
| 15:16.17 | DocScrutinizer05 | ~fso |
| 15:16.17 | infobot | well, fso is the freesmartphone.org mobile devices middleware. |
| 15:16.37 | *** join/#maemo drathir87 (~kamiljk8@s51.linuxpl.com) |
| 15:16.43 | *** join/#maemo Hakki_ (~hakki@ip212-226-155-81.adsl.kpnqwest.fi) |
| 15:18.09 | DocScrutinizer05 | ~fso is also http://www.freesmartphone.org// |
| 15:18.09 | infobot | okay, DocScrutinizer05 |
| 15:21.03 | *** join/#maemo netkat_ (~me@80.79.126.176) |
| 15:22.57 | DocScrutinizer05 | WTF?! MICKEY!! maemo is no "foreign environment"! maemo is plain GNU/linux for all that matters to FSO |
| 15:23.03 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 15:24.04 | DocScrutinizer05 | for sure maemo is not same class of "foreign" that has mambers like android and webOS |
| 15:24.13 | DocScrutinizer05 | members* |
| 15:24.16 | *** join/#maemo jon_y (~enforcer@2001:e68:4053:6823:e01f:8e6d:cdca:d0e5) |
| 15:24.41 | *** join/#maemo StyXman (~mdione@grulic/root/StyXman) |
| 15:27.14 | *** join/#maemo alien2003 (~alien@37.58.52.30) |
| 15:28.25 | *** join/#maemo FlameReaper (~assassin@115.132.144.223) |
| 15:28.28 | *** join/#maemo silviof (~silviof@unaffiliated/silviof) |
| 15:28.37 | *** join/#maemo andre__ (~andre__@wikimedia/aklapper) |
| 15:29.00 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0d9de3.pool.mediaWays.net) |
| 15:32.06 | *** join/#maemo lizardo (lizardo@nat/indt/session) |
| 15:32.07 | *** join/#maemo lizardo (lizardo@nat/indt/x-qrqfzznxltmfvopn) |
| 15:35.18 | RES401 | would this be the right place to ask about getting metasploit running properly? and yes i have googled but can't find the error that im getting |
| 15:36.24 | *** join/#maemo hxka (~hxka@95-25-102-159.broadband.corbina.ru) |
| 15:38.54 | DocScrutinizer05 | yes, I think it's an appropriate place to ask |
| 15:39.36 | DocScrutinizer05 | (assuming metasploit is a maemo app) |
| 15:41.15 | DocScrutinizer05 | possibly an incorrect assumption |
| 15:41.41 | vi__ | RES401: Easy answer, just run it through easy Debian. |
| 15:41.47 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?t=81816 |
| 15:43.52 | RES401 | ok tahnks. When i attempt to start metasploit I get/home/opt/msf3/lib/gemcache/ruby/1.9.1/gems/activesupport-3.2.2/lib/active_support/inflector/methods.rb:218:in 'const_defined?': wrong constant name #<Module:0x421ec540> (NameError) |
| 15:44.31 | RES401 | Easy answer, just run it through easy Debian, you mean in a debian chroot? |
| 15:45.29 | *** join/#maemo shentey (~shentey@wlan-141-23-77-78.tubit.tu-berlin.de) |
| 15:45.57 | vi__ | RES401: Yeah. |
| 15:46.00 | vi__ | Chroot. |
| 15:46.17 | *** join/#maemo ruskie (ruskie@sourcemage/mage/ruskie) |
| 15:46.39 | RES401 | would i have to install it in the chroot first? |
| 15:47.02 | vi__ | There is a debian chroot available. |
| 15:47.13 | vi__ | So it would simply be a case of apt-get install. |
| 15:47.25 | vi__ | Being all nice and debian, it should just work. |
| 15:48.04 | RES401 | ok i'll give that a try, thanks |
| 15:55.14 | *** join/#maemo Wulfe (~ninja@74.61.222.224) |
| 15:55.14 | *** join/#maemo Wulfe (~ninja@unaffiliated/wulfe) |
| 15:58.18 | DocScrutinizer05 | HMMMs at http://cdimage.kali.org/kali-latest/armel/kali-linux-1.0.6-armel.img.xz |
| 16:00.36 | DocScrutinizer05 | hi vi__ |
| 16:07.57 | DocScrutinizer05 | wtf .xz? |
| 16:11.51 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 16:16.41 | *** join/#maemo ccxN (~ccxCZ@156.200.broadband11.iol.cz) |
| 16:20.52 | *** join/#maemo louisdk (~louis@static-5-103-130-65.seas-nve.net) |
| 16:25.36 | *** join/#maemo Jo2006 (~jo@p5DC0D1EC.dip0.t-ipconnect.de) |
| 16:28.17 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 16:32.33 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 16:34.03 | *** join/#maemo alien2003 (~alien@46.165.208.194) |
| 16:46.57 | *** join/#maemo sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
| 16:47.58 | *** join/#maemo Anz_ (~Anz_@korn92.bitnet.nu) |
| 16:49.37 | *** join/#maemo ccxN (~ccxCZ@156.200.broadband11.iol.cz) |
| 16:54.20 | honestly | so apparently my emmc is just fucked :/ |
| 16:54.35 | honestly | is there a way to boot from the nand flash? |
| 16:54.45 | honestly | or rather, not have the rootfs on the emmc |
| 16:57.26 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 16:59.42 | DocScrutinizer05 | yes |
| 17:01.01 | DocScrutinizer05 | we did this maybe a year ago, online in this channel. In the end it been a one char patch, commenting out the renaming that swaps MMC1 and MMC0 |
| 17:02.34 | freemangordon | vi__: hi! how's UI coding going on? |
| 17:02.49 | honestly | DocScrutinizer05: cool |
| 17:03.08 | honestly | DocScrutinizer05: is there any documentation of this process? |
| 17:03.42 | *** join/#maemo NIN101 (~core@n900.quitesimple.org) |
| 17:06.02 | honestly | reflashing worked without any trouble at all |
| 17:06.05 | vi__ | freemangordon: Heh, I got a new job since then. |
| 17:06.16 | freemangordon | cool |
| 17:06.16 | honestly | but I'd rather not have to reflash every time I turn the phone off :/ |
| 17:06.57 | freemangordon | honestly: wait, how did you decide your emmc is broken if you are able to boot after a reflash? |
| 17:07.10 | honestly | no |
| 17:07.11 | freemangordon | vi__: is it better than the old one? I guess so |
| 17:07.21 | honestly | I decided my emmc is broken after a lot of debugging |
| 17:07.23 | vi__ | It is the greatest job evr. |
| 17:07.34 | freemangordon | honestly: did you reflash emmc too? |
| 17:07.40 | freemangordon | vi__: great |
| 17:07.42 | honestly | yes |
| 17:07.55 | honestly | reflashing emmc was the step that revived the phone in the first place |
| 17:08.04 | honestly | I think you were there for most of it, a week ago or so |
| 17:08.08 | freemangordon | honestly: by following the wiki procedure ? |
| 17:08.12 | honestly | yes |
| 17:08.18 | freemangordon | oh, I remember now |
| 17:08.41 | honestly | flashing vanilla first, and then flashing PR1.3 over it immediately |
| 17:08.50 | freemangordon | yeah |
| 17:08.54 | freemangordon | so, what happened? |
| 17:09.08 | honestly | well I let it sit turned off for a few days |
| 17:09.27 | honestly | turned it on again today and only got to the "flashing lights forever" again |
| 17:10.03 | freemangordon | hmm, wasn't your NAND faulty, not emmc? |
| 17:10.18 | honestly | err |
| 17:10.22 | honestly | I might be confusing those two? |
| 17:10.33 | freemangordon | can't remember, sorry |
| 17:10.40 | honestly | lemme see if I can find the old logs |
| 17:10.50 | freemangordon | was it you to post dmesg logs? |
| 17:11.06 | honestly | yeah |
| 17:11.06 | freemangordon | vi__: what kind of job, EE? |
| 17:11.40 | freemangordon | IIRC it is your NAND that is broken, not emmc. |
| 17:11.56 | honestly | http://ix.io/au2 |
| 17:11.59 | vi__ | freemangordon: yes, EE! |
| 17:12.05 | vi__ | freemangordon: read your PM. |
| 17:12.45 | honestly | I think that says it found bad blocks on the NAND |
| 17:12.58 | freemangordon | vi__: hmm, no PM to read :) |
| 17:13.03 | vi__ | eh? |
| 17:13.15 | vi__ | I meant irc /query |
| 17:18.17 | freemangordon | honestly: try a couple of flashes, that might mark all bad blocks and fix your problems |
| 17:19.16 | *** join/#maemo cypherc (~user@f212009.upc-f.chello.nl) |
| 17:22.51 | *** join/#maemo VDVsx (~VDVsx@a88-114-88-95.elisa-laajakaista.fi) |
| 17:26.05 | *** join/#maemo HylianSavior (~hyliandes@HYLIANDESKTOP.RES.CMU.EDU) |
| 17:26.56 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 17:33.09 | *** part/#maemo vi__ (~psleggs@146.255.2.70) |
| 17:57.08 | sixwheeledbeast | freemangordon: any clues on how to reproduce that bug in h-d from cssu-devel yet? I can't seem to reproduce at all. |
| 18:06.25 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 18:07.21 | freemangordon | sixwheeledbeast: no idea :( |
| 18:08.23 | freemangordon | sixwheeledbeast: if we find a way to reproduce it, we'll easily find the problematic code by bisecting |
| 18:08.34 | hxka | What bug? |
| 18:08.47 | sixwheeledbeast | freemangordon: mmm, I keep playing and let you know if I can reproduce anything. |
| 18:08.52 | freemangordon | ok |
| 18:09.55 | sixwheeledbeast | hxka: http://talk.maemo.org/showpost.php?p=1414487&postcount=322 |
| 18:10.13 | freemangordon | sixwheeledbeast: what about these instructions http://talk.maemo.org/showpost.php?p=1414482&postcount=320 ? |
| 18:10.21 | hxka | Oh, I encountered it a lot |
| 18:10.33 | freemangordon | hxka: how to reproduce? |
| 18:10.43 | hxka | Since the beginning of portait launcher |
| 18:10.45 | hxka | no idea |
| 18:10.53 | freemangordon | BTW I think this is #maemo-ssu material |
| 18:11.09 | sixwheeledbeast | They're the instructions I have been trying |
| 18:11.56 | freemangordon | oh, just reproduced it :) |
| 18:12.09 | freemangordon | by using them |
| 18:13.40 | freemangordon | very easy to reproduce, I'll try to fix it if arcean don't do it till saturday :) |
| 18:18.41 | *** join/#maemo Kabouik (~quassel@85.154.92.79.rev.sfr.net) |
| 18:29.48 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 18:40.58 | *** join/#maemo SmilyOrg (Smily@BSN-143-41-36.dial-up.dsl.siol.net) |
| 18:49.20 | *** join/#maemo dos11 (~dos@unaffiliated/dos1) |
| 19:00.56 | *** join/#maemo RES401 (Elite9109@gateway/shell/elitebnc/x-yglxvkaxgicbokmm) |
| 19:01.03 | *** join/#maemo apuvai (72824099@gateway/web/freenode/ip.114.130.64.153) |
| 19:11.40 | *** join/#maemo arcean (~arcean@apn-46-76-90-115.dynamic.gprs.plus.pl) |
| 19:14.02 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 19:36.47 | *** join/#maemo peterbjornx_n900 (~user@524A9150.cm-4-3c.dynamic.ziggo.nl) |
| 19:37.44 | alien2003 | can somebody compile RetroShare or RetroMessenger for maemo 5? |
| 19:43.05 | *** join/#maemo vakkov (~vakko@79.132.28.147) |
| 19:44.23 | *** join/#maemo sequantz (~sequantz@194.11.24.44) |
| 19:48.12 | *** join/#maemo florian (~fuchs@sign-4d0942e8.pool.mediaWays.net) |
| 19:48.12 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:50.01 | *** join/#maemo lbt (~david@Maemo/community/contributor/lbt) |
| 19:51.05 | *** join/#maemo mvp_ (~mvp@port463.ds1-abc.adsl.cybercity.dk) |
| 19:51.22 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 19:51.52 | *** join/#maemo fuz_ (nobody@vau75-10-88-164-23-88.fbx.proxad.net) |
| 19:53.00 | *** join/#maemo Venemo (~Timur@fedora/Venemo) |
| 20:11.24 | *** join/#maemo sq-one (~sq-one@p549AB079.dip0.t-ipconnect.de) |
| 20:17.16 | *** join/#maemo konelix (~konelix@186.151.29.95) |
| 20:24.45 | *** join/#maemo thomasjfox (~thomasjfo@rockbox/developer/thomasjfox) |
| 20:25.06 | *** part/#maemo antithesis (antithesis@5.44.97.38) |
| 20:27.03 | *** join/#maemo valeriusL (~valerius@85.26.180.161) |
| 20:29.22 | *** join/#maemo valerius (~user@85.26.180.161) |
| 20:38.33 | *** join/#maemo CR0W (foo@unaffiliated/em64t) |
| 20:40.59 | CR0W | Hello. I just bought an N900 (used) and wanted to flash it clean. I found a page with images, subpage of mrcrab.net. However, I only wound a binary file with COMBINED. Where can I find the eMMC/VANILA one? |
| 20:41.19 | hxka | ~emmc |
| 20:41.20 | infobot | i guess emmc is magnet:?xt=urn:btih:402fb5cc8a48ecbc18a77c9cf70d869a775bcf53&dn=RX-51%5F2009SE%5F10.2010.13-2.VANILLA%5FPR%5FEMMC%5FMR0%5FARM.bin or https://dl.dropboxusercontent.com/u/4105928/RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.torrent |
| 20:42.53 | CR0W | Is this the latest one? Can I use it with RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM? |
| 20:43.54 | hxka | Yes to both questions, though eMMC and Combined images aren't related |
| 20:44.35 | hxka | Sorry, going to sleep now |
| 20:44.45 | CR0W | hxka: Sorry, I thought they are. Sweet dreams. |
| 20:45.33 | *** join/#maemo alien_2003 (~alien@46.165.251.148) |
| 20:47.24 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-102-146-9.net.upcbroadband.cz) |
| 20:47.42 | DocScrutinizer05 | CR0W: see |
| 20:47.45 | DocScrutinizer05 | ~flashing |
| 20:47.45 | infobot | i guess maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware |
| 20:48.11 | CR0W | DocScrutinizer05: I'm reading that. It's a bit harder now, since the tablet-dev page is down. |
| 20:48.28 | DocScrutinizer05 | yes, sorry for that. Nokia made us take it down |
| 20:48.59 | CR0W | DocScrutinizer05: Yeah, Nokia hates freedom. |
| 20:49.25 | DocScrutinizer05 | Noiia loves peace. Particularly at their lawyers front |
| 20:49.34 | DocScrutinizer05 | nokia even |
| 20:50.18 | CR0W | I personally hate lawyers, cophyright, and closed source. |
| 20:50.24 | DocScrutinizer05 | they seem to be *very* concerned about stuff they once distributed to maemo users but don't really own it |
| 20:50.47 | DocScrutinizer05 | see flash plugin |
| 20:50.57 | DocScrutinizer05 | powervr libs from TI |
| 20:51.02 | DocScrutinizer05 | dunno what else |
| 20:51.45 | DocScrutinizer05 | and then a lot of the maemo core apps are also not *owned* by Nokia, it seems. Many are developed by subcontractors, and the copyright is unclear |
| 20:52.35 | CR0W | I sory of understand, but only sort off. I was surprised that flasher program is closed source. |
| 20:52.50 | DocScrutinizer05 | yeah |
| 20:53.05 | DocScrutinizer05 | thanks to Pali we have working 0xFFFF now |
| 20:53.11 | CR0W | *sort of |
| 20:53.16 | CR0W | DocScrutinizer05: What's that? |
| 20:53.24 | DocScrutinizer05 | FOSS flasher |
| 20:54.06 | CR0W | DocScrutinizer05: Great to hear. Hey, by the way, are there folks still working on Maemo and can I help? |
| 20:54.21 | DocScrutinizer05 | /join maemo-ssu |
| 20:54.34 | DocScrutinizer05 | see |
| 20:54.35 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?t=91142 |
| 20:54.39 | DocScrutinizer05 | and |
| 20:54.43 | DocScrutinizer05 | ~fptf |
| 20:54.43 | infobot | hmm... fptf is the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=91308 |
| 20:55.15 | CR0W | DocScrutinizer05: OK, I'll try tomorrow. |
| 20:55.23 | DocScrutinizer05 | :-) |
| 20:56.16 | DocScrutinizer05 | ~neo900 |
| 20:56.16 | infobot | [neo900] at http://talk.maemo.org/showthread.php?t=91142, or at http://neo900.org/ |
| 20:56.43 | ShadowJK | DocScrutinizer05; There's hand tool for making thread |
| 20:56.56 | DocScrutinizer05 | o.O |
| 20:57.03 | DocScrutinizer05 | wow, those craftsmen |
| 20:57.40 | DocScrutinizer05 | I wonder how that works |
| 20:58.18 | DocScrutinizer05 | something spinning screw while moving it along the axis, so you can file a thread in? |
| 21:00.15 | ShadowJK | Also there's hand tool for making thread in hole |
| 21:00.31 | DocScrutinizer05 | I bet it's something so ridiculously simple and effective that I will wonder why it just avoided my mind |
| 21:00.52 | DocScrutinizer05 | ooh, those! yeah, sure |
| 21:01.13 | DocScrutinizer05 | of course, I know those cutting irons |
| 21:01.32 | DocScrutinizer05 | weird I forgot about those |
| 21:01.41 | ShadowJK | this: http://upload.wikimedia.org/wikipedia/commons/8/87/ThreadingDies.jpg |
| 21:02.07 | DocScrutinizer05 | I don't need to check the URL, I just remembered all of that |
| 21:02.23 | ShadowJK | http://en.wikipedia.org/wiki/Tap_and_die |
| 21:03.05 | DocScrutinizer05 | I used those a lot, some 35 years ago |
| 21:03.30 | DocScrutinizer05 | (also broke quite a number of them) |
| 21:03.51 | CR0W | This is a vanilla image right? http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/5/--FID--A0A22YHFSICNA/--LID--FiRe1275051276916/AE98ED9D_RX-51_2009SE_10.2010.13-2.CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin |
| 21:04.04 | DocScrutinizer05 | umm |
| 21:04.18 | DocScrutinizer05 | good enough |
| 21:04.21 | *** join/#maemo mavhc (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 21:04.34 | DocScrutinizer05 | ~vanilla |
| 21:04.35 | infobot | well, vanilla is just plain old up & down & up & down & up & down & up & down & ooooh!, or the finest of the flavors |
| 21:04.35 | CR0W | DocScrutinizer05: any issues with it? |
| 21:04.41 | DocScrutinizer05 | dafq |
| 21:04.47 | CR0W | LOL |
| 21:05.08 | DocScrutinizer05 | ~emmc |
| 21:05.08 | infobot | emmc is, like, magnet:?xt=urn:btih:402fb5cc8a48ecbc18a77c9cf70d869a775bcf53&dn=RX-51%5F2009SE%5F10.2010.13-2.VANILLA%5FPR%5FEMMC%5FMR0%5FARM.bin or https://dl.dropboxusercontent.com/u/4105928/RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.torrent |
| 21:05.24 | CR0W | I know, but that dls slowly. |
| 21:05.44 | DocScrutinizer05 | the relevant part of name is identical |
| 21:06.04 | DocScrutinizer05 | ~emmc is also http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2010/5/--FID--A0A22YHFSICNA/--LID--FiRe1275051276916/AE98ED9D_RX-51_2009SE_10.2010.13-2.CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin |
| 21:06.04 | infobot | okay, DocScrutinizer05 |
| 21:06.12 | CR0W | DocScrutinizer05: I guess the one I found just has some central europe specific crap added? |
| 21:06.25 | DocScrutinizer05 | possible. Or removed |
| 21:06.37 | DocScrutinizer05 | it media content mostly, so nevermind |
| 21:07.07 | DocScrutinizer05 | maybe obsolete map tiles |
| 21:07.19 | CR0W | OK, thanks. |
| 21:07.22 | DocScrutinizer05 | yw |
| 21:07.34 | DocScrutinizer05 | thnks for the fire.nokia.com link |
| 21:07.44 | DocScrutinizer05 | ~pr131 |
| 21:07.44 | infobot | extra, extra, read all about it, combined is the rootfs fiasco image of maemo. For N900 latest (PR1.3.1) see http://nds2.fds-fire.nokia.com/fdp/interface/FiRe/2011/9/--FID--A0A22MVWFVFAM/--LID--FiRe1317015685654/RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin (or http://maemo.cloud-7.de/maemo5/fiasco+co/ ) |
| 21:08.27 | DocScrutinizer05 | flasher-3.5 linux is in many distro repos (arch for example) |
| 21:09.18 | CR0W | It's not in arch's repo. |
| 21:09.26 | DocScrutinizer05 | windows flasher-3.5 vanishing from internet slowly is probably a bless |
| 21:09.30 | CR0W | Is the above link newer than 21.2011.38.1? |
| 21:09.51 | DocScrutinizer05 | err nope, it *is* 38.1. look closer! |
| 21:10.06 | CR0W | Oh. |
| 21:10.47 | DocScrutinizer05 | MR0 means "international" |
| 21:11.08 | DocScrutinizer05 | or "global" |
| 21:11.27 | CR0W | I.e. has translations? |
| 21:11.53 | DocScrutinizer05 | i.e. has some restrictions missing |
| 21:12.44 | DocScrutinizer05 | and the asian version is special, global and western localized versions don't have the simpligied chinese etc support |
| 21:13.12 | DocScrutinizer05 | that's 203 or somthing instead MR0 then |
| 21:14.23 | CR0W | I aready tried flashing with pc suite. It was succesful, but didn't help. I have an issue that probably the cover and proximity sensors malfunction. |
| 21:14.43 | DocScrutinizer05 | :-o |
| 21:14.49 | CR0W | That is the cover sensor says it's open and proximity that something is close, I think. |
| 21:15.04 | DocScrutinizer05 | :-S |
| 21:15.10 | CR0W | When someone calls, the screen locks. Is this normal? |
| 21:15.21 | DocScrutinizer05 | cover sensor might be missing magnet in kickstand |
| 21:15.33 | DocScrutinizer05 | err, nope |
| 21:15.36 | CR0W | I think it's cause the proximity sensor works wrong. Magnet is in place. |
| 21:15.46 | DocScrutinizer05 | mompls |
| 21:16.38 | CR0W | I bought it used. I'll do a full flash, and if it doesn't help, I'll try returning it, thought the seller isn't required to accept returns. |
| 21:17.08 | *** join/#maemo alien2003 (~alien@178.162.199.144) |
| 21:18.00 | DocScrutinizer05 | IroN900:~# watch --interval=0,5 cat /sys/devices/platform/gpio-switch/proximity/state |
| 21:18.57 | DocScrutinizer05 | this is for proximity sensor, located landscape upper left corner |
| 21:19.21 | DocScrutinizer05 | you need root to run it, I guess |
| 21:19.35 | CR0W | DocScrutinizer05: I already tried reading all gpio stuff, but I'll run this now. |
| 21:20.09 | CR0W | I shoudln't need root for reading? |
| 21:21.11 | DocScrutinizer05 | you need root |
| 21:21.23 | DocScrutinizer05 | umm, wait |
| 21:21.42 | DocScrutinizer05 | nope, world readable |
| 21:21.57 | DocScrutinizer05 | just like magnet: |
| 21:22.05 | DocScrutinizer05 | IroN900:~# watch --interval=0,5 cat /sys/class/mmc_host/mmc0/cover_switch |
| 21:22.42 | CR0W | Watch doesn't accept these params. |
| 21:22.51 | CR0W | Guess I need watch from core utils? |
| 21:22.59 | DocScrutinizer05 | dang, you got the messybox crap I giess |
| 21:23.04 | DocScrutinizer05 | change interval to 1 |
| 21:23.09 | CR0W | OK. |
| 21:24.21 | CR0W | Ok, I did the first one, |
| 21:24.25 | CR0W | what to do now? |
| 21:24.29 | CR0W | It shows closed. |
| 21:24.36 | DocScrutinizer05 | what does it say? |
| 21:24.40 | DocScrutinizer05 | dang |
| 21:24.55 | CR0W | I tried covering and uncovering, and nothing. |
| 21:25.07 | CR0W | So it's 100% a hw problem then? |
| 21:25.09 | DocScrutinizer05 | first shpuld be "open" until you cover upper left corner |
| 21:25.32 | CR0W | Or could a full flash help? |
| 21:25.36 | DocScrutinizer05 | second should be "closed" when battery lid is attached |
| 21:25.41 | DocScrutinizer05 | hardly |
| 21:26.03 | DocScrutinizer05 | this is as straight to hardware as it gets |
| 21:26.09 | *** join/#maemo LauRoman (~LauRoman@5-14-192-20.residential.rdsnet.ro) |
| 21:26.18 | CR0W | Second shows open and cover is attached. |
| 21:26.27 | DocScrutinizer05 | unless somebody installed a fskdup debian kernel or sth, it must work |
| 21:26.55 | DocScrutinizer05 | for second you can try placing a magnet near main camera and move it a bit |
| 21:27.20 | DocScrutinizer05 | check kickstand "bay". Does kickstand snap to a small magnet when closed? |
| 21:27.54 | DocScrutinizer05 | the magnet is in the middle of the bay. the kickstand has a tiny metal patch there |
| 21:28.20 | CR0W | The kickstand magnet is there. |
| 21:28.33 | CR0W | So the sensor must be broken or the kernel is. |
| 21:28.34 | DocScrutinizer05 | hw defect |
| 21:28.42 | DocScrutinizer05 | uname -a |
| 21:28.59 | *** join/#maemo odin_ (~Odin@93-97-168-38.zone5.bethere.co.uk) |
| 21:29.55 | CR0W | Linux Nokia-N900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv71 unknown |
| 21:30.07 | DocScrutinizer05 | original kernel |
| 21:30.20 | DocScrutinizer05 | hw defect |
| 21:30.38 | DocScrutinizer05 | I got a deja vu |
| 21:30.50 | DocScrutinizer05 | maybe you are 4th owner of that device |
| 21:30.53 | freemangordon | the same one with gatta_negra's device |
| 21:31.04 | DocScrutinizer05 | :nod: |
| 21:31.35 | DocScrutinizer05 | CR0W: could you please disclose serial number? |
| 21:32.37 | DocScrutinizer05 | eventually maemo community will grab the torches and pitchforks |
| 21:33.13 | DocScrutinizer05 | ~seen gatta_negra |
| 21:33.14 | infobot | gatta_negra <~SailCat@89.190.196.121> was last seen on IRC in channel #maemo, 35d 4h 33m 35s ago, saying: 'it can work without sim card also '. |
| 21:34.16 | DocScrutinizer05 | CR0W: where's shipping origin of your device? |
| 21:36.22 | DocScrutinizer05 | CR0W: and pretty please post a photo of label under battery, or serial number or IMEI, or at very least leave a unique mark on label under battery and tell us what's that mark looking like |
| 21:37.09 | DocScrutinizer05 | CR0W: also, how much did you pay for device? |
| 21:38.02 | CR0W | DocScrutinizer05: Poland is probably the place where it was sold. |
| 21:38.36 | CR0W | I paid around 100$. |
| 21:38.46 | DocScrutinizer05 | anybody already checked geolocation of 89.190.196.121 ? |
| 21:39.59 | DocScrutinizer05 | CR0W: too expensive for a defect device |
| 21:40.50 | DocScrutinizer05 | 89.190.196.121BulgariaGrad Sofiya |
| 21:41.23 | CR0W | DocScrutinizer05: Guy sold it as "100% working". I'll try to send it back to him and get my money back. |
| 21:41.54 | DocScrutinizer05 | CR0W: could you disclose the numer printed on label under battery? I want to keep track of such broken devices now |
| 21:42.40 | DocScrutinizer05 | the numer probably starts with 3569 |
| 21:43.01 | DocScrutinizer05 | and has 3 "/" in it |
| 21:44.48 | DocScrutinizer05 | "100% working" LOL! Those are two obvious blatant hw defects, and they are totally unrelated. No way they went unnoticed or happened both during shipping |
| 21:44.50 | CR0W | I don't want to disclose my IMEI now, but if I'll send it back, I'll post it to you, okay? |
| 21:45.00 | DocScrutinizer05 | okay |
| 21:45.41 | CR0W | Maybe the guy is stupid or something, or he thought someone won't notice. |
| 21:45.50 | DocScrutinizer05 | though IMEI isn't as sikrit as everybody thinks it should be |
| 21:46.27 | DocScrutinizer05 | but ypou could send md5sum of IMEI :-D |
| 21:46.39 | CR0W | I'll research how sensitive is it tomorrow. Md5sum? OK. |
| 21:48.01 | DocScrutinizer05 | please add the full set of characters, incl the slashes |
| 21:49.11 | DocScrutinizer05 | imei=892472489724ß8971ß9871; cat $imei|wc; cat $imei|md5sum |
| 21:49.18 | CR0W | 32b3d6d57edd4b904e2fabbdf5f8c2f1 |
| 21:49.34 | CR0W | Slashes? |
| 21:49.50 | CR0W | This is md5sum of what *#06# returned. |
| 21:49.58 | DocScrutinizer05 | ok, good enough |
| 21:50.07 | DocScrutinizer05 | that's without slashes then |
| 21:50.18 | CR0W | Where's the one with slashes? |
| 21:50.27 | DocScrutinizer05 | under battery |
| 21:50.41 | CR0W | Ok, I see it. |
| 21:52.25 | CR0W | With slashes: ecb4a71e16b9587b38e8cb07d2cdf703 |
| 21:53.26 | CR0W | I have a question: when the guide says to flash with emmc, then remove battery and place again and flash with fiasco, can I unplug the cable when removing the battery? |
| 21:55.05 | DocScrutinizer05 | http://talk.maemo.org/showthread.php?p=1414689#post1414689 |
| 21:55.35 | DocScrutinizer05 | yes, you can unplug cable |
| 21:55.45 | CR0W | Thanks. You're joerg? |
| 21:55.50 | DocScrutinizer05 | yep |
| 21:55.52 | DocScrutinizer05 | ~joerg |
| 21:55.52 | infobot | joerg is, like, a natural born EE, ex HW-developer and engineer of Openmoko, now mainly involved in maintenance of maemo and N900. Usually known as DocScrutinizer |
| 21:56.26 | M4rtinK | DocScrutinizer05: maybe add Neo900 there ? :) |
| 21:56.41 | DocScrutinizer05 | *shrug* |
| 21:56.46 | CR0W | Cool. Hey, do you know something new about AD-54 and similar? |
| 21:57.00 | DocScrutinizer05 | what's AD-54? |
| 21:57.05 | CR0W | On N900/Neo900 that is. |
| 21:57.19 | CR0W | DocScrutinizer05: one of those multimedia headsets. |
| 21:57.32 | DocScrutinizer05 | ooh, ECI yoi mean? |
| 21:57.35 | DocScrutinizer05 | you* |
| 21:57.43 | CR0W | Yeah. |
| 21:57.48 | DocScrutinizer05 | multibutton headsets? |
| 21:57.52 | CR0W | Yes. |
| 21:58.03 | DocScrutinizer05 | will be supported as they basically are on n900 |
| 21:58.15 | CR0W | They are? |
| 21:58.20 | DocScrutinizer05 | just for fremantle nobody wrote a driver yet |
| 21:58.32 | DocScrutinizer05 | in nitdroid they are supported afaik |
| 21:58.41 | DocScrutinizer05 | hw support is in place |
| 21:58.49 | CR0W | I mean, mic and call button works on any OMTP device, but the multimedia buttons. |
| 21:59.21 | DocScrutinizer05 | that's ECI. one wire serial protocol. Basically fast morse with headset call button |
| 21:59.29 | DocScrutinizer05 | but bidir |
| 21:59.31 | CR0W | So I could take a driver from android and write it for the kernel used in N900? |
| 21:59.38 | DocScrutinizer05 | yes |
| 22:00.02 | DocScrutinizer05 | N900 has the needed comparators |
| 22:00.20 | CR0W | Cool. In a few months I'll have time for playing with stuff, so I'll take this, if it won't be done yet. |
| 22:00.35 | DocScrutinizer05 | much appreciated |
| 22:00.38 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 22:01.07 | CR0W | Never did any kernel stuff, but I know C99 good. |
| 22:01.31 | DocScrutinizer05 | that particular driver is maybe not so much kernel at all |
| 22:01.57 | DocScrutinizer05 | well, it probably is |
| 22:02.10 | DocScrutinizer05 | it needs to bitbang serial |
| 22:02.17 | DocScrutinizer05 | this needs terse timing |
| 22:02.23 | CR0W | It's something called nokia-av.c I think. |
| 22:02.29 | DocScrutinizer05 | yep |
| 22:02.52 | DocScrutinizer05 | check for ECI in there |
| 22:03.35 | CR0W | OK. I need to setup a dev envirioment. |
| 22:03.40 | DocScrutinizer05 | :-) |
| 22:03.43 | CR0W | What tools do we use? |
| 22:03.50 | DocScrutinizer05 | scratchbox |
| 22:04.00 | DocScrutinizer05 | all sane devels use VM now |
| 22:04.01 | CR0W | What's that? |
| 22:04.16 | DocScrutinizer05 | ~sb |
| 22:04.16 | infobot | well, scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, or hosted by maemo.org now, maintainer thedead1440 |
| 22:04.31 | CR0W | Oh, OK. |
| 22:04.47 | CR0W | Does it use qemu? |
| 22:04.53 | DocScrutinizer05 | yep, afaik |
| 22:05.11 | DocScrutinizer05 | there's a VM image |
| 22:05.19 | DocScrutinizer05 | roundabout 1GB |
| 22:05.31 | CR0W | So I can boot the stuff in qemu and see if things work, except for maybe devices like accelerometer? |
| 22:05.40 | DocScrutinizer05 | more convenient than "native" scratchbox on host |
| 22:05.49 | DocScrutinizer05 | yes |
| 22:05.56 | CR0W | Great. |
| 22:06.03 | DocScrutinizer05 | that qemu in qemu then, when yu use a VM ;-) |
| 22:06.56 | CR0W | Inception, heh. |
| 22:07.35 | DocScrutinizer05 | freemangordon: what's the damn filename of the scratchbox VM image? |
| 22:08.19 | DocScrutinizer05 | merlin1991: ping |
| 22:08.24 | arcean | Maemo_Ubuntu_Lucid_Desktop_SDK_Virtual_Image_Final ? |
| 22:08.25 | DocScrutinizer05 | merlin1991: ^^^^^ |
| 22:08.32 | DocScrutinizer05 | yep, that |
| 22:08.34 | merlin1991 | yep |
| 22:09.15 | DocScrutinizer05 | CR0W: google for that |
| 22:09.30 | merlin1991 | or http://maemo.merlin1991.at/files/SB/ |
| 22:09.37 | DocScrutinizer05 | ~sb |
| 22:09.37 | infobot | methinks scratchbox is a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, or hosted by maemo.org now, maintainer thedead1440 |
| 22:09.43 | DocScrutinizer05 | ~literal sb |
| 22:09.43 | infobot | "#maemo sb" is "<reply>see scratchbox" |
| 22:10.07 | DocScrutinizer05 | ~#maemo sb is also at http://maemo.merlin1991.at/files/SB/ |
| 22:10.07 | infobot | okay, DocScrutinizer05 |
| 22:10.10 | DocScrutinizer05 | ~sb |
| 22:10.11 | infobot | scratchbox is, like, a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, or hosted by maemo.org now, maintainer thedead1440, or at http://maemo.merlin1991.at/files/SB/ |
| 22:11.06 | CR0W | Found it, thanks. |
| 22:13.22 | DocScrutinizer05 | errr *cough* |
| 22:13.25 | DocScrutinizer05 | ~literal sb |
| 22:13.25 | infobot | "#maemo sb" is "<reply>see scratchbox" |
| 22:13.38 | DocScrutinizer05 | wow, infobot is so smaaaart |
| 22:14.06 | DocScrutinizer05 | and I'm so unattentative |
| 22:14.52 | DocScrutinizer05 | ~literal scratchbox |
| 22:14.52 | infobot | "scratchbox" is "a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, or hosted by maemo.org now, maintainer thedead1440, or at http://maemo.merlin1991.at/files/SB/" |
| 22:15.20 | DocScrutinizer05 | ~botsnack |
| 22:15.20 | infobot | thanks, DocScrutinizer05 |
| 22:16.54 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 22:17.38 | CR0W | DocScrutinizer05: Question: when chargin, should there also a little led in the corner light up? |
| 22:17.57 | DocScrutinizer05 | yes, usually should |
| 22:18.35 | DocScrutinizer05 | though for "normal" charging user is free to define all he likes, from flashing fireworks to no notification at all |
| 22:18.45 | DocScrutinizer05 | usually only shows when screen is locked |
| 22:18.56 | DocScrutinizer05 | yellow flashing |
| 22:19.22 | DocScrutinizer05 | when you get steady yellow, something is odd |
| 22:19.51 | CR0W | Well, I didn't observe it flashing at any point. So another defect I think. |
| 22:20.01 | DocScrutinizer05 | lock screen! |
| 22:20.14 | DocScrutinizer05 | slider lockswirch right side |
| 22:20.16 | CR0W | I'll try after flash. |
| 22:21.18 | DocScrutinizer05 | yeah, during flashing it neither locks nor charges |
| 22:22.13 | CR0W | OK, it's rebooting and I see those icons pulsing. |
| 22:22.23 | CR0W | Hands, yay! |
| 22:28.18 | DocScrutinizer05 | ooh, friggin hands |
| 22:28.23 | DocScrutinizer05 | ~jrtools |
| 22:28.23 | infobot | i heard jrtools is http://wiki.maemo.org/User:Joerg_rw/tools |
| 22:28.26 | DocScrutinizer05 | for the rescue |
| 22:28.38 | CR0W | Ok, flashed and still broken. I'll try to return it. |
| 22:29.19 | CR0W | The most problematic thing is the cover open state will cause microsd cards to not work. |
| 22:37.38 | *** join/#maemo HylianSavior (~hyliandes@HYLIANDESKTOP.RES.CMU.EDU) |
| 22:46.55 | *** join/#maemo Agge (~Durand@ghs/durand) |
| 22:51.50 | *** join/#maemo odin_ (~Odin@93-97-168-38.zone5.bethere.co.uk) |
| 22:53.24 | *** join/#maemo ZogG_laptop (~ZogG_lapt@109.66.136.56) |
| 22:53.25 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 22:54.25 | *** join/#maemo mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 22:55.08 | *** join/#maemo ALoGeNo (~alogeno@198.Red-79-155-15.dynamicIP.rima-tde.net) |
| 22:55.08 | *** join/#maemo ALoGeNo (~alogeno@unaffiliated/alogeno) |
| 22:56.00 | CR0W | DocScrutinizer05: are you still here? |
| 22:56.19 | DocScrutinizer05 | yes |
| 22:57.03 | CR0W | DocScrutinizer05: I guess downgrade won't help with my problem, right? |
| 22:57.13 | DocScrutinizer05 | there's a patched kernel driver module somewhere that ignores the magnet sensor |
| 22:57.26 | DocScrutinizer05 | no, downgrade doesn't help |
| 22:57.49 | CR0W | DocScrutinizer05: I thought about that, I'll probably do that and patch also the poximity sensor. |
| 22:58.22 | CR0W | How does the prox. sensor work, is it an ir led and sensor? |
| 22:58.30 | DocScrutinizer05 | you rather should send back the device to that b***ard who sold it to you |
| 22:58.43 | DocScrutinizer05 | yes |
| 22:58.49 | DocScrutinizer05 | integrated |
| 22:59.06 | CR0W | Could it be that under the screen cover it's just dirty? |
| 22:59.24 | CR0W | Is it hard to remove that cover? |
| 23:00.52 | DocScrutinizer05 | well, it's not exactly easy |
| 23:01.03 | DocScrutinizer05 | you have to disassemble from backside |
| 23:01.26 | DocScrutinizer05 | first disassemble bottom half and detach screen flex cable *carefully* |
| 23:01.32 | DocScrutinizer05 | get service manual for that |
| 23:02.08 | CR0W | OK. |
| 23:02.20 | DocScrutinizer05 | I however never heard about dirt causing proximity sensor failing |
| 23:02.22 | CR0W | Also, in gpio-switch/proximity, |
| 23:02.26 | CR0W | there's disable |
| 23:02.30 | CR0W | and it has value 1. |
| 23:02.34 | CR0W | What does that mean? |
| 23:02.38 | DocScrutinizer05 | o.O |
| 23:03.36 | DocScrutinizer05 | nfc. has "1" here too |
| 23:04.23 | DocScrutinizer05 | he sensor is always powered. lways working, and always reporting directly to a GPIO |
| 23:04.26 | DocScrutinizer05 | afaik |
| 23:04.36 | DocScrutinizer05 | ~schematics |
| 23:04.37 | infobot | extra, extra, read all about it, schematics is http://wiki.maemo.org/N900_Hardware_Schematic |
| 23:05.14 | DocScrutinizer05 | it's a OSRAM combined IR detector |
| 23:05.22 | *** join/#maemo Hurrian (~textual@unaffiliated/rikanee) |
| 23:05.59 | CR0W | I wonder, is it a common problem with those sensors, like with the micro usb desoldering? |
| 23:06.14 | DocScrutinizer05 | I heard of them going thermonuclear and even burn a hole into digitizer. |
| 23:06.32 | CR0W | Wow. |
| 23:06.39 | DocScrutinizer05 | once report |
| 23:06.46 | DocScrutinizer05 | one* |
| 23:07.00 | CR0W | So I guess I should be glad I didn't get one that explodes. |
| 23:07.10 | DocScrutinizer05 | you can swap whole flex cable |
| 23:09.12 | CR0W | I could take those two sensors from an N900 sold as broken if it was really cheap. |
| 23:09.39 | DocScrutinizer05 | a new flex cable cost ~8bucks |
| 23:10.22 | honestly | 18:18:17 < freemangordon> honestly: try a couple of flashes, that might mark all bad blocks and fix your problems |
| 23:10.30 | honestly | ouch :| |
| 23:11.11 | DocScrutinizer05 | http://www.ebay.com/itm/New-Flex-Cable-Ribbon-with-Camera-For-Nokia-N900-/280966940848?pt=LH_DefaultDomain_0&hash=item416aef48b0 |
| 23:12.10 | CR0W | DocScrutinizer05: I rather not buy from ebay, I prefer my local auctioning site (allegro). |
| 23:12.14 | DocScrutinizer05 | the backcover hall switch is a bigger problem |
| 23:12.30 | CR0W | DocScrutinizer05: how is it connected? |
| 23:12.43 | DocScrutinizer05 | that's your nightmare |
| 23:14.29 | CR0W | Meh, I'd live with patched kernel for the hall, if the proximity ir works. |
| 23:14.38 | DocScrutinizer05 | it's soldered to a "satellite" PCB that's tightly connected to the main PCB. Integrated flexible PCB cable. When that is broken, your camera LEDs and hall switch and camera door sensor (another of those OSRAM proximity sensors) and the uSD will never come back |
| 23:15.22 | DocScrutinizer05 | http://maemo.cloud-7.de/Gallery-N900-exploded/ |
| 23:15.53 | DocScrutinizer05 | http://maemo.cloud-7.de/Gallery-N900-exploded/n900_12.jpeg uooer right small brownish thingie |
| 23:15.57 | CR0W | But that sattelite PCB is connected with some zif connector? |
| 23:16.10 | DocScrutinizer05 | no |
| 23:16.13 | *** join/#maemo arcean_ (~arcean@apn-37-7-112-22.dynamic.gprs.plus.pl) |
| 23:16.38 | DocScrutinizer05 | it's basically *one* PCB with a flexible section |
| 23:16.50 | DocScrutinizer05 | the most nasty hardware I ever seen |
| 23:16.53 | CR0W | Oh, it's joined with the main one. |
| 23:16.54 | CR0W | Damn. |
| 23:17.24 | *** join/#maemo jon_y (~enforcer@2001:e68:4052:34f:e01f:8e6d:cdca:d0e5) |
| 23:17.27 | DocScrutinizer05 | http://maemo.cloud-7.de/Gallery-N900-exploded/platine_02.jpeg |
| 23:18.27 | DocScrutinizer05 | honestly, rather try to get your money back and get a better N900. One thta works |
| 23:20.15 | DocScrutinizer05 | when you had paid 50$ for it, i'd say it's worth repairing it. 100$ though, you should expect "like new" condition |
| 23:21.06 | DocScrutinizer05 | and when the sattelite conncetion ribbon is broken, you're completely out of luck |
| 23:21.49 | DocScrutinizer05 | check camera! does it flash? |
| 23:22.01 | DocScrutinizer05 | does it notice door open? |
| 23:24.35 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 23:24.43 | DocScrutinizer05 | http://wstaw.org/m/2014/02/28/plasma-desktopDk3389.png left bizarre thing is OSRAM proximity IR sensor for cam door. right tiny "MK" is a hall switch for battery cover. Top right is a part of uSD card |
| 23:25.33 | honestly | DocScrutinizer05: I've had this phone for two years |
| 23:26.04 | honestly | and it's been worth the 70 euros I paid (: |
| 23:29.50 | CR0W | Camera works properly. |
| 23:29.56 | CR0W | Flash also. |
| 23:30.25 | CR0W | Accelerometer also, screen as well, touch yep, not tested gps and ir, usb works, bluetooth and wifi works. |
| 23:32.07 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 23:35.10 | *** join/#maemo wmarone__ (~wmarone@c-24-10-24-149.hsd1.ca.comcast.net) |
| 23:40.33 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 23:41.11 | *** join/#maemo mavhk (~mavhc@cpc65310-basf8-2-0-cust204.12-3.cable.virginmedia.com) |
| 23:41.20 | *** join/#maemo qwazix_nc (~qwazix@Maemo/community/council/qwazix) |
| 23:42.29 | *** join/#maemo lool- (~lool@debian/developer/lool) |
| 23:43.38 | *** join/#maemo b1101 (~b@66.55.135.219) |
| 23:44.09 | *** join/#maemo Earthwings_ (dennis@nienhueser.de) |
| 23:46.12 | *** join/#maemo VDVsx (~VDVsx@a88-114-88-95.elisa-laajakaista.fi) |
| 23:47.53 | *** join/#maemo lbt (~david@78-32-229-233.static.enta.net) |
| 23:47.53 | *** join/#maemo lbt (~david@Maemo/community/contributor/lbt) |
| 23:49.28 | *** join/#maemo esaym153 (~esaym153@216-45-91-132.gvec.net) |
| 23:53.40 | *** join/#maemo StyXman (~mdione@ant06-1-82-242-111-163.fbx.proxad.net) |
| 23:53.40 | *** join/#maemo StyXman (~mdione@grulic/root/StyXman) |
| 23:59.56 | *** join/#maemo xray256 (~xray256@4e56af3d.skybroadband.com) |
