| *** amccarthy is now known as Guest4562 | 00:03 | |
| *** amccarthy_ is now known as amccarthy | 00:03 | |
| T42 | <Teleram2022> Hello everybody 👋 | 10:07 |
|---|---|---|
| T42 | <CarbontedCaffeine> I have a question regarding the feasibility of porting Samsung devices. I have an A52s with a max stock firmware of A14 and builds of LOS 21. | 12:24 |
| T42 | <Danct12> why are you EVERYWHERE | 12:24 |
| T42 | <CarbontedCaffeine> Shhhh. | 12:24 |
| T42 | <morciatka> oh hello Danct12 | 12:24 |
| T42 | <CarbontedCaffeine> Don't mind me Dan. | 12:25 |
| T42 | <Danct12> and of course you're here too (re @morciatka: oh hello Danct12) | 12:25 |
| T42 | <morciatka> ohhahahah (re @Danct12: and of course you're...) | 12:25 |
| T42 | <CarbontedCaffeine> We're active in Mister_Magisters group chat. | 12:25 |
| T42 | <morciatka> not only there, but also fedi and so on (re @CarbontedCaffeine: We're active in Mist...) | 12:25 |
| T42 | <CarbontedCaffeine> Yes, yes. | 12:26 |
| T42 | <Danct12> yeah :) we all met on fedi | 12:26 |
| T42 | <CarbontedCaffeine> Anyway yeah I'm looking to port SFOS to my A52s. | 12:26 |
| T42 | <morciatka> actually... I've been actually following your work since 2020 on twitter, postmarketOS on lavender and so on (re @Danct12: yeah :) we all met o...) | 12:27 |
| T42 | <Danct12> haha, that was long ago (re @morciatka: actually... I've bee...) | 12:27 |
| T42 | <Danct12> old times | 12:27 |
| T42 | <CarbontedCaffeine> Dan has been everywhere. | 12:27 |
| T42 | <CarbontedCaffeine> XD | 12:27 |
| T42 | <Danct12> i'm still using lavender as my daily driver.. went through two battery replacements | 12:28 |
| T42 | <Danct12> and now the buttons are kind of toast but nothing you can't fix hahahahaah | 12:28 |
| T42 | <Danct12> the buttons on the chassis is broken, but the button board is still fine | 12:29 |
| T42 | <CarbontedCaffeine> Well loved :) | 12:29 |
| T42 | <morciatka> as for this, the hybris tree for 21 should be up already? I believe it could be doable probably (re @CarbontedCaffeine: I have a question re...) | 12:30 |
| T42 | <Danct12> but not really that well taken care of :) (re @CarbontedCaffeine: Well loved :)) | 12:30 |
| T42 | <CarbontedCaffeine> Mainly asking because I haven't seen many Samsung ports. (re @morciatka: as for this, the hyb...) | 12:30 |
| T42 | <CarbontedCaffeine> At least modern ones. | 12:30 |
| T42 | <Danct12> it definitely had suffered from being dropped in one way and another, but i've replaced the screen protector many times too | 12:30 |
| T42 | <morciatka> we just like other brands more | 12:31 |
| T42 | <CarbontedCaffeine> Real | 12:31 |
| T42 | <morciatka> I haven't dailydriven a Samsung phone since 2014, so that's that | 12:31 |
| T42 | <CarbontedCaffeine> The A52s was a really nice device. | 12:32 |
| T42 | <CarbontedCaffeine> *Is | 12:32 |
| T42 | <Danct12> many brands offer better specs for about the same price as a budget samsung device, so yeah (re @morciatka: we just like other b...) | 12:32 |
| T42 | <CarbontedCaffeine> Samsung ended putting a Qualcomm chip in the A52 during covid. Dunno if it was supply issues. But this thing is great. | 12:33 |
| T42 | <morciatka> a person who sits pretty well in my heart has had one until a certain Windows on ARM experiment messed with the UFS (re @CarbontedCaffeine: The A52s was a reall...) | 12:33 |
| T42 | <CarbontedCaffeine> The only problem I have currently is the proprietary VoLTE firmware. | 12:34 |
| T42 | <morciatka> oh yeahhhh, that's what I heard being broken on LOS ports on most Samsung devices | 12:34 |
| T42 | <CarbontedCaffeine> oops, the WiFi isn't working. | 12:34 |
| T42 | <CarbontedCaffeine> just flashed LOS 21 | 12:34 |
| T42 | <Danct12> don't want to do soc shaming here but apparently many people agreed that qualcomm devices performed better than exynoses (re @CarbontedCaffeine: Samsung ended puttin...) | 12:36 |
| T42 | <CarbontedCaffeine> I think that's just an objective fact. | 12:36 |
| T42 | <CarbontedCaffeine> Exynos is kinda lame | 12:36 |
| T42 | <morciatka> something tells me that the Exynos in the Galaxy Note 7 performs better than the 820/821 that would've been in it if it was a chinese/american unit. But that's probably because MSM8996 was a pile of steaming mess | 12:37 |
| T42 | <CarbontedCaffeine> I think I solved the issue with WiFi. A major bootloader update happened. The firmware might be different. | 12:51 |
| T42 | <CarbontedCaffeine> So there's two bootloader versions for Android 14. | 12:52 |
| T42 | <CarbontedCaffeine> UGH. | 12:52 |
| T42 | <Danct12> oneui 8 💀 (re @CarbontedCaffeine: I think I solved the...) | 12:52 |
| T42 | <CarbontedCaffeine> It never got Android that | 12:53 |
| T42 | <CarbontedCaffeine> *it never got that update | 12:53 |
| T42 | <Danct12> lucky you | 12:53 |
| T42 | <CarbontedCaffeine> I might have to target LOS 22 if I can't get LOS 21 to work. | 12:55 |
| T42 | <CarbontedCaffeine> Okay LOS 22 fixed it | 12:57 |
| T42 | <CarbontedCaffeine> So it is a firmware issue. | 12:57 |
| mal | I probably should push manifests for newer hybris bases | 13:08 |
| T42 | <CarbontedCaffeine> Please, if you could mal. Is there any way I can access the sources for hybris-22 wip? | 13:09 |
| *** poetaster is now known as Guest4609 | 13:22 | |
| mal | I pushed a manifest now for hybris-22.2, I just started a test build, I haven't built it in a while | 13:45 |
| T42 | <CarbontedCaffeine> Thx will check back if I have problems | 14:01 |
| mal | @CarbontedCaffeine one thing, use this fork of libhybris when building https://github.com/mlehtima/libhybris the branch pr-testing | 14:07 |
| T42 | <CarbontedCaffeine> Noted, thank-you | 14:09 |
| mal | and I use "breakfast lineage_CODENAME-bp1a-user" when building, replace codename of course | 14:10 |
| mal | probably just "breakfast CODENAME" also works but will result in userdebug build usually | 14:10 |
| mal | I'll try to get more of the android 15 and 16 changes merged next wekk | 14:16 |
| mal | *week | 14:16 |
| mal | my test build was successful | 14:27 |
| T42 | <nc1x72> Anyone having the kernel repo (with latest commits) used to compile fp5 build? | 16:21 |
| T42 | <nc1x72> | 16:21 |
| T42 | <nc1x72> Found some of the repositories on git but not the kernel sources. | 16:21 |
| mal | @nc1x72 I forgot to push the latest versions there | 16:28 |
| mal | for FP5 https://github.com/mlehtima/android_kernel_fairphone_qcm6490/commits/hybris-23.2/ | 16:30 |
| mal | for FP4 https://github.com/mlehtima/android_kernel_fairphone_sm7225/commits/hybris-23.2/ | 16:30 |
| mal | note that the android side builds I use are actually lineage 21 based but I used kernel from lineage 23.2 | 16:32 |
| T42 | <nc1x72> Ok got it! Thanks! Are the other repos on your git up to date? I’m porting to a device quite similar to fp5 and anything from fp5 will be helpful. It’s a Nothing Phone 1. | 16:35 |
| T42 | <nc1x72> | 16:35 |
| T42 | <nc1x72> Was even able to boot the fp5 build blindly on it with UT kernel (+ some minor changes). Obviously most things didn’t work. So, I’m trying to setup the repositories and compile from sources as it should be. | 16:35 |
| T42 | <nc1x72> | 16:35 |
| T42 | <nc1x72> The repos for fp5 were quite helpful in booting and fixing UT on Spacewar. | 16:35 |
| mal | yeah, the droid-config repo is the latest one I use, droid-hal-version and droid-hal img-boot also | 16:36 |
| mal | but the img-boot repo is for lvm based builds | 16:37 |
| mal | droid-hal repo is not there but I can push that also | 16:38 |
| mal | I now pushed droid-hal repos also, but note that those are also for lvm based build and need slight changes for non-lvm based builds | 16:42 |
| T42 | <nc1x72> I thought the current fp5 build was lvm. No? | 16:50 |
| mal | it has | 17:32 |
| mal | just meant that if that is used as example for some other device then it needs the taken in to account | 17:32 |
| T42 | <nc1x72> Ok got it! Thanks | 17:44 |
| T42 | <CarbontedCaffeine> We're using the same soc @nc1x72. 778G? | 19:55 |
| T42 | <nc1x72> SM7325 is essentially a QCM6490 without LTS from qcom. So, technically, yes. | 20:17 |
| T42 | <CarbontedCaffeine> Not sure how much my Samsung port is going to be able to share with the FP5 | 22:09 |
| T42 | <edp_17> @CarbontedCaffeine , what samsung model is that? | 22:28 |
| T42 | <moworola> Samsung custom firmware in the big 26 is wild | 22:31 |
| T42 | <nc1x72> Even if you happen to have a Samsung with QCM6490, whether it will be able to boot a rootfs made for fp5 is anyone’s guess. Samsung tends to heavily customize their phones, even on kernel level, making them hard to work on compared to other devices. I have a Samsung A52s with 778G. Can’t even get UT to work on it! | 22:42 |
| T42 | <CarbontedCaffeine> Sorry, it is a A52s 5G with a 778G. | 22:52 |
| T42 | <CarbontedCaffeine> Max of Android 14. | 22:52 |
| T42 | <CarbontedCaffeine> @nc1x72 that's what I was thinking. I think since Samsung used a lot of their own versions for vendor firmware that some things may not work at all. | 22:53 |
| T42 | <CarbontedCaffeine> I know they use their own VoLTE firmware so that will never end up working in SFOS. | 22:53 |
| T42 | <nc1x72> Yes, I have the same device. An A51 and a Pixel C tablet too. Samsung’s are the hardest. Getting SIM card detected is a task on its own… They (used, not sure if still relevant) to have their own RIL implementation. | 22:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!