| *** ced117_ is now known as ced117 | 06:56 | |
| ArnoRU | Hello. I have a question about porting. Can I use Android 12L as a base for porting? I don't really know the differences between A12 and A12L, but my phone supports only LineageOS 19.1 to LOS 22.1 (officially). I would not risk to port on android 13-14. | 10:28 |
|---|---|---|
| Mister_Magister | I'm not sure whats android 12 L but you can use android 12 | 10:32 |
| Mister_Magister | you can use lineage 19 to 21 | 10:32 |
| ArnoRU | Mister_Magister, google said it is android 12, but with big screen support (after 12L it has been merged to main brunch) | 10:51 |
| Mister_Magister | then pay no attention to L | 10:56 |
| ArnoRU | Ah, okay. I'll use this then | 11:14 |
| ArnoRU | May i ask, how do i need to find a kernel for my device? I Have xiaomi 11 lite 5g ne (lisa). It has official support of LOS. I found device tree in LineageOS/android_device_xiaomi_lisa, but when I'm searching for LineageOS/android_kernel_xiaomi_lisa or LineageOS/android_kernel_xiaomi_sm7325 I found nothing. On official page of lineageos my CPU called Qualcomm sm7325. What's wrong? Why I cant find any kernel in the official LOS repo? | 11:27 |
| Mister_Magister | check the dependencies | 11:34 |
| Mister_Magister | https://github.com/LineageOS/android_device_xiaomi_lisa/blob/lineage-22.2/lineage.dependencies | 11:35 |
| Mister_Magister | https://github.com/LineageOS/android_device_xiaomi_sm8350-common/blob/lineage-22.2/lineage.dependencies | 11:35 |
| Mister_Magister | and voila https://github.com/LineageOS/android_kernel_xiaomi_sm8350 | 11:35 |
| ArnoRU | Ughh... Why it uses the different name? Why sm8450 if cpu is sm7325? | 11:36 |
| Mister_Magister | maybe they're the same thing who knows | 11:38 |
| Mister_Magister | they look almost same in specs so they could be REALLY similar | 11:39 |
| Mister_Magister | 8350 is clocked higher it seems | 11:39 |
| ArnoRU | wait. sm8450 kernel will not help me. only for lineage 22.2 | 11:41 |
| Mister_Magister | where did you get 8450 from? | 11:41 |
| Mister_Magister | https://github.com/LineageOS/android_kernel_xiaomi_sm8350/tree/lineage-19.1 | 11:42 |
| ArnoRU | AH. misspeled | 11:43 |
| Mister_Magister | Like i got two devices one with 4G another without, one snapdragon 400 another snapdragon 410 but they both use snapdragon 400 kernel, sometimes two model numbers are basically same thing | 11:44 |
| ArnoRU | fine though if it will work. what is not fine is i have no proprietary for 19.1 and have no option to extract them. so, i'm moving to los 20 | 11:48 |
| Mister_Magister | might as well go straight to 21 xd | 11:50 |
| ArnoRU | I think lower is better | 11:50 |
| Mister_Magister | not necessarily :P lower = older kernel | 11:51 |
| ArnoRU | and? | 11:51 |
| ArnoRU | does old kernel is not working fine with sfos? | 11:52 |
| ArnoRU | btw, haven't anyone tried to build a bundle like GSI? and can it be created or only native install with no other options? | 11:55 |
| ArnoRU | btw, haven't anyone tried to build a bundle like GSI? and can it be created or only native install with no other options? / | 11:56 |
| T42_ | <TheVancedGamer> mal: could you post the output of vulkaninfo of an SFOS device please? | 12:21 |
| mal | @TheVancedGamer https://pastebin.com/N97WnGRs | 12:32 |
| T42_ | <TheVancedGamer> ok, I'm confused now | 12:32 |
| T42_ | <TheVancedGamer> so I have the same extensions exposed, but running `vkcube-wayland` doesn't actually render anything on screen | 12:32 |
| mal | hmm | 12:32 |
| T42_ | <TheVancedGamer> it's just an empty window | 12:32 |
| mal | need to see about building vkcube-wayland, where is source of that? | 12:33 |
| T42_ | <TheVancedGamer> I just installed vulkan-tools package in apt repos | 12:33 |
| T42_ | <TheVancedGamer> that package also provides vulkaninfo for me | 12:33 |
| mal | ok, I think I might not have that built | 12:34 |
| Mister_Magister | mal: would you be so kind and poke someone about the hbm patch? | 13:22 |
| Mister_Magister | it's been months | 13:22 |
| mal | Mister_Magister: is the commit message and PR title accurate anymore, that only does configurable path now? | 13:30 |
| Mister_Magister | yes, per request, but i couldn't get it to work, hence i asked for example config | 13:30 |
| Mister_Magister | either i could do hbm all day every day or no hbm ever | 13:31 |
| mal | so what did you change in the als config file in your tests? | 13:34 |
| Mister_Magister | many things and none of them worked | 13:36 |
| Mister_Magister | putting 500 in every spot = HBM all day, putting 256 in every spot, which should result in HBM being set to 1 and brightness being set to 0 did not work, putting in numbers from 0 to 510 in every profile, did not work, changing interpolation so that from 1/3 onwards numbers are greater than 255 did not work. I also tried many other things that I do not remember and none of them worked and at this point i have no idea how does | 13:46 |
| Mister_Magister | it work or how does spiiroin think it works | 13:46 |
| mal | every spot as in which entry in the config file? | 13:48 |
| mal | LevelsProfile? | 13:49 |
| Mister_Magister | yes | 13:50 |
| mal | and the lux values match to some degree what you get from sensor? | 13:50 |
| mal | I mean the range of those | 13:51 |
| Mister_Magister | sure sensor goes 5000+ | 13:51 |
| mal | ok | 13:51 |
| Mister_Magister | i did mess with BrightnessLed LevelsProfile0 as well | 13:51 |
| Mister_Magister | you'd think that if sensor is at 5000, automatic brightness is set to max so profile 0, and you put in last place value higher than 255 which should put 1 in the hbm place it would work but it does not | 13:54 |
| mal | so did you try adding some debug prints if verbose logging is not helpful to see what kind of values it really uses | 13:59 |
| Mister_Magister | i tried everything mate, I have no idea how it works but spiiroin seems confident that if you put values they'll be used so I asked for sample config | 14:01 |
| Mister_Magister | I'm sure if he provides one it will all work just fine | 14:01 |
| Mister_Magister | the code is so mangled i cannot make head or tailis of it | 14:01 |
| mal | so so that hbm_and_level is never anything above 255? | 14:03 |
| Mister_Magister | unless you put 500 in every spot | 14:03 |
| Mister_Magister | I would also like to point out that DEFAULT_HBM_TIMEOUT is not used anywhere, nor have I seen any timeouting functionality | 14:03 |
| mal | what is the value of hbm_and_level when 500 is used? | 14:03 |
| Mister_Magister | I don't quite remember as it was months ago but it did write 1 to hbm path | 14:04 |
| T42_ | <adampigg> rinigus: looking at your plugin commits .. is it possible for one plugin to support both the hidl and aidl interfaces? | 21:01 |
| mal | of course it is, it just needs detection for it | 21:10 |
| T42_ | <adampigg> I thought so looking at the code | 21:13 |
| mal | that is how I have done other binder packages like gps, sensors, nfc, and also the jolla volte plugin | 21:17 |
| mal | main ofono binder plugin is the exception | 21:17 |
| mal | examples for doing autodetection can be found in those geoclue hybris plugin, sensorfw and nfc-binder-plugin repos | 21:19 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!