T4 | linusdan was added by: linusdan | 01:57 |
---|---|---|
T4 | <BirdZhang> @linusdan line 31: ERROR: CONFIG_IKCONFIG_PROC is invalid | 02:03 |
T4 | <linusdan> Hi Bird! … So, I do not know if I put the configuration in the wrong place or it was the same value … In mer-kernel-check passed without errors | 02:07 |
T4 | <BirdZhang> you need change it in your kernel, and rebuild hybris-boot | 02:08 |
*** ChanServ sets mode: +v T4 | 02:13 | |
T4 | Mufga1 was added by: Mufga1 | 02:15 |
T4 | <linusdan> (Photo, 447x28) http://149.202.119.142:9090/llXWvGt0RG.png Is already done. And compiled also with this configuration. … I can not even put it as N because hybris-boot needs it … I'm lost :/ | 02:16 |
T4 | <BirdZhang> can you share your kernel source github link ? | 02:16 |
T4 | <linusdan> Of course! … Its here: … https://github.com/linusdan/android_kernel_samsung_smdk4412 | 02:17 |
T4 | <BirdZhang> https://cateee.net/lkddb/web-lkddb/IKCONFIG_PROC.html | 02:19 |
T4 | <BirdZhang> CONFIG_IKCONFIG_PROC depends on: CONFIG_IKCONFIG && CONFIG_PROC_FS | 02:19 |
T4 | <BirdZhang> so need enable CONFIG_IKCONFIG and CONFIG_PROC_FS | 02:19 |
T4 | <BirdZhang> https://github.com/linusdan/android_kernel_samsung_smdk4412/blob/hybris-14.1/arch/arm/configs/lineageos_i9100_defconfig#L78 | 02:20 |
T4 | <linusdan> THANKS! … I'll look the others too! Did not know I had a summary for kernel dependencies. I searched before and did not find it! … Can you suggest any book so I can learn more about kernels? I do not understand almost anything | 02:32 |
T4 | <BirdZhang> https://public.etherpad-mozilla.org/p/hot-hadk and https://public.etherpad-mozilla.org/p/faq-hadk and merproject.org logs are very helpful. i know few about kernels. | 02:35 |
T4 | <linusdan> My heart beat faster … 😍😍😍😍😍😍😍😍 … THANKS THANKS THANKS ❤️❤️❤️ | 02:39 |
T4 | <BirdZhang> you are welcome ;) | 02:40 |
Umeaboy | Hi! | 03:41 |
Umeaboy | The instructions in the HADK to do export PLATFORM_SDK_ROOT=/srv/mer followed by curl -k -O http://releases.sailfishos.org/sdk/installers/latest/Jolla-latest-SailfishOS_Platform_SDK_Chroot-i486.tar.bz2 seems to contain a typo or am I wrong? | 03:42 |
Umeaboy | I mean the first thing you do is to add export PLATFORM_SDK_ROOT="/srv/mer" into the hadk.env file. | 03:42 |
Umeaboy | That contains quotes. | 03:43 |
Umeaboy | I'm sorry if I'm wrong. | 03:44 |
T4 | Null0101 was added by: Null0101 | 03:49 |
T4 | louisdemedicis was added by: louisdemedicis | 04:23 |
Umeaboy | Can anyone confirm if that's the case or not? | 05:12 |
T4 | louisdemedicis was added by: louisdemedicis | 06:41 |
T4 | WaseemAlkurdi was added by: WaseemAlkurdi | 06:48 |
T4 | dohniks was added by: dohniks | 08:40 |
*** ChanServ sets mode: +v T4 | 08:44 | |
mal | Umeaboy: what typo? | 10:06 |
wdehoog | hi, I have audio problems on bacon. when playing music from streams using qmultimedia (shoutcast, somafm) the | 11:52 |
wdehoog | audio always has hickups. This has always been a problem. | 11:52 |
wdehoog | I have a patch for qmultimedia that adds support for QT_GSTREAMER_PLAYBIN_FLAGS | 11:52 |
wdehoog | and a config file .config/qtmultimedia/settings.conf with support for | 11:52 |
wdehoog | flags, buffer-duration, buffer-size, ring-buffer-max-size, connection-speed | 11:52 |
wdehoog | when I use buffer-size=256000 , flags=0x182 the audio is ok (no hickups) | 11:52 |
wdehoog | Nobody else seem to suffer this problem so maybe there is a much better solution. | 11:52 |
wdehoog | adding the playbin buffer also drastically speeds up filling the buffer of the qml audio object | 11:58 |
T4 | <MarcoDS_bit> Hi all again, could you please help me with this error? https://pastebin.com/Ckh4n1BB | 13:05 |
mal | that file should be provided by external/vim | 13:20 |
T4 | <MarcoDS_bit> Tried re-syncing external/vim but I get the error anyway | 13:22 |
T4 | <MarcoDS_bit> Mhhh | 13:22 |
T4 | <MarcoDS_bit> Oh and I don't have vim in my manifest.xml is that normal? | 13:23 |
mal | it should be in the snippets manifest | 13:25 |
mal | https://github.com/mer-hybris/android/blob/hybris-15.1/snippets/lineage.xml | 13:25 |
T4 | <MarcoDS_bit> Yep it is there and it is uncommented, but not working🤔 | 13:28 |
mal | @MarcoDS_bit have you ever made a successful build yet? | 13:33 |
T4 | <MarcoDS_bit> Nope, just re-downloaded all the stuffs for building sailfish | 13:34 |
mal | can you give your local manifest | 13:34 |
T4 | <MarcoDS_bit> Pastebin or file? | 13:35 |
mal | pastebin is fine | 13:35 |
T4 | <MarcoDS_bit> :P … https://pastebin.com/8Befyy4k | 13:37 |
mal | I mean local manifest, not the actual manifest | 13:38 |
mal | local manifest as in the file where you have the device repos | 13:38 |
mal | in .repo/local_manifests | 13:39 |
T4 | <MarcoDS_bit> Ouch sorry, https://pastebin.com/bKPdA6nL | 13:45 |
T4 | <linusdan> Hi all, … I was able to solve the kernel problem! Now I have this problem: … https://pastebin.com/0anGubgz | 13:46 |
mal | @linusdan do you use latest build target? | 13:52 |
T4 | <linusdan> @MarcoDS_bit [Oh and I don't have vim in my manifest.xml is …], If all dependencies for your device are not met, the repository clone will be requested. Do until the compilation stops fill the patience :) … While at manifest file: Yes, to avoid downloading unnecessary things | 13:55 |
T4 | <linusdan> @mal [@linusdan do you use latest build target?], Yes, 3.0.0.8 | 13:55 |
T4 | <linusdan> Mer-hybris repositories are also up-to-date | 13:59 |
mal | @MarcoDS_bit the vendor repo is wrong, neither path or name should have whyred, the repo is vendor specific not device specific | 14:05 |
T4 | <linusdan> In name="TheMuppets/proprietary_vendor_xiaomi/whyred" exclude whyred | 14:12 |
T4 | <linusdan> If you just want the whyred folder, it would be better to make a fork and delete what you do not need | 14:16 |
*** ChanServ sets mode: +v T4 | 14:27 | |
T4 | <MarcoDS_bit> Ouch yeah I'm changing it now, but could it be related to the vim problem? | 15:34 |
T4 | <linusdan> No, just the path error | 15:39 |
r0kk3rz | wdehoog: make a pr in mer and talk to abranson about it | 15:46 |
T4 | <linusdan> rokk3rz, did you mean me or Marco? | 15:51 |
T4 | <MarcoDS_bit> @linusdan [rokk3rz, did you mean me or Marco?], None of us | 15:52 |
mal | I saw the wim error in channel logs from quite a while back and they just worked around it in an ugly way | 16:13 |
T4 | <MarcoDS_bit> Manually copying files? | 16:15 |
mal | yes | 16:15 |
wdehoog | r0kk3rz: first I'd like to know if this is a problem on other devices as well | 16:19 |
mal | wdehoog: is there some app that can be used for easy testing | 16:20 |
wdehoog | mal: for example sailsoma (from openrepos). but I see this problem for more then a year on bacon so I doubt it also happens on another device | 16:23 |
r0kk3rz | wdehoog: yeah, thats why i said talk to andy about it | 16:28 |
r0kk3rz | its ok if its uncommon, being able to tweak things in configs is useful | 16:30 |
mal | wdehoog: how often do you hear those hiccups in the audio? | 16:34 |
mal | I had some during the first 10-20 seconds of playback but then it seems ok | 16:35 |
wdehoog | yes at the start it is most prominent, but it takes more then 20s for me to go away | 16:38 |
wdehoog | mal: high bitrate streams (320 mp3) almost never reach 100 bufferprogress | 16:39 |
wdehoog | mal: for me with a small buffer (256K) the problem is gone | 16:40 |
mal | wdehoog: which channel uses 320 bitrate? | 16:40 |
wdehoog | ma: with other apps, I created shoutcast-sailfish, try to remain qml only | 16:41 |
mal | ok | 16:42 |
wdehoog | some streams in the Electronic | Techo list have 320 | 16:42 |
wdehoog | but the current version of my app behaves weird due to buffering | 16:42 |
mal | but even with that quick test I made it seems that buffer could use improvements | 16:45 |
wdehoog | mal: thanks for testing. lets see what abranson has to say. I guess now it is holidays | 16:48 |
T4 | <linusdan> I solved my problem of the 'geoclue-providers-hybris' repository by reversing the last pull request ☺️ | 17:15 |
mal | ok, so it probably need newer release, maybe the next that will be made available or something | 17:28 |
T4 | saukkom was added by: saukkom | 18:03 |
T4 | <MarcoDS_bit> New error, https://pastebin.com/CPEg2fbQ mhh | 18:09 |
T4 | <MarcoDS_bit> Ok solved using the ugly way lol | 18:24 |
T4 | <srmane4444> Ох его опять нету | 18:27 |
T4 | Carmelo (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) was added by: Carmelo (MISSING @USERNAME! telegram.org/faq#usernames-and-t-me) | 18:31 |
T4 | <MarcoDS_bit> pt.2 https://pastebin.com/Z3ckuSuq | 18:33 |
T4 | <linusdan> The error for the glory! … sed not create ks file … https://pastebin.com/Q5XvDmYk | 18:38 |
mal | you missed one > | 18:43 |
mal | there should be one > before $KS near the end of sed command | 18:44 |
mal | i.e. forwarding the output to file defined by $KS | 18:44 |
Umeaboy | mal: When you begin with making the hadk.env file you add export PLATFORM_SDK_ROOT="/srv/mer" and then when you get to the PlatformSDK installation you do export PLATFORM_SDK_ROOT=/srv/mer | 18:47 |
Umeaboy | I don't know about you, but I'm missing quotes. | 18:48 |
mal | does it really need quotes in the latter case? | 18:52 |
Umeaboy | I'm not an expert so you tell me. | 18:53 |
mal | never heard anyone having issues so I assume that is fine | 18:54 |
Umeaboy | OK. | 18:56 |
r0kk3rz | quite sure they are equivalent | 18:56 |
Umeaboy | Any chance of having my PR merged? https://github.com/mer-hybris/hybris-boot/pull/157 | 18:56 |
r0kk3rz | once we know its right | 18:57 |
mal | first of all squash the commits to one and make sure the commit message follows the usual format in most of the commits [codename] Add Some device to fixup-mountpoints | 18:57 |
Umeaboy | mal: I can't find the Squash and merge option in my PR. | 19:03 |
r0kk3rz | should really go through all those PRs at some point | 19:04 |
mal | Umeaboy: git rebase -i some_hash and then do the needed stuff to commit list and after the commits are ok force push to github | 19:05 |
mal | r0kk3rz: indeed, many seem ok | 19:05 |
r0kk3rz | i find it easier to use the HEAD~X macro, so for the last 5 commits you do HEAD~5 | 19:06 |
mal | that works also | 19:06 |
mal | Umeaboy: there are many guides online how to do squashing using git rebase | 19:06 |
mal | Umeaboy: why did you close the PR, like I said you should have just force pushed to the same branch you used and the PR would have updated automatically | 19:15 |
Umeaboy | I opened a new one with just one commit. | 19:18 |
mal | you should learn the basics on git so that is not needed in the future | 19:20 |
mal | Umeaboy: why did't you follow the commit syntax I told? | 19:20 |
Umeaboy | I could've done that, but chose to start over instead. | 19:21 |
mal | so now you can learn how to change the commit message using git commit --amend and then git push --force | 19:21 |
Umeaboy | Right. I was aware of the git commit --amend command from before. I just don't use it. | 19:22 |
r0kk3rz | why not? | 19:22 |
mal | amending is very common thing to do | 19:22 |
mal | so is rebasing | 19:22 |
mal | and interactive rebasing | 19:23 |
Umeaboy | Why rebase if you can undo what you've done and learn NOT to do the mistakes again? Just saying. I'm not expecting you to agree, it's just how I work. | 19:26 |
r0kk3rz | because its less effort :P | 19:27 |
mal | consider it this way, if others review the changes they would have to start over as they cannot see what changed to the previous version if you always make new PRs, also you rarely get finished code on first try, it's easy that typos happen or that others think there is a better way to do the same thing so modifying the PR is very common | 19:28 |
r0kk3rz | yeah, github is set up for that kind of process | 19:29 |
Umeaboy | Yeah, I just prefer stuff to be as close to perfect as it can get before it gets merged so you won't have to update it much more than needed. | 19:29 |
mal | that might work for simple changes but not for anything bigger | 19:29 |
mal | you just need to learn that rebasing and amending is going to be needed quite often | 19:30 |
Umeaboy | Yeah, and my PR was simple this time. | 19:31 |
T4 | <linusdan> linusdan: <mal> The error persists. The file is generated, but not read. | 19:31 |
r0kk3rz | dont be so precious, you know its not important when mal says 'just amend it' :P | 19:31 |
Umeaboy | Yeah. I know. Problem solved now so now I'll just wait for it to be merged. | 19:32 |
mal | Umeaboy: but you did't rewrite the commit message again yet | 19:34 |
mal | *didn't | 19:35 |
kimmoli | (and it is "Add" not "Added") | 19:36 |
kimmoli | dont tell what you did, tell what the commit does | 19:36 |
mal | that's what I said when I told the correct format: [codename] Add Some device to fixup-mountpoints | 19:38 |
Umeaboy | Does it look OK now? | 19:41 |
mal | Umeaboy: what did I say about amending | 19:42 |
mal | and no | 19:42 |
mal | the commit message is still wrong | 19:42 |
Umeaboy | I don't use the terminal. I do it straight to the github website. | 19:42 |
mal | well then it won't work | 19:43 |
mal | how is it so difficult to use [codename] Add Some device to fixup-mountpoints | 19:43 |
mal | i.e. in your case [maple] Add Sony Xperia XZ Premium to fixup-mountpoints | 19:44 |
mal | the dual and single sim versions probably use the same codename | 19:44 |
Umeaboy | Yeah, they do. | 19:45 |
Umeaboy | Unfortunatelly. | 19:45 |
*** ChanServ sets mode: +v T4 | 20:28 | |
abranson | wdehoog, mal: fine tuning those buffers sounds good. leszek did some adjustments there in the past that we keep as a patch. | 20:31 |
abranson | just checked - that was deactivating the max-size-time | 20:33 |
wdehoog | abranson: this is my "fix" https://api.merproject.org/package/view_file/home:wdehoog/qtmultimedia/_service:tar_git:001-configure-pipeline-properties.patch?expand=1 | 20:34 |
abranson | wdehoog: is that affecting the same thing but from the higher end? | 20:35 |
abranson | https://git.merproject.org/mer-core/gstreamer/blob/master/rpm/deactivate_max_size_time.patch | 20:35 |
wdehoog | abranson: looks like it. I only wanted changes for the qml mediaplayer and wanted to see which setting would help so that is why I used a settings file | 20:37 |
abranson | might be a good idea to add those values to leszek's patch and see if it helps. some things use gst directly after all. | 20:46 |
tortoisedoc | abranson : are you mantainer of sb2+ | 21:06 |
tortoisedoc | s/+/? | 21:06 |
wdehoog | abranson: you mean for my phone (oneplus one) only? I hate all those hardcoded stuff. | 21:06 |
wdehoog | abranson: maybe something like in /var/lib/environment/nemo/60-multimedia.conf ? | 21:06 |
wdehoog | but then for gstreamer | 21:06 |
tortoisedoc | abranson : at least from the mantainers list you show up; would you be interested to take a look at this mr : https://git.merproject.org/mer-core/scratchbox2/merge_requests/16 | 21:09 |
tortoisedoc | (its a two-liner fixing a missing dont expand last path item flag on the remove gate ) | 21:10 |
mal | tortoisedoc: afaik usually having a mer bug id in the commit message is wanted | 21:12 |
tortoisedoc | mal : hmhm ok | 21:27 |
tortoisedoc | mal : where can i fill in a mer bug? | 21:27 |
tortoisedoc | there was a bugzilla somewhere iirc | 21:28 |
mal | https://bugs.merproject.org/ | 21:28 |
tortoisedoc | thanks mal just got there myself .) | 21:28 |
mal | there is the scratchbox2 component in Mer core category | 21:29 |
mal | so file it under that | 21:29 |
tortoisedoc | mal : done , https://bugs.merproject.org/show_bug.cgi?id=1997 | 21:36 |
merbot | Mer bug 1997 in scratchbox2 "The bitter end expansion: Last path of symlink is always expanded" [Critical,New] | 21:36 |
tortoisedoc | mal : how can I link it to my mr? | 21:37 |
tortoisedoc | i recall from bitbucket, jira tickets are automagically linked to commits via the id's | 21:39 |
tortoisedoc | i dont know if something similar is available for bugzilla / gitlab | 21:40 |
mal | tortoisedoc: just add MER#1997 to the end of the commit message, preferrably to the first line (so it shows nicely) | 21:41 |
mal | tortoisedoc: maybe reformat the commit message so the first line contains a short message and any further longer description in the following lines | 21:42 |
mal | tortoisedoc: also check the other commits in sb2 repo for the normal formatting i.e. [something] in the beginning of the commit message | 21:43 |
mal | that makes it appear properly in changelogs | 21:44 |
tortoisedoc | mal : added [gates], as the change pertains to taht | 21:44 |
tortoisedoc | *that | 21:44 |
tortoisedoc | also added MER bug in it | 21:45 |
mal | tortoisedoc: in commit message, not PR title (which can be anything but usuall close to commit message) | 21:46 |
tortoisedoc | moved | 21:46 |
tortoisedoc | now what? :) | 21:47 |
tortoisedoc | mal : ^ | 21:47 |
mal | commit message still looks wrong, you only added [gates] to PR title | 21:48 |
mal | maybe the commit message could be [gates] Add missing flags to remove gates. MER#1997 and then on second line you can say why | 21:49 |
mal | or something like that | 21:50 |
mal | so the first line is not too long | 21:50 |
mal | it's messy in my opinion if the message shown here is not complete but instead part of it is hidden https://git.merproject.org/mer-core/scratchbox2/merge_requests/16/commits | 21:51 |
tortoisedoc | mal : you think title is ok? | 21:52 |
mal | yes, PR title is ok, just adapt the commit message | 21:53 |
tortoisedoc | _b | 21:53 |
mal | tortoisedoc: sorry for bugging, I just like nice and clean commit history :) | 21:54 |
tortoisedoc | hehe it's ok :) im not allergic to nitpicking :) | 21:54 |
tortoisedoc | mal : how about now? | 21:55 |
mal | did you force push the change? | 21:55 |
tortoisedoc | edited in-place | 21:55 |
tortoisedoc | (the commit comment / title I mean) | 21:56 |
mal | I can't see any difference in the commit message, you always just edit the PR title | 21:56 |
tortoisedoc | but yes, I force-pushed a few times | 21:56 |
tortoisedoc | hmm | 21:56 |
tortoisedoc | I have | 21:57 |
tortoisedoc | Add the flag to avoid resolution of last part of path; see MER#1997 | 21:57 |
tortoisedoc | as the first comment line | 21:57 |
tortoisedoc | packed and juicy :D | 21:57 |
mal | you are mixing things, I'm talking about te git commit message not the PR | 21:57 |
mal | so git commit --amend and then edit the commit message and then git push --force | 21:58 |
tortoisedoc | ;_; | 21:59 |
tortoisedoc | will do! | 21:59 |
mal | I thought it was clear what I meant when I said commit message | 22:00 |
tortoisedoc | its too late for this, my bad :P | 22:00 |
mal | np | 22:00 |
tortoisedoc | mal : whats the max line size in commit history usually? 80 chars? | 22:01 |
tortoisedoc | mal : repushed | 22:02 |
tortoisedoc | mal : btw thanks for taking the time to guide me through this :) | 22:02 |
mal | tortoisedoc: 80 or 72 I think | 22:06 |
mal | tortoisedoc: looking good now, let's wait for someone who maintains that to check it | 22:07 |
T4 | <linusdan> mal: i9100 is coming! My error while trying to generate the kickstarter file was because it had extra space between the \ and the $ KS hahaha 👌🏼 🙃 … Tkanks! | 22:15 |
mal | @linusdan you have to be careful when copying multiline commands from hadk | 22:16 |
T4 | <linusdan> I'll take more care at other times :) | 22:23 |
T4 | <linusdan> Another problem. In the root filesystem compilation appeared: … Q: Failed to apply RootPasswordConfig, skip and continue? … If I confirm, will I be able to configure later or will I have to do something else? | 22:42 |
r0kk3rz | you mean running mic? | 22:45 |
T4 | <linusdan> yes, i'm running mic :) | 22:45 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!