| *** sledges_ is now known as sledges | 10:20 | |
| *** OhYash1 is now known as ohyash | 11:22 | |
| steeeve | Esketit guys, I noticed that with anbox device reboots after few seconds after it boots. Here's the pstore dmesg https://bpaste.net/show/ab6202bf2edc dunno, if you know let me know :P | 20:48 |
|---|---|---|
| steeeve | Aww hell, wrong group, ill ask in sfdroid :D | 20:51 |
| r0kk3rz | sounds like dodgy kernel patch | 21:31 |
| steeeve | Yeah but nooo | 21:32 |
| steeeve | I applied them accurately | 21:33 |
| steeeve | In the past (5-6 months ago) it used to work. Now it doesnt | 21:34 |
| r0kk3rz | that doesnt mean shit | 21:36 |
| steeeve | But but | 21:37 |
| steeeve | Last kernel commits was 10 months ago, and in the past anbox used to work, so, it cant be a kernel thing | 21:38 |
| steeeve | I think, especially if anbox doesnt require new stuff | 21:38 |
| r0kk3rz | your logic doesnt logic | 21:39 |
| r0kk3rz | anyway, it appears to be starting a lxc thing on boot | 21:39 |
| r0kk3rz | so stop it | 21:39 |
| steeeve | My logic is legit | 21:39 |
| steeeve | What? | 21:39 |
| r0kk3rz | oh hang on, is this even sailfish? | 21:40 |
| steeeve | Yes ._. | 21:41 |
| r0kk3rz | ok, that must be an anbox thing then | 21:42 |
| steeeve | Oh no, it's broken :( | 21:43 |
| steeeve | Why all these things happens only to me? | 21:43 |
| r0kk3rz | because youre the only one with some horrible samsung thing? | 21:45 |
| steeeve | Really? In 2019 im the only samsung dude who deals with sailfish? | 21:45 |
| steeeve | In addition this thing costed a lot :/ | 21:46 |
| r0kk3rz | pretty much yeah | 21:47 |
| r0kk3rz | afaik all the only samsung ports have been dropped as 'too broken' | 21:48 |
| r0kk3rz | s/only/other | 21:48 |
| steeeve | Hahaha noobs | 21:48 |
| steeeve | I mean, half of the hardware has been fixed thanks to this group, but except fm audio everything works ^^ | 21:49 |
| steeeve | For the cost of a partially burned amoled display | 21:50 |
| *** steeeve is now known as steevie | 21:51 | |
| r0kk3rz | there was a dude that got reasonably far with the s7 | 21:54 |
| r0kk3rz | but i think he switched to halium | 21:54 |
| steevie | Ah, yeah, the guy i took ofono fix from | 21:55 |
| steevie | Halium is crap | 21:55 |
| r0kk3rz | yeah well, for some people sfos isnt open source enough | 21:56 |
| steevie | It's a thing that wants to unify stuff but it only breaks everything. After I ported halium omly display was working lol | 21:56 |
| steevie | Then i laughed and gave up | 21:57 |
| r0kk3rz | we do have the best hybris porters here | 21:58 |
| steevie | Like me? | 21:58 |
| r0kk3rz | totally | 22:00 |
| mal | I do have on wip samsung tablet port | 22:01 |
| steevie | <3 | 22:01 |
| r0kk3rz | which you mostly dropped as being 'too broken' :P | 22:01 |
| mal | true, I haven't worked on it much, I did fix some issues a while ago | 22:01 |
| mal | last month or so | 22:02 |
| steevie | There are chinese phones that are even worse than samsung | 22:02 |
| r0kk3rz | oh ok, i havent been around in the last month | 22:02 |
| mal | steevie: about fm radio audio, do you have defined the correct audio device for that, it can be configured | 22:03 |
| mal | steevie: how did you manage to partially burn a display? | 22:03 |
| mal | too much heat? | 22:03 |
| steevie | No, but i need to set different audiomanager parameters like realcall for calls | 22:03 |
| mal | steevie: so you haven't done any audio configuration for fm radio? | 22:04 |
| mal | there are usually options what the device is, depending on android base mostly | 22:04 |
| steevie | No, basically at the begin of port, i stucked at boot logo, and since i stucked at it for some times, now the white parts of the boot logo are darker :( | 22:04 |
| r0kk3rz | steevie: people have attempted huawei kirin based ports and turned away in sheer horror | 22:04 |
| mal | steevie: ok, that's not nice :/ | 22:05 |
| steevie | mal: no, it requires quirks in pulseaudio | 22:05 |
| steevie | But who cares of fm radio? | 22:05 |
| steevie | The answer of that question is why i didnt fix it ^^ | 22:05 |
| r0kk3rz | nerds | 22:05 |
| mal | steevie: perfectionists | 22:06 |
| steevie | Yeah, a full green line on adaptations page is cool tho | 22:06 |
| mal | steevie: what android base was that? | 22:07 |
| steevie | In 16.0 i implemented source built audio hal with amplifier which doesnt require those quirks but when i tried it in 14.1 audio on calls didnt work (in lineageos) | 22:08 |
| mal | maybe try https://github.com/mer-hybris/droid-config-onyx/blob/master/sparse/etc/pulse/xpolicy.conf.d/xvars.conf assuming you have also this symlink https://github.com/mer-hybris/droid-config-onyx/blob/master/sparse/etc/pulse/xpolicy.conf.d/fmradio.conf | 22:08 |
| steevie | No, it's a different thing | 22:08 |
| mal | steevie: what is? | 22:09 |
| mal | I don't understand what the problem is with fm radio because you don't give any information | 22:09 |
| steevie | If 15.1 hybris is buildable i can try to cherry-pick my professional 16.0 source-built audio commits | 22:09 |
| steevie | Wait | 22:09 |
| steevie | https://github.com/vlw/android_device_samsung_a3-common/blob/453b8e6eddc666011e090e19f9d3f24759bf6fab/patchfm.diff . as you can see from here it sets some audiomanager parameters. I need to set those, and that would require pulseaudio changes like in realcall for audio on calls | 22:12 |
| steevie | https://github.com/mer-hybris/pulseaudio-modules-droid/commit/9a4165f42d2a3522414c826964ac2dc6df3908f6 | 22:13 |
| mal | steevie: what fm chip does the device have? | 22:13 |
| steevie | Msm8916. But the problem is stock audio hal which requires those parameters, not fm radio itself | 22:14 |
| steevie | Maybe also fm radio but those audio parameters need to be set | 22:14 |
| mal | quite odd | 22:15 |
| steevie | Yeah, thats why now i build source-built audio ^ | 22:15 |
| steevie | With a professional tfa9895 amplifier hal | 22:16 |
| steevie | But as i said with source built audio in 14.1 i dont have audio in calls (in lineage calls dont even start) while in 16.0 i do | 22:17 |
| mal | no wonder people don't port more samsungs when they need all kinds of hacks | 22:17 |
| steevie | Yeah, hacks nooo | 22:18 |
| steevie | Im too lazy to fix fm | 22:18 |
| steevie | But one day ill fix it | 22:18 |
| steevie | You know any info about xa2 android 8.1 support? Is it device-specific? If no, it can be hackerable😏 | 22:26 |
| r0kk3rz | its binderized up the wazoo so it should be fairly portable | 22:27 |
| r0kk3rz | but it needs an android 8 base or higher | 22:27 |
| steevie | There is an hybris-15.1 branch on manifest so, that wouldnt be a problem | 22:28 |
| steevie | But...is that thing closed sources? I mean, do sailfish guys want that thing to be used only on their devices? | 22:28 |
| r0kk3rz | but im not sure community folk have really poked around with it too much yet | 22:28 |
| r0kk3rz | yeah its closed | 22:29 |
| r0kk3rz | could be due to myriad, or simply because they want to | 22:29 |
| mal | steevie: as an example of perfectionism I implemented the fm radio adaptation plugin for qtmultimedia because I wanted to have working fm radio, although I rarely listen to live radio | 22:29 |
| steevie | Does sailfish even have fm radio apps? | 22:30 |
| steevie | On store all radio apps are wlan radios | 22:30 |
| mal | yes, the default media app supports fm radio | 22:30 |
| r0kk3rz | there was also that one kimmoli did | 22:31 |
| steevie | Ah | 22:31 |
| mal | r0kk3rz: that was just for testing before the official app got support | 22:31 |
| r0kk3rz | it works well enough | 22:31 |
| r0kk3rz | and i dont use the official media app, so it suited my need | 22:31 |
| mal | yes, fm radio doesn't really need many features so both of those do pretty much the same thing | 22:32 |
| steevie | Perfectionism is useless when lineage doesnt support your nfc chip. I mean, youll always have that red box on libhybris adaptations page :/ | 22:32 |
| mal | I use the official app | 22:32 |
| steevie | Btw...what's the status of halium implementation in sailfishos? I heard they could use it about 2 years ago | 22:36 |
| r0kk3rz | no status | 22:36 |
| steevie | So, no halium? | 22:37 |
| r0kk3rz | i dont think anyone is interested in using halium with sfos | 22:37 |
| r0kk3rz | 2 years ago is approx when halium started, and they were trying to get everyone on board | 22:38 |
| steevie | Good. Because it was sad to see how ubports ruined their os with halium | 22:38 |
| steevie | Yes, the beginning | 22:38 |
| r0kk3rz | technically it should be possible, but it would require being decently proficient in both toolchains | 22:40 |
| r0kk3rz | so maybe TheKit is the only person who would do it | 22:40 |
| steevie | Oh that thekit guy...nice person | 22:41 |
| TheKit | at this point Halium vs Sailfish way differ mostly in just Android being run in same root or inside LXC container | 22:42 |
| steevie | You mean unified but you'll never have full hardware working vs not unified but you have a chance to fix your hardware? | 22:43 |
| r0kk3rz | yeah but youd have to do something with mic to build an image the halium way | 22:43 |
| r0kk3rz | because they seperate the adaptation from the os layer right? | 22:44 |
| steevie | And halium it's not even unified, since when you port it you'll have less hardware working than a normal sailfish port :/ | 22:44 |
| steevie | But nice person eh | 22:45 |
| TheKit | steevie, unified vs not unified is not that much Halium-level choice, Halium just provides Android parts | 22:48 |
| steevie | Yes, but in theory if you installed halium+rootfs you would have everything working, assuming that everything works in lineageos | 22:49 |
| steevie | Like treble | 22:49 |
| TheKit | that's supposed to be that way on paper, but now most of issues that are on UBPorts are from os layer middleware, which is different from Sailfish | 22:51 |
| steevie | Exactly | 22:52 |
| steevie | Like the droid-config in sailfish that you want to unify but it's impossible to unify | 22:53 |
| TheKit | r0kk3rz, basically it would replace functionality of droid-hal-init and /system partition, so probably droid-hal-device package gets replaced | 22:53 |
| TheKit | steevie, replacing droid-config is out of scope, what UBPorts do is basically providing configs as overlay embedded in system.img and doing stuff in generic way where possible (e. g. reading device name from build.props instead of hardcoding it in rootfs config) | 22:56 |
| r0kk3rz | you will always need device specific configs, its just a question of where they live | 22:58 |
| steevie | It's impossible to unify everything, thats all. Just go to old porting method | 22:59 |
| r0kk3rz | halium isnt trying to unify everything | 23:01 |
| steevie | It is | 23:02 |
| TheKit | what it is trying to unify is building Android port bits for UBPorts/Plasma/LuneOS | 23:02 |
| TheKit | analogue of hybris-hal build + LineageOS system.img in Sailfish terms | 23:03 |
| steevie | No its trying to unify everything | 23:03 |
| steevie | Otherwise it would use lineage zip like sailfish | 23:04 |
| TheKit | it's mostly just a design choice between "building patched parts we need and overlaying them on top of unmodified /system" and "building only parts of /system we need with patches" | 23:06 |
| r0kk3rz | steevie: sometimes you really dont make sense :P | 23:07 |
| r0kk3rz | using or not using a lineage base image has nothing to do with any unification | 23:08 |
| r0kk3rz | lineage use a single android source tree, you could build that yourself | 23:08 |
| steevie | Halium is not only lineage | 23:09 |
| steevie | Ive worked with halium, i know it | 23:09 |
| r0kk3rz | you have some strange ideas about why it is though | 23:10 |
| r0kk3rz | even if you know what it is | 23:10 |
| steevie | It's a modified lineage with only the needed android parts | 23:10 |
| steevie | I KNOW ITTTT | 23:10 |
| steevie | Bhushan shah | 23:11 |
| steevie | He wants to unify everything. Nice person tho | 23:11 |
| r0kk3rz | ok, you believe what you want | 23:11 |
| steevie | 👍🏻 | 23:12 |
| steevie | Btw today its my birthday and i didnt even hear anyone saying happy birthday steevie sailfish porter | 23:21 |
| r0kk3rz | thats sad | 23:22 |
| steevie | Yeah but you can remedy ;) | 23:23 |
| heroic_1 | https://github.com/fredldotme and me are gonna attempt a halium-8 bringup on sony devices soon-ish | 23:38 |
| heroic_1 | at least the boot image generation and chroot launching could be unified | 23:38 |
| heroic_1 | as well as shared kernels | 23:39 |
| heroic_1 | sf/mer could also learn a thing or two from halium about community involvement and documentation | 23:40 |
| heroic_1 | and btw: same commit, but do you see the difference? https://github.com/mer-hybris/hybris-boot/pull/160 vs https://github.com/Halium/hybris-boot/pull/73 | 23:40 |
| r0kk3rz | ? | 23:42 |
| TheKit | heroic_1, keep me updated on this, I attempted to get phh-treble inside LXC, it's kinda running, but many things are crashing yet | 23:43 |
| heroic_1 | cool | 23:44 |
| steevie | Phh lol, i know him | 23:44 |
| heroic_1 | what base? | 23:44 |
| heroic_1 | and which device? | 23:44 |
| heroic_1 | r0kk3rz: I'll give you a hint, one is merged and one is stale | 23:46 |
| r0kk3rz | yeah we should really go through those fixup mountpoints prs, theres quite a lot of them | 23:50 |
| steevie | And my pull request for them hasnt been merged, yet | 23:51 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!