| Wizzup | rafael2k: did the image work btw? | 01:39 |
|---|---|---|
| rafael2k | Wizzup, testing it now, sorry | 07:14 |
| rafael2k | https://maedevu.maemo.org/images-devel/pinephone/20230127-chimaera/maemo-leste-1.0-arm64-pinephone-20230127.img.xz downloading | 07:42 |
| rafael2k_ | Wizzup, image tested and working! | 08:51 |
| rafael2k_ | tks! | 08:52 |
| rafael2k_ | if possible, leave it available. It is already in a reasonable shape for distribution! | 08:54 |
| Wizzup | ok | 10:17 |
| buZz | is chimaera daily-driverable yet? :P on d4 | 12:32 |
| Wizzup | no | 12:35 |
| Wizzup | tmlind: https://wizzup.org/warning.txt just got this when toying with hdmi on d4, not sure it's related to hdmi | 12:35 |
| Wizzup | buZz: it will be daily-driverable when we have tp-ring working properly, conversations as sms ui, and the tp calls work out of the box | 12:37 |
| Wizzup | but uvos doesn't like the tp work I did for sphone, so we have to either fork sphone to something like phone and potentially merge back later, or just create a new ui for phone calls and stop using sphone | 12:37 |
| buZz | ah, there's no sphone for chimaera now? | 12:39 |
| Wizzup | there is, but it doesn't work how it's supposed to work | 12:39 |
| buZz | ah yeah , thats a drag | 12:39 |
| Wizzup | if you have a different definition of 'daily-driverable', then you can feel free to try it | 12:39 |
| Wizzup | I want it to be like maemo fremantle in UX | 12:39 |
| buZz | well, do calls/sms/mobiledata work? | 12:40 |
| Wizzup | e.g. contacts icons show up, names show up, recent calls in main dialog so I can easily call back a missed number a little bit later, sms from conversations with a UI, delivery status reporting, message read marking, etc | 12:40 |
| Wizzup | without that it is not 'daily driverable' imo | 12:40 |
| buZz | ah hmhm | 12:41 |
| Wizzup | here are some screenshots from fremantle in landscapehttps://wizzup.org/dirlist/maemo-leste/call-ui/ | 12:41 |
| Wizzup | https://wizzup.org/dirlist/maemo-leste/call-ui/ | 12:41 |
| Wizzup | there's also portrait but whoever made the screenshots didn't include that | 12:41 |
| buZz | hmhm, looks a lot more phone-y | 12:52 |
| buZz | oo cool, we already have this data in rtcom or something? https://wizzup.org/dirlist/maemo-leste/call-ui/9%20-%20dbArUkx.png | 12:53 |
| Wizzup | this is probably gconf data, maybe it's in rtcom db | 12:55 |
| Wizzup | not sure, but we definitely don't have this atm | 12:55 |
| Wizzup | it's possible this is just aggregated from rtcom db | 12:55 |
| buZz | hmhm | 12:58 |
| Wizzup | but yeah the recent calls list we get for free | 12:59 |
| Wizzup | it's an existing gtk widget :) | 12:59 |
| Wizzup | well, from a foss maemo lib | 12:59 |
| buZz | i havent decided for my battery monitor, if i want to build my own history of old stats, or just use the 120second values from upower, it seems its a bit .. empty? | 13:00 |
| buZz | that batteryeye thing did its own collection | 13:00 |
| buZz | atm its still realtime only, and seems to have something wrong, its drawing way too much cpu for what its doing | 13:01 |
| Wizzup | back late rtoday | 13:07 |
| buZz | ciao | 13:15 |
| uvos__ | buZz: sphone works just fine on chimeara incl sms | 13:25 |
| uvos__ | its just that sphone and comversations with sms are not compatabil | 13:25 |
| uvos__ | but this istent a change that came with chimeara | 13:26 |
| buZz | just fine = just as poorly as on beowulf? | 13:26 |
| uvos__ | sure not change | 13:27 |
| uvos__ | so its just as unfinished | 13:28 |
| buZz | ah, so there's a plan to finish it? | 13:28 |
| uvos__ | sure | 13:50 |
| uvos__ | well atm it looks like it will just be forked (wich means i will stop working on it - at least for leste purposes) | 13:51 |
| bencoh | oh? | 13:54 |
| Wizzup | uvos__: so the way I see it there are a few things that conflict. (1) is that you said using voicecall-manager was 'unacceptable' from an architectural pov, whereas for maemo leste it makes a lot of sense to share things with sailfish. I can rename comm-telepathy to comm-sfos-voicecallmanager is that somehow solves the problem. (2) We're trying to make a free phone os like maemo, and your UX ideas | 15:47 |
| Wizzup | don't seem particularly compatible - we want integrate things that look and work (to some extend) like maemo, you want the dialer to be the main window with no obvious recent calls like in maemo. | 15:47 |
| Wizzup | My thought was that we could have all this maemo work be contained in modules: one that interfaces with tp through voicecall-manager, one gtk module that has more rtcom integration and separates out the dialer | 15:48 |
| uvos__ | eh 2 i dont really care about | 15:48 |
| uvos__ | since sphone allready has a way to swich what window is the "first" | 15:48 |
| Wizzup | but you've repeatedly opposed it, it seems, so I don't know how to deal with it, for example, how do I get others to check out or try the work? there's no way to build it for the repo | 15:48 |
| uvos__ | (hint its just what you pass to c in the .desktop file) | 15:48 |
| uvos__ | *-c | 15:48 |
| Wizzup | so it's not that I -want- to fork sphone, but I want to make it like maemo, and I don't really see a way out of this if you're not ok with optional modules with extra dependencies | 15:49 |
| uvos__ | so sure make recents the first window, ill just change it back locally | 15:49 |
| Wizzup | like, I am very happy to accomodate requests, make things modular, make it sensible, but I spent over a week on the tp stuff (mostly non stop) and I think it makes a lot of sense for *maemo* to use sfos code, at least in this case | 15:50 |
| uvos__ | im not against using sfos code, im against having yet another deamon doing the same thing | 15:51 |
| uvos__ | and im not against having jet antoher deamon as a stopgap either | 15:51 |
| Wizzup | hmm ok, maybe I misunderstood then | 15:51 |
| uvos__ | im also agaisnt integrating more rtcom dialogs | 15:51 |
| uvos__ | beacuse i want to port to qt | 15:51 |
| uvos__ | and this would get in the way | 15:52 |
| Wizzup | as in, please don't read this as me not liking criticism on a pr, I'm happy to put in a lot of time and make it more to your wishes, but I don't see a big architectural problem with sphone having a module to interface with voicecall-manager, since I see sphone as 'the phone interface for maemo' with is pretty generic | 15:52 |
| Wizzup | and I understand you see that part differently (re: architecture) | 15:52 |
| Wizzup | well, how do you suggest we proceed? I can fix up the PR, maybe rename the module, and see if I can make some mock up gtk module with rtcom lib in it (just to play around) | 15:53 |
| uvos__ | Wizzup: i understand you point to, you want it to work like freemantle as soon as possible, i would rather it take longer if that means cleaner code | 15:53 |
| uvos__ | or cleaner arch more than code | 15:53 |
| uvos__ | anyhow | 15:53 |
| Wizzup | (btw I have a lot of ideas/thoughts on qt, but it is currently extra work to go for it now) | 15:54 |
| uvos__ | Wizzup: sure ill merge the module if you clean it up (and maybe sip works?) as a stopgap (that ok ill replace it myself but please help me with tp then) | 15:54 |
| Wizzup | I'm glad we found some understanding and I'm sorry if I'm pushy. | 15:54 |
| Wizzup | so I'll: (1) clean up the PR, maybe rename it if you want to sfos-voicecallmgr instead of comm-telepathy (2) see if I can make SIP work at least audio routing wise | 15:55 |
| Wizzup | at that point we'll probably have to collaborate on sip addresses | 15:55 |
| Wizzup | and independently I can at least try to make a gtk module with the rtcom widget in it, see how it works | 15:55 |
| uvos__ | Wizzup: sure sounds good | 15:56 |
| Wizzup | btw: the current state of sip is that it can get incoming calls, answer them, gstreamer says it sets up audio, but I don't see the audio in pulseaudio | 15:56 |
| Wizzup | so there's something finnicky there, but the other parts seem to work | 15:56 |
| uvos__ | Wizzup: ok hmm, no idea on that front | 15:56 |
| Wizzup | yeah, I'll dive into it a bit later | 15:57 |
| Wizzup | ok, cool | 15:57 |
| * Wizzup is less stressed now | 15:57 | |
| Wizzup | time for a coffee :) | 15:57 |
| uvos__ | oh and can you see the inline comments on gh now? | 15:58 |
| uvos__ | or shal i paste them somewhere | 15:58 |
| Wizzup | I thought that maybe my browser was not wide enough to see them, but not really, the way I understand the gh comments work: (1) I get emails about each one of them (2) they show up as 'unresolved questions' and (3) there is something interwoven in the code view that shows the comments | 15:59 |
| Wizzup | for some reason I don't see anything besides the two messages in the main view of the pr | 15:59 |
| uvos__ | wierd | 15:59 |
| Wizzup | https://wizzup.org/wip.png | 16:01 |
| Wizzup | (not sure why the bottom is black, but there's no chat there either) | 16:01 |
| Wizzup | Is it maybe somehow saved in your browser but not submitted? | 16:01 |
| uvos__ | im on a different device right now | 16:02 |
| Wizzup | ok, no rush | 16:02 |
| uvos__ | maybe i have to make the comments public somehow | 16:02 |
| uvos__ | i must be missing something | 16:02 |
| Wizzup | I know what to do mostly anyway, at least for rev 1 :) | 16:02 |
| uvos__ | instead of just commenting i started a "review" and apreantly it wont show for others (with no indication that it is so) untill i submitt the review | 16:04 |
| uvos__ | TIL | 16:04 |
| uvos__ | Wizzup: ^^ should show now | 16:04 |
| Wizzup | ty! | 16:08 |
| rafael2k | a screen cap of the just now updated pinhole camera app: http://abradig.org.br/maemo-crazyness/pinhole-working/screen-cap-1.jpg | 19:03 |
| rafael2k | a couple of pictures actually taken from pinhole: http://abradig.org.br/maemo-crazyness/pinhole-working/ | 19:04 |
| rafael2k | totally out-of-focus... as AF is still being wired up | 19:07 |
| sicelo | but this is really nice. kudos! | 19:08 |
| rafael2k | better than nothing! | 19:10 |
| rafael2k | : )) | 19:10 |
| rafael2k | the app is pretty cool indeed, it already has a gallery to see the photos | 19:10 |
| Wizzup | nice!! | 19:11 |
| sicelo | we don't have any other device that can take pics in Leste ... so this is amazing | 19:11 |
| rafael2k | how far is the N900 from having the camera supported? | 19:11 |
| sicelo | far. no one has looked at it in a long time | 19:12 |
| sicelo | i hope to ... but there are other, more pressing issues i want to tackle first | 19:12 |
| rafael2k | as soon as we have PinePhone Pro support, we'll have a second phone with cameras support | 19:14 |
| sicelo | do you have access to a Pro? | 19:24 |
| sicelo | nokia-n900:/usr/lib/ofono/test$ ./send-ussd *557# | 19:24 |
| sicelo | State: idle | 19:24 |
| sicelo | USSD: Credit: E0.00. Data: 500.00MB. Carry Over 287.13MB. | 19:24 |
| sicelo | why i still love N900 ... we depend on USSD in these parts | 19:24 |
| bencoh | oh, that thing works? neat | 19:31 |
| sicelo | yeah. without working USSD, it gets difficult to use the SIM | 19:36 |
| Wizzup | does it not work at all, or do we have an idea of what the problems are? | 19:38 |
| sicelo | on droid 4? maybe just needs porting | 19:40 |
| rafael2k | sicelo, no | 19:41 |
| rafael2k | I dont have this send-ussd | 19:43 |
| rafael2k | which package it is? In theory we should have ussd supported in the PinePhone, but without UI | 19:44 |
| sicelo | that sucks then (@Pro) ... would definitely be nice to support it | 19:45 |
| sicelo | maybe our community needs someone with a OnePlus 6/6T too ... these devices are getting popular among devs, and if we support them, we probably get more hands | 19:45 |
| sicelo | rafael2k: ofono-scripts ... i know ussd works on pp, at least with modemmanager | 19:46 |
| rafael2k | ofono-scripts is an empty package here | 19:48 |
| rafael2k | pkg -S ofono-scripts | 19:49 |
| rafael2k | ofono-scripts: /usr/share/doc/ofono-scripts/changelog.Debian.gz | 19:49 |
| rafael2k | ofono-scripts: /usr/share/doc/ofono-scripts/changelog.gz | 19:49 |
| rafael2k | ofono-scripts: /usr/share/doc/ofono-scripts | 19:49 |
| rafael2k | ofono-scripts: /usr/share/doc/ofono-scripts/copyright | 19:49 |
| rafael2k | but I'm sure it works, yes | 19:49 |
| rafael2k | I wish to have time to understand ofono enough to be able to integrate it to https://github.com/mhogomchungu/ussd-gui | 19:50 |
| sicelo | what's `pkg` now? debian? | 19:50 |
| Wizzup | dpkg | 19:52 |
| Wizzup | probably | 19:52 |
| rafael2k | dpkg | 19:52 |
| rafael2k | dpkg | 19:52 |
| sicelo | https://packages.debian.org/bullseye/all/ofono-scripts/filelist | 19:53 |
| sicelo | no idea why yours is empty ... as you can see, it contains lots of files in debian | 19:53 |
| Wizzup | rafael2k: try dpkg -L ? | 19:54 |
| Wizzup | or is -S the same? | 19:54 |
| Wizzup | it contains a lot on my d4 | 19:54 |
| Wizzup | yeah, no, use dpkg -L | 19:54 |
| sicelo | no, -S is for finding out what package provided the file provided in arguments | 19:54 |
| rafael2k | my bad | 20:04 |
| rafael2k | /usr/share/ofono/scripts/ | 20:04 |
| rafael2k | they are all there | 20:04 |
| Wizzup | btw, with xrandr I have d4 hdmi mirror working quite well with my capture device | 20:04 |
| rafael2k | mixed up -L and -S | 20:04 |
| Wizzup | I wonder if we ought to make that mode default | 20:04 |
| Wizzup | shouldn't use any pm when cable is not plugged in | 20:05 |
| Wizzup | I'd imagine | 20:05 |
| rafael2k | ussd works indeed | 20:06 |
| rafael2k | State: idle | 20:10 |
| rafael2k | USSD: Баланс:21,50р | 20:10 |
| Wizzup | on d4 I get: | 20:11 |
| Wizzup | dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.ofono.SupplementaryServices" doesn't exist | 20:11 |
| sicelo | rafael2k: yay :-) | 20:17 |
| rafael2k | ussd-gui compiles out-of-box! | 20:17 |
| sicelo | Wizzup: on another topic ... in future kernels, might be good to consider this, https://docs.kernel.org/next/admin-guide/mm/multigen_lru.html | 20:18 |
| sicelo | rafael2k: i don't know if ussd would be accepted into sphone, but i think it's a much better fit in a phone application | 20:18 |
| Wizzup | sicelo: sounds good, I think rafael2k and uvos are our kernel guys atm, for pinephone and mapphone/n900 respectively | 20:20 |
| Wizzup | as in, it might make sense to ask them | 20:20 |
| Wizzup | and really, ideally we eventually try to have one kernel pkg. | 20:20 |
| Wizzup | but yeah | 20:20 |
| Wizzup | :D | 20:20 |
| sicelo | rafael2k: does that application work with ofono btw? i see references to gammu | 20:21 |
| uvos | sure sphone should do ussd | 20:22 |
| Wizzup | ofono on d4 doesn't implement ussd yet I believe | 20:22 |
| uvos | one problem i foresee is that i would have a hard time testing it | 20:22 |
| uvos | since my carrier dosent have any codes | 20:22 |
| rafael2k | sicelo, it uses gammu / AT over serial.. | 20:23 |
| sicelo | Wizzup: heh, i don't think we can have one kernel for arm32 and arm64, unless i'm mistaken | 20:23 |
| uvos | sicelo: sure | 20:23 |
| rafael2k | https://docs.kernel.org/next/admin-guide/mm/multigen_lru.html this is good stuff | 20:23 |
| uvos | one tree | 20:23 |
| uvos | rafael2k: ussd over at is mostly useless | 20:23 |
| uvos | since not all phones have at interfaces | 20:24 |
| uvos | we have to use ofono | 20:24 |
| sicelo | rafael2k: yes. i'm running it on my N900 with linux 6.2-rc6. can't say i see magic, but seems somewhat useful for sure. | 20:25 |
| rafael2k | uvos, ussd over at works pretty well also, why it is useless (not that we should use it... but it works) | 20:26 |
| uvos | rafael2k: sure it works.. on the pinephone. my point is we cant rely on ussd working over at, or there even beeng a at interface at all | 20:27 |
| Wizzup | sicelo: one kernel tree I mean :) | 20:27 |
| rafael2k | sicelo, I can jump to 6.2 soon in the PP... but then I'll be on my own, as Mobian seems to like 6.1. but no problem at all, as they just pick the patches from megi and apply | 20:27 |
| Wizzup | uvos: my dutch carrier seems to have ussd codes, although I assumed it didn't | 20:27 |
| rafael2k | ahhmmmm | 20:27 |
| sicelo | Wizzup: understood :-) | 20:27 |
| Wizzup | uvos: which is your carrier? | 20:27 |
| uvos | some sublet of telefonica | 20:28 |
| sicelo | rafael2k: i guess there's no rush to switch kernels. i have just recently got into the habit of testing every new rc to catch N900 regressions early, since it gets supper annoying when they're discovered a long time later | 20:28 |
| rafael2k | with list-modems script, check in "ServiceNumbers = " | 20:28 |
| rafael2k | sicelo, got it | 20:28 |
| rafael2k | What I'm doing is backporting stuff from 6.2 to 6.1 | 20:29 |
| rafael2k | like the sun6i-csi, ov5640 drivers | 20:29 |
| rafael2k | and keep with the "Mobian" fork (which is not really from Mobian as I realized they just rebase Megi's kernel fork work) | 20:30 |
| rafael2k | but I like that there are many people using, so I'm not alone in the boat | 20:30 |
| Wizzup | rafael2k: hm, I am not sure if those service numbers are correct, at least on my d4 | 20:31 |
| Wizzup | I think mine does ussd, but they are not listed there | 20:31 |
| Wizzup | but again - d3 | 20:31 |
| Wizzup | d4* | 20:31 |
| rafael2k | I found the USSD to check balance there... but of course the carrier could fuck up that field and put garbage / outdated info | 20:31 |
| rafael2k | but they don't need to be listed there | 20:32 |
| rafael2k | try this: *100# | 20:32 |
| rafael2k | or this: *123# | 20:32 |
| Wizzup | http://dpaste.com/CD6R7ABUA | 20:33 |
| sicelo | there are no universal ussd codes afaik | 20:33 |
| Wizzup | point is that d4 ofono does not advertise ussd support | 20:33 |
| Wizzup | we might need to improve drivers/motorolamodem for that | 20:34 |
| Wizzup | ussd.c in qmimodem isn't that big either | 20:35 |
| Wizzup | probably freemangordon or tmlind have a better idea on this | 20:36 |
| rafael2k | *101# also works with MTS | 20:37 |
| Wizzup | might be worth to file two bugs, one for a gui for it, one for d4 support | 20:37 |
| uvos | Wizzup: some dead simple additions to help you remove_filter_from_datapipe | 20:51 |
| uvos | upp | 20:51 |
| uvos | s | 20:51 |
| uvos | https://github.com/maemo-leste/sphone/commits/master | 20:51 |
| Wizzup | thanks! I'll take a look a little later tonight (some work stuff atm) | 21:01 |
| Wizzup | hi | 21:03 |
| soldan | hi people, me again, i finally installed maemo leste on my n900, nice OS! | 21:04 |
| soldan | what mail-cliente do you recommend me? sorry, my english is awful, | 21:04 |
| Wizzup | modest | 21:08 |
| Wizzup | the same as on the original maemo | 21:08 |
| soldan | thnk | 21:09 |
| Wizzup | which image did you choose? | 21:11 |
| Wizzup | (date/version) | 21:11 |
| soldan | i tried this https://maedevu.maemo.org/images/n900/20221225/maemo-leste-1.0-armhf-n900-20221225.img.xz | 21:12 |
| soldan | wich web browser do you recommend? | 21:13 |
| Wizzup | this is a harder question on the n900 | 21:14 |
| soldan | ok, and mail client? i search for "modest" in apt ? | 21:14 |
| Wizzup | sudo apt-get install modest | 21:14 |
| soldan | great | 21:14 |
| Wizzup | in our to-be-released new image it is installed by default | 21:14 |
| soldan | and a contacts apps that i can sync with a server? is there any? | 21:15 |
| Wizzup | https://leste.maemo.org/Contacts | 21:15 |
| Wizzup | https://leste.maemo.org/Sync | 21:15 |
| Wizzup | those pages should help | 21:15 |
| soldan | thnk, im gonna check it | 21:18 |
| soldan | when im install something with apt or even with the application manager, it doesnt add a launcher, i have to launch the app from the terminal, it is normal? | 21:33 |
| Wizzup | if it is a debian package, it appears in the debian launcher sub menu | 21:34 |
| Wizzup | if it is a maemo leste package, it should appear | 21:34 |
| soldan | ohh, ok! | 21:34 |
| Wizzup | maybe some trigger doesn't work and they will show on restart | 21:34 |
| Wizzup | but normally it should appear | 21:34 |
| uvos | if it isent a leste package it should still appear | 22:01 |
| uvos | but in the debian menu | 22:01 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
