| diejuse | Hello everyone | 00:58 |
|---|---|---|
| * gnarface waves | 01:00 | |
| Wizzup | hi | 01:04 |
| Wizzup | diejuse: welcome back | 01:05 |
| diejuse | thanks Wizzup | 01:06 |
| diejuse | I have something new in mind | 01:06 |
| Wizzup | diejuse: what is that? | 01:56 |
| diejuse | I emulated Maemo on Android with the chroot technique for rooted Android smartphones. Now I want to try to emulate Maemo with the proot technique for non-rooted smartphones. | 02:14 |
| diejuse | I think it's a good idea to make Maemo more popular since most people don't root their smartphones. Thus it would be installable on any Android smartphone so that people can try it on their phone. | 02:16 |
| Wizzup | I think your guide was also for beowulf, so some people might struggle with the new version | 02:27 |
| Wizzup | maybe we can make it a bit easier too | 02:27 |
| diejuse | I recently updated my github and reduced the steps to make the installation a little faster. | 02:29 |
| diejuse | Regarding proot. I have successfully tried emulating Maemo on my unrootable Blackberry Key1. | 02:30 |
| diejuse | It has also worked on another smartphone that I have with the Android 7 version. But however, on more modern smartphones it gives me problems and I need your help. | 02:31 |
| Wizzup | ah, great to know @ updated github | 02:35 |
| Wizzup | What kind of problems? (I might go to sleep soon though) | 02:35 |
| diejuse | My problem is with /etc/init.d/dbus start. On my phones with Android 7 there is no problem. But in the most modern ones I get the error "[: lt: unexpected operator" so it does not create the /run/dbus/system_bus_socket. | 02:37 |
| diejuse | (Yes, I have to go to sleep soon too.) | 02:39 |
| Wizzup | seems the shell being used it not compatible | 02:44 |
| Wizzup | the script uses /bin/sh, maybe it is not compatible with the android sh | 02:44 |
| diejuse | I thought so, and changed it to /bin/bash but it didn't fix the problem. I don't understand why it works on older Android phones and not more modern ones. Could it be because of the kernel? | 02:47 |
| Wizzup | not likely, maybe check if /bin/bash is actually bash | 02:48 |
| diejuse | But I do exactly the same thing on all the smartphones I have but it only fails on those with a more modern version of Android. Mmm | 02:55 |
| Wizzup | maybe check what version /bin/sh is | 02:55 |
| Wizzup | like /bin/sh --version | 02:56 |
| diejuse | In both cases it says "GNU Bash, version 5.0.3(1)-release (aarch64-unknown-linux-gnu). | 03:03 |
| diejuse | Searching on pages like this https://forum.proxmox.com/threads/pve7to8-broken-kernel.130989/ about the error "[: lt: unexpected operator" they talk about it being solved by reinstalling another kernel. | 03:05 |
| diejuse | With the command "uname -a" on my old smartphone I get "Linux localhost 3.18.31-perf-g625ad6d" and on the modern one "Linux localhost 5.15.137-BKLYN-Kalama-Gki-Kernel-1.0.5" | 03:13 |
| Wizzup | diejuse: I don't know if it matters, but what about /usr/bin/[ --version | 10:44 |
| Wizzup | uvos: looks like charge mode works on mz617 | 10:48 |
| uvos__ | Wizzup: more like discharge mode given that it only takes 500ma max there | 11:31 |
| Wizzup | lol | 11:33 |
| Wizzup | uvos__: should still be enough since with screen off it doesn't use more than 100mA or so | 11:34 |
| Wizzup | (because it doesn't idle yet) | 11:34 |
| Wizzup | but yeah can't we change the input current limit in dts? | 11:35 |
| uvos__ | isent safe to do because youll crash devices that cant supply | 11:35 |
| Wizzup | ok | 11:35 |
| uvos__ | charging 14Ah battery at 400mA | 11:35 |
| uvos__ | weee | 11:35 |
| Wizzup | well it just needs enough to boot to leste proper | 11:36 |
| Wizzup | btw, I also booted my xt912 to leste now (for the first time) and I indeed also see the screen issue that you are seeing | 11:36 |
| Wizzup | and now I need to go to the store to get more sd cards :) | 11:36 |
| uvos__ | not achiveing hsync yeah | 11:37 |
| Wizzup | right | 11:38 |
| uvos__ | one could try diffing the omap-dss regs to see what to change there | 11:39 |
| Wizzup | same tool as for droid 3? | 11:39 |
| uvos__ | probubly some timeing is configured slightly differently somehow | 11:39 |
| uvos__ | no this is omap reg | 11:40 |
| uvos__ | so you need rwram for android | 11:40 |
| uvos__ | the other tool is for reading cpcap regs via the stock kernels custom interface | 11:40 |
| tmlind | fyi, you can set the charge limit with something like echo 900000 > /sys/class/power_supply/usb/input_current_limit for 900mA | 11:41 |
| uvos__ | yeah we do that | 11:41 |
| tmlind | won't work with all chargers as the detection is missing | 11:41 |
| tmlind | ok | 11:41 |
| uvos__ | not early in boot however | 11:41 |
| freemangordon | tmlind: in that regard - what is the proper way to implement cpcap-extcon? | 11:42 |
| freemangordon | because we need that for charger detection | 11:43 |
| Wizzup | uvos__: I can try to get the now on leste and android, iirc I will need the reg addrs? | 11:44 |
| uvos__ | the now on leste? | 11:44 |
| Wizzup | them | 11:45 |
| Wizzup | the regs | 11:45 |
| Wizzup | assuming you wanted to diff them | 11:45 |
| Wizzup | or do you just need them on android? | 11:45 |
| uvos__ | the reg addresses you will find in the omap datasheet ofc | 11:45 |
| tmlind | freemangordon: not sure if a separate driver is needed or if the iio driver can also implement that | 11:45 |
| uvos__ | i would just diff the whole dss region and try to understand the differences | 11:46 |
| uvos__ | tmlind: any better ideas about this problem? | 11:46 |
| freemangordon | tmlind: hmm | 11:47 |
| freemangordon | is it ok to have one driver multiple subsystems? | 11:47 |
| Wizzup | uvos__: quick check, it looks like leste-config-razr doesn't depend on leste-config-mapphone which seems wrong, or rather mapphone doesn't depend on leste-config-razr, shall I fix that? | 11:47 |
| uvos__ | i have seen several drivers do this | 11:47 |
| Wizzup | also do we want to split razr into razr-xt910 and razr-xt912 | 11:47 |
| freemangordon | uvos__: ok | 11:48 |
| uvos__ | not sure if reccomende behavor tho | 11:48 |
| uvos__ | Wizzup: yes, spi modem | 11:48 |
| uvos__ | but maybe have xt91x.dtsi | 11:48 |
| Wizzup | I will fix up the meta in a bit then | 11:48 |
| Wizzup | I mean just leste pkg wise | 11:48 |
| uvos__ | oh | 11:48 |
| uvos__ | no | 11:48 |
| uvos__ | they can share with bionic even i think | 11:48 |
| uvos__ | same with atrix2 | 11:48 |
| Wizzup | doesn't this config what gets written to boot.cfg and thus the dtb that is being loaded | 11:49 |
| Wizzup | or am I wrong and boot.cfg never gets touched | 11:49 |
| * Wizzup checks | 11:49 | |
| uvos__ | we have a special package for that | 11:49 |
| uvos__ | this one needs all variants | 11:49 |
| Wizzup | it looks like boot.cfg isn't written, that's fine then | 11:50 |
| uvos__ | it is | 11:50 |
| uvos__ | we have a pacakge for that | 11:50 |
| Wizzup | maemo-kernel-config ? | 11:50 |
| tmlind | freemangordon: git grep extcon drivers/iio does not show such things, maybe you can implement an drivers/extcon driver that just uses the iio calls as the voltages etc should be already available via iio | 11:50 |
| uvos__ | Wizzup: not sure what its called | 11:50 |
| uvos__ | but i remember makeing it with parazyd | 11:50 |
| Wizzup | I made maemo-kernel-config for n900 postinst mostly | 11:50 |
| Wizzup | dpkg -S doesn't claim that anyone owns boot.cfg | 11:51 |
| uvos__ | no no theres a kexecboot config package | 11:51 |
| uvos__ | i sware it owns the boot.cfg | 11:51 |
| Wizzup | this is new to me | 11:51 |
| uvos__ | or should anyhow | 11:51 |
| Wizzup | droid4-kexecboot-config - boot.cfg file for Motorola Droid4 kexecboot | 11:51 |
| uvos__ | we did this to add charge mode | 11:51 |
| freemangordon | tmlind: back then I extended phy-cpcap-usb | 11:51 |
| Wizzup | uvos__: yes, looks like it | 11:51 |
| tmlind | freemangordon: ok makes sense if no other use for it | 11:51 |
| Wizzup | uvos__: well then we still need separate meta's for the devices anyway | 11:51 |
| uvos__ | ok | 11:52 |
| freemangordon | tmlind: 'it'? | 11:52 |
| tmlind | freemangordon: no other use for the extcon driver beyond the charger detection | 11:52 |
| Wizzup | uvos__: https://github.com/maemo-leste/mapphone-kexecboot-config | 11:52 |
| uvos__ | looks like i even allready added support for xt91x | 11:53 |
| Wizzup | there is no pkg for it on my system | 11:53 |
| Wizzup | uvos__: I don't see it btw, just bionic/droid3/droid4 | 11:53 |
| Wizzup | in any case this is trivial I will look at it | 11:53 |
| freemangordon | hmm, ok, I will try to dig what I have done back then and maybe resume the work | 11:54 |
| Wizzup | regarding the regs, uhh :) | 11:54 |
| Wizzup | uvos__: oh maemo/chimaera is not in sync with master it looks like | 11:56 |
| tmlind | freemangordon: sounds good to me :) especially the tablets need to max out the cpcap charger until we have the cpcap-gpio operated charger implemented.. | 11:56 |
| freemangordon | tmlind: oh, no, I wrote extcon-cpcap driver, and just fixed a bug in phy driver :) | 11:57 |
| freemangordon | maybe I will send RFC patch | 11:57 |
| freemangordon | unless someone wants to take over | 11:58 |
| freemangordon | tmlind: ^^^ | 11:58 |
| Wizzup | uvos__: apart from finding the regs, I guess I need to run this with the screen on | 11:58 |
| Wizzup | does the brightness matter | 11:58 |
| freemangordon | it is just that I won;t have time to work on that soon | 11:58 |
| uvos__ | Wizzup: brightness is in no way related to dss so no | 11:58 |
| uvos__ | yes dss needs to be active | 11:59 |
| uvos__ | else nonsene | 11:59 |
| uvos__ | *nonsense | 11:59 |
| Wizzup | ok, well I can try to do this but you'll have to feed me the locations/addrs | 12:00 |
| uvos__ | pretty busy rn, maybe later | 12:00 |
| Wizzup | ok | 12:00 |
| uvos__ | maybe look at d3 cpcap first should not need me for that | 12:01 |
| Wizzup | mhm | 12:01 |
| tmlind | freemangordon: i'm pretty limited on time for the infinite future.. | 12:04 |
| tmlind | can't commit to anything right now beyond trying to get the mz617 patches upstream and the usb oops fixed | 12:05 |
| diejuse | Wizzup /usr/bin/[ --version the same output inside proot, both on the old and new smartphone | 12:08 |
| freemangordon | tmlind: ok | 12:09 |
| Wizzup | diejuse: ok, not sure then | 12:11 |
| Wizzup | brb | 12:11 |
| diejuse | On my modern smartphone Maemo does work with chroot but not with proot. By doing "echo $SHELL" , inside chroot it gives an output of "/system/bin/sh" while inside proot it gives an output of "/bin/bash". I think this is a good clue. | 12:25 |
| Wizzup | diejuse: yes | 12:31 |
| humanbeta | Is there any hints how get Pinephone get connected to TV...Docking Bar has HDMI-out put is that usb-c port actually USB2.0+displayport combination? So can it work cheap usb–c to displayport adapter? | 12:58 |
| humanbeta | Has anybody ever connected Pinephone with Maemo to external display? | 13:05 |
| humanbeta | hardware itself should support up to 4K resolution. | 13:08 |
| Wizzup | humanbeta: I haven't done that yet | 13:15 |
| Wizzup | I do have some usb hub that I got with it that has a hdmi port | 13:15 |
| humanbeta | Is yours USB-C Docking Bar that come with every new Pinephone these days (Beta Edition with Convergence Package)? | 13:21 |
| xmn | I've use the PP with external monitors extensively, but this was not use Leste. In the past some folks had challenges with the docks. But it could be the cable, if the monitor need too much power or if its a dock that didn't come with the PP then it could be that dock may not work with it for some reason. | 13:23 |
| xmn | I have 2 dock and both worked with the PP hardware. | 13:24 |
| Wizzup | humanbeta: I don't know, I got it with the pre braveheart | 13:26 |
| humanbeta | xmn: what OS support it? | 13:35 |
| xmn | I can only say the ones I used or tested, which is not extensive :). I tried mobian, manjaro phosh & plasma. I never thought to plug it in when trying maemo, but have used an ext monitor with my n900 before (which was only mirrored. | 13:37 |
| Wizzup | uvos__: working on the d3 but it takes a bit since I have to root the device again, and I did it using sigmakey last time | 13:40 |
| humanbeta | xmn: so if it working with mobian, then it should not be too hard to get work with Maemo...what have to do with mobian to setup hdmi on? | 13:42 |
| Wizzup | pretty sure you can just turn it on with xrandr | 13:43 |
| Wizzup | but maemo's hildon-desktop doesn't really support multi monitor | 13:43 |
| Wizzup | the real question is, what do you want to do with the external monitor | 13:43 |
| humanbeta | just mirroring to big screen..more easy to show more than one people. | 13:45 |
| Wizzup | this should work ok with xrandr | 13:45 |
| xmn | Not sure how it is in Leste, and I haven't used xrandr before ... but hildon on n900 mirror at a low resolution. Basically it was like a giant phone screen ... lol. It does give more room or change aspect ratio. The smart guys in the Leste project may have changed that, but I haven't tested that. But would be curious to know. | 13:52 |
| xmn | For me mirror is not so useful. I think I used it only a few time with n900 over 10 + years of daily driving it. But maybe it could be for you. | 13:53 |
| xmn | Wizzup xrandr seems like a cool little solution. Thanks for sharing that. | 13:54 |
| humanbeta | Wizzup: Pinephone detected TV!, chatting now at 1920x180 with Pinephone! | 13:59 |
| humanbeta | *1920x108 | 14:00 |
| humanbeta | *1920x1080 | 14:00 |
| xmn | nice | 14:00 |
| humanbeta | and display of Pinephone shows upper part of that resolution | 14:01 |
| humanbeta | same time | 14:01 |
| humanbeta | touch act strange | 14:03 |
| humanbeta | it seems that it try to be scale some how | 14:05 |
| Wizzup | you can scale with xrandr | 14:05 |
| xmn | but are you doing this in maemo? | 14:05 |
| Wizzup | or just change the resolution of the tv/hdmi with xrandr | 14:05 |
| humanbeta | yes I do this with Maemo | 14:06 |
| xmn | nice | 14:09 |
| humanbeta | Pinephone touch screen works if I choose 1280x720 to HDMI, but If I choose 1920x1080 it scale touch and show upper part of screen on Pinephone, but looks good on TV. | 14:12 |
| Wizzup | if you want to mirro the screen you must have the hdmi as the same res as native phone | 14:12 |
| Wizzup | or set some scaling | 14:12 |
| Wizzup | everything else is probably a nightmare | 14:13 |
| humanbeta | It mirror by default. | 14:14 |
| xmn | humanbeta it seems like you have it working, so how does this relate to your original questions "Pinephone get connected to TV ... " | 14:17 |
| Wizzup | uvos__: btw looks like just booting android to charge also wipes data | 14:17 |
| Wizzup | (and cache, and preinstall) | 14:17 |
| humanbeta | xmn: So question is answered, thanks to you and Wizzup. | 14:18 |
| humanbeta | it was easier than I though. | 14:19 |
| xmn | heh, ah cool. And I would say it was Wizzup :D. | 14:20 |
| xmn | Glade to hear you got it figured out. | 14:21 |
| Wizzup | maybe document it somewhere on the wiki | 14:22 |
| xmn | ^ | 14:23 |
| bencoh | Wizzup: why would it wipe data/ | 14:25 |
| bencoh | ? | 14:25 |
| bencoh | oh, because btrfs/unknown fs? | 14:25 |
| humanbeta | Put example to wiki: xrandr --output HDMI-1 --mode 1280x720 | 14:26 |
| Wizzup | bencoh: yes | 14:29 |
| humanbeta | if somebody know better xrandr can try better settings and widening desktop to both screen. | 14:29 |
| Wizzup | this does not exist other than xrandr fractional scaling | 14:29 |
| humanbeta | ok | 14:30 |
| freemangordon | humanbeta: hmm, how does it mirror if resolutions on both displays differ? | 14:31 |
| freemangordon | isn;t it better to set hdmi on the same resolution as panel? | 14:32 |
| humanbeta | freemangordon: If hdmi has higher resolution than on Pinephone, then Pinephone crop, but it seems that hdmi crop when using lower resolution than on Pinephone. | 14:33 |
| humanbeta | but touch scaling..so touch not usable if bigger resolution on HDMI. | 14:35 |
| humanbeta | I have connect mouse if using 1920x1080. | 14:35 |
| freemangordon | humanbeta: exactly that's why you should have same resolution on both displays, by adjusting HDMI to match internal panel | 14:38 |
| humanbeta | My test display doesn't support 1440x720..so that is why using 1280x720. | 14:41 |
| uvos | with glamor one could use a xrandr transformation matrix to fit any resolution onto the internal display | 14:42 |
| humanbeta | impressive is that I tought internal display use 720x1440 with software rotate and still HDMI output work right away. | 14:45 |
| humanbeta | btw..HDMI audio does not work. | 14:51 |
| humanbeta | anyway..if somebody can program TV-output Settings to Settings like was in Maemo 5, it would be nice ;) | 14:59 |
| gnarface | so far i haven't heard anyone claim they were able to get HDMI audio working on pine64 hardware | 16:20 |
| gnarface | that's an outstanding issue that is probably not maemo's fault | 16:20 |
| gnarface | display out; yes, though finicky. but not audio. | 16:21 |
| gnarface | (and not isolated to just the phones either) | 16:22 |
| gnarface | and it doesn't seem to be clear whether it's a kernel issue or a hardware issue. nobody actually knows enough about the hardware. | 16:45 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!