| T42 | kskarthik was added by: kskarthik | 06:45 |
|---|---|---|
| T42 | <kskarthik> Hello everyone! Is installing platform sdk mandatory for porting sailfish os to new device? | 06:47 |
| Thaodan | Kinda or you can't build anything | 06:52 |
| T42 | <kskarthik> Ok, thanks for the answer! | 07:29 |
| T42 | <kskarthik> i have a spare device motorola sanders which i will try to port !! | 07:29 |
| T42 | <kskarthik> @sledgram are you there !? | 07:31 |
| T42 | <kskarthik> sledges: ping !! | 07:31 |
| piggz | with fingerprint unlock ... first press wakes up, second unlocks .... anyway to have it all in one? | 09:39 |
| spiiroin | piggz: not really, atm. iirc there is a task about such thing, but... some background info can be found from tjc: https://together.jolla.com/question/209614/fingerprint-reader-unlimited-retries-when-display-is-off/?answer=210577#post-id-210577 | 09:44 |
| spiiroin | i.e. what we have now is: when device lock is not using fp for auth/unlock -> mce steps in and uses it for waking up (and mce must not unlock device) | 09:46 |
| rinigus | do we have a resident expert on /vendor/etc/mixer_paths.xml? I need to adjust mic gains to avoid echo during a call and would like to know which knobs to turn | 10:18 |
| rinigus | commit that I am reverting: https://github.com/sonyxperiadev/device-sony-apollo/commit/ee4982625e2720669eb3e513f9cb4f02618b8df9 | 10:19 |
| rinigus | more specific questions regarding knobs at https://github.com/sonyxperiadev/bug_tracker/issues/688#issuecomment-815149063 | 10:19 |
| piggz | rinigus: on a similar topic, do you know how to increase volume of speaker output ... its v quiet on pro1 | 10:20 |
| piggz | spiiroin: thx | 10:20 |
| Thaodan | rinigus: jusa might now that | 10:21 |
| rinigus | piggz: regarding speakers maybe this will help: https://github.com/sonyxperiadev/bug_tracker/issues/411#issuecomment-518236303 | 10:22 |
| rinigus | but we could both wait in that "jusa come and help us out" line | 10:22 |
| T42 | <kskarthik> Please help with this err | 12:44 |
| T42 | <kskarthik> ```PlatformSDK karthik@ALIPL5159:~$ ubu-chroot -r $PLATFORM_SDK_ROOT/sdks/ubuntu | 12:44 |
| T42 | <kskarthik> mount_bind /var/run/dbus: None of these exists on your host - please report this bug | 12:44 |
| T42 | <kskarthik> Env setup for sanders``` | 12:44 |
| T42 | <zinstack625> @kskarthik what kind of distro are you running that dbus doesn't exist on the host? | 12:46 |
| T42 | <kskarthik> ubuntu 20.04 | 12:46 |
| T42 | <zinstack625> Is it ubuntu server? | 12:47 |
| T42 | <kskarthik> @zinstack625 [Is it ubuntu server?], desktop | 12:47 |
| T42 | <kskarthik> but dbus is there in my system | 12:48 |
| T42 | <kskarthik> dpkg -l | grep dbus shows it | 12:48 |
| T42 | <zinstack625> Okay, then your SDK installation might be broken. Sfossdk should invoke the needed mounts. Try reinstalling sdk | 12:49 |
| T42 | <kskarthik> ok | 12:50 |
| T42 | <kskarthik> thanks for the help | 12:50 |
| T42 | <kskarthik> @zinstack625 [Okay, then your SDK installation might be brok …], also, which hybris version should we pick up for android 10 devices? | 12:54 |
| T42 | <zinstack625> 17.1 | 12:54 |
| T42 | <kskarthik> @zinstack625 [17.1], Thanks! | 12:55 |
| T42 | <kskarthik> anyone has chroot compatible `repo` tool? latest repo does not work due to min python ver requirement | 13:33 |
| rinigus | @kskarthik: just use repo on your regular Linux. no need to do it in chroot | 13:37 |
| T42 | <kskarthik> ok, thanks! | 13:37 |
| T42 | Stellar_Eagle was added by: Stellar_Eagle | 14:34 |
| T42 | <gibcheesepuffs> @zinstack625 [17.1], Is 17.1 booting to ui on any device yet? | 14:36 |
| T42 | <Stellar_Eagle> @kskarthik [Please help with this err | 14:42 |
| T42 | <Stellar_Eagle> PlatformSDK karthi …], It seems to do with 4.0.1.48 called latest. Doesn't show this error on Platform SDK Chroot 3.4.0.24 in Ubuntu 20.10. Avbl at releases.sailfishos.org/sdk/installers/3.3.6/. | 14:42 |
| T42 | <kskarthik> @zinstack625 [17.1], I chose base android ROM pixel experience. Is that compatible with hybris 17.1 branch ? | 15:45 |
| Thaodan | Try | 15:52 |
| Thaodan | There is no hybris-17.1 branch for libhybris just master | 15:54 |
| Thaodan | which is compatible with aosp-10 | 15:55 |
| T42 | <kskarthik> Thaodan: oh ! | 16:00 |
| T42 | <kskarthik> but i could see the hybris-17.1 in the repo? | 16:02 |
| Thaodan | I was talking about libhybris | 16:28 |
| Thaodan | about what were you talking? | 16:28 |
| T42 | <zinstack625> Ah, libhybris is fine at master I think | 16:35 |
| rinigus | Thaodan: if I want to update system/vendor AOSP10 builds with new mixer_paths and pull latest updates from Sony (such as new camera parameters), what would be the best way to proceed? | 17:33 |
| rinigus | get new branch of android from mer-hybris and update tagged manifest? as well as fork all 3 repos with mixer_paths? | 17:34 |
| rinigus | and use them in my android build... | 17:34 |
| Thaodan | in which repos are the changes? | 17:49 |
| rinigus | Thaodan: device-sony-apollo,akari,akatsuki,tama | 18:14 |
| rinigus | probably others as well | 18:14 |
| Thaodan | https://github.com/mer-hybris/android/pull/132 | 18:16 |
| Thaodan | if the commits in the q_mr1 branch it should come | 18:16 |
| rinigus | Thaodan: thank you very much! | 18:20 |
| rinigus | any idea on how to revert mixer xml? I can do it manually in my tree, but that is probably not the best way :) . although, I can always document it | 18:20 |
| rinigus | (and yes, it does seem to pull the changes nicely) | 18:22 |
| T42 | * Youssef_Hesham_V | 18:22 |
| Thaodan | Well should they not revert it? | 18:22 |
| rinigus | maybe they should. surely for apollo, but I haven't tested on others. let's see. I will do tmp substitution and document it in the build instructions. and then we will act according to the response and tests | 18:25 |
| Thaodan | I wonder why only for apollo and not for other tama based devices? | 18:25 |
| rinigus | I assume that they don't see these issues on xz3 - as far as I understood, that where it started from | 18:26 |
| rinigus | but I would suggest to reset mixer to earlier setting for all tama devices and later adjust if needed | 18:27 |
| rinigus | at least for our port | 18:27 |
| Thaodan | strange I wonder what is different, it is the same soc. | 18:27 |
| T42 | <LxZero> To whom you are talking? | 18:28 |
| Thaodan | Sony | 18:28 |
| rinigus | no clue. maybe mic is quieter in speaker mode, as it is so. or maybe some other changes done later changed it. | 18:28 |
| rinigus | let's see how it evolves. at least we know how to solve it without any black magic on blobs | 18:29 |
| T42 | <LxZero> What this bot doing? | 18:30 |
| rinigus | Thaodan: I can see you don't update android_tag in your update. is that fixed now | 18:30 |
| rinigus | ? | 18:30 |
| Thaodan | It is the ref for tagged manifest | 18:30 |
| Thaodan | if you use the non tagged you get all the latest changes in q_mr1 anyway | 18:30 |
| rinigus | I do use tagged from hybris. but I wonder if it is planned to bump refs/tags/android-10.0.0_r41? or is it non-relevant now? | 18:32 |
| rinigus | ... with every repo using a tag | 18:32 |
| Thaodan | device repos use q_mr1 tag not the android tag | 18:35 |
| rinigus | Thaodan: syncing leads to "device-sony-griffin update-ref: fatal: 6734a393f25b131f1d52cd3cbbf58f71b29f154d^0: not a valid SHA1" | 18:36 |
| rinigus | re tags - thanks for explaining | 18:36 |
| Thaodan | Hm I will look into that later | 18:37 |
| rinigus | Thaodan: 'd' was missing: d6f09a43539e799f8b19eba632fccd9125702e75 | 18:38 |
| rinigus | ... hmm, different id, not just d | 18:38 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!