Tuesday, 2019-03-12

*** sledges_ is now known as sledges10:20
*** OhYash1 is now known as ohyash11:22
steeeveEsketit 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 :P20:48
steeeveAww hell, wrong group, ill ask in sfdroid :D20:51
r0kk3rzsounds like dodgy kernel patch21:31
steeeveYeah but nooo21:32
steeeveI applied them accurately21:33
steeeveIn the past (5-6 months ago) it used to work. Now it doesnt21:34
r0kk3rzthat doesnt mean shit21:36
steeeveBut but21:37
steeeveLast kernel commits was 10 months ago, and in the past anbox used to work, so, it cant be a kernel thing21:38
steeeveI think, especially if anbox doesnt require new stuff21:38
r0kk3rzyour logic doesnt logic21:39
r0kk3rzanyway, it appears to be starting a lxc thing on boot21:39
r0kk3rzso stop it21:39
steeeveMy logic is legit21:39
r0kk3rzoh hang on, is this even sailfish?21:40
steeeveYes ._.21:41
r0kk3rzok, that must be an anbox thing then21:42
steeeveOh no, it's broken :(21:43
steeeveWhy all these things happens only to me?21:43
r0kk3rzbecause youre the only one with some horrible samsung thing?21:45
steeeveReally? In 2019 im the only samsung dude who deals with sailfish?21:45
steeeveIn addition this thing costed a lot :/21:46
r0kk3rzpretty much yeah21:47
r0kk3rzafaik all the only samsung ports have been dropped as 'too broken'21:48
steeeveHahaha noobs21:48
steeeveI mean, half of the hardware has been fixed thanks to this group, but except fm audio everything works ^^21:49
steeeveFor the cost of a partially burned amoled display21:50
*** steeeve is now known as steevie21:51
r0kk3rzthere was a dude that got reasonably far with the s721:54
r0kk3rzbut i think he switched to halium21:54
steevieAh, yeah, the guy i took ofono fix from21:55
steevieHalium is crap21:55
r0kk3rzyeah well, for some people sfos isnt open source enough21:56
steevieIt's a thing that wants to unify stuff but it only breaks everything. After I ported halium omly display was working lol21:56
steevieThen i laughed and gave up21:57
r0kk3rzwe do have the best hybris porters here21:58
steevieLike me?21:58
malI do have on wip samsung tablet port22:01
r0kk3rzwhich you mostly dropped as being 'too broken' :P22:01
maltrue, I haven't worked on it much, I did fix some issues a while ago22:01
mallast month or so22:02
steevieThere are chinese phones that are even worse than samsung22:02
r0kk3rzoh ok, i havent been around in the last month22:02
malsteevie: about fm radio audio, do you have defined the correct audio device for that, it can be configured22:03
malsteevie: how did you manage to partially burn a display?22:03
maltoo much heat?22:03
steevieNo, but i need to set different audiomanager parameters like realcall for calls22:03
malsteevie: so you haven't done any audio configuration for fm radio?22:04
malthere are usually options what the device is, depending on android base mostly22:04
steevieNo, 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
r0kk3rzsteevie: people have attempted huawei kirin based ports and turned away in sheer horror22:04
malsteevie: ok, that's not nice :/22:05
steeviemal: no, it requires quirks in pulseaudio22:05
steevieBut who cares of fm radio?22:05
steevieThe answer of that question is why i didnt fix it ^^22:05
malsteevie: perfectionists22:06
steevieYeah, a full green line on adaptations page is cool tho22:06
malsteevie: what android base was that?22:07
steevieIn 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
malmaybe 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.conf22:08
steevieNo, it's a different thing22:08
malsteevie: what is?22:09
malI don't understand what the problem is with fm radio because you don't give any information22:09
steevieIf 15.1 hybris is buildable i can try to cherry-pick my professional 16.0 source-built audio commits22:09
steeviehttps://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 calls22:12
malsteevie: what fm chip does the device have?22:13
steevieMsm8916. But the problem is stock audio hal which requires those parameters, not fm radio itself22:14
steevieMaybe also fm radio but those audio parameters need to be set22:14
malquite odd22:15
steevieYeah, thats why now i build source-built audio ^22:15
steevieWith a professional tfa9895 amplifier hal22:16
steevieBut 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 do22:17
malno wonder people don't port more samsungs when they need all kinds of hacks22:17
steevieYeah, hacks nooo22:18
steevieIm too lazy to fix fm22:18
steevieBut one day ill fix it22:18
steevieYou know any info about xa2 android 8.1 support? Is it device-specific? If no, it can be hackerable😏22:26
r0kk3rzits binderized up the wazoo so it should be fairly portable22:27
r0kk3rzbut it needs an android 8 base or higher22:27
steevieThere is an hybris-15.1 branch on manifest so, that wouldnt be a problem22:28
steevieBut...is that thing closed sources? I mean, do sailfish guys want that thing to be used only on their devices?22:28
r0kk3rzbut im not sure community folk have really poked around with it too much yet22:28
r0kk3rzyeah its closed22:29
r0kk3rzcould be due to myriad, or simply because they want to22:29
malsteevie: 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 radio22:29
steevieDoes sailfish even have fm radio apps?22:30
steevieOn store all radio apps are wlan radios22:30
malyes, the default media app supports fm radio22:30
r0kk3rzthere was also that one kimmoli did22:31
malr0kk3rz: that was just for testing before the official app got support22:31
r0kk3rzit works well enough22:31
r0kk3rzand i dont use the official media app, so it suited my need22:31
malyes, fm radio doesn't really need many features so both of those do pretty much the same thing22:32
steeviePerfectionism is useless when lineage doesnt support your nfc chip. I mean, youll always have that red box on libhybris adaptations page :/22:32
malI use the official app22:32
steevieBtw...what's the status of halium implementation in sailfishos? I heard they could use it about 2 years ago22:36
r0kk3rzno status22:36
steevieSo, no halium?22:37
r0kk3rzi dont think anyone is interested in using halium with sfos22:37
r0kk3rz2 years ago is approx when halium started, and they were trying to get everyone on board22:38
steevieGood. Because it was sad to see how ubports ruined their os with halium22:38
steevieYes, the beginning22:38
r0kk3rztechnically it should be possible, but it would require being decently proficient in both toolchains22:40
r0kk3rzso maybe TheKit is the only person who would do it22:40
steevieOh that thekit guy...nice person22:41
TheKitat this point Halium vs Sailfish way differ mostly in just Android being run in same root or inside LXC container22:42
steevieYou mean unified but you'll never have full hardware working vs not unified but you have a chance to fix your hardware?22:43
r0kk3rzyeah but youd have to do something with mic to build an image the halium way22:43
r0kk3rzbecause they seperate the adaptation from the os layer right?22:44
steevieAnd halium it's not even unified, since when you port it you'll have less hardware working than a normal sailfish port :/22:44
steevieBut nice person eh22:45
TheKitsteevie, unified vs not unified is not that much Halium-level choice, Halium just provides Android parts22:48
steevieYes, but in theory if you installed halium+rootfs you would have everything working, assuming that everything works in lineageos22:49
steevieLike treble22:49
TheKitthat'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 Sailfish22:51
steevieLike the droid-config in sailfish that you want to unify but it's impossible to unify22:53
TheKitr0kk3rz, basically it would replace functionality of droid-hal-init and /system partition, so probably droid-hal-device package gets replaced22:53
TheKitsteevie, 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
r0kk3rzyou will always need device specific configs, its just a question of where they live22:58
steevieIt's impossible to unify everything, thats all. Just go to old porting method22:59
r0kk3rzhalium isnt trying to unify everything23:01
steevieIt is23:02
TheKitwhat it is trying to unify is building Android port bits for UBPorts/Plasma/LuneOS23:02
TheKitanalogue of hybris-hal build + LineageOS system.img in Sailfish terms23:03
steevieNo its trying to unify everything23:03
steevieOtherwise it would use lineage zip like sailfish23:04
TheKitit'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
r0kk3rzsteevie: sometimes you really dont make sense :P23:07
r0kk3rzusing or not using a lineage base image has nothing to do with any unification23:08
r0kk3rzlineage use a single android source tree, you could build that yourself23:08
steevieHalium is not only lineage23:09
steevieIve worked with halium, i know it23:09
r0kk3rzyou have some strange ideas about why it is though23:10
r0kk3rzeven if you know what it is23:10
steevieIt's a modified lineage with only the needed android parts23:10
steevieI KNOW ITTTT23:10
steevieBhushan shah23:11
steevieHe wants to unify everything. Nice person tho23:11
r0kk3rzok, you believe what you want23:11
steevieBtw today its my birthday and i didnt even hear anyone saying happy birthday steevie sailfish porter23:21
r0kk3rzthats sad23:22
steevieYeah but you can remedy ;)23:23
heroic_1https://github.com/fredldotme and me are gonna attempt a halium-8 bringup on sony devices soon-ish23:38
heroic_1at least the boot image generation and chroot launching could be unified23:38
heroic_1as well as shared kernels23:39
heroic_1sf/mer could also learn a thing or two from halium about community involvement and documentation23:40
heroic_1and 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/7323:40
TheKitheroic_1, keep me updated on this, I attempted to get phh-treble inside LXC, it's kinda running, but many things are crashing yet23:43
steeviePhh lol, i know him23:44
heroic_1what base?23:44
heroic_1and which device?23:44
heroic_1r0kk3rz: I'll give you a hint, one is merged and one is stale23:46
r0kk3rzyeah we should really go through those fixup mountpoints prs, theres quite a lot of them23:50
steevieAnd my pull request for them hasnt been merged, yet23:51

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!