| Wizzup | tmlind: uvos: looks like this xt898 'rare prototype' that I ordered on ebay is a photon q with sim slot | 07:07 |
|---|---|---|
| Wizzup | so not omap | 07:07 |
| diejuse | @arno Launching Android applications (camera, calls, sms, settings, battery level) from Maemo Leste is now fixed (should work on all smartphones). I have also made other improvements such as fixing "sudo" and being able to use a non-root "user" user. And I have added the changes you researched to make dummy networks work. Everything is already | 11:51 |
| diejuse | uploaded in a new version (v100 -> v110 https://github.com/diejuse/proot_MaemoLeste_on_Android/blob/main/UPDATES.md) | 11:51 |
| diejuse | @arno11 | 11:53 |
| arno11 | diejuse: very nice ! | 13:03 |
| arno11 | btw what were the main issues/errors with a more recent img ? | 13:04 |
| diejuse | the way to call android apps was not the most correct due to LD_PRELOAD | 13:06 |
| diejuse | You must also enable the advanced draw over other apps permission in Termux. | 13:07 |
| diejuse | advanced permission: "draw over other apps" | 13:07 |
| diejuse | I also had to make changes to prootMaemo.sh so that it works on all Android versions from 8 onwards. | 13:08 |
| arno11 | ok, btw on my redmi, i don't see the 'draw over other apps' | 13:10 |
| diejuse | go to Android settings -> search Termux -> It should be at the bottom | 13:11 |
| arno11 | already done but nothing related to that option | 13:12 |
| diejuse | screenshoot | 13:12 |
| arno11 | let me check again | 13:12 |
| arno11 | seems ok now, options were a bit different with 2 options to activate | 13:15 |
| arno11 | weird, can't show them anymore lol, but it works | 13:15 |
| diejuse | so camera works? | 13:16 |
| arno11 | yes :) | 13:16 |
| diejuse | nice | 13:16 |
| diejuse | battery level widget? | 13:17 |
| arno11 | how to use it ? | 13:18 |
| diejuse | click over it | 13:18 |
| arno11 | i mean, i don't have it | 13:19 |
| diejuse | The two versions I uploaded had the battery level desktop-cmd-exec widget on the desktop home. | 13:21 |
| diejuse | three icons and the widget | 13:21 |
| arno11 | ok, i still use the old version :P | 13:21 |
| diejuse | You can easily maintain both, for example: mv ~/leste ~/leste_v100 and install the new. | 13:22 |
| arno11 | ok, sorry, i'm busy ATM, i'll have look later | 13:24 |
| arno11 | ttyl | 13:24 |
| diejuse | sure | 13:24 |
| uvos__ | Wizzup: an acctual photon q that someone did the sim slot mod on or something very simmilar but by motorola (ie a gsm photon q)? | 14:08 |
| uvos__ | Wizzup: did you read the description on conversations behavior? is all that currently as espected? | 14:08 |
| sicelo | diejuse: btw you're basing off an old arm64 image ... so you need to first to a big upgrade (or even dist-upgrade)? | 14:24 |
| sicelo | 2020 ...i guess yes, you need dist-upgrade | 14:24 |
| sicelo | Wizzup: maybe we need newer arm64 images? i can't recall if they were already asked for, but i might have a need too | 14:33 |
| sicelo | btw, with image builder .. is there a correct way to 'exit' at the end? so all the mounts are cleanly unmounted | 15:26 |
| Wizzup | uvos: actual photon q pre-release from motorola | 15:29 |
| Wizzup | so yes gsm photon q | 15:29 |
| Wizzup | sicelo: hm, yeah, let me check what the tsatus of those is | 15:29 |
| Wizzup | sicelo: it should with just ^D or exit | 15:30 |
| Wizzup | sicelo: I think mounts should always get cleanly unmounted now, if that's not the case let me know I'll try to fix it | 15:37 |
| Wizzup | the mounts not unmounting cleanly has been a real issue | 15:38 |
| uvos__ | Wizzup: thats still kinda neat, even though you can create allmost to same thing by moding a phonon q | 15:50 |
| Wizzup | yeah, it has no mainline support though I think | 15:51 |
| Wizzup | I did send someone one, I think or two years ago, but they didn't do much with it iirc | 15:51 |
| uvos__ | yeah also phonon qs are notoriously unreliable | 15:52 |
| uvos__ | who knows how long this one will work for | 15:52 |
| Wizzup | there's one more on ebay btw | 15:53 |
| Wizzup | I don't think I'm interested in it | 15:53 |
| diejuse | sicelo I don't think you have read that it is a Chimaera image... The 2020 version that you mentioned is the one that I started working with more than two years ago and is what the current version is based on, obviously updated. I imagine you are joking when you tell me to run apt dist-upgrade. | 16:06 |
| sicelo | i clicked the link you gave us .. https://github.com/diejuse/proot_MaemoLeste_on_Android/blob/main/UPDATES.md ... it refers to 2020 image | 16:07 |
| sicelo | and no, i haven't run this on my device. it was a question | 16:07 |
| diejuse | "The base version (Chimaera Devuan). Based on ARM64 generic Raspberry Pi 3 https://maedevu.maemo.org/images/arm64-generic/20200114/" | 16:07 |
| diejuse | It is the base (proot) version (CHIMAERA). And it was based on 2020 image. | 16:08 |
| sicelo | so what's the problem? | 16:08 |
| diejuse | I don't know. What is? | 16:08 |
| sicelo | alright | 16:09 |
| diejuse | I mean it's obviously updated. | 16:09 |
| sicelo | ok. | 16:09 |
| diejuse | The reason that everything I do is based on that old image is that I have tried others and they have given me more problems that I have not been able to solve. So I always start from that image and go from ASCII to Beowulf and then to Chimaera. | 16:12 |
| sicelo | building image is taking forever, gawd | 16:23 |
| Wizzup | sicelo: are you trying arm64? | 16:33 |
| sicelo | no, n900, just to get used to the tool | 16:34 |
| Wizzup | ok | 16:41 |
| Wizzup | https://phoenix.maemo.org/view/Images/job/leste-image-arm64generic/4/console | 16:42 |
| Wizzup | I don't expect this to pass, but let's see | 16:42 |
| sicelo | don't jinx it :p | 16:43 |
| Wizzup | 16:24 < sicelo> building image is taking forever, gawd | 16:45 |
| Wizzup | it's probably limited by network and i/o | 16:45 |
| sicelo | probably i/o .. i'm on plain old HDD, that's not in the best condition tbh. network that i'm on is reasonably fast (>30Mbps) | 16:46 |
| sicelo | also probably just apt/dpkg. i think i see why alpine folk love their apk thing. | 16:48 |
| Wizzup | yeah apk is fast, but I/O is still I/O | 16:49 |
| Wizzup | seems to me like old HDD is the likely issue | 16:50 |
| uvos__ | apt, dpkg is really horrendously slow | 16:53 |
| uvos__ | comeing from archlinxes packman | 16:54 |
| Wizzup | coming from gentoo/portage, apt is _fast_ :D | 16:59 |
| uvos__ | yeah well portage at least has a good excuse :P | 17:02 |
| Wizzup | yup | 17:03 |
| sicelo | i'm mentioning this because i build images for pmos regularly. it takes nowhere as much as this :p | 17:27 |
| sicelo | ahah, portage - i never tried gentoo :-) | 17:27 |
| sicelo | Wizzup: and the arm64 build failed. | 17:40 |
| sicelo | The following packages have unmet dependencies: | 17:40 |
| sicelo | iphb-dkms : Depends: linux-headers but it is not installable or | 17:40 |
| sicelo | linux-headers-amd64 but it is not installable | 17:40 |
| sicelo | maybe that's part of the cause? mmm, why amd64 | 17:40 |
| Wizzup | sicelo: ok, always this darn iphb-dkms | 17:43 |
| Wizzup | we just need to figure out the name of linux headers on arm64 | 17:43 |
| Wizzup | seems to be linux-headers-arm64 | 17:45 |
| Wizzup | we could add that to iphdb | 17:58 |
| Wizzup | hah it is in there | 17:58 |
| Wizzup | not sure if I ever built it for devel | 17:59 |
| Wizzup | yeah ok let me fix this | 17:59 |
| Wizzup | freemangordon: looks like you didn't sync/update master for iphd-dkms | 18:01 |
| Wizzup | that's why this change was not included | 18:01 |
| Wizzup | I'll just forcepush master | 18:02 |
| Wizzup | sicelo: trying again (arm64 generic image) | 18:14 |
| sicelo | yay! i think it'll be successful | 18:14 |
| Wizzup | sicelo: it's definitely getting further along | 19:09 |
| arno11 | diejuse: the battery cmd-exec widget is ok btw | 19:31 |
| arno11 | so now i wonder what is not working in proot... | 19:34 |
| arno11 | Wizzup: sicelo: uvos: freemangordon: now i'm running my N900 24h a day, -devel 6.1.76 using boost @720 (sometimes @805-850), light transitions, absolutely no troubles, modem is always ok, sms, sip and fb through conversations work fine, calls through sphone are ok, video and streaming ok, audio ok, fmtx ok and almost all other stuff. looks like a great beta :) | 19:49 |
| sicelo | 👌 | 19:49 |
| Wizzup | great, calls with voicecallmgr/telepathy? | 19:49 |
| arno11 | that's ok | 19:49 |
| arno11 | a bit slower now, we need a qt5 boost imo | 19:50 |
| arno11 | i mean sphone and conversations are a bit slower to start | 19:50 |
| Wizzup | both start on boot | 19:51 |
| arno11 | yes but the ui is slower to start | 19:51 |
| arno11 | example: before voicecallmgr/telepathy changes, sphone took around 1 sec to start, now it's around 3-5 sec (not a major issue ofc) | 19:55 |
| Wizzup | hm | 19:56 |
| arno11 | even in proot, sphone takes around 3 sec to start | 19:56 |
| sicelo | arno11: what battery cmd-exec widget btw | 19:56 |
| arno11 | conversations 3 sec in proot | 19:56 |
| arno11 | sicelo: /diejuse_scripts/android_batterylevel.sh | 19:58 |
| uvos | theres something wrong if sphone takes any amount of time to show up | 19:58 |
| sicelo | ok | 19:58 |
| uvos | on d4 is so instant it bugs out the applicaiton starup effect | 19:58 |
| uvos | since all it dose it present a window it as loaded already | 19:59 |
| Wizzup | doesn't h-d launch the .desktop file? | 20:00 |
| Wizzup | and then sphone that is launched tells the other sphone to start? | 20:00 |
| uvos | sure yeah | 20:00 |
| uvos | point is this is really fast | 20:00 |
| diejuse | arno11 OMP and lockscreen | 20:00 |
| Wizzup | well, if sphone takes a while to start then this can take a while | 20:00 |
| uvos | well it should not it dosent load any modules | 20:01 |
| uvos | and the core sphone binary is tiny | 20:01 |
| Wizzup | right, trying this from terminal might make sense | 20:01 |
| uvos | btw why is the name of the vcm sphone backend so insane? | 20:02 |
| uvos | is there a technical reason for that? | 20:02 |
| arno11 | starting sphone dial from command line is slow as well | 20:04 |
| arno11 | diejuse: yes indeed | 20:06 |
| uvos | arno11: could you "mv /usr/share/sphone/sphone.ini.d/00-maemo-voicecallmanager.ini /usr/share/sphone/" | 20:07 |
| uvos | then "killall sphone" | 20:07 |
| uvos | then click on the sphone desktop file | 20:07 |
| arno11 | ok let's go | 20:07 |
| uvos | then start sphone from the cmd line | 20:07 |
| uvos | is it still slow? | 20:07 |
| arno11 | uvos: :) :) | 20:09 |
| arno11 | it works fine now from the desktop | 20:10 |
| uvos | ok | 20:11 |
| arno11 | takes less than a sec now | 20:11 |
| arno11 | thx | 20:11 |
| uvos | wait a moment | 20:11 |
| uvos | ok so no go edit /usr/share/sphone/sphone.ini | 20:12 |
| uvos | and change LoopModule=glibloop to qtloop | 20:12 |
| uvos | and killall sphone | 20:12 |
| uvos | and try again | 20:12 |
| uvos | is it slow again now? | 20:12 |
| uvos | btw if you want to use fast sphone you need to uninstall telepathy-ring | 20:13 |
| uvos | otherwise it wont work | 20:13 |
| arno11 | indeed that's slow again | 20:14 |
| arno11 | (with qtloop i mean) | 20:14 |
| uvos | hmm ok | 20:15 |
| uvos | https://github.com/maemo-leste/sphone/blob/d0dea784e1d809777b03387e1be66837dede4ced/src/modules/qtloop.cpp#L18 must be realy slow | 20:15 |
| uvos | hmm | 20:15 |
| uvos | anyhow you can go back to stock sphone (moved 00-maemo-voicecallmanager.ini), glibloop, to avoid this for now, but you need to uninstall telepathy-ring because it breaks stock sphone | 20:17 |
| uvos | what device is this? | 20:17 |
| uvos | i wonder why starting qt is so slow on your system | 20:17 |
| arno11 | N900 | 20:19 |
| arno11 | but even on my redmi, qt is not fast | 20:21 |
| arno11 | brb | 20:21 |
| uvos | using qtloop is certenly also slower on my d4 | 20:21 |
| uvos | but not 3 seconds slow | 20:21 |
| diejuse | arno11 mmm and volume change notification too | 20:23 |
| sicelo | Wizzup: it failed again | 21:23 |
| sicelo | Setting up hildon-im-fkb (3.9.86+m7) ... | 21:23 |
| sicelo | /var/lib/dpkg/info/hildon-im-fkb.postinst: 4: hildon-im-recache: not found | 21:23 |
| sicelo | dpkg: error processing package hildon-im-fkb (--configure): installed hildon-im-fkb package post-installation script subprocess returned error exit status 127 | 21:23 |
| sicelo | looks like hildon-im-fkb should depend on hildon-input-method, which provides recache | 21:24 |
| sicelo | although i wonder why it would be working fine for other images | 21:24 |
| Wizzup | sicelo: ok, thanks, weird that this doesn't happen for d4 images | 21:38 |
| Wizzup | might be my -meta changes | 21:38 |
| Wizzup | sicelo: well this is a -devel image | 21:38 |
| Wizzup | build | 21:38 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!