Sunday, 2019-01-06

*** ChanServ sets mode: +v T402:04
T4<It_sMike> mal : fmradio just playing back the microphone, even restarting the pulseaudio doesn't help. any idea about this07:47
T4<It_sMike> ?07:47
*** ChanServ sets mode: +v T408:45
T4<adampigg> tracing through the wlan driver is _loads_ of fun to fgure out why a random mac is assiged on startup!10:59
T4<It_sMike> Nevermind mal :), just fixed it ( Finally ! )11:58
mal@It_sMike I assume the fix was adding the needed symlink to /etc/pulse/xpolicy.conf.d ?12:29
T4<It_sMike> nope, it was already added on that time12:30
T4<It_sMike> Made some changes on fmradio.conf12:31
T4<It_sMike> Will upload them for you once I finished building new system :)12:31
malso then the input device?12:31
T4<It_sMike> Hmm... can't get your meaning?12:33
malwhat did you change?12:34
T4<It_sMike> Made some changes to fmradio.conf under the /etc/pulse/xpolicy.conf.d directory: …
malwhich lines?12:40
T4<It_sMike> I add every single line that I sent for you to that file :)12:41
malwhat lines did you change from the original file?12:41
T4<It_sMike> Let me see mal....12:42
T4<It_sMike> :D The original one were empty12:45
malso where did you get the content then?12:46
malcome on, the original was a symlink so you obviously compare it to the file it pointed to12:47
T4<It_sMike> Get them from github xD12:47
malunless you really had a empty file instead of symlink12:47
T4<It_sMike> maybe...12:47
malwhere are your repos12:47
r0kk3rzare you trying to update the cancro port?12:48
T4<It_sMike> Yep12:49
r0kk3rzmaybe talk to Nokius then :)12:49
malthat has no such file12:49
r0kk3rzand maybe saidinesh512:49
T4<It_sMike> Where can I find them !?12:49
malthe other branch has a file12:49
malbut maybe you should try adding the symlink12:50
T4<It_sMike> mal : It was deleted in the last commit I guess12:50
malfmradio.conf pointing to fmradio.conf.disabled12:50
T4<It_sMike> mal : symlink was just like this...12:50
T4<It_sMike> I have to run pactl set-source-port source.primary input-fm_rx everyt ime to fix the radio12:51
malso you didn't read what it says in the beginning of the file where it pointed12:54
malyou probably should use the symlink and add this to the same folder
T4<It_sMike> Maybe :D12:55
T4<It_sMike> just get confused o-o12:56
maladd the symlink and
malnothing else12:57
T4<It_sMike> give me a moment to check everything from the first mal!12:57
T4<It_sMike> Something is really wrong :/12:58
T4<It_sMike> Guess I find it out :D13:00
T4<It_sMike> Let me test the broken config again...13:01
Benclark006I'm getting somewhat confused when it comes to chapter 5.313:18
Benclark006do I just run ls -l /dev/13:18
Benclark006(on adb shell)13:18
malyou check what you have in the fstab file and then find the actual device nodes for those13:22
Benclark006ok, thanks13:22
malbetter add all just in case13:22
Benclark006ah ok13:23
Benclark006thank you13:23
malso check the base path you are looking for in fstaB13:24
malsometimes it block/platform/*/by-name/ but sometimes block/bootdevice/by-name13:25
malthen make fixup-mountpoints based on that13:25
Benclark006wait so how do you make fixup-mountpoints13:25
malcheck the existing entries in fixup13:26
malit should be quite simple13:26
Benclark006so you just run ls -l /dev/13:28
Benclark006and that's it?13:28
Benclark006or is there a step i'm missing here13:28
abransonadampigg: with the sonys the wlan and bt mac had to be read from the ta with a special tool. macaddrsetup i think it's called. if that wasn't run it'd use a random one.13:35
malBenclark006: did you check fstab what path you are supposed to find?13:36
Benclark006i don't think so13:36
Benclark006should i do that first?13:36
r0kk3rzabranson: sounds like a sony specific thing13:42
Benclark006ok sorry13:46
r0kk3rzBenclark006: you notice how in the fixup-mountpoints its a sed command that is run13:47
r0kk3rzthat sed runs on the fstab, so it kinda needs to match whats in there13:48
T4<It_sMike> Mal thanks a loooot :) , and sorry for being much noob today, putting xvars.conf file under the xpolicy.conf.d fixed the problem.13:51
Benclark006ok i think it's working now13:52
*** ChanServ sets mode: +v T414:04
mal@It_sMike so now you have that file and the symlink also15:07
Benclark006sorry for all the questions but google isn't producing many good answers16:49
Benclark006when i run repo sync it returns error: in `sync --fetch-submodules`: revision stable/lineage-15.1 in LineageOS/android_kernel_lge_mako not found16:49
Benclark006** repo sync --fetch-submodules16:49
Benclark006regular repo sync doesn't work either16:50
Benclark006here's my mainfest file16:52
T4<elros34> as you can see there is no stable/lineage-15.1 branch:
T4<elros34> use lineage-15.1 instead16:55
Benclark006i still get the same error D: error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS/android_kernel_lge_mako not found16:55
malBenclark006: try without --fetch-submodules17:04
Benclark006will do17:05
Benclark006that worked, thanks17:20
Benclark006ok great i've got more problems17:30
Benclark006when i run breakfast $DEVICE it returns all this
Benclark006so then i googled it and i found an xda post ( which said to add TheMuppets/proprietary_vendor_lge to my manifest so then i did and now i get a different error which is in the above gist17:32
Benclark006and it's giving me a huge headache so i was wondering if anyone knew a solution17:33
malwhich android base are you using?17:35
malare you sure you used correct base when doing repo init?17:35
Benclark006oh whoops17:36
Benclark006that would explain it17:36
Benclark006i'll try try again17:36
maljust do repo init again using correct branch and the repo sync17:37
malno need to remove anything17:37
malBenclark006: maybe we need a very big note in hadk that people will make sure they use correct branch17:42
malalthough it says that17:42
malbut it's quite rarely anyone uses wrong branch17:42
Benclark006yeah i'm just terrible at reading17:59
Benclark006among other things17:59
Benclark006extra headaches: i still get basically the same error after correcting the branch thing18:12
malBenclark006: what exactly did you do before that? did you run repo init with correct parameters and then repo sync? and both were successful?18:30
malBenclark006: show your local manifest18:31
malin .repo/local_manifests folder18:31
T4Andreu (MISSING @USERNAME! was added by: Andreu (MISSING @USERNAME!
Benclark006mal: yes, both were successful18:38
Benclark006i ran repo init -u git:// -b hybris-15.118:38
malBenclark006: show your local manifest from .repo/local_manifests18:39
Benclark006nevermind, i found out what i've done wrong18:40
malalso make sure there is no .repo/local_manifests/roomservice.xml18:41
Benclark006ok, thanks18:41
T4<linusdan> mal - hi mal! … Today compiled the sailfish by changing some parameters in the kernel. Recognize the device, but with the command 'lsusb-v | grep iSerial' does not return. … There were some compilation errors, but I think it's not important. Can you take a look when you can? Links of pastebin: … build test 5 log:
T4RWbMc … dmesg:
T4<linusdan> * does not give the desired return19:23
r0kk3rzwhat do you mean compilation errors?19:25
malstill no sign of the sailfish kernel init in the dmesg19:26
T4<linusdan> r0kk3rz: in line 382 for example … There is other, I don't know if influences19:29
T4<linusdan> mal: What do you suggest I do?19:30
r0kk3rzyeah ignore those, thats just mic spewing garbage like usual19:31
malyes, mic is not the problem here19:31
r0kk3rzwhat device is this?19:32
T4<linusdan> Hahahahaha ok19:33
T4<linusdan> the device is i910019:33
r0kk3rzdrop the grep, and just print lsusb -v19:34
r0kk3rzwith the phone connected and on of course19:34
T4<linusdan> appears the things of laptop19:37
r0kk3rzthere should be some entry there for the phone19:41
r0kk3rzif not, something is very wrong19:41
r0kk3rzapparently you can get uart from the usb on that device, that could also be quite useful19:43
T4<linusdan> Thank you! I will try to look for and make one … Here where I live it is complicated to find specific things of electronics … Too expensive too … I hope this is not19:55
T4<linusdan> Is it because you do not mount the default fstab? …
T4<linusdan> init, in the case19:57
T4<elros34> you can also enable one by one configs for kernel, most reported by kernel-checker are needed by sailfish, initramfs needs only few19:57
r0kk3rzyeah thats a fair point20:00
T4<linusdan> Enable everything recommended by mer-kerkel-check and follow your tip by disabling CONFIG_CGROUP_MEM_RES_CTLR … Still the same thing20:00
r0kk3rzdoes it have a notification led?20:02
T4<elros34> kernel might have broken configs, for example for cm-13 I I had broken CONFIG_VT and CONFIG_DEVTMPFS20:02
T4<elros34> so its better to start with clean android kernel20:02
T4<linusdan> rokk3rz: not have, only sensor20:03
r0kk3rzlame, thats another trick, to try and turn on the LED at a specific point20:04
T4<elros34> maybe vibra instead LED :P20:05
r0kk3rzhooray the bot is dead20:06
Benclark006when i try to run repo sync again it returns fatal: duplicate path device/lge/mako in /home/ben/hadk/.repo/manifest.xml20:07
Benclark006is there a fix for that?20:07
*** ChanServ sets mode: +v T420:07
Benclark006here's the manifest.xml file in question
r0kk3rzyes, remove the duplicate path in your manifest20:07
T4<linusdan> I'll activate the usb again in the tree and test :)20:08
T4<It_sMike> mal : yes, both of them are present in that directory :)20:08
T4<It_sMike> @linusdan Did you get boot Dan ?20:08
r0kk3rz@linusdan btw just rebuild and flash the boot.img, no need to go through the rest of it20:09
T4<elros34> if you mean init*rc then it's not the issue. You are not even in initramfs.20:09
T4<It_sMike> mal : the problem just caused by that xvars.conf file. when I put it in there everything fixed :D20:10
T4<linusdan> mike: Now it's easier to eat 1 kg ice cream than seeing boot sailfish 😅20:11
T4<It_sMike> lol 😄20:11
T4<linusdan> r0kk3rz: I'm going to do this! … I'll be back in a little while20:13
kimmoliomnom icecream...20:19
T4<It_sMike> kimmoli : lol xD20:19
T4<NotKit> @linusdan just to confirm, do you know if your device has normal boot.img format? I remember someone porting to i9100g and that device had initramfs stored inside kernel during compilation and abootimg format completely unused20:35
T4<NotKit> could you give link to any working boot.img for your device?20:36
T4<linusdan> TheKit: no have idea … link of boot.img:
T4<NotKit> @linusdan you have same with that device. boot-lineage.img is actually zImage, not abootimg20:56
T4<NotKit> you would need some workarounds to include hybris-boot initramfs into kernel and then flash kernel onto boot partition, not hybris-boot.img20:57
maloh, there are such odd devices20:59
Benclark006is CONFIG_SCHEDSTATS usually needed?21:02
malfocus on the errors, not warnings21:10
r0kk3rzi would not have thought to check that21:12
T4<adampigg> @eugenio_g7 , mal: fixed random mac issue with 2 line patch \o/21:32
T4<eugenio_g7> \o/ awesome21:33
r0kk3rzgogo superpiggz21:33
malwhat was needed?21:33
T4<adampigg> mal,
T4<adampigg> after much tracing and printing, i found that it reads the mac, then overwrites it with a random one!21:41
T4<It_sMike> Thanks Adam for sharing :)21:43
mal@adampigg so that driver doesn't support writing mac later?21:43
*** kimmoli is now known as Guest449421:49
*** kimmoli__ is now known as kimmoli21:49
kimmoliis that ifdef correctly placed?21:49
kimmolielse branches to DHD_TRACE ?21:50
malgood point21:55
mal@adampigg ^21:55
r0kk3rzit must get set again later though, since you said the adapter had it right21:55
T4<adampigg> There is a driver info struct, and an instance struct....22:17
T4<adampigg> The instance one gets the correct mac when connman attaches, but that seems too late....22:18
T4<adampigg> The driver info struct loads the mac then overwrites it22:18
T4<adampigg> Yrs, should be line above!22:19
T4<adampigg> I did that when cleaning up all my other stuff!!22:20
r0kk3rzhmm, your driver looks a lot different to mine22:22
r0kk3rzoh you stoles it from sony kernel?22:23
T4<adampigg> Yes22:25
T4<adampigg> With added features like acpi!22:31

Generated by 2.17.1 by Marius Gedminas - find it at!