norayr | buzz, i also love it. i am ready to pay resources for it. | 00:27 |
---|---|---|
norayr | and i do, i have many pidgin windows opened on maemo always | 00:27 |
buZz | :D with moving video inside? | 00:28 |
norayr | and pidgin with many many windows eats less resources than one dino with one window | 00:28 |
norayr | well in pidgin i see that text is updated, and scrolled | 00:28 |
norayr | i see some changes in 'watch' command outputs in remote ssh sessions | 00:29 |
norayr | or i connect to one or two console chat servers. com, if u heard. | 00:30 |
norayr | i hate it that phosh is so slow, eats so much memory on the same device, and shows screenshots | 00:30 |
norayr | it's so dumb for me | 00:30 |
norayr | also they have one line of windows in phosh | 00:31 |
norayr | so i need to scroll through all to choose the window i need | 00:31 |
norayr | in maemo it's there after one or two taps | 00:31 |
norayr | i can see it | 00:31 |
norayr | maemo is very fash aand lightweight | 00:32 |
norayr | it is fast on droid | 00:32 |
norayr | i guess on n900, didn't try | 00:32 |
norayr | and on pinephone it is probably a fastest distro | 00:32 |
norayr | if we don't count bad video driver | 00:33 |
norayr | which already improved a lot | 00:33 |
norayr | you know, i was working on very old and slow machines | 00:33 |
norayr | for we droid or pinephone aren't weak | 00:33 |
norayr | but very powerful | 00:34 |
norayr | so we can afford it | 00:34 |
norayr | also it can be implemented more efficdently | 00:34 |
norayr | after all on xorg screen we see many windows simultaneously with updates in them | 00:34 |
norayr | could be maybe something like thatmto save resources | 00:35 |
norayr | still with all its 'hunger' leste is the fastest and most responsive intelfare imo. | 00:35 |
norayr | and it makes sense. it was written long ago and didn't get much wmore hunger since. | 00:36 |
norayr | i don't know why on such a powerful device like pinephone i should wait for so long fol simple gtk3 or qt programs to start. i even afraid tht maybe that's gtk3 problem. | 00:37 |
norayr | and what do they do in dino that it draaains so much power? | 00:38 |
norayr | pidgin with 29 opened windows can be opened whole day for me | 00:38 |
norayr | 20 | 00:38 |
norayr | plus live wallpaper | 00:38 |
norayr | in wy desktop life i always use windowmaker. | 00:39 |
norayr | i was using 486 with linux, it had troubles playing mp3 files. i was giving high priority to the special fork of mpg123 for 486 in order to be able to liten music. | 00:40 |
norayr | and since long ago i am in lovu with wmaker. it takes like 2mb in ram. and it is extremely flexible. | 00:41 |
norayr | i don't know what i am talking about | 00:41 |
norayr | probably that i think phosh and praasma are toooo fatty | 00:42 |
norayr | and waemo is so responsive i don't feel it is slow on very old and 'weak' devices. | 00:42 |
norayr | but those aren't weak. | 00:43 |
norayr | for someone who started vith com'uher with 32kb of ram | 00:43 |
norayr | it is a miracle. | 00:43 |
norayr | and i think gnome3 and kde plasma obviously do something wrong if they are so slow on pinephone. | 00:44 |
norayr | and dino, that it drains the battery ten times faster than pidgin with tens of opened windows. | 00:46 |
buZz | lol, did 'a long voicecall' on leste, now my xorg seems locked, many programs open | 14:31 |
buZz | i guess the proximity sensor doesnt work or sphone dailer doesnt use it | 14:32 |
buZz | ah, does respond to long-power-button-holding | 14:32 |
sicelo | :-) | 14:33 |
Wizzup | buZz: yes, I don't think sphone deals with the proximity sensor yet | 14:33 |
buZz | $soon | 14:35 |
buZz | but, quality was topnotch | 14:35 |
buZz | (after i put the 'voice' volume slider a bit higher, and enabled noise cancellation) | 14:35 |
Wizzup | buZz: that should be enabled by default | 14:36 |
buZz | it isnt on mine | 14:37 |
uvos | mce should deal with the proximity sensor (if sphone puts it in the right mode) | 14:51 |
uvos | its not working? | 14:51 |
Wizzup | not for me afaik | 14:51 |
uvos | (it cant work for me because its in lock-tklock) | 14:51 |
Wizzup | I always lock the phone when calling | 14:51 |
uvos | ok ill have to check whos at fault there | 14:51 |
uvos | i assume every one else is running tklock | 14:52 |
Wizzup | yes | 14:52 |
SuperMarioSF | hi | 16:11 |
SuperMarioSF | I'm back | 16:11 |
Wizzup | hi, I'mm not avail for debugging atm :) | 16:24 |
SuperMarioSF | no problem | 16:32 |
SuperMarioSF | my plan today is flashing another Droid 4 | 16:32 |
SuperMarioSF | however this time a little different | 16:32 |
SuperMarioSF | this droid 4 have already installed LineageOS 14.1, kernel version 3.0.8, with kexecboot already installed. | 16:33 |
SuperMarioSF | so I don't know what to do next. Should I just flash my SD card and just go with it? | 16:33 |
uvos | it came with kexecboot installed? | 16:35 |
uvos | yes you can just flash a sdcard | 16:35 |
SuperMarioSF | so the file flashed on SD card already have necessary information to let an existing kexecboot installation just found the distro on the card? | 16:38 |
SuperMarioSF | currently the kexecboot menu only show the android option and the settings menu. | 16:38 |
uvos | yes | 16:38 |
SuperMarioSF | OK | 16:38 |
SuperMarioSF | Then I just flash a new card then. | 16:38 |
uvos | kexecboot checks for /boot/boot.cfg on every partition | 16:38 |
uvos | and then aggregates all boot entries | 16:38 |
SuperMarioSF | what is the maximum capacity allowed on d4's controller? 32G? | 16:39 |
uvos | there is none | 16:39 |
uvos | or there is, but it huge | 16:39 |
uvos | >2tb | 16:39 |
SuperMarioSF | oh, then I can just toss a 128G card in it just fine. | 16:40 |
SuperMarioSF | I got some really crappy card to test with. My extra durance card will arrive the day after. | 16:42 |
SuperMarioSF | just test for fun at the moment | 16:42 |
SuperMarioSF | oh, crappy card indeed. only 5MB/s write speed. | 16:56 |
SuperMarioSF | the kexecboot installed there is v0.6, seems working just fine. | 17:03 |
uvos | the kexecboot version is not really related to our kexecboot relase | 17:08 |
uvos | its just the version of the ui | 17:08 |
uvos | please do upgrade it if its old, there was a fix that prevents some crashes in the os later (after boot) | 17:09 |
SuperMarioSF | the first boot seems okay | 17:20 |
SuperMarioSF | the only problem is d-pad control are sideways | 17:20 |
uvos__ | wdym dpad? the arrow keys? | 17:30 |
uvos__ | also wdym sideways? | 17:30 |
uvos__ | in what app | 17:30 |
sicelo | dpad nearly always means arrow keys, yes | 17:33 |
SuperMarioSF | arrow keys in kexecboot v0.6 | 17:36 |
SuperMarioSF | the "up" is actually bind on left key | 17:36 |
SuperMarioSF | that is not the case for kexecboot v0.8 | 17:36 |
SuperMarioSF | v0.8 works correctly | 17:37 |
SuperMarioSF | but that isn't a big deal, since it boots kernel no problem | 17:37 |
SuperMarioSF | I'm testing my other exactly the same crappy 128GB SD card, I doubt this card are fake since it was unbelievably cheaply made, and that was an addon for literally US$2 for some other thing that I bought. | 17:41 |
uvos__ | oh that | 17:55 |
uvos__ | that version of kexecboot is really old and must be replaced | 17:56 |
uvos__ | it will cause random failures in the booted kernel+ | 17:56 |
uvos__ | its not fine | 17:56 |
SuperMarioSF | ok | 18:01 |
SuperMarioSF | I guess I see some problems there. | 18:01 |
SuperMarioSF | such as screen tearing | 18:01 |
SuperMarioSF | rebooting and reflashing | 18:02 |
SuperMarioSF | wait I must mixed something | 18:13 |
SuperMarioSF | I just found out my working one running v0.6 of kexecboot | 18:13 |
SuperMarioSF | there is no v0.8.4 after all... | 18:13 |
SuperMarioSF | weird, where I see that version before... | 18:14 |
sicelo | What's the driver for d4 modem? I want to unload and load it again | 18:16 |
sicelo | Right now ofono isn't working, but that seems to be because modem itself is awol | 18:16 |
sicelo | I do have ttyUSB[3,4] though .. not sure if that's the one, but i doubt | 18:17 |
uvos | sicelo: there is not modem driver as sutch | 18:25 |
uvos | its various | 18:25 |
uvos | phy_mapphone_mdm6600 dose the usb if, snd_soc_motmdm the modem->cpu dai, gnss_motmdm gps | 18:26 |
uvos | etc | 18:26 |
uvos | also the "drivers" dont do a whole lot | 18:26 |
uvos | phy_mapphone_mdm6600 just exposes the natvie interfaces of the modem to userspace | 18:26 |
uvos | so im not sure reloading those would help if the modem itself is in a funny state | 18:27 |
SuperMarioSF | just fixed my stiff slide by applying some WD-40 | 19:11 |
SuperMarioSF | be warned not put too much, or WD-40 will leak into screen and that isn;t very easy for cleanup... | 19:12 |
SuperMarioSF | I wonder if OMAP3410 chipset can be supported by maemo-leste | 19:33 |
SuperMarioSF | Motorola Charm and Motorola Flipout | 19:35 |
SuperMarioSF | those device can be interesting | 19:35 |
sicelo | i guess it's time for a reboot then. sigh | 19:41 |
uvos__ | SuperMarioSF: Wizzup was interested in makeing sholes based devices work | 19:41 |
uvos__ | SuperMarioSF: but that would come in the form of xt610 or maybe a855 at first | 19:42 |
uvos__ | also imo its a waste of time | 19:42 |
sicelo | SuperMarioSF: looks like 3410 isn't much different from N900's 3430, so should be doable | 19:42 |
sicelo | hah! no SGX at all in it | 19:43 |
SuperMarioSF | there is no info about dsp in 3410 tho... | 19:43 |
sicelo | well ... dsp is not used on N900 either | 19:44 |
uvos__ | yeah nvm looks like those are not sholes, there even older platform wise | 19:44 |
uvos__ | ? the dsp is used for video decoding no? | 19:44 |
uvos__ | imo its even more of a waste of time to do something <sholes | 19:45 |
sicelo | SuperMarioSF: if you have bootloader issue handled, i'm sure those devices can be well supported in pmOS at least | 19:45 |
sicelo | damn ... those devices have very interesting design. me likey | 19:46 |
sicelo | SuperMarioSF: do you have these devices, or just asking out of interest? | 19:51 |
SuperMarioSF | just out of interest. however if needed, I can just buy one very cheap. | 20:12 |
SuperMarioSF | well not that cheap. | 20:14 |
SuperMarioSF | average 200~300CNY | 20:14 |
SuperMarioSF | no one seems old stock, all used. some even doesn't have battery. | 20:14 |
SuperMarioSF | they were selling as "Game Console Emulation Phone" because the QWERTY keyboard. | 20:15 |
sicelo | I guess buying one would indeed be a waste as uvos says. But working on one you already own is a different matter | 20:20 |
SuperMarioSF | I don't have one, but I would like to have something like that in my collection. | 20:44 |
SuperMarioSF | so far Droid 4 served me well. | 20:44 |
SuperMarioSF | it is very likely to became a daily driver for me. | 20:44 |
Danct12 | sorry for a offtopic question, but i'm currently adapting wl1251-cal to postmarketOS and for some reason fallback mechanism fails to work on boot | 20:46 |
Danct12 | here's the udev debug log: https://termbin.com/6gbg | 20:48 |
sicelo | it's not offtopic | 20:48 |
sicelo | https://github.com/maemo-leste/bugtracker/issues/115 | 20:49 |
sicelo | https://github.com/maemo-leste/bugtracker/issues/102 | 20:49 |
sicelo | those were Wizzup's and my experiences back then. i doubt anyone's looked into it much since then | 20:49 |
SuperMarioSF | so I have a question then... | 20:51 |
SuperMarioSF | battery gauge says need calibration | 20:51 |
SuperMarioSF | how can I do that manually? | 20:51 |
SuperMarioSF | I didn't see anything I can just run in package droid4-battery-calibration | 20:52 |
sicelo | charge it to full, allow it to drain to empty ... you can let this happen naturally. at some point towards completely empty, it will auto-calibrate | 20:52 |
sicelo | ymmv | 20:53 |
SuperMarioSF | ok | 20:53 |
SuperMarioSF | what if power just suddently down while battery percentage isn't nearly as low? Is that will still works? | 20:54 |
sicelo | i think this is also in wiki :-) | 20:54 |
Wizzup | not sure, our doc isn't that great, at least structure wise | 20:54 |
sicelo | SuperMarioSF: hence the 'ymmv' ... if you're luckly, it will still be considered. otherwise, you need to repeat the steps | 20:54 |
Wizzup | sicelo: Danct12: can look in an hr or two | 20:55 |
SuperMarioSF | just looked up on wiki, no such thing were mentioned anywhere... | 20:56 |
SuperMarioSF | but I remember I may read something about battery calibration script in news, it doesn't talked about how it works either. | 20:57 |
sicelo | ah. it's a bit hacky, but works some. the problem is that under linux/Leste, cpcap (currently?) doesn't store the calibration itself, nor does the battery. the script attempts to do this using a file | 21:01 |
SuperMarioSF | ok | 21:02 |
SuperMarioSF | so I will try that after I replaced my battery. | 21:02 |
buZz | you dont need a script to calibrate the battery | 21:28 |
buZz | just : 1) deplete battery without shutting down leste, so you get the 'recharge battery' popup with 'pooodoonk' sound , 2) charge it -once- fully to 100% , 3) repeat 1) , then redo 2) , it will update the measurement | 21:30 |
buZz | every time you do this , it will update the known/measured mAh from the battery you have | 21:30 |
buZz | 'charge fully to 100%' is till the green led goes -off- and message 'disconnect charger' appears , plus battery says 'fully charged' in statusmenu etc | 21:31 |
sicelo | well you do, https://github.com/maemo-leste/droid4-battery-calibration | 21:31 |
sicelo | it's just that you don't need to manually use it :-) | 21:31 |
sicelo | otherwise your precious calibration data vanishes on a reboot | 21:32 |
buZz | ah yeah, indeed | 21:34 |
sicelo | mmm, i actually have a PR against that package. i wonder why it wasn't merged :-/ | 21:46 |
Wizzup | maybe it was missed | 21:47 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!