| Wizzup | uvos: https://github.com/maemo-leste/sphone/tree/wip-rtcom don't merge yet, but this mostly does it | 00:01 |
|---|---|---|
| Wizzup | I will do another test tomorrow morning | 00:01 |
| Wizzup | not sure why the remote_name is not set for me, but maybe it doesn't get the contact | 00:02 |
| uvos | it looks up the name in the default eds address book | 00:04 |
| uvos | abook dosent use the default eds address book at all irrc | 00:04 |
| uvos | it just creates its own and dosent want to interop with other applications that use eds at all (gnome-contacts, evolution etc) | 00:05 |
| Wizzup | ah, ok, so that's why it didn't find anything | 00:05 |
| uvos | you can just set the abook addressbok to be the default | 00:05 |
| uvos | in eds | 00:05 |
| uvos | or you can tell sphone what address book to use | 00:06 |
| Wizzup | do we have some doc on that? | 00:07 |
| uvos | no | 00:07 |
| uvos | really abook should just use whater book is set as default | 00:08 |
| uvos | instead of hardcodeing the selection by name or whatever | 00:08 |
| Wizzup | I don't know how to change it in sphone or in eds really | 00:15 |
| Wizzup | but would like to know for testing purposes :) | 00:15 |
| SuperMarioSF | Just bought 2 Droid 4, in case something went wrong. | 05:35 |
| SuperMarioSF | with replacement batteries. | 05:35 |
| SuperMarioSF | I found the dock for d4, also getting one. | 06:00 |
| SuperMarioSF | wow, one of my d4 had already started shipping. ETA: Aug. 11th | 06:01 |
| dsc_ | SuperMarioSF: where did you find 'm? | 09:34 |
| SuperMarioSF | I was introduced by #aosc guys long before, and recently rediscovered by searching Linux based phone distro. | 09:35 |
| SuperMarioSF | And I had a Nokia N900, so I looked in. | 09:36 |
| SuperMarioSF | more accurately, I was introduced by #aosc-retro guys. | 09:38 |
| SuperMarioSF | they were trying some hildon desktops themselves iirc | 09:38 |
| dsc_ | SuperMarioSF: oh I meant where did you find the Droid4's | 09:38 |
| SuperMarioSF | oh, here are plenty in second-hand market of China. | 09:39 |
| SuperMarioSF | even spare parts are available. | 09:39 |
| dsc_ | ah cool | 09:39 |
| SuperMarioSF | so I can just buy some batteries and replace the old one. | 09:39 |
| SuperMarioSF | I also found a dock for d4 | 09:41 |
| uvos__ | SuperMarioSF: the problem with the "new" batteries is that they where all produced before 2014 | 09:41 |
| SuperMarioSF | yeah, that was old stock | 09:41 |
| uvos__ | they often have little remaining capacity | 09:41 |
| SuperMarioSF | but they never used, seems keeping at a good condition. | 09:41 |
| uvos__ | 50% is typical | 09:41 |
| uvos__ | the d4 uses screw terminals, and is fine with a bare cell | 09:42 |
| uvos__ | i would reccomend soruceing some other cell and just using that | 09:42 |
| SuperMarioSF | if there is need and enough demand, maybe you can order a custom batch of fresh new batteries. | 09:43 |
| uvos__ | SuperMarioSF: its not nessecary | 09:43 |
| uvos__ | really | 09:43 |
| uvos__ | i desinged a pcb to connect to the battery terminals | 09:43 |
| uvos__ | and you can just solder some leads to that | 09:43 |
| uvos__ | SuperMarioSF: the batterys age particualy badly btw | 09:43 |
| uvos__ | they are hvlipo chem | 09:43 |
| SuperMarioSF | so is there a way to convert existing battery into it? | 09:44 |
| uvos__ | so no the unused ones are usually not in good condition | 09:44 |
| uvos__ | SuperMarioSF: yes | 09:44 |
| SuperMarioSF | for example, mass produced (or should I say, mass copied) Nokia battrries? | 09:44 |
| uvos__ | i would just buy a bare cell | 09:44 |
| SuperMarioSF | I usuay don't want to deal with bare cell. but from capacity standpoint you are right. | 09:45 |
| uvos__ | http://uvos.xyz/maserati/screenshots/IMG_20201015_185706.jpg | 09:45 |
| uvos__ | i ended up with another cell | 09:45 |
| SuperMarioSF | since those old batteries are dirt cheap now I can just replace them at will. | 09:45 |
| uvos__ | (this one had high internal resitance) | 09:46 |
| uvos__ | but thats what i did | 09:46 |
| uvos__ | http://uvos.xyz/maserati/maseraiBatteryAdapter.tar.xz | 09:46 |
| uvos__ | adapter pcb | 09:46 |
| uvos__ | SuperMarioSF: btw since you say there are spares available | 09:53 |
| uvos__ | SuperMarioSF: are battery doors available? with or without the inductive chraging. we have i thin on the order of 20 d4s with no rear door | 09:54 |
| uvos__ | if you can find where we could maybe buy those, that would be neat | 09:54 |
| SuperMarioSF | no luck finding those. | 09:55 |
| SuperMarioSF | However if you need I can design a 3D printed one. | 09:55 |
| uvos__ | sure, but unfortinatly its not so easy | 09:56 |
| uvos__ | i did a test design | 09:56 |
| uvos__ | and the hooks where to fragile (sla) | 09:56 |
| SuperMarioSF | yup, that were the problem. | 09:56 |
| uvos__ | yeah | 09:57 |
| SuperMarioSF | btw I'm going to Shenzhen next week, maybe we can find some really old parts there. | 09:59 |
| SuperMarioSF | Last time I checked there I found a lots of weird old thing. | 10:00 |
| uvos__ | would be neat | 10:01 |
| uvos__ | Wizzup: btw that patch for sphone | 10:01 |
| uvos__ | Wizzup: thats not sufficant | 10:01 |
| uvos__ | Wizzup: you changed the code for writing a call int the store and reading a sms out of the store | 10:01 |
| uvos__ | Wizzup: but the code for reading a call and writing a sms remains unchainged | 10:01 |
| SuperMarioSF | maybe I can came up a solution for 3d printing back cover. | 10:02 |
| uvos__ | SuperMarioSF: maybe yeah, you could friction fit it to the inside of the bay i gues | 10:03 |
| uvos__ | at the very least | 10:03 |
| uvos__ | you pull that off with fdm even | 10:03 |
| uvos__ | Wizzup: get_calls_for_contact for instance | 10:03 |
| SuperMarioSF | for example change some part to some more sturdy material like epoxy. | 10:04 |
| uvos__ | im skeptical that would work | 10:05 |
| SuperMarioSF | or why not just DIY molding with epoxy? | 10:05 |
| uvos__ | you could insert stamped or milled sheet of aluminum as the hooks | 10:05 |
| uvos__ | that woudl probubly work | 10:05 |
| uvos__ | i have been wanting to try that on my mill | 10:05 |
| SuperMarioSF | probably. | 10:05 |
| uvos__ | Wizzup: btw its ContactsSource in sphone.ini | 10:06 |
| uvos__ | to tell sphone what to use | 10:07 |
| uvos__ | Wizzup: this takes the book uid | 10:07 |
| Wizzup | uvos__: just woke up, will take a look at the sphone commit momentarily | 10:32 |
| Wizzup | 09:38 < SuperMarioSF> they were trying some hildon desktops themselves iirc | 10:33 |
| Wizzup | when was this? | 10:33 |
| SuperMarioSF | I can't remember, should in few months ago. | 10:41 |
| Wizzup | okay, would be good to know in case we could collaborate | 10:45 |
| SuperMarioSF | I guess they are happy to help. They managed to boot a i486 with 96MB RAM with full systemd support. | 10:47 |
| SuperMarioSF | (on AOSC/Retro branch) | 10:47 |
| Wizzup | with h-d? | 10:48 |
| SuperMarioSF | h-d? | 10:48 |
| uvos__ | hildon-desktop | 10:48 |
| SuperMarioSF | nope. desktop-less. | 10:48 |
| SuperMarioSF | for a desktop enabled one, at least 128MB | 10:49 |
| SuperMarioSF | running icewm | 10:49 |
| Wizzup | interesting, so aosc (android open source?) retro are booting, what, android on old pcs? | 10:49 |
| SuperMarioSF | Anthon Open Source Community, not Android related. | 10:49 |
| SuperMarioSF | on really old PCs, PDAs, UMPCs and forgotten Dev boards. | 10:50 |
| Wizzup | Oooh | 10:51 |
| Wizzup | cool | 10:52 |
| SuperMarioSF | for details: https://wiki.aosc.io/aosc-os/retro/intro/ | 10:52 |
| SuperMarioSF | they have IRC channel on libera.chat #aosc-retro | 10:53 |
| Wizzup | cool, I'll idle there | 10:54 |
| SuperMarioSF | btw the IRC channel is bridged with Discord and Telegram. So you can see the whole picture on the community. | 10:56 |
| dreamer | "bridged" | 10:56 |
| Wizzup | I've seen that before, usually, depending on the integration it becomes a bit messy | 10:57 |
| dreamer | not a bridge | 10:57 |
| Wizzup | dreamer: aren't there some more neat/native integrations? | 10:57 |
| Wizzup | I naively assumed there were | 10:57 |
| dreamer | indeed there are not | 10:57 |
| dreamer | only matrix does actual bridging of protocols | 10:57 |
| Wizzup | well, I suppose for the things you can't self host it's harder | 10:57 |
| dreamer | thigs like discord and telegram rely on bots shouting messages back and forth | 10:57 |
| Wizzup | what about mattermost, or spectrum? | 10:57 |
| dreamer | I call those "tin can telephones" | 10:58 |
| dreamer | mattermost has an ircd bridge | 10:58 |
| dreamer | that essentially works as a kind of bouncer service | 10:58 |
| dreamer | works rather well imo | 10:58 |
| Wizzup | in any case, it would be good to make it easier for folks to join at some point | 10:58 |
| dreamer | (means you connect to that service as if it's an ircd. using your irc client) | 10:58 |
| Wizzup | yeah I understand | 10:58 |
| Wizzup | SuperMarioSF: noted, I only saw a few folks on irc and /names doesn't show the rest I guess :) | 10:59 |
| dreamer | imo is generally less annoying as matrix with it's massive quits/joins :P | 10:59 |
| dreamer | and doesn't really have to "bridge" any thing, since it connects directly with mattermost | 10:59 |
| SuperMarioSF | on telegram side there are 120 members. | 10:59 |
| Wizzup | yeah, one of the downsides of your own ircd is that people usually prefer being on one of the larger irc servers I thought | 11:00 |
| Wizzup | I know that debian bridged xmpp and irc somehow, any idea how that worked? | 11:00 |
| SuperMarioSF | well maybe that is not actually 'bridging', more like forwarding. | 11:19 |
| SuperMarioSF | (also apply on AOSC's) | 11:19 |
| SuperMarioSF | some bad news. | 12:48 |
| SuperMarioSF | I can't get the old stock XT883. because seller refused to sell me. | 12:49 |
| SuperMarioSF | apparently someone tricked this person, make him paranoid about buyer request pay shipping fee when arrived. | 12:50 |
| bencoh | uh | 12:50 |
| SuperMarioSF | there are two less good condition XT883 available. also new stock. | 12:51 |
| SuperMarioSF | I had to admit these days the trust between two random strangers is basically a non-existence thing in China, no matter online or offline... | 12:58 |
| Wizzup | I can imagine | 13:07 |
| SuperMarioSF | One of XT883's stock have been secured. | 13:37 |
| SuperMarioSF | 1 to go. | 13:37 |
| Wizzup | sweet :) | 13:43 |
| Wizzup | not sure if anyone has seen it before, but my d4 has a slightly smaller screen render now, like there's a black border everywhere, and the screen redraw works weirdly | 14:24 |
| Wizzup | I have occasionally seen this on my n900 with fremantle, but it happened very rarely | 14:25 |
| Wizzup | screen rotation also fails | 14:26 |
| Wizzup | a few xrandr rotates makes it work again | 14:27 |
| Wizzup | weird | 14:27 |
| SuperMarioSF | maybe some X or compositor issue? | 14:32 |
| sicelo | i think it never happens in stock hildon, but from modified hildon as found in cssu onwards. I recall it happens when device boots up in portrait instead of landscape (hence not a problem in stock hildon, as portrait isn't really supported there) | 14:33 |
| Wizzup | sicelo: this just happened 'over night' | 14:41 |
| Wizzup | like, I woke up, unlocked the device, and it was like this, but uptime was 1+ day | 14:41 |
| buZz | Wizzup: i have sometimes seen such , but always assumed it was just my mind | 14:41 |
| buZz | does 'xrandr' also see it? | 14:42 |
| Wizzup | buZz: yes, it had a weird effect on me some times a few years ago when I was like "is this me?" | 14:44 |
| buZz | maybe you can see it on scrot? | 14:45 |
| Wizzup | I 'fixed' it already | 14:45 |
| Wizzup | but I'm sure it's there | 14:45 |
| buZz | next time | 14:45 |
| Wizzup | trust me, it is :) | 14:45 |
| buZz | is eh 'google talk' in 'voip&IM accounts' the general XMPP one? | 14:54 |
| buZz | oh 'telepathy-gabble' perhaps? | 14:55 |
| Wizzup | did you update? | 14:56 |
| Wizzup | there should be normal jabber/xmpp | 14:56 |
| buZz | i did, still have google talk and irc in there, no xmpp/jabber | 14:56 |
| buZz | do i need to install telepathy-gabble ? | 14:56 |
| Wizzup | sure, but isn't that pulled automatically | 14:57 |
| uvos__ | Wizzup: does 'xrandr' also see it? | 14:57 |
| uvos__ | this one is imporant | 14:57 |
| buZz | maybe some meta package isnt grabbing new items for it? | 14:57 |
| Wizzup | uvos__: it was giving the usual res | 14:58 |
| Wizzup | buZz: sorry, I can't check for you now, I can check in a few hours, I'm about to go out | 14:58 |
| uvos__ | ok | 14:58 |
| Wizzup | uvos__: I didn't check overscan and such | 14:58 |
| uvos__ | i gues also kill h-d next time | 14:58 |
| uvos__ | to exonerate xorg | 14:58 |
| uvos__ | but sounds like a bug in hildon | 14:59 |
| buZz | np, i'll just try installing it, someone at nurdspace setup a xmpp server | 14:59 |
| buZz | i might be online with buzz@space.nurdspace.nl now | 15:00 |
| Wizzup | which server? prosody? | 15:00 |
| buZz | yez | 15:02 |
| buZz | indeed | 15:02 |
| buZz | https://nurdspace.nl/Xmpp <- poor documentation | 15:02 |
| buZz | i might only have seen your msg because i opened conversations manually? | 15:02 |
| buZz | can you send another | 15:02 |
| buZz | any interface to send a msg to a random address? :P | 15:03 |
| Wizzup | I don't know if we even built the latest conversations for the repo btw | 15:03 |
| Wizzup | yes, conversations currently does -no- notifications whatsoever | 15:03 |
| buZz | its been a while, but it does have tabs for irc/jabber/ofono | 15:03 |
| buZz | yet, all SMS are only in 'all' , not in 'ofono' | 15:04 |
| buZz | :) | 15:04 |
| Wizzup | yes, the ofono logging of sphone is broken | 15:04 |
| Wizzup | I am going to fix it today | 15:04 |
| buZz | ah ok | 15:05 |
| buZz | Wizzup: can you also s/Unkown/Unknown/ everywhere :P | 15:05 |
| uvos__ | buZz: its as the author intended | 15:06 |
| buZz | ^_^ | 15:06 |
| buZz | some kinda interface to see my xmpp friends and their status would be useful too i guess | 15:07 |
| buZz | maybe i'll just try installing pidgin or something? | 15:07 |
| Wizzup | buZz: this will be in the address book | 15:08 |
| Wizzup | it should work already | 15:08 |
| buZz | not sure how 'contacts' will let me state if a user is jabber/irc/phone | 15:09 |
| Wizzup | (1) it should populate based on your contacts (2) just like on fremantle/n900 :) | 15:10 |
| buZz | :) | 15:10 |
| buZz | from the xmpp server you mean? i think ours doesnt store contacts | 15:10 |
| buZz | wait , -contacts- should populate on my -contacts- ? | 15:11 |
| buZz | contacts > get contacts > import contacts from new account > tap my xmpp one > i just get a edit screen? | 15:12 |
| Wizzup | osso-addressboot reads the roster from telepathy jabber contacts | 15:12 |
| buZz | hm ok | 15:12 |
| Wizzup | sorry, this is fremantle territory | 15:12 |
| Wizzup | got to go | 15:12 |
| Wizzup | ttyl | 15:12 |
| buZz | ci8ao | 15:12 |
| buZz | -8 | 15:12 |
| buZz | ahhh https://farm4.static.flickr.com/3525/4031796040_62de75ded3_o.png | 15:15 |
| buZz | those 'jabber xxx' fields are missing in my osso-abook | 15:15 |
| buZz | maybe needs to restart | 15:15 |
| buZz | hi | 15:18 |
| buZz | btw, rebooting did bring some jabber fields, but kinda weird? i'm not allowed to edit the jabber IM field for instance | 16:26 |
| buZz | i do wish i could start a conversation yet :P | 16:38 |
| dreamer | I think this is the universe telling you something ;) | 16:38 |
| buZz | ^_^ | 16:38 |
| buZz | telepathy seems pretty wide? especially in KDE land | 16:41 |
| buZz | telepathy-tank matrix, telepathy-rakia sip, telepathy-idle irc, telepathy-haze 'anything libpurple', telepathy-gabble jabber, telepathy-salut some linklocal/bonjour xmpp variant, telepathy-ring something-for-GSM ? | 16:43 |
| buZz | but not finding a lot of frontends that could co-exist on maemo, i think | 16:43 |
| norayr | please give me a link to a proper usb condom. | 17:03 |
| norayr | mine turns droid4 up. | 17:03 |
| norayr | uvos said it shoudn't. | 17:03 |
| norayr | but when i search a usb condom on ebay, i only see something which looks like mine. and which i already got. | 17:03 |
| buZz | noidea_: eh, i just made one myself, with a USB-A female and a USB-A male | 17:14 |
| buZz | and just connected GND and +5V inside it | 17:14 |
| buZz | i plan to make another one that does D+/D-/GND but no +5V | 17:14 |
| uvos__ | you could build a condom that still pulls the id pin up | 17:20 |
| uvos__ | a condom by itself dosent guarentee that the device says off | 17:20 |
| buZz | uvos__: or add a switch for that! | 17:20 |
| uvos__ | you need to just connect vbus and gnd | 17:20 |
| uvos__ | buZz: sure | 17:21 |
| buZz | but USB-A has no ID pin | 17:21 |
| uvos__ | yeah but microusb dose | 17:21 |
| uvos__ | the id pin is for iding the cable | 17:21 |
| uvos__ | not for anything with the host | 17:21 |
| buZz | just noticed: osso-abook can show 'recent' contacts, which includes unadded contacts | 17:21 |
| buZz | tapping one crashes the tool | 17:21 |
| buZz | uvos__: so, a usb-micro condom could use a ID switch | 17:22 |
| uvos__ | buZz: you could, im not sure why you would want to tho | 17:22 |
| uvos__ | (for d4 usage) | 17:22 |
| buZz | yeah not sure, a data-only condom could benefit more i guess | 17:24 |
| buZz | 'export' in osso-abook also crashes :( | 17:33 |
| norayr | another question (not sure it was answered, but maybe i missed the answer) is why maemo kbd opens a window to type in? why initially they didn't do it the way it is in meego/sailfish/android. is wayland/xorg the issue? | 17:47 |
| norayr | (i cannot do hw hacks myself i think) | 17:47 |
| Wizzup | buZz: it shouldn't crash for sure, but yes, it's normal that it adds online folks from protocols even if they are not in the book | 17:50 |
| buZz | norayr: afaik thats just the plain maemo method | 17:55 |
| buZz | meego/sailfish/android are indeed different, ios is similar though | 17:56 |
| Wizzup | buZz: I think if you want to edit the fields, you need to first add the contact as a contact, and then edit it | 18:04 |
| buZz | right, i dont really need to/want to, just trying to figure out how it works :P | 18:14 |
| buZz | fun to see my hackerspace buddies presence icons in contacts now though :) | 18:14 |
| Wizzup | :) | 18:17 |
| sicelo | norayr: maemo predates those OSes you talk about. Also, they may have done it that way because by then, they had no other way to do spell-checks for example | 18:25 |
| sicelo | FYI that 'window' was largely unchanged from even older iterations of Maemo (think N770, N8x0) | 18:26 |
| uvos | its a limitation of the way the vkb was desined not anything else | 18:26 |
| Wizzup | they designed it that way, yes | 18:26 |
| sicelo | norayr: also they supported text input via scribbling (but this didn't make it to Fremantle, probably ran out of time) | 18:28 |
| sicelo | So yeah, today it's considered a problem for obvious reasons | 18:29 |
| sicelo | Maybe Leste should have built itself on Harmattan as opposed to Fremantle :-p | 18:29 |
| uvos | it should be noted that the window is also an option on android, that android uses below a certain screen size | 18:29 |
| uvos | (not really relevant anymore) | 18:29 |
| sicelo | Android definitely does on landscape afaict | 18:30 |
| uvos | depends on screen size | 18:30 |
| sicelo | Tbh, the window thingy is somewhat expected in landscape (which maemo before harmattan was designed for) | 18:31 |
| sicelo | uvos: very few phones have 'deep' enough screen in landscape | 18:31 |
| uvos | on asop the screen has to be very small | 18:32 |
| uvos | i know samsung fidlled with it | 18:32 |
| uvos | but on asop it has to be less than 5 inches or something | 18:32 |
| uvos | (at 16:9 ofc) | 18:33 |
| sicelo | Continuing on my earlier thought - landscape keyboard is also a problem for phosh ... they're currently trying to keep the application visible, but the keyboard gets weird after that | 18:33 |
| sicelo | 5 inches 🤣 | 18:33 |
| sicelo | N900 diagonal is 3.5", ftr | 18:34 |
| buZz | maybe a osso-xterm fork could be made thats only portrait mode , plus , keeps a keyboard on bottom half of the screen | 18:47 |
| Wizzup | maybe different h-i-m could be made so it works for more apps | 18:47 |
| sicelo | And then I'm back to battery woes on d4 :'( | 18:47 |
| buZz | sicelo: you are? | 18:47 |
| buZz | what kinda woes | 18:47 |
| sicelo | Failure to charge | 18:48 |
| buZz | completely? | 18:48 |
| sicelo | Yes | 18:48 |
| buZz | it doesnt boot when connecting a usb cable? | 18:48 |
| sicelo | It boots, to death :-D | 18:48 |
| buZz | sicelo: what do you mean? you get kexecboot? | 18:50 |
| sicelo | Yeah | 18:50 |
| buZz | does it start the kernel then? | 18:50 |
| buZz | ever reaches that chargemode-sdl application? | 18:50 |
| sicelo | Currently doesn't get there | 18:50 |
| sicelo | Because cpcap thinks there's no charger or some such | 18:51 |
| buZz | sicelo: eh, during boot on lowpower, often for me, the d4 doesnt notice the USB cable offering power | 18:52 |
| sicelo | Yes, i remember you sais | 18:52 |
| buZz | sicelo: so during the time -after- kexecboot and the vibrating notification , but -before- i get txt on display, i tend to disconnect/reconnect USB cable a couple times, until LED goes green | 18:52 |
| sicelo | And it matches what i always see. I've accepted it as a "feature" | 18:53 |
| buZz | maybe this can help you? | 18:53 |
| sicelo | I know and do that | 18:53 |
| buZz | as a failsafe, i just have a external li+ charger in my bag with 2 wires :P | 18:53 |
| buZz | just connect it to the battery straight up, and charge from ~whatever (often a powerbank) | 18:53 |
| buZz | just some while is plenty to have it able to boot fully and charge itself again | 18:53 |
| sicelo | Yeah. It's a hassle | 18:55 |
| buZz | ¯\_(ツ)_/¯ | 18:56 |
| buZz | sicelo: another thing i do, is just carry my second d4 along with full battery and powered off | 18:56 |
| Wizzup | I've never been able to not power it | 18:56 |
| buZz | sicelo: then when first is ded/empty, just swap sim+SD over | 18:56 |
| buZz | :P | 18:57 |
| sicelo | I have 1 d4 ;-) | 18:57 |
| buZz | not really recommended imho (wifi calibration and battery calibration goes off) | 18:57 |
| sicelo | Why wifi calibration goes off when you swap sim? | 18:57 |
| buZz | Wizzup: ooo yesterday i almost got a nurdspacer into joining the maemo leste dev-ers , but he's still a bit held back :P any convincing arguments for him? | 18:57 |
| buZz | sicelo: because the wifi radio is calibrated | 18:58 |
| sicelo | Ah, sd | 18:58 |
| buZz | yeah sim&SD | 18:58 |
| Wizzup | depends on what he'd find a convincing argument :P | 18:58 |
| buZz | Wizzup: hehe not sure | 18:58 |
| buZz | he was going on that he really -needs- root on a device and how so many dont really do that | 18:58 |
| buZz | or how they arent coming with source, etc | 18:59 |
| sicelo | Wizzup: uvos says he also hasn't experienced it. But at least myself and buZz do, and somewhat frequently | 18:59 |
| buZz | yeah quite regular | 18:59 |
| Wizzup | sicelo: yeah, when I leave it on a wall charger for a bit it usually just boots after ~10 mins | 18:59 |
| buZz | but i can leave it 'on usb' while 'not charging' (no led goes on, doesnt boot) | 18:59 |
| buZz | just leave it for a while, it -will- charge some, slowly | 18:59 |
| Wizzup | right | 19:00 |
| buZz | iirc that even works when it boots directly from USB connecting, and then crashes during bootup | 19:01 |
| sicelo | It's never happened to me, or I didn't wait long enough. I'm not used to this :-P | 19:01 |
| uvos | did you update to devel | 19:09 |
| uvos | like this week? | 19:09 |
| uvos | i made the cpcap module built in | 19:09 |
| uvos | and ajdusted the irq timeing | 19:09 |
| uvos | and yeah i never have a problem with it | 19:09 |
| sicelo | I am updated | 19:12 |
| buZz | uvos: built-in so the cpmem stuff can work now/soonish ? | 19:13 |
| Wizzup | looks like if we implement handle channels well, we might be able to start a conversation from the address book easily | 19:13 |
| buZz | was it cpmem? not sure | 19:13 |
| uvos | buZz: cpmem? | 19:21 |
| buZz | eh, the library in kernel to read the data from battery? to know if its HV lipo or not | 19:37 |
| buZz | some 1wire protocol | 19:37 |
| uvos | buZz: no thats unrealted | 19:41 |
| uvos | also that works right now | 19:41 |
| uvos | i tested it recently on xt875 | 19:41 |
| buZz | i dont see it working | 19:41 |
| uvos | you just have to unblacklist the module | 19:41 |
| buZz | oh | 19:41 |
| uvos | then detection works and design voltage is set to 4350 mV | 19:42 |
| uvos | you still have to change the charge voltage to 4.3 too | 19:42 |
| uvos | but you can do that over sysfs | 19:42 |
| buZz | i see just bluetooth and idle blacklisted? | 19:42 |
| buZz | at least, in /etc/modprobe.d/* | 19:43 |
| uvos | no | 19:43 |
| uvos | in leste we also blacklist hdq | 19:43 |
| uvos | i cant check rn | 19:44 |
| buZz | ah, yeah , thats in _idle | 19:44 |
| uvos | but im sure its there | 19:44 |
| buZz | i didnt know that was the one you ment :P | 19:44 |
| buZz | i didnt know charge voltage was settable over sysfs, nice :) | 19:45 |
| * buZz reboots with hdq unblacklisted | 19:45 | |
| uvos | should be reflected in voltage_max or what the sysfs file is called | 19:47 |
| uvos | and theres also charge_voltage or so | 19:47 |
| buZz | sadly, still sees 4200000 as max_design :( | 19:48 |
| uvos | thats stays 4.2 (design decision) | 19:48 |
| buZz | 'can not find battery nvmem device' sadly in dmesg :( | 19:48 |
| uvos | check if the module probed | 19:49 |
| uvos | also i do have one battery where the nvmem failed | 19:49 |
| uvos | so theres that | 19:49 |
| buZz | omap_hdq couple lines above, also a 'w1_master_driver attaching...' right after first 'can not find battery nvmem device' , then another two 'can not find battery nvmem device' | 19:49 |
| buZz | i can try with another eb41 i guess | 19:50 |
| uvos | hmm thats wierd maybe dump the nvmem | 19:50 |
| uvos | its in systfs | 19:50 |
| uvos | somewhere | 19:50 |
| uvos | bus/twi or something | 19:50 |
| buZz | its saying it cannot find the nvmem device, how could i read it then? | 19:50 |
| uvos | it cant find the battery nvmem device | 19:51 |
| uvos | the way it works is i dumped a bunch of batteries and looked at the contence | 19:51 |
| uvos | idk what the bytes mean | 19:51 |
| * buZz rubs the flexpcb against contacts a bit | 19:51 | |
| uvos | if its some other version than i know of it might not work | 19:51 |
| buZz | uvos: ahh, ok, i'll check then | 19:51 |
| dreamer | buZz: or else it gets the hose again? | 19:52 |
| buZz | :D | 19:52 |
| uvos | ah also it wont work rn | 19:52 |
| uvos | since i built the cpcap modules in | 19:53 |
| uvos | but the 1w module is a module | 19:53 |
| uvos | the cpcap dependancy is soft | 19:53 |
| uvos | so in this case it cant work | 19:53 |
| uvos | it wont wait for the 1w module | 19:53 |
| uvos | since building it in dosent seam to help sicleo ill make it a module again next release | 19:53 |
| buZz | ah, hmm | 19:55 |
| buZz | 'break irqstatus not cleared (04)' and 'TX irqstatus not cleared' are flooding my dmesg now, it seems | 19:58 |
| buZz | ah, after 'cat nvmem' a bunch of times, it eventually does give a reply | 19:59 |
| uvos | that sounds like you also have a hw issue | 19:59 |
| buZz | perhaps, or the irq isnt properly handled? should that happen through dtb? | 20:00 |
| buZz | https://space.nurdspace.nl/~buzz/2022-08-08-195917_960x540_scrot.png | 20:01 |
| buZz | uvos: does that help? does it confirm 'not the same as my dumps' ? | 20:05 |
| uvos | cant ceck rn | 20:07 |
| uvos | please just provide the file | 20:07 |
| uvos | or sha1 | 20:07 |
| buZz | ah 89-500029ba0f73 is what you seem to check on, but i have 89-5000385c064b | 20:09 |
| buZz | https://space.nurdspace.nl/~buzz/89-5000385c064b.nvmem is the raw file | 20:10 |
| buZz | at least, here you check for that 1w device ; https://github.com/maemo-leste/droid4-linux/blob/maemo-5.18/drivers/power/supply/cpcap-battery.c#L426 | 20:13 |
| uvos | buZz: yeah so you have a different chip | 20:14 |
| uvos | thats thorny | 20:14 |
| uvos | but ok that explains why it never worked for you | 20:14 |
| buZz | :) | 20:15 |
| buZz | i wonder what my other d4 has | 20:15 |
| buZz | or where it is :D | 20:15 |
| buZz | lol, first drawer | 20:15 |
| buZz | the other d4 -also- has a different chip for its EB41 | 20:23 |
| buZz | https://space.nurdspace.nl/~buzz/89-50003a31240b.nvmem is the other battery | 20:25 |
| buZz | seems to contain the same data? | 20:25 |
| buZz | at least, md5,sha1 and sha256sum match ;) | 20:29 |
| Wizzup | btw, this is with our kernel, right? | 20:30 |
| Wizzup | not yours? | 20:30 |
| buZz | yes, with stock kernel , but removed a single blacklist entry in /etc/modprobe.b/blacklist-idle.conf | 20:31 |
| buZz | stock -devel kernel, btw | 20:31 |
| buZz | Wizzup: uvos was telling me it 'should/could' work for getting HV lipo modes working | 20:31 |
| buZz | but alas, it seems to work only with the 89-500029ba0f73 identifying battery, thats in uvos possession? :D | 20:32 |
| uvos | buZz: well all of my batteries report as sutch, since it works on both the d4 with eb41 and bionic with bw8x and and hw4x | 20:34 |
| uvos | but looks like thats just luck | 20:34 |
| uvos | or is unlucky really | 20:34 |
| buZz | perhaps | 20:34 |
| buZz | or maybe you have clones that all copied that one sting? | 20:34 |
| buZz | string* | 20:34 |
| uvos | nah | 20:34 |
| uvos | there are no clones | 20:35 |
| buZz | https://github.com/maemo-leste/bugtracker/issues/621#issuecomment-1208472742 <- has some instructions to get it locally | 20:40 |
| norayr | I saw a unisoc t606 device today first time in my life. never heard before about unisoc company | 20:41 |
| norayr | it's nokia g21 | 20:41 |
| buZz | cool :) | 20:46 |
| norayr | i also cannot charge my droid again | 20:47 |
| norayr | need to unscrew the battery to use separate charger | 20:48 |
| norayr | hate doing that. | 20:48 |
| buZz | tried just leaving it for 30mins on 'unable to boot, not showing sign of charging' ? | 20:48 |
| buZz | with USB connected | 20:48 |
| buZz | that so often works for me | 20:48 |
| uvos | thats _supposed_ to work | 20:48 |
| buZz | a 'usb doctor' then shows ~50mA of draw | 20:48 |
| uvos | cpcap has device off trikle charging | 20:48 |
| buZz | which isnt a lot :P | 20:49 |
| uvos | thats what its set to by mbm | 20:49 |
| buZz | but, enough to get some boot working well enough to charge more later | 20:49 |
| norayr | my pine64 charger shows how much the device draws | 20:49 |
| buZz | uvos: we cant change that right? | 20:49 |
| buZz | norayr: ah, built-in doctor :) | 20:49 |
| uvos | buZz: no also its like 75mA max | 20:49 |
| buZz | i'd love if some people could do the unblacklisting + check their 89-50003xxxxxxxxx number in /sys/bus/w1/devices/ | 20:50 |
| buZz | :P | 20:50 |
| buZz | maybe thats visible on android even? | 20:50 |
| uvos | not sure what to do about that btw | 20:50 |
| norayr | so i noticed in android mode (with empty battery sign) it draws about 0.1-0.2 amper, so i left it like that overnight, but that dxdn't help. | 20:50 |
| uvos | not really sure how to id the chip then if its not allways the same | 20:50 |
| buZz | uvos: i know, but we first need to know how/what is happening , right? so more data could help | 20:50 |
| norayr | sometimes in same mode it ioesn't draw at all. | 20:50 |
| buZz | maybe we used the unique ID of the chip as the -name- of chip , while its actually just the ID string of the same chip? | 20:51 |
| buZz | norayr: maybe your ribbon is breaking a bit on the battery? | 20:51 |
| uvos | buZz: i mean its something to check but it for sure works on various batteries i have | 20:51 |
| buZz | right, but it would maybe be nicer if this works for >1 person? :D | 20:52 |
| uvos | yeah android not wanting to charge after booting (the ! battery sign means the android kernel bootet fully) | 20:52 |
| uvos | suggests some kind of hw failure | 20:52 |
| uvos | or you discharging the battery below 2.5V or something | 20:53 |
| uvos | android refuses to charge below some thresh around there | 20:53 |
| uvos | (also this is _terribe_ for the battery) | 20:53 |
| buZz | uvos: it may be as simple as 'just check for leading 89-500003' | 20:54 |
| buZz | eh, one 0 less | 20:54 |
| buZz | maybe its '89-5000' as chip identifier, and the remaining 4 bytes hex are just the unique battery serial# ? | 21:55 |
| Wizzup | uvos: so I am trying to understand your comments regarding my sphone patch and rtcom | 22:42 |
| Wizzup | I only see two rtcom_el_event_new, and I thought I patched both | 22:43 |
| joerg | buZz: >>leaving it for 30mins on 'unable to boot, not showing sign of charging' << didn't work e.g. on my N950 recently | 22:55 |
| buZz | joerg: yeah i was talking about the droid4 specifically | 22:59 |
| joerg | buZz: probably a common problem with a lot of embedded devices that use somewhat software controled charging | 23:00 |
| sicelo | indeed | 23:00 |
| joerg | seems the hysteresis between where the system tries booting when batvoltage goes up and where it stops working when batvoltage drops is too small for old batteries with high ESR | 23:01 |
| buZz | yeah totally | 23:03 |
| buZz | many devices just let the battery charger chip itself manage the poweron/off , so it can always trickle prior to booting | 23:04 |
| buZz | or at least, many i was analyzing | 23:04 |
| joerg | they do tricky charge with a tiny current like the aforementioned 50mA (USB Vbus) and then when a certain battery voltage threshold gets tripped, the system tries booting and often succeeds to get to the point where it messes with charging chip, enables USB PHY and statemachine and the latter two alone need 60mA for themselves on N900 OMAP3. This in turn means the battery suddenly doesn't get charged by a 50+mA but gets DIScharged at a rate of (trickecharge | 23:15 |
| joerg | - sytembootcurrent) = possibly up to 100mA. Depending on the internal impedance of the battery this will cause a Vbat drop that might suffice to make the whole system emergency-shutdown from brownout-detection | 23:15 |
| joerg | trickle* not tricky :-) | 23:15 |
| uvos | Wizzup: yeah but sphone also reads events | 23:17 |
| uvos | and now its reading the backend in the wrong place | 23:17 |
| Wizzup | uvos: right, but the writing was ok | 23:18 |
| Wizzup | uvos: I get confused with the usage of local-name in sphone | 23:18 |
| Wizzup | what is this supposed to be? | 23:18 |
| Wizzup | it's always '<SelfHandle>' in fremantle | 23:18 |
| Wizzup | (since there is no name for the local contact/phone) | 23:18 |
| Wizzup | Is that supposed to be the name of the contact, human friendly? | 23:18 |
| uvos | no idea what its supposed to be in rtcom-el | 23:20 |
| sicelo | joerg: yeah. i always knew N900 to have that problem. but compared with what i've experienced on the Droid 4, N900 problem becomes completely insignificant. Maybe it's kexecboot dance that affects it (since device takes a while to get into kexecboot menu, and all this time it's only draining, not charging battery) | 23:21 |
| uvos | the point is that you changed the way that sphone stores events | 23:22 |
| uvos | but not it reads them | 23:22 |
| uvos | so this disconnect obv breaks sphone | 23:22 |
| Wizzup | yeah, I fixed this locally I think | 23:22 |
| Wizzup | I am just trying to figure out what sphone does with the "name" | 23:22 |
| uvos | what name? | 23:23 |
| Wizzup | it seems to use local-name for the contact->name | 23:23 |
| Wizzup | which is also wrong | 23:23 |
| uvos | thats human readable contact name | 23:23 |
| uvos | as the struct would suggest | 23:23 |
| Wizzup | I think that should be remote-uid | 23:23 |
| uvos | maybe, i cant help you with how rtcomm fields are supposed to be filled | 23:23 |
| Wizzup | :) | 23:24 |
| uvos | i have nothing to go by other than the field name | 23:24 |
| Wizzup | what about a n900 with fremantle? :P | 23:24 |
| uvos | nope | 23:24 |
| sicelo | :-P | 23:24 |
| joerg | sicelo: basically the problem needs hardware and bootloader cooperation to get solved. I N900 they had average hardware support for it and they compensated a lot by fixing the bootloader | 23:27 |
| joerg | obviously the OMAP3-ROMBL enables USB to allow coldflashing, but in NOLO (next "1st" stage bootloader after OMAP's ROMBL) I think they deliberately shut down everything not needed - maybe incl USB PHY and interface - as soon as possible to reduce system power demand, and then let the battery charge while monitoring battery voltage for a certein higher threshold that allows safe regular system boot. Unless the battery is very old and high impedance | 23:36 |
| uvos | the d4 on the other hand is fully hw implemented, the bootloader just sets some regs and shutsdown | 23:37 |
| joerg | wow | 23:37 |
| uvos | problem is the comperator threshold is low | 23:38 |
| uvos | and we have to boot android and then linux before we can charge | 23:38 |
| uvos | this takes to long | 23:38 |
| joerg | the N900 charger controller has a watchdog that mandates tickling every ~10s or it will reset all registers to safe default state which is trickle charge | 23:39 |
| joerg | uvos: yeah, I can see how that takes waaaay too long | 23:40 |
| uvos | new version of mce: pools all key events into one handler and filters from there | 23:51 |
| uvos | this fixes: | 23:51 |
| uvos | * volume keys on xt875 | 23:51 |
| uvos | * volume keys on pp | 23:51 |
| uvos | * lock-generic's lock on slide | 23:52 |
| uvos | * lock-tklock's relock feature | 23:52 |
| uvos | * power key on mz617 | 23:52 |
| uvos | unfotinatly is also very likely to cause some hithero unkown subtle bugs | 23:53 |
| uvos | so please report | 23:53 |
| Wizzup | which kind of bugs should we look for? | 23:54 |
| Wizzup | is this -devel? | 23:54 |
| uvos | Wizzup: yeah | 23:54 |
| Wizzup | ok | 23:54 |
| uvos | anything with input | 23:54 |
| uvos | obv | 23:54 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
