**** BEGIN LOGGING AT Fri Apr 15 02:59:58 2016 Apr 15 07:27:51 DocScrutinizer05: what kind of video out port(s) are on the Neo900? Apr 15 07:30:37 http://talk.maemo.org/showpost.php?p=1503625&postcount=1397 Apr 15 07:32:33 DO NOT USE YAPPARI. Apr 15 07:32:35 seems clear Apr 15 07:33:22 add " / FIND ANOTHER SANE IM NETWORK" Apr 15 07:33:40 after every warning Apr 15 07:38:35 ceene: it gets you banned? Apr 15 07:43:31 temporarily Apr 15 07:56:05 hi, can i use yappari? Apr 15 07:58:49 yes, who are we to stop you from doing it? Apr 15 08:00:27 kerio: sure you can! Apr 15 08:00:35 when you get banned you can blame then :D Apr 15 08:00:43 s/blame/blame me/ Apr 15 08:00:43 ceene meant: when you get banned you can blame me then :D Apr 15 08:01:07 bencoh: yep, it seems so Apr 15 08:01:13 is there yappari for macbooks? Apr 15 08:01:15 due to the protocol change Apr 15 08:01:26 what? Apr 15 08:01:35 even if it exists, do not use it Apr 15 08:01:40 kerio has an apple product Apr 15 08:01:42 do not use anything that comes from ceene Apr 15 08:01:52 it'll break everything Apr 15 08:01:57 ceene: pull the package from the repos Apr 15 08:02:05 can i do that? Apr 15 08:02:10 didn't know Apr 15 08:02:12 i assume so \_o_/ Apr 15 08:02:15 just add a warning before connect and reupload Apr 15 08:02:34 just replace yappari with /usr/bin/true Apr 15 08:02:44 not the gnu coreutils version though, that one sucks Apr 15 08:02:48 false would be better, i guess Apr 15 08:02:58 yeah, cos return 0 is too dificult to write for the gnu bunch Apr 15 08:03:20 make it display picture of a kitten too! Apr 15 08:03:45 do you guys know that i have a work? Apr 15 08:03:53 ceene: honestly just pull the package Apr 15 08:03:53 pah Apr 15 08:03:59 i can't spend all my time not only fixing yappari but also placing kittens Apr 15 08:04:08 placing kittens > fixing yappari Apr 15 08:04:15 kittens > work Apr 15 08:04:30 http://www.ex-parrot.com/pete/upside-down-ternet.html Apr 15 08:04:35 i did this in fact, for a coworker Apr 15 08:04:39 http://imgur.com/r/kittens Apr 15 08:04:56 pick one and redisplay on 'connect' Apr 15 08:05:08 "due to changes in the whatsapp protocol, we had to choose between things to focus on; thus we decided to focus on our core purpose of displaying kittens, dropping the IM functionality" Apr 15 08:05:14 :D Apr 15 08:05:25 no but seriously remove the package from the repos Apr 15 08:05:45 i'm trying Apr 15 08:05:48 but i don't think i can Apr 15 08:05:51 that's insane Apr 15 08:05:54 i can push another version Apr 15 08:05:54 i think one cant remove package without admin help, so replacing with a warning is doable Apr 15 08:05:56 or promote it Apr 15 08:06:03 which doesn't seem a cool thing to do right now Apr 15 08:06:03 is it in extras? Apr 15 08:06:07 only on extras-devel Apr 15 08:06:15 in principle nobody should use that Apr 15 08:06:21 just push an empty package Apr 15 08:06:23 as an upgrade Apr 15 08:20:29 hi Apr 15 08:27:35 i've just uploaded an empty package, 2.0.28 Apr 15 08:27:52 if i get this thing to work it'll be version 3.0 Apr 15 08:27:54 empty package without any info will get you lots of confusion Apr 15 08:28:10 all of the confused people can go and use telegram Apr 15 08:28:12 or the fuck they want Apr 15 08:28:16 i may do that myself Apr 15 08:28:26 go irc Apr 15 08:28:50 i like irc very much Apr 15 08:28:57 i've been using it for thousands of years Apr 15 08:29:00 even before it was invented Apr 15 08:29:05 well, not so much Apr 15 08:29:10 since i knew what a computer was, almost Apr 15 08:29:36 there was no irc for timex2048 :/ Apr 15 09:03:35 do we have a signal client already Apr 15 09:06:56 do we need one Apr 15 09:12:37 signal is cool Apr 15 09:15:47 Seems like what people are most interested in for the N900 is a client for Whatsapp (something that was in progress but is now stalled) Apr 15 09:16:16 ceene: have you tried talking to mark zuckerberg Apr 15 09:16:31 add him on facebook Apr 15 09:18:01 It seems like the companies behind Whatsapp and other proprietary protocols would rather not have 3rd party open implementations floating around out there. Apr 15 09:18:18 I bet if the N900 didn't have an official Skype client and someone wrote an unofficial one, Microsoft would care Apr 15 09:19:10 Me, I dont care about Facebook, WhatsApp, Instagram or anything else connected to the Zuckerberg empire Apr 15 09:44:43 kerio: and what should i tell him? Apr 15 09:44:57 "yo how do i whatsapp" Apr 15 09:45:07 to pay a couple of developers to port whatsapp to n900, a device that has been out of market for nearly a decade when they're deprecating even old android phones? Apr 15 09:45:27 nah, just ask him to send you the specs Apr 15 09:45:35 it's not a matter of specs right now Apr 15 09:45:40 it's more or less there, with written code Apr 15 09:45:51 it's the time required to port all that existing code to my specific platform and gui Apr 15 09:46:41 right now, libwa is segfaulting on me Apr 15 09:49:30 oh neat Apr 15 09:49:49 ceene: https://www.youtube.com/watch?v=ZXsQAXx_ao0 Apr 15 09:52:18 ceene: it would be sufficient to write sample client lib for linux, with open source Apr 15 09:52:51 oh, great Apr 15 09:52:57 now i got a heisenbug Apr 15 09:53:11 if i add a qDebug() to print what parameters i'm sending, there's no more segfaulting Apr 15 09:53:47 KotCzarny: a lib doesn't get you to speak with anyone... Apr 15 09:53:55 that already exists Apr 15 09:54:13 ceene: leave the qDebug there Apr 15 09:54:15 ez Apr 15 09:54:24 HTH.HAND Apr 15 09:55:53 I thought the plan was to use the existing pigin/libpurple WhatsApp implementation Apr 15 09:56:09 na, it's segfaulting again Apr 15 09:56:20 jonwil: easiest for me right now should be coderus' libwa Apr 15 09:56:24 as it's written in qt Apr 15 09:56:33 and api is similar although not equal Apr 15 09:57:01 I thought the problem with whatsapp is the fact that they keep banning you with alt implementations. Apr 15 09:57:23 they only ban us because they detect we do something different as them Apr 15 09:57:29 if we do the same, they can't know who we are Apr 15 09:57:34 Exactly, that is what I am saying Apr 15 09:57:43 Maybe someone needs to cleanroom the Android version Apr 15 09:57:45 ceene: so they change their client to pad an extra byte, and then ban all others that do ot do that. Apr 15 09:57:51 jonwil: or just don't care about it Apr 15 09:57:59 jonwil: use ssh + some other client Apr 15 09:58:25 yeah Apr 15 09:59:30 ceene: do you get a protocole version number from whatsapp at first connection attempt? Apr 15 09:59:54 I guess their client has a way of knowing protocole has changed and they should upgrade Apr 15 10:07:06 debian packaging question ... i once built a package for maemo (irssi with perl support), and created a deb. however, that deb actually included the source files too. :p Apr 15 10:07:10 where did i go wrong? Apr 15 10:12:06 wizzup: banning on change of protocol without making sure most users upgraded would surely ban many legitimate users Apr 15 10:12:17 unless they implement 'upgrade first then connect' Apr 15 10:14:11 they do Apr 15 10:14:32 users who suddenly cannot connect know they have to upgrade Apr 15 10:14:52 it is a rather messy system Apr 15 10:15:02 nope, i meant something different Apr 15 10:15:17 client that wouldnt even allow connecting after version check Apr 15 10:15:33 otherwise trying to connect == ban Apr 15 10:20:46 i understand you now Apr 15 10:20:58 and just to add insult to injury my internet went off ¬¬ Apr 15 10:21:51 your isp banned you for using unauthorized device Apr 15 10:21:53 ;) Apr 15 10:22:29 na, the lights went off Apr 15 10:22:40 how is it called in english? Apr 15 10:22:42 the thingy Apr 15 10:22:45 the general switches Apr 15 10:23:13 blackout Apr 15 10:23:21 not exactly Apr 15 10:23:32 only a section of the distribution network Apr 15 10:23:35 we did have lights Apr 15 10:23:40 but no switches or network devices Apr 15 10:23:52 i'm goona be testing libwa on the device itself Apr 15 10:23:58 i'm thinking that this segfaults aren't normal Apr 15 10:24:04 and maybe are caused by scratchbox Apr 15 10:25:36 ceene, segv with different debug flags/code paths means bad pointers somewhere Apr 15 10:28:04 the piece of shit that is qt shouldn't segfault as much Apr 15 10:28:11 i've never had so many segfaults on my simple C code Apr 15 10:28:19 :) Apr 15 10:28:29 complex code == bugs Apr 15 10:28:52 especially code that was modified during development Apr 15 10:34:03 ok Apr 15 10:34:07 this is not libwa's fault Apr 15 10:34:08 it can't be Apr 15 10:34:19 this shit is segfaulting when entering an empty method Apr 15 10:35:35 calling convention issues? (doubt it) Apr 15 10:36:20 my guess is scratchbox Apr 15 10:36:26 or my scratchbox installation Apr 15 12:06:52 Mussorgsky album art lookup is not working. Well, restart might cure that... Apr 15 12:15:55 Searching (album + artist): https://www.google.com/search?tbm=isch&q=Quincy%20Jones+Mackenna%27s%20Gold&tbs=isz:m&iar:s Apr 15 12:15:58 Can't find URL in results Apr 15 12:16:00 No image results returned Apr 15 12:16:12 Mussorgsky ^ Not finding album art Apr 15 12:18:04 And, bibisco is pre-compiled for linux32, but apparently not for armel (doesn't work out of the box, in short). Apr 15 12:29:23 Maepad is nice... Dependencies list looks complicated, though Apr 15 12:58:52 ceene: ask council resp repo maintainer ( merlin1991) to lock or delete yappari if that is what you want Apr 15 13:03:53 * stryngs calculates the Traveling Salesman algorithm via his n900... Apr 15 13:04:11 isnt there a solution on google already? Apr 15 13:05:21 No... Apr 15 13:05:24 Still worth 1 Mil Apr 15 13:15:54 there is a marble plugin but I don't think it's compiled for n900 Apr 15 13:25:43 ok, this code seems to work on n900 without segfault Apr 15 13:34:26 ceene: do you still need to lock yappari repo? Apr 15 13:39:14 DocScrutinizer05: no, that's okay Apr 15 13:39:18 i uploaded an empty package Apr 15 13:39:34 and i've made it very very explicit that no one should use yappari Apr 15 13:55:50 ok, so you don't need repo admin action Apr 15 13:56:20 one off my todo list :-) Apr 15 15:39:15 ramose: why don't you use already working one? Apr 15 15:51:58 Could do with getting email working on my stable N900 again within the week or so. Any other email clients available that will work? Apr 15 15:52:20 firefox? Apr 15 16:03:19 umm, istn't there a lot of them, like claws etc? Apr 15 16:04:22 mutt Apr 15 16:04:38 * Sicelo uses it 90% of the time on N900 Apr 15 16:05:05 firefox o.O Apr 15 16:05:33 swb: if you have webmail option, there are webmails that arent heavy on js Apr 15 16:05:44 which means they probably work with microb too Apr 15 16:06:19 and yeah, mutt/pine/alpine Apr 15 16:06:24 I would be happy with modest if it still worked on stable. Although I don't know what is actually broken. It's for work so no web mail option. Apr 15 16:06:53 stable might have deprecated/banned certs Apr 15 16:07:43 sixwheeledbeast: work? exchange? or IMAP/POP? Apr 15 16:10:11 Sicelo: I am guessing POP but I don't know yet, only they are giving If-fones to everyone for company email Apr 15 16:11:37 if it's certs then another client may not solve the issue then, hm Apr 15 16:11:50 try it :) Apr 15 16:12:02 also test with openssl s_client Apr 15 17:46:29 argh, i have so many things to do Apr 15 17:46:36 i made a port of openssl1.0.2 Apr 15 17:46:49 watch some kittens, it will ease the pain, watch them Apr 15 17:47:00 i've finished watching today The night manager Apr 15 17:47:11 no kittens but spies, which are cool in their own way Apr 15 17:47:22 the night kittehs Apr 15 17:47:25 :D Apr 15 17:47:44 i have a cat myself, nowadays she lets me sleep Apr 15 17:47:53 must be getting old Apr 15 17:47:55 :) Apr 15 17:48:20 no, she goes to purrrrrr over my gf Apr 15 17:48:27 and i can sleep, but she can't Apr 15 17:48:32 a decoy! Apr 15 17:49:11 talking about cats: Apr 15 17:49:14 https://www.facebook.com/dailypicksandflicks/videos/vb.168146169872122/1110961762257220/?type=2&theater Apr 15 17:55:15 "... just seconds before the crash" ;-P Apr 15 17:56:59 :D Apr 15 18:30:22 libqt4-core (>= 1:4.7.4~git20110505) Apr 15 18:30:24 where is that? Apr 15 18:30:26 in which repo? Apr 15 18:30:46 ah Apr 15 18:30:47 nah Apr 15 18:30:47 forget it Apr 15 18:31:25 this is incredible, i am the sole maintainer of yappari and can't find a .deb i can install on this scratchbox installation Apr 15 18:31:28 :D Apr 15 18:31:55 #tooDrunkToCode ? Apr 15 18:32:03 not yet Apr 15 18:32:17 ahm, the %% peak incoming Apr 15 18:32:43 https://xkcd.com/323/ Apr 15 18:32:44 ;) Apr 15 18:34:41 there's truloy an xkcd for everything Apr 15 18:35:52 https://xkcd.com/968/ Apr 15 18:36:01 and of course: https://xkcd.com/231/ Apr 15 18:40:42 Eres un gato! Apr 15 18:40:53 that's what I tell my cat Apr 15 18:40:56 a lot, to be honest Apr 15 18:46:28 hello Apr 15 18:46:35 i am trying to flash emmc on n900 Apr 15 18:46:43 ~flashing Apr 15 18:46:44 from memory, maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline Apr 15 18:47:34 but the flasher doesnt start, here's paste from console http://pastebin.com/raw/JXVpcxnz Apr 15 18:48:00 old flasher Apr 15 18:48:03 grab 3.5 Apr 15 18:48:12 in the link above Apr 15 18:52:30 i have 3.5 Apr 15 18:52:45 flasher v2.5.2 (Sep 24 2009) Apr 15 18:52:52 why does it say 2.5.2 then? Apr 15 18:53:02 maemo_flasher-3.5_2.5.2.2_i386.deb to be exact Apr 15 18:53:06 ahm Apr 15 18:54:23 try another usb port? Apr 15 18:54:37 or cable? or os? Apr 15 18:55:33 btw. is it in bootloop? Apr 15 18:56:52 yes it is Apr 15 18:57:06 low battery maybe? Apr 15 18:57:13 well, i tried flashing the COMBINED image firsst and it works Apr 15 18:57:35 try booting rescueos and charge it using the script Apr 15 18:57:37 maybe i'll try it after its flashed Apr 15 18:58:32 but if it has enough battery still just use the script from factoid infobot said Apr 15 18:59:01 hey it works now Apr 15 19:01:09 boot sure is taking its time.... Apr 15 19:02:06 yes, 1st boot does Apr 15 19:02:49 hey what do you know, it actually didn't freeze Apr 15 19:02:55 who woulda thought Apr 15 19:04:19 i guess you know about cssu? Apr 15 19:04:58 yeah sure but its been *years* since i last messed around with n900 Apr 15 19:05:13 is https://wiki.maemo.org/N900_The_Perfect_Setup#Initial_Firmware_Setup still relevant? Apr 15 19:05:24 you might be interested in cssu-thumb if you like nice tricks Apr 15 19:05:24 i mean the whole article Apr 15 19:05:34 nah, the article isnt authoritative Apr 15 19:05:39 but some tips are ok Apr 15 19:05:48 never really was Apr 15 19:06:19 one man's perfect setup is another man's WTF of the week Apr 15 19:06:58 i remember trying to use swappolube and slight OC to make the device more smooth Apr 15 19:07:13 so is this cssu-thumb the real deal? Apr 15 19:07:25 i mean swappolube didn't do much for me at least Apr 15 19:07:28 no Apr 15 19:07:28 yup, few megs of ram more to play Apr 15 19:07:58 but should be treated as 'testing' Apr 15 19:08:00 yeah i dont understand the technicalities of it but i'll give it a shot Apr 15 19:08:06 cssu-thumb is *one* way to go ahead, though this particular one has some intrications you should be aware of Apr 15 19:08:30 for sure not recommended for 'noobs' Apr 15 19:08:34 yeah like it cant run normal stuff right? Apr 15 19:08:39 you can Apr 15 19:08:58 it can run normal stuff, but you can't run the whole system on a stock kernel Apr 15 19:09:31 yeah i know its not for noobs but i never listen to that kind of warnings Apr 15 19:09:37 which has quite nasty little implications to watch out for, during backup/restore and reflashing Apr 15 19:09:52 tiss: but if you just flashed its the perfect time to try it out Apr 15 19:10:06 whats that about implications Apr 15 19:10:21 as long you flash thumb enabled kernel you are fine Apr 15 19:10:32 which means either cssu kernel or powerkernel Apr 15 19:10:39 just not the stock one Apr 15 19:11:08 so first things first Apr 15 19:11:16 1/ install cssu Apr 15 19:11:20 2/ go cssu-thumb Apr 15 19:11:28 but going straight to 2 might work too Apr 15 19:11:31 for example you reflash your device to recover from a broken kernel or whatever. Now you hope you can use the apps that were not touched by the COMBINEd replash in /home. You can't since they might be thumb binaries which give you an unbootable system Apr 15 19:11:58 ~csssu-thumb Apr 15 19:11:58 COMBINED reflash* Apr 15 19:12:04 ~cssu-thumb Apr 15 19:12:04 cssu-thumb is probably [thumb2 microb] indeed seems to render like mad, subjectively, or http://talk.maemo.org/showpost.php?p=1220597, or http://wiki.maemo.org/Community_SSU/Thumb Apr 15 19:12:28 now just hole up Apr 15 19:12:57 you're maybe better off with: Apr 15 19:13:01 ~jrtools Apr 15 19:13:01 jrtools is probably http://wiki.maemo.org/User:Joerg_rw/tools Apr 15 19:13:05 so if i install thumb then reflashing may be difficult? Apr 15 19:13:05 for first steps Apr 15 19:13:10 tiss: nope Apr 15 19:13:16 reflash always works Apr 15 19:13:17 than with this 'perfect setup' Apr 15 19:14:01 he was talking about this scenario: cssu-thumb -> backup menu backup -> reflash with stock -> backup menu restore will fail Apr 15 19:14:02 ah alright now i get it Apr 15 19:14:05 tiss: yes, exactly. reflashing is rather a sure way to get a broken system, after you went to cssu-thumb Apr 15 19:14:20 wait now i dont get it again Apr 15 19:14:23 but if you flash thumb enabled kernel as a first thing after reflash its ok Apr 15 19:15:03 you can reflash your complete system and thus return to stock maemo. reflashing only COMBINED will break a thumb system Apr 15 19:15:17 yeah i can live with that Apr 15 19:16:14 anyway you can go stock/CSSU -> thumb any time. So no hurries and no complications in an early stage of making friends with maemo (again) Apr 15 19:16:36 is what I'd recommend Apr 15 19:17:03 IOW you don't need thumb to be happy with your N900 Apr 15 19:17:18 well i go ham and go ahead with the thumb thing Apr 15 19:17:19 it's not a decision you need to do on day1 Apr 15 19:18:02 I *strongly* suggest to first go for cssu-testing or even cssu-stable first and then use this setup for a few weeks before you go thumb Apr 15 19:18:50 i always went with stable before Apr 15 19:18:56 there's enough to tweak and customize before you might consider using thimb to tune your device a bit more Apr 15 19:19:51 let me put it this way: when you buy a new car, it's not the N2O injection you retrofit first Apr 15 19:23:15 anyway is there a noticeable difference in using thumb vs normal cssu Apr 15 19:23:28 yes, as i said, more free ram Apr 15 19:23:36 is it hecking snappy as heck then? Apr 15 19:23:44 nah Apr 15 19:24:09 256M gets eaten by preloaded things quite wholly Apr 15 19:24:24 so you'll be able to open more windows at once then Apr 15 19:25:08 thats basically what its about then? Apr 15 19:25:18 diska space/ram Apr 15 19:25:46 but if you start opening windows it will go into swappyland anyway Apr 15 19:26:10 still, having 10-20M of free ram doesnt hurt, right? Apr 15 19:26:44 im inclined to answer "right" Apr 15 19:27:33 also, disabling few things that you dont use in the system also helps Apr 15 19:28:56 i guess i'll go with testing or the time being, seeing its got the lastest updates and all Apr 15 19:29:00 *for Apr 15 19:31:40 tiss: no, the thumb advantages are noticeable but not fundamental Apr 15 19:32:48 tiss: this is my version of 'perfect' setup: https://wiki.maemo.org/Slimming_OS Apr 15 19:32:50 you shouldn't notice any difference between CSSU-testing and CSSU-thumb, except for an occasional speed advantage Apr 15 19:33:40 the device will enter swap hell a tad later, thanks to thumb binaries being smaller and thus eating less RAM Apr 15 19:34:01 so basically thumb is like adding another 25% of RAM Apr 15 19:34:40 loading executables from flash might also speed up slightly since you got less data to read in Apr 15 19:36:08 well heck Apr 15 19:36:11 maybe ill toss a coin Apr 15 19:36:23 heads for testing tails for thumbing Apr 15 19:36:37 you should NOT go for thumb right away. You can do this any time later Apr 15 19:36:49 well i got heads anyway Apr 15 19:37:00 hehe Apr 15 19:37:24 you will be able to compare memory/speed then when you decide going thumb Apr 15 19:38:32 i didn't see much difference myself, but then, my N900 has 5 year-old cruft. otoh, i do think thumb is worth it Apr 15 19:39:34 yup, we would get much more if we could disable parts of the os Apr 15 19:39:51 * DocScrutinizer05 idly wonders if BM could simply save the needed files, and trigger a dpkg -i $recent_kernel_package after restore Apr 15 19:40:18 its nice to have mail client preloaded, but what if one never used/uses it? 10M eaten senselessly Apr 15 19:40:33 thats a lot of libqtm packages Apr 15 19:41:03 Sicelo: thumb is worth it for sure (though I don't use it simply because of what I mentioned above) - however it's _not_ recommended for day1 Apr 15 19:41:42 of course. agreed Apr 15 19:42:20 tissi doesn't sound too new otoh. not saying he must :) Apr 15 19:43:06 well, he's dealing with "https://wiki.maemo.org/N900_The_Perfect_Setup#Initial_Firmware_Setup Apr 15 19:43:13 yeah i had this device for years Apr 15 19:43:17 she? Apr 15 19:43:20 never became much of a pro though Apr 15 19:43:45 n900 headphone jack crapped out on me so i returned to this device Apr 15 19:43:49 *n9 Apr 15 19:43:57 oh, audio user? Apr 15 19:44:18 might i interest you in my audio player for n900? Apr 15 19:44:22 more like audio listener Apr 15 19:44:28 ~flashing-cmdline Apr 15 19:44:29 flashing-cmdline is, like, http://mg.pov.lt/maemo-irclog/%23maemo.2016-04-09.log.html#t2016-04-09T01:18:12 Apr 15 19:44:30 im aware of oscp if thats where you're going Apr 15 19:44:43 yes, what do you think of it? Apr 15 19:45:30 maybe its because prior to flashing n900 just now everything was all over the place and not working quite right Apr 15 19:45:36 so oscp also didnt function perfectly Apr 15 19:45:45 playback would stop after track finishes Apr 15 19:45:51 so i had to manually select next track every time Apr 15 19:45:57 i think i told you of this issue earlier Apr 15 19:46:04 which version? Apr 15 19:46:12 donatello / salamisami if you remember Apr 15 19:46:21 i think i was fixing it at some point Apr 15 19:46:22 im pretty sure it was the latest Apr 15 19:46:33 well not 100% sure but anyway Apr 15 19:46:57 i ended up deciding to flash the thing actually because for some reason the n900 would freeze and reboot itself after a while of playing music Apr 15 19:47:02 could be also that i've fixed it on pc and forgot to make a package Apr 15 19:48:07 29-Nov-2015 Apr 15 19:48:08 hrm Apr 15 19:48:20 im not sure if i had the latest version Apr 15 19:48:21 definitely i should make a package Apr 15 19:48:31 or maybe i did heck i dont remember when i last used oscp Apr 15 19:49:08 i moved my audio playing tasks from n900 to banana pi last year Apr 15 19:49:16 :) Apr 15 19:49:22 for those who didn't notice: http://mg.pov.lt/maemo-ssu-irclog/latest.log.html#t2016-04-15T22:04:31 Apr 15 19:49:34 freemangordon: congrats and kusos Apr 15 19:49:39 kudos even Apr 15 19:57:48 anyone got any wack ass boot videos? Apr 15 19:58:15 something really obnoxiously "h4ck3r" would be swell Apr 15 19:58:45 Don't Panic Apr 15 19:58:46 or alternatively something like drake's hotline bling Apr 15 19:58:55 but most of us remove it completely Apr 15 19:59:22 tissi: DONT PANIC! Apr 15 19:59:26 ~jrtools Apr 15 19:59:26 hmm... jrtools is http://wiki.maemo.org/User:Joerg_rw/tools Apr 15 19:59:39 http://www.quadronyx.org/mirror/maemo/boot_videos/killer.avi rofl Apr 15 20:00:25 (dont panic) I *think* somebody even packaged it Apr 15 20:01:58 http://maemo.org/packages/view/dontpanic/ Apr 15 20:03:33 http://maemo.cloud-7.de/maemo5/bootvideo-DONTPANIC/ Apr 15 20:03:55 http://maemo.cloud-7.de/maemo5/bootvideo-DONTPANIC/dontpanic.avi Apr 15 20:05:22 tissi: you should bookmark http://maemo.org/packages/ Apr 15 20:05:45 alright Apr 15 20:05:52 well i settled with just disabling the hands video Apr 15 20:06:07 for now Apr 15 20:06:15 :-) Apr 15 20:06:38 zx tape loader was cool but 24 seconds? come on Apr 15 20:07:28 * DocScrutinizer05 had DONT PANIC even on GTA02 :-) Apr 15 20:07:54 bootloader splashscreen Apr 15 20:25:35 so which kernel do i install now Apr 15 20:25:45 wont be going for thumb yet Apr 15 20:27:02 http://maemo.org/downloads/product/Maemo5/kernel-power-flasher/ this one best? Apr 15 20:30:00 yep Apr 15 20:30:22 afaik Apr 15 20:31:10 you don't want to install the overclocking stuff (UI) Apr 15 20:31:17 prolly Apr 15 20:36:17 nah i've done it before had no problems with it Apr 15 20:36:33 my device can certainly handle 720mhz just fine Apr 15 20:40:49 yes, it can Apr 15 20:40:57 just it's basically useless Apr 15 20:41:18 how so? Apr 15 20:41:19 ~720/600 Apr 15 20:41:20 1.2 Apr 15 20:41:31 well how about 850? Apr 15 20:41:46 btw isnt it just fine to set the min clock to 125 s well Apr 15 20:42:03 since it'll automatically scale and all or what? Apr 15 20:43:05 it's a known fact that speed improvements in UIs only get really noticed when in the range of factor 2 or higher, and a factor 1.2 is probably not even noticeable when you tell the tester that there is some speed difference they should look for Apr 15 20:44:32 125 is considered instable, and you don't really need it anywaqy since maemo has a run-to-idle general approach Apr 15 20:45:19 okay okay Apr 15 20:45:28 you best don't assume Nokia had a funny idea of arbitrarily limiting the performance of the device without reason Apr 15 20:45:30 but undervolting is still smart? Apr 15 20:45:58 didn't some samsung phone basically have the identical cpu as n900 Apr 15 20:46:06 but clocked higher to 800-something Apr 15 20:46:21 there are lots of devices that "have the same CPU *basically*" Apr 15 20:46:56 TI procuses lots of chip flavors, and they get even binned after production Apr 15 20:47:25 Nokia for sure didn't buy same binning of the SoC like Samsung did Apr 15 20:48:29 still, undervolting = good and smart as advised by https://wiki.maemo.org/Overclocking#Undervolting Apr 15 20:48:36 right? Apr 15 20:48:50 for sure its fine Apr 15 20:49:04 less voltage could never hurt things Apr 15 20:49:11 yeah i'll go ahead and do that Apr 15 20:49:13 Nokia just might have ordered another operation-time-to-failure than Samsung, since they want their devices to live longer or shorter than Samsung Apr 15 20:50:00 undervolting is just begging for less stability Apr 15 20:50:22 oh looks like its already enabled by default by the power kernel v53 Apr 15 20:50:36 at least both the smartreflex vdd values are already 1 Apr 15 20:53:11 smartreflex is not undervolting Apr 15 20:53:12 N900 doesn't need user configuration of basic system parameters. It's supposed to ship with proven good values, either in stock kernel (takes care of some more fringe cases) or in powerkernel which got tested by a lot of people and has a setting considered optimized as long as you're not a hardcore hacker trying to test some new leete fringe case Apr 15 20:54:19 smartreflex been tagged "non-stable" by Nokia and TI devels in the N900 prototypes. Maybe meanwhile it usually works on the newer silicon in series devices Apr 15 20:55:29 ~sr Apr 15 20:55:30 [SmartReflex] >>Again, TI and we [Nokia] couldn't fix SmartReflex - we say memory corruption in front of our own eyes with that enabled, so we had to ship that disabled.<< Apr 15 20:56:41 hey by the btw way is there still any browser nicer than the default nokia web browser? Apr 15 20:57:48 ceene has found Midori through Easy Debian to work very well for his needs Apr 15 20:58:11 i still use MicroB. others prefer Opera Mini (I removed it) Apr 15 20:58:20 what about that one Apr 15 20:58:34 looked like microb Apr 15 20:58:37 but was new Apr 15 20:58:44 cant remember the name Apr 15 20:59:01 qml-browser? no comment .. didn't work well for me Apr 15 21:00:27 yeah qml browser Apr 15 21:00:30 yeah didnt work for me either Apr 15 21:00:36 was wondering if there was any progress Apr 15 21:01:16 i use fennec at times Apr 15 21:01:51 too cumbersome Apr 15 21:01:55 imho Apr 15 21:01:56 tbh, midori does work better as ceene mentions. Apr 15 21:04:58 Note that Opera Mini does everything through Opera's rendering proxies. Apr 15 21:05:17 (Opera Mobile doesn't though) Apr 15 21:05:30 well, I think there's an option to do it there. Apr 15 21:05:50 is there any other better irc client than xchat? Apr 15 21:06:05 * Sicelo009N uses irssi Apr 15 21:06:18 * Maxdamantus does too. Apr 15 21:06:28 i wanted to use weechat Apr 15 21:06:30 opera mobile does too if you activate Turbo mode .. Apr 15 21:06:35 though a simple answer would be: HexChat. Apr 15 21:06:43 Linkandzelda: check repos, or build :) Apr 15 21:06:48 XChat was abandoned a number of years ago and forked into HexChat. Apr 15 21:06:55 because the maintainer became unresponsive. Apr 15 21:07:06 i build my irssi for my own perl needs Apr 15 21:07:07 well there's no hexchat for n900 right? Apr 15 21:07:43 Dunno, but it shouldn't be hard to compile it. Apr 15 21:08:09 [2016-04-10 Sun 20:36:01] a 2020 website won't even fit on our ram, however [2016-04-10 Sun 20:36:12] so it won't mind much at all Apr 15 21:08:11 [2016-04-10 Sun 20:37:15] in 2020 I probably stopped using web, that's an insane development in a number of aspects and I don't want to participate in such insanity [2016-04-10 Sun 20:38:29] when it's more lightweight to run VNC to a web rendering server than to use plain HTML, something went massively wrong on a design and architecture level Apr 15 21:08:24 If it's similar to XChat it should have fairly standard dependencies (glib, gtc, etc) Apr 15 21:08:31 s/gtc\>/gtk/ Apr 15 21:08:32 how can i delete all the preset internet radio stations Apr 15 21:08:38 the fast way i mean Apr 15 21:09:26 Linkandzelda: there's xchat Apr 15 21:09:52 aah you asked for a better client than xchat Apr 15 21:10:06 prolly depends on your definition of "better" Apr 15 21:10:42 well xchat does the job really, its just pretty cluttered with the ui Apr 15 21:11:25 umm, adjust it. I agree the default settings are massively useless Apr 15 21:11:40 is there a command i can send in the terminal to give a notification to the system? like the ones that show up when you get an sms Apr 15 21:11:56 http://wiki.maemo.org/User:Joerg_rw/xchat/ Apr 15 21:11:57 as for adjusting it, i removed a lot of stuff from it so its much better Apr 15 21:12:02 dbus-foo .. Apr 15 21:12:17 ~phonecontrol Apr 15 21:12:17 i heard phonecontrol is http://wiki.maemo.org/Phone_control Apr 15 21:12:19 but phone-control package makes it easier Apr 15 21:12:39 nice Apr 15 21:12:50 i could try to get weechat to send notifications Apr 15 21:15:06 you could try if my settings and 'hacks' with xchat please you better Apr 15 21:15:59 im still kinda miffed about the camera being unable to launch without the magnet in the back cover Apr 15 21:16:16 i already bought one new backcover but the magnet fell off or something Apr 15 21:16:28 http://wiki.maemo.org/User:Joerg_rw/xchat/notify.sh http://wiki.maemo.org/User:Joerg_rw/xchat/loginhost.xsh http://wiki.maemo.org/User:Joerg_rw/xchat/xchat.conf Apr 15 21:16:36 so cant use the camera... because no magnet even though the camera module itself is just fine Apr 15 21:16:38 and of course the keybindings too Apr 15 21:17:16 DocScrutinizer05: going to check those out, thanks Apr 15 21:17:40 tissi: how about just getting a new magnet in place? Apr 15 21:18:04 well i would need to do that Apr 15 21:18:27 so i havent done it Apr 15 21:18:29 yes, the self-fixer in maemo is out of order ;-) Apr 15 21:19:19 there are hacked kernel modules that assume magnet always there Apr 15 21:22:40 is the config files in .xchat2? Apr 15 21:23:13 Why hack the kernel? It should be a matter of hacking something in userspace. Apr 15 21:23:16 Probably camera-ui. Apr 15 21:23:58 though you don't even need a magnet. Apr 15 21:25:29 hacker kernel modules you say Apr 15 21:25:58 i noticed when i had my back off when i put it down the camera opened... could be useful? Apr 15 21:26:11 * Maxdamantus made a modified omap_hsmmc so it wouldn't make the SD card inaccessible when the back cover was removed. Apr 15 21:31:47 DocScrutinizer05: how do i use this notify.sh? Apr 15 21:32:47 place it into the .xchat2(?) folder Apr 15 21:33:10 ok, did that Apr 15 21:33:18 wondered if there is any other step Apr 15 21:33:29 http://wiki.maemo.org/User:Joerg_rw/xchat/xchat.conf >> sound_command = /home/user/.xchat2/notify.sh << Apr 15 21:33:41 ah Apr 15 21:33:56 ;-) Apr 15 21:35:21 pretty convenient yet simple hack Apr 15 21:36:01 you could even make notify.sh do different actions based on the (soundfile) parameter passed to it by xchat Apr 15 21:37:30 most of this is completely transparent to xchat and can get set up via xchat's setting GUI Apr 15 21:38:11 what was the package to watch .mkv videos and other stuff Apr 15 21:38:55 gstreamer-plugins-ultranasty ? Apr 15 21:39:25 ;-) Apr 15 21:39:50 oh heck Apr 15 21:40:26 I have no clue Apr 15 21:40:30 cant get it to play for some reason, DocScrutinizer05 Apr 15 21:40:42 umm, check permissions Apr 15 21:40:52 i gave it +x Apr 15 21:41:02 chmod a+x ~/.xchat2/notify.sh Apr 15 21:41:58 IroN900:~# ll ~user/.xchat2/ Apr 15 21:42:00 insgesamt 60 Apr 15 21:42:01 -rw------- 1 user users 186 2016-02-02 15:04 chanopt.conf Apr 15 21:42:03 -rw------- 1 user users 1065 2015-11-22 22:36 colors.conf Apr 15 21:42:04 -rw------- 1 user users 0 2016-02-02 15:04 ignore.conf Apr 15 21:42:06 -rw------- 1 user users 1003 2011-09-20 19:28 keybindings.conf Apr 15 21:42:07 -rw------- 1 user users 0 2016-02-02 15:04 notify.conf Apr 15 21:42:09 -rwxr--r-- 1 user users 180 2009-12-18 15:42 notify.sh Apr 15 21:42:10 -rw------- 1 user users 10714 2010-07-16 01:51 pevents.conf Apr 15 21:42:12 drwxr-xr-x 8 user users 4096 2015-09-04 23:45 scrollback Apr 15 21:42:13 -rw------- 1 user users 9135 2016-01-19 21:57 servlist_.conf Apr 15 21:42:15 -rw------- 1 user users 400 2016-02-02 15:04 sound.conf Apr 15 21:42:16 -rw------- 1 user users 0 2009-12-13 05:45 sound.confback Apr 15 21:42:18 -rw------- 1 user users 3632 2016-02-02 15:04 xchat.conf Apr 15 21:42:19 -rw------- 1 user users 121 2012-12-20 15:07 xchat-login.xsh Apr 15 21:42:21 drwx------ 2 user users 4096 2011-03-10 02:37 xchatlogs Apr 15 21:42:22 you need sound.conf of course Apr 15 21:42:40 or do it via xchat settings Apr 15 21:43:09 huh looks like the camera doesnt respond even with my strongest fridge magnet Apr 15 21:43:14 well screw that Apr 15 21:43:39 http://paste.opensuse.org/43664105 Apr 15 21:43:40 would just use it to take pics of myself and become more self conscious anyway Apr 15 21:43:55 tissi: you don't need extremely stron magnets Apr 15 21:44:10 well fridge magnets arent exactly extremely strong Apr 15 21:44:21 there's just zero response Apr 15 21:44:31 DocScrutinizer05: i have sound.conf but its empty Apr 15 21:45:09 tissi: cat /sys/class/mmc_host/mmc0/cover_switch Apr 15 21:46:45 DocScrutinizer05: great colors btw Apr 15 21:47:25 says closed Apr 15 21:47:42 echoing "open" wouldnt work right? Apr 15 21:47:49 any magnet paced to the little 'pool' next to camera should do Apr 15 21:48:16 closed is what means "there's a magnet" Apr 15 21:48:35 how can there be a magnet Apr 15 21:48:37 echoing anything into this sysnode doesn't work Apr 15 21:48:52 when the back cover isnt even in place Apr 15 21:49:04 hw defect? Apr 15 21:49:15 Linkandzelda: you need some content in it ;-D Apr 15 21:49:18 wait oh wait Apr 15 21:49:20 it says open Apr 15 21:49:32 but still the camera application says "open lens cover" Apr 15 21:49:56 DocScrutinizer05: i figured, but i have no idea what Apr 15 21:50:28 use the settings GUI to define the events you want to cause a highlight&sound, and which Apr 15 21:50:28 when i place the n900 on my desk Apr 15 21:50:35 the camera actually functions Apr 15 21:50:45 and when i take it off the application closes Apr 15 21:50:49 but briefly i can see the camera image Apr 15 21:50:54 http://paste.opensuse.org/43664105 for a suggestion Apr 15 21:51:37 tissi: that's the infrared proxy sensor testing for black or white zone on the cam door slider Apr 15 21:52:13 sooo... watnou Apr 15 21:52:23 when you got a new battery cover, it possibly lacks that paper sticker with the black and white zone Apr 15 21:53:08 nah its there Apr 15 21:54:57 hey, is there a way to check battery condition? Apr 15 21:55:10 how much charge it can hold vs factory capacity Apr 15 21:57:23 crap the battery fell out Apr 15 21:57:27 time and date reset again Apr 15 21:57:42 hey, automatic time update doesnt work Apr 15 21:57:49 or do i need to have a simcard for that? Apr 15 21:58:01 it wont pick the time from my wifi at least Apr 15 22:02:21 (( or do i need to have a simcard for that?)) yes Apr 15 22:02:37 yeah i realized it after googling Apr 15 22:02:41 unless you install ntpdate Apr 15 22:02:47 maybe i should practice more self censorship Apr 15 22:03:22 ((hey, is there a way to check battery condition?)) Apr 15 22:03:27 ~bq27 Apr 15 22:03:27 bq27 is, like, http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/ Apr 15 22:07:22 heck, I can't find the sysnode for cam door IR proxy Apr 15 22:08:53 cat /sys/devices/platform/gpio-switch/cam_shutter/state Apr 15 22:09:36 open|close as you'd expect Apr 15 22:09:47 tissi: ^^^ Apr 15 22:13:03 tissi: closed is black, open is white. When your sensor doesn't detect white of your cover, then there's something pretty odd Apr 15 22:13:37 sec Apr 15 22:13:50 the sensor however seems to be ok since it detects a table as white Apr 15 22:14:17 so something must be odd with your cover Apr 15 22:15:29 cat returns closed Apr 15 22:15:30 since you said you got a replacement cover, I'd not be too surprised to find something odd with it Apr 15 22:15:44 hey it was supposedly german Apr 15 22:15:49 superior german engineering man Apr 15 22:15:54 tz Apr 15 22:17:52 gahh it stopped working again Apr 15 22:17:57 DocScrutinizer05: sounds working, thanks :) Apr 15 22:17:57 now it wont detect table Apr 15 22:19:08 http://maemo.cloud-7.de/share-service/20160416_003.jpg Apr 15 22:19:38 you shouldn't test with table Apr 15 22:20:05 yeah it looks 100% like that Apr 15 22:20:27 btw you also see the backside of the magnet there Apr 15 22:20:41 wait now it detects again Apr 15 22:20:48 wheres the magnet exactly Apr 15 22:21:01 the wide rectangle right side attached to that vertical bar Apr 15 22:22:25 i still dont get it Apr 15 22:26:04 please do http://paste.opensuse.org/20286135 Apr 15 22:26:50 cya, afk for dinner etc Apr 15 22:30:14 even better: watch -n 0,2 -d cat /sys/devices/platform/gpio-switch/cam_shutter/state Apr 15 22:33:16 even better yet: watch -n 0,2 -d cat /sys/devices/platform/gpio-switch/cam_shutter/state /sys/class/mmc_host/mmc0/cover_switch Apr 15 22:34:01 use a magnet to make second one read "closed" then try what happens when you slide open the cam shutter Apr 15 22:35:03 invalid number Apr 15 22:35:04 any normal magnet should suffice for that, in a distance lower than 1cm Apr 15 22:35:23 ummm Apr 15 22:35:33 try 0.2 instead 0,2 Apr 15 22:35:41 tried, same Apr 15 22:36:39 well, maybe that's my special version of watch whioch I pimped to use fractions of a second. Use -n 1 that works Apr 15 22:37:28 aaah yours is messybox watch applet, which again is Apr 15 22:37:32 ~messybox Apr 15 22:37:32 messy... err busybox is meant for lean scripting. Regarding all the missing options and immanent limitations (see su, passwd, nice, ps, diff as used by mc...) it's not really the interactive shell of choice. A lot of people hate busybox because a lot of system integrators don't understand the difference between busybox and a decent user interactive shell plus unix utils Apr 15 22:38:24 instead of a recursive list of "closed" "open" the screen just flashes two instances of either and refreshes Apr 15 22:38:47 oh thats the idea Apr 15 22:39:22 both read "closed" by default... Apr 15 22:39:38 putting a magnet near does nothing Apr 15 22:40:16 both closed sounds OK, should be a magnet there Apr 15 22:40:40 remove cover, watch it go "open" Apr 15 22:41:10 first is cam door, second is magnet Apr 15 22:41:35 opening cover doesnt do anything Apr 15 22:41:35 magnet needs to be closed, cam door should be open/closed depending on... cam door Apr 15 22:41:36 nor does bringing magnet close Apr 15 22:41:57 cant get the readings to change Apr 15 22:42:07 that's pretty strange Apr 15 22:42:26 yeah im confused Apr 15 22:42:32 but thats by default Apr 15 22:42:33 hw defect? my 2nd N900 has hw defect preventing it from detecting mmc Apr 15 22:42:57 yes, but usually you get a always-open then, I'd guess Apr 15 22:43:01 removing th back cover of the n900 entirely does change the second one to open Apr 15 22:43:18 I told you to do that, didn't I? Apr 15 22:43:41 so your cover has a magnet and the sensor works great Apr 15 22:43:44 aaand putting the device on table changes both to open Apr 15 22:43:54 i thought you were telling me about the lens cover Apr 15 22:44:09 wait so wheres the problem then Apr 15 22:44:23 [2016-04-16 Sat 00:40:40] remove cover, watch it go "open" Apr 15 22:44:43 yeah yeah i thought you meant lens cover Apr 15 22:44:54 not battery cover Apr 15 22:45:07 oh heck the battery fell out again Apr 15 22:45:17 :) Apr 15 22:45:23 put on cover, slide open cam door, watch it go "open closed" Apr 15 22:45:30 sorry. it is rather loose Apr 15 22:45:42 no problem i forgive you Apr 15 22:45:55 bend springs in a bit so it sticks firmly Apr 15 22:46:10 really easy Apr 15 22:46:30 the steel springs at bottom end of battery Apr 15 22:46:48 use fingernail, no tools Apr 15 22:46:58 gently pull it a bit out Apr 15 22:47:29 there are two of those latches Apr 15 22:48:37 * DocScrutinizer05 away now for good. When you still don't see camera coming up a few seconds after "open closed", you got an issue with the camera app or DSP Apr 15 22:48:49 put on cover, slide open cam door, watch it go "open closed" Apr 15 22:49:07 cam door opening doesnt change anything Apr 15 22:49:10 thanks for your help though Apr 15 22:49:32 when cam door opening doesn't change anything, your 'white' isn't Apr 15 22:49:50 check your cover Apr 15 22:50:00 the white area on cam door Apr 15 22:50:18 it's not really white then, evidently Apr 15 22:50:36 yeah its more like grey Apr 15 22:50:52 or bluish hue Apr 15 22:51:10 bueish is bad for infrared light I guess Apr 15 22:51:28 stick some white paer there Apr 15 22:51:31 paper Apr 15 22:51:49 or white stickytape Apr 15 22:52:28 ok Apr 15 22:53:53 w0000t Apr 15 22:53:54 it worked Apr 15 22:53:59 :-) Apr 15 22:54:08 damn Apr 15 22:54:15 thanks a ton Apr 15 22:54:20 your food's getting cold tho Apr 15 22:54:20 there's hardly anything I can't fix, usually even remote ;-P Apr 15 22:54:42 you're my hero Apr 15 22:56:24 damn now i have a 100% functioning n900 Apr 15 22:56:45 seems my battery isnt improving, its got good standby time though (tte: 6-9k) when idling with no apps. when turned on though, tte: 150-300. guess i'll try to reflash and hope it changed something Apr 15 22:57:14 first calibrate Apr 15 22:57:44 did that Apr 15 22:57:54 what's LMD now? Apr 15 22:58:08 Last Measured Discharge: 1635 mAh Apr 15 22:58:13 off Apr 15 22:58:21 what should it be? Apr 15 22:58:40 calibration adjusts only 12% or sth, you need to repeat calibration until it settles to ~1200 Apr 15 22:58:56 i see Apr 15 22:59:04 resp settles, no matter where Apr 15 22:59:11 and is there any chance the battery itself is just old? Apr 15 22:59:17 sure Apr 15 22:59:47 alas the meter resets each time you remove battery Apr 15 23:00:04 makes sense since new battery might be a different one Apr 15 23:00:29 any way to tell with the data this script puts out? if its the battery itself? Apr 15 23:00:52 whats with the new camera application that came with the cssu Apr 15 23:01:00 how do i take video Apr 15 23:01:05 also the focus is a bit off Apr 15 23:01:19 well, you could monitor a charging from empty battery with a bq27200.sh 60 >batlog.txt Apr 15 23:01:27 oh the controls are a bit different Apr 15 23:01:30 found video Apr 15 23:02:08 when you're done (battery fully charged) provide the batlog.txt and I can tell you details Apr 15 23:02:31 ok, i will let it die until it turns itself off Apr 15 23:02:39 good Apr 15 23:03:10 then i'll plug in, boot, ssh, run script, and let it charge while idling and screen off Apr 15 23:03:25 for however long it takes Apr 15 23:03:25 already start bq27200.sh 60 >>batlog.txt, then start it again after plugging to charger Apr 15 23:03:39 ok Apr 15 23:03:51 note the double >> Apr 15 23:03:57 yea, append iirc Apr 15 23:04:03 yep Apr 15 23:04:48 you can even run this in a second shell, while other shell does calibrate Apr 15 23:05:13 E: Couldn't find package tmux Apr 15 23:05:15 aww Apr 15 23:05:23 tmux?? Apr 15 23:05:37 aah Apr 15 23:05:44 meh Apr 15 23:06:03 its the lazy mans "cant be bothered to open a second window" Apr 15 23:06:17 and does a really good job at it Apr 15 23:06:31 but in this case, second window it is Apr 15 23:06:52 yust run the job in background ;-) Apr 15 23:07:04 bq27200.sh 60 >>batlog.txt& Apr 15 23:07:12 ok that works Apr 15 23:07:37 stop it with kill % Apr 15 23:07:41 dang Apr 15 23:07:45 stop it with kill %% Apr 15 23:08:21 running calibrate too Apr 15 23:08:29 TTE: 3239 minutes Apr 15 23:08:35 or get it to foreground with fg Apr 15 23:08:53 background again with ^Z bg Apr 15 23:09:11 though that *sometimes* fails Apr 15 23:09:15 since its outputting nothing to the terminal i can leave it in the bg Apr 15 23:09:22 yep Apr 15 23:09:32 now cheers for good Apr 15 23:10:22 check with jobs Apr 15 23:10:37 guess i'll keep doing this cycle until it gets to that number for lmd Apr 15 23:11:14 that system of fg and bg is missing a crucial thing Apr 15 23:11:23 the ability to stop output from background processes Apr 15 23:11:34 http://paste.opensuse.org/1273034 Apr 15 23:12:31 yeah, linux shell lacks a means to change file handles when they are already opened Apr 15 23:12:49 actually I guess that's linux at large Apr 15 23:17:34 the shell should use pipes for stdin, stdout, stderr ;-) I'm planning since long to have different fonts or colors for stdout and stderr Apr 15 23:20:30 Linkandzelda: when the last LMD differs less that 12(?)% from previous LMD, it adjusted to the real value Apr 15 23:21:31 actually that 12% limit is deliberately implemented into bq27200 chip to avoid massive bogus LMD changes Apr 15 23:22:35 however from a log of bq27200.sh 60 you can read the actual measured LMD, rather than the limited/capped value that gets stored to the LMD register Apr 15 23:26:14 Linkandzelda: when you first start calibrate-bq27k.sh *before you plug in the charger at end of day, you can run a calibration cycle each day, with minimal impact to battery wear Apr 15 23:28:20 calibrate-bq27k.sh will notice there's a valid discharge cycle (VDQ) and immediately turns off charger, so plugging in charger doesn't start charging until battery got discharged sufficiently for completing the learning cycle, then charging gets enabled like normal Apr 15 23:38:14 you also might want to give bq27k-detail2.sh a try. It's my original design on which the rest is based. and it's the most verbose one Apr 15 23:38:39 ~battery-faq Apr 15 23:38:42 ~batteryfaq Apr 15 23:38:43 i heard batteryfaq is http://wiki.openmoko.org/wiki/Battery_Questions_and_Answers Apr 15 23:39:03 http://wiki.openmoko.org/wiki/Battery_Questions_and_Answers#That_bq27000_chip_seems_to_be_pretty_cool.2C_how_can_i_read_and_understand_its_raw_registers.3F Apr 15 23:45:59 (calculate *real* LMD from log) see http://maemo.cloud-7.de/maemo5/patches_n_tools/n900-bq27log_til_empty.log - you simply subtract the value of NAC in last line before "VDQ:0 EDV1:1" (194) from NAC of start of discharge where RSOC=100 (1377), the result is _real_ LMD Apr 15 23:47:33 ~1377-194 Apr 15 23:47:34 1183 Apr 15 23:48:12 for you it prolly will look like 1833-655 Apr 15 23:50:28 * DocScrutinizer05 feels tempted to massively improve http://maemo.cloud-7.de/maemo5/patches_n_tools/calibrate-bq27k.sh to do all that math plus optional logging like "bq27200.sh 60 >>batlog.txt", plus work with a nice GUI of sorts Apr 16 00:40:35 11:17:34 < DocScrutinizer05> the shell should use pipes for stdin, stdout, stderr ;-) I'm planning since long to have different fonts or colors for stdout and stderr Apr 16 00:40:39 It does. Apr 16 00:40:54 You can open files over the existing fd using exec. Apr 16 00:40:58 exec >foo.txt Apr 16 00:41:24 That should open the file, dup2 it over the 1 fd and close the original fd. Apr 16 00:43:25 (close the original fd from the open, that is—dup2 will close the original stdout fd) Apr 16 00:54:23 [2016-04-16 Sat 01:11:14] that system of fg and bg is missing a crucial thing Apr 16 00:54:25 [2016-04-16 Sat 01:11:23] the ability to stop output from background processes Apr 16 00:55:20 [2016-04-16 Sat 01:12:30] yeah, linux shell lacks a means to change file handles when they are already opened [2016-04-16 Sat 01:12:49] actually I guess that's linux at large Apr 16 00:56:01 Ah, well those aren't part of the shell anymore. Apr 16 00:56:08 except in being a child process of it. Apr 16 00:56:20 It evades me how this is related to a process closing own filehandles and opening them to a different destination Apr 16 00:57:27 You'd probably do something involving ptrace to swap fds in that case. Apr 16 00:57:44 * Maxdamantus wonders if someone's written such a tool. Apr 16 01:01:12 Doesn't look like it. Apr 16 01:01:29 Someone on SO basically suggests doing that manually, using gdb. Apr 16 01:07:11 * Maxdamantus might write one. Apr 16 01:08:01 swapfd 1234 1 >(sed 's/ //' >/tmp/fixed) Apr 16 01:12:18 sounds decent Apr 16 01:25:26 prolly a 'starting point' - at least for me if I'd try to understand how to tackle that: http://paste.opensuse.org/13602740 Apr 16 01:30:36 cat /proc/2971/fd/1 already results in 'funny' effects Apr 16 01:32:04 Yes, you basically need to make the other process do that (so it opens an fd belonging to the `swapfd` process) Apr 16 01:32:29 When you cat it you're just duplicating that fd into a new one in the cat process. Apr 16 01:33:11 echo -e "date\n" >/proc/2971/fd/0 Apr 16 01:33:59 a process' STDOUT filehandle is a pty's input Apr 16 01:34:19 and vice versa Apr 16 01:35:11 I didn't completely wrap my mind around that yet Apr 16 01:35:42 Yeah, and to change that you need to make the process open something else and overwrite that STDOUT (1) fd. Apr 16 01:36:04 which requires something like ptrace. Apr 16 01:36:25 The /proc/*/fd interface just lets you duplicate fds into other processes. Apr 16 01:36:27 just you can't make the process do that, unless you somehow insert code via GDB or sth Apr 16 01:36:41 You can do it using ptrace. Apr 16 01:36:54 It doesn't involve injecting code, just system calls. Apr 16 01:37:21 A process does some computation, invokes a system call and repeats. Apr 16 01:43:08 I would try tolocate the data structure that represents the file handle and replace its content by the content of a similar filehandle I prepared for the process Apr 16 01:44:04 There is no datastructure. Apr 16 01:44:09 The datastructure is in the kernel. Apr 16 01:44:28 At the process level, the file handle is the integer 1. Apr 16 01:44:43 in shell the filehandles you see (0, 1, 2, etc) are indizes into an array of file descriptor structures Apr 16 01:44:53 That's not just a shell thing. Apr 16 01:45:06 If you do `write(1, "foo", 3);` in your program, it writes to whatever the `1` fd is, according to Linux. Apr 16 01:45:20 If you strace a program that does that, you'll simply see exactly that code. Apr 16 01:45:39 in other processes the file descriptor data structures are no indexed array bit possibly static variables Apr 16 01:45:43 because the program is telling the kernel to write data at some address to the file descriptor 1. Apr 16 01:45:58 not "stdout", or "the file handle at some address" Apr 16 01:46:31 All processes ultimately use these read/write/etc calls, which address file descriptors using integers. Apr 16 01:46:57 When you use `stdout`, you're going through a `FILE *`, which is a C concept implemented by glibc. Apr 16 01:46:59 then the integer is an array index to a per-process table in kernel Apr 16 01:47:16 so that has a datastructure, but not all processes use `FILE *`s (which use fwrite, etc) Apr 16 01:47:38 Yes, but you can't practically modify that datastructure directly in the kernel. Apr 16 01:47:48 prolly not Apr 16 01:47:52 The best way to do that would be to just make the process do the system calls that have that effect. Apr 16 01:47:57 using ptrace. Apr 16 01:47:59 unless you are the kernel Apr 16 01:48:34 which is basically identical to "make process do the systemcalls" Apr 16 01:49:16 * DocScrutinizer05 idly wonders if debugfs has an API for that Apr 16 01:50:16 so you don't do the systemcalls from process space but via debugfs Apr 16 01:54:06 you prolly also could try to go via /dev/kmem Apr 16 02:01:10 you'd need to find the address of the kernel's process descriptor data structure for the process first, I guess Apr 16 02:01:38 then the rest should be relatively simple Apr 16 02:03:03 It wouldn't be relatively simple. Apr 16 02:03:08 What would you replace it with? Apr 16 02:03:09 since process descriptor table is fixed length, odds are that job is relatively simple too to find the process descriptor table and the right entry for your process you want to tweak in it Apr 16 02:03:12 How would you close that fd? Apr 16 02:03:50 I's simply swap two file descriptors, then close the old one in the donator process Apr 16 02:04:05 "the donator process" Apr 16 02:04:17 file descriptors belong to particular processes. Apr 16 02:04:33 When the "donator process" exits, all of its file descriptors are closed. Apr 16 02:04:41 why? Apr 16 02:04:47 Because that's how POSIX works. Apr 16 02:04:55 sorry that's no answer Apr 16 02:05:13 when you do something like `(foo & bar) | cat`, how do you think the `cat` process knows when to stop reading? Apr 16 02:05:29 I don't see a POSIX rule that says "whenever there is a donator process it has closed file handles only" Apr 16 02:05:52 POSIX doesn't have a concept of "donator process" so it wouldn't refer to anything as that. Apr 16 02:06:05 that's why it wasn't an answer Apr 16 02:06:22 When any process exits, all of its file descriptors are closed. Apr 16 02:06:32 and again, try to answer my question. Apr 16 02:06:34 sorry that's nonsense Apr 16 02:06:43 It's really not. Apr 16 02:07:02 when all filehandles of all processes are always closed, then what the heck do we need filehandles for? Apr 16 02:07:30 They're not always closed. Apr 16 02:07:33 They're closed on exit. Apr 16 02:07:45 it's plain obvious that there exist processes with open filehandles Apr 16 02:07:51 or on exec if it was opened with CLOEXEC or configured as such afterwards. Apr 16 02:08:09 who said "exit"?? Apr 16 02:08:14 14:06:21 < Maxdamantus> When any process exits, all of its file descriptors are closed. Apr 16 02:08:17 Me. Apr 16 02:08:22 who cares? Apr 16 02:08:26 You. Apr 16 02:08:29 no Apr 16 02:08:37 Then what the fuck are you going on about? Apr 16 02:08:45 I never talked of an EXITED donator process Apr 16 02:08:58 au contraire Apr 16 02:09:15 You were responding to my statements about what happens when a process exits as if they were incorrect. Apr 16 02:09:59 since when the donator process would already have exited, then how would it go to close the swapped filehandle after donating his own filehandle to the process-under-tweaking? Apr 16 02:10:58 sorry I missed to notice the "when exiting" in your statement Apr 16 02:13:29 swapfd creates and opens a filehandle, finds own process table in kernel and finds destination process' table in kernel, swaps the two file descriptors, then closes own (now swapped) filehandle Apr 16 02:13:55 done Apr 16 02:15:01 you just need to block premeptive multitasking during the whole swap process Apr 16 02:15:40 swapfd must not get interrupted amidst doing the swap Apr 16 02:16:19 prolly not even after locating the process table entries Apr 16 02:17:00 otherwise odds are the destination process exits meanwhile and a new process gets same table entry in process table Apr 16 02:17:16 would cause funny havok Apr 16 02:18:38 prolly swapfd's own process table entry can safely considered stable during runtime of swapfd Apr 16 02:21:15 so seach process table for destination process, on find do lock the multitasking, verify that the process table entry you found is still valid, write the own new file descriptor to target process table entry, re-enable multitasking, write 'old' file descriptor to own process table entry, close own file descriptor, exit Apr 16 02:23:41 lemme augment to make it comprehensive... Apr 16 02:25:48 or you can just use ptrace to back up the process' registers, modify the ones inside the process' address space such that it will make the appropriate system calls, then restore the registers again afterwards. Apr 16 02:25:53 so swapfd creates own fd to new file, finds own process table entry, and in there the file descriptor, seaches process table for destination process, on find do lock the multitasking, verify that the process table entry you found is still valid, write the own new file descriptor to target process table entry, re-enable multitasking, write 'old' file descriptor to own process table entry, close own file descriptor, exit Apr 16 02:26:31 Then its only dependent on a stable interface for each architecture, rather than internel assumptions about how the kernel works at any given time. Apr 16 02:27:48 good point, I just fail to understand how a process that already has opened a filehandle would do a systemcall to close() and open() again, without losing another systemcall you used to patch the process Apr 16 02:28:34 unless you divert the write() and read() systemcalls to own code that does all this Apr 16 02:28:57 and even then you need to wait until the process calls write() or read() next time Apr 16 02:29:07 which might be quite a while Apr 16 02:29:35 maybe I comletely missed to understand your concept Apr 16 02:30:50 You might need to check to see if it's in the middle of a call involving the replace fd. Apr 16 02:31:45 even if you didn't, it wouldn't block anyway since that old fd would be closed shortly afterwards. Apr 16 02:32:25 yeah, that for sure :-) An advantage of the concept I sketched is that you can safely assume that the process isn't inside a kernel function call when it gets suspended, unless it's poll() or the like Apr 16 02:34:42 and yes, my concept has nasty dependencies on deep knowledge about kernel data structures Apr 16 02:35:29 I still wonder if it could already be there waiting for us, in debugfs Apr 16 02:37:06 basically what forbids a filedescriptor node that's writeable, in a debug-enabled /proc/$pid/fd/${fd}_descriptor Apr 16 02:37:31 it's just not there because... Apr 16 02:38:39 in /proc/8113/fdinfo you are almost there already, just the right node missing, plus write permissions Apr 16 02:39:25 cat /proc/8113/fdinfo/1 Apr 16 02:40:04 now make that writeable and allow a "path: " as well Apr 16 02:41:36 I'm missing /debug/8113/fd/1* or sth like that. Just because no debugfs installed here Apr 16 02:43:01 mount -t debugfs none /sys/kernel/debug Apr 16 02:48:15 * Maxdamantus suspects it could be made less architecture-dependent by creating another child process that appears to do the actual system calls. Apr 16 02:48:55 hmm, no, doesn't look like anything I'm dreaming up is in debugfs. only stuff like /sys/kernel/debug/tracing/events/ext4/ that might or might not have something useful Apr 16 02:49:31 so it will ptrace both that child (which just does the open, dup2, close) and the target process, but will swap the registers structure around so it looks like the calls are done in the other process. Apr 16 02:49:36 yeah, new lightweight thread Apr 16 02:49:50 sharing memory space Apr 16 02:50:36 It doesn't need to share its address space. Apr 16 02:50:54 would simplify stuff, I guess Apr 16 02:51:15 maybe not Apr 16 02:51:20 You just need to copy the registers from the new child to the target child before the system call, then from the target child to the new child after the system call. Apr 16 02:51:24 too tired to think that in deep Apr 16 02:51:56 then you resume the new child (PTRACE_SYSEMU), so it looks like the call was made there. Apr 16 02:52:32 it anyway seems this _can_ get done, one way or another, but it's nontrivial and you prolly correctly say nobody implemented it yet Apr 16 02:52:33 since open/dup2/close only involve inputs/outputs in the registers themselves. Apr 16 02:53:22 I haven't even looked into ptrace in depth yet Apr 16 02:53:37 I just know what it's used for Apr 16 02:53:43 usually :-) Apr 16 02:54:54 I prolly would know how to (ab)use gdb to do this FD redirection Apr 16 02:56:50 first I'd patch the program text to append the code doing the close() and open() stuff, then change program counter to point to that interim new code, wun it, and continue where we left regular program text, not without restoring all registers etc to their original values Apr 16 02:57:12 s/wun/run/ Apr 16 02:57:13 DocScrutinizer05 meant: first I'd patch the program text to append the code doing the close() and open() stuff, then change program counter to point to that interim new code, run it, and continue where we left regular program text, not without restoring all registers etc to thei... Apr 16 02:58:22 finally I could delete the interim code from target's programtext again **** ENDING LOGGING AT Sat Apr 16 02:59:58 2016