| buZz | hmm meh, "battery-charging-blink-full-solid" trigger doesnt turn solid on 'full' | 01:22 |
|---|---|---|
| tmlind | Wizzup: ok pushed out droid4-kexecboot with xt912 support and initramfs offset read dynamically: https://github.com/tmlind/droid4-kexecboot/tree/master/2022-12-05 | 07:21 |
| tmlind | the issue was there's no hd in busybox there, changed to use od instead | 07:22 |
| freemangordon | Wizzup: ugh, isn't that a double-free? https://github.com/maemo-leste/eds-backend-telepathy/blob/b96f28389554f2a1d39d6b8eeef3bd1a66e701fc/src/e-book-backend-tp.c#L2670 | 08:34 |
| tmlind | uvos: maybe try setting razr_xt9xx_data te_support = 1 assuming you merged with the pvr hacks and have 7c72e56fd0a2 ("WIP: Forward port of droid4 stock kernel changes to prevent tearing") | 09:25 |
| tmlind | note the te_type in the v3.0.8 stock kernel is different between xt894 and xt910, so some other changes may be needed | 09:26 |
| uvos__ | tmlind: thanks for the lead | 09:36 |
| uvos__ | ill try that | 09:36 |
| tmlind | ok | 09:38 |
| uvos__ | tmlind: do you happen to come across what the touch buttons are connected to on xt910 in the stock kernel? they arnt on the lcds touch controller so xt910 must have somthing sperate for those | 09:38 |
| tmlind | yeah there's some separate controller, let me check | 09:38 |
| uvos__ | really wierd that they did that, the whole point of touch buttons was that its cheap becaue you can just use the display touch controller | 09:40 |
| tmlind | yeah | 09:41 |
| tmlind | i think it might be the drivers/input/misc/cy8c201xx_core.c in the stock kernel | 09:41 |
| uvos__ | ok ill take a look | 09:41 |
| tmlind | probably takes less power compared to keeping the lcd controller enabled | 09:41 |
| uvos__ | the touch buttons are never active when the display is not in android | 09:42 |
| uvos__ | so idk where that helps | 09:42 |
| tmlind | ok | 09:43 |
| tmlind | might be this one in the mainline kernel Documentation/devicetree/bindings/pinctrl/cypress,cy8c95x0.yaml | 09:44 |
| tmlind | or similar | 09:44 |
| tmlind | drivers/input/touchscreen/cy8ctm*.c | 09:44 |
| tmlind | so the mxt touch screen works fine, right? | 09:45 |
| uvos__ | tmlind: yeah | 09:45 |
| uvos__ | well idk | 09:45 |
| uvos__ | it often dosent resigter touches | 09:46 |
| uvos__ | but that might also be the display | 09:46 |
| uvos__ | it works at least sometimes | 09:46 |
| uvos__ | it seams like the display also hangs often | 09:46 |
| uvos__ | (see video this happens at the beginning) | 09:46 |
| tmlind | ok maybe different firmware | 09:46 |
| tmlind | embedded in the dts | 09:47 |
| uvos__ | maybe or its just the entire device/or display hanging for 1-2 sec | 09:47 |
| tmlind | yeah ok | 09:47 |
| uvos__ | not sure its the mx touch controllers fault | 09:47 |
| tmlind | i'm also seeing the sideways jumping with just dd if=/dev/urandom of=/dev/fb0 | 09:48 |
| tmlind | sideways as in portrait mode | 09:48 |
| uvos__ | ok | 09:48 |
| uvos__ | hblank issues :P | 09:48 |
| tmlind | the timings should be the same, well what is used for timings in the command mode case | 09:49 |
| tmlind | as on xt894 | 09:49 |
| uvos__ | ok, at lesat it looks like hblank not syncing up, could be another cause | 09:50 |
| tmlind | i guess i'll continue on the mz61x bridge stuff when i get a chance | 09:53 |
| tmlind | i mean mz6xx. i need to also figure out why memtester fails on my mz609 while android works happily | 09:54 |
| tmlind | could be some cpcap regulator low level init thingy | 09:54 |
| uvos__ | tmlind: that would be neat. im mutch more excited about leste on mz6xx than xt910 (or mb865) | 09:56 |
| Wizzup | freemangordon: will take a look, I didn't look anymore after this weekend | 10:00 |
| * tmlind bbl tonight | 10:06 | |
| uvos__ | ttyl tmlind | 10:06 |
| Wizzup | freemangordon: looks like it likely is a double free yes | 10:27 |
| Wizzup | freemangordon: I see you pushed already | 10:27 |
| Wizzup | tmlind: thanks, will try the new kexecboot | 10:35 |
| freemangordon | Wizzup: yes | 10:44 |
| Wizzup | ty | 10:48 |
| Wizzup | https://www.phoronix.com/news/SDL-3.0-Drops-Open-GLES-1.0 | 10:55 |
| uvos__ | droppting gles makes so little sense if your not going to drop ogl 1.x too | 11:30 |
| uvos__ | i just dont get it at all | 11:30 |
| uvos__ | and you cant possibly drop ogl 1.x because almost everything is still part of the ogl 3.0 compat spec | 11:32 |
| uvos__ | so unless your willing to drop ogl 3.0 | 11:32 |
| uvos__ | i dont get it | 11:32 |
| Wizzup | freemangordon: btw, when you get back later today, maybe we can talk my qt idea through for menus | 11:50 |
| freemangordon | ok | 11:56 |
| Wizzup | freemangordon: basically https://github.com/maemo-leste/bugtracker/issues/679 | 12:02 |
| Wizzup | uvos__: btw I have these, but none have mbm allow flashing: VRZ_7.7.1-85_MZ617-27_CFC_1FF.xml.zip VRZ_9.8.2OT_127_MZ617_CFC_1FF.xml.zip VRZ_MZ617_1.6.0_279_CFC_1FF.xml.zip | 12:16 |
| uvos__ | Wizzup: yes i downloaded all mz6xx updates | 12:16 |
| uvos__ | none have it | 12:16 |
| uvos__ | only the otg updates have | 12:16 |
| uvos__ | but bearly anyone saved the otg updates | 12:17 |
| Wizzup | hmm | 12:17 |
| Wizzup | do we have any file hashes? | 12:17 |
| uvos__ | i dont think so | 12:17 |
| uvos__ | but can look in my notes later | 12:17 |
| Wizzup | cool, I'm heading out first now anyway | 12:17 |
| uvos__ | i have never seen a otg update at all | 12:17 |
| uvos__ | i only know from xda | 12:17 |
| uvos__ | and someone posted the mz607 file there with the comment that it came from otg | 12:18 |
| freemangordon | Wizzup: hmm, why do we need that? | 12:53 |
| freemangordon | (thi issue) | 12:53 |
| freemangordon | *the | 12:53 |
| uvos__ | desktop applications are unsable without | 12:53 |
| uvos__ | since they tend to have alot of actions | 12:53 |
| freemangordon | uvos__: see the issue | 12:54 |
| freemangordon | it is not about meus | 12:54 |
| freemangordon | *menus | 12:54 |
| freemangordon | also, if we are going to implement stacked menus, I don;t see why we shall do that for qt apps only | 12:54 |
| uvos__ | sorry right | 12:54 |
| uvos__ | freemangordon: because we can for qt | 12:55 |
| freemangordon | ok, but IIUC it is the WM that draws menus, no? | 12:55 |
| uvos__ | sure | 13:06 |
| uvos__ | or no | 13:06 |
| uvos__ | th application draws the menu | 13:06 |
| uvos__ | the wm just places it | 13:06 |
| uvos__ | but the point is that the qt definiton of the menu allready contains a hieracy that we are not useing | 13:06 |
| uvos__ | while the gtk2 menus are indeed flat | 13:07 |
| uvos__ | in gtk2 the menu is formed by the application implementing a custom window and teling the wm that this is the menu | 13:07 |
| uvos__ | so only mameo applications do this ofc | 13:08 |
| uvos__ | in qt the qmenu is used to generate a window. the qmenu is the same thing that generates the file, edit, help etc buttons in a desktop application | 13:08 |
| uvos__ | so all of the regular desktop applications have a maemo menu | 13:09 |
| uvos__ | thats great! .. in theroy, in practice it dosent work so well becasue the actions are flattend, Wizzup wants to improve this | 13:09 |
| uvos__ | so implementing stacked windows in gtk2 would be possibe, but would be an entirely seperate piece of code and would have no current users | 13:11 |
| uvos__ | while stacked windows in qt are instantly usefull and used by various applications | 13:12 |
| uvos__ | freemangordon: the qt application featherpad is a good demonstator of how current behavior is undesirable | 13:14 |
| uvos__ | run it first the normal way | 13:14 |
| uvos__ | and then with -platform xcb | 13:14 |
| Wizzup | freemangordon: this is about menus | 13:55 |
| Wizzup | freemangordon: so for example, when do we render the arrow at the top indicating there is a maemo menu? | 13:55 |
| Wizzup | currently we don't at all, but if I implement it, I have to check (1) if there is a qmenu and (2) if the app wants a menu there | 13:55 |
| Wizzup | qt maemo just hacked it | 13:56 |
| Wizzup | I think we ideally support applications with qmenu but not with hildon menu | 13:56 |
| Wizzup | and applications that want a hidon menu | 13:56 |
| Wizzup | and optionally, later, a way to use hildon menu for nested menus | 13:56 |
| Wizzup | for this we have to know if the app wants to use maemo menus or not | 13:56 |
| Wizzup | for example, currently all 'maemo qt' apps manually "hide" their qmenu | 13:56 |
| Wizzup | like, in C++ code | 13:56 |
| uvos__ | if netsted windows work we can presumably just hide the qmenu attached to qmainwindow | 13:58 |
| uvos__ | or? | 13:58 |
| uvos__ | for everyone | 13:58 |
| uvos__ | the arrow is more tricky with qmenu or gtk2 menus used by otherwise qt apps | 13:59 |
| Wizzup | uvos__: ok, I have a xt1602 | 14:00 |
| Wizzup | uvos__: if nested menus work you mean? | 14:00 |
| uvos__ | nice | 14:00 |
| uvos__ | yes | 14:00 |
| Wizzup | I still think we should have an option for using regular menus | 14:01 |
| uvos__ | ok like in code or env override? | 14:01 |
| Wizzup | both | 14:01 |
| Wizzup | then we could set the env override by default if we want it for everything eventually | 14:01 |
| uvos__ | ok | 14:01 |
| Wizzup | pmos doesn't mention ofono for xt1602 | 14:05 |
| Wizzup | I find it amusing that folks on that page write that the 1GB ram version is 'very slow' | 14:06 |
| uvos__ | Wizzup: yes | 14:06 |
| Wizzup | this page I mean: https://wiki.postmarketos.org/wiki/Motorola_Moto_G4_Play_(motorola-harpia) | 14:06 |
| Wizzup | I guess they are using phosh or something | 14:06 |
| uvos__ | Wizzup: but it works, at least ofono sees the modem | 14:06 |
| Wizzup | uvos__: cool | 14:06 |
| uvos__ | idk if it _really_ works | 14:07 |
| Wizzup | mhm | 14:07 |
| uvos__ | yeah 1gb slow seams wierd | 14:08 |
| uvos__ | besides the ram the device is more performant than pp | 14:08 |
| Wizzup | pretty sure it's just phosh using a lot of ram or something | 14:08 |
| Wizzup | I read somewhere that people had to wait 60 seconds for the phone app to launch on a pinephone | 14:09 |
| Wizzup | maybe I read that here :D | 14:09 |
| Wizzup | memory is hazy | 14:09 |
| uvos__ | heh sphone has that beat | 14:09 |
| uvos__ | ist 1604 the 1gb ram version? | 14:11 |
| uvos__ | i dont really know how the xt160x relate to the features | 14:11 |
| Wizzup | uvos__: yeap @ beat | 14:12 |
| uvos__ | xt1602 gpu is 22 gflops vs pps 8 | 14:17 |
| uvos__ | i wonder how this will affect hildon | 14:17 |
| Wizzup | probably not negatively? :P | 14:20 |
| The_Niz | 15 | 14:38 |
| The_Niz | woops | 14:38 |
| The_Niz | window change typo ;) | 14:39 |
| Wizzup | tmlind: new kexecboot allows me to boot to android | 14:58 |
| Wizzup | (on the 4.0.x device) | 14:58 |
| uvos__ | xt912? | 14:59 |
| Wizzup | yes | 14:59 |
| uvos__ | ill check if it works x910 4,0,4 | 14:59 |
| Wizzup | fwiw it's 2022-12-05/droid4-kexecboot.img | 14:59 |
| Wizzup | and I also flashed xt912 tags, although iirc they are the same as xt910 :) | 14:59 |
| Wizzup | er, they are different, but yeah | 15:00 |
| Wizzup | in any case it worked for me :) | 15:00 |
| sicelo | Wizzup: re:ofono/pmos - nearly everything switched to modemmanager in pmos | 16:52 |
| Wizzup | sicelo: doesn't that depend on what the mobile frontend wants? | 17:55 |
| uvos | Wizzup: everything has ditched ofono | 18:34 |
| uvos | both calls (the phosh frontend) and the plamo one moved from ofono to ofono and modemanager to just modemmanager | 18:35 |
| uvos | i do intend to do the same with sphone (well not the ditch the ofono backend part) | 18:36 |
| uvos | hopefully leste on xt1602 will provide a good test case were i can use both mm and ofono | 18:36 |
| Wizzup | ofono seems to do bluetooth well | 18:37 |
| uvos | sure maybe idk the merits of these systems | 18:37 |
| uvos | thats a reason why i want to try write a sphoen backend for it | 18:38 |
| uvos | presumably modemmanager has some merrits (maybe just better support for modern phones) otherwise the other uis would not be switching | 18:38 |
| sicelo | Wizzup: mm does bluetooth just fine too | 19:16 |
| Wizzup | uvos: I thought for gnome it was just nih or something :p | 19:35 |
| Wizzup | sicelo: did you test it? | 19:38 |
| uvos | Wizzup: so in leste-config | 19:56 |
| uvos | https://github.com/maemo-leste/leste-config/blob/master/debian/leste-config-droid4.undisplace | 19:57 |
| uvos | undisplaces files it dosent ad (the mapphone package adds these) | 19:57 |
| uvos | i presume this is an error | 19:57 |
| uvos | also none of the other packages have an undisplace at all | 19:58 |
| uvos | is it even nessecary? | 19:58 |
| tmlind | Wizzup: ok good to hear it booted :) | 19:58 |
| uvos | Wizzup: https://github.com/maemo-leste/leste-config/pull/34 | 20:04 |
| uvos | tmlind: is the XT910-16 XT912-16 in utags really nessecay? | 20:08 |
| uvos | bootloader dosent seam to care | 20:08 |
| uvos | tmlind: latest kexecboot also manages to boot android on my xt910 (dident work before) | 20:10 |
| tmlind | uvos: yeah not sure if it matters, that's the naming the mz6xx use, different from what xt8xx use | 20:31 |
| tmlind | makes more sense for the naming than the proto naming.. | 20:32 |
| tmlind | it might make some difference on 16gb vs 32gb emmc tablets but i doubt it | 20:33 |
| uvos | tmlind: ok yeah thats what i though | 20:33 |
| uvos | t | 20:33 |
| uvos | why dont like solana, maserati, targa, edison, spyder and pasteur? :P | 20:34 |
| uvos | totaly makes sense and is easy to remember | 20:34 |
| tmlind | is there a car model called pasteur? why not edsel? | 20:35 |
| uvos | mz609 | 20:36 |
| uvos | oh car model | 20:36 |
| uvos | no idea | 20:36 |
| uvos | both mz609 and mz617 being called pastuer feals like them giveing up anyhow :P | 20:36 |
| tmlind | canning it? :) | 20:39 |
| uvos | xD | 20:39 |
| Wizzup | uvos: what does git log say about it? (undisplace) | 21:12 |
| Wizzup | uvos: merged, shall I release for -devel? | 21:15 |
| uvos | Wizzup: dunno what you want to know about git log | 22:21 |
| uvos | it was added before -mapphone existed | 22:21 |
| uvos | Wizzup: its broken for sure | 22:21 |
| uvos | since this way uninstalling -droid4 breaks lots of files in -mapphone | 22:22 |
| uvos | i just dont know how its supposed to be | 22:22 |
| uvos | Wizzup: not dont release | 22:22 |
| uvos | there is another problem | 22:22 |
| uvos | this https://github.com/maemo-leste/leste-config/blob/deb9a79200993b6e43ce4bceca71ce901c33dafe/debian/control#L29 | 22:23 |
| uvos | you need to add razr here to make it work, but then i think razr needs to be in its own section | 22:23 |
| uvos | otherwise i have no idea what happens when you install -mapphone | 22:23 |
| uvos | tmlind: enableing te_support apears to make things worse | 22:41 |
| Wizzup | uvos: ok, I'll investigate | 23:01 |
| Wizzup | uvos: looks like undisplace does nothing | 23:28 |
| Wizzup | to me at least | 23:28 |
| Wizzup | uvos: hmm, right, that's why we had the sections I guess | 23:29 |
| Wizzup | uvos: well the images will have one specified in the meta | 23:29 |
| Wizzup | Package: hildon-meta-bionic | 23:30 |
| Wizzup | ... | 23:30 |
| Wizzup | leste-config-mapphone, | 23:30 |
| Wizzup | uvos: actually, it doesn't contain leste-config-bionic | 23:30 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!