| Wizzup | buZz: this is entirely normal @ cores | 00:45 |
|---|---|---|
| buZz | :) ok | 00:48 |
| freemangordon | uvos: I don't know how did you measure android idle current, but here I see ~90 mA min | 08:30 |
| freemangordon | it jumps to 10 for a split second, but then again jumps to at least 100 | 08:30 |
| freemangordon | this is without sim card and not connected to wifi | 08:31 |
| uvos | freemangordon: thats los | 09:36 |
| uvos | its spends little time in off mode | 09:36 |
| uvos | becuase its very busy for some reason | 09:37 |
| uvos | you need to mesure motorola android | 09:37 |
| uvos | btw leste encounters a bug where the modem power consuption is 40mA or so higher when no sim is insertet | 09:53 |
| uvos | idk if android suffers from the same bug | 09:53 |
| uvos | but i mesured with sim in flightmode | 09:54 |
| uvos | for 15-20mA | 09:54 |
| freemangordon | this is motorolla droid, iiuc | 10:36 |
| freemangordon | 4.somthing | 10:36 |
| freemangordon | but ok, will measure again with sim | 10:36 |
| freemangordon | oh, there was sim card in that device | 10:39 |
| freemangordon | Wizzup: ^^^ | 10:39 |
| freemangordon | is that yours? | 10:39 |
| freemangordon | verizon :) | 10:40 |
| Wizzup | freemangordon: yeah that happened sometimes, but not mine | 10:40 |
| freemangordon | I will keep it for some tests | 10:41 |
| Wizzup | sure | 10:41 |
| Wizzup | btw, is bringing up status applet also relatively slow for some? sometimes it's fast, sometimes it's a bit slow | 10:42 |
| freemangordon | leste idles @ 30mA | 10:45 |
| Wizzup | it can be less, usually between 16-32 on my psu at home | 10:46 |
| Wizzup | but this was probably without modem online | 10:46 |
| freemangordon | uvos: with the fix, current draw after power-off is the same as after android power-off | 10:46 |
| Wizzup | (been a while) | 10:46 |
| Wizzup | freemangordon: oh 30mA when off? | 10:47 |
| freemangordon | Wizzup: this is with modem online and connected to wireless | 10:47 |
| Wizzup | ah | 10:47 |
| freemangordon | no, when off it is 1mA | 10:47 |
| Wizzup | ok | 10:47 |
| freemangordon | without shutdown fix, power usage is the same to the precision my dmm has | 10:58 |
| freemangordon | maybe more on th 2mA side than on 1mA | 10:58 |
| freemangordon | uvos: what kernel you did your measurements with? | 10:58 |
| freemangordon | Wizzup: uvos: http://46.249.74.23/leste/d4/power_usage/ | 11:03 |
| freemangordon | seems the patch is needed to strip some .5mA further down | 11:03 |
| freemangordon | but we are already ok even without it | 11:04 |
| Wizzup | til firefox loads bmp | 11:04 |
| Wizzup | leste-fix is empty for me | 11:04 |
| freemangordon | hmm? | 11:04 |
| freemangordon | oh, I don;t know why | 11:04 |
| freemangordon | lemme see | 11:04 |
| freemangordon | well, chinese dmm software broke it somehow | 11:05 |
| freemangordon | bu, just open .csv | 11:05 |
| freemangordon | anyway bmp precosion is not good | 11:05 |
| freemangordon | *precision | 11:05 |
| Wizzup | right | 11:10 |
| freemangordon | Wizzup: http://46.249.74.23/leste/d4/power_usage/leste-fix.ods | 11:10 |
| freemangordon | do you want me to measure something else? | 11:12 |
| Wizzup | not sure, I don't think so, but I didn't give it a lot of thought | 11:16 |
| freemangordon | Later on I will try to find some 0.1 Ohm resistor to try to improve the precision in idle | 11:16 |
| freemangordon | like, if there is any difference in voltage android vs leste-fix vs leste-nofix | 11:17 |
| freemangordon | umm, in off, not in idle | 11:22 |
| uvos__ | freemangordon: i used a dmm, but one with very low burden voltage | 13:18 |
| uvos__ | if motorola android uses 100mA somthing is very wrong there | 13:20 |
| uvos__ | on your install | 13:20 |
| uvos__ | aside from mine and tmlinds mesurements | 13:22 |
| uvos__ | motorola android can also idle for over 1w expieramentally | 13:23 |
| freemangordon | uvos__: well, I have no idea what install is that, it is waht was there on the device | 16:52 |
| freemangordon | without SIM card and withou uSD card now it idles @ 8 | 16:59 |
| freemangordon | 8mA that is | 16:59 |
| freemangordon | ok, after power-off from android, current draw is 1.57 mA | 17:02 |
| freemangordon | hmm, now, with SIM card and uSD, it is 1.80 mA, but decreases | 17:06 |
| freemangordon | weird | 17:07 |
| freemangordon | uvos__: anyway, the shutdown fix seems to not be unneeded, bot with and without it off draw is the same, for some reason it is 2.0 mA right after power-off, but decreases with time, exponentially, to ~1.60 mA | 17:28 |
| freemangordon | the same happens with android | 17:29 |
| freemangordon | so, whatever was causing high off current is already fixed | 17:32 |
| uvos | hmm thats.. wierd | 17:46 |
| uvos | i was mesureing <1mA with android | 17:46 |
| freemangordon | well, lemme explain my methodology, maybe I am doing something wrong | 17:47 |
| freemangordon | I have 47 Ohm resistor connected in series with the battery, which I short-circuit during boot with DMM on 4A range | 17:48 |
| freemangordon | I short-circuit the resistor ofc, not the battery :) | 17:48 |
| freemangordon | after boot, I power-off | 17:48 |
| freemangordon | after power-off is completed, I switch DMM to 200 mA range, it is still in parallel to the resistor | 17:49 |
| freemangordon | resistor is there to keep the current while I change the terminals on DMM (I have separate holes for 10A and 200mA) | 17:50 |
| freemangordon | anything obviously wrong? | 17:50 |
| freemangordon | (it has separate holes) | 17:50 |
| uvos | well the resisor is pulling some current that bypasses the dmm, but that should make the mesurement low not high | 17:51 |
| freemangordon | during the switch, voltage drop because of the resistor is < 100mV, should not affect the state | 17:52 |
| uvos | no i mean durring the mesurement some current flows through the dmm and some though the resistor | 17:52 |
| freemangordon | sure, but 47Ohm should make some .01 diff | 17:52 |
| uvos | makeing the dmm read low | 17:52 |
| freemangordon | yes, I know | 17:52 |
| uvos | it probubly makes more sense to mesure the voltage drop on the resistor | 17:52 |
| uvos | but dosent explain the high mesurement | 17:53 |
| uvos | what do you mesure before the device is ever booted | 17:53 |
| freemangordon | well, my goal was to check leste vs android | 17:53 |
| freemangordon | 1.57 mA | 17:53 |
| uvos | ok and yeah any inaccuracies shouldend matter anyhow as long as android and leste are the same | 17:53 |
| freemangordon | mhm | 17:54 |
| uvos | so yes i gues it was fixed sometime between 5.10 and now | 17:54 |
| freemangordon | also, keep in mind the exponential decrease of the off current | 17:54 |
| uvos | but ill repeat the expierament when i have time | 17:54 |
| freemangordon | please do | 17:54 |
| uvos | 8mA sounds sane fore android idle btw | 17:55 |
| freemangordon | but I am pretty sure my DMM is pretty much accurate | 17:55 |
| uvos | so thats a fine mesurement now | 17:55 |
| freemangordon | yeah, maybe verizon SIM that was there was doing some crazy things | 17:55 |
| uvos | possibly the modem dosent sleep but keeps searching for a network or something | 17:55 |
| uvos | but yeah | 17:56 |
| freemangordon | so, I see no flaw in my methodology, do you? | 17:58 |
| uvos | no | 17:58 |
| uvos | i gues it was fixed sometime between 5.10 and now | 17:58 |
| freemangordon | mhm | 17:58 |
| uvos | or only affects the other cpcap mfd | 17:59 |
| freemangordon | please measure d3 (or whatever device you said has issues as well) when you have time | 17:59 |
| uvos | bionic | 17:59 |
| freemangordon | yeah | 17:59 |
| uvos | bionic is pretty insane | 17:59 |
| uvos | its empty in 2 days usualy even when turned off full | 18:00 |
| freemangordon | from android? | 18:00 |
| uvos | from leste | 18:00 |
| uvos | cant turn it off from android anymore | 18:00 |
| freemangordon | even with latest kernel? | 18:00 |
| uvos | since installing the bootloader breaks android on this device | 18:00 |
| uvos | weill last time i used it | 18:00 |
| uvos | (also a 5.18 kernel( | 18:00 |
| uvos | but not the latest | 18:00 |
| freemangordon | well, I meant 5.18 | 18:01 |
| uvos | right | 18:01 |
| freemangordon | ok, maybe try the shutdown patch kernel | 18:01 |
| freemangordon | uvos: http://46.249.74.23/leste/d4/modem_patch/ | 18:01 |
| uvos | yeah i know (this patch) | 18:01 |
| uvos | oh kernel image | 18:02 |
| freemangordon | just providing the link again, in case you've missed it | 18:02 |
| freemangordon | yeah, this is compiled so you can just use it as is | 18:02 |
| freemangordon | this is 5.18.y-cpcap + shutdown fix | 18:02 |
| uvos | ok can you link the patch again | 18:02 |
| freemangordon | with broken cpcap-battery though | 18:02 |
| uvos | id rather compile it myself | 18:03 |
| freemangordon | umm, lemme see if I can find it | 18:03 |
| freemangordon | as I just did git stash drop :D | 18:03 |
| freemangordon | uvos: https://pastebin.com/7jtJFtGR | 18:04 |
| uvos | thanks, saved | 18:04 |
| freemangordon | uvos: BTW, I think if we have working charger detection, we don;t need charge mode | 18:06 |
| freemangordon | agree? | 18:06 |
| freemangordon | esp if we do cpcap stuff build-in | 18:07 |
| uvos | well not need from the perpective of the device beein unbootable | 18:09 |
| uvos | but i would still like the option to charge while off | 18:09 |
| freemangordon | oh, sure | 18:10 |
| uvos | but yes the mapphones wont have any specific need anymore | 18:10 |
| freemangordon | mhm | 18:10 |
| freemangordon | do you know what driver is that cpcap-uc or whatever? | 18:10 |
| uvos | ./drivers/mfd/cpcap-uc.c | 18:12 |
| uvos | if you mean the bits that upload the fw and so on | 18:12 |
| freemangordon | well, I don't know what I mean | 18:13 |
| freemangordon | like, I am trying to find where to start from | 18:13 |
| uvos | cpcap-uc is just a microcontoller on cp where android uploads fw | 18:13 |
| uvos | that fw then dose several things | 18:13 |
| uvos | theres a enum with "macros" that the kernel calls on the fw | 18:14 |
| uvos | to have cpcap perform certain tasks | 18:14 |
| uvos | sec if i can find it | 18:14 |
| freemangordon | oh, so those are these MACRO_IRQ in cpcap-battery (in vendor kernel) | 18:15 |
| uvos | right | 18:17 |
| uvos | so cpcap-battery.c for instance mostly lets the uc do everything | 18:19 |
| freemangordon | I see cpcap-usb-det.c | 18:19 |
| uvos | looks like the kernel dose most of it here | 18:21 |
| uvos | yeah dosent look like you have to use the fw, despite there being a macro that detects usb, at least going by the name | 18:25 |
| uvos | get_sense() and detection_work() seam to do it | 18:25 |
| freemangordon | do you know what WHISPER is? | 18:28 |
| uvos | no | 18:30 |
| uvos | probubly some code name of a different chip involved in charging | 18:31 |
| uvos | (maybe the inductive charging ic?) | 18:31 |
| freemangordon | or some docking station? | 18:32 |
| uvos | possible | 18:32 |
| freemangordon | does d4 support inductive charging? | 18:32 |
| uvos | maybe something in the lapdock | 18:32 |
| uvos | freemangordon: optinally | 18:32 |
| Wizzup | I think the pins in the back can be used ofr it | 18:32 |
| uvos | freemangordon: the pogo pins beneth the battery door are for this | 18:32 |
| freemangordon | ok | 18:32 |
| Wizzup | uvos: super unrelated but is this also a mapphone? https://www.gsmarena.com/motorola_droid_x-3473.php | 18:33 |
| uvos | no | 18:33 |
| uvos | sholes | 18:33 |
| Wizzup | ok | 18:33 |
| uvos | its the same as the d2 | 18:33 |
| Wizzup | ah, I kind of assumed the d2 was a mapphone | 18:35 |
| Wizzup | should have checked the spreadsheet I guess :D | 18:35 |
| uvos | d2 is just a d1 with a locked bootloader | 18:36 |
| uvos | and more ram | 18:36 |
| uvos | and a more plasticy case | 18:36 |
| Wizzup | mhm | 18:38 |
| Wizzup | well, the xt610 was also a sholes, right? | 18:38 |
| uvos | yes | 18:39 |
| uvos | the lte modem is also sholes xD | 18:39 |
| uvos | at least it uses the sholes kernel | 18:39 |
| Wizzup | uvos: hmm interesting | 18:45 |
| Wizzup | uvos: the d4 lte modem? | 18:45 |
| uvos | yes - but calling it sholes is overstateing it a bit, they used the sholes android source tree to start and it uses the same pmic but otherwise its quite different (as you might imagine - it being a modem and all) | 18:46 |
| uvos | also they bolted on the cpcap stuff | 18:47 |
| uvos | that sholes dosent have | 18:47 |
| uvos | thats also pretty siginificant | 18:47 |
| Wizzup | mhm | 18:47 |
| freemangordon | ok, seems charger detection is some "switch" stuff | 18:51 |
| uvos | right | 18:51 |
| uvos | massive statemachine | 18:51 |
| uvos | well "massive" | 18:51 |
| freemangordon | /sys/class/switch/charge_capability/state | 18:51 |
| uvos | oh that kind of switch | 18:51 |
| uvos | also right | 18:51 |
| freemangordon | lives in cpcap-usb-det.c | 18:52 |
| uvos | looks like yes | 18:53 |
| uvos | get_sense() and detection_work() | 18:53 |
| uvos | and friends | 18:53 |
| freemangordon | unfortunately charger_capacity seems to come from userspace | 18:53 |
| freemangordon | see cpcap_accy_charger | 18:54 |
| freemangordon | CPCAP_IOCTL_ACCY_CHARGER | 18:54 |
| uvos | i think tmlind or sre? had a way io intercept the stuff userpace reads form the cpcap userspace interface | 18:54 |
| uvos | presumably if its done in userspace userspace is using this file/interface | 18:54 |
| freemangordon | battd I guess | 18:55 |
| freemangordon | or no? | 18:55 |
| uvos | i dont know | 18:55 |
| freemangordon | ok | 18:55 |
| uvos | so theres a file you can use on android to do almost anything with cpcap from userspace | 18:56 |
| freemangordon | ok, but I want to know who calls CPCAP_IOCTL_ACCY_CHARGER :) | 18:56 |
| freemangordon | because that's how charger capacity is set | 18:57 |
| uvos | well its called with this fd | 18:57 |
| freemangordon | sure | 18:57 |
| uvos | so check what has it open | 18:57 |
| freemangordon | yeah | 18:57 |
| freemangordon | I'll check batd first | 18:57 |
| freemangordon | uvos: is it possible that they ramp up the charging current until limit? | 19:57 |
| uvos | we ramp up the current to avoid lead inductance triggering, they probubly do too | 19:58 |
| uvos | ramping to limit would be grossly negligent | 19:58 |
| freemangordon | right | 19:58 |
| uvos | you have to tell the usb port your a high power device, unless you get the data lines tied symbol to get more than 500uA legaly per spec | 19:58 |
| * freemangordon searches for documentation on how fast-charger should be detected | 19:58 | |
| uvos | (yes thats uA not mA) | 19:59 |
| sicelo | Wizzup: https://lists.dyne.org/lurker/message/20221109.203328.c5b5a322.en.html | 22:51 |
| * norayr trying to calibrate the battery under droid3. | 23:06 | |
| norayr | under android. | 23:06 |
| norayr | for 3 days, i cannot get it to 0. it's about 80% now. | 23:06 |
| norayr | android on droids probably has very good power management. | 23:07 |
| sicelo | naturally. nearly all devices (including laptops) have better power management when running their 'native' OS | 23:20 |
| Wizzup | I think it's just OFF mode here | 23:48 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!