| Guest92 | Latest release? | 04:04 |
|---|---|---|
| Wizzup | Guest92 -- I'm almost back in europe (literally, in air atm), and then I'll get on it. | 06:46 |
| Wizzup | I also have a call re: leste and the new blog post on friday | 06:46 |
| freemangordon | norayr: and for how much longer do you expect your already bad battery to last? | 07:09 |
| freemangordon | also, there is no argument that there should be enough charge before shutdown | 07:09 |
| freemangordon | the discussion is about no warning given before shutdown | 07:11 |
| freemangordon | I guess that was the reason your battery went so flat that you had to charge it externally | 07:11 |
| Wizzup | either that, or the device uses power after power off | 07:12 |
| freemangordon | it uses, but uvos said 1-2 mA | 07:12 |
| freemangordon | which for 24 gours is less that 50 mAh | 07:13 |
| freemangordon | *hours | 07:13 |
| freemangordon | hmm, do we power-down the modem on shutdown? | 07:14 |
| Wizzup | still, that could be enough | 07:14 |
| Wizzup | I think the kernel does | 07:15 |
| freemangordon | does it? | 07:15 |
| Wizzup | unloading the module afaik powers it down | 07:15 |
| freemangordon | this is different | 07:15 |
| Wizzup | worth checking | 07:15 |
| freemangordon | lemme check | 07:15 |
| freemangordon | nope | 07:16 |
| Wizzup | it powers up the modem though I think | 07:17 |
| freemangordon | yes | 07:17 |
| freemangordon | and leaves it powered on :) | 07:17 |
| Wizzup | hm | 07:18 |
| freemangordon | do you have d4 with psu connected so we can test? | 07:18 |
| Wizzup | well, yes, but I'm still in-air | 07:18 |
| freemangordon | well, ok | 07:18 |
| freemangordon | when you are on the ground obviously :) | 07:18 |
| Wizzup | I'll try to remember, have a bunch to do | 07:18 |
| Wizzup | I think my d4 currently on a lab psu at home has an idle draw of 0.16A even when powered off and never powered on | 07:19 |
| freemangordon | I guess uvos has psu/d4 as well | 07:19 |
| Wizzup | probably something burned (it still works) | 07:19 |
| freemangordon | 160mA?!? | 07:19 |
| Wizzup | so I should swap that out | 07:19 |
| Wizzup | uh sorry 1 | 07:19 |
| Wizzup | 16 | 07:19 |
| freemangordon | ah | 07:19 |
| freemangordon | if you power down from android, does it still draw the same current? | 07:19 |
| Wizzup | if I take away all the power and turn the psu off, and then the psu back on, it still draws it, yes | 07:20 |
| Wizzup | this is unrelated | 07:20 |
| Wizzup | mostly just saying that I need to swap the device first | 07:20 |
| Wizzup | (for our test) | 07:20 |
| freemangordon | ah | 07:20 |
| freemangordon | yeah | 07:20 |
| freemangordon | tmlind: don;t we need .shutdown callback in phy_mdm6600_driver structure, to power-off the modem on shutdown? | 07:23 |
| freemangordon | otherwise it will be left in reset (I guess) | 07:23 |
| freemangordon | tmlind: this? https://pastebin.com/7jtJFtGR | 07:37 |
| tmlind | hmm yeah maybe, worth measuring if there is s difference in power consumption after shutdown | 07:52 |
| freemangordon | do you have d4 with lab psu? | 07:59 |
| tmlind | yeah i have one wired with an ina226 i2c shunt, afaik power consumption is already very low after poweroff but yet lower after android poweroff. the difference might be missing shtudown functions for cpcap audio or modem etc like you're suggesting | 08:26 |
| tmlind | will measure with your patch at some point when i get a chance | 08:27 |
| tmlind | for runtime measurements, polling the charge counter about once a minute follows the ina226 numbers reasonably close | 08:28 |
| uvos__ | i no longer have a d4 on psu | 09:49 |
| uvos__ | since my main device broke | 09:49 |
| uvos__ | so now i use this one | 09:49 |
| uvos__ | the difference between android and mainline shutdown is mutch greater on bionic btw | 09:53 |
| uvos__ | it uses like 7-8mA | 09:53 |
| uvos__ | and was even more recently | 09:54 |
| uvos__ | there was an issue where the button backlights wherent turned off proparly, the upstream regulator was disabled | 09:54 |
| uvos__ | but the leds where not in cpcap | 09:54 |
| uvos__ | the upstream regulator leaked some power even when disabled | 09:54 |
| uvos__ | you could even see the leds glow slightly while the device was off | 09:55 |
| uvos__ | this is fixed | 09:55 |
| uvos__ | by disableing the leds in cpcap on shutdown, but just sayiing its been cpcap before ;) | 09:55 |
| freemangordon | ok, lets wait for Wizzup to land, I guess he will measure the draw with and without the patch, unless tmlind is faster | 09:57 |
| uvos__ | btw when considering shutdown voltage | 09:58 |
| uvos__ | also consider the bionic, since it takes even loger to boot | 09:58 |
| uvos__ | it has to boot android then mainline and then mainline again | 09:58 |
| uvos__ | same for d3 | 09:59 |
| uvos__ | but we could fix that in kexecboot i gues | 09:59 |
| freemangordon | I understand that, but I think we shall not try to support batteries that has 500 mAh capacity left | 09:59 |
| freemangordon | or at least we shall give priority to good batteries over bad | 09:59 |
| uvos__ | (ie add something that causes kexecboot to pause if its running on mainline) | 10:00 |
| uvos__ | and the battery is low | 10:00 |
| uvos__ | another option is also to add charging support to kexecboot, even when running on the android kernel | 10:00 |
| uvos__ | and also haveing it pause if the battery is low | 10:01 |
| uvos__ | maybe tmlind knows how the cpcap interface on the android kernel works | 10:01 |
| freemangordon | also, I think a simple lowering the mce shutdown voltage from 3350 to 3250 or similar will have great effect on UX while in leste | 10:01 |
| uvos__ | i gues maybe you do to since you re'd the blob that uses it to do charging | 10:01 |
| uvos__ | this is insufficant | 10:01 |
| uvos__ | i tested this alot | 10:02 |
| freemangordon | well, 3300 then | 10:02 |
| freemangordon | or 3299 | 10:02 |
| uvos__ | the voltage is so noisy i doubt this makes a real difference | 10:02 |
| freemangordon | it will make all the difference on good battery | 10:03 |
| uvos__ | i think you massively overestimate how mutch charge remains at so low voltages | 10:03 |
| uvos__ | the discarge curve is realy steep here | 10:03 |
| freemangordon | sure, but we need 50 mAh | 10:03 |
| freemangordon | and I bed we have that @ 3.3 | 10:04 |
| freemangordon | *bet | 10:04 |
| freemangordon | even for bad batteries | 10:04 |
| freemangordon | also, what we can do for d4 is to disable cpu1 on boot as soon as we have a chance | 10:05 |
| uvos__ | im more refearing to that 50mV extra will make a difference | 10:05 |
| freemangordon | sure | 10:05 |
| freemangordon | but we can workaround that by disabling cpu1 | 10:05 |
| uvos__ | the discarge curve is too steep and the mesurement uncertanty is to high imo | 10:05 |
| freemangordon | but it still depends on the load | 10:06 |
| freemangordon | well... | 10:06 |
| freemangordon | we can at least try to | 10:06 |
| freemangordon | the other option is those with good batteries to have no low warnings | 10:06 |
| freemangordon | and I don;t think that's acceptable | 10:06 |
| uvos__ | and we discused how to solve that | 10:07 |
| uvos__ | its an independen problem from when shutdown happens exatcly | 10:07 |
| freemangordon | but this is a massive work compared to what I propose | 10:07 |
| freemangordon | also, how is upower going to produce low signals? polling? | 10:07 |
| uvos__ | it polls allready | 10:08 |
| uvos__ | how do you think mce gets the voltage | 10:08 |
| freemangordon | on kernel event | 10:08 |
| uvos__ | no upower polls the battery | 10:09 |
| freemangordon | and by polling, I mean - timer based polling | 10:09 |
| uvos__ | im very sure it polls the battery the kernel creates no events for changeing voltage | 10:09 |
| freemangordon | ah, it polls tha battery and when it sees low it generates dbus signal? | 10:09 |
| uvos__ | and upower recodes it even | 10:09 |
| freemangordon | I am not si sure | 10:09 |
| freemangordon | *so | 10:09 |
| uvos__ | mce just reacts to upowers signals | 10:09 |
| uvos__ | they come in regular intervals | 10:09 |
| freemangordon | "/sys" supports inotufy | 10:10 |
| freemangordon | *inotify | 10:10 |
| uvos__ | anyhow its imaterial if upower polls or gets a signal form the kernel at regular intervals, the point is upower gets voltage at regular intervals | 10:10 |
| freemangordon | also, if we do that, we risk calibration to never finish | 10:10 |
| uvos__ | and could absolutly act on it | 10:10 |
| freemangordon | because it needs low irq, IIUC | 10:11 |
| uvos__ | freemangordon: yes this is antoher problem | 10:11 |
| uvos__ | it works ok rn tho | 10:11 |
| freemangordon | sure | 10:11 |
| freemangordon | that's why I prefer to keep it | 10:11 |
| uvos__ | but yes if you set the tresh very high | 10:11 |
| freemangordon | and just reduce shutdown voltage by a bit | 10:12 |
| freemangordon | combined with idle fix(hopefully) and disabling cpu1 shall be ok | 10:12 |
| freemangordon | also, I will start working to bring charger detection at some point | 10:14 |
| freemangordon | and then we'll be more or less fine, no matter the charge | 10:15 |
| uvos__ | iirc on android this works via cpcap-uc | 10:15 |
| uvos__ | detection | 10:15 |
| freemangordon | well, 'almost' | 10:15 |
| freemangordon | ok | 10:15 |
| freemangordon | so, really, lets at least try what I propose. we can always revert it | 10:16 |
| freemangordon | assuming poweroff fix works | 10:16 |
| * freemangordon checks what cpcap-uc is | 10:17 | |
| uvos__ | i came up with the current value by doing testing, chainging it just because you think is ok (and we use very good batteries so ofc its going to be ok for us, but it wont for others) is absurd | 10:17 |
| uvos__ | freemangordon: microcontroller on cpcap | 10:17 |
| uvos__ | android uploades short macros to it | 10:17 |
| freemangordon | uvos__: you checked in different conditions | 10:17 |
| freemangordon | now I propose to change the conditions and test again | 10:18 |
| uvos__ | i dont see how you having a good battery now are valid conditions | 10:18 |
| freemangordon | 1. you reserved some charge because of the idle draw, now that's (hopefully) fixed | 10:18 |
| freemangordon | I have a bad battery too | 10:18 |
| freemangordon | and another device to test with, if needed | 10:18 |
| uvos__ | for sure you have not fixed it on bionic | 10:19 |
| freemangordon | how do you know? | 10:19 |
| uvos__ | because i doubt that the same issue uses mutch more power on one device than the other | 10:19 |
| uvos__ | ie there are at least 2 issues | 10:19 |
| freemangordon | why not, modem firmwares are diffirent, no? | 10:19 |
| uvos__ | yes, slightly still i doubt | 10:20 |
| freemangordon | and 'fixing' it by putting a band-aid (lets shut down @ 3.35) is not a real fix | 10:21 |
| uvos__ | never siad its a real fix | 10:21 |
| freemangordon | so, lets try to properly fix it | 10:21 |
| uvos__ | how | 10:21 |
| uvos__ | the real fix would be to drop every mapphone besides xt910 | 10:21 |
| freemangordon | modem shutdown is step 1, for sure | 10:21 |
| uvos__ | (wich has no locked bootloader) | 10:21 |
| freemangordon | disable cpu1 is step2 | 10:22 |
| freemangordon | what you proposed (charge in kexecboot) - step 3 | 10:22 |
| uvos__ | you could also build cpcap modules into kernel | 10:22 |
| uvos__ | to make it charge slightly sooner in boot | 10:22 |
| freemangordon | right | 10:23 |
| sicelo | freemangordon: what do you mean 'bring charger detection' ... or you mean to kexecboot? | 11:26 |
| uvos__ | sicelo: cpcap-charger dosent negotiate for power via usb protocoll | 11:27 |
| uvos__ | nor dose it recognize the tied datapins signal | 11:27 |
| uvos__ | it just takes 500mA, no matter if the port supports less or more than that | 11:28 |
| sicelo | ok | 11:28 |
| uvos__ | this causes additional headaches at boot | 11:29 |
| uvos__ | as the device will continue to discharge even after enableing charging | 11:29 |
| uvos__ | until its truely done with booting | 11:29 |
| Wizzup | uvos__: ping | 11:44 |
| Wizzup | https://twitter.com/maemoleste/status/1588120000220450816 | 11:45 |
| uvos__ | Wizzup: pong (limited avialability) | 11:45 |
| uvos__ | Wizzup: nice :) | 11:45 |
| Wizzup | just check the photo | 11:45 |
| Wizzup | I managed to carry this all somehow | 11:45 |
| Wizzup | lol | 11:45 |
| uvos__ | what are those white ones? | 11:45 |
| Wizzup | droid 2 | 11:46 |
| Wizzup | just white | 11:46 |
| uvos__ | not the d2 | 11:46 |
| uvos__ | second row | 11:46 |
| Wizzup | also atrix | 11:46 |
| Wizzup | mb886 | 11:46 |
| Wizzup | others are mb885 | 11:46 |
| Wizzup | maybe they're not mapphones :) | 11:46 |
| uvos__ | these cant be the same | 11:46 |
| uvos__ | they dont even have touchscreen buttons | 11:47 |
| Wizzup | https://www.gsmarena.com/motorola_atrix_hd_mb886-4867.php | 11:47 |
| Wizzup | qualcomm | 11:47 |
| uvos__ | ah atrix hd | 11:47 |
| uvos__ | ok | 11:47 |
| uvos__ | yeah atrix 2 is mapphone atrix hd and atrix 4g are not | 11:47 |
| Wizzup | still MSM8960 is pretty well supported in mainline | 11:47 |
| uvos__ | true | 11:48 |
| Wizzup | but all the other stuff :D | 11:48 |
| uvos__ | altho id rather support xt1602, i need to try to get another one | 11:48 |
| uvos__ | anyhow neat :) | 11:48 |
| Wizzup | yeah I didn't know I had this many | 11:48 |
| Wizzup | explains why my back hurts | 11:49 |
| Wizzup | argh I wrote create instead of crazy | 11:52 |
| * norayr | 14:25 | |
| norayr | on pmo wiki i see there are even modern sony phones that work with mainline: sony xperia 10 and 10 plus or xa2 plus. | 14:27 |
| norayr | those are very fast devices. | 14:27 |
| norayr | on motorola, i think i'll buy a tablet as soon as you tell me that tablet has chances to be supported by maemo. | 14:28 |
| norayr | no space on the table for notebook to watch youtube together so a tablet which can do that would be great. | 14:30 |
| norayr | i see even sony z2 tablet is supported by mainline. just it is too expensive for us now. | 14:30 |
| Wizzup | norayr: do they work with modem and 3d and everything? | 14:32 |
| Wizzup | all the ones I checked usually only have some things working | 14:32 |
| uvos__ | if devices are to be taken from pmos to support | 14:34 |
| norayr | i don't know, i see the screenshots on their wiki and i filtered those down by the "mainline: works" field. | 14:35 |
| uvos__ | i imo makes the most sense to coose from the ones in at least the Community support category in the devices wiki page | 14:35 |
| norayr | many other devices dont have that. | 14:35 |
| Wizzup | can you link to some that actually work? | 14:35 |
| norayr | yeah, the one plus has pretty good support, i saw it on video. | 14:36 |
| uvos__ | Wizzup: MSM8916 devices like xt1602 really work with mainline quite well | 14:36 |
| uvos__ | on xt1602 specificly everything works really | 14:36 |
| uvos__ | besides the cameras | 14:36 |
| Wizzup | got a link to one from the wiki? | 14:36 |
| norayr | I think i saw 8916 devices on their wiki | 14:37 |
| uvos__ | https://wiki.postmarketos.org/wiki/Devices | 14:37 |
| uvos__ | take your pick | 14:37 |
| uvos__ | really | 14:37 |
| uvos__ | choose one with manny Y | 14:37 |
| norayr | i was filtering sony's from there because i like how they look. | 14:38 |
| Wizzup | so I have looked there many times and ask you to pick one, because I never saw that supports all the things say the d4 does | 14:38 |
| uvos__ | right ok | 14:38 |
| uvos__ | https://wiki.postmarketos.org/wiki/Motorola_Moto_G4_Play_(motorola-harpia) | 14:38 |
| uvos__ | i have one of those | 14:38 |
| uvos__ | everything works | 14:38 |
| uvos__ | like d4 | 14:38 |
| uvos__ | except pm | 14:38 |
| uvos__ | its worse | 14:38 |
| Wizzup | yeah, pm is probably poor | 14:39 |
| uvos__ | its also fairly fast | 14:39 |
| uvos__ | chipset can do good pm, but it is not teribly great on mainline | 14:40 |
| uvos__ | note that everything only works on xt1602, (ie european variant) other people have wierd issues with the other variants | 14:41 |
| Wizzup | yeah I saw that on the wiki page | 14:41 |
| Wizzup | *shrug* | 14:41 |
| Wizzup | it would be good to support some of those, but it doesn't seem like it's only a little bit of work | 14:42 |
| Wizzup | I wonder if they have scripts for pm for example | 14:42 |
| Wizzup | and if it works with ofono (it mostly mentions mm, probably because phosh wants that) | 14:42 |
| uvos__ | it works with ofono | 14:42 |
| uvos__ | at least in very basic capacity | 14:42 |
| Wizzup | ok | 14:43 |
| uvos__ | i dont think it would be mutch more work than mapphone bringup | 14:43 |
| * Wizzup going to rest for bit, bbl | 14:43 | |
| uvos__ | to get it to the state of pp | 14:43 |
| Wizzup | right | 14:43 |
| uvos__ | gn :P | 14:44 |
| uvos__ | still on us clock i imagine | 14:44 |
| Wizzup | mostly just no sleep during travel, and I have more work in a few hours :) | 14:44 |
| Wizzup | but yes, also on west coast clock | 14:44 |
| norayr | i even think of n9 sometimes because it also looks good, i like square corners, jolla is pretty good looking for me. but i understand it is very difficult to find n9 with good battery and it is d to replace it. | 14:48 |
| norayr | and jolla has no mainline support. | 14:48 |
| norayr | i have the device and i dont use it. just hope it will have better mainline support one day. | 14:49 |
| uvos__ | i kinda think the n9 is a poor target, it dident sell nearly as well as mainstream android devices and its hw was really outdated even when it was released | 14:49 |
| norayr | in generally it would be great to be available on something which is produced today. | 14:52 |
| uvos__ | with a keyboard in d4 size :P | 14:54 |
| uvos__ | i gues they still make the pp, at least the pro | 14:54 |
| sicelo | norayr: you're wasting your time :-) | 14:54 |
| norayr | Lets say shift https://wiki.postmarketos.org/wiki/SHIFT_SHIFT6mq_(shift-axolotl) | 14:56 |
| uvos__ | norayr: they very mutch might not even make this phone 2 years on | 14:59 |
| uvos__ | without the vendors themselves supportin mainline linux | 15:00 |
| uvos__ | we will imo never have fully working devices that are not fairly old | 15:00 |
| uvos__ | like at least a couple of years | 15:01 |
| norayr | sicelo: what do you mean? (: | 16:14 |
| norayr | (i am, surely, thats what i do best is wasting, but it is interesting what do you think about this situation) | 16:14 |
| sicelo | i still get unexpected reboots on droid 4, with no load, and no power issues (it rebooted while on charger) | 18:19 |
| Wizzup | I haven't really seen those recently, on -devel | 18:19 |
| Wizzup | uvos: also I don't recall seeing Xorg hangs really, is that the same drm thing still? | 18:19 |
| sicelo | i'm on devel too | 18:20 |
| freemangordon | sicelo: battery | 18:42 |
| freemangordon | charger doe not make much differerence as it is allowed to draw up to 500 mA | 18:43 |
| freemangordon | as soon as you go over that, charger is disconnected and all of the load is taken by the battery | 18:43 |
| freemangordon | Wizzup: me neither, but I use it mainly with cromium | 18:44 |
| sicelo | there was no load on the system at all | 18:44 |
| freemangordon | was it connected to network? | 18:44 |
| sicelo | actually i wanted to do `apt update` ... but it died while i was just typing | 18:47 |
| sicelo | freemangordon: yes, it was on wifi. no network applications running | 18:48 |
| sicelo | it'd be funny for it to die on charger due to battery issues | 18:50 |
| freemangordon | try to increase charging current | 18:53 |
| freemangordon | to see if it will happen | 18:53 |
| freemangordon | like, connect some 2.4 A charger | 18:53 |
| freemangordon | and set max current to 2.2 or something | 18:53 |
| sicelo | the thing is ... it does this when i don't expect it | 18:54 |
| freemangordon | could it be something stupid, like loose battery connection ? | 18:55 |
| sicelo | after it rebooted, i actually did the apt upgrade without issue. it's still fine now, after installing a few other packages in ham | 18:55 |
| sicelo | not loose battery. the last time it happened (i reported here), the device was sitting on a table | 18:56 |
| freemangordon | did you try to tighten the screws? | 18:57 |
| sicelo | they're tight :-) | 18:58 |
| sicelo | anything beyond this tight will break something | 18:58 |
| freemangordon | ok | 18:58 |
| freemangordon | what is the capacity of your battery? | 18:58 |
| sicelo | no idea tbh. the general consensus in the chat is that it's weak | 18:59 |
| freemangordon | please pastebin /sys/class/power_supply/battery/uevent | 19:00 |
| sicelo | https://paste.debian.net/1259437/ | 19:02 |
| freemangordon | 903982 | 19:02 |
| freemangordon | also, what do you mean by 'unexpected reboot"? | 19:03 |
| freemangordon | does it just reset or it is normal shutdown? | 19:03 |
| sicelo | typing `apt update`, device dies and starts up again. i didn't expect it to do that | 19:03 |
| sicelo | it's not shutdown. it boots itself up | 19:03 |
| freemangordon | the battery is genuine or some replacement? | 19:04 |
| sicelo | actually not even the white led shows up, so it's not a shutdown | 19:04 |
| freemangordon | when kernel shuts down because of low voltage, there is no white led | 19:05 |
| sicelo | battery is a replacement. i reused the original eb41 circuitry however | 19:05 |
| freemangordon | what is the design capacity? | 19:05 |
| sicelo | it's written 2000mAh, but likely false :-p | 19:06 |
| freemangordon | well, I would recommend to bye another one. The one uvos recommended seems to be very good and is very easy to disassemble | 19:08 |
| sicelo | can't find those batteries this side of the world. | 19:08 |
| freemangordon | you cant find battery for LG Google Nexus 4? | 19:11 |
| freemangordon | E960 BL-T5 | 19:11 |
| freemangordon | amazon should have it, no idea if they will deliver | 19:12 |
| freemangordon | https://www.amazon.com/Replacement-Battery-BL-T5-Google-Adhesive/dp/B08XBMX51M | 19:12 |
| freemangordon | not sure this one is good though, but you got the idea | 19:13 |
| sicelo | yes, no nexus phones ever landed here. anyway, i don't mind the capacity of this battery atm since i don't really use the droid 4. just boot it to update once in a while. | 19:45 |
| freemangordon | it is not about the capacity | 19:58 |
| freemangordon | but about the internal resistance | 19:58 |
| freemangordon | keep in mind that it is possible that eb41 BMS might cut off the connection under some unknown conditions | 19:59 |
| freemangordon | for example, the battery of the second d4 I have here (the one I used as a donor for battery circuit) was providing 0V at the terminals, despite the cell was @ 3.8V | 20:01 |
| freemangordon | I had to connect a charger to make it provide voltage | 20:02 |
| freemangordon | we don;t know what else protection logic there is | 20:02 |
| Wizzup | nedko: I'll get you the sticker files tomorrow | 20:07 |
| nedko | Wizzup: great, thanks | 20:08 |
| uvos | my d4 also ocassionaly hangs and watchdog reboots | 20:09 |
| uvos | its mutch less often than it used to | 20:09 |
| uvos | but it still happens | 20:09 |
| uvos | its def a hang and wd reboot | 20:09 |
| Wizzup | was the microwave wifi problem ever fixed? | 20:09 |
| uvos | because i use the device to listen to music alot, and when it happens the music will loop for a while untill wd kicks in | 20:10 |
| uvos | Wizzup: no idea, its at least better, it used to crash very often when loosing wifi | 20:10 |
| uvos | but havent tested that explictly | 20:11 |
| uvos | the wd reboot ends with no logs in pstore | 20:11 |
| uvos | hmm | 20:12 |
| uvos | maybe the reason why i dont see the wifi hang anymore could also be because i use gprs now while under way | 20:13 |
| uvos | so the device dosent autoconnect to public wifi aps anymore | 20:13 |
| sicelo | i would agree to the hang + wd observation | 20:14 |
| freemangordon | just happened | 20:20 |
| freemangordon | but I have oops | 20:20 |
| freemangordon | uvos: https://pastebin.com/PWbWmk30 | 20:23 |
| freemangordon | I guess cpcap_battery_lowbph_enable | 20:23 |
| freemangordon | looks like my 30s patch | 20:24 |
| freemangordon | tmlind: please help with ^^^ | 20:45 |
| freemangordon | why does it complain that I can't schedule from a timer function?!? do I need to have a wq for that? | 20:46 |
| freemangordon | oh: "Timer functions must be atomic in all the ways we discussed in..." | 21:03 |
| sicelo | freemangordon: that's LDD? :-) | 21:07 |
| * sicelo guesses he should get a copy too | 21:07 | |
| freemangordon | umm, ldd? | 21:07 |
| freemangordon | ah, "linux device drivers" I guess | 21:08 |
| sicelo | yes. is 3rd edition still the latest, or my search engine-fu fails me? | 21:09 |
| freemangordon | oh, ok, seems I have to use delayed_work and not timer | 21:23 |
| Wizzup | 'rethink possible' - atrix startup screen | 22:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!