| diejuse | can I decrease the dpi of maemo theme? | 01:12 |
|---|---|---|
| diejuse | found: QT_SCALE_FACTOR | 02:24 |
| uvos | diejuse: you cant, besides qt stuff everything is gtk2, gtk2 cant be scaled at all. The only thing you can scale is the font via dpi settigs, but because nokia implemented this the wrong way that dosent really work either. | 10:29 |
| diejuse | uvos I'm a little confused about what QT, GTK2 or GTK3 is. I managed to scale the "CountDown Timer" numbers but I don't know if it is QT or GTK2. | 14:46 |
| freemangordon | it is qt | 14:48 |
| freemangordon | afaik | 14:48 |
| diejuse | And you (the members of the Maemo Leste project), do you make applications for Maemo in QT or GTK? | 15:06 |
| buZz | i think the 'original' maemo applications are all QT | 15:19 |
| buZz | but either works, they both have 'themes' to make them 'maemo looks' | 15:20 |
| buZz | and the maemo windowmanager understand those themes | 15:20 |
| inky | i wonder if old android devices also concerned by old unusable openssl versions. | 15:24 |
| inky | do they use openssl in android? | 15:25 |
| inky | if so then they also cannot connect to modern websites? | 15:25 |
| inky | s/concerned/affected/ | 15:44 |
| buZz | inky: 'being old openssl' doesnt really prevent many ssl usage? | 15:45 |
| buZz | as long as the certificates are up to date | 15:45 |
| buZz | and if it supports the actually used cypher | 15:45 |
| buZz | certificates up to date -and- local clock configured correctly ;) | 15:45 |
| diejuse | inky I installed svkbd virtual keyboard but when I run it it opens in full screen and below the app I want to write in. And if I run it as a dock it does appear below but the keys are not visible. | 15:56 |
| diejuse | I need a keyboard that allows me to edit content directly in the application I am using. Because when I create a video using Maemo on Android via proot I would like to not have to take out the Android keyboard to edit text. | 15:59 |
| buZz | diejuse: hook up external USB keyboard? :D | 16:01 |
| buZz | hihi | 16:01 |
| diejuse | nooo! I have a very high empathy with the majority user of an Android smartphone and I want to show that majority user that Maemo Leste is very cool. It would be very good for this fantastic OS. :P | 16:02 |
| diejuse | the majority user never uses an external physical keyboard. | 16:03 |
| Wizzup | maemo keyboard allows editing in gtk2 | 16:06 |
| Wizzup | not yet in qt5 | 16:06 |
| diejuse | I want to get something very simple. Open osso-xterm, run nano, edit nano with Maemo Leste keyboard. Right now that is not possible and it should be possible. | 16:07 |
| diejuse | I want to be able to go to text line 34 (for example) and edit that line with the virtual keyboard | 16:09 |
| Wizzup | right, missing arrow keys. | 16:12 |
| Wizzup | you can add them on osso-xterm via gconf but it is not great | 16:12 |
| inky | >certificates up to date -and- local clock configured correctly | 16:12 |
| inky | buzz, really? if i scp certificates from xperia or maemo to jolla it will work? | 16:12 |
| inky | or to n900 | 16:12 |
| buZz | perhaps | 16:12 |
| Wizzup | 15:20 < buZz> i think the 'original' maemo applications are all QT | 16:12 |
| Wizzup | they are not | 16:12 |
| Wizzup | they are mostly gtk2 | 16:13 |
| Wizzup | inky: this is mostly a sw support thing wrt certs | 16:13 |
| inky | so certs won't help right? | 16:13 |
| buZz | oh! ok | 16:13 |
| inky | it's the version of openssl. | 16:14 |
| inky | well if you configure web server you can tell it which encryption to accept. lets say if web server only accepts tls 1.3 or 1.2 i believe n900 or even jolla won't support it. | 16:14 |
| diejuse | Wizzup Keep in mind to try to solve it when you can so that it is possible to do what I said please... | 16:16 |
| inky | diejuse, i am sorry svkbd doesn't work for you. i myself didn't try it in maemo. | 16:16 |
| inky | i use it in sxmo (sort of dwm) in postmarketos. | 16:16 |
| Wizzup | diejuse there is qterminal | 16:19 |
| Wizzup | it has qt keyboard iirc | 16:19 |
| sicelo | buZz: original maemo applications were gtk, i.e. ootb, everything is gtk. then qt came along (when nokia owned it?) and many newer applications started using that (partly because it was easier to support them on symbian too) | 16:42 |
| sicelo | diejeuse can, as a temporary hack, add arrows on xterm's bottom bar. i mentioned this before | 16:43 |
| sicelo | ah indeed @qterminal ... is it ported to leste? | 16:44 |
| Wizzup | I think it is in debian | 16:50 |
| arno11 | hi guys, i used n900 with 6.1.76 during 5 days with no reboot to check how stable it is and that's fine: ram/swap usage is ok, no crash/freeze. | 18:58 |
| uvos | Wizzup: please dpkg -s sphone your sphone compiled with vcm | 19:01 |
| uvos | "[15:25] <inky> do they use openssl in android?" yes they do | 19:03 |
| uvos | less of a problem on android however since if you care enough you can build modern (enough) android for any device really | 19:04 |
| uvos | arno11: great | 19:08 |
| uvos | Wizzup: maybe you can move it to stable | 19:09 |
| uvos | probubly a good idea since this is presumably the last 6.1.x release we will do | 19:09 |
| arno11 | uvos: any news about cpufreq troubles in newer kernel ? | 19:15 |
| Wizzup | uvos: do I need to upgrade first? and sorry, move what to stable? | 19:35 |
| Wizzup | oh, the kernel | 19:35 |
| Wizzup | uvos: https://bpa.st/NOXA | 19:58 |
| uvos | Wizzup: so this was to find out what to depend on | 20:09 |
| uvos | but it seams your sphone package dosent depend on anything vcm | 20:09 |
| Wizzup | it doesn't, no, I would manage this through hildon-meta or so | 20:15 |
| uvos | Wizzup: thats nice, but you must depend on something during build time | 20:26 |
| uvos | since otherwise the module wont build | 20:27 |
| inky | > less of a problem on android however since if you care enough you can build modern (enough) android for any device really | 21:19 |
| inky | but android (though it can work on mainline) usually uses some other mainline kernel? some android specific their own mainline? | 21:19 |
| uvos | android uses various vendor kernels and blobs but has a realtively high degree of backward and forward compatability | 21:20 |
| inky | so what lineageos uses? vendor kernels? | 21:20 |
| uvos | yes | 21:21 |
| inky | binary? open source kernels? | 21:21 |
| inky | do all vendors provide sources? or all sources? | 21:21 |
| uvos | all western vendors provide sorces | 21:21 |
| inky | aha, so lineage takes those sources and build the kernels. | 21:21 |
| inky | but then, how they build newer kernels for older devices? | 21:22 |
| uvos | yes + various binary blobs that those vendor kernels need | 21:22 |
| uvos | inky: for chineese device that violate gpl they dont | 21:22 |
| inky | do they take drivers from old device kernels and then apply them to new kernels? | 21:22 |
| uvos | no | 21:22 |
| uvos | they just build the ainchent kenrels | 21:23 |
| uvos | with very few exceptions where people forward ported the vendor patches | 21:23 |
| inky | aaah, ancient kernel and over it newer android. | 21:23 |
| uvos | i know only of one sutch device: the atrix 4g | 21:23 |
| inky | so atrix has lineageos now? | 21:24 |
| uvos | it used to | 21:24 |
| inky | i saw somewhere lineageos profile for droid3 or droid4. | 21:24 |
| inky | to build real lineageos. but didn't understand what is it. | 21:24 |
| uvos | lineageos up to the version based on android 7 was officaly on the droid4 | 21:24 |
| uvos | this is new enough (2019) works great | 21:25 |
| uvos | if anyone cared enough you could try and build newer linageos too | 21:25 |
| uvos | but theres no point really since there are better android devices to use than a droid4 | 21:25 |
| uvos | anyhow all of this used the old motorola android kernel with a few patches | 21:26 |
| inky | i see. | 21:28 |
| inky | i learned a lot today. thank you. | 21:28 |
| diejuse | A very interesting conversation. | 21:29 |
| uvos | btw android since android 11 supports running on the mainline kernel | 21:29 |
| uvos | so you could also build modern linageos and pair it with the leste kenrel | 21:29 |
| uvos | only problem: somehow you need powervr blobs compiled against bionic instead of glibc | 21:29 |
| uvos | or no 3d accell | 21:29 |
| uvos | maybe if you ask ti nicely | 21:30 |
| inky | i see. | 21:30 |
| inky | i prefer "real" linux anyway. | 21:30 |
| inky | so old androids also affected by old openssl? they cannot connect right? | 21:30 |
| inky | i think d3 was not able to connect to anything, but i don't remember. with stock android 2. | 21:31 |
| uvos | yes, athlo i dont know how old you have to go | 21:31 |
| uvos | google did support old android version with updates for 4 ish years | 21:31 |
| uvos | sometimes longer | 21:31 |
| inky | i turned on my n900 yesterday. and fcamera is such an amazing software. | 21:32 |
| inky | did anyone try it? | 21:32 |
| inky | i think it replaced default drivers in nokia kernel. | 21:32 |
| inky | and then it is able to shoot raw images. | 21:32 |
| inky | it would be great to make it run on leste, if only on n900. | 21:33 |
| inky | but i am not sure that just open source drivers are enough. | 21:33 |
| inky | maybe there is some firmware. | 21:33 |
| bencoh | fcamera *is* awesome indeed, considering when it was written | 21:34 |
| inky | i think martijn braam's megapixels also work on n900 under postmarketos. or maybe it was millipixels? he has another software too. but i don't remember what was the difference. | 21:39 |
| inky | megapixels on pinephone takes very beautiful pictures. | 21:40 |
| uvos | in theroy everything is there to shoot raw pictures with n900 | 21:58 |
| uvos | but its not integrated | 21:58 |
| uvos | and you will get really raw images | 21:58 |
| uvos | not colour calibration at all | 21:58 |
| inky | fcamera generates dng files. | 21:59 |
| uvos | or any other processing | 21:59 |
| inky | probably you mena more raw. | 21:59 |
| uvos | inky: sure but those raw files are mutch less raw than you get from the iss interface | 21:59 |
| Wizzup | uvos: oh, let me see | 22:52 |
| Wizzup | uvos: strange, I think the current 0.9.0 already had the module built, did it not? | 22:53 |
| Wizzup | I guess not | 22:54 |
| uvos | i dont see how | 22:54 |
| uvos | its not like the qtvoicecall cmake file will be found on ci | 22:54 |
| Wizzup | ok, I remember | 22:54 |
| Wizzup | I built it on my d4 myself | 22:54 |
| Wizzup | and there I have the packages installed | 22:54 |
| uvos | right | 22:54 |
| uvos | which packages is the point | 22:54 |
| Wizzup | I understand now, let me see | 22:54 |
| Wizzup | I think voicecall-qt5 also contains the build deps | 22:55 |
| Wizzup | that -should- be all you need | 22:56 |
| uvos | ok so Build-Depends: voicecall-qt5 Suggests: voicecall-qt5 ? | 22:56 |
| uvos | nothing else | 22:56 |
| uvos | sphone is now: | 22:57 |
| uvos | Depends: libc6, libgdk-pixbuf-2.0-0, libglib2.0-0, libgtk2.0-0, libhildon1, libnotify4, libpango-1.0-0 | 22:57 |
| uvos | Recommends: ofono, libebook-1.2-20, libebook-contacts-1.2-3, libedataserver-1.2-25, libgstreamer1.0-0, libpulse0, librtcom-eventlogger1 | 22:57 |
| uvos | Suggests: libnotify4, libosso-abook, libprofile0, voicecall-qt5 | 22:57 |
| Wizzup | I think that should work | 22:58 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!