| *** ubuntu is now known as Guest41975 | 01:52 | |
| *** Guest41975 is now known as zhxt | 01:53 | |
| wiktorek140 | mal: audio during call fixed. removed audio xml from sparse | 08:40 |
|---|---|---|
| mal | wiktorek140: hmm, which one? | 08:43 |
| wiktorek140 | wait, i will check xD | 08:43 |
| wiktorek140 | mal: /etc/pulse/xpolicy.conf | 08:46 |
| wiktorek140 | i mean it was replaced during building image but that version work | 08:46 |
| mal | oh, so you had some old versiin of that? | 08:50 |
| mal | well that would indeed cause problems | 08:50 |
| wiktorek140 | mal: probably yes, it was copied when i make fixes and updates and forgot to remove | 08:51 |
| ghosalmartin | mal, krnlyng : am making a fresh X build, would it be best to use android 6, or android 8? | 09:24 |
| r0kk3rz | 6 id say | 09:35 |
| r0kk3rz | it would be cool to do an android 8 build though | 09:35 |
| r0kk3rz | ghosalmartin: are you maintainer of hammerhead as well? i saw your name on the repo | 09:36 |
| ghosalmartin | r0kk3rz, not really but I dont mind attempting it, I have a spare device | 09:36 |
| r0kk3rz | yeah it shouldnt need a lot of work to update | 09:38 |
| *** Nokius_ is now known as Nokius | 09:51 | |
| krnlyng | ghosalmartin, if you want to be bleeding edge use 8 | 10:00 |
| krnlyng | ghosalmartin, if you just want to replicate the image use 6 | 10:00 |
| krnlyng | ghosalmartin, but newer is always better right :)? at least newer is more interesting when talking about android :). | 10:00 |
| krnlyng | android apis* | 10:01 |
| mal | ghosalmartin: if you want to use it as a phone then android 6, if not then you can try 8 | 10:02 |
| ghosalmartin | mal, krnlyng : its to put on xda and alike so probably 6 | 10:54 |
| krnlyng | ghosalmartin, if you want to bring android 8 adaptations further then android 8 :) | 11:09 |
| ghosalmartin | krnlyng, ill make the testing one android 6, and the devel android 8 :P | 11:10 |
| OhYash | hi | 11:47 |
| OhYash | doesnt like this app is sending messages | 11:48 |
| OhYash | with proximity sensor enabled, screen goes black during a call. and I cant do anything to bring back.screen until.call ends. (which the other person would have to do) | 11:49 |
| mal | so proximity sensor is not working properly | 11:50 |
| OhYash | mal: it works. Auto brightness works | 11:51 |
| OhYash | but yeah, during calls its like its sending 'dark' reports. | 11:52 |
| mal | display blanking during calls is controlled by proximity sensor, if display doesn't turn on after removing what is blocking proximity sensor then it doesn't work properly | 11:52 |
| OhYash | yep, thats the problem. | 11:53 |
| r0kk3rz | auto brightness is ALS | 11:57 |
| OhYash | oh, then yep | 11:58 |
| OhYash | proximity is not working | 11:58 |
| r0kk3rz | test it with csd | 11:59 |
| mal | did you add the sensor fixes mentioned in faq? | 11:59 |
| OhYash | yep | 12:00 |
| OhYash | wait | 12:00 |
| OhYash | leemi recheck | 12:00 |
| OhYash | the hw-settings.ini file only right? | 12:02 |
| OhYash | I have it. | 12:05 |
| OhYash | the probem occurs with ProxSensor=1 value | 12:05 |
| OhYash | yep csd test shows its 'covered' constantly | 12:34 |
| mal | try cleaning the area on the device where the sensor is | 12:35 |
| OhYash | nope, doesnt help | 12:37 |
| OhYash | it works totally fine on android tho. | 12:38 |
| demonaxsh | Hi, everyone. | 12:45 |
| demonaxsh | I rebuild fs with surfaceflinger (qpa-plugin etc) components: | 12:45 |
| demonaxsh | EGL_PLATFORM=null | 12:45 |
| demonaxsh | QT_QPA_PLATFORM=surfaceflinger | 12:45 |
| demonaxsh | # Determine which node is your touchscreen by checking /dev/input/event* | 12:45 |
| demonaxsh | LIPSTICK_OPTIONS=-plugin evdevtouch:/dev/input/event0 -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap | 12:45 |
| demonaxsh | But now, screen does not switch from bootlogo | 12:45 |
| demonaxsh | https://drive.google.com/open?id=13QDxsatwfqZVlByWQ2R5aJjV8oFs3ehT | 12:45 |
| demonaxsh | test_sf not crashed, there are ideas, what can be problem? | 12:45 |
| mal | do you have the surfaceflinger qpa plugin installed? | 12:46 |
| mal | did it work before? | 12:46 |
| mal | which android base? | 12:47 |
| demonaxsh | android 6.0 | 12:48 |
| demonaxsh | device based on mt6735 (mediatek) | 12:48 |
| demonaxsh | yes, plugin installed | 12:48 |
| demonaxsh | "/usr/lib/qt5/plugins/platforms/libsurfaceflinger.so | 12:51 |
| demonaxsh | /usr/libexec/droid-hybris/system/lib64/libsurfaceflinger.so" | 12:51 |
| krnlyng | demonaxsh, do you have the permission fix? | 12:53 |
| krnlyng | demonaxsh, do you have the LD_PRELOAD? | 12:54 |
| krnlyng | demonaxsh, do you have the surfaceflinger service enabled? | 12:54 |
| Mister_Magister | hello mal krnlyng have a nice day :P | 12:55 |
| demonaxsh | permission? no, for what? for /usr/lib/qt5/plugins/platforms/libsurfaceflinger.so? | 12:56 |
| demonaxsh | LD_PRELOAD - no, without it not worked? or you want say that plugin must first load, and then real libsurfaceflinger? | 12:56 |
| Mister_Magister | demonaxsh: no and no | 12:57 |
| demonaxsh | for libsf_compat_layer.so? | 13:02 |
| demonaxsh | for starting surfaceflinger need droidmedia? | 13:03 |
| mal | Mister_Magister: do you remember where the instruction for surfaceflinger method were? | 13:04 |
| Mister_Magister | i have them in bookmarks but im not at home rn sorry :/ | 13:04 |
| demonaxsh | it's popular question? in faq nothing for this theme | 13:06 |
| demonaxsh | is dark secret of the sith? | 13:16 |
| mal | demonaxsh: nobody has yet found where the recent instructions are, the old quite obsolete instructions have been found though | 13:19 |
| mal | demonaxsh: if you want you can try these, all before and including the big NOTE is obsolete and should not be done https://bpaste.net/show/10d83e7092c0 | 13:30 |
| demonaxsh | ok, I'll try | 13:32 |
| Mister_Magister | mal: demonaxsh: do everything below line 15 (including line 15) | 13:33 |
| Mister_Magister | and it should be fine | 13:33 |
| Mister_Magister | lines above line 15 are obsolate and basically breaking everything | 13:33 |
| mal | Mister_Magister: line 18 is very wrong | 13:40 |
| Mister_Magister | i know :) | 13:40 |
| mal | so why did you say to do it? | 13:40 |
| Mister_Magister | i just fix it automatically :P | 13:40 |
| mal | that package is already included in build_packages.sh | 13:40 |
| Mister_Magister | qt5-qpa-surfaceflinger-plugin? since when | 13:41 |
| Mister_Magister | mal: then from line 22 | 13:42 |
| mal | Mister_Magister: since july 5th | 13:43 |
| Mister_Magister | whoa | 13:43 |
| mal | it was included for android 8 | 13:43 |
| Mister_Magister | im not following very much lately | 13:43 |
| Mister_Magister | no new devices to port and busy with college :P | 13:43 |
| demonaxsh | oh my god... gui worked | 15:36 |
| demonaxsh | but not worked touchs, but it's progress | 15:41 |
| mal | demonaxsh: touch device is defined in /var/lib/environment/compositor/droid-hal-device.conf you just need to find out which device is the correct one | 15:43 |
| demonaxsh | ls -l /dev/input/by-path/platform-10003000.keypad-event | 15:48 |
| demonaxsh | lrwxrwxrwx 1 root root 9 May 29 15:24 /dev/input/by-path/platform-10003000.keypad-event -> ../event0 | 15:48 |
| demonaxsh | but apparently it's hardware buttons | 15:48 |
| mal | demonaxsh: you can either check the names from there if something would hint that it's the touchscreen or just cat the /dev/input/eventX devices one by one and see which one shows something when you touch the screen | 15:50 |
| demonaxsh | yes, thx I already understood | 15:52 |
| wiktorek140 | mal: some clue about fmradio? https://pastebin.com/TBnQSmBX hadk tutorial and faq done | 16:53 |
| wiktorek140 | https://pastebin.com/pJYd9ndF additional logs from journalctl | 16:56 |
| mal | wiktorek140: your kernel driver might be one of those that need either patching or this https://github.com/piggz/qt5-qtmultimedia-plugin-mediaservice-irisradio note that that requires a env var called HYBRIS_FM_INIT_PATH to give path to init | 16:59 |
| wiktorek140 | mal: where i can find patch? | 17:00 |
| mal | wiktorek140: it depends on the kernel | 17:01 |
| wiktorek140 | mal: what if i dont have /sys/module/radio_iris_transport/parameters/fmsmd_set? | 17:03 |
| mal | show your kernel sources | 17:04 |
| wiktorek140 | https://github.com/wiktorek140/android_kernel_motorola_msm8916/tree/cm-14.1 | 17:04 |
| * piggz checks the faw for anything new | 17:07 | |
| piggz | s/faq | 17:07 |
| mal | wiktorek140: probably not related but you do have some old fmradio pulseaudio configs | 17:16 |
| mal | wiktorek140: also you are sure the fm radio works in android? | 17:16 |
| wiktorek140 | mal: not synced repo but i removed and symlinked like in your repo | 17:16 |
| wiktorek140 | mal: yes, it was warking | 17:17 |
| mal | ok | 17:18 |
| mal | the iris-transport is built as module and you verified the module has been loaded properly? | 17:18 |
| mal | wiktorek140: is bluetooth working on that device? | 17:19 |
| wiktorek140 | mal: bluetooth yes, iris-transport build in, not as module | 17:20 |
| mal | try as module | 17:20 |
| wiktorek140 | need to rebuld whole system or only boot and push it to device? | 17:21 |
| mal | wiktorek140: kernel and droid-hal | 17:21 |
| wiktorek140 | so whole system ;p | 17:22 |
| mal | if you want you can manually copy the modules but it's easier to just package the droid-hal rpms and copy them to the device and install | 17:22 |
| wiktorek140 | mal: its a some solution ;) | 17:22 |
| mal | if you think building whole image is easier than installing the droid-hal rpms then go ahead | 17:22 |
| wiktorek140 | mal: impossible to build kernel with iris-transport as module | 17:29 |
| mal | hmm, what error | 17:29 |
| wiktorek140 | https://pastebin.com/uahy7HMd | 17:29 |
| mal | wiktorek140: add here an #else with content "extern int radio_hci_smd_init(void);" https://github.com/wiktorek140/android_kernel_motorola_msm8916/blob/cm-14.1/drivers/media/radio/radio-iris.c#L5247 | 17:32 |
| mal | or just move the extern int radio_hci_smd_init(void); out of the #ifndef MODULE | 17:33 |
| wiktorek140 | mal: something like this? https://pastebin.com/aAVcMUDd | 17:34 |
| mal | yes, that should work | 17:35 |
| wiktorek140 | still the same | 17:37 |
| wiktorek140 | mal: config_radio_iris can be module? | 17:38 |
| mal | not sure, maybe | 17:40 |
| mal | try building also it as module | 17:40 |
| mal | and remove the change you made | 17:40 |
| wiktorek140 | mal: first try build with changes | 17:40 |
| wiktorek140 | mal: complete with succes | 17:41 |
| mal | yep, it seems both have to be modules for it to work | 17:42 |
| mal | also edit the systemd service to modprobe both if needed | 17:42 |
| wiktorek140 | so changes are unnecesary, remove it | 17:43 |
| wiktorek140 | yea, i remember it | 17:43 |
| wiktorek140 | mal: that was strange, module in theory was build, but not packed in kernel | 17:58 |
| mal | ? | 17:58 |
| wiktorek140 | that what i say. module radio-iris-transport was not packed in droid-hal | 17:59 |
| mal | it's in the kernel module package | 18:00 |
| wiktorek140 | no, its not there | 18:01 |
| mal | but it's in out? | 18:01 |
| wiktorek140 | it dont exist in whole android tree on my pc ;/ | 18:01 |
| mal | are modules enabled in your kernel? | 18:02 |
| wiktorek140 | i thing yes because wnal is from modules | 18:02 |
| wiktorek140 | wlan* | 18:02 |
| mal | so you built kernel the usual way using either make hybris-boot or make hybris-hal? | 18:03 |
| wiktorek140 | make hybris-boot | 18:03 |
| mal | does the build output show anything about iris module | 18:04 |
| wiktorek140 | mal: hmm, i dont see anything. just tell that build it and nothing more | 18:05 |
| wiktorek140 | mal: i will try with make hybris-hal and see then | 18:06 |
| wiktorek140 | mal: https://pastebin.com/AaHFjpyB probbly this. i will try to fix | 18:07 |
| mal | so you'll just need to add some #ifndef MODULE around that line | 18:09 |
| wiktorek140 | mal: that help, try to put it in device | 18:10 |
| wiktorek140 | mal: radio work, audio no | 18:20 |
| wiktorek140 | audio on radio of course | 18:21 |
| wiktorek140 | still error connected with headphoneasfmradiolp | 18:22 |
| mal | wiktorek140: are you sure you did the xpolicy change correctly, also depending on the device you might need to change the audio device name | 18:25 |
| wiktorek140 | mal: yes its file provided with droid-config | 18:26 |
| mal | https://github.com/piggz/droid-config-mido/blob/master/sparse/etc/pulse/xpolicy.conf.d/xvars.conf you might need that with input-fm_rx | 18:26 |
| mal | or tuner, which ever works | 18:27 |
| wiktorek140 | mal: tested both, still no change | 18:32 |
| wiktorek140 | mal: can this fix it? https://github.com/kimmoli/droid-config-onyx/commit/e719fa422d9e20c95da83e1f8ccca3a44af60d8b | 18:32 |
| mal | not sure what that was for but you can try | 18:33 |
| wiktorek140 | still nothing | 18:37 |
| mal | did you always reboot after changes? or at least restart pulseaudio | 18:38 |
| wiktorek140 | reboot always | 18:38 |
| wiktorek140 | mal: half sucess xD culprit was bad symlink | 18:52 |
| wiktorek140 | mal: but now in radio output i have mic input | 18:52 |
| mal | which configs do you have now? | 18:55 |
| wiktorek140 | kimmoli patch removed, input-fm_rx stay | 18:57 |
| wiktorek140 | fixed symlink | 18:57 |
| wiktorek140 | mal: fixed, replace input-fm_rx with input-fm_tuner | 19:00 |
| mal | tuner is the default so you can remove the file I think | 19:01 |
| wiktorek140 | ok, i will try it | 19:01 |
| wiktorek140 | works | 19:13 |
| wiktorek140 | mal: so left one thing, mce led diode | 19:27 |
| mal | wiktorek140: what about it? | 19:31 |
| wiktorek140 | mal: config file created, correct path set in it | 19:32 |
| wiktorek140 | but still no blinking | 19:32 |
| wiktorek140 | white, binary led diode | 19:32 |
| mal | does it only have such simple led | 19:33 |
| wiktorek140 | yes | 19:33 |
| mal | does the led have blink file? | 19:34 |
| wiktorek140 | nope. only brightness and control | 19:34 |
| wiktorek140 | both work with echo | 19:35 |
| mal | wiktorek140: only blinking is the problem or does it completely fail? | 19:37 |
| mal | wiktorek140: no max_brightness? | 19:38 |
| wiktorek140 | mal: oh, yes, max_brightness too | 19:38 |
| wiktorek140 | but that doesnt matter, it operate on 0 and 1 | 19:39 |
| wiktorek140 | and completly fail in system notification | 19:39 |
| wiktorek140 | mal: maybe change backend from binary to white? | 19:40 |
| mal | depends on what kind of led it is | 19:41 |
| wiktorek140 | mal: in name - rgb, in specyfication - dont know, in real - binary white diode | 19:44 |
| mal | you can try white | 19:45 |
| wiktorek140 | something other than baceend name should i change? | 19:47 |
| wiktorek140 | hmm, start working, but it blink strange | 19:51 |
| _sven | btw. nice led action on the geminipda while incoming call http://woelk.net/sw/video_2018-07-23_19-39-17.mp4 | 19:51 |
| wiktorek140 | only for miliseconds | 19:51 |
| wiktorek140 | mal: some clues? on binary dont work. on white work strange | 20:11 |
| wiktorek140 | mal: fixed. max_brightness return too high value | 20:20 |
| wiktorek140 | create temp file with 1, and set it in config fix it | 20:20 |
| neothefox | where can I adjust kernel boot options? | 20:25 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!