Tuesday, 2018-08-21

echo_salikhey guys ... ihave a question...what will be my port arch? my device is a sd 425... it says armv8... so i should type armv8 in that?06:55
echo_salikor are ther eany suffixes?06:55
echo_saliksailfish doesnt support 64 bit arms?07:20
echo_salikok... went through some posts... it is supported... but i dont see v8 tageting tools in the `sdk/latest`07:32
r0kk3rzyou want armv7hl08:12
* sledges sleighs in08:20
sledgesTheKit: done https://build.merproject.org/project/users/nemo:devel:hw:xiaomi:hermes08:21
sledgesmal: lbt: I've created the repo for steeeve [1] long time before your conversation on 23rd July, but he'd never checked channel logs/OBS and thought it still doesn't exist08:21
sledges[1] https://build.merproject.org/project/show/nemo:devel:hw:samsung:a5ultexx08:21
sledgesbirdzhang: done https://build.merproject.org/project/users/nemo:testing:hw:xiaomi:vince08:21
sledgesYardanico: done https://build.merproject.org/project/users/nemo:devel:hw:xiaomi:markw08:22
birdzhangsledges: Thank you :)08:22
sledgesPSA: New HADK revision fixing droidmediafglue builds & re-explaining straggler files; https://sailfishos.org/develop/hadk/ diff to https://pastebin.com/H0C9y3gF08:22
sledgesAlso update your dhd submodule if mic (thanks KayMW for spotting), zypper, or droidmedia builds were giving you hard time recently08:22
sledgesAlso update your dhd submodule if mic (thanks KayMW for spotting), zypper, or droidmedia builds were giving you hard time recently08:22
Mister_Magistermal: could you help me? i saw yesterday that when i zypper ref and dup there are updated packages (on testing) but i didnt rebuild anything there. and after upgrading sensors stop working. i thappened on 2 devices and rest is probably affected too. Something changed?08:30
Mister_Magisteroh hadk-faq:825?08:31
dr_gogeta86good mornign all08:35
dr_gogeta86hi sledges08:35
Mister_Magisterdr_gogeta86: hi doc08:37
Mister_Magisteryeah boiiii mal nevermind thats it08:38
echo_salikr0kk3rz, so arm7hl ~= armv8 ?09:07
r0kk3rzecho_salik: not quite, but basically rootfs is armv7hl for arm based devices09:49
r0kk3rzsledges: o/09:49
T4<adampigg> Masya_ like mido,.had to find.32bit libs from.elsewhere09:52
echo_salikr0kk3rz, oh... nice... thanks!10:01
echo_saliki read somewhere that arm7hl is the 32 bit part of armv8l... is it like that?10:02
r0kk3rzgenerally all you need to know is armv7hl is 32bit arm, aarch64 is 64bit arm10:03
* Mister_Magister has flashbacks frm -vietnam- huiawei kernel with no 32bit support because screw you10:08
echo_salikgreat... thanks dude!10:17
echo_salikim asked by console to build libhybris when running this: rpm/dhd/helpers/build_packages.sh11:27
echo_salikif i answer yes i get: You are not currently on a branch. Please specify which11:27
r0kk3rznuke your hybris/mw/libhybris folder11:29
echo_salikr0kk3rz, im getting this error: https://hastebin.com/ahelefonax.makefile11:59
r0kk3rzyeah that doesnt look happy12:03
echo_salikso that should i do...12:07
echo_salikargh *what12:07
echo_saliki have currently change <> to "" and building...12:08
*** ambernight is now known as qtwyeuritoiy12:08
echo_salikr0kk3rz, is there a way to make this script build hybris only and not everything else12:09
r0kk3rz-m should skip the hal packages at least12:11
r0kk3rzthen say n to the others12:11
r0kk3rzim going to guess that your kernel might be missing that sync.h file12:12
r0kk3rzso check that12:12
echo_salikok.... thanks12:21
echo_salikr0kk3rz, i have sync.h in my kernel12:30
r0kk3rzit is built ok?12:41
echo_salikr0kk3rz, how to check that13:06
echo_salikhybris-hal had built without errors13:08
r0kk3rzwhat about the droid-hal package?13:09
echo_salikr0kk3rz, do i have to make that?13:32
echo_saliki have made hybris-boot and hybris-recovery as well13:33
_gnus_Hi, While syncing repo, I got "CyanogenMod/android_device_motorola_condor" cm-14.1 baseline not found ERROR. Can you please give your inputs?14:08
_gnus_b nuke14:09
echo_salikr0kk3rz, yeah that built too i think... i am cleaning the output dir and everythin just to retrace my steps... if i forgot something14:15
demonaxshhi, everyone14:54
demonaxshcurrent version ofono works with mtk devices? because, I've tried all  sockets already, but every time ophono can not connect to socket14:54
demonaxshstandart sockets rild not exists in /dev/sockets14:54
r0kk3rzdemonaxsh: talk with monich14:55
monichdisappearance of ril sockets is not so much mtk specific14:57
monichit's android 8 specific14:58
demonaxshon device android 614:58
monichdemonaxsh: then it's something else, sockets must work there14:59
monichsomething is not being initialized properly or whatever14:59
monichin android 8 those are gone for good, that's a different story14:59
r0kk3rzdemonaxsh: is it running?15:00
demonaxshno, it's disabled by default15:01
demonaxshok, i check sockets on android, without sailfish15:02
monichI don't have any mtk device with me atm, can't compare15:04
monichand I don't remember this stuff by heart, sorry15:04
monichand it's a bit closer to bare metal than what I'm usually dealing with :)15:05
demonaxshon android rild sockets exists in /dev/socket, it means that something is not being initialized15:21
demonaxshfucking mediatek...))15:25
maldemonaxsh: which android base?15:26
demonaxshenabling service fixed it, but no idea why vendor did it15:45
NeKitdemonaxsh, usually it's triggered after nvram init15:49
NeKitwhich waits for signal from vold, but probably you already fixed that before?15:49
demonaxshno, how can this be manifested?15:51
demonaxshhmmm... nvram_daemon not started15:59
echo_salikr0kk3rz: i dont see any error in droid-hal stuff... https://hastebin.com/lohaliyuze.coffeescript16:50
echo_salikit is currently building libhybris.spec16:50
echo_salikand i got the error16:50
echo_salikr0kk3rz: youre right... i got an error in hal-rolex: Can't create cache at /var/cache/zypp/solv/local-rolex-hal - no writing permissions.16:54
echo_salikim getting this error: https://hastebin.com/dolasutusu.bash | !! can't update pkg info18:09
echo_salikmain error: Can't create cache at /var/cache/zypp/solv/local-rolex-hal - no writing permissions.18:10
_gnus_I am in 'Building the Android HAL stage'. I am trying to fetch repos. I got error - error: in 'sync --fetch-submodules' : revision stable/cm-14.1 in Cyanogemod/android_device_motorola_condor not found18:10
_gnus_I am following Porting PDF. trying to build Moto phone.18:11
mal_gnus_: is that ytpo in the path a copy paste error to IRC or in the file also?18:11
malCyanogemod vs Cyanogenmod18:12
_gnus_typo. could not paste it from xterm.18:12
malwhich android base?18:12
maland try without --fetch-submodules18:12
_gnus_ok, I will try without --fetch-submodules.18:14
mal_gnus_: is there a reason you use cyanogenmod repo and not lineageos?18:15
malalthough not much differences in the device it seems18:16
_gnus_First, I created repo using - repo init -u git://github.com/mer-hybris/android.git -b hybris-14.1. And then created condor.xml. I have added18:19
_gnus_<?xml version="1.0" encoding="UTF-8"?> <manifest>         <project path="device/motorola/condor"                 name="CyanogenMod/android_device_motorola_condor"                 revision="stable/cm-14.1" />         <project path="kernel/motorola/condor"                 name="CyanogenMod/android_kernel_motorola_condor"                 revision="stable/cm-14.1" /> </manifest>18:20
_gnus_mal is this correct way? I could not find cm branch in mer-hybris/androi repo18:21
mal_gnus_: the branch is cm-14.1 not stable/cm-14.1, also you didn't answer why you use cyanogenmod and not lineageos, I would assume it's easier to find lineageos images? or are the cyanogenmod images still somewhere?18:26
mal_gnus_: also you did you add the dependencies to local manifest, check the cm.dependencies or lineage.dependencies in all repos you add to see if there are more repos needed18:27
_gnus_I agree, switching to LineageOS.18:28
_gnus_Looking into dependencies.18:29
mal_gnus_: you can see these kind of files with dependencies on some repos https://github.com/LineageOS/android_device_motorola_condor/blob/cm-14.1/lineage.dependencies18:30
_gnus_mal, thanks a lot.18:31
echo_salikhey mal18:37
echo_salikany idea regarding my error?18:38
malecho_salik: what error?18:39
echo_salikCan't create cache at /var/cache/zypp/solv/local-rolex-hal - no writing permissions.18:39
echo_salikhttps://hastebin.com/dolasutusu.bash | !! can't update pkg info18:39
maldid the build work before?18:40
malhave you been using sudo when you shouldn't have?18:40
echo_saliknope... sudo only for zypper18:40
maland are the mount options correct for the partition you have setup in?18:41
echo_saliki just run sfossdk and source build/envsetup.sh18:42
echo_salikI'll see the mount options18:42
malecho_salik: source build/envsetup.sh is run in habuild_sdk not in platform sdk18:42
echo_salikcould that be a reason?18:43
maland that has nothing to do with rpm building18:43
malyou are not mixing things18:43
echo_salikyeah... i am... but that should not do anything with this command shoud it? `rpm/dhd/helpers/build_packages.sh`18:44
r0kk3rzecho_salik: print whole output, including command18:44
echo_salikr0kk3rz: its the same as above... but recreated it with command: https://hastebin.com/bekiyuhema.bash18:47
pseudodevecho_salik: rm the entire cache dir18:49
echo_saliki tried zypper clean -a is that different?18:49
malalso do note that running zypper in platform sdk is not the same as running it in target18:50
pseudodevecho_salik: try "sudo rm /var/cache/zypp"18:51
echo_salikBTW i ran it in target...18:51
malecho_salik: how?18:51
echo_salik*i meant SDK18:51
malthis is how run things in target: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper18:52
echo_salikmal: zypper clean -a18:52
echo_saliki did not know...18:52
pseudodevecho_salik: did you try this "sudo rm /var/cache/zypp"18:52
echo_salikpseudodev: yeah just did... re-runing build.sh thing18:53
pseudodevdoes it work now?18:53
echo_saliki got this now: Error building the cache: Can't create /var/cache/zypp18:54
maljust in case exit the sdk and re-enter, do not run any additional things18:54
echo_salikits building droid-hal-rolex waiting for it to complete...18:56
echo_salikor fail18:56
echo_salikthanks mal, pseudodev & r0kk3rz18:56
pseudodevecho_salik: I dont know the consequences (probably not too drastic) by trt rm the entire cache folder19:05
pseudodev*but try19:06
echo_salikpseudodev, mal, r0kk3rz: after cleaning cache, exinting and entering Platform SDK... i got the exact same error19:07
pseudodevdid you clean the entire cache folder?19:07
echo_salikpseudodev: i ran rm -rf /var/cache/zypp/19:07
mali target?19:08
echo_saliki had even given zypp folder 77719:08
echo_saliknope in sdk19:08
pseudodevrun rm -rf /var/cache19:08
malI would just remove the target and resetup it19:09
pseudodevthen run mkdir -p /var/cache/zypp19:09
pseudodevecho_salik: Also do what mal suggested first19:09
malpseudodev: you should also know that sdk and target are not the same thing19:09
echo_salika question (mal): how'd i do that?19:09
echo_salikmal im running this in SDK19:10
malecho_salik: the instrutions are in the same place that has the installation instructions, obviously https://sailfishos.org/wiki/Platform_SDK_Target_Installation19:10
r0kk3rzyeah that error is going to be in the target19:10
malI am still amazed how many way people manage to mess up the build,19:11
r0kk3rzits turtles all the way down19:11
maleveryone seems to be mixing sdk and target19:11
r0kk3rzi guess its not that obvious that creating the target and running build_packages.sh are related19:12
malseems like it19:12
pseudodevmal: I used to be really confused. I won't exactly say that i'm all clear, but certainly better from earlier....19:13
echo_salikok... sorry if my next few statement seems dumb ( i know they will be )19:13
echo_saliknow in PLATFORM_SDK chroot, i have to remove all sdk targets and reinstall them?19:14
echo_salikand then run build_packages.sh?19:14
pseudodevremove target19:14
pseudodevre install the target19:15
pseudodevthen rebuild19:15
pseudodevthats it19:15
r0kk3rza simple yes would've worked too19:15
malremember to use the correct name for the target19:15
echo_salikok... thanks guys... sorry if i annoyed you all...19:15
r0kk3rztbh its a weird error, ive not seen that particular one before19:16
vknechtor this ?19:16
vknecht(worked for me)19:16
echo_salikwait... thats really simialr19:17
malI already told to do that but it seems he never did19:17
echo_salikdamn my keyboard -.-19:17
echo_salikmal: yeah i skipped that and removed it via rm -rf19:18
r0kk3rzecho_salik: you understand what these targets are right?19:18
echo_salikr0kk3rz: i dont think so...19:18
malI mentioned many times that target is different and even gave an example how to run commands in target19:19
r0kk3rzok so, we want to build code to run on arm, but we're building on an x86 machine right?19:20
malI think I will stop helping today before I get too annoyed19:20
r0kk3rzso to do that, we create an arm based qemu system to build in, thats the target19:20
echo_salikoh... so that is like a container?19:21
echo_salikso what is that ubu chroot for?19:21
r0kk3rzbuilding androidy stuff19:21
r0kk3rzwhich is unrelated to the sailfish build tooling19:21
echo_salikso we build android related stuff in ubu-chroot ( for alien dalvik or something like that? ) and then we build sailfish stuff in platform sdk using an arm container called target?19:22
echo_salikthats cool19:23
echo_salikand we use a 32 bit arm container?19:23
echo_salikand that build.sh script is actaully running in that container?19:26
malyou can easily see that it uses sb2 inside it19:27
echo_salikyeah i should have opened the file...19:27
vknecht"heard" a lot about watches and sfos, what about (bathroom)scales ? is there one usable with sfos (not necessarily running it ;-)19:36
malvknecht: if those use standard bluetooth profiles then it shouldn't be impossible, if custom profiles then it needs more work19:38
r0kk3rzecho_salik: not for alien-dalvik, for libhybris19:47
*** kimmoli_ is now known as kimmoli220:19
*** kimmoli2 is now known as kimmoli20:19

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!