| 00:00.15 | *** join/#maemo atk (Arch-TK@ircpuzzles/staff/Arch-TK) |
| 00:01.53 | DocScrutinizer05 | root; cd /tmp; wget http://repository.maemo.org/pool/maemo5.0/non-free/l/location-test-gui/location-test-gui_0.93-1+0m5_armel.deb && dpkg -i location-test-gui/location-test-gui_0.93-1+0m5_armel.deb |
| 00:02.35 | DocScrutinizer05 | or you add the SDK repo to HAM |
| 00:02.59 | rhombus | that would be easier, wouldn't it? |
| 00:03.04 | DocScrutinizer05 | yep |
| 00:04.44 | rhombus | how do I add the SDK repo to HAM? |
| 00:05.52 | DocScrutinizer05 | good question |
| 00:05.58 | rhombus | lol |
| 00:06.26 | DocScrutinizer05 | http://maemo.org/packages/repository/list/fremantle_sdk-tools_non-free_armel/ |
| 00:06.59 | DocScrutinizer05 | analog to http://wiki.maemo.org/Extras-devel |
| 00:07.09 | DocScrutinizer05 | you can edit catalogs in HAM |
| 00:08.02 | DocScrutinizer05 | http://wiki.maemo.org/Extras-devel#How_to_activate_Extras-devel |
| 00:08.15 | DocScrutinizer05 | chnage the text accordingly |
| 00:10.26 | rhombus | do I still put "fremantle" in the Distribution field? |
| 00:12.03 | rhombus | so then I go to All and search for location-test-gui, yes? |
| 00:12.06 | DocScrutinizer05 | yes |
| 00:12.33 | rhombus | the URL you gave me is old |
| 00:12.44 | DocScrutinizer05 | If the config doesn't work, HAM will bitch about "broken catalog" |
| 00:12.53 | rhombus | as it did |
| 00:13.56 | rhombus | it didn't work, I get a 301 error, "moved permanently" |
| 00:15.16 | DocScrutinizer05 | http://susepaste.org/85581366 |
| 00:17.03 | DocScrutinizer05 | as info source, not to copy the file |
| 00:17.22 | rhombus | oh |
| 00:17.46 | DocScrutinizer05 | actually you won't have that file, it's from my enable-catalogs "tool" |
| 00:18.01 | rhombus | I don't even have enable-catalogs :) |
| 00:19.39 | rhombus | checking updates |
| 00:19.43 | DocScrutinizer05 | http://maemo.cloud-7.de/maemo5/usr/local/sbin/enable-catalogs |
| 00:20.22 | rhombus | what does it do? |
| 00:21.24 | rhombus | installing location-test-gui |
| 00:23.15 | rhombus | wa wa |
| 00:23.16 | DocScrutinizer05 | look into it, it comes with --help |
| 00:23.25 | rhombus | No satellites |
| 00:23.43 | rhombus | It still has the location of some previous owner of the devices |
| 00:23.46 | rhombus | It still has the location of some previous owner of the device |
| 00:24.07 | rhombus | ok |
| 00:24.14 | rhombus | I think that's enough for tonight |
| 00:24.23 | rhombus | I will have to revisit this some other time |
| 00:24.23 | DocScrutinizer05 | well, you need to be outside for it seeing satellites |
| 00:24.42 | rhombus | I was hoping that my proximity to the window would help, but you are right of coruse |
| 00:24.57 | rhombus | my satnav device doesn't work in the apartment either :) |
| 00:25.07 | rhombus | I will try it tomorrow on the train platform :) |
| 00:25.18 | rhombus | Thanks Jörg for all your patience and help |
| 00:25.24 | rhombus | I still have a lot to learn |
| 00:25.40 | DocScrutinizer05 | yw |
| 00:25.47 | rhombus | oh - wait, it sees two sats now |
| 00:26.01 | DocScrutinizer05 | yeah, it's not all bad |
| 00:26.23 | rhombus | but I won't wait for it to lock, I can try it tomorrow |
| 00:26.39 | rhombus | thanks again, I'll be around :) |
| 00:26.41 | DocScrutinizer05 | I usually get a fix within 20s when I really fold the device to the window |
| 00:26.58 | rhombus | then it should work great outside tomorrow :) |
| 00:27.19 | rhombus | ciao |
| 00:27.23 | DocScrutinizer05 | o( |
| 00:27.27 | rhombus | hehe |
| 00:27.32 | DocScrutinizer05 | o/ |
| 00:27.40 | rhombus | o/ |
| 00:41.03 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1:7061:3b2a:37df:ded3) |
| 00:52.57 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 01:08.33 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 01:33.35 | jonwil | I finally found the cause of the boot loop that started all my N900 troubles. I wanted to see what packages apt-get upgrade on cssu-devel actually wanted to install. So I added cssu-devel to my repo list and ran apt-get update. Then I ran apt-get -s upgrade (to simulate the list of packages it wanted to install) and it seems that if you do that, it will install package kernel-modules but NOT... |
| 01:33.37 | jonwil | ...the kernel itself. |
| 01:33.48 | jonwil | So that then screwed up the kernel modules |
| 01:34.17 | jonwil | Of course I didn't actually install anything and then I disabled cssu-devel immediately |
| 02:13.17 | Maxdamantus | dislikes the idea of the package manager maintaining kernel modules (ie, files under /lib/modules belongining to the package itself) |
| 02:14.06 | Maxdamantus | The kernel and the modules *could* be installed by something that is maintained by the package manager, but the package manager shouldn't maintain either directly. |
| 02:14.49 | Maxdamantus | Not sure how it typically works on, eg, Debian, since I've just been compiling my own kernels for as long as I can remember. |
| 02:57.39 | jonwil | I think the answer is to change something (dont know what) so that its impossible for the kernel modules to be installed without installing the matching kernel |
| 02:57.41 | jonwil | and vice versa |
| 03:09.11 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 03:25.04 | Maxdamantus | So `a` depends on `b` and `b` depends on `a`, therefore it's impossible to install either, problem solved. |
| 03:25.38 | LjL | package managers are usually a little smarter than that |
| 03:25.44 | LjL | modern ones at least |
| 03:26.16 | Maxdamantus | but yeah, if a kernel/modules are part of a package, they really should be part of the same package. |
| 03:26.40 | Maxdamantus | Since they're meant to be artifacts of the exact same build process. |
| 03:26.52 | Maxdamantus | make && make install && make modules_install |
| 03:31.22 | Maxdamantus | (note that my point about not having the package manager "install" the modules/kernel still stands; it would be logical for something like `apt-get install kernel-installer` to give you some "install-kernel" command, which copies modules into /lib/modules and a kernel into /boot, and maybe updates some bootloader configuration) |
| 03:32.18 | Maxdamantus | (that way, when you uninstall/upgrade the "kernel-installer" package, it doesn't try to remove the old kernel/modules .. just the ability to install them again) |
| 03:34.10 | jonwil | Anyhow, if I end up being in a position to do updates to CSSU-devel I will make some changes to solve that |
| 03:41.57 | jonwil | merlin1991: ping |
| 03:42.29 | DocScrutinizer05 | well... NEVER run apt-get zpgrade or apt-get dist-upgrade on maemo |
| 03:43.35 | jonwil | regardless of all that, it shouldn't ever be possible to install a package in a way where some other thing is also needed for the system to work but that other thing doesn't get installed |
| 03:44.02 | DocScrutinizer05 | hmm, good luck |
| 03:44.09 | jonwil | why do you say that? |
| 03:44.51 | DocScrutinizer05 | because that's a question of dependencies and maemo isn't built in a way that handles dependencies so you could do upgrade or dist-upgrade. |
| 03:46.53 | jonwil | I am not interested in fixing it so you can do upgrade or dist-upgrade, I am interested in making it so its impossible to do apt-get install blah and end up with a system that doesn't work (regardless of what blah is) |
| 03:46.56 | DocScrutinizer05 | and like you're not supposed to do a apt-get upgrade, you as wel could install some conflicting lib or module or the like with dpkg -i pkgname and that would also not get handled gracefully if the dependencies inside the packages are not made to cope with it |
| 03:47.51 | DocScrutinizer05 | CSSU-devel *is* broken |
| 03:49.23 | DocScrutinizer05 | maemo-extras-devel has broken packages. You're not supposed to enable either of both repos and if you do neverthrless you MUST NOT do apt-get upgrade. You will be able to install the nroken packages with apt-get install. FIX: do not enable those repos |
| 03:50.46 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 03:58.03 | DocScrutinizer05 | to make it utterly clear: the kernel modules are supposed to have a dependency to kernel (obviously) but - partially due to the way kernel gets flashed on N900 rather than installed as a package - this can't get done in maemo |
| 04:00.44 | DocScrutinizer05 | maemo has metapackage that consists of all the needed and paired things to make a working system. and you install that package instead of doing apt.get upgrade. The wrong kernel modules wouldn't get installed by installing the PR metapackage |
| 04:02.38 | DocScrutinizer05 | you could apt-get install wrong kernel modules on any system I guess, when you have wrong repos enabled and point to the wrong kernel modulles. that's not specifically maemo and not a bug |
| 04:03.15 | jonwil | Yeah fair enough I guess |
| 04:04.18 | DocScrutinizer05 | O hosed my PC linux by installing some libs from a newer distro release |
| 04:04.21 | DocScrutinizer05 | I* |
| 04:04.42 | jonwil | If you install anything manually from any of the CSSU repos instead of installing cssu (stable, testing or thumb) the recommended way and getting mp-fremantle-community-pr and its exact dependencies) its your own fault if the system is screwed |
| 04:05.19 | DocScrutinizer05 | which really is a bug I'd say, at least as far as shared object libs are concerned, since tthey are supposed to be able to coexist |
| 04:06.09 | DocScrutinizer05 | jonwil: pretty much yes :-) |
| 04:07.16 | jonwil | Its my own fault for screwing up my N900 by not reading the warnings never to use apt-get upgrade and by not checking what packages it wanted to install. |
| 04:07.42 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 04:08.26 | jonwil | But definitely we should update cssu-devel with newer packages and we should figure out what packages in cssu-devel have been tested enough to be safe to promote to cssu-testing |
| 04:08.40 | DocScrutinizer05 | well, we can try to fix that sick maemo-*-PR metapackage scheme as much as possible |
| 04:08.57 | jonwil | I am sure the latest version of maemo-security-certman should be put in cssu-testing for example |
| 04:09.01 | DocScrutinizer05 | yes, that too |
| 04:09.55 | jonwil | Speaking of which, there is probably a newer certdata.txt that I could pull into maemo-security-certman :) |
| 04:12.34 | jonwil | actually, no there is not |
| 04:12.52 | jonwil | I just pulled the latest one and it matches the one I pulled last time I updated things |
| 04:34.48 | merlin1991 | jonwil: pong |
| 05:20.43 | KotCzarny | jonwil: ignoring multiple warnings because 'it wont happen to me' isnt smart ;) |
| 05:20.52 | KotCzarny | 1/ you ignored warnings about -devel repos |
| 05:21.04 | KotCzarny | 2/ ignored warning of not using apt-get update |
| 05:21.24 | KotCzarny | but it's fine, you've learned a bit in the process |
| 05:21.45 | KotCzarny | (fear greatly increases remembering ;) |
| 05:30.20 | *** join/#maemo TheKit (~nekit@95-83-41-210.saransk.ru) |
| 06:14.41 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 06:27.45 | *** join/#maemo XDS2010|AFK (sid1218@gateway/web/irccloud.com/x-ukulkdxkimywovdo) |
| 07:13.39 | *** join/#maemo jkepler (~Thunderbi@gateway/vpn/privateinternetaccess/jkepler) |
| 07:20.59 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:39.33 | *** join/#maemo florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 08:07.56 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 08:09.59 | *** join/#maemo Kabouik (~kabouik@158.38.1.70) |
| 08:16.12 | *** join/#maemo jskarvad (~jskarvad@ip4-83-240-32-61.cust.nbox.cz) |
| 08:16.12 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 08:25.02 | *** join/#maemo freemangordon_ (~ivo@195.128.225.2) |
| 08:28.57 | *** join/#maemo rhombus (~rhombus@remote.rl-institut.de) |
| 08:30.24 | rhombus | DocScrutinizer05: My phone was "charging" all night -- when I checked it this morning the LED was still blinking yellow. When I disconnected it from the charger, the battery level was just above empty. |
| 08:30.39 | rhombus | I am not sure what happened there. |
| 08:30.40 | KotCzarny | uh-oh |
| 08:30.49 | KotCzarny | what charger/cable? |
| 08:31.08 | KotCzarny | your phone might be using more juice than provided |
| 08:31.38 | rhombus | KotCzarny: It could be that the WLAN was running all night, that's why I rebooted |
| 08:31.50 | rhombus | KotCzarny: The charger is the Nokia AC-2E |
| 08:31.52 | KotCzarny | wifi alone isnt enough |
| 08:32.14 | KotCzarny | did you set it not to turn of the display? maybe some application running all the time? |
| 08:32.32 | rhombus | 5.3 V, 500 mA output |
| 08:32.56 | rhombus | The browser was left open, other than that I don't think anything else was running |
| 08:33.23 | KotCzarny | definitely 500 might be enough, but best to use 900mA or better |
| 08:33.31 | KotCzarny | close browser |
| 08:33.38 | rhombus | I rebooted, so... |
| 08:33.42 | rhombus | browser closed :) |
| 08:33.49 | KotCzarny | any widgets on desktop? |
| 08:34.00 | KotCzarny | anything weird you have installed? |
| 08:34.07 | rhombus | KotCzarny: You mean open applications? |
| 08:34.22 | KotCzarny | well, you can have widgets |
| 08:34.33 | KotCzarny | tiny apps that take place on the desktop |
| 08:34.39 | KotCzarny | not recommended usually |
| 08:35.50 | KotCzarny | there was also a battery/current monitoring script, you might want to run it to see |
| 08:35.57 | rhombus | KotCzarny: I did the lazyflashing procedure yesterday with Joerg and installed CSSU |
| 08:36.00 | KotCzarny | ~bq2700 |
| 08:36.04 | KotCzarny | ~bq2700.sh |
| 08:36.08 | KotCzarny | hrm |
| 08:36.15 | rhombus | bot is asleep maybe |
| 08:36.18 | jonwil | ~bq27200 |
| 08:36.18 | infobot | well, bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2, or ~bq27 |
| 08:36.19 | KotCzarny | yeah, cssu is recommended |
| 08:36.39 | KotCzarny | i suspect browser was running some weird js |
| 08:37.04 | jonwil | I have definitely had instances when a web page open in the browser drains my battery real fast |
| 08:37.09 | KotCzarny | you can run the bq script as root with '1' as a param to observe current usage |
| 08:37.14 | rhombus | KotCzarny: that's possible, the whole procedure (despite all the claims that it would "not take long") took about four hours |
| 08:37.50 | jonwil | The n900 browser is a massive resource hog unfortunately |
| 08:37.56 | KotCzarny | is your network slow? last time i was flashing/installing cssu wasnt longer than 30 min |
| 08:38.03 | KotCzarny | that including me reading the steps |
| 08:38.49 | rhombus | KotCzarny: I'm talking about the entire procedure |
| 08:39.13 | KotCzarny | yup |
| 08:39.20 | rhombus | backups (many), package installs, flashing, restores, etc. |
| 08:39.38 | KotCzarny | well, i dont know about backups, just flashing+cssu |
| 08:39.49 | rhombus | Can i install bq27200 from the HAM? |
| 08:40.06 | KotCzarny | nope, it's just a shell script |
| 08:40.11 | KotCzarny | download with wget |
| 08:40.15 | rhombus | jonwil: is it the browser or the wifi module that's the resource hog? ;-) |
| 08:40.15 | KotCzarny | then run in shell |
| 08:40.19 | KotCzarny | can be ran via ssh |
| 08:40.20 | jonwil | browser |
| 08:40.29 | jonwil | wifi isn't a buge resource hog in my experience |
| 08:40.33 | jonwil | huge |
| 08:40.38 | rhombus | jonwil: that's not what I've been told |
| 08:40.45 | KotCzarny | wifi can be resource hog in crowded areas |
| 08:40.50 | Wizzup | is the battery maybe just dead? |
| 08:41.02 | jonwil | Yes WiFi can be a resource hog if the network is congested |
| 08:41.06 | rhombus | jonwil: when I first got the phone I left the WLAN on and the new, fully charged battery was dead by the end of the day |
| 08:41.08 | KotCzarny | wizzup, he wouldnt be able to flash then |
| 08:41.11 | rhombus | so I turned it off |
| 08:41.48 | jonwil | my experience is that WiFi doesn't drain the battery |
| 08:41.54 | rhombus | Wizzup: the battery is not that old |
| 08:42.14 | rhombus | jonwil: do you live in the country? |
| 08:42.15 | jonwil | but you may have something about the WiFi environment in your area that might be a battery hod |
| 08:42.20 | jonwil | I live in a city |
| 08:42.25 | KotCzarny | also, dont enable 'periodically search for networks' |
| 08:42.32 | KotCzarny | THAT's a battery hog |
| 08:42.34 | rhombus | KotCzarny: That was on, yes |
| 08:42.42 | rhombus | KotCzarny: and yes, I turned that off, too |
| 08:42.45 | jonwil | Yeah that is definitely the battery hog there |
| 08:42.52 | jonwil | regular old WiFi not so much |
| 08:42.56 | rhombus | Well, that is on by default :) |
| 08:43.11 | rhombus | so... unless you know this and actively turn it off... |
| 08:44.11 | KotCzarny | apart from that, you can install battery-eye app |
| 08:44.26 | KotCzarny | from my experience it's very good to observe battery history |
| 08:44.43 | KotCzarny | and isnt like many of the others, not eating battery itself |
| 08:45.00 | KotCzarny | also provides nice statistics |
| 08:45.20 | jonwil | Where is the "periodically search for networks" option? |
| 08:45.27 | rhombus | Ok, I'll make a note |
| 08:45.30 | jonwil | I see "search interval" at 10 minutes, is that it? |
| 08:45.35 | rhombus | While I have you all here, isn't this phone supposed to have an FM receiver? |
| 08:45.44 | rhombus | I can't find an app for it |
| 08:45.50 | KotCzarny | jonwil: internet connections |
| 08:45.59 | KotCzarny | then 'switch to wifi when available' |
| 08:46.09 | KotCzarny | and search interval |
| 08:46.21 | KotCzarny | well, mostly 'search interval' |
| 08:46.24 | jonwil | I have that option enabled with search interval at 10 minutes and I dont get battery hog |
| 08:46.36 | buZz | rhombus: the radio only works if you put a headphone in, it uses the wire as antenna |
| 08:46.37 | rhombus | I had it enabled at 10 min |
| 08:46.53 | rhombus | buZz: But I can't even find an app for it :) |
| 08:47.00 | KotCzarny | there is app for fm radio |
| 08:47.03 | buZz | well thats something else, cant help you there :P |
| 08:47.21 | rhombus | KotCzarny: in the community catalogs? |
| 08:47.24 | KotCzarny | called.. 'fm radio' |
| 08:47.25 | KotCzarny | ;) |
| 08:47.37 | KotCzarny | dont remember, probably |
| 08:47.41 | rhombus | such a strange name |
| 08:47.55 | KotCzarny | it was a few years since i last installed things on my n900 |
| 08:48.27 | KotCzarny | usually most things come from extras |
| 08:48.37 | KotCzarny | and many times newest versions in extras-devel |
| 08:48.47 | KotCzarny | while extras should be safe to leave enabled |
| 08:49.02 | KotCzarny | extras-devel should be only enabled to install specific apps |
| 08:49.21 | KotCzarny | and only if you trust devel and want latest version |
| 08:49.22 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 08:50.22 | KotCzarny | https://wiki.maemo.org/N900_FM_radio_receiver#User |
| 08:50.27 | KotCzarny | also, you should read wiki more |
| 08:50.30 | rhombus | my stupid wlan at work has a super tight firewall filter, the install fails |
| 08:50.34 | rhombus | I'll have to do this at home |
| 08:50.49 | KotCzarny | http://maemo.org/packages/view/fmradio/ |
| 08:50.55 | rhombus | KotCzarny: I am fond of reading, but the Wiki is a bit of a mess |
| 08:51.01 | KotCzarny | it is |
| 08:51.09 | KotCzarny | but also great source of useful information |
| 08:51.16 | rhombus | KotCzarny: There's lots of stuff there that is totally outdated and for a new user it is confusing and sometimes even dangerous |
| 08:51.23 | bencoh | indeed |
| 08:51.25 | rhombus | without Joerg's help yesterday I would have had no chance |
| 08:51.31 | KotCzarny | nah |
| 08:51.34 | KotCzarny | you would be fine |
| 08:51.35 | rhombus | If people point me to the right info, yes :) |
| 08:51.43 | KotCzarny | just you would learn a lot more |
| 08:51.48 | KotCzarny | (at the expense of more time) |
| 08:51.54 | KotCzarny | (and errors ;) |
| 08:52.04 | rhombus | KotCzarny: yes and yes :) |
| 08:52.10 | KotCzarny | usually you can check user's pages on wiki |
| 08:52.21 | KotCzarny | people bookmark important bits |
| 08:52.41 | rhombus | Ah, good tip, thanks |
| 08:54.18 | KotCzarny | i wonder why User:Dik is targetted by spam |
| 08:54.23 | KotCzarny | probably someone wrote a script |
| 08:54.59 | KotCzarny | and published in some spamkit |
| 08:57.56 | KotCzarny | sixwheeledbeast: ^ |
| 09:01.06 | KotCzarny | rhombus: also, is your wifi enabled with power saving mode? |
| 09:01.12 | KotCzarny | it tends to eat a bit without |
| 09:01.27 | *** join/#maemo eMHa (~mh@2a02:788:113:142:d6be:d9ff:fe2b:f21b) |
| 09:07.08 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 09:08.57 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 09:23.23 | rhombus | KotCzarny: Let me see |
| 09:28.14 | rhombus | KotCzarny: Where do I find that setting? |
| 09:28.28 | KotCzarny | in internet connections |
| 09:28.34 | KotCzarny | probably in advanced button |
| 09:28.58 | rhombus | KotCzarny: I don't see an advanced button, unfortunately |
| 09:29.48 | KotCzarny | connections -> (select your net) edit -> few times 'next' until you see 'advanced' |
| 09:30.55 | rhombus | power saving is at max |
| 09:31.03 | rhombus | is that a general setting or does that apply only to this connection? |
| 09:31.15 | KotCzarny | yeah, default is max |
| 09:31.23 | KotCzarny | but you can change it per-connection i think |
| 09:31.40 | rhombus | Ah, ok |
| 09:45.20 | sixwheeledbeast | done. |
| 09:45.48 | sixwheeledbeast | Been away for a bit, just reading ^^^ |
| 09:48.35 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 09:58.47 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 10:07.22 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 10:08.01 | Wizzup | https://www.krackattacks.com |
| 10:08.12 | Wizzup | well, rip n900 wifi |
| 10:08.19 | Wizzup | maemo* |
| 10:11.26 | bencoh | yeah ... |
| 10:13.14 | Wizzup | unless we switch to wpa_supplicant (and then a new version) :) |
| 10:15.48 | bencoh | or patch the current implementation (is it closed?) |
| 10:15.59 | KotCzarny | The weaknesses are in the Wi-Fi standard itself, and not in individual products or implementations. Therefore, any correct implementation of WPA2 is likely affected |
| 10:16.01 | KotCzarny | ;) |
| 10:16.39 | bencoh | KotCzarny: apparently there is some kind of workaround to the weakness |
| 10:16.46 | Wizzup | bencoh: closed |
| 10:16.47 | bencoh | (backward-compatible) |
| 10:28.12 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 10:30.40 | rhombus | Damn. I think my battery is damaged :( |
| 10:31.04 | KotCzarny | ~polarcell |
| 10:31.05 | infobot | somebody said polarcell was http://www.ebay.co.uk/itm/390402445382 BL-5J Replacement |
| 10:31.23 | rhombus | I have a variocell, it's been great up until now |
| 10:31.32 | rhombus | but it's only 5 months old! |
| 10:31.41 | KotCzarny | yup, that's how those cheapos work |
| 10:31.47 | KotCzarny | great at the first sight |
| 10:31.52 | KotCzarny | then deteriorate quickly |
| 10:31.58 | rhombus | Cheapos? It was the only thing available! |
| 10:32.11 | KotCzarny | i still own and use ORIGINAL nokia battery that came with my n900 in 2009 |
| 10:32.22 | rhombus | My original battery was totally useless |
| 10:32.54 | rhombus | It took two days to fully charge and then it held its charge for about six hours |
| 10:33.12 | sixwheeledbeast | I have had good success with several polarcells from wannasee |
| 10:33.20 | KotCzarny | but aslo get good charger |
| 10:33.27 | KotCzarny | 500mA isnt going to cut it |
| 10:33.45 | KotCzarny | beware of cheapos too. |
| 10:33.49 | bencoh | reminds me I should probably order a spare battery and compatible charger |
| 10:33.50 | KotCzarny | better get original nokia charger |
| 10:34.00 | sixwheeledbeast | expected life is only 2-3 years |
| 10:34.19 | rhombus | I'm using the charger that came with the phone, an original Nokia charger |
| 10:34.27 | bencoh | actually I dont really need a compatible charger, only a compatible cable (ie D+/D- shorted to ground) |
| 10:34.42 | rhombus | The battery was working beautifully until I did this reflash |
| 10:37.29 | rhombus | Stellar, these Varocells aren't even available anymore |
| 10:38.10 | rhombus | Is there any point in buying an old Nokia BL-5J, or one in original packaging? They've gotta be ancient by now |
| 10:38.51 | sixwheeledbeast | I was looking at them magnetic USB cables but I imagine they are not D shorted. |
| 10:40.01 | rhombus | When I search for BL-5J on ebay, nothing but junk comes up |
| 10:40.30 | rhombus | Are there other model numbers that are equivalent? |
| 10:42.59 | Maxdamantus | rhombus: why not just get a Polarcell? |
| 10:43.26 | Maxdamantus | I imagine if anyone claims to be selling a BL-5J nowadays, it's probably fake. |
| 10:43.27 | rhombus | Maxdamantus: There isn't one available -- that link comes up with a "CURRENTLY SOLD OUT" page |
| 10:43.56 | rhombus | and the links below are to UK sellers, that's not much use to me |
| 10:49.01 | rhombus | Ok, where do I get a decent charger? Can I just use a generic (micro-)USB charger? |
| 10:49.15 | rhombus | I don't want cheap junk |
| 10:51.52 | Maxdamantus | They seem to be advertising them on Amazon still, maybe they'll ship to other countries through there. |
| 10:53.42 | Maxdamantus | Do you mean a charger to just plug into the phone? |
| 10:55.03 | sixwheeledbeast | http://www.wannsee-electronic.de/handyakkus/nokia/polarcell_hochleistungsakku_fuer_nokia_n900_ersetzt_originalakku__bl-5j_i2_2090_0.htm |
| 10:55.10 | Maxdamantus | aiui, you can get around the D shorting issue through software. |
| 10:55.29 | rhombus | Maxdamantus: there must be suppliers on the Continent |
| 10:55.43 | sixwheeledbeast | No idea if there is an english site but maybe a good idea to replace the factiod with the company site over ebay. |
| 10:56.03 | KotCzarny | there were still new bl-5j produced by nokia for some nokia asha series |
| 10:56.10 | KotCzarny | that was year ago or so |
| 10:56.21 | rhombus | sixwheeledbeast: No worries, I can read the German |
| 10:56.35 | sixwheeledbeast | i can't |
| 10:56.43 | rhombus | KotCzarny: Produced by Nokia, or by "Nokia"? ;-) |
| 10:57.43 | Maxdamantus | I think you can just do something like: echo 1800 >/sys/class/power_supply/bq24150a-0/charge_current |
| 10:57.48 | KotCzarny | since nokia is no more since ~2012, by whatever m$ ordered it to, i presume factories didnt change |
| 10:58.19 | Maxdamantus | after plugging in a non-shorted supply .. not sure though, I've just shorted the supplies I happen to use. |
| 10:58.24 | KotCzarny | also, my n900 came with 900mA charger |
| 11:01.04 | rhombus | KotCzarny: Can you direct me to a suitable 900 mA charger? |
| 11:01.06 | Maxdamantus | Hmm .. with those magnetic cables, do you actually need to short them? Shouldn't they just function as normal USB cables, so you'd just have it shorted at the type A port, or have it plugged into a computer that it can negotiate a current with? |
| 11:01.54 | KotCzarny | https://wiki.maemo.org/N900_Accessories#Chargers |
| 11:02.33 | KotCzarny | oh, it's 1200mA, not 900 |
| 11:02.50 | KotCzarny | most likely my n800 charger is 900 one |
| 11:03.28 | KotCzarny | AC-10U |
| 11:04.20 | KotCzarny | but if you have htc/samsung etc, you can use that one |
| 11:04.34 | KotCzarny | just use the original, not noname one |
| 11:05.20 | rhombus | AC-10U will have a NEMA 1-15 plug, no? |
| 11:05.25 | rhombus | It says here for US N900 |
| 11:06.25 | rhombus | I need a type F plug |
| 11:06.52 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 11:07.01 | KotCzarny | ac-10e seems eu version |
| 11:07.09 | rhombus | ah, thank you |
| 11:08.54 | rhombus | these reviews are not encouraging |
| 11:09.15 | KotCzarny | maybe fakes? |
| 11:09.32 | rhombus | Entirely possible :( |
| 11:10.02 | KotCzarny | i havent seen anyone on #maemo saying his/hers charger breaking bad |
| 11:10.03 | rhombus | Is this a standard charger format? Does it have to be a Nokia charger? |
| 11:10.19 | KotCzarny | as i've said, even cheapo fake will charge |
| 11:10.30 | KotCzarny | but it's best to use branded one |
| 11:10.39 | KotCzarny | and yes, doesnt have to be nokia branded |
| 11:10.52 | KotCzarny | just that nokia did solid products |
| 11:11.01 | rhombus | The reviews on the German Amazon site are savage -- ("broke after three weeks", "complete junk", etc) |
| 11:11.21 | rhombus | they are probably poorly refurbished previously defective units |
| 11:12.13 | rhombus | oh, and some more "fake" and "really original? I doubt it" "not recommended" |
| 11:12.16 | rhombus | so much for that |
| 11:12.31 | rhombus | So a standards compliant micro-USB charger will do the job |
| 11:12.37 | rhombus | I'll get one of those then |
| 11:13.39 | Maxdamantus | Though I think there's some chance a "standard-compliant" charger wouldn't be standards-compliant enough. |
| 11:14.02 | KotCzarny | if it's original and branded, it should be ok |
| 11:14.16 | KotCzarny | try borrowing some charger |
| 11:14.16 | Maxdamantus | in that it might not have its data pins shorted, which means the device needs to negotiate a current with a computer. |
| 11:14.20 | rhombus | Maxdamantus: one issue is that the Nokia charger has an output voltage of 5.3 V listed, wheres the standard chargers have 5 V output |
| 11:14.33 | Maxdamantus | The voltage shouldn't be an issue. |
| 11:15.11 | KotCzarny | i often charge n900 straight from my thinkpad too |
| 11:15.15 | KotCzarny | no issues |
| 11:15.26 | KotCzarny | (but thinkpads can easily supply more than 500mA) |
| 11:16.32 | Maxdamantus | Mm, I've done that too, including using the charging port thing, which I think acts as a dumb supply (so the N900 will be able to draw 1.6 A or something from it). |
| 11:16.51 | Maxdamantus | (I think that's only while the thinkpad is asleep/off) |
| 11:17.04 | rhombus | man, it just gets worse: "The third time I plugged it in, there was a dull thud... and the charger was dead." |
| 11:17.10 | KotCzarny | maxd: if main battery isnt charging, there is a lots of power available |
| 11:18.03 | Maxdamantus | KotCzarny: yeah, but afaik you're not normally going to draw more than 500 mA from a computer, since the device won't try to negotiate more than 500 mA. |
| 11:18.29 | KotCzarny | maxd: i was running 1A and more hdds via usb with thinkpads |
| 11:18.36 | KotCzarny | those are really solid machines |
| 11:18.39 | KotCzarny | (were.) |
| 11:18.46 | Maxdamantus | KotCzarny: I'm just talking about the current draw from an N900. |
| 11:19.06 | rhombus | KotCzarny: yes. I will hang on to my T500 for as long as possible, it was the last decent model |
| 11:19.13 | Maxdamantus | KotCzarny: sure, the Thinkpad has more than enough power available, but I don't think the N900 will draw more than 500 mA from a computer, unless you force it to. |
| 11:19.28 | Maxdamantus | (that is, more than 500 mA from a smart power supply) |
| 11:19.34 | KotCzarny | maxd: still better power quality than any noname charger |
| 11:20.43 | Maxdamantus | Well, if it supplies enough current at the right voltage, it should be the same as any other charger. |
| 11:22.03 | rhombus | a huge industry, producing tonnes of electronics that turns to junk in just a few months |
| 11:22.05 | rhombus | very discouraging |
| 11:22.29 | KotCzarny | rhombus: i use my n900 since 2009 |
| 11:22.40 | KotCzarny | got 3 spares just in case |
| 11:22.49 | Maxdamantus | and yeah, I can confirm that it behaves the way I described. |
| 11:22.49 | rhombus | KotCzarny: I wasn't referring to the N900 or the Thinkpad T_series prior to 2009 :) |
| 11:22.58 | Maxdamantus | plug it into computer, charge_limit = 500 |
| 11:23.09 | Maxdamantus | plug it into power supply with data pins shorted, charge_limit = 1800 |
| 11:23.13 | rhombus | The rest of the industry... all I can say is, holy $%& |
| 11:23.37 | Maxdamantus | and iirc, the Thinkpad only acts as a dumb supply when it's off/asleep. |
| 11:23.54 | Maxdamantus | otherwise it's just a computer, and a USB device shouldn't ask for more than 500 mA. |
| 11:23.59 | Maxdamantus | at least until USB 3 |
| 11:24.16 | Maxdamantus | (which N900 obviously doesn't implement) |
| 11:26.09 | KotCzarny | btw. in idle n900 should take ~10mA |
| 11:26.16 | Maxdamantus | You can always just force the N900 to draw up to 1800 mA by writing "1800" into the "charge_limit" sysfs node, which might be okay. |
| 11:26.32 | KotCzarny | that's why even 500mA would work. unless something eats a lots of power |
| 11:27.28 | Maxdamantus | Well, the advantage would be faster charging. |
| 11:27.42 | KotCzarny | yes, but he had a problem charging overnight |
| 11:27.57 | Maxdamantus | If it used 0 mA, it would still take at least 3.2 hours to charge a 1600 mAh battery at 100% efficiency. |
| 11:28.13 | Maxdamantus | (when drawing 500 mA) |
| 11:29.28 | rhombus | KotCzarny: Maxdamantus As I said, the charger worked wonderfully right up until yesterday, when I did the flashing |
| 11:29.34 | rhombus | The battery was full when the process started |
| 11:29.59 | rhombus | I did not have the phone plugged in during the updates, as I assumed that a full battery would mean I had more than enough time |
| 11:30.10 | rhombus | by the time the process was complete the battery was almost totally empty |
| 11:30.19 | rhombus | And now, it is not charging |
| 11:30.22 | KotCzarny | anyway, in full use with screen on battery suffices for ~4-10 hours |
| 11:30.31 | rhombus | I don't think the charger is to blame |
| 11:30.40 | rhombus | I think the battery has checked out |
| 11:31.10 | rhombus | I have no way of knowing this for certain, but the phone recognizes that a charger has been connected when I plug it in and indicates that it is charging |
| 11:31.25 | KotCzarny | you can try leaving it OFF for 30 minutes |
| 11:31.29 | rhombus | I would use that script you recommended but I am at work and I can't use the network |
| 11:31.30 | KotCzarny | and see if it charged |
| 11:31.32 | KotCzarny | a bit |
| 11:31.36 | Maxdamantus | rhombus: it needs to be able to boot the OS to charge effectively. |
| 11:31.54 | rhombus | KotCzarny: you mean charge it in off state? |
| 11:31.55 | KotCzarny | maxd: he left it installing cssu |
| 11:32.00 | Maxdamantus | rhombus: it will only draw a small amount of current (I think 100 mA) through just hardware. |
| 11:32.07 | rhombus | KotCzarny: when I went to bed the installlation was complete |
| 11:32.25 | *** join/#maemo ecloud_ (quassel@nat/qt/x-cenetnjuzkhdebdd) |
| 11:32.36 | rhombus | Maxdamantus: as I've said, I haven't any issues charging the phone -- on or off -- until this reflash |
| 11:33.01 | rhombus | This is not an existing problem, this started last night |
| 11:33.11 | rhombus | I will try turning the phone off and charging it that way |
| 11:33.48 | rhombus | and order two replacement cells |
| 11:34.14 | Maxdamantus | rhombus: hang on, how are you determining that charging isn't working? |
| 11:34.35 | rhombus | Maxdamantus: It charged over night and the battery was still almost empty |
| 11:34.47 | Maxdamantus | rhombus: maybe installing CSSU included using replacement-bme, which can be misleading if the battery is uncalibrated. |
| 11:34.49 | rhombus | Maxdamantus: then I charged for 2 hours this morning, after a reboot, and still nothing |
| 11:34.53 | KotCzarny | ya. that too |
| 11:35.13 | rhombus | Maxdamantus: oh, man, really? (I wish someone had mentioned this when I did the update) |
| 11:35.52 | KotCzarny | ~calibration |
| 11:36.08 | KotCzarny | ~battery-calibration |
| 11:36.14 | KotCzarny | ~listkeys battery |
| 11:36.33 | KotCzarny | ~listkeys calibration |
| 11:36.42 | KotCzarny | ~bq27k-calibration |
| 11:36.42 | infobot | well, bq27k-calibration is http://talk.maemo.org/showthread.php?p=1247595#post1247595 |
| 11:37.01 | Maxdamantus | rhombus: lsmod | grep bq27 |
| 11:37.22 | Maxdamantus | rhombus: if that shows the module, it'll be using the bme replacement. |
| 11:37.45 | rhombus | Maxdamantus: ok, hang on, I have to boot the phone, it was off |
| 11:38.01 | rhombus | also, you are right, it was not charging when off. Why is that? That worked last night |
| 11:38.02 | KotCzarny | Maxdamantus: but one thing is weird, because he have said, he left it charging overnight and in the morning it was still orange |
| 11:38.04 | Maxdamantus | which uses information stored in the batter calibration chip to show charge, instead of just doing something weird with the current voltage. |
| 11:38.32 | Maxdamantus | KotCzarny: hm, I guess that might be weird. |
| 11:38.34 | KotCzarny | rhombus: no, phone never goes into off mode, it fakes being off |
| 11:38.47 | KotCzarny | he meant when 'laptop is off' |
| 11:38.55 | rhombus | oh, sorry |
| 11:38.59 | DocScrutinizer05 | ((<KotCzarny> also, dont enable 'periodically search for networks' THAT's a battery hog)) ONLY when WLAN is not logged in to an AP |
| 11:39.14 | rhombus | KotCzarny: But then it should still charge when off, no? The yellow LED was not on even though the phone was plugged in |
| 11:39.19 | rhombus | and the charger stopped whistling |
| 11:39.28 | rhombus | when I turned it on again, the whistling returned |
| 11:39.52 | DocScrutinizer05 | battery-eye DRAINS battery |
| 11:39.54 | KotCzarny | btw. it was ON or pulsing? |
| 11:40.30 | KotCzarny | DocScrutinizer05: nope, afair it only takes snapshots when system events occur, and the graph isnt continuous |
| 11:40.34 | rhombus | KotCzarny: When? Just now? Just now it was totally off |
| 11:40.39 | KotCzarny | no, in the morning |
| 11:40.46 | rhombus | Maxdamantus: lsmod | grep bq27 returns nothing |
| 11:41.09 | rhombus | KotCzarny: in the morning it was yellow... I *think* it was pulsing |
| 11:41.28 | KotCzarny | ok. because sometimes daemon responsible hangs |
| 11:41.34 | rhombus | DocScrutinizer05: It may drain battery, but the key point here is that this worked fine until the reflash |
| 11:41.42 | rhombus | DocScrutinizer05: with battery-eye on |
| 11:42.01 | rhombus | KotCzarny: Ok, well, I've rebooted this morning |
| 11:42.19 | rhombus | bq27 module is not running, so can I assume it is using the old battery manager? |
| 11:42.23 | DocScrutinizer05 | sorry, wall of text with lots of ... |
| 11:42.47 | DocScrutinizer05 | I can't see what's happening and what all the incorrect assumptions were |
| 11:43.46 | KotCzarny | basically he claims his battery didnt charge overninght after cssu install |
| 11:43.55 | KotCzarny | *overnight |
| 11:44.17 | DocScrutinizer05 | you might recall I tried to make sure your device charged. That was for a reason. Maybe we should have given it another boot. Then a 500mA charger is not compatible with N900 anyway |
| 11:44.37 | KotCzarny | but it should charge even with 500mA |
| 11:44.41 | DocScrutinizer05 | I assumed you had a compatible charger |
| 11:44.57 | KotCzarny | also, he says it was working before |
| 11:45.00 | DocScrutinizer05 | KotCzarny: no. 500mA has no D+- short |
| 11:45.16 | KotCzarny | but it still would charge, only slower |
| 11:45.30 | KotCzarny | not 'almost empty' after whole night of charging |
| 11:46.20 | DocScrutinizer05 | no |
| 11:46.30 | DocScrutinizer05 | it would charge with max 100mA |
| 11:46.55 | KotCzarny | still WOULD charge |
| 11:47.06 | DocScrutinizer05 | and yes, that can and will result in battery almost empty after a night |
| 11:47.16 | DocScrutinizer05 | when display backlight on |
| 11:47.25 | KotCzarny | did he left lcd on? |
| 11:47.34 | DocScrutinizer05 | do you know he didn't? |
| 11:47.35 | rhombus | DocScrutinizer05: So whoever sold me the phone wasn't totally honest -- the charger is not original? |
| 11:48.03 | DocScrutinizer05 | it's maybe a genuine Nokia charger but not for that device |
| 11:48.15 | KotCzarny | maybe the cable is just 2 wires? |
| 11:48.24 | KotCzarny | is the cable unusually thin? |
| 11:48.36 | rhombus | DocScrutinizer05: but... how many times do I have to repeat this? This worked fine until yesterday. Was I imagining things? |
| 11:49.01 | rhombus | It would take about eight hours to charge from totally empty to totally full |
| 11:49.18 | rhombus | I routinely did partial charges (from say 50 - 60 % to 100 %) in the evenings or over night |
| 11:49.23 | KotCzarny | btw. can you access www at all? |
| 11:49.27 | rhombus | and a charge held typically two to three days |
| 11:49.32 | DocScrutinizer05 | yeah, charging has a number of modes |
| 11:49.34 | rhombus | KotCzarny: let me check |
| 11:49.55 | DocScrutinizer05 | [2017-10-16 Mon 13:44:16] <DocScrutinizer05> you might recall I tried to make sure your device charged. That was for a reason. Maybe we should have given it another boot. |
| 11:50.49 | DocScrutinizer05 | wild guessing, anecdotal "evidence", and inappropriate measures won't "fix" this now |
| 11:51.06 | DocScrutinizer05 | give the device a reboot! |
| 11:51.13 | rhombus | again? I rebooted this morning |
| 11:51.19 | rhombus | then charged for two hours |
| 11:51.25 | rhombus | no effect, battery shows as empty |
| 11:51.29 | KotCzarny | https://wiki.maemo.org/N900_Hardware_Charge_Meter/bq-script |
| 11:51.39 | KotCzarny | dont know if its the latest/proper version |
| 11:51.44 | DocScrutinizer05 | aah ok. This morning then fine |
| 11:51.54 | DocScrutinizer05 | unplig and replug USB |
| 11:52.05 | rhombus | KotCzarny: I'm on the company guest network, it has a portal |
| 11:52.14 | rhombus | Let me see if I can use the employee wifi |
| 11:53.11 | KotCzarny | do you have any data plan on gsm? |
| 11:53.12 | KotCzarny | :) |
| 11:53.34 | DocScrutinizer05 | ohmy |
| 11:55.32 | DocScrutinizer05 | D+- short means fastcharging. 500mA is no fatscharging, so a 500mA charger will most likely not have D+- short. And device is meant to try USB ENUM when it sees VBUS without D+- short |
| 11:56.02 | DocScrutinizer05 | hook it up to a PC so you know it's charging with 500mA |
| 11:56.13 | rhombus | damn, I can't authenticate |
| 11:56.32 | DocScrutinizer05 | maybe do that stuff tonight then? |
| 11:56.43 | rhombus | DocScrutinizer05: yeah, i will have to do it then |
| 11:56.58 | DocScrutinizer05 | instead of draining your battery further by futile installaion efforts |
| 11:57.07 | rhombus | (I don't understand why this authentication doesn't work, but oh well) |
| 11:57.34 | rhombus | I would connect the phone to my thinkpad but lack a suitable microUSB cable |
| 11:57.39 | rhombus | more stuff to add to the shopping list |
| 11:58.21 | DocScrutinizer05 | close all apps and lock/dim the screen, then atach it to that charger. This way it should still charge a little bit |
| 11:59.05 | DocScrutinizer05 | and yeah, disable WLAN |
| 11:59.17 | KotCzarny | also, funny, you can access irc but not www |
| 11:59.25 | DocScrutinizer05 | scanning for APs really is a terrible battery hog |
| 12:00.27 | DocScrutinizer05 | the more APs in vicinity the worse |
| 12:01.22 | DocScrutinizer05 | there's a reason the system does this only periodically |
| 12:01.59 | DocScrutinizer05 | disable periodic scanning, that's OK then |
| 12:04.52 | Maxdamantus | You should still be able to get 500 mA from a 500 mA charger, by doing `echo 500 >/sys/class/power_supply/bq24150a-0/charge_limit` after plugging it in. |
| 12:06.31 | Maxdamantus | (you can also read that file to see how much it's willing to draw; will probably say 100 after plugging it into that charger) |
| 12:11.30 | DocScrutinizer05 | ~power |
| 12:11.30 | infobot | well, power is http://wiki.maemo.org/N900_Hardware_Power_Consumption |
| 12:12.07 | rhombus | (on phone) |
| 12:12.48 | DocScrutinizer05 | >>WLAN on - no powersave *) - 200 mA<< *) or no associated AP which controls powersave |
| 12:13.41 | DocScrutinizer05 | NB: >>WLAN transmit 802.11b - 150 mA<< - only |
| 12:13.55 | KotCzarny | b |
| 12:14.06 | DocScrutinizer05 | so WLAN RX without AP sucks more power than constant TX |
| 12:32.02 | DocScrutinizer05 | ((<rhombus> It would take about eight hours to charge from totally empty to totally full)) doesn't match charging with 500mA which shouldn't take longer than 3h to charge a 1300mAh battery. Rather matches charging a maybe 20% battery (shows as empty) to 80% (shows as full) at 100mA, particularly when the battery capacity has aged and is maybe only 1000mAh now |
| 12:32.47 | DocScrutinizer05 | and 100mA charging is what you'd expect to see from a charger without D+- short |
| 12:33.05 | rhombus | DocScrutinizer05: ok |
| 12:33.05 | KotCzarny | see what maxd said |
| 12:33.13 | rhombus | so I need a new charger |
| 12:33.18 | KotCzarny | connect that charger, then check the sys file |
| 12:33.34 | DocScrutinizer05 | also note that charging details changed from PR1.2 to PR1.3 iirc |
| 12:33.34 | KotCzarny | if it's 100, set it to 500 and observe |
| 12:33.41 | rhombus | KotCzarny: that works only if bq27 is installed |
| 12:33.54 | KotCzarny | you can try switching to cssu-thumb |
| 12:34.12 | KotCzarny | or cssu-testing |
| 12:34.13 | DocScrutinizer05 | errwut? |
| 12:34.33 | KotCzarny | ahm |
| 12:34.37 | DocScrutinizer05 | rhombus: please don't touch *thumb! (for now) |
| 12:34.49 | KotCzarny | thought cssu comes with newer module already |
| 12:35.46 | DocScrutinizer05 | no, CSSU is about fixing stuff |
| 12:36.01 | KotCzarny | hmm, where does that module coming from? |
| 12:36.09 | DocScrutinizer05 | PK |
| 12:36.15 | KotCzarny | i have pk53 |
| 12:36.19 | KotCzarny | and no such sys file |
| 12:36.30 | KotCzarny | it needs to load that module by hand? |
| 12:36.38 | DocScrutinizer05 | then the module is most probably blacklisted |
| 12:36.57 | KotCzarny | what was the module named again? |
| 12:37.16 | DocScrutinizer05 | no idea |
| 12:37.33 | KotCzarny | only mousedev is in blacklist |
| 12:38.33 | KotCzarny | ./bq27x00_battery.ko |
| 12:40.46 | rhombus | ok, off the phone |
| 12:41.04 | DocScrutinizer05 | ((<KotCzarny> see what maxd said)) sorry, I don't see that |
| 12:41.30 | KotCzarny | funny, seems that module is not used, and bq script works fine without it |
| 12:41.40 | rhombus | KotCzarny: I'm on IRC on my laptop on the LAN |
| 12:41.54 | DocScrutinizer05 | yes, BQ script works fine *only* without that module |
| 12:41.57 | KotCzarny | rhombus: download bq script on laptop then scp ? |
| 12:42.07 | bencoh | +1 for scp |
| 12:42.52 | DocScrutinizer05 | please leave rhombus alone with messing up his phone while no connection to internet |
| 12:43.08 | rhombus | whoa, just noticed something |
| 12:43.21 | rhombus | When I press on the status bar, I see |
| 12:43.23 | KotCzarny | bq script is safe |
| 12:43.27 | DocScrutinizer05 | a notifier "not enough charging power"? |
| 12:43.48 | rhombus | "Battery: 13% Battery charging 168/1234 mAh 3 hours" |
| 12:44.04 | DocScrutinizer05 | KotCzarny: don't you tell the inventor of bq script about its properties ;-) |
| 12:44.18 | KotCzarny | oh, tell me more, what are the risks? :P |
| 12:44.39 | rhombus | (reading all your previous messages) |
| 12:45.56 | rhombus | KotCzarny: I cannot get on the company intranet, I have to do this at home this evening |
| 12:46.23 | rhombus | Ok, I have closed all apps and dimmed the screen. Internet connections says "no connection" |
| 12:47.00 | DocScrutinizer05 | make sure you set to "scan for new APs: never" or somesuch, in internet/WLAN settings |
| 12:47.00 | rhombus | I will have to see about a replacement charger, the Nokia ones seem to be fakes |
| 12:47.16 | DocScrutinizer05 | s/never/manually/ |
| 12:48.17 | rhombus | DocScrutinizer05: I have : "Connect automatically: Always ask" |
| 12:48.30 | rhombus | is that the right place? |
| 12:48.42 | DocScrutinizer05 | next to it, moment please |
| 12:48.47 | DocScrutinizer05 | fetches phone |
| 12:50.05 | DocScrutinizer05 | Einstellungen - Suchinterval: Nie |
| 12:50.15 | DocScrutinizer05 | Einstellungen - Internet - Suchinterval: Nie |
| 12:50.32 | rhombus | From which Settings applet? |
| 12:50.37 | DocScrutinizer05 | yes |
| 12:50.55 | DocScrutinizer05 | settings - internet - >> |
| 12:50.58 | rhombus | from which one? |
| 12:51.01 | rhombus | Internet connections? |
| 12:51.04 | DocScrutinizer05 | yes |
| 12:51.13 | rhombus | Because there, I see only |
| 12:51.30 | rhombus | "Automatisch verbinden: Immer fragen" |
| 12:51.32 | rhombus | then on the right |
| 12:51.35 | rhombus | "Verbindungen" |
| 12:51.39 | rhombus | and "Speichern" |
| 12:51.49 | rhombus | "Suchintervall" is greyed out |
| 12:52.20 | rhombus | (And it says 30 min) |
| 12:52.49 | rhombus | Ok, now I set "WLAN" and changed the interval to never |
| 12:52.57 | rhombus | and then set it back to Always ask |
| 12:53.23 | rhombus | I'm going to leave this be until I get home tonight |
| 12:53.35 | rhombus | DocScrutinizer05: Until then, can you suggest a better charger? |
| 12:53.55 | DocScrutinizer05 | three buttins: "Autimatisch verbinden", "Suchinterval" and a checkbox "[ ] Bei verfuegbarkeit in WLAN wechseln" - values: "Beliebige Verbindung", "Nie", "[x]" |
| 12:54.25 | rhombus | DocScrutinizer05: What's wrong with "Immer fragen"? |
| 12:54.34 | DocScrutinizer05 | up to you |
| 12:54.50 | rhombus | Otherwise it will automatically try to connect, no? |
| 12:54.54 | DocScrutinizer05 | yes |
| 12:55.07 | DocScrutinizer05 | but not via WLAN when interval is set to "Nie" |
| 12:55.15 | rhombus | I don't have a data plan, so "always ask" is fine, it worked fine last night |
| 12:55.21 | DocScrutinizer05 | yes |
| 12:55.36 | rhombus | It tells me there is no connection, shows me a list, and lets me choose -- that's perfectly acceptable |
| 12:56.23 | rhombus | DocScrutinizer05: Can you suggest a charger? |
| 12:56.33 | rhombus | DocScrutinizer05: There are loads of Nokia fakes out there |
| 12:56.56 | DocScrutinizer05 | they are usually good fakes or even originals |
| 12:57.18 | rhombus | DocScrutinizer05: The product reviews I've been reading suggest otherwise |
| 12:58.21 | KotCzarny | buy some nokia phone from telco? ;) |
| 12:58.35 | DocScrutinizer05 | but no, I can't recommend a charger since I usually get them with phones |
| 12:58.45 | rhombus | KotCzarny: you're suggesting that any Nokia charger will do |
| 12:58.59 | rhombus | KotCzarny: I need not limit myself to the AC-10E, then |
| 12:59.14 | rhombus | KotCzarny: Do I have to start soldering shit? Because I don't have time for that |
| 12:59.24 | KotCzarny | rhombus: for slow charging any will do |
| 12:59.34 | DocScrutinizer05 | basically any charger will do as long as it has the (usual) 1000mA+ and it has (needs check) a short between D+ and D- data line of USB |
| 12:59.43 | KotCzarny | for fast charging, it nees to follow a standard |
| 13:00.10 | rhombus | DocScrutinizer05: is that some sort of standard? |
| 13:00.20 | DocScrutinizer05 | and those without D+- short are useless even for slow charging |
| 13:00.38 | rhombus | DocScrutinizer05: What does it need to support fast charging? |
| 13:00.40 | DocScrutinizer05 | rhombus: yes, it's one of 4 competing standards |
| 13:00.50 | rhombus | DocScrutinizer05: What's the standard called? |
| 13:01.05 | DocScrutinizer05 | they don't have names, it's a hige PITA |
| 13:01.12 | DocScrutinizer05 | huge* |
| 13:01.17 | KotCzarny | funny as it is, i havent ever seen a charger that wouldnt work with my n900 |
| 13:01.44 | DocScrutinizer05 | most chargers now follow the Apple standard which has a resistor network on D+/- |
| 13:01.44 | KotCzarny | ie. my gf's samsing travel charger works as expected and is doing fast charge |
| 13:01.52 | KotCzarny | *samsung |
| 13:02.02 | rhombus | KotCzarny: so I can get a Samsung travel charger, done |
| 13:02.12 | KotCzarny | um, results may vary |
| 13:02.13 | KotCzarny | ;) |
| 13:02.20 | KotCzarny | better just borrow one |
| 13:02.23 | KotCzarny | before buying |
| 13:02.28 | rhombus | KotCzarny: argh, then why do you make a claim like that? |
| 13:02.36 | KotCzarny | because it works in my case? |
| 13:02.57 | rhombus | KotCzarny: why wouldn't it work in mine? |
| 13:03.08 | KotCzarny | how many chargers did you try? |
| 13:03.23 | rhombus | KotCzarny: I haven't tried any apart from the one that was packaged with the phone |
| 13:03.39 | rhombus | Because I don't want to wreck the phone, for starters |
| 13:03.43 | KotCzarny | nah |
| 13:03.46 | KotCzarny | you wont |
| 13:03.49 | DocScrutinizer05 | rhombus: you best get a charger with USB A receptacle for regular USB cable. Then either check (and if needed fix) D+/- short, or mod a USB cable by opening the outer sleeve carefully and cutting+conecting the green and yellow cable |
| 13:04.12 | rhombus | DocScrutinizer05: can D-short cables be purchased? |
| 13:04.24 | DocScrutinizer05 | yes, but tricky to find |
| 13:04.27 | rhombus | I'll need a multimeter to check the cable, yes? |
| 13:04.35 | KotCzarny | rhombus: do you have access to any phone charger in house/at work? |
| 13:04.37 | DocScrutinizer05 | no |
| 13:04.37 | rhombus | I've been meaning to purchase one anyway |
| 13:04.40 | KotCzarny | just borrow for a charge or two |
| 13:04.43 | rhombus | KotCzarny: my wife has one or two |
| 13:04.44 | DocScrutinizer05 | you can check with your N900 |
| 13:05.08 | rhombus | I'm guessing infobot will tell me how |
| 13:05.15 | KotCzarny | if it has microusb, just try it |
| 13:05.16 | DocScrutinizer05 | I was busy to find the cmdline for you but I had to abort that to kicj in here once more to stop shit happen |
| 13:05.46 | rhombus | yes, I was getting a lot of dangerous advice |
| 13:05.51 | rhombus | ;-) |
| 13:06.01 | KotCzarny | you have backup, no? ;) |
| 13:06.07 | KotCzarny | if so, fire away! |
| 13:06.41 | rhombus | What I have little of is time, and I've already spent way too much of it on this today already. If you guys are around this evening, I might see you then. I have to get back to work. |
| 13:06.59 | DocScrutinizer05 | rhombus: cat /sys/devices/platform/musb_hdrc/charger |
| 13:07.01 | rhombus | But thank you all for your tips. Now at least I know why the charging performance on this phone has been modest |
| 13:07.09 | DocScrutinizer05 | 1=D+- short |
| 13:07.48 | rhombus | DocScrutinizer05: it says "1" |
| 13:07.59 | DocScrutinizer05 | let me verify |
| 13:08.36 | DocScrutinizer05 | yes, verified |
| 13:09.04 | rhombus | ok, so the charger can do fast charging? |
| 13:09.26 | rhombus | DocScrutinizer05: ^ |
| 13:09.34 | DocScrutinizer05 | it can't (fastcharging means > 1A), it just *claims* it could |
| 13:09.46 | rhombus | ok |
| 13:09.50 | DocScrutinizer05 | I.E it has D+- short |
| 13:09.59 | rhombus | but I can verify that any other charger i connect at least has D+-short |
| 13:10.05 | DocScrutinizer05 | it mustn't unless it can provide 1A |
| 13:10.11 | DocScrutinizer05 | yes |
| 13:10.33 | rhombus | so fast charging = must have D+-short |
| 13:10.41 | rhombus | no D+-short, definitely no fast charging |
| 13:10.42 | DocScrutinizer05 | and 1A plus |
| 13:10.47 | rhombus | right |
| 13:10.48 | rhombus | got it |
| 13:10.48 | DocScrutinizer05 | yes |
| 13:10.55 | buZz | i thought no short == no charging |
| 13:10.56 | DocScrutinizer05 | :-) |
| 13:10.57 | buZz | at all |
| 13:11.07 | DocScrutinizer05 | buZz: only 100mA |
| 13:11.19 | DocScrutinizer05 | it thinks it's a USB host |
| 13:11.20 | buZz | but not without D- and D+ connected to -something- |
| 13:11.28 | buZz | if its not connected to anything, it wont charge |
| 13:11.33 | rhombus | ok, friends, I have to work |
| 13:11.35 | rhombus | thanks again |
| 13:11.38 | DocScrutinizer05 | o/ |
| 13:11.39 | rhombus | see you this evening |
| 13:11.40 | buZz | (aka just V+ and GND) |
| 13:11.42 | rhombus | o/ |
| 13:11.45 | buZz | \o |
| 13:12.57 | KotCzarny | weird as it is, all ac-2e chargers i find are using barrel plug, not microusb |
| 13:13.07 | KotCzarny | could it be someone was fiddling with his? |
| 13:13.42 | DocScrutinizer05 | buZz: iirc the method is: when VBUS then set 100mA, check for D+- short and set 1A if seen, try USB host detection and start ENUM when seen |
| 13:13.56 | buZz | weird |
| 13:14.00 | DocScrutinizer05 | ENUM would negotiate up to 500mA then |
| 13:14.09 | buZz | i see zero charging happen on my selfmade powerbanks |
| 13:14.20 | buZz | which have D- and D+ just not connected |
| 13:14.45 | DocScrutinizer05 | powerbanks are weird, they stop VBUS when no load |
| 13:14.54 | buZz | points at selfmade |
| 13:15.01 | DocScrutinizer05 | hmm |
| 13:15.08 | buZz | this one never stops to power the outputs |
| 13:15.50 | DocScrutinizer05 | sorry can't speculate |
| 13:15.58 | buZz | thats ok :P |
| 13:16.07 | DocScrutinizer05 | you could trace what's going on |
| 13:17.36 | DocScrutinizer05 | to make it more challenging, this whole shit changed somewhere around PR1.2->PR1.3 and then again with Pali's open "BME" implementation |
| 13:17.54 | DocScrutinizer05 | so odds are when you got powerkernel, no charging at all is what you see |
| 13:18.24 | DocScrutinizer05 | depending on whether or not that bq27xx.ko and friends are loaded |
| 13:18.53 | buZz | oh i might actually have powerkernel yeah |
| 13:19.11 | KotCzarny | doc, can you find microusb based ac-2e charger? |
| 13:19.32 | DocScrutinizer05 | wouldn't even know what that is |
| 13:19.56 | KotCzarny | just google nokia ac-2e |
| 13:20.04 | KotCzarny | he has that charger and uses it |
| 13:20.24 | DocScrutinizer05 | he said the charger says 500mA |
| 13:20.31 | DocScrutinizer05 | don't need toknow more |
| 13:20.46 | KotCzarny | yes, but all chargers i find use barrel plug |
| 13:20.54 | DocScrutinizer05 | what? |
| 13:21.03 | DocScrutinizer05 | never seen any |
| 13:21.47 | KotCzarny | pity old nokia pages are already nuked |
| 13:22.00 | DocScrutinizer05 | aah wait, you say it's a fake ac-2e with micro-USB instead of barrel plug at cable end? |
| 13:22.03 | DocScrutinizer05 | possible |
| 13:22.14 | KotCzarny | ac-2e might be original, just cable changed |
| 13:22.17 | KotCzarny | ie. some refurb |
| 13:22.22 | DocScrutinizer05 | :nod: |
| 13:23.06 | DocScrutinizer05 | 500mA USB chargers are very unusual |
| 13:23.23 | DocScrutinizer05 | always have 70mA minimum, now 1000 |
| 13:23.28 | DocScrutinizer05 | 700mA* |
| 13:23.34 | KotCzarny | and maybe he was able to charge before, because he wasnt on cssu |
| 13:23.44 | DocScrutinizer05 | yes |
| 13:23.55 | KotCzarny | which means he is going to have flatbat soon |
| 13:23.56 | KotCzarny | ;) |
| 13:24.45 | DocScrutinizer05 | yeah, with 13% SoC |
| 13:25.10 | DocScrutinizer05 | that's why I advised to not do lots of futile messing to download and install stuff |
| 13:25.12 | KotCzarny | there is a chance his wife samsung charger would work |
| 13:25.44 | DocScrutinizer05 | or he just uses PC to charge |
| 13:26.25 | KotCzarny | shouldnt that warning be added to cssu page? |
| 13:26.34 | DocScrutinizer05 | which will work just fine unless you installed some kernel modules that make the whole thing bootloop ;-) |
| 13:27.01 | DocScrutinizer05 | shouldn't that get investigated and fixed in CSSU rather? |
| 13:27.11 | KotCzarny | that's also fine idea |
| 13:27.32 | KotCzarny | but i guess bme is pali's area of competence |
| 13:27.40 | DocScrutinizer05 | add bogus warnings based on a hypothesis... tzzz |
| 13:28.14 | DocScrutinizer05 | no, actually BME is my genuine competence. Pali's domain is his BME replacement implementation |
| 13:28.16 | KotCzarny | not so bogus, we have seen one sample today ;) |
| 13:28.28 | DocScrutinizer05 | do we? |
| 13:28.30 | jonwil | Just about ready to upload a bunch of stuff to cssu-devel (a lot of which I haven't tested and dont know if it works) |
| 13:28.40 | KotCzarny | how do you explain his almost empty device? |
| 13:28.51 | DocScrutinizer05 | you don't even have any data if the thing charged at 100mA or not at all |
| 13:29.06 | jonwil | which is why I want to check with fmg before I upload some of it just to see if he thinks its OK to upload or not |
| 13:30.25 | KotCzarny | kids today, saying the phrase then leaving |
| 13:30.29 | KotCzarny | ;) |
| 13:30.44 | DocScrutinizer05 | WLAN on - no powersave - 200 mA; Backlight on max +150 mA |
| 13:31.55 | DocScrutinizer05 | you wouldn't know the difference whether it's charging @100mA or not at all. So please don't suggest to add bogus warnings |
| 13:32.46 | KotCzarny | but note, he claims it was working fine before installing cssu |
| 13:32.53 | KotCzarny | and i suspect he was actively using it |
| 13:33.04 | DocScrutinizer05 | rather consider how to do proper investigation on your own device |
| 13:33.14 | KotCzarny | i have no fake chargers |
| 13:33.22 | KotCzarny | no bad cables either |
| 13:33.31 | DocScrutinizer05 | then don't do fuzzy conclusions |
| 13:35.51 | DocScrutinizer05 | when I hear "I suspect... (it worked...)" I always answer "I suspect there are other explanations too" |
| 13:36.25 | KotCzarny | got any? |
| 13:36.31 | DocScrutinizer05 | see above |
| 13:37.17 | DocScrutinizer05 | I'm not wasting my time on suspecting a likely usage pattern a few years ago, or whatever |
| 13:37.46 | KotCzarny | usage pattern 'device left overnight with wifi on and charger connected' |
| 13:38.00 | DocScrutinizer05 | headdesks |
| 13:38.30 | DocScrutinizer05 | read what I said: associated to AP (very low WLAN power consumption) and with dim backlight |
| 13:39.03 | DocScrutinizer05 | now please stop that |
| 13:40.45 | DocScrutinizer05 | you don't even know if power saving setting has chaged during reflash and upgrade |
| 13:41.38 | DocScrutinizer05 | and you don't know if backlight on or off |
| 13:41.45 | KotCzarny | he checked, it's at 'max' |
| 13:41.50 | KotCzarny | (wifi power save) |
| 13:41.55 | DocScrutinizer05 | basically we know nothing at all |
| 13:42.47 | DocScrutinizer05 | meh, wasting my time |
| 13:48.29 | DocScrutinizer05 | before: worked with unknown usage pattern (most likely WLAN turned off and backlight turned off) allegedly 3 days standby. NOW: reflashed and upgraded to CSSU, on a supposedly broken charger overnight, then in use for at least 6h and now at 13% charge -- "DAMN there is something wrong!!! We should add a warning that CSSU has a bug in charging" ... No Way! |
| 13:51.42 | *** join/#maemo till (~till@vispillo.org) |
| 13:52.22 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 13:55.52 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 13:56.05 | DocScrutinizer05 | please google "powersupply foldback" for a story about how a 500mA charger could reduce voltage to a point where only a few mA would flow, when overload detected. Overload is possibly under very specific conditions when you attach a 500mA charger to N900 |
| 13:57.02 | DocScrutinizer05 | overload *not* likely with >>[2017-10-16 Mon 13:49:18] <rhombus> I routinely did partial charges (from say 50 - 60 % to 100 %) in the evenings or over night<< |
| 13:58.04 | DocScrutinizer05 | as a re: >>[2017-10-16 Mon 15:36:26] <KotCzarny> got any?<< |
| 14:53.54 | *** join/#maemo Kabouik (~kabouik@236.34.200.37.customer.cdi.no) |
| 15:07.24 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 15:08.30 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 15:17.13 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 15:34.21 | DocScrutinizer05 | http://paste.opensuse.org/15528693 |
| 15:34.46 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:34.57 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 15:35.11 | DocScrutinizer05 | seems device is a tad busy immediately after unplugging charger |
| 15:36.20 | DocScrutinizer05 | ...or the calculated corrected remaining energy in cell gets adjusted by bq27200 chip due to battery chemistry and temperature settling |
| 15:37.11 | DocScrutinizer05 | or it's just a random factor from IRC traffic to xchat ;-) |
| 15:38.11 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 15:48.51 | *** join/#maemo Vajb (~Vajb@85-76-67-253-nat.elisa-mobile.fi) |
| 15:49.03 | DocScrutinizer05 | aah, I know (maybe). It's probably nased on CACT x *current* VOLT and the latter changes with load thanks to battery ESR |
| 15:49.17 | DocScrutinizer05 | based* |
| 15:55.37 | KotCzarny | https://crocs.fi.muni.cz/public/papers/rsa_ccs17 |
| 15:55.51 | KotCzarny | is there a chance it helps break some maemo's core keys? |
| 15:56.01 | KotCzarny | ie. repo keys? |
| 16:02.07 | DocScrutinizer05 | what for? |
| 16:04.03 | DocScrutinizer05 | <PROTECTED> |
| 16:04.05 | DocScrutinizer05 | 17:50 4115 96 96 -41 1098 1098 1098 65535 1606 25 NOACT:0 IMIN:0 CI:0 CALIP:0 VDQ:1 EDV1:0 EDVF:0 |
| 16:04.06 | DocScrutinizer05 | 17:55 4131 96 96 -13 1095 1095 1095 65535 4882 25 NOACT:0 IMIN:0 CI:0 CALIP:0 VDQ:1 EDV1:0 EDVF:0 #1098-1095=3mAh, per 5min= 36mA avg |
| 16:04.08 | DocScrutinizer05 | 18:00 4131 96 96 -14 1094 1094 1094 65535 4496 24 NOACT:0 IMIN:0 CI:0 CALIP:0 VDQ:1 EDV1:0 EDVF:0 #1095-1094=1mAh, per 5min= 12mA avg |
| 16:06.59 | *** join/#maemo geaaru (~geaaru@host109-170-dynamic.8-87-r.retail.telecomitalia.it) |
| 16:09.48 | DocScrutinizer05 | KotCzarny: I doubt Nokia generated their signing keys for repos by using >>a software library adopted in cryptographic smartcards, security tokens and other secure hardware chips manufactured by Infineon Technologies AG<< |
| 16:10.57 | DocScrutinizer05 | anyway it would be worth lottle to break their signature |
| 16:11.05 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 16:11.10 | DocScrutinizer05 | little, even |
| 16:11.34 | DocScrutinizer05 | unless, for Harmattan maybe |
| 16:19.56 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 16:20.24 | DocScrutinizer05 | http://paste.opensuse.org/25948187 shows how the more on-spot measurements for mA and derived values like TTE reproduce noise from random system activity, while the delta-NAC is relatively steady (though corse granularity) at ~3mAh/5min aka 36mA |
| 16:21.54 | DocScrutinizer05 | this is idle device with WLAN on PSM-max with AP supporting that, locked, with xchat running in background |
| 16:22.39 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 16:27.16 | DocScrutinizer05 | 1098 - 1080 NAC = 18mAh per 30min = 36mAh/h :-D |
| 16:28.14 | DocScrutinizer05 | http://paste.opensuse.org/737649 |
| 16:32.49 | DocScrutinizer05 | avrage over all spot readputs of current (8 points): 37mA |
| 16:33.59 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 16:38.38 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 16:52.52 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 17:07.09 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 17:07.24 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 17:22.01 | DocScrutinizer05 | http://paste.opensuse.org/9666482 54 * 50 / 90 = 36 |
| 17:22.05 | DocScrutinizer05 | :-)) |
| 17:22.27 | DocScrutinizer05 | s/50/60/ |
| 17:28.19 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 17:31.38 | *** join/#maemo LjL (~ljl@unaffiliated/ljl) |
| 17:44.03 | *** join/#maemo jkepler (~Thunderbi@gateway/vpn/privateinternetaccess/jkepler) |
| 18:42.17 | DocScrutinizer05 | https://www.kb.cert.org/vuls/id/228519 hmm lol, hope we can get a wpa-supplicant update soon |
| 18:43.19 | *** join/#maemo Kabouik_ (~kabouik@188.165.85.239) |
| 18:53.51 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 18:54.32 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 18:56.40 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 18:57.55 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 18:58.26 | DocScrutinizer05 | dang, maemo doesn't use wpa-supplicant, eh? |
| 19:17.56 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 19:29.26 | *** join/#maemo eMHa (~mh@p200300738E0CE800267703FFFE6CC360.dip0.t-ipconnect.de) |
| 19:43.56 | *** join/#maemo louisdk (~louisdk@5.103.138.205) |
| 19:45.08 | *** join/#maemo eMHa (~mh@p200300738E0CE800267703FFFE6CC360.dip0.t-ipconnect.de) |
| 19:45.49 | DocScrutinizer05 | let's see if TI conmes up with a new firmware for the WL12xx then. The benefits of non-FSF-RYF compliant firmware that does _nit_ live in a ROM in WLAN chip |
| 19:46.04 | DocScrutinizer05 | _not_, even |
| 19:47.42 | DocScrutinizer05 | [2017-10-16 Mon 21:23:44] <DocScrutinizer05> is the communication "fixed" when only one of both has the patches? [2017-10-16 Mon 21:24:05] <fromport> DocScrutinizer05: yes <fromport> it is a man in the middle attack and you have to convince both sides to re-use a previous key. <fromport> if one of the sides refuses, you are already safe |
| 19:47.57 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 19:59.36 | *** join/#maemo thuttu77 (~thuttu77@82-181-37-124.bb.dnainternet.fi) |
| 19:59.39 | sicelo | DocScrutinizer05: that's the vuln i showed yesterday ... i didn't quite understand why you said it's a good thing |
| 20:01.07 | sicelo | n900 doesn't use wpa_supplicant .. but i won't be surprised if eapd (what we use) is just as vuln. someone's got to test |
| 20:02.36 | sicelo | from what i understood, it is not really a firmware issue, so we don't necessarily need wl12xx. |
| 20:10.03 | DocScrutinizer05 | sicelo: yes |
| 20:10.52 | DocScrutinizer05 | it's unclear where the WPA protocol gets handled on maemo |
| 20:10.59 | DocScrutinizer05 | to me, at least |
| 20:17.34 | sicelo | eapd |
| 20:18.25 | sicelo | you can use wpa_supplicant though, if you first stop wlancond, and can live with having some applications get confused about connectivity state |
| 20:21.23 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 20:58.44 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 21:14.53 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 21:50.24 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 22:18.35 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 22:20.55 | *** join/#maemo Kabouik- (~kabouik@236.34.200.37.customer.cdi.no) |
| 22:22.59 | jonwil | damn, I closed the window and now I cant remember who fmg told me to talk to about cssu-testing |
| 22:39.39 | *** join/#maemo cyteen (~cyteen@230.178.93.209.dyn.plus.net) |
| 23:05.09 | *** join/#maemo lawl (~lawl@ns332320.ip-37-187-123.eu) |
| 23:13.09 | *** join/#maemo cachoahio (~reoplo@50.28.130.186) |
| 23:13.10 | *** part/#maemo cachoahio (~reoplo@50.28.130.186) |
| 23:17.40 | *** join/#maemo frapha (~froil@50.28.130.186) |
| 23:17.41 | *** part/#maemo frapha (~froil@50.28.130.186) |
| 23:30.36 | DocScrutinizer05 | merlin1991: |
| 23:39.35 | DocScrutinizer05 | sicelo: that sounds extremely promising |
| 23:40.04 | DocScrutinizer05 | jonwil: seen this?^^^ [2017-10-16 Mon 22:18:25] <sicelo> you can use wpa_supplicant though, if you first stop wlancond, and can live with having some applications get confused about connectivity state |
| 23:44.49 | jonwil | I suspect the answer is to figure out what external interfaces are exposed by the wlan system (wlancond, eapd, icd plugins, related connectivity UI bits) then figure out who else needs those interfaces and go from there. It probably isn't that hard, even the gconf keys could be figured out fairly easily with a bit of work in IDA |
| 23:45.28 | jonwil | Then you could easily rip the whole subsystem out (including the ICD plugins and related UI bits) and replace it with something else based around wpa_supplicant |
| 23:45.59 | jonwil | I am busy getting things into cssu-devel and also cleaning up my pigsty of an apartment so I wont be doing that right now |
| 23:48.12 | jonwil | If you replace things like connui-conndlgs-wlan and connui-iapsettings-wlan as well as the lower level bits it becomes even easier (a lot of the gconf keys for example are only used by that stuff and don't get used outside the wlan subsystems) |
| 23:48.53 | jonwil | Bonus is that once this work is done, all you need is a new GPRS plugin and you could replace ICD completly with something new without much effort |
| 23:56.35 | *** join/#maemo cyberlyra (~cyberlyra@cpe-23-240-11-86.socal.res.rr.com) |
| 23:59.57 | *** join/#maemo FalconSpy (falconspy@ip72-208-230-47.ph.ph.cox.net) |
| 23:59.57 | *** join/#maemo FalconSpy (falconspy@unaffiliated/falconspy) |