**** BEGIN LOGGING AT Tue Jul 09 03:00:00 2013 Jul 09 03:02:10 hello Jul 09 03:03:13 I was coming to my problem ssu button "reboot device" Jul 09 03:03:59 action after push button reboot devise with ssu application Jul 09 03:04:10 http://pix.toile-libre.org/?img=1373338899.png Jul 09 03:04:35 have you meet this problem Jul 09 03:04:38 ? Jul 09 03:07:53 to see this button, press the power button on the n900, ssu and choose the application and look in the parameter there is a "reboot devices" button and after the restart I no more character Jul 09 04:22:58 Now I have yet another problem... modest claims 'device storage full. remove data to free memory' even though there are 10G free on mydocs, 790M on opt, 148M on /... Jul 09 04:35:50 And HAM doesn't show catalogues anymore. what a mess... Jul 09 04:46:11 fs broken, probably went read-only Jul 09 04:51:34 fs? hw or sw? Jul 09 04:53:56 ShadowJK: in any case, I can still create files on all fs Jul 09 04:54:16 I also checked for inode limits Jul 09 06:58:45 Shapeshifter: i found that too, modest's database is rather fragile... it appears to consist of a memory-mapped file with raw C data structures in it... Jul 09 06:59:13 Shapeshifter: and also, maemo will never check or repair the filesystem if it's broken... yay... Jul 09 06:59:21 Shapeshifter: check dmesg for fs errors, reflash... Jul 09 07:04:35 my N900 messed up it's /home fs couple of a weeks ago. It happened during regular day, just noticed that I could not browse any of the photos I had taken. Restarted phone and nothing worked properly after that point. Tried to fsck the /home, but there was always some process locking the fs, so I ended up reflashing. Jul 09 07:07:48 japa-fi: run out of space ? Jul 09 07:08:51 jpinx, I don't think so. I did have space on /home. well, at least on MyDocs and I had not done any installing lately Jul 09 07:09:03 Don't have that many items installed anyway Jul 09 07:10:07 only asking because I almost borked my n900 by taking too many movies ;) Jul 09 07:11:46 my current /home has 1500megs (80%) available, /home/MyDocs lot more. Jul 09 07:13:01 I did have extended call log -software set to store quite bit of call information, so in theory it could have filled up the filespace, but even getting filesystem full don't result to corrupted fs. or does it? Jul 09 07:14:22 Aside the pain of loosing some contact information and some photos I thought I would not think of worth anything, I'm kind of happy that I have now reflashed my phone. Jul 09 07:15:24 Because it made me aware of backup menu, I now have latest stable kernel-power (might not had that version prior), have teetian and in general the phone is in good shape without software rot Jul 09 07:15:38 If I could just get the blessN900 work.. Jul 09 07:18:58 I thought BackupMenu has ways to allow one to fsck those other partitions that one cannot fsck whilst running the device normally. Jul 09 07:19:38 psycho_oreos, Yes, I didn't have backup menu prior to my crash. It would have saved my butt.. Jul 09 07:21:32 Looking at "mount" command, it seems that /home is mounted as ext3. I don't think ext3 would normally corrupt data when the partition is already full and there's more data to be inserted. I think the loss of power would be one of the cases that would result in dirty filesystem. Jul 09 07:21:52 Kind of irony: at home I have a NAS where I store my stuff (pictures, docs etc). The NAS has 2 drives, one being master, on which an incremental backup is made on daily basis to the slave. On top of that I rsync the contents to a hosted server (which has it's own backups etc). Yet I had no backup strategy for my phone.. Jul 09 07:22:54 psycho_oreos, Yeah, my experiences with ext3 (and ext4) with linux is that it's very difficult to get it corrupted. Jul 09 07:23:22 I rememeber when my /home was full (because ironically my /opt was full and needed to move some more stuff into /home/user/MyDocs and /home/user/MyDocs is formatted as ext3 mind you). I couldn't add a new contact, it kept giving me error about unable to store the new contact. Jul 09 07:24:39 heh, you learn that a backup strategy would be ideal for devices/smartphones. I guess N900 sort of paved in that way first, especially when tinkering. Jul 09 07:25:07 japa-fi, yeah so I wouldn't personally rule out ext3 to get corrupted when its already full. Jul 09 07:25:50 ext4 had issues with large files but that was addressed to years ago. Jul 09 07:27:22 /dev/mmcblk0p1: LABEL="Nokia N900" UUID="4BB1-E781" TYPE="vfat" <-- MyDocs is fat by default Jul 09 07:27:31 BlessN900 is also broken on my setup, I am unsure what broke it but I　guess I could look into it. Jul 09 07:28:09 Yeah its FAT32 by default is for compatibility on many scales. Though I deliberately made mine ext3 for various reasons that suits me. Jul 09 07:28:17 psycho_oreos, BlessN900 and kernel power have something against each other. Removed blessn900 to be able to take images (and scan QR codes) Jul 09 07:29:44 japa-fi, When you had BlessN900 installed and kernel-power you couldn't use any other camera programs to take photos or scan QR codes? o.O hmmm I guess I'll need to look into that. I have BlessN900 installed but I　think camera program was still working (except for BlessN900 of course). Jul 09 07:31:06 psycho_oreos, Yes. Having blessN900+kernel power, I could not start the regular camera app. I could not start the mbarcode application, nor blessN900 itself. They would crash prior finnishing loading. Jul 09 07:34:16 japa-fi, I just took a random photo out of curiousity. Running the latest kp42 here and also have BlessN900 installed. The normal camera app still allows me to take photos, it also stores the photos properly as well it seems. Jul 09 07:37:54 FCam seems to be borked on my end, it can take photos but it won't store them. mBarcode works currently with those standard barcodes, I haven't tested QR codes yet. Jul 09 07:39:54 QR code is working, just tested on a random QR code. I guess being able to scan for QR code or those standard barcode works is kinda moot if it already could sense the standard barcode already. Jul 09 08:01:08 psycho_oreos, Linux Nokia-N900 2.6.28.10-power50 Jul 09 08:01:53 japa-fi, Linux Nokia-N900 2.6.28.10-power52 #1 PREEMPT Sat Apr 6 11:59:23 UTC 2013 armv7l GNU/Linux Jul 09 08:02:13 Is that dev version? Jul 09 08:02:40 Not that I would know having kp52 would necessarily fix anything, I got some errors whilst running blessn900, but the output isn't useful. FCam doesn't seem to report decent errors. Jul 09 08:03:00 I think so, not too sure. I usually have extras-devel enabled on my device :) Jul 09 08:04:03 Any strange reboots / shutdowns? Jul 09 08:05:18 Prior my reflashing I had somewhat unstable phone, couple of times a week it would have just turned off unexpectedly which I would only notice after the thing had happened. ("No wonder I got no calls") Jul 09 08:05:57 No strange reboots/shutdowns to my knowledge, though ymmv. Jul 09 08:09:03 http://privatepaste.com/73968692b0 <-- output of blessn900 from console. Notice how it keeps on saying failed to open panel socket, that was happening right throughout when I was trying to look for a random photo to take and trying to kill cameraui launcher app. Jul 09 08:16:45 psycho_oreos, how do I see my apt-get history? Jul 09 08:17:11 With yum i'd do: yum histoy Jul 09 08:18:30 japa-fi, that I wouldn't know :) Jul 09 08:18:54 I guess if you still keep the debs of installed files you could probably check the mtime on them. Jul 09 08:19:48 I have no idea what "yum history" does, but on your standard debian installation you'd have /var/log/dpkg.log and more stuff under /var/log/apt Jul 09 08:21:08 yum history example: http://paste.fedoraproject.org/23874/58051137 Jul 09 08:22:20 yum history info ## (## is number) will give more details on the transaction Jul 09 08:23:08 dpkg.log would be the closest match that I'm aware of. feel free to write a parser that produces something similar. Jul 09 08:23:26 Nokia-N900:~# /opt/blessn900/blessn900 Jul 09 08:23:26 Could not parse application stylesheet Jul 09 08:23:26 Cannot open '/dev/video0': 2, No such file or directory Jul 09 08:24:23 actually, /var/log/apt/history.log might be better for quick review Jul 09 08:24:29 Yeah you have a completely different error. Though the error seems to do with the missing libs or something. Jul 09 08:25:17 installing blessN900 pulls fcam_drivers with it. I wonder if there still is a version issue. What is your fcam_drivers version? Jul 09 08:25:47 (and how do I list mine from command line, withtou the GUI) Jul 09 08:25:56 1.0.7-2 Jul 09 08:26:03 dpkg -l| grep fcam Jul 09 08:26:28 wnd seems to be on the money there with /var/log/apt/history.log. I googled and haven't found a better alternative. Jul 09 08:28:18 fcam-drivers 1.0.6-1 Jul 09 08:28:54 Possibly a little outdated I suppose, then again I really don't know if updating fcam-drivers would honestly help. Jul 09 08:30:05 I mean FCam on my end can see whatever the camera can see, it can take photos but it cannot store them. There's no meaningful error output from FCam when ran in terminal and I haven't bothered stringing it yet. Jul 09 08:33:44 Enabled extras-devel and updated fcam_drivers. Now restarting.. Jul 09 08:41:33 Whoppee, works. http://tinypic.com/m/fx84n7/3 <-- regular cam would have missed the shadows or burned the highlights Jul 09 08:46:09 japa-fi: BlessN900 makes the blue vignetting on the N900 really obvious though :( Jul 09 08:46:41 also, probably belongs on #harmattan, but the N9 has a really strong fisheye effect. Jul 09 08:50:16 japa-fi, you took that photo with FCam not long ago right? I just realised why FCam wasn't saving.. the actual cause was most likely because /home/user/MyDocs/FCamera isn't in trackerd's config or something. I　can see all those photos that I took lol. Jul 09 08:50:45 psycho_oreos, Taken: 2013:07:09 11:39:49 Jul 09 08:50:52 It's now 11:50 here :) Jul 09 08:51:27 Ahh yeah, definitely just now. So FCam works but not blessn900, hmm. Jul 09 08:53:01 blessn900 0.49-4 Jul 09 08:53:06 * psycho_oreos rebuilds tracker database. Jul 09 08:53:30 Same version as yours. Jul 09 08:55:30 I wonder if fcam-drivers are really needed anymore since kp52. I thought FCam wasn't working so I started diving in and did up a nasty hack by symlinking the installed kp modules (by fcam-drivers package) with the latest kp bundled files. FCam still works apparently. Jul 09 08:58:26 Wait.. what.. I　just noticed there was EXIF data and you have blessn900 working?　o.O Jul 09 08:59:10 psycho_oreos, yes. installing the updated fcam_drivers from etras-devel did the trick Jul 09 08:59:52 IIRC, the default cam driver does post processing for camera-ui only, and can't do anything fancy, so fcam-drivers will always be needed. Jul 09 09:00:07 japa-fi, funnily enough it doesn't work for me. I'll try reinstalling I suppose after tracker-{indexer,extract} finishes doing rebuilding of db. Jul 09 09:01:14 Yeah though in my case I already have fcam-drivers installed and when I load up blessn900 it freezes at the camera screen, showing nothing at all. Jul 09 09:07:50 psycho_oreos: i think fcam has trouble saving photos anywhere bit MyDocs/DCIM Jul 09 09:08:09 in my case i made hdrcapture save photos by making the stock camera a Jul 09 09:08:27 er save one in MyDocs/DCIM Jul 09 09:09:01 still its iffy Jul 09 09:22:34 psycho_oreos: fcam drivers are general purpose better cam drivers that give better resilts to all cam apps Jul 09 09:25:55 DocScrutinizer05: BTW, fcam-drivers dump sensor output to RAM, right? Jul 09 09:25:55 JPEG conversion etc. is done per-app, and a large reason of why fcam-based apps are slightly slower than cam-ui. Jul 09 09:25:55 DocScrutinizer05, ahh thanks. Though its probably outdated, the last one that it seems to be compiled on was power44. Then again I guess it doesn't really need fixing/hacking :). I managed to get blessn900 to work all of the sudden, now it seems to save photos much slower than the first photo I managed to take with blessn900. The first photo was really "croppy" :/ Jul 09 09:27:43 I haven't looked into it, but I seem to recall pali telling me that all KP use same fcam driver Jul 09 09:29:31 so I dunno details about jpeg compression. On a related info I *think* I heard that OMAP DSP does jpeg compressing Jul 09 09:29:54 ah, right, the omap-isp does it. Jul 09 09:29:54 or maybe only de-compressing? Jul 09 09:30:53 there, I remembered - fancy things fcam does isn't built into ISP/DSP firmware, so ISP just dumps whatever the camera module gives out, and fcam processes it. Jul 09 09:31:13 sounds about right Jul 09 09:32:11 probably fcan kernel driver for cam module add a function to get raw data Jul 09 09:32:51 iirc the fcam driver just *added* a few functions Jul 09 09:33:12 and maybe fixed one or two minor bugs Jul 09 09:33:38 wouldn't be surprised if it also added new ones Jul 09 09:35:46 there been an issue with white balance causing greenish pictures in pre-PR1.1 iirc, now with CSSU cam I see occasional flickering between ok'ish picture and that greenish picture in viewfinder Jul 09 09:36:23 while I can't recall to ever have seen this with stock post-PR1.1 cam driver Jul 09 09:40:13 DocScrutinizer05: pretty sure it's a hw errata Jul 09 09:40:36 blue/green tinting with varying lighting is a thing on the N900 Jul 09 09:50:03 * DocScrutinizer05 wonders if that's somehow caused by the "6" in 5-6-5 RGB Jul 09 09:51:17 but then it was only viewfinder/LCD, since I bet the cam has internal 8-8-8 Jul 09 09:52:26 do the pictures come out ok? Jul 09 09:53:11 I don't know, I seen to never have managed to take a shot when that greenish viewfinder flickered up Jul 09 09:53:37 camera probably has twice as many green elements than red or blue Jul 09 09:54:02 tbh I never investigated in deep, I not even noticed it again ever, until recently Jul 09 09:58:37 jaska: right, I forgot about that detail Jul 09 09:59:33 well, if you feel curious, there's that cam module datasgheet Jul 09 10:00:45 somewhere in docs in maemo.cloud-7.de hidden Jul 09 10:01:16 (no please do NOT post the correct URL, neither here nor anywhere else) Jul 09 10:06:57 h iall Jul 09 10:06:59 hi all Jul 09 10:07:52 I have order today mugen power for n900, what amazed me that its hot item , it mean lots of users uses meamo, didn't know Jul 09 10:08:40 I don't think "hot item" does mean a thing Jul 09 10:08:48 it makes the N900 too big to put in your jeans pocket though Jul 09 10:08:56 and it does not cover the camera Jul 09 10:09:07 DrCode: it's kind of a bad battery nowadays Jul 09 10:09:30 i got my polarcell 1500mah the other day Jul 09 10:09:40 in the space of two bl-5js, you get a lot less than twice of what a good bl-5j holds Jul 09 10:09:52 Lava_Croft: suck it, i have a 1600mAh battery Jul 09 10:09:56 if you've got tight jeans, not even coins will fit in them Jul 09 10:09:59 so it depends Jul 09 10:10:10 lol Jul 09 10:10:12 Lava_Croft: (note: only suck it if you want) Jul 09 10:10:17 I read it in meamo site Jul 09 10:11:13 * DocScrutinizer05 often put beer can or beer bottle in his jeans' pocket Jul 09 10:11:23 L) Jul 09 10:11:47 srsly though, this battery is really cool Jul 09 10:11:54 i should tie my bl5js together Jul 09 10:12:16 not exactly confortable ;-P but useful when you need both hands to make a cigarette Jul 09 10:12:59 @Doc, who can be contacted with regards to Midgard, if there is anyone still around? Jul 09 10:13:09 the mugen back cover is well worth it, the battery not so much Jul 09 10:13:22 I see Jul 09 10:13:36 well, I will try it Jul 09 10:13:37 nemein guys, particularly Rambo/Eero Jul 09 10:13:41 i can't find that battery on aliexpress again :( Jul 09 10:14:02 it was listed as a 1700mAh Jul 09 10:14:05 I read that there is possible to make it with two bl5js Jul 09 10:14:09 yep Jul 09 10:14:34 is there reay made like mugen power? Jul 09 10:14:43 no Jul 09 10:15:07 what recommanded to buy? Jul 09 10:15:22 the akku polarcell bl-5j is standard-sized and it's 1500mAh Jul 09 10:15:22 ~battery Jul 09 10:15:28 hmm Jul 09 10:15:31 yes Jul 09 10:15:33 ~useless Jul 09 10:15:38 and friendly company Jul 09 10:15:57 the battery i have is unnamed but it's 1600mAh Jul 09 10:16:16 ok Jul 09 10:16:42 time to kick bot's ass via ssh, eh? Jul 09 10:16:57 seems it gone offline 1h ago Jul 09 10:17:13 my original bl-5j is in the box Jul 09 10:17:17 i bet it's dead by now Jul 09 10:18:10 i had a new one in one of the N900 boxes Jul 09 10:18:16 made me all happy to find it Jul 09 10:18:30 yeah but it's a subpar battery nowadays Jul 09 10:18:45 always has been Jul 09 10:19:10 lazy bot Jul 09 10:19:15 silly human Jul 09 10:20:19 DocScrutinizer: infobot joined! Jul 09 10:20:58 ~uptime Jul 09 10:21:06 ~+uptime Jul 09 10:21:07 - Uptime for purl - Jul 09 10:21:08 Now: 2m 40s running infobot 1.5.4 (SVN) -- linux Jul 09 10:21:09 1: 59d 8h 41m 19s running infobot 1.5.4 (SVN) -- linux, ended Sun Nov 14 18:39:57 2010 Jul 09 10:21:09 2: 57d 3h 9m 23s running infobot 1.5.4 (SVN) -- linux, ended Fri Jun 26 20:39:27 2009 Jul 09 10:21:09 3: 36d 20h 47m 14s running infobot 1.5.4 (SVN) -- linux, ended Tue Aug 4 17:38:59 2009 Jul 09 10:22:27 ~battery Jul 09 10:22:27 well, battery is made by Danionics http://www.danionics.com/products/icphh02.asp, or at http://www.handhelds.org/handhelds-faq/questions.html#AEN744 Jul 09 10:22:36 hmm Jul 09 10:23:11 ~listkeys battery Jul 09 10:23:12 Factoid search of 'battery' by key (12 of 15): as battery acid ;; heh, no bottom view. can't tell if the battery ;; batteryfaq ;; zaurus battery ;; battery damage ;; flips ibot's battery disconnect switch ;; battery-usage ;; wmbattery ;; battery life ;; ipaq battery ;; battery pack ;; true, but the lack of extra battery. Jul 09 10:23:16 ~useless Jul 09 10:23:17 * infobot starts crying and hides from kerio in the darkest corner of the room. :( Jul 09 10:27:27 lol Jul 09 10:27:31 ~battery disconnect switch Jul 09 10:27:32 * infobot powers off, forgetting all of his factoids. Jul 09 10:28:19 wut Jul 09 10:28:21 ~useless Jul 09 10:28:22 * infobot starts crying and hides from kerio in the darkest corner of the room. :( Jul 09 10:28:26 ok, that still works Jul 09 10:30:55 http://talk.maemo.org/showthread.php?t=65568 Jul 09 10:31:14 ~batterytest is http://talk.maemo.org/showthread.php?t=65568 Jul 09 10:31:15 DocScrutinizer05: okay Jul 09 10:41:32 Ref: batteries. I have quite new Nokia battery, yet it no longer charges more than ~80% (1100mhA as reported by some battery widget) Jul 09 10:43:01 "some battery widget" Jul 09 10:43:04 do a calibration Jul 09 10:43:43 Ah, it was qtbatterywidget Jul 09 10:44:15 have you made a bq27k calibration cycle? Jul 09 10:45:07 * japa-fi goes to https://www.google.com/search?q=bq27k+calibration+cycle&ie=utf-8& ... Jul 09 10:46:10 http://talk.maemo.org/showpost.php?p=1053809&postcount=846 Jul 09 10:49:21 I found http://talk.maemo.org/showpost.php?p=1247595&postcount=1369 Jul 09 10:53:52 "Remember that regular USB ports current limit is 500 mAh, and charge.sh use 1050 mA (charge21.sh 950 mA)." Jul 09 10:54:24 I was under the impression that one can't get more than 500mA from USB unless the device specifically negotiates/requests it Jul 09 10:56:35 you can't negotiate >500mA, per USB specs Jul 09 10:57:07 (not even the range of the value allows it, it's a byte*4mA iirc) Jul 09 10:57:25 or even *2mA Jul 09 10:57:39 (unsigned) Jul 09 10:59:41 ~bq27k-calibration is http://talk.maemo.org/showthread.php?p=1247595#post1247595 Jul 09 10:59:41 DocScrutinizer05: okay Jul 09 11:03:22 for the discharging: Should I just leave the display on, or additionally have some nasty webpage in Opera. Those seem to drain the CPU quite fast? Jul 09 11:03:56 read what the post you linked says Jul 09 11:04:18 tells to discharge the battery... Jul 09 11:04:24 "For proper unattended discharging/calibrating during you're asleep in the night, you want to set screen backlight to 'always on' and level 5 (will result in discharge during ~4h). " Jul 09 11:04:32 japa-fi: that depends on what you want to achieve Jul 09 11:04:38 i dont know if this works while sleeping during daytime Jul 09 11:06:17 the calibration result will vary depending on how hard to discharge the battery, 100% accurate calibration only for usage pattern that's similar to your calibration scenario Jul 09 11:06:38 higher load results in lower tested battery capacity Jul 09 11:07:09 obviously higher load also results in faster calibration since discharge phase takes shorter ;-) Jul 09 11:07:35 How do I set the screen backlight "always on"? I can select only up to 2 minutes Jul 09 11:08:39 DocScrutinizer05: so the proper way to discharge is via "slow drip" to avoid dropping battery voltage too fast? Jul 09 11:09:02 on a rule of thumb you might discharge a battery to a nominal measured capacity of 1600mAh when device sits in standby idle with drawing only 10mA (takes 160h then), while with brute force discharge you meter same cell at only 1200mAh (discharge takes 2h then) Jul 09 11:09:36 japa-fi: I use simple brightness applet for that. Indispensible applet Jul 09 11:10:10 rikanee: depends on what you want to calibrate to Jul 09 11:10:35 Perhaps I'll start by using the battery to halfway before going to the test process.. Jul 09 11:10:37 DocScrutinizer05: 'you can't negotiate' - A USB2 peripheral can speak USB1, and use features not present in the USB1 standard - like class devices say. If you update the firmware on your USB2 device to say it's USB3, can you then if plgugged into a USB3 socket do 900mA? Jul 09 11:10:52 rikanee: cell behave different to each other, when you compare ratio between fast and slow discharge Jul 09 11:11:28 SpeedEvil: I have no faintest idea Jul 09 11:11:34 :) Jul 09 11:11:37 possibly Jul 09 11:12:16 japa-fi: the calibration script starts by *charging* the battery! Jul 09 11:12:22 In principle, I should read the US2 spec Jul 09 11:12:27 USB3 Jul 09 11:12:40 I admit I didn't yet Jul 09 11:14:21 japa-fi: so the best way to use my calibration script is to plug in the device to fastcharger when you "come home", and then simply start the script. You'll find your device fully charged after some hours longer than usually needed for normal charging, but calibrated bq27k Jul 09 11:15:30 however keep in mind that bq27k is NOT used by "normal" (HAL/bme-based) battery meters Jul 09 11:17:21 so unless you use bq27200.sh or bq27k-detail.sh or one of the more nifty GUI meters that are based on bq27* I2C-get or kernel drivers (only available in KP), you won't see a difference Jul 09 11:18:30 ~bq27k Jul 09 11:18:38 ~bq27k-detail Jul 09 11:18:39 i heard bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2 Jul 09 11:19:03 ~bq27200 Jul 09 11:19:04 hmm... bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2 Jul 09 11:19:13 *shrug* Jul 09 11:20:25 DocScrutinizer05, any nifty gui meters that you could recomend? Jul 09 11:20:34 ^^^^ Jul 09 11:20:35 DocScrutinizer05: my battery is 1600mAh at a ~200mA constant draw Jul 09 11:20:38 ^_^ Jul 09 11:20:50 kerio: that's pretty good Jul 09 11:21:04 it was 1400mAh during the winter, though Jul 09 11:21:25 as a general rule those cells that have higher capacity also lose more of the available capacity on fast discharge Jul 09 11:21:46 i wonder if the 1700mAh rating was done through a very slow discharge Jul 09 11:22:00 In the settings window you can choose the informations to display, the type of percentage (module bq27x00, standard or dr_frost_dk based on his battery meter widget), the percentage style (graphical, standard progressbar or textual) and the widget opacity. Jul 09 11:22:08 I guess I had one already :--) Jul 09 11:22:20 * kerio almost suggests the whole bme replacement thing Jul 09 11:22:39 10mA/500mA: 1100mAh-cell: 1100mAh/1000mAh 1600mAh-cell: 1600mAh/1150mAh Jul 09 11:23:38 kerio: generally those ratings are *supposed* to be made at (iirc) C/10 Jul 09 11:23:53 yeah but it's a chinese battery :) Jul 09 11:23:59 sure Jul 09 11:24:07 i want to believe that they didn't outright lie Jul 09 11:24:12 they just obfuscated the truth Jul 09 11:24:22 at 1mA you can probably push a 1300mAh cell to 2200mAh Jul 09 11:24:29 unlike those 2700mAh "high capacity" batteries that end up being 800 Jul 09 11:24:35 mh, neat Jul 09 11:24:46 you can't quite do that on a n900 though Jul 09 11:24:54 right Jul 09 11:25:01 the absolute lowest i managed to get was like 8mA Jul 09 11:25:33 unless you parallel 30 or 40 of those cells ;-P Now THAT would be a nice mugen cover XP Jul 09 11:27:24 i wonder why they always pair two bl-5js Jul 09 11:27:31 instead of a bl-5j and a slightly bigger battery Jul 09 11:27:41 because of balancing issues of some sorts? Jul 09 11:27:51 generally the higher the capacity of a given formfactor cell, the higher the ESR. And a higher ESR causes higher loss on high discharge current, while on very low discharge current ESR is mostly irrelevant Jul 09 11:28:19 it seems counterintuitive though Jul 09 11:28:32 is that effect big enough to offset having a higher capacity? Jul 09 11:28:39 nah, it's very plausible Jul 09 11:29:19 and no, it usually isn't offsetting your higher capacity, until you trip a certain discharge current threshold Jul 09 11:30:19 (ESR) the higher the capacity, the thinner are your anodes to achieve larger active surface. Thinner annode means higher ESR Jul 09 11:30:57 (simplified picture) Jul 09 11:31:17 so there's nothing more to battery design? Jul 09 11:31:32 every li-ion is just the same thing with slightly different parameters? Jul 09 11:32:26 yes, basically that's it Jul 09 11:32:49 pff, EE is easy Jul 09 11:32:51 :P Jul 09 11:33:35 with same cell chemistry all cells are somewhat alike, just changing parameters like surface structure and thickness of anodes, minor tweaks to electrolyte, etc Jul 09 11:33:45 I'm missing the module bq27x00 for the qtbatterywidget :( Jul 09 11:34:16 japa-fi: this module comes with KP Jul 09 11:34:46 DocScrutinizer05, enabled by default? Jul 09 11:34:50 (I have kp50) Jul 09 11:35:00 and it's deprecated since it causes bme to segfault on restarts Jul 09 11:35:18 thus it's blacklisted in KP49+ Jul 09 11:38:07 japa-fi: find a battery meter app that uses I2Cget, this will work on all systems *except* those with bq27x00 kernel module loaded Jul 09 11:39:37 bq27x00 module MUST stay blacklisted unless you take special care about bme, possibly even completely replacing it, or making sure that bme always gets started when bq27x00 module is UNLOADED Jul 09 11:40:33 since bq27x00 module makes bme segfault on startup, and that causes even bootloops Jul 09 11:41:55 sure it's basically fremantle's/bme's fault, but for standard fremantle systems the standard bq27x00 module is forbidden Jul 09 11:42:01 it's incompatible Jul 09 11:42:08 DocScrutinizer05: bme proprietary? Jul 09 11:42:21 bme is a closed blob, yes Jul 09 11:42:46 hmm, that sucks Jul 09 11:42:48 and it uses direct /dev/i2c access to bq27200 chip Jul 09 11:43:29 as in open()? Jul 09 11:43:52 bq27x00 module exclusively locks that /dev/i2c permanently and thus bme when trying to open it -> segfault Jul 09 11:44:43 sime nifty fool added a botch to kp<48 to *globally* *disable* locking :-O Jul 09 11:45:01 bme sucks, yeah Jul 09 11:45:25 a segfault is as far as you can get from a graceful failure, really Jul 09 11:45:54 resulted in bme not segfaulting on trying to open 7dev/i2c when bq27x00 module loaded, but it might cause collisions on i2c bus resulting in arbitrary stuff in hardware emitting blue magic smoke Jul 09 11:46:56 kerio: for bme it doesn't matter *how* it quits. DSME will reboot the device anyway ;-P Jul 09 11:48:03 resulting in our beloved bootloop when you un-blacklist bq27x00 module Jul 09 11:48:53 unless you tweak initscripts really hard to not even try to start bme via dsmetool Jul 09 11:49:29 even then you're fscked since no more charging, which pretty much defeats any reasonable purpose of bq27x00 module ;-P Jul 09 11:50:10 so, bottomline: bq27x00 module is useful *only* for bme-replacement Jul 09 11:51:06 put a dummy bme module? Jul 09 11:51:15 bme is not a module Jul 09 11:51:18 and even then it's pathetic afaik, by not exposing all the info from bq27200 chip, and mangling other info fubar Jul 09 11:51:36 DocScrutinizer05: otoh, usb host mode with battery indicator and stuff Jul 09 11:51:44 jon_y: you could do that, but then you lose charging Jul 09 11:52:26 kerio: sigh Jul 09 11:52:59 yeah, hostmode immanetly garbles battery meter, since it also needs to stop bme Jul 09 11:53:34 but you can't do much about that unless you replace hald-addon-bme by sth that doesn't mind bme not running Jul 09 11:53:57 which is what pali's bme-replacement is all about, basically Jul 09 11:54:10 yep Jul 09 11:54:17 or at least it's the crux of that bme-replacement project Jul 09 11:56:06 ooh, on a stack-pop back to last night: the 1/3 blackout was for all houses on left side of my street. The energy company didn't know about any such problem until this morning ;-P Jul 09 11:57:12 heh, reminds me when the cell towers were out once Jul 09 11:57:20 nobody could call the cell provider :) Jul 09 11:57:21 * DocScrutinizer05 wonders what galaxy his neighbours are from, that not a single one of several dozen houses with several flats each noticed the problem until 8h after it happened Jul 09 11:58:05 I don't know what insanity happened but the service provider went black on the whole country Jul 09 11:58:06 DocScrutinizer05: wow, 8h to fix a blackout? Jul 09 11:58:49 about blackouts Jul 09 11:58:58 I had one that was 2 days long :| Jul 09 11:59:15 it isn't that bad now Jul 09 11:59:31 even more exciting: when I opened the warm water tap in my bathroom (24kW heater), my bathroom light went on, for a short while and dim. Now I assume that also "the bathroom light" of 2 dozen other hoeses' flats went on same time :-o Jul 09 12:00:11 DocScrutinizer05: you live in a place with winter? Jul 09 12:00:20 yes Jul 09 12:00:24 not now though Jul 09 12:00:43 but yeah, we have winters here Jul 09 12:00:55 during December Jul 09 12:01:04 ok, I have not seen warm water taps around Jul 09 12:01:11 DocScrutinizer05: are you kidding me Jul 09 12:01:16 except when I travel to countries further north Jul 09 12:01:17 germany is cold all the fucking time Jul 09 12:01:27 hah Jul 09 12:01:29 ~weather EDDN Jul 09 12:01:31 Nuernberg, Germany; (EDDN) 49-30N 011-03E 318M; last updated: 2013.07.09 1150 UTC; Dew Point: 51 F (11 C); Pressure (altimeter): 30.21 in. Hg (1023 hPa); Relative Humidity: 39%; Temperature: 78 F (26 C); Visibility: greater than 7 mile(s); Wind: from the ENE (060 degrees) at 6 MPH (5 KT) (direction variable) Jul 09 12:01:47 ~weather efva Jul 09 12:01:48 26 C Jul 09 12:01:49 Vaasa, Finland; (EFVA) 63-03N 021-46E; last updated: 2013.07.09 1150 UTC; Dew Point: 48 F (9 C); Pressure (altimeter): 29.97 in. Hg (1015 hPa); Relative Humidity: 52%; Temperature: 66 F (19 C); Visibility: greater than 7 mile(s); Wind: from the SSW (210 degrees) at 12 MPH (10 KT) (direction variable) Jul 09 12:02:03 26C is kind of nice, isn't it? Jul 09 12:02:06 my A/C is currently at 27 Jul 09 12:02:15 26c is a bit too hot Jul 09 12:02:22 really? Jul 09 12:02:28 indeed, I should close the windows Jul 09 12:02:37 average around 30s here in the noon Jul 09 12:02:44 oops, already closed Jul 09 12:02:58 STAY IN DOORS, you are not supposed to weather the sun Jul 09 12:03:00 I'm just waiting for the 32 to come here again Jul 09 12:03:15 jon_y: I can see why you don't have warn errr cold water taps Jul 09 12:03:22 yay for vienna where the temperature goes between -10 and +34 each year :D Jul 09 12:03:34 DocScrutinizer05: just a single tap :) Jul 09 12:03:57 some places have warm/cold taps, but they really connect to the same pipes Jul 09 12:04:00 it goes between -35 +30 here Jul 09 12:04:08 probably you're happy when the water is less than 25°C Jul 09 12:04:14 26C, hot? Jul 09 12:04:16 jeez. Jul 09 12:04:24 -40 some years Jul 09 12:04:28 32-35C @ ~100% humidity. Jul 09 12:04:33 25 water is COLD for me Jul 09 12:04:34 okay jaska, you win :D Jul 09 12:05:02 check out Moskow Jul 09 12:05:11 -45 to +40 iirc Jul 09 12:05:20 btw, I saw something perculiar today, a C++ programmer called assembly listing "bytecode" Jul 09 12:05:24 wtf bytecode?? Jul 09 12:05:44 moron Jul 09 12:05:49 supposedly a C++11 lecturer Jul 09 12:06:06 it's code, and it's made of bytes! Jul 09 12:06:24 like C++ Jul 09 12:06:28 I tend to think interpreters and VMs when bytecode comes in Jul 09 12:06:41 and rightly so Jul 09 12:07:03 bytecode is close to P-code Jul 09 12:07:06 DocScrutinizer05: yeah but you can't be certain that a text file is valid c++ Jul 09 12:07:11 in _my_ semantics Jul 09 12:07:15 also, int i; sizeof(i) <- runtime object information <-wtf?? Jul 09 12:07:40 man, I don't even know wtf Jul 09 12:07:41 which is my favourite c++ horror Jul 09 12:08:00 C does that, and it sure as hell is compile time Jul 09 12:08:20 yep Jul 09 12:08:28 sizeof becomes runtime on stuff like VLAs Jul 09 12:08:34 but that's also in C99, iirc Jul 09 12:09:06 hmm I never tried sizeof on VLAs Jul 09 12:09:53 * DocScrutinizer05 giggles at c++ coders breaking their fingers and screwing their brain trying to code assembler level stuff in c++ Jul 09 12:10:09 he actually did Jul 09 12:10:19 with objdump Jul 09 12:10:54 which he calls the disassembly code as bytecode Jul 09 12:11:13 it usually goes like "well, MY compiler does late binding there" "but the microsoft compiler does early binding" Jul 09 12:12:14 hmm, sizeof is still compile time with vla Jul 09 12:12:31 isn't it a bless to always use the exactly right tool for the task at hand? ;-P Jul 09 12:12:33 int a[argc] says sizeof(a) is 4 Jul 09 12:13:36 man, I feel almost like an old fart I read his lecture notes Jul 09 12:14:15 > using short instead of int for returning main() Jul 09 12:14:19 wait, what Jul 09 12:14:21 like Jul 09 12:14:27 short main(int argc, char **argv)? Jul 09 12:14:39 what the FUCK Jul 09 12:14:49 int main() {short ret; ... return ret;} Jul 09 12:15:05 his logic was $? goes only up to 255 Jul 09 12:15:11 oh, meh Jul 09 12:15:17 facepalm worthy Jul 09 12:15:19 it gets converted to int anyway, doesn't it Jul 09 12:15:23 * DocScrutinizer05 is temped to tell that story for the 1000th time, about that guy at Siemens who knew zilch but excel, and he wrote his own excel-based text editor, one char per spreadsheet cell Jul 09 12:15:44