Sunday, 2018-06-17

TAMplus39Can i dirty flash a new lineage zip flashing my base zip?00:35
MeowDudeholy shit00:51
MeowDudengfd didn't error out while building00:51
MeowDude*guys I am scared*00:52
TAMplus39Hey, how can i add the extra sailfish apps? (calculator, media player and such)00:58
MeowDudeoof sorry01:39
MeowDudeif you can find the actual rpms you can include them in your image via putting them in droid-local-repo and adding the package name to patterns, but as far as I know the actual jolla apps like calculator and weather are copy-right protected. Just sign into your jolla account and deal with the auto download S01:40
MeowDudeoof that sucks, so my Galaxy Nexus display went dark and the notification LED turned on then it rebooted01:41
MeowDudeway to get my hopes up01:42
MeowDudeambient light sensor works too01:42
MeowDudemal: what does this mean? ambient light sensor is working, power button turns display on and off, but it only shows the bootlogo01:42
MeowDudelibminisf is incompatible or missing01:50
MeowDudefbdev works01:51
TAMplus39So this is a new one, network shows as limited02:30
TAMplus39And when i try to enable untrusted software it says it cant connect to merrepo02:46
TAMplus39So rolled back to android for today, i think that im gonna make all of the changes That i have to and recompile a more mature package03:09
shark1mal : abhishek_0: sorry for going offline abruptly. Actually my system shut down due to low battery and it takes time whenever that happens :p03:47
shark1Btw I investigated the sensors, none of them are online03:47
shark1 here is a log of journalctl of sensors only03:48
shark1and sensors are not being initialized03:48
shark1It says few libs not found. But I have those libs but only in 64bit03:49
shark1so does that mean I need 32bit libs?03:49
MeowDudeCBRILD isn't started03:56
shark1MeowDudeCB : Was that a reply to me?03:56
MeowDudeCBwhere do I go from here? hadk says to check init*.rc but I have no idea what to look for03:56
MeowDudeCBalso no that is for me sorry, I am debugging RILD isn't started on maguro03:56
MeowDudeCBbut I might be able to help you let me check the logs03:57
shark1lol how would that help me :p03:57
shark1oh wait03:57
shark1I posted the logs above btw03:57
MeowDudeCBI noticed you said you didn't make the 32bit libraries for sensors. I am pretty sure you have to make the 32bit sensors if you have a 64bit device03:58
shark1Lol I cant make a 32bit lib :|03:59
shark1How can one make a lib of whose sources are not there04:00
MeowDudeCBhave you tried manually building,, and qfp-wakeup.so04:00
MeowDudeCB*thinking* manually grab the sources and put them in $ANDROID_ROOT/external (assuming they go there)04:00
MeowDudeCBcat init.rc04:00
MeowDudeCBgod damnit my bad04:01
shark1ok let me check then04:01
shark1Iam not sure if I can grab sources for sensors04:02
MeowDudeCBWho is the in-house RILD and ofono expert?04:16
MeowDudeCBGalaxy Nexus RILD won't start, and there is no rild or netd init*.rc files. Not only this but /dev/socket is devoid of any rild folders, and /dev doesn't contain any modem related folders04:17
MeowDudeCBI think I found the socket in /dev/alog it has a file named "radio" in it and it seems to house all the rild related goodies, but now I am curious as to why rild won't start04:28
shark1MeowDudeCB : did you try anbox?04:30
MeowDudeCBha ha no, neither of my port devices are even alpha quality04:31
shark1lol how many ports are you doing?04:31
MeowDudeCBjust 204:31
MeowDudeCBNexus 10 and Galaxy Nexus04:31
MeowDudeCBokay so I tried manually starting rild, here is the pastebin of that:
MeowDudeCBit would seem that there are no permissions to start rild related stuffs, how would I go about this..04:33
MeowDudeCBI'll try to change the permissions of rild from twrp... wait... that makes no sense...04:36
MeowDudeCBokay so this is the big ticket error: [grilio] ERROR! Can't connect to RILD: Connection refused04:41
MeowDudeCBsaidanish5: I noticed you had this error in the logs, how did you resolve it?04:41
MeowDudeCBsaidinesh5 ^^04:41
r0kk3rzif rild isnt running, then yeah thats the problem09:01
shark1r0kk3rz hi09:06
malshark1: does test_sensors work?09:06
shark1mal : yes09:06
shark1It shows 0 sensors09:06
shark1The problem is the lib only. Is there any way out?09:07
shark1 test_sensors09:08
r0kk3rzthere should be an androidy sensor service running09:10
r0kk3rzwhich might not be the one called 'sensorservice' if its custom09:11
shark1oh so should I check it in android?09:11
shark1r0kk3rz, here is the earlier log of journalctl of sensors09:12
r0kk3rzlogcat would be better to look at09:13
r0kk3rzsensorfwd is sailfish side, your problem is definitely android side09:17
shark1so how can I go about the problem now?09:18
shark1The problem is the lib09:18
shark1Its 64bit sailfish needs 32bit probably09:18
r0kk3rzidk if binder can do mixed mode like that, maybe it can09:20
shark1But it is still searching the lib in 32bit09:21
shark1I tried shifting 64bit lib in place of 32bit, it complains that it needs 32bit lib09:21
r0kk3rzwhen you say 'it' what exactly?09:24
shark1'it' in last text was, "test_sensors"09:29
r0kk3rzyeah i wouldnt worry too much about that just yet, check the android service09:30
r0kk3rzyou can double check by stracing test_sensors to see what it is loading, not all ' not found' errors are catestophic09:44
shark1will do that now09:46
shark1r0kk3rz, see test_sensors loading quite a few things with "not found" in strace10:22
shark1But does not seem relevant10:22
malshark1: did you enable sensorservice, it might conflict if it's enabled10:30
shark1in init.qcom.rc? Let me check10:31
malshark1: what device is that?10:31
malshark1: also don't mix sensors.qcom with sensorservice10:31
shark1Le max210:31
malthose are different things10:31
maldo you find any sensor*.so files in /vendor or or /system or such10:32
shark1but in 64bit10:32
shark1mal here
shark1sensor*.so but is only in lib6410:35
shark1also where can I check if sensorservice is enabled?10:37
shark1Coz only sensor.qcom is present and no sensorservice10:37
r0kk3rzyeah sensor.qcom is a custom service, so make sure its running and check logcat10:38
malusually sensorservice is not running on device, sensors.qcom is enough10:39
shark1so I tried to trigger sensor.qcom10:41
malshark1: how about you just check if the process is running10:41
shark1in a minute10:42
shark1mal : It is not running
shark1and this is what I see when I run "ps -ef"
shark1so according to "ps" sensor.qcom is running but in logcat, I cant see that10:50
malnot all processes print to logcat10:52
shark1so the service is running then10:55
shark1so, is there any way for me?10:59
malshark1: the first lines in that last paste are confusing, did you start the sensors.qcom manually=11:04
shark1mal : no11:04
shark1I did not start manually11:04
shark1I rebooted the phone before taking the log11:04
malshark1: just to be sure, disable sensorfwd systemd service (systemctl mask sensorfwd), reboot and try test_sensors again, some devices don't like two sensor processes reading the sensors11:07
shark1mal : Did that. test_sensors shows 0 again11:12
shark1Nothing else I can try?11:24
malthere are always possibilies, it just might take a while to figure those out11:32
shark1will keep trying11:35
malshark1: I saw many messages about sensors in your logcat but whether those are critical is not clear11:35
shark1ok. But I remember my sensors worked earlier(atleast rotation and light)11:36
shark1Like 2-3 months ago when I was building sailfish11:36
shark1but after many updates, it isnt working11:37
malshark1: same device and android base?11:38
shark1yes same deive11:38
shark1*device and base11:38
malwhat has changed in that time11:39
shark1I think I should wait for hybris-15.1 since this 14.1 is giving so much trouble for me11:41
T4<abhishek_0> how do i setup OBS ? :-311:52
mal@abhishek_0 check topic "Building things on OBS" in faq11:56
T4<abhishek_0> so what do architecture i have to select for sailfish_latest_armv7hl .. default is armv8el12:06
mal@abhishek_0 not 100% sure, I never use the graphical selector, I just add the target manually to meta
T4<abhishek_0> can i push stuff through terminal... gui is annoying12:47
T4<abhishek_0> *using12:47
malthat is the better way to do it12:47
saidinesh5@abhishek_0 AND
T4<abhishek_0> thanks :')13:50
T4<abhishek_0> okay so .. in droid-hal-$device .. i will build and push the packages .. and rest is taken care off automatically14:02
T4<abhishek_0> right?14:02
malassuming you do everything correctly14:05
T4<abhishek_0> how do i get this stuff
T4<abhishek_0> oh ..14:44
T4<abhishek_0> nvm14:44
malyou only add the _service file to other packages than droid-hal-$DEVICE14:44
T4<abhishek_0> got it .. it built it automatically ..... its cooool af14:45
*** Nokius_ is now known as Nokius15:03
T4<abhishek_0> few build errors
T4<abhishek_0> how should i resolve them ?16:56
vknecht@abhishek_0; something along these lines ;
mal@abhishek_0 add suitable project config17:06
malPrefer: droid-config-$DEVICE-bluez4 or bluez5 depending on which you use17:06
mallike here
T4<abhishek_0> gst-libav also fails
malyou can clearly see the reason for the failure in the output17:26
T4<abhishek_0> ffmpeg ?17:32
T4<abhishek_0> this stuff was not in my build .. i never built them offline .. and never caused issue17:38
T4<abhishek_0> weird17:38
vknechtis sfos supposed to handle configuration over sms ? just got one after checking voicemal for first time with new sim17:42
vknechtsomething like //VVM:STATUS with many fields like srv IP adress, ports, password...17:43
mal@abhishek_0 why do you need gst-libav?17:45
T4<abhishek_0> for audio17:53
malwhat audio exactly17:54
T4<abhishek_0> media playback .. like playing youtube and stuff17:55
malyou really should try to fix gst-droid17:56
T4<abhishek_0> abranson had to do it.... stutters and colours issue18:01
T4<abhishek_0> *will18:02
*** moralrec1rdings is now known as moralrecordings18:04
T4<abhishek_0> let me try removing gst-omx and libav on device .. and see what happens18:05
T4<abhishek_0> mal this happens .... gst-droid is is completely fine from my side, fixes have to be made in upstream, piggz and meow also has this issue.18:33
T4<abhishek_0> lbt , lbt- : ping ping ping ;P18:38
T4<abhishek_0> please patternise nemo:devel:hw:wingtech:wt8804718:38
vknecht@abhishek_0: now wait and relax ? :-)18:47
duncan^So the HADK document claims that it is important to use the SDK target.18:51
duncan^Why is this?18:51
duncan^Does this still apply? (I know what it says, but it's been 8 months or so)18:51
malduncan^: use
duncan^So I guess the adaption guide is out of date?18:54
duncan^Thanks for the clarification18:54
malit usually doesn't give exact version, just an example18:54
malduncan^: as you can see the hadk pdf mentions that it's a special case for the time when 2.1.1 was the current version18:55
malthe guide just is updated very rarely18:56
abransonI wonder if for these device there's no colour conversion blob, and the colour format coming out of those decoders isn't one we know about.19:39
abransonit'd be helpful to know exactly what colour format it is, but that would require some LOG_NDEBUG in the android sources maybe19:40
ghosalmartinabranson, any idea if the btusb.c is strictly for bt devices that are mainly dongles?20:13
vknechtabranson, just a logcat like this is not enough ?
vknechtwith some instructions, I could try that LOG_NDEBUG thing20:17
T4<abhishek_0> vknecht i cant wait and relax, many commitments i have to fulfill :P21:30
vknecht@abhishek_0: this is our burden :-)21:50
MeowDudekrnlyng: any known fixes for rild not starting on the android side?23:14
MeowDudeI foolishly thought the socket for maguro was /dev/socket/netd instead of realizing that /dev/socket/rild was spawned by rild itself.23:14

Generated by 2.17.1 by Marius Gedminas - find it at!