rinigus | something is wrong in the current Jolla-latest-SailfishOS_Platform_SDK_Chroot-i486.tar.bz2. tar missing (easy to install though), ubu-chroot missing (which package provides that?). anything else? [was doing full refresh before starting to work on 2.2.x]. nothing seems relevant regarding it in the faq as well | 06:41 |
---|---|---|
rinigus | ... or I managed to make a mistake(s) while unpacking platform chroot. | 06:41 |
rinigus | turns out that android-tools-hadk was not installed in sfos platform | 06:57 |
r0kk3rz | rinigus: yes theres a few things like that, which is a bit annoying | 08:58 |
rinigus | r0kk3rz: ok, then at least its not some local install issue | 09:00 |
r0kk3rz | yeah everyones been tripping up over that one | 09:02 |
rinigus | :) | 09:03 |
elros | spiiroin: there is something wrong in mce. When I cover als sensor ( get "2" value from evdev_trace) then lock phone and unlock, brightness jumps for a while (line 231): https://pastebin.com/avFu2VLW | 11:47 |
elros | so for some reason I get: modules/filter-brightness-als.c: fba_status_sensor_value_change_cb(): sensor: 400 | 12:33 |
elros | I thought mce use /dev/input/event* for als sensor but looks like it use sensorfw | 12:36 |
elros | lux data from evdev_trace and HybrisAlsAdaptor::processSample(const sensors_event_t& data) are correct | 12:44 |
branek_ | What should I do to get all .mount services in sailfish os image? I am missing everything from here: https://github.com/LineageOS/android_device_oneplus_msm8998-common/blob/lineage-15.1/recovery.fstab | 14:02 |
branek_ | Even if I have: TARGET_RECOVERY_FSTAB := $(PLATFORM_PATH)/recovery.fstab in BoardConfigCommon.mk, .mount files are still missing from rootfs, so no /system, etc... | 14:02 |
r0kk3rz | if you create your own mount services you should just be able to chuck them in your sparse in your config repo | 14:11 |
branek_ | Ok, my understanding was that should be generated during build time, from .fstab... | 14:23 |
r0kk3rz | they should be | 14:23 |
r0kk3rz | but clearly they arent | 14:23 |
r0kk3rz | but the end game is that you have .mount unit files in your rootfs, so how they get there doesnt really matter so much | 14:26 |
mal | so then you need to make sure the fstab file is found | 14:29 |
mal | branek_: hybris-boot doesn't know anything about android side fstab variables, I mean that TARGET_RECOVERY_FSTAB is not used in hybris-boot | 14:29 |
mal | hybris-boot tries to search for the fstab files using some rules which might not always work | 14:30 |
branek_ | mal: I see now what you are speaking... Sorry for basic questions, but still getting all pieces... | 14:37 |
ghosalmartin | has anyone ever managed to get the kernel booting in qemu and telnet into it? | 16:05 |
r0kk3rz | should work in theory | 16:12 |
ghosalmartin | but theory is a treacherous thing and becomes see through when you put it on paper :P | 16:25 |
locusf | hypothesis :p | 16:26 |
locusf | theories require evidence | 16:26 |
ghosalmartin | and now i have nothing :P | 16:27 |
ghosalmartin | its all CONFIG_VTs fault and theres no obvious reasons why :( | 16:28 |
ghosalmartin | is there anyway to check that a kernel is atleast booting even if it ends up panicing because it seems this kernel is just corrupt from the onset | 16:29 |
r0kk3rz | you really need uart access | 16:30 |
ghosalmartin | so what your telling me is am fooked :P | 16:31 |
r0kk3rz | but an alternative is to get a kernel of the same version and diff the CONFIG_VT stuff to see if anything is mangled | 16:31 |
branek_ | mal: fstabs were correctly detected during hybris-hal build: /fstab is on device/oneplus/msm8998-common/init/vendor/etc/fstab.qcom device/oneplus/msm8998-common/recovery.fstab | 16:32 |
ghosalmartin | r0kk3rz, well its weird since guhl had a working version, but he has one of those massive configs so can't tell whats required and whats not | 16:32 |
ghosalmartin | r0kk3rz, also is it possible to diff a compiled kernel? | 16:32 |
r0kk3rz | that was an earlier version though wasnt it? | 16:32 |
r0kk3rz | and im sure you can think of a way to dump just the enabled flags from a megaconfig | 16:33 |
ghosalmartin | well am sure a lovely grep would hook a brother up | 16:33 |
locusf | if you really want a binary diff, gunzip the kernels and do a hexdump on them | 16:34 |
locusf | pipe to diff | 16:34 |
locusf | or redirect to files | 16:34 |
locusf | it will help you zilch much | 16:34 |
r0kk3rz | i guess you also want to pay attention to any set to n as well | 16:35 |
ghosalmartin | theres like 5000 entries :P | 16:36 |
ghosalmartin | time for a beet | 16:37 |
ghosalmartin | r | 16:37 |
r0kk3rz | presumably you've tried using that config? | 16:39 |
ghosalmartin | yeah theres errors all over the place | 16:39 |
r0kk3rz | nice | 16:39 |
ghosalmartin | and while I can fix some, i think cpu_time_t was deprecated which makes it all a pita | 16:39 |
ghosalmartin | well may as well attempt it again | 16:42 |
branek_ | Ok, it looks like rpm/dhd/helpers/makefstab is the right thing to process .fstab and get .mount services... | 16:44 |
r0kk3rz | ghosalmartin: it probably wont help, since you've already identified a problem flag | 16:44 |
ghosalmartin | r0kk3rz, thing is it doesnt even break like a normal flag though, it seems to just nuke the entire kernel, wont even call init | 16:46 |
ghosalmartin | no console-ramoops | 16:46 |
ghosalmartin | i mean that must be crashing like super early | 16:46 |
r0kk3rz | yeah thats not all that surprising | 16:48 |
r0kk3rz | if you wanted to print the rest of the kernel init process to the VT, you'd want to start it really early | 16:49 |
ghosalmartin | and am guessing vt is super important i guess itd explain the panic without it | 16:49 |
ghosalmartin | interesting android-recommends.cfg is that config_vt is disabled | 16:52 |
ghosalmartin | The diff you're trying to view is too large. We only load the first 3000 changed files. | 17:02 |
ghosalmartin | that not even fair :P | 17:03 |
locusf | do you happen to have console=ttyFOOBAR in your kernel command line? | 17:14 |
locusf | if you do, its quite useless as kernel cannot allocate a terminal to a tty | 17:15 |
ghosalmartin | locusf, so just tty? | 17:57 |
locusf | no, remove it altogether | 18:26 |
locusf | console and all | 18:27 |
ghosalmartin | yeah no dice there ive had it removed for a while | 18:36 |
_sven | when i'm connected to the gemini via serial console i can see the boot process and after finish that i get a prompt like 130|aeon6797_6m_n: User is "shell". If i try journal -f i get the error "error: ld.so: object 'libdirect-coredump.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored". Any idea how i can see logs? I can't access /run/log/journal/<id>, devel-su doesn't work | 18:38 |
Nokius | o/ | 18:45 |
Nokius | anything to keep in mind when moving from 2.1.3.7 to 2.2.0.29 ? | 19:06 |
r0kk3rz | the csd ini file, but thats it really | 19:18 |
mal | and updating submodules | 19:23 |
r0kk3rz | that goes without saying | 19:26 |
Nokius | aarrgg | 19:29 |
Nokius | somehow I get confused wehn looing into other repos history | 19:29 |
Nokius | mal: why did you set sparse/etc/pulse/xpolicy.conf.d/fmradio.conf to fmradio.conf.disabled ? | 19:38 |
Nokius | your devices has a fmradio | 19:38 |
mal | Nokius: you miss the point of that | 19:42 |
Nokius | mal: yes I do, so if I disable it it means it enabled like vise versa? | 19:43 |
mal | Nokius: I created a symlink that doesn't have .disabled as the file ending so the parser finds the file, if there is only the file with .disabled ending then parser skips that and fm radio is disbaled | 19:43 |
mal | *disabled | 19:44 |
mal | Nokius: it only parses files ending with .conf so the default situation with only fmradio.conf.disabled means fm radio not enabled | 19:45 |
Nokius | okay thanks | 19:45 |
r0kk3rz | mal: for what purpose? | 19:49 |
mal | r0kk3rz: ? | 19:52 |
piggz | mal: comments welcome https://github.com/jdrescher2006/Laufhelden/pull/99 | 19:53 |
* Nokius it's hard to keep track of port | 19:53 | |
Nokius | mal: why did you remove sparse/lib/udev/rules.d/999-droid-vidc.rules ? this is not in dcd? | 20:01 |
mal | Nokius: https://github.com/mer-hybris/droid-hal-configs/commit/e167d7e70b3c795a018990b2e647d0ec1d70e3fa | 20:06 |
mal | Nokius: you should learn to check submodule commit history :) | 20:06 |
Nokius | I do right now :D | 20:07 |
mal | if I remove something it's quite common it's because of some change in submodule | 20:07 |
mal | piggz: we'll need to discuss the naming of the dbus service with people from jolla | 20:08 |
r0kk3rz | does sensorfw do dbus? | 20:10 |
mal | yes | 20:13 |
Nokius | mal: I belive you do so, I was just couriuse thats why I asked ;) | 20:24 |
mal | Nokius: did you really need to led configuration? I only have it because my device has some issues with led | 20:31 |
mal | Nokius: it's not good to just randomly copy things | 20:31 |
Nokius | |-) | 20:32 |
mal | same for the vibrator configuration, did you have very weak keypad feedback in the past? | 20:33 |
Nokius | okay thanks | 20:38 |
mal | Nokius: you didn't answer my question | 20:44 |
mal | Nokius: I need custom vibrator config because feedback from virtual keyboard was not noticeable | 20:45 |
Nokius | mal: no we faced no issue with the vibrator | 20:45 |
mal | Nokius: the led fix was because the blinking didn't work correctly because of a kernel bug | 20:45 |
r0kk3rz | hmm i might try that on scorpion | 20:45 |
mal | Nokius: so you can feel the vibration when you type with virtual keyboard? | 20:46 |
mal | r0kk3rz: which one? | 20:46 |
r0kk3rz | vibra config | 20:46 |
Nokius | mal no I dont | 20:46 |
mal | r0kk3rz: ok, I used the values from xperia x repo as the base and then adapted until I had the same feedback as on xperia x | 20:47 |
Nokius | mh obs gives a No space left on device | 20:48 |
T4 | <abhishek_0> i successfully created 64bit sources ... soon i'll start porting with 64bit sources as base | 20:48 |
mal | Nokius: usually there should be a small feedback from virtual keyboard | 20:48 |
r0kk3rz | yeah pretty sure i broke obs by building new python :) | 20:49 |
Nokius | mal: when I type I feel nothing | 20:49 |
mal | Nokius: maybe test with different values in the feedback config to see if something works, maybe start from this https://github.com/mer-hybris/droid-config-f5121/blob/master/sparse/usr/lib/qt5/plugins/feedback/droid-vibrator-device.ini | 20:50 |
Nokius | mal: okay | 20:50 |
Nokius | mal: thanks | 20:50 |
Nokius | mal: increasing Press ( I assume it's the one when typing) to an higher value did help I still feel nothing | 20:58 |
Nokius | ah looks like the deivce is vibrating after type for a while | 21:02 |
Nokius | :-/ | 21:02 |
piggz | mal: good topic for meeting ... would u like to bring it up? i often cant make them | 21:04 |
piggz | you can link to the repos | 21:04 |
r0kk3rz | does it really need its own service? | 21:05 |
TAMplus39 | Can anyone tell me how and where to symlink mixpaths.xml? | 22:23 |
mal | TAMplus39: what is the problem, it should be quite cleat that you need to create some symlinks in /etc which point to file in /system/etc | 22:46 |
mal | *files in | 22:46 |
TAMplus39 | It always says permission denied | 22:54 |
TAMplus39 | And im directing it to where the device tree has the file | 22:55 |
mal | what exact command are you running? | 22:56 |
mal | what do you mean? | 22:56 |
TAMplus39 | That I dont know what system/etc folder you refer to | 22:57 |
mal | /system/etc/ | 22:57 |
mal | you don't seem to understand how symlinks work? | 22:57 |
TAMplus39 | I only used time ago on OS X really dont know them on linux | 22:58 |
mal | so either on device (in /etc folder) or in config repo sparse (in $ANDROID_ROOT/hybris/droid-configs/sparse/etc) you run ln -s /system/etc/some_filename | 22:59 |
mal | normally it's ln -s target linkname but since the link name we want is the same as the original filename and we run it in the correct folder we can skip link name from the command | 23:01 |
TAMplus39 | Oh, that makes it easier | 23:02 |
TAMplus39 | I was running it as ln -s /system/etc/mixer_paths.xml /etc/mixer_paths.xml | 23:02 |
TAMplus39 | But running ln -s /system/etc/mixer_paths.xml | 23:02 |
TAMplus39 | Did the trick | 23:02 |
mal | are you sure? | 23:03 |
mal | the command you gave works also | 23:03 |
mal | TAMplus39: or did you mean you ran that in your build enviroment and not on the device? | 23:04 |
TAMplus39 | Build environment | 23:04 |
mal | then of course you cannot use the absolute path for the link name | 23:06 |
TAMplus39 | mal: Oh and also I have another question, Building wlan as module is the only way to get wifi working? | 23:08 |
T4 | <adampigg> r0kk3rz, I dont know, thats why im opening up the debate ... seems like a usefull function that allows integration with sports type apps easily | 23:09 |
TAMplus39 | Because enabling kernel modules derps kernel building | 23:10 |
mal | TAMplus39: depends on the device, not all device need it as module but many do | 23:12 |
TAMplus39 | Then I guess I have to get more knowledge on building android kernels to get modules enabled without error :/ | 23:20 |
mal | we really can't help if you don't show the errors | 23:25 |
mal | but anyway it's very late now so not today anymore | 23:25 |
TAMplus39 | I posted it on here a few days ago:c | 23:27 |
TAMplus39 | https://pastebin.com/syrLC2aR | 23:27 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!