| 00:26.00 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 00:27.34 | *** join/#maemo maybeHere (~cl@p5B1642D1.dip.t-dialin.net) |
| 00:33.57 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 00:39.46 | *** join/#maemo lardman|home (~lardman@138-38-179-52.docking.bath.ac.uk) |
| 00:41.25 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 00:50.12 | *** join/#maemo spoofy (~spoofy@e151.rwd.prospect.pl) |
| 00:53.27 | *** join/#maemo chadi (chadi@unaffiliated/chadi) |
| 01:08.19 | DocScrutinizer51 | ~botsnack |
| 01:08.19 | infobot | DocScrutinizer51: :) |
| 01:11.29 | Drathir | what can be a reason that when system start have 20mb swap used? clean after restart use some about 120mb of ram thats a lot or not? |
| 01:11.45 | Drathir | botsnack |
| 01:11.53 | Drathir | gochi |
| 01:52.16 | Drathir | that will be strange if coreplayer will can smoothly play stream video on n80 but on n900 not i must will testing that... |
| 01:56.19 | SpeedEvil | there is a lot of stuff run once on boot |
| 01:56.39 | SpeedEvil | all at once |
| 01:57.00 | SpeedEvil | it pushing stuff into swap seems bad though |
| 02:00.32 | DocScrutinizer05 | we got default setting of swappiness=100 (max), means everything that can gets swapped out |
| 02:01.48 | DocScrutinizer05 | OTOH threre are several greedy processes that are preloaded at boot time and ram-locked (dialer, browserd, whatnot else) - that's why you see swap getting used pretty quickly |
| 02:01.55 | SpeedEvil | if it's swapping while booting, and not hitting ram limit while booting, that's bad |
| 02:02.15 | SpeedEvil | if it's swapping after booting, when idle, good. |
| 02:03.09 | *** join/#maemo uen| (~uen@p5DCB2A45.dip.t-dialin.net) |
| 02:09.48 | *** join/#maemo robbiethe1st (~robbiethe@71-221-196-99.spkn.qwest.net) |
| 02:10.45 | *** join/#maemo shamus (~shamus@ip-206-192-195-49.marylandheights.ip.cablemo.net) |
| 02:36.29 | *** join/#maemo degtep (~Smith@87.224.132.2) |
| 02:38.12 | DocScrutinizer05 | Drathir: (botsnack) infobot's attention-char is '~' |
| 02:39.26 | DocScrutinizer05 | ~ |
| 02:39.35 | DocScrutinizer05 | thought as much |
| 02:39.46 | DocScrutinizer05 | ~chanset #maemo |
| 02:39.46 | infobot | chan: #maemo (see _default also) |
| 02:39.46 | infobot | <PROTECTED> |
| 02:40.00 | DocScrutinizer05 | WUT? |
| 02:40.11 | DocScrutinizer05 | ~chanset _default |
| 02:40.11 | infobot | Default channel settings |
| 02:40.11 | infobot | <PROTECTED> |
| 02:40.11 | infobot | <PROTECTED> |
| 02:40.11 | infobot | <PROTECTED> |
| 02:40.12 | infobot | <PROTECTED> |
| 02:40.50 | DocScrutinizer05 | addressCharacter => ~ |
| 02:42.28 | DocScrutinizer05 | Drathir: try ~help |
| 02:47.12 | *** join/#maemo aloril_ (~aloril@dsl-tkubrasgw3-fe7ef900-153.dhcp.inet.fi) |
| 02:47.31 | DocScrutinizer05 | ~stat :) |
| 02:47.37 | DocScrutinizer05 | ~stat |
| 02:50.15 | DocScrutinizer05 | ~upsidedown test |
| 03:00.59 | *** join/#maemo maybeWTF (~cl@p5B163A86.dip.t-dialin.net) |
| 03:29.52 | Drathir | DocScrutinizer05: thanks little other than oryginal gochi have... |
| 03:38.08 | *** join/#maemo SmilyOrg (Smily@89.142.210.105) |
| 03:44.53 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 03:57.47 | *** join/#maemo MohammadAG (~MohammadA@xceleo.us) |
| 03:58.17 | *** join/#maemo _xnt14 (~xnt14@xceleo.us) |
| 04:03.44 | *** join/#maemo DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 04:44.51 | *** join/#maemo radic_ (~radic@dslb-178-002-208-250.pools.arcor-ip.net) |
| 04:47.47 | *** join/#maemo Hurrian_ (~Hurrian@121.54.32.135) |
| 04:53.58 | *** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg) |
| 05:07.01 | *** join/#maemo Jade (~jade@modemcable190.180-203-24.mc.videotron.ca) |
| 05:07.02 | *** join/#maemo Jade (~jade@unaffiliated/jade) |
| 05:46.58 | *** join/#maemo sirdancealot2 (~sirdancea@98.82.broadband5.iol.cz) |
| 05:47.04 | *** join/#maemo sirdancealot8 (~sirdancea@98.82.broadband5.iol.cz) |
| 05:47.12 | *** join/#maemo till- (till@vispillo.org) |
| 05:49.33 | *** join/#maemo kerio92 (kerio@unaffiliated/kerio) |
| 05:50.32 | *** join/#maemo kerio92 (kerio@unaffiliated/kerio) |
| 05:52.03 | *** join/#maemo kerio92 (kerio@unaffiliated/kerio) |
| 05:58.32 | *** join/#maemo kerio92 (kerio@unaffiliated/kerio) |
| 06:05.48 | *** join/#maemo thedead1440_ (~thedead14@cm53.sigma102.maxonline.com.sg) |
| 06:28.27 | *** join/#maemo sirdancealot8 (~sirdancea@98.82.broadband5.iol.cz) |
| 06:29.21 | *** join/#maemo ghjgfjghjbn1119 (~jdfgf@c-67-173-101-12.hsd1.il.comcast.net) |
| 06:32.46 | *** part/#maemo thedead1440_ (~thedead14@cm53.sigma102.maxonline.com.sg) |
| 06:46.46 | *** join/#maemo Jade (~jade@2001:5c0:1000:b::b41b) |
| 06:46.46 | *** join/#maemo Jade (~jade@unaffiliated/jade) |
| 07:00.14 | *** join/#maemo till- (till@vispillo.org) |
| 07:27.46 | *** join/#maemo MacDrunk (~marper@187.243.202.128) |
| 07:29.23 | *** part/#maemo MacDrunk (~marper@187.243.202.128) |
| 07:31.56 | *** join/#maemo fredrinLap (~fn@74.203.34.95.customer.cdi.no) |
| 07:32.54 | kerio | rm_you: try booting, now |
| 07:39.06 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 07:41.49 | *** join/#maemo m4g0g (~Maledictu@178.121.130.23) |
| 07:57.27 | *** join/#maemo calvaris (~calvaris@fanzine.igalia.com) |
| 07:59.20 | *** join/#maemo kerio92 (kerio@unaffiliated/kerio) |
| 08:01.17 | *** join/#maemo murrayc (~murrayc@ppp-188-174-3-65.dynamic.mnet-online.de) |
| 08:23.11 | *** join/#maemo fredrinLap (~fn@74.203.34.95.customer.cdi.no) |
| 08:29.39 | *** join/#maemo sasquatch (~username@p579582D2.dip.t-dialin.net) |
| 08:34.16 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 08:35.10 | *** join/#maemo eijk (~eijk@e178216096.adsl.alicedsl.de) |
| 08:36.41 | *** join/#maemo fecub (~fecub@p5DC9EBC4.dip.t-dialin.net) |
| 08:37.34 | *** join/#maemo kolp (~quassel@212.255.39.205) |
| 08:42.14 | *** join/#maemo stardiviner (~stardivin@218.74.185.135) |
| 08:45.41 | *** join/#maemo doc|home (~doc@gentoo/contributor/doc-007) |
| 08:51.50 | *** join/#maemo m4g0g (~Maledictu@178.121.130.23) |
| 08:56.58 | *** join/#maemo eMHa_ (~mh@et-0-30.gw-nat.bs.kae.de.oneandone.net) |
| 08:57.38 | *** join/#maemo Rantwolf (~rantwolf@static-217-17-207-54.net.encoline.de) |
| 09:00.36 | *** join/#maemo wazd (~wazd@broadband-188-255-81-182.nationalcablenetworks.ru) |
| 09:08.25 | *** join/#maemo khertan (~khertan@AAmiens-554-1-1-221.w86-198.abo.wanadoo.fr) |
| 09:11.03 | *** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg) |
| 09:14.27 | *** join/#maemo mpthx (~mpthx@support.leaseweb.net) |
| 09:18.32 | *** join/#maemo Muelli (~muelli@port-13790.pppoe.wtnet.de) |
| 09:19.49 | *** join/#maemo OkropNick (kuba@host-n2-72-190.telpol.net.pl) |
| 09:25.19 | Drathir | try to make video works correctly... |
| 09:26.15 | Drathir | x264 mean... |
| 09:33.03 | *** join/#maemo valerius (~user@95.153.171.11) |
| 09:41.32 | *** join/#maemo jhb (~joerg@p579F6763.dip.t-dialin.net) |
| 09:46.12 | *** join/#maemo aloril (~aloril@dsl-tkubrasgw3-fe7ef900-153.dhcp.inet.fi) |
| 09:46.28 | *** join/#maemo VDVsx (~VDVsx@a88-112-254-211.elisa-laajakaista.fi) |
| 09:50.13 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 09:50.59 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 09:51.35 | *** join/#maemo rcg-work (~rcg-work@fb2-pub-1.dv-nr.fh-frankfurt.de) |
| 09:55.57 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 10:01.11 | *** join/#maemo Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
| 10:16.46 | *** join/#maemo ZogG_laptop (~ZogG_lapt@bzq-109-64-187-170.red.bezeqint.net) |
| 10:16.47 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 10:16.56 | *** join/#maemo valerius (~user@178.76.208.218) |
| 10:21.19 | Skry | morning |
| 10:21.28 | Skry | Drathir: what's your problem? |
| 10:23.10 | *** join/#maemo zap_ (~zap@94.25.228.65) |
| 10:24.59 | vi____ | yo |
| 10:32.09 | *** join/#maemo tanty (~agomez@cs78210056.pp.htv.fi) |
| 10:32.51 | *** join/#maemo lizardo (lizardo@nat/indt/x-gqwrqmqzjoydjgvn) |
| 10:37.18 | *** join/#maemo inz (inz@inz.fi) |
| 10:46.23 | *** join/#maemo pcfe (~pcfe@160.44.248.188) |
| 10:48.38 | vi____ | How do I explain to my boss that I am not 'lazy' I am just giving myself an artificial pay rise? |
| 11:09.27 | *** join/#maemo lbt_ (~david@78.32.229.233) |
| 11:09.28 | *** join/#maemo lbt_ (~david@Maemo/community/contributor/lbt) |
| 11:09.31 | *** join/#maemo kontio (~kontio@unaffiliated/kontio) |
| 11:13.20 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 11:15.51 | teotwaki | vi____: just tell him that you want to be able to focus entirely on the company and work, which means you're not greedy, you just don't want to have to worry about money. |
| 11:19.10 | *** join/#maemo trx (ns-team@212.200.198.195) |
| 11:19.42 | *** join/#maemo lardman (~lardman@Maemo/community/contributor/lardman) |
| 11:34.05 | *** join/#maemo m4g0g (~Maledictu@178.121.130.23) |
| 11:35.26 | vi____ | teotwaki: The pre-previous guy left for a job with a 50% increase in salary. He left with a compiled version of the last firmware but no source code. |
| 11:35.46 | vi____ | I am pretty sure it was a final fuck-you from beyond the grave. |
| 11:38.07 | teotwaki | vi____: how much do you make? |
| 11:38.17 | vi____ | I am ashamed to say. |
| 11:38.20 | teotwaki | actually, you don't need to say it out loud, just think of the answer |
| 11:38.32 | teotwaki | And think of how much you enable the company to 1/ function, 2/ ruin your life. |
| 11:38.32 | vi____ | Yup. |
| 11:38.40 | vi____ | Yup. |
| 11:38.49 | teotwaki | Does your salary seem just to you? |
| 11:38.57 | vi____ | Not even slightly. |
| 11:39.07 | teotwaki | Then either get a payraise, or walk away. |
| 11:39.13 | vi____ | I am already on it. |
| 11:39.33 | vi____ | I have a couple of applications allready 'in'. |
| 11:39.35 | teotwaki | Don't tell them "I'll leave", and don't go to interviews without telling them |
| 11:39.55 | vi____ | teotwaki: Dont go to the interviews without telling? |
| 11:40.16 | teotwaki | Just tell them, "I've been asking for a raise for x months, and have been blatantly ignored, so I'm just letting you know that I've been contacted by other companies and am pondering my options" |
| 11:40.55 | vi____ | teotwaki: Normally I would agree, however this particular company has demonstrated beyond any reasonable doubt that they do not give raises. |
| 11:41.07 | teotwaki | "This doesn't mean that I've decided to leave, but I don't feel the company values my skills enough, nor does it take my questions and worries into account." |
| 11:41.25 | teotwaki | vi____: yeah, people said that about my company when I joined as well. |
| 11:41.52 | teotwaki | I got an 20% raise after 3 months in, and 30% a year later. |
| 11:42.12 | vi____ | They let the my pre-predecessor walk away. He had been working on this project for almost 2 years. He knew it inside out. They let him walk away without a fight. Then they hired his replacement at the salary that he was asking for a raise too. |
| 11:42.22 | teotwaki | And am currently negotiating another 10% raise. |
| 11:42.22 | vi____ | His replacement did not even know how to program. |
| 11:42.36 | vi____ | teotwaki: That is because you are a gifted programmer. |
| 11:42.40 | teotwaki | No. |
| 11:42.44 | teotwaki | I just know how to negotiate ;) |
| 11:42.50 | vi____ | heh. |
| 11:42.56 | teotwaki | Anyway, lunch break, 'later. |
| 11:57.11 | *** join/#maemo MrPingu (~MrPingute@85.133.27.6) |
| 11:57.21 | MrPingu | Yo! |
| 11:58.56 | MrPingu | vi____: My N900 does not start on battery insert, however it "forgets" the time/date in less than 5 seconds |
| 12:00.55 | vi____ | MrPingu: Yeah, all n900 go like that eventually. The internal battery is garbage. |
| 12:01.14 | vi____ | We are waiting for some brave soul to replace it with a capacitor! |
| 12:02.08 | MrPingu | vi____: I know, but you started that thread asking how N900 acts on batteryinsert. Was too lazy to find that thread |
| 12:03.05 | M4rtinK | vi____: we did something like that on a Neo FreeRunner rework party - replaced all RTC batteries by supercapacitors |
| 12:13.00 | *** join/#maemo etrunko (etrunko@nat/intel/x-xdcvyqmagktzvuhz) |
| 12:17.43 | vi____ | M4rtinK: Any details on the super caps you used? |
| 12:18.24 | *** join/#maemo guampa (~guampa@unaffiliated/guampa) |
| 12:19.30 | *** join/#maemo MrPingu (~MrPingute@86.92.226.97) |
| 12:29.03 | M4rtinK | vi____: I think it was done according to these instructions: http://wiki.openmoko.org/wiki/GTA02_RTC_backup_battery |
| 12:33.15 | vi____ | M4rtinK: Now that is a nice link! Thank you. |
| 12:33.18 | *** join/#maemo Dibblah (~Dibblah@host86-139-134-59.range86-139.btcentralplus.com) |
| 12:34.04 | M4rtinK | I can also ask the guy who did the actual reworks if you need some more info :) |
| 12:34.31 | M4rtinK | ist been a year and a half since, so hope he still remembers something :) |
| 12:34.56 | vi____ | M4rtinK: That link tells me all I need to know. |
| 12:40.49 | *** join/#maemo Timo (~timo@unaffiliated/tiempjuuh) |
| 12:41.22 | *** join/#maemo marek__ (~marek@dhcp20.dmg.tuwien.ac.at) |
| 12:53.26 | *** join/#maemo freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 12:57.37 | *** join/#maemo eijk (~eijk@e178203157.adsl.alicedsl.de) |
| 12:58.51 | *** join/#maemo Darkchaos (~darkchaos@88.130.207.11) |
| 12:59.28 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 13:03.06 | *** join/#maemo SmilybOrg (Smily@89.142.210.105) |
| 13:21.56 | *** join/#maemo MetalGearSolid (~MetalGear@175.142.127.48) |
| 13:40.24 | *** join/#maemo Muelli (~muelli@port-13790.pppoe.wtnet.de) |
| 13:42.44 | *** part/#maemo malin (~malin@213.236.233.237) |
| 13:58.56 | *** join/#maemo shanttu (~shanttu@dsl-hkibrasgw3-ff55c100-11.dhcp.inet.fi) |
| 14:07.39 | *** join/#maemo setanta (setanta@nat/indt/x-tfpufhisbwkughea) |
| 14:15.22 | *** join/#maemo ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com) |
| 14:25.53 | *** join/#maemo calvaris (~calvaris@fanzine.igalia.com) |
| 14:33.03 | *** join/#maemo panjgoori (779af844@gateway/web/freenode/ip.119.154.248.68) |
| 14:41.08 | *** join/#maemo thedead1440 (~chatzilla@cm53.sigma102.maxonline.com.sg) |
| 14:46.03 | DocScrutinizer05 | :-D |
| 14:50.35 | FIQ | :-D |
| 14:51.53 | *** join/#maemo auenf (David@171.72.233.220.static.exetel.com.au) |
| 14:51.58 | *** join/#maemo ian--- (ian---@46.11.25.81) |
| 14:55.54 | DocScrutinizer05 | ~joerg |
| 14:55.54 | infobot | from memory, joerg is a HW-developer and engineer of Openmoko, usually known as DocScrutinizer |
| 14:58.14 | DocScrutinizer05 | guess who originally suggested that rework |
| 15:08.48 | *** join/#maemo shamus (~shamus@ip-206-192-195-49.marylandheights.ip.cablemo.net) |
| 15:16.37 | ShadowJK | has a supercap to change at $work |
| 15:16.53 | ShadowJK | but I don't think I have the skills, it looks tricky |
| 15:17.02 | ShadowJK | components on both side of board too |
| 15:20.52 | *** join/#maemo Timo (~timo@unaffiliated/tiempjuuh) |
| 15:22.20 | DocScrutinizer05 | nah, the bupbat has nice huge 'pins' |
| 15:22.34 | DocScrutinizer05 | should be easier than soldering of a DIL14 |
| 15:23.52 | DocScrutinizer05 | you might use some kapton film, solid thin carton etc, to push it between 'pin' and pad while desoldering |
| 15:24.02 | *** join/#maemo stardiviner (~stardivin@122.236.243.106) |
| 15:24.17 | DocScrutinizer05 | or just use two soldering irons in parallel |
| 15:25.25 | DocScrutinizer05 | or - the brute force EE approach - you cut the 'wires' of the bupbat so you can desolder one after the other |
| 15:29.40 | *** join/#maemo ced117 (~ced117@AStrasbourg-552-1-92-134.w92-141.abo.wanadoo.fr) |
| 15:29.41 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 15:31.41 | *** join/#maemo ketas (ketas@ketas6-sixxs.si.pri.ee) |
| 15:34.32 | DocScrutinizer05 | ShadowJK: anyway after desoldering the soldering of capacitor is just a piece of cake |
| 15:34.55 | Gh0sty | hmm |
| 15:35.07 | DocScrutinizer05 | as long as you don't have to worry about oversize of new component |
| 15:35.10 | *** join/#maemo valerius (~user@178.76.208.218) |
| 15:35.26 | Gh0sty | could it be the led controller is acting funny of my n900 due to a "relatively bad" battery? |
| 15:35.36 | DocScrutinizer05 | sure |
| 15:35.41 | Gh0sty | basicly when i plug it in it still charges ... |
| 15:35.56 | Gh0sty | sometimes I even see a steady orange light when I plug it in |
| 15:36.07 | DocScrutinizer05 | that's emergency charging |
| 15:36.12 | Gh0sty | but backlight nor warnings from sms or anything light up the led |
| 15:36.28 | DocScrutinizer05 | hah, check your settings |
| 15:36.30 | Gh0sty | and it all started recently when battery started drowning mega-fast |
| 15:36.45 | DocScrutinizer05 | o.O |
| 15:36.46 | Gh0sty | can't even keep it for longer then a whole day without calls |
| 15:37.05 | Gh0sty | last week was on a party, took 1 call, made 2 pictures |
| 15:37.10 | DocScrutinizer05 | not exactly unreasonable standby time |
| 15:37.14 | Gh0sty | was fully charged before that |
| 15:37.25 | Gh0sty | like say 3 - 4 hours it ran |
| 15:37.37 | Gh0sty | when i took it out my pocket it wasdead |
| 15:37.47 | Gh0sty | battery completly discharged |
| 15:37.49 | jon_y | was it warm? |
| 15:37.54 | Gh0sty | no |
| 15:38.16 | Gh0sty | until recently I could use it for ... 2 days (and nights) on standby |
| 15:38.16 | DocScrutinizer05 | 3..4h is about the timespan you can expect with CPU at full load, and possibly screen backlight on |
| 15:38.29 | Gh0sty | well it was not on at all |
| 15:38.44 | jon_y | try get a new battery to see if it makes a difference |
| 15:38.51 | Gh0sty | now it lasts more like 1 day and night on standby ... |
| 15:39.07 | Gh0sty | will have a look i think they sold these also on dealextreme :P |
| 15:39.25 | DocScrutinizer05 | get bq27200.sh, run it like `bq27200.sh 60 >>mybatlog` from a xterm, on boot |
| 15:39.26 | jon_y | obviously a battery problem if you can fix by replacing it |
| 15:40.33 | *** join/#maemo Viltzu_ (viltzu@xob.kapsi.fi) |
| 15:41.24 | DocScrutinizer05 | obviously a battery problem when data in mybatlog suggests that |
| 15:41.28 | *** join/#maemo d1b_ (~db@d1b.org) |
| 15:43.05 | *** join/#maemo tchell_ (~mitchell@unyew.silverninja.net) |
| 15:47.27 | *** join/#maemo kontio (~kontio@unaffiliated/kontio) |
| 15:49.12 | *** join/#maemo jonne (~jonne@109.133.80.44) |
| 15:57.21 | *** join/#maemo konelix (~konelix@190.143.220.79) |
| 16:08.19 | DocScrutinizer05 | Gh0sty: all the symptoms you described are more hinting towards some problem with rootfs than with battery |
| 16:12.05 | *** join/#maemo konelix (~konelix@190.143.220.79) |
| 16:13.40 | *** join/#maemo valerius (~user@95.153.170.148) |
| 16:16.38 | *** part/#maemo MetalGearSolid (~MetalGear@175.142.127.48) |
| 16:19.59 | ShadowJK | DocScrutinizer05; oh, the supercap at $work is throughhole with smd components on both side of board and around (and between) the supercap pins |
| 16:24.43 | *** join/#maemo vi_ (~paul@31.185.144.86) |
| 16:25.44 | Gh0sty | a problem with rootfs causes the led and backligt to stop working? |
| 16:28.34 | vi_ | Gh0sty: reboot. |
| 16:28.44 | vi_ | I just had a funny conversation with tmobile. |
| 16:29.17 | vi_ | The customer service literally does not understand what the internet is nor how it works. |
| 16:29.30 | ShadowJK | Gh0sty's problem sounds vaguely familiar to some hw failure modes I've seen discussed before, but it's definitely too early to say anything one way or another witout further tests |
| 16:29.33 | Gh0sty | vi_: already did several times |
| 16:29.53 | vi_ | Gh0sty: powerdown, take battery out for 1 min. |
| 16:29.55 | Gh0sty | ShadowJK: and how does it end? |
| 16:30.01 | Gh0sty | I need to backup my phone? :p |
| 16:30.09 | vi_ | Gh0sty: You did that? |
| 16:30.11 | Gh0sty | vi_: already did several times ... |
| 16:30.11 | ShadowJK | how does what end? |
| 16:30.12 | vi_ | Battery out? |
| 16:30.21 | vi_ | ShadowJK: he wants to know how to fix it. |
| 16:30.27 | Gh0sty | to try and fix the led controller you mean ;) |
| 16:30.31 | Gh0sty | no its not working |
| 16:30.32 | vi_ | Oh wait, the screen has stopped working? |
| 16:30.42 | Gh0sty | no |
| 16:30.44 | vi_ | Gh0sty: What is the last thing you did? |
| 16:30.49 | vi_ | Gh0sty: no? |
| 16:30.54 | vi_ | Then wtf are you asking? |
| 16:30.59 | Gh0sty | lets start from the beginning ... |
| 16:31.05 | vi_ | ok :) |
| 16:31.16 | ShadowJK | Gh0sty; does it at any point when charging or plugging in do the glowing/pulsing yellow led thing? |
| 16:31.22 | Gh0sty | like 2 weeks ago my led and KEYBOARD backligt did not work anymore |
| 16:31.24 | vi_ | Gh0sty: every detail you leave out, god punches a kitten. |
| 16:31.34 | Gh0sty | i tried any of the following combinations found on the internet: |
| 16:31.54 | Gh0sty | turn off - remove battery for 10 minutes - turn on |
| 16:32.05 | Gh0sty | turn off - remove battery whole night - turn on |
| 16:32.13 | vi_ | what did you do before the backlight stopped working? |
| 16:32.15 | Gh0sty | turn off - remove battery and sim - turn on |
| 16:32.18 | vi_ | did you drop it? |
| 16:32.35 | Gh0sty | turn off - remove battery - sim and plug it in without battery - turn back on |
| 16:32.35 | Gh0sty | etc |
| 16:32.39 | Gh0sty | no |
| 16:32.57 | Gh0sty | well not in the recent history at least |
| 16:33.06 | Gh0sty | it made a couple of drops long time ago |
| 16:33.36 | Gh0sty | then all of the sudden plugging it in a couple of days later and *yay* led and keyboard backlight returned |
| 16:33.43 | Gh0sty | 2 days later again everything gone ... |
| 16:34.27 | Gh0sty | the next day i noticed the battery has made a serious capacity dive |
| 16:34.51 | Gh0sty | up to the fact this weekend it even went down after couple of hours (but i had used it then) |
| 16:34.53 | ShadowJK | Gh0sty; does it at any point when charging or plugging in do the glowing/pulsing yellow led thing? |
| 16:35.10 | Gh0sty | now when i recharge it its only good for a full day in stdby |
| 16:35.38 | Gh0sty | not anymore well if i plug it in without battery you still see the orange led very weak for a split second ... |
| 16:37.34 | Gh0sty | ever since I have not seen led nor keyboard backligt working ... |
| 16:38.01 | Gh0sty | also the strange thing there after the battery died in a couple of hours that weekend ... |
| 16:38.15 | Gh0sty | I am pretty sure I plugged it in that night and turned it on a little later |
| 16:38.33 | Gh0sty | that noon when i woke up it was off ... |
| 16:45.23 | DocScrutinizer05 | yeah pretty detailed description of 5% of the relevant facts. I still say it's sw related |
| 16:45.37 | DocScrutinizer05 | possibly mce, or bme |
| 16:45.38 | vi_ | Gh0sty: Do a complete reflash. |
| 16:45.42 | DocScrutinizer05 | yes |
| 16:45.46 | freemangordon | :nod: |
| 16:45.48 | vi_ | If problem persists, it is probably hardware related. |
| 16:47.21 | ShadowJK | places bets on hw fault |
| 16:47.27 | ShadowJK | either way, backup. |
| 16:47.59 | DocScrutinizer05 | of course we could start investigating stuff like (power)top, mce, syslog, bq27200.sh, whatnot else |
| 16:48.24 | DocScrutinizer05 | ShadowJK: which hw fault? |
| 16:48.52 | freemangordon | Gh0sty: it you your RGB LED not working? |
| 16:48.57 | freemangordon | *it is |
| 16:49.29 | DocScrutinizer05 | which hw fault would make indicator LED not work properly, cause massively reduced standby time, and issues with screen backlight? and battery deep discharge |
| 16:50.06 | freemangordon | DocScrutinizer05: those could be separated things, we all know HW misdesign n900 has |
| 16:50.28 | freemangordon | light sensor that is |
| 16:50.35 | DocScrutinizer05 | might be generic NAND hw fault. Couldn't think of any other plausible single point of hw failure causing all this |
| 16:50.46 | freemangordon | I have the same experience (excludng the battery drain) |
| 16:50.48 | *** join/#maemo valerius (~user@85.26.180.173) |
| 16:51.21 | freemangordon | it disappeared in a couple of days |
| 16:51.31 | freemangordon | (LED not working) |
| 16:51.51 | freemangordon | actually it works, but on very low brightness |
| 16:52.10 | DocScrutinizer05 | freemangordon: sure you haven't fsckd your ALS calibration? |
| 16:52.26 | freemangordon | DocScrutinizer05: for sure I didn;t touch it |
| 16:52.34 | freemangordon | BTW it was during the summer |
| 16:52.35 | freemangordon | ;) |
| 16:53.01 | DocScrutinizer05 | ALS calib is in CAL |
| 16:53.30 | freemangordon | Gh0sty: is it possible that your n900 has been exposed to very bright light? |
| 16:53.39 | DocScrutinizer05 | ???????????? |
| 16:54.09 | DocScrutinizer05 | CAL erasure by ultrahard photons? |
| 16:54.12 | DocScrutinizer05 | ;-P |
| 16:54.34 | freemangordon | DocScrutinizer05: toldya, I had the same LED not working proble, not solved with battery removal |
| 16:56.27 | DocScrutinizer05 | who suggested battery removal? |
| 16:56.29 | freemangordon | DocScrutinizer05: iirc ALS is connected on the same power bus? or something as some of the LEDs. If not all of the lleds |
| 16:57.09 | DocScrutinizer05 | also you had NOT same problems, since you admitted ind LED was dim, not defect. And your standby time didn't drop |
| 16:57.24 | freemangordon | BTW I cannot remember if i flashed |
| 16:57.35 | freemangordon | DocScrutinizer05: not dim, but almost invisible |
| 16:57.41 | DocScrutinizer05 | no. ALS is not connected to any power bus |
| 16:57.54 | freemangordon | well, then proximity |
| 16:58.00 | DocScrutinizer05 | neither |
| 16:59.06 | freemangordon | however, i've seen that. and it repaired by itself. almost NFC how |
| 16:59.19 | freemangordon | *has repaired |
| 17:00.04 | DocScrutinizer05 | battery removal can reset LP5523 ind (& kbd) LED controller. That's all. All other 'fix' attempts are random nonsense, since neither removing one night nor SIM has anything to do with LP5523. And LP5523 hardly can cause massive reduction of standby time |
| 17:00.30 | freemangordon | DocScrutinizer05: <Gh0sty> then all of the sudden plugging it in a couple of days later and *yay* led and keyboard backlight returned |
| 17:00.36 | freemangordon | the same here |
| 17:00.56 | freemangordon | was^^^ |
| 17:01.20 | DocScrutinizer05 | see ^^^ |
| 17:02.41 | freemangordon | DocScrutinizer05: yep. but that could be a different problem. Forgotten wifi power savings disabled for example ;) |
| 17:05.40 | *** join/#maemo vi__ (~user@31.185.144.86) |
| 17:07.03 | *** join/#maemo sLumPia (~sLumPia@182.10.252.150) |
| 17:07.13 | DocScrutinizer05 | I'd check LP5523 for basic functionality (e.g. with MohammadAG's nightrider light), then reflash (incl stock kernel!) |
| 17:07.48 | freemangordon | DocScrutinizer05: sure. What I am trying to say is that maybe HW is ok. |
| 17:08.07 | DocScrutinizer05 | as mentioned above, I couldn't think of a single point of hw failure explaining the listed symptoms |
| 17:08.13 | freemangordon | but mce has gone crazy |
| 17:08.20 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 17:12.40 | DocScrutinizer05 | btw Gh0sty told about a party, about photos, even videos maybe. I recall fcam messing with LP5523 sysnodes in a way so mce starts segfaulting |
| 17:13.24 | DocScrutinizer05 | we had several reports about similar symptoms with LEDs related to fcam, some years ago |
| 17:13.53 | *** join/#maemo NIN101 (~NIN@p5DD28E5A.dip0.t-ipconnect.de) |
| 17:14.43 | DocScrutinizer05 | depending on race conditions during boot up, you can end with a working or a broken mce, depending on who's first to open/lock the lp5523 sysnodes |
| 17:15.07 | *** join/#maemo freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net) |
| 17:15.41 | DocScrutinizer05 | fcam seriously crapped own pants with that indicatior LED control it implemented |
| 17:19.01 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 17:19.55 | *** join/#maemo konelix_ (~konelix@200.119.189.253) |
| 17:24.13 | *** join/#maemo ron0062000 (~ron006200@cpe-72-181-242-49.tx.res.rr.com) |
| 17:27.48 | *** join/#maemo konelix_ (~konelix@190.143.210.194) |
| 17:41.18 | *** join/#maemo juozapas (~juozapas@78-61-169-218.static.zebra.lt) |
| 17:45.18 | *** join/#maemo valeriusN (~valerius@85.26.180.162) |
| 17:48.03 | *** join/#maemo qwazix (~qwazix@193.185.223.3) |
| 17:49.54 | *** join/#maemo valerius (~user@85.26.180.162) |
| 17:52.23 | *** join/#maemo ivgalvez (~quassel@229.pool85-49-213.dynamic.orange.es) |
| 17:56.29 | *** join/#maemo MentalistTraceur (~mentalist@2001:470:1f0f:728:c238:f9ff:fe18:4fad) |
| 18:13.15 | *** join/#maemo marek__ (~marek@dhcp11.dmg.tuwien.ac.at) |
| 18:14.36 | *** join/#maemo Pali (~pali@unaffiliated/pali) |
| 18:20.24 | *** join/#maemo janemba (~101@cev75-4-82-247-118-210.fbx.proxad.net) |
| 18:27.40 | *** join/#maemo janemba_ (~101@cev75-4-82-247-118-210.fbx.proxad.net) |
| 18:32.14 | *** join/#maemo vi__ (~user@31.185.144.86) |
| 18:34.52 | vi__ | shai hulud! |
| 18:38.51 | Drathir | Skry: i try to optimise smoothly of play x264 on n900... try throught xforward ssh, sshfs, and locally play... |
| 18:39.01 | Drathir | hi all... |
| 18:40.35 | Drathir | vi__: maybe give you more interesting things to work if something interesting you lazy dosent matter... |
| 18:45.14 | *** join/#maemo BigBoxDriver (~BigBoxDri@p5B3DFBE8.dip.t-dialin.net) |
| 18:45.43 | *** join/#maemo iDont (~iDont@dhcp-077-250-143-002.chello.nl) |
| 18:56.58 | *** join/#maemo sq-one (~sq-one@p549A9CCF.dip.t-dialin.net) |
| 19:05.48 | *** join/#maemo eMHa_ (~mh@HSI-KBW-5-56-244-117.hsi17.kabel-badenwuerttemberg.de) |
| 19:08.04 | *** join/#maemo inz (inz@inz.fi) |
| 19:13.21 | *** join/#maemo crope (crope@otitsun.oulu.fi) |
| 19:20.09 | *** join/#maemo Raimu (rmaunula@tuomi.oulu.fi) |
| 19:20.40 | *** join/#maemo inz (inz@inz.fi) |
| 19:41.57 | *** join/#maemo etrunko (etrunko@nat/intel/x-hsqwduwbebwuyjjw) |
| 19:47.45 | *** join/#maemo Darkchaos (~darkchaos@88.130.207.11) |
| 19:49.20 | *** join/#maemo BigBoxDr_ (~BigBoxDri@p5B3DFBE8.dip.t-dialin.net) |
| 19:51.57 | Drathir | O.o new updates... |
| 19:52.24 | *** join/#maemo iDont (~iDont@dhcp-077-250-143-002.chello.nl) |
| 19:59.54 | kerio | DocScrutinizer05: was the fcam led bug fixed? |
| 20:02.38 | *** join/#maemo M4rtinK (~M4rtinK@mail.melf.eu) |
| 20:05.35 | *** join/#maemo Venusaur (~desu@wikipedia/Antonio-Lopez) |
| 20:11.23 | *** join/#maemo ToJa92 (~ToJa92@90-231-48-224-no126.tbcn.telia.com) |
| 20:14.14 | DocScrutinizer05 | kerio: tbh I got no idea |
| 20:19.06 | vi__ | so are we allowed to distribute the firmware files? |
| 20:23.40 | DocScrutinizer05 | vi__: nobody will ever ask that question |
| 20:25.52 | *** join/#maemo geaaru (~geaaru@host191-87-dynamic.244-95-r.retail.telecomitalia.it) |
| 20:27.32 | *** join/#maemo piggz (~piggz@host-92-18-208-163.as13285.net) |
| 20:28.03 | vi__ | I mean if I roll community-firmware_no-crap-edition.bin and make a post on tmo will I get in trouble? |
| 20:30.06 | kerio | vi__: to be safer, i'd install the bme replacement on your firmware :3 |
| 20:30.34 | *** join/#maemo piggz (~piggz@host-92-18-208-163.as13285.net) |
| 20:32.48 | vi__ | kerio: to be clear I do not think I have done enough to call it my firmware, lets call it CE (community edition). |
| 20:33.18 | vi__ | kerio: the goal is to create the best starting point for flashing from. |
| 20:33.49 | vi__ | so there will be nothing installed except maybe flash 10 and rootfs. |
| 20:34.03 | vi__ | also backupmenu. |
| 20:34.07 | kerio | don't ship rootsh please :( |
| 20:34.11 | vi__ | no? |
| 20:34.23 | kerio | ship a known password and a sudoers file that lets you do stuff passwordly |
| 20:34.48 | kerio | hell, ship an empty password and a passwordful sudoers |
| 20:35.08 | vi__ | does that mean if the user installs rootfs, they will have to type in a password when they type root? |
| 20:35.29 | kerio | they'll have to type in a password when they type "sudo <something>" |
| 20:35.32 | kerio | as it should be |
| 20:35.36 | kerio | no, wait |
| 20:35.49 | kerio | when the user installs rootsh, he'll just be able to sudo gainroot passwordlessly |
| 20:35.55 | kerio | he *shouldn't* |
| 20:36.01 | kerio | because rootsh is fucking awful |
| 20:36.23 | vi__ | That will be a massive break from convention and will potentially brake loads of peoples poorly written scriots. |
| 20:40.59 | kerio | scripts don't expect passwordless sudo |
| 20:45.15 | DocScrutinizer05 | vi__: (trouble) if you ask dor it, you might be able to get into trouble |
| 20:45.19 | DocScrutinizer05 | for* |
| 20:46.43 | DocScrutinizer05 | I'll however make you feel trouble when users make 'maemo-ssu feel trouble about stuff 'optimized' out of that firmware for no good reason, based on incomplete and sloppy evaluation |
| 20:47.21 | vi__ | The point is there is nothing optimised. |
| 20:48.39 | vi__ | it is just standard firmware with things like ovi-widget removed. |
| 20:49.46 | DocScrutinizer05 | I'm fine with removing ovi-widget. I start to frown when removing games, and I'll ask for moderation of tmo when that firmware has e.g. jumping-dots removed |
| 20:51.37 | Drathir | DocScrutinizer05: ovi proppably hard to remove because its nokia... |
| 20:51.48 | vi__ | but jumping dots is just a package. It requires no bodgery to remove it. |
| 20:52.10 | vi__ | Drathir: apt-get purge ovi-promotion-widget |
| 20:52.27 | Drathir | vi__: hrhr O.o |
| 20:56.16 | *** join/#maemo rcg (~rcg@e180221105.adsl.alicedsl.de) |
| 21:06.11 | DocScrutinizer51 | vi__: fine. A pretty good argument to leave removing it to user then |
| 21:08.20 | DocScrutinizer51 | if $cssu would have considred it worth removing, it probably already was removed, don't you think so? so how you gonna roll an "official" cssu fiasco? |
| 21:08.40 | DocScrutinizer51 | this IS NOT official |
| 21:10.40 | kerio | he never said it's a cssu fiasco |
| 21:11.29 | kerio | btw, make an official cssu fiasco |
| 21:12.20 | kerio | DocScrutinizer51: maemoblocks *is* awful |
| 21:12.24 | vi__ | DocScrutinizer51: Did I say this wa anything official? jesus christ, I just want to do something for the community. |
| 21:14.33 | tadzik | vi__++ |
| 21:15.00 | vi__ | do you think I am going to create the next speedpatch by removing startup dots and that bullshit rss feeder? |
| 21:15.02 | *** join/#maemo lardman|home (~simon@host86-158-105-100.range86-158.btcentralplus.com) |
| 21:15.43 | *** join/#maemo Ken-Young (~kenyoung@wrls-67-134-207-195.wrls.harvard.edu) |
| 21:16.22 | Skry | I certainly would welcome *-no-crap-edition.* very warmly and could see myself even using one, if available. |
| 21:16.28 | *** join/#maemo piggz (~piggz@host-92-18-208-163.as13285.net) |
| 21:16.37 | DocScrutinizer51 | if you all can't see how silly an idea it was to roll 6487 different permutations of fiasco images to meet every single user's personal preferences, then I really dunno |
| 21:18.00 | DocScrutinizer51 | at CSSU we'll definitely deprecate and discourage usage of any such personalized fiasco |
| 21:18.55 | DocScrutinizer51 | since we simply CAN NOT do support for it |
| 21:20.00 | Ken-Young | If one is not interested in overclocking, is there any real advantage to using the power kernel on the N900? I haven't seen any bug fixes in it that look especially important for normal users. Am I missing something? |
| 21:20.11 | kerio | Ken-Young: iptables |
| 21:20.28 | DocScrutinizer51 | if you think XY has to get kicked, go and discuss it in #maemo-ssu and provide a patch so every CSSU installation will be similar, no matter what fiasco it's based on |
| 21:20.31 | kerio | smartreflex |
| 21:20.33 | tadzik | mobile-hotspot |
| 21:20.46 | kerio | bridge interfaces |
| 21:20.50 | kerio | fbcon |
| 21:20.58 | kerio | wifi injection |
| 21:21.01 | Ken-Young | mobile-hotspot works on my N900 with the vanilla kernel. |
| 21:21.12 | kerio | Ken-Young: really? |
| 21:21.13 | kerio | :o |
| 21:21.25 | Ken-Young | Yup. I use it all the time at airports. |
| 21:21.29 | tadzik | surprising |
| 21:21.55 | Ken-Young | It's better than Joiku, because it doesn't burn through the battery so quickly. |
| 21:22.07 | M4rtinK | mobile hotspot != joikuspot |
| 21:22.08 | DocScrutinizer51 | eh? you use mobile hotspot at airports? |
| 21:22.13 | DocScrutinizer51 | why?? |
| 21:22.14 | Ken-Young | I know. I have both. |
| 21:22.40 | Ken-Young | DocScrutinizer05, I use it to get net access for my laptop. |
| 21:22.43 | DocScrutinizer51 | rogue honeypot AP? |
| 21:22.44 | tadzik | there's no wifi at certain airports |
| 21:22.50 | tadzik | *cough*FRA*cough* |
| 21:23.09 | Ken-Young | FRA? I don't know what that is. |
| 21:23.31 | DocScrutinizer51 | frankenfurth |
| 21:23.35 | tadzik | Frankfurt International Airport. Claims to be the biggest-ish airport in europe, no way to get a wifi anywhere |
| 21:23.36 | Ken-Young | All major airports in the US have WiFi, but it isn't free, |
| 21:24.21 | *** join/#maemo croppa (~stuart@CPE-120-146-137-99.static.nsw.bigpond.net.au) |
| 21:24.57 | DocScrutinizer51 | anyway, better do a uname -a |
| 21:25.06 | DocScrutinizer51 | you might be surprised |
| 21:25.39 | DocScrutinizer51 | odds are you're already using KP sinve ages without even noticing |
| 21:25.44 | Ken-Young | uname -a = Linux Nokia-N900 2.6.28-omap1 #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 armv7l GNU/Linux |
| 21:25.53 | DocScrutinizer51 | weird |
| 21:26.15 | DocScrutinizer51 | I always thought mobile hotspot depends on KP |
| 21:26.31 | Ken-Young | Both Joiku spot and mobile hotspot work, although Joiku works best as a hand warmer. |
| 21:28.05 | DocScrutinizer51 | anyway, no there's no 'sekrit' rationale to use KP. If you need it, you'll know that |
| 21:29.12 | DocScrutinizer51 | nobody, literally nobody, so far came up with any hard numbers about any supposed battery savings or whatever in KP |
| 21:29.27 | *** join/#maemo kolp (~quassel@212.255.39.205) |
| 21:29.48 | DocScrutinizer51 | such claims always based 'on the obvious' |
| 21:29.54 | Ken-Young | OK, thanks for the info. I kinda soured on KP, because I ended up unintentionally overclocking. I'm sure it was something dumb I did, but if I don't really get any extra functionallity from KP, I'll just stick with the stock kernel. |
| 21:36.35 | Luke-Jr | ahahahaha |
| 21:36.42 | Luke-Jr | I forgot I keep my N900 in my N810 case |
| 21:36.44 | Luke-Jr | <.< |
| 21:37.48 | DocScrutinizer51 | there's a lot of extra funcionality in KP. *extra* functionality, not improved funcionality. If you ned anyof those extras, you'll probably notice that |
| 21:38.21 | *** join/#maemo muellisoft (~muelli@port-13326.pppoe.wtnet.de) |
| 21:39.33 | vi__ | there is free wifi in frankfurt airport. |
| 21:39.46 | vi__ | just need a little mac spoofing is all. |
| 21:41.53 | Ken-Young | DocScrutinizer05, Yeah, I've seen some lists of extra functionality, but nothing I need. Maybe I'm living in a fool's paradise, but I see no need for iptables, etc. |
| 21:42.41 | *** join/#maemo Neutron18 (~neutron@171.80-202-122.nextgentel.com) |
| 21:44.09 | vi__ | more MHz==MOAR POWUH |
| 21:45.34 | Drathir | vi__: moar what? |
| 21:47.00 | Drathir | some kind of fast kill the phone? |
| 21:48.47 | *** join/#maemo ColdFyre_ (~lenny@c-98-248-56-123.hsd1.ca.comcast.net) |
| 21:49.10 | DocScrutinizer51 | basically yes |
| 21:50.22 | DocScrutinizer51 | ~omap-oc |
| 21:50.23 | infobot | methinks omap-oc is http://mg.pov.lt/maemo-irclog/%23maemo.2010-08-01.log.html#t2010-08-01T22:16:05 read that!, or and this http://mg.pov.lt/maemo-irclog/%23maemo.2011-03-11.log.html#t2011-03-11T03:04:11 |
| 21:52.31 | *** join/#maemo Milhouse (~irc_milho@Maemo/community/contributor/Milhouse) |
| 21:52.50 | *** join/#maemo NIN101 (~NIN@p5DD28E5A.dip0.t-ipconnect.de) |
| 21:54.25 | DocScrutinizer51 | CPU livetime at 500MHz: 50k hours. at 600MHz: 10k h. at 800MHz: probabaly 1000 h or less |
| 21:55.17 | DocScrutinizer51 | after that operation time 5..7 percent will show defects |
| 21:58.36 | *** join/#maemo Preflex (~ashes@70-57-130-52.albq.qwest.net) |
| 21:59.37 | *** join/#maemo Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
| 22:05.02 | *** join/#maemo _rd (~rd@p57B48E44.dip0.t-ipconnect.de) |
| 22:09.12 | vi__ | <PROTECTED> |
| 22:09.45 | vi__ | it is not 6487. It is 1 with the junk removed. |
| 22:10.24 | vi__ | No cherry, no ovi widget, no maemoblocks. I honestly cannot see what the rpoblem is. |
| 22:10.58 | vi__ | If it was loaded up with VM tweakz and warez then yes, you would have a point. |
| 22:11.43 | vi__ | I do not see you condemning robbiethe1st rolled backupmenu .img |
| 22:12.00 | *** join/#maemo piggz (~piggz@host-92-18-208-163.as13285.net) |
| 22:14.36 | DocScrutinizer51 | robbiethe1st ADDED something to fiasco, particularly he added exactly what is needed to recover from flashing |
| 22:15.15 | DocScrutinizer51 | he didn't remove things he personally found 'awful' or 'useless' |
| 22:15.35 | kerio | vi__: hater gonna hate |
| 22:15.46 | *** join/#maemo mvp_ (~mvp@62.225.102.227) |
| 22:15.56 | DocScrutinizer51 | troll gonna troll |
| 22:16.19 | vi__ | Keep it civil man. |
| 22:17.12 | DocScrutinizer51 | who? kerio? hah, he usually doesn't know what's civil |
| 22:17.53 | kerio | DocScrutinizer51: removing cherry is ok, right? |
| 22:18.04 | kerio | what about that one dude who likes MyNokia? |
| 22:18.35 | DocScrutinizer51 | sure, since there's nobody missing it and there's a real rationale why you want to remove it |
| 22:19.31 | kerio | ovi promo widget? |
| 22:19.45 | kerio | the various installers? |
| 22:19.46 | DocScrutinizer51 | kerio: that one dude I'll happily find the number and text of the SMS, so he can send manually |
| 22:25.02 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 22:29.00 | *** join/#maemo _rd (~rd@p57B48E44.dip0.t-ipconnect.de) |
| 22:29.27 | *** join/#maemo mvp_ (~mvp@62.225.102.227) |
| 22:30.11 | DocScrutinizer51 | sorry, but every time I hear somebody cheerfully pondering what else could get nuked to give user the benefit of missing choice, I get upset |
| 22:31.56 | Skry | Vi is doing something for himself, in a way it could be useful for at least some other community members. He is obviously not doing anything "official". I'm seeing shit like request for moderation and such about 'dots. I don't see it's vi who is making someone miss a choice here. |
| 22:32.37 | DocScrutinizer51 | IOW there's no sense in removing anything now that as well can get removed later |
| 22:34.02 | kolp | But we'd learn something from figuring out how to create our own fisco images, which could be useful later |
| 22:34.44 | kolp | And so long as it's clearly not marked 'official'... I don't see a problem |
| 22:34.47 | DocScrutinizer51 | we could even use a fiasco that includes latest CSSU stuff |
| 22:35.51 | DocScrutinizer51 | but only if the result of flashing that cssu fiasco is same result as flashing stock fiasco and then running CSSU on top of that |
| 22:36.12 | *** join/#maemo piggz (~piggz@host-92-18-208-163.as13285.net) |
| 22:39.14 | DocScrutinizer51 | s/CSSU on/CSSU updae on/ |
| 22:41.32 | merlin1991 | kolp: there is some blog post on how to build your own fiasco *somewhere* on the net |
| 22:43.05 | *** join/#maemo pvanhoof (~philip@codeminded.be) |
| 23:00.34 | *** join/#maemo dhbiker (~dhbiker@193.2.218.150) |
| 23:06.54 | *** join/#maemo `0660 (~olli@180.148.124.200) |
| 23:15.18 | *** join/#maemo m_pahlevanzadeh (~mohsen@91.98.176.115) |
| 23:15.45 | m_pahlevanzadeh | What's package name of u-boot-update-bootmenu ? |
| 23:17.24 | *** join/#maemo ekze (~nyan@bakaekze.ru) |
| 23:45.26 | merlin1991 | uboot-tools or similar |
| 23:45.51 | merlin1991 | m_pahlevanzadeh: if you can install you can find it out via dpkg-query -S u-boot-update-bootmenu |
| 23:46.02 | merlin1991 | s/can install/have it installed/ |
| 23:50.48 | *** join/#maemo auenfx4 (David@171.72.233.220.static.exetel.com.au) |