**** BEGIN LOGGING AT Fri Apr 01 02:59:58 2016
Apr 01 03:00:12 <azkay_> i.imgur.com/BjJU9Pi.jpg someone should throw this into an n900
Apr 01 07:06:01 <kerio> azkay_: april fools
Apr 01 07:09:59 <azkay_> :P
Apr 01 10:58:41 <zGrr> moin :)
Apr 01 13:02:31 <Sicelo> i am trying to connect my N900 to a bluetooth serial device (car obd scanner). i can successfully bind the port (rfcomm0). when i type in minicom, the LED on the scanner comes on. however i never get a reply for any command i send. i am quite sure baud rate is fine (9600 8N1) as per the documentation. Have also tried 38400. when i press the enter key, no LED comes up. i tried connecting to the device using android, and it works. however android apps don't
Apr 01 13:03:58 <Sicelo> also, i have tried same from my 2nd N900, with exactly the same unhappy outcome
Apr 01 13:05:13 <liu_> n900
Apr 01 13:05:28 <Sicelo> yes, it is :)
Apr 01 13:06:09 <liu_> my english is bad
Apr 01 13:08:07 <Sicelo> if you have a question, you can just ask. we will try to undersand
Apr 01 13:08:20 <liu_> I can't install to ForecaWeather. do you have ForecaWeatherdeb?
Apr 01 13:08:44 <sixwheeledbeast> Sicelo: ELM OBD unit? I had fun getting mine to pair, but when I did works great with pyOBD
Apr 01 13:09:20 <sixwheeledbeast> Wasn't Foreca Weather on Ovi? I have used OMWeather for a long time now
Apr 01 13:10:19 <Sicelo> yes sixwheeledbeast. mine pairs fine. pyOBD connects and gets stuck after sending ATE0. so i thought to try it manually and see. unfortunately manually i have not had any success so far. works fine on my friend's android phone
Apr 01 13:10:28 <liu_> I from china . so I can't on ovi. 
Apr 01 13:11:30 <Sicelo> liu, make sure you have up-to-date repos. it is there
Apr 01 13:12:03 <liu_> OMWeather also bad
Apr 01 13:12:32 <Sicelo> i'm talking about foreca
Apr 01 13:13:05 <liu_> Can't install foreca
Apr 01 13:13:13 <sixwheeledbeast> Sounds like package management issue if you can't install anything.
Apr 01 13:13:32 <liu_> Network wall
Apr 01 13:14:20 <liu_> no , the others can be
Apr 01 13:15:00 <liu_> is network problems
Apr 01 13:17:00 <Sicelo> http://maemo-repos.com/apt-mirror/mirror/downloads.maemo.nokia.com/fremantle/apps/ ... it's there
Apr 01 13:19:07 <liu_> thanks
Apr 01 13:19:39 <Sicelo> sixwheeledbeast: still using pyobd? :)
Apr 01 13:19:52 <Sicelo> thread basically "died" unfortunately
Apr 01 13:20:39 <sixwheeledbeast> Sicelo: yep not regularly but every now and again for a long while.
Apr 01 13:21:07 <sixwheeledbeast> you can see from the thread when I first used it
Apr 01 13:21:33 <sixwheeledbeast> it's only a port, needs a lot of work to be n900 friendly imo
Apr 01 13:22:29 <Sicelo> if you don't mind, you could test for me if minicom/screen can connect to it :)
Apr 01 13:28:03 <sixwheeledbeast> Sicelo: I have to get back to work now, but if you want to send me some instructions of what you want to check and I'll try it later.
Apr 01 13:28:25 <Sicelo> tranks. will let you know.
Apr 01 13:30:19 <Sicelo> basically, as root, 'rfcomm bind 0 <bt_addr> 1' followed by 'minicom -D /dev/rfcomm0 -b 9600'. then you can try writing intp minicom the commands from tmo, such as ATZ,ATE0, etc
Apr 01 13:31:48 <Sicelo>  intp/into
Apr 01 13:41:27 <DocScrutinizer05> Sicelo: check RTS/CTS and software flow control
Apr 01 13:42:11 <DocScrutinizer05> rather, uncheck both ;-)
Apr 01 13:45:26 <Sicelo> i did. no luck :(
Apr 01 13:57:26 <DocScrutinizer05> try an electrical loopback - ooops this is BT not RS232 right?
Apr 01 13:58:56 <DocScrutinizer05> try ATE1 which enables echo on far end
Apr 01 13:59:30 <DocScrutinizer05> though I got NFC whats a ELM OBD unit
Apr 01 14:00:10 <DocScrutinizer05> engine canbus adapter?
Apr 01 14:01:22 <Sicelo> DocScrutinizer05: yes. :)
Apr 01 14:01:47 <DocScrutinizer05> aah k
Apr 01 14:02:15 <DocScrutinizer05> I guess those critters can be very tricky
Apr 01 14:02:29 <Sicelo> i'll try again
Apr 01 14:02:57 <DocScrutinizer05> AT cmdset is not exactly what canbus protocol speaks ;-)
Apr 01 14:03:30 <DocScrutinizer05> so it's prolly like a sort of "modem" I guess
Apr 01 14:04:17 <DocScrutinizer05> do you have a link to the tmo thread?
Apr 01 14:07:08 <DocScrutinizer05> aaaaaah! :-D  >>On Board Diagnostics (OBD)<<
Apr 01 14:08:23 <DocScrutinizer05> http://www.elmelectronics.com/obdic.html
Apr 01 14:10:05 <Sicelo> at, definitely
Apr 01 14:14:01 <DocScrutinizer05> yes, the interpreter chip speaks AT it seems
Apr 01 14:14:30 <DocScrutinizer05> there's a car manufacturer named "Saturn" ??
Apr 01 14:15:49 <DocScrutinizer05> anyway elmelectronics looks like decent source of info,  http://www.elmelectronics.com/obdhelp.html
Apr 01 14:19:50 <DocScrutinizer05> http://www.elmelectronics.com/DSheets/ELM322DS.pdf  >> RS232 baud rate  9600  baud //  Nominal data transfer rate when a 3.58 MHz crystal is used as the frequency reference. Data is transferred to and from the ELM322 with 8 data bits, no parity, and 1 stop bit (8 N 1).<<
Apr 01 14:20:26 <DocScrutinizer05> as standard as it possibly gets
Apr 01 14:24:38 <DocScrutinizer05> http://wstaw.org/m/2016/04/01/plasma-desktoplB2219.png
Apr 01 14:29:05 <alien2003> Hi! Do you have MyDocs in ext3? I need some help with mounting
Apr 01 14:31:06 <Sicelo> DocScrutinizer05: trying right now again. 
Apr 01 14:31:17 <DocScrutinizer05> Sicelo: try ATI (Info)
Apr 01 14:31:27 <alien2003> Sicelo: can you pls give me your /usr/sbin/mmc-mount?
Apr 01 14:31:32 <DocScrutinizer05> or "Identify"
Apr 01 14:31:43 <DocScrutinizer05> ATI<cr>
Apr 01 14:31:46 <Sicelo> alien2003: no ext3 here :)
Apr 01 14:31:51 <alien2003> sorry
Apr 01 14:32:11 <alien2003> I just need mmc-mount script to be capable to mount ext and vfat both. I have it broken :(
Apr 01 14:33:01 <DocScrutinizer05> alien2003: CSSU should take care, but... you prolly don't use CSSU krcv?
Apr 01 14:33:28 <alien2003> I use CSSU but I modified that file and now it can only mount ext3, not vfat
Apr 01 14:33:54 <Sicelo> DocScrutinizer05: no response to any command. not even the > prompt (which does appear on the android)
Apr 01 14:34:07 <DocScrutinizer05> alien2003: usually you simply use "-t ext3" parameter to the mount command
Apr 01 14:34:18 <alien2003> DocScrutinizer05: I mean automount
Apr 01 14:34:32 <alien2003> I can mount it manually without any problems
Apr 01 14:34:35 <Sicelo> however, as i type the characters, "a" "t" etc, the led on the scanner comes on to indicate it received the data
Apr 01 14:34:53 <DocScrutinizer05> try ATE1
Apr 01 14:35:06 <DocScrutinizer05> upper case A snd T
Apr 01 14:35:19 <DocScrutinizer05> and use CR to end the line
Apr 01 14:35:32 <DocScrutinizer05> try ^J and ^M
Apr 01 14:36:45 <DocScrutinizer05> also make sure no other process has opened your interface device, use lsof|grep
Apr 01 14:36:47 <Sicelo> no dicel actually there's absolutely no sign of life on pressing Enter, Ctrl+J, Ctrl+M
Apr 01 14:39:06 <Sicelo> i will try on my computer when i'm back home. maybe n900 minicom has problem? not sure. but screen does't succeed either
Apr 01 14:39:25 <Sicelo> nothing else using the device
Apr 01 14:44:08 <alien2003> can you pls pastebin me default CSSU's /usr/bin/mmc-mount file?
Apr 01 14:48:31 <alien2003> just default file from CSSU
Apr 01 15:20:06 <sixwheeledbeast> Sicelo: another thought is have you tried a different vehicle.
Apr 01 15:27:10 <Sicelo> not yet. but for now i'm failing to connect even to the dongle itself (powered). i can connect just fine from the droid without being in a car
Apr 01 15:35:30 <Sicelo> okay .. minicom on pc not successful either. absolutely weird
Apr 01 15:54:05 <sixwheeledbeast> I haven't got minicom installed I am also struggling to locate my OBD reader :S
Apr 01 15:54:34 <sixwheeledbeast> If it will not work with pc there maybe more to it.
Apr 01 15:57:35 <Sicelo> i don't understand what could be the cause. the OBD reader clearly does receive my input, but either doesn't reply, or 'something absorbs' them
Apr 01 16:06:15 <DocScrutinizer05> alien2003: http://maemo.cloud-7.de/maemo5/usr/sbin/mmc-rename.sh  err wait...
Apr 01 16:06:37 <alien2003> DocScrutinizer05: I just fixed everything...
Apr 01 16:06:43 <alien2003> just reinstalled from scratch
Apr 01 16:06:46 <alien2003> thank you anyway
Apr 01 16:08:05 <DocScrutinizer05> http://maemo.cloud-7.de/maemo5/usr/sbin/mmc-mount
Apr 01 16:10:59 <DocScrutinizer05> wasted another 5.2MB of my tiny server space :-)
Apr 01 16:11:13 <DocScrutinizer05>  http://maemo.cloud-7.de/maemo5/usr/sbin/
Apr 01 17:50:29 <luke-jr_> wow, N900 shut down for heat
Apr 01 17:53:06 <kerio> D:
Apr 01 17:56:55 <kerio> DocScrutinizer05: how do i clear VDQ
Apr 01 17:59:45 <DocScrutinizer05> clear?
Apr 01 17:59:56 <DocScrutinizer05> start charging
Apr 01 18:01:58 <DocScrutinizer05> VDQ goes 1 on batt full and gets cleared whenever something messes with proper contiguous discharge until learning
Apr 01 18:10:57 <DocScrutinizer05> https://www.youtube.com/watch?v=HMQkV5cTuoY
Apr 01 18:11:03 <DocScrutinizer05> oops echan
Apr 01 18:15:20 <kerio> Last Measured Discharge (LMD): 1122.765 mAh
Apr 01 18:15:25 <kerio> let's see what i get after this calibration cycle
Apr 01 18:23:06 <Sicelo> sixwheeledbeast: got my pyobd semi-working by commenting out the ATE0 part of initialization. Not working so well yet though, but i can see a couple of sensors
Apr 01 18:23:27 <Sicelo> still can't minicom though. wish i knew what i'm doing wrong
Apr 01 18:26:10 <DocScrutinizer05> minicom is a bitch
Apr 01 18:28:46 <Sicelo> i've used it on N900 to go into a cisco router some years ago. i do think there's something i'm not doing right, but can't figure out why. pyobd uses 9600,8N1 the same as how i connect with minicom
Apr 01 18:29:46 <kerio> DocScrutinizer05: charger plugged in but disabled causes like 50mA of current more
Apr 01 18:30:32 <kerio> is that normal
Apr 01 18:30:46 <DocScrutinizer05> err yes
Apr 01 18:30:59 <kerio> but where are the electrons going :<
Apr 01 18:31:00 <DocScrutinizer05> that's the friggin MUSB core and its busses
Apr 01 18:31:19 <DocScrutinizer05> aka activated USB
Apr 01 18:31:58 <DocScrutinizer05> I think there's a 'trick' to send MUSB to suspend again by "echo off >sys/dunnowhat"
Apr 01 18:32:42 <DocScrutinizer05> maybe even modprobe -r though I think USB is monolithic
Apr 01 18:34:28 <DocScrutinizer05> I think Pali knows more than me here
Apr 01 18:35:32 <kerio> nah it's fine it's just weird
Apr 01 18:35:39 <Pali> what me? :-)
Apr 01 18:35:46 <DocScrutinizer05> or check pali's hostmode, it tries to shut dowm musb core after hostmode disabled
Apr 01 18:35:53 <DocScrutinizer05> iirc
Apr 01 18:36:07 <kerio> DocScrutinizer05: what kind of measured discharge am i looking at, at a constant 230mA draw?
Apr 01 18:36:24 <DocScrutinizer05> sorry please rephrase
Apr 01 18:36:26 <kerio> is ~1200mAh at 230mA good?
Apr 01 18:36:31 <DocScrutinizer05> yes
Apr 01 18:36:34 <kerio> :3
Apr 01 18:36:58 <kerio> why does my akku polarcell say "lithium polymer" on the label
Apr 01 18:37:05 <DocScrutinizer05> blabla
Apr 01 18:37:43 <DocScrutinizer05> I recently learnd they call cells LiPo now when the case is made of plastic ;-P
Apr 01 18:38:10 <DocScrutinizer05> or similar nonsense
Apr 01 18:38:44 <DocScrutinizer05> once LiPo was a cell chemistry variant
Apr 01 18:40:09 <DocScrutinizer05> >>The designation "lithium polymer" has caused confusion among battery users because it can be interpreted in two ways. Originally, "lithium polymer" represented a developing technology using a polymer electrolyte instead of the more common liquid electrolyte<<
Apr 01 18:40:16 <DocScrutinizer05> https://en.wikipedia.org/wiki/Lithium_polymer_battery
Apr 01 18:40:28 <kerio> ye that's what i was thinking of
Apr 01 18:43:19 <DocScrutinizer05> Pali: ((what me? :-)  )) How to disable MUSB core after e.g. hostmode?
Apr 01 18:43:32 <Pali> what is musb core?
Apr 01 18:43:41 <Pali> or what do you mean by "disable",
Apr 01 18:43:42 <Pali> ?
Apr 01 18:43:53 <DocScrutinizer05> the mentorgraphics shit state machine that controls the USB states
Apr 01 18:44:08 <DocScrutinizer05> it has a bus to CPU and a bus to PJY
Apr 01 18:44:13 <DocScrutinizer05> PHY even
Apr 01 18:44:26 <Pali> rmmod all gadgets
Apr 01 18:44:28 <kerio> can't we do that with the real cpu
Apr 01 18:44:30 <DocScrutinizer05> and all three (core and the 2 buses) eats 50mA
Apr 01 18:44:35 <Pali> that could do all tricks :-)
Apr 01 18:44:55 <Pali> and modprobe g_nokia back
Apr 01 18:45:13 <DocScrutinizer05> aaah so it loads g_nokia or whatever whenever there's 5V on VBUS?
Apr 01 18:45:53 <kerio> i think that he means to unload them all
Apr 01 18:46:00 <kerio> so there's nothing doing the detection
Apr 01 18:46:01 <kerio> or something
Apr 01 18:46:05 <DocScrutinizer05> I thought there was a magic handle in /sys/bla/bla/*/power or sth
Apr 01 18:46:28 <DocScrutinizer05> kerio: yes, that's what I got
Apr 01 18:48:07 <DocScrutinizer05> Pali: do you recall the issue that device ate 50mA more after using hostmode, even when it been completely disabled? I think you found a cure for that
Apr 01 18:48:51 <Pali> now I do not remember
Apr 01 18:48:57 <Pali> maybe it was some softconnect
Apr 01 18:49:00 <Pali> or vbus
Apr 01 18:49:04 <Pali> or another sysfs entry
Apr 01 18:49:37 <Pali> anyway, unloading and loading g_nokia fixing some problem with musb internal state
Apr 01 18:49:57 <Pali> sometimes after turning host mode off, musb is in wrong state
Apr 01 18:50:05 <Pali> and kernel write error messages to dmesg
Apr 01 18:50:20 <Pali> reloading gadget fixes it
Apr 01 18:55:17 <DocScrutinizer05> aah ok
Apr 01 18:56:03 <DocScrutinizer05> thanks
Apr 01 18:58:58 <kerio> this is just for vboost/host mode right
Apr 01 18:59:03 <kerio> not for just simply disabling and reenabling the charget
Apr 01 18:59:05 <kerio> charger
Apr 01 19:04:02 <DocScrutinizer05> it's not the disabling/re-enabling of BME that does this, it's the 5V on VBUS I think
Apr 01 19:04:56 <DocScrutinizer05> 5V on VBUS means either a charger or a PC host got connected, so to distinguish the two you need MUSB core
Apr 01 19:05:39 <DocScrutinizer05> particularly you need MUSB core to do ENUM on a possibly connected host
Apr 01 19:06:35 <DocScrutinizer05> actually the system *could* stop MUSB after detecting the D+/- short, but I dunno who detects it and if that system takes care about shutting down USB data
Apr 01 19:06:54 <DocScrutinizer05> most likely not when BME got stopped
Apr 01 19:11:28 <Sicelo> Pali: with usb-mode, how would i enumerate additional devices i connect? or i have to use the /proc/something method?
Apr 01 19:12:05 <Pali> additonal devices? nokia n900 has just one usb port, so you cannot connect more usb devices
Apr 01 19:12:11 <Sicelo> and, did you find any further solutions for the stuck blue LED after deactivation of host mode?
Apr 01 19:12:40 <Sicelo> if i connect a hub for example, then i need to enumerate the additional USB devices
Apr 01 19:12:44 <Pali> blue led, no idea :-( I was not able to reproduce it on my n900
Apr 01 19:13:02 <Pali> "if i connect a hub...", so you do not connect additinal device :-)
Apr 01 19:13:08 <Pali> it is up to hub and hub driver
Apr 01 19:13:45 <Pali> it do enumeration without any other other "hacks" in musb
Apr 01 19:13:48 <Pali> so automatically
Apr 01 19:14:01 <Pali> if not, then hub is buggy and you cannot do anything
Apr 01 19:14:07 <Sicelo> okay. thanks. will test. i was just wondering.
Apr 01 19:14:51 <Sicelo> in h-e-n there was an enumerate button, which i think sends an echo F to some location in /proc
Apr 01 19:17:49 <DocScrutinizer05> with a hub you don't need that since the data link to the hub is already installed
Apr 01 19:18:10 <DocScrutinizer05> I meant, you only need it when connecting the hub
Apr 01 19:18:31 <Sicelo> i see. thanks for information
Apr 01 22:14:18 <DocScrutinizer05> Sicelo: stuck blue LED?
Apr 01 22:21:39 <DocScrutinizer05> Pali: how does your hostmode control the LED? via MCE dbus call for pattern?
Apr 01 22:21:50 <Pali> mce dbus
Apr 01 22:21:58 <DocScrutinizer05> best practice
Apr 01 22:22:08 <DocScrutinizer05> :)
Apr 01 22:22:38 <Pali> but when using bme replacement, then my usbmode does not touch led
Apr 01 22:22:54 <Pali> bme replacement care of mce led dbus pattern
Apr 01 22:22:54 <DocScrutinizer05> does it wait until method call sends ack reply via dbus before process terminates?
Apr 01 22:23:25 <Pali> yes, it must
Apr 01 22:23:38 <Pali> this is how dbus method call works
Apr 01 22:23:38 <DocScrutinizer05> then I don't see how LED could possibly get stuck
Apr 01 22:23:54 <Pali> I think there is some bug in mce
Apr 01 22:24:00 <Pali> or race condition...
Apr 01 22:24:00 <DocScrutinizer05> possible
Apr 01 22:24:13 <Pali> do not know what happen if you request led two times
Apr 01 22:24:25 <Pali> if you need then to disable it two times too or not
Apr 01 22:24:50 <DocScrutinizer05> I think mce has a one element deep "stack" to resume previous state when a pattern gets discontinued
Apr 01 22:25:21 <DocScrutinizer05> not sure if it's deeper than just one element
Apr 01 22:26:31 <Pali> if Sicelo can reproduce that bug, probably he needs to debug it too...
Apr 01 22:28:05 <DocScrutinizer05> a dmus-monitor >tracelog.txt should do
Apr 01 22:28:21 <DocScrutinizer05> dbus even#
Apr 01 22:30:26 <Sicelo> i would have loved to. but all 3 batteries are bad now. device switches of within 2 minutes of hostmode.
Apr 01 22:33:40 <DocScrutinizer05> eeew
Apr 01 22:34:14 <DocScrutinizer05> batteries are rare and extremely expensive at your site, no?
Apr 01 22:35:02 <DocScrutinizer05> can'
Apr 01 22:35:09 <Sicelo> good ones, yes. fake ones that last a month are in abundance :)
Apr 01 22:35:18 <DocScrutinizer05> t you get a used one which is still in good condition?
Apr 01 22:36:12 <DocScrutinizer05> also it's hot where you live?
Apr 01 22:37:41 <Sicelo> not so hot, i'd say. interestingly the batteries last at least 8 hours continuous use per day, but die immediately on hostmode (high internal resistance, i assume)
Apr 01 22:38:43 <DocScrutinizer05> yes
Apr 01 22:38:50 <DocScrutinizer05> seems so
Apr 01 22:39:33 <DocScrutinizer05> could you run a bq27200.sh 10 >batlog.txt   in parallel?
Apr 01 22:40:04 <DocScrutinizer05> with at least 15 minutes history before activating hostmode
Apr 01 22:40:36 <DocScrutinizer05> dunno if bq27200.sh works for your system
Apr 01 22:40:53 <DocScrutinizer05> (I.E. for the hostmode BME
Apr 01 22:40:55 <DocScrutinizer05> )
Apr 01 22:48:00 <Sicelo> i modified it to work. 
Apr 01 22:50:50 <DocScrutinizer05> good
Apr 01 22:51:57 <DocScrutinizer05> I'm really interested how a batlog of a supposedly worn battery would look like, when said battery works even with backlight but fails during 2 minutes on hostmode
Apr 01 23:32:33 <kerio> Last Measured Discharge (LMD): 1212.9075 mAh
Apr 01 23:32:45 <kerio> 1122 to 1212
Apr 01 23:33:08 <kerio> how much was the maximum increase?
Apr 01 23:39:08 <liuhoujiang> k
Apr 01 23:48:10 <DocScrutinizer05> kerio: iirc 1/8
Apr 01 23:48:21 <kerio> 1/8 of what
Apr 01 23:48:26 <DocScrutinizer05> of the value
Apr 01 23:49:13 <DocScrutinizer05> ~1212/1122
Apr 01 23:49:13 <infobot> 1.080213903743
Apr 01 23:49:22 <kerio> ~1122*9/8
Apr 01 23:49:23 <infobot> 1262.25
Apr 01 23:49:23 <DocScrutinizer05> <1.125
Apr 01 23:49:44 <kerio> ok i'm gonna call this value the true one
Apr 01 23:49:52 <kerio> so this is 1200mAh under heavy draw
Apr 01 23:50:00 <DocScrutinizer05> yup
Apr 01 23:50:19 <DocScrutinizer05> pretty decent
Apr 01 23:51:01 <kerio> how do i measure the capacity under zero load
Apr 01 23:52:06 <DocScrutinizer05> discharge for a minute, no load for a minute, probe voltage
Apr 01 23:52:38 <kerio> also can't we measure the mWh instead
Apr 01 23:52:40 <DocScrutinizer05> repeat, until voltage < EVDF
Apr 01 23:52:57 <DocScrutinizer05> bq27200 already does that
Apr 01 23:53:04 <DocScrutinizer05> (mWh)
Apr 01 23:55:13 <DocScrutinizer05>  SAE Available Energy
Apr 01 23:55:19 <DocScrutinizer05> http://paste.opensuse.org/53587960
**** ENDING LOGGING AT Sat Apr 02 02:59:58 2016