**** BEGIN LOGGING AT Sun Nov 04 02:59:59 2018 Nov 04 08:34:57 I'm trying to create a manifest for amami (sony xperia z1 compact) Nov 04 08:35:01 This is what I got Nov 04 08:35:05 https://gist.github.com/doniks/828569b28c173c81e8ee9ec47696b56b Nov 04 08:35:27 but `lunch aosp_d5503-userdebug` is not happy Nov 04 08:35:37 https://paste.ubuntu.com/p/DNVd3qgxCC/ Nov 04 08:35:55 seems I'm missing rhine-amami !? Nov 04 08:36:15 but I can't find that one Nov 04 08:36:16 https://github.com/sonyxperiadev?utf8=%E2%9C%93&tab=repositories&q=rhine&type=&language= Nov 04 08:37:00 @dohniks, you need to add the vendor files in your source dir Nov 04 08:40:41 right. that is stuff that goes into `vendor/sony/...` right? Wouldn't I normally get those from the same place where I got my `device/sony/...` stuff? Nov 04 08:41:01 which would be this place: Nov 04 08:41:11 Fwd from dohniks: https://github.com/sonyxperiadev?utf8=%E2%9C%93&tab=repositories&q=rhine&type=&language= Nov 04 08:41:21 but there I don't find them Nov 04 08:42:55 @dohniks, you need to add you device vendor repo on your manifest file, after adding, type repo sync or repo sync --force-sync Nov 04 08:44:01 ok. I think this is my challenge: Nov 04 08:44:09 "add your device vendor repo" Nov 04 08:44:15 how do I find it? Nov 04 08:44:50 is `vendor` that whole proprietary unredistributable stuff which one normally gets from themuppets, but from the looks there is no rhine-amami folder there ... Nov 04 08:45:49 @dohniks, u mean the muppets have no vendor for your device Nov 04 08:49:16 well, I'm not sure tbh :) ... I've added https://github.com/TheMuppets/proprietary_vendor_sony in my manifest and that seems to go into `vendor/sony` and my `lunch` command seems to miss `vendor/sony/rhine-amami/` .... Nov 04 08:49:44 does that mean we conclude them miss something I need? Nov 04 08:50:39 what's your device code name Nov 04 08:50:55 NB: there is no official lineage os for amami, some community things on xda and yesterday @VeryOriginalUsername suggested there is aosp in that sony repo I'm using Nov 04 08:50:57 amami Nov 04 08:51:17 wait Nov 04 08:53:00 your full device name Nov 04 08:54:46 Sony Xperia Z1 Compact Nov 04 08:54:50 do you mean that? Nov 04 08:55:00 yup Nov 04 08:59:04 https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/amami Nov 04 08:59:39 change the branch to n7.1 , in revision Nov 04 09:00:20 ok. do I use this instead of them or in addition to them Nov 04 09:01:01 ah or https://github.com/AICP/proprietary_vendor_sony this instead Nov 04 09:01:07 and what you pointed out in addition Nov 04 09:01:55 try out Nov 04 09:02:04 👍 Nov 04 09:14:26 nice. this got me through `lunch` lets see what make thinks of this Nov 04 09:14:36 [Edit] nice. this got me through `lunch` lets see what `make` thinks of this Nov 04 09:15:04 👍 Nov 04 09:39:14 seems `make hybris-boot` is trying to use a prebuilt kernel instead of building one .. Nov 04 09:39:17 http://paste.ubuntu.com/p/zq2RKY6dYs/ Nov 04 10:18:34 what kernel repository are you using? Nov 04 10:19:25 Nov 04 10:20:33 I guess the official one would be one of these https://github.com/sonyxperiadev/kernel but I can't figure out which one ... Nov 04 10:21:46 on xda I run into this repeatedly : https://github.com/SuperLamic/android_kernel_sony_msm8974 I could try ... Nov 04 10:22:01 no no dont use the official one Nov 04 10:22:45 the copyleft one cuts out stuff that sony cannot redistribute.. without looking for replacement Nov 04 10:23:02 and the vanilla one is for not running android iirc Nov 04 10:23:16 you are using the lineage device repository? Nov 04 10:24:20 well, I use the kernel only from there Nov 04 10:24:21 https://gist.github.com/doniks/828569b28c173c81e8ee9ec47696b56b Nov 04 10:24:26 this is my manifest Nov 04 10:24:42 [Edit] well, I use the kernel only from los Nov 04 10:27:30 Did I answer your question? Nov 04 10:28:33 yes.. I was just looktng through the makefiles Nov 04 10:28:46 lineage/halium export TARGET_KERNEL_SOURCE to be set to the kernel path Nov 04 10:28:55 [Edit] lineage/halium expects TARGET_KERNEL_SOURCE to be set to the kernel path Nov 04 10:29:18 and i do not see that happening in those makfiles .. probably tailored for aosp or so.. Nov 04 10:30:04 You will encounter more issues like that in which you have to adapt the makefiles.. you could try to take the cm-13 lineage repositories and see if they would work with 14.1 .. Nov 04 10:30:25 or you go through the xperiadev makefiles and make them compatible with lineageos 14.1 Nov 04 10:30:56 mhm, rock or hardplace ha? Nov 04 10:32:03 i.e. TARGET_KERNEL_SOURCE should be TARGET_KERNEL_SOURCE := kernel/sony/msm8974/ i.e. set in the BoardConfig.mk of amami .. TARGET_KERNEL_CONFIG := I dont know.. some def_config file name.. Nov 04 10:32:11 then maybe you need to set the cmd line Nov 04 10:32:20 but that might already be correct Nov 04 10:32:26 trial and error through this thing :) Nov 04 10:33:49 [Edit] I mean there are lineageos 13 == android 6 repositories for amami .. so maybe those work .. or maybe you find other device repositories that work with lineageos 14/1 Nov 04 10:36:08 use the kernel from the aicp repo, don't forget to choose the branch to 7.1 Nov 04 10:38:32 ahhh, aicp is a whole android thing right, I probably want to use everything from there, no sony, no los ... Nov 04 10:51:31 just try if it works Nov 04 10:51:58 pfff or maybe not ... following down the rabbit hole of aicp.dependencies files it looks like I'm depending on los and omnirom, except I don't because the n7.1 branch of this has a lineage.dependencies file ..... Nov 04 10:52:17 https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/aicp.dependencies Nov 04 10:59:47 yeah you want those android_sony_device repos at version n7.1 those look liek lineage friendly make fils Nov 04 10:59:54 [Edit] yeah you want those android_sony_device repos at version n7.1 those look like lineage friendly make fils Nov 04 11:00:12 yeah, I'm soldering through the dependecies :) Nov 04 11:00:38 [Edit] yeah, I'm soldiering through the dependecies :) Nov 04 11:03:43 @anpok, sodp kernel != copyleft Nov 04 11:03:59 sodp? Nov 04 11:04:02 couldn't that hole .dependencies stuff be automated somehow? how does los do this? Nov 04 11:04:05 sony open devices Nov 04 11:04:17 kernel repo is for aosp kernel and kernel-copyleft is for stock kernel sources Nov 04 11:04:17 [Edit] couldn't that whole .dependencies stuff be automated somehow? how does los do this? Nov 04 11:04:31 [Edit] sony open devices (project) Nov 04 11:26:52 oh ok.. i might have discarded that for the wrong reason Nov 04 11:36:08 ok, I have a new manifest based on aicp https://gist.github.com/doniks/828569b28c173c81e8ee9ec47696b56b Nov 04 11:36:20 but how do I `breakfast` or `lunch`? Nov 04 11:36:39 not like this: https://paste.ubuntu.com/p/x2fNxbt2rN/ Nov 04 11:38:54 `breaskfast amami`' Nov 04 11:38:55 [Edit] `breaskfast amami` Nov 04 11:39:01 or w/e was the codename Nov 04 11:39:17 or lunch Nov 04 11:39:23 lunch is for 7.1 I think Nov 04 11:40:01 still fails https://paste.ubuntu.com/p/r5mhvwPVX6/ Nov 04 11:41:46 rename aicp.dependencies to lineage.dependencies etc Nov 04 11:42:20 cd device/ … grep -r "aicp" … change all aicp that pops up to lineage Nov 04 11:52:14 I leave this alone I guess: https://paste.ubuntu.com/p/9ZZG2pPskr/ Nov 04 11:52:24 I've renamed two files now Nov 04 11:52:48 device/sony/aicp.dependencies and device/sony/aicp.mk Nov 04 11:53:05 both to lineage.* Nov 04 11:53:32 that's all I find with `grep -r --exclude '*.graffle' --exclude '*.svg' --exclude '*.gif' --exclude-dir=.repo -Ee 'aicp|AICP|Aicp'` Nov 04 11:54:04 but `breakfast amami` still complains Nov 04 11:56:25 because breakfast downloads it again Nov 04 11:56:35 do the changes again and upload to your git Nov 04 11:56:52 and instead of breakfast try running `lunch` and then pick the number that says amami-userdebug or something Nov 04 11:59:14 "the changes" is just the two renamed files right? the are still the way I changed them after `breakfast` Nov 04 11:59:22 [Edit] "the changes" is just the two renamed files right? they are still the way I changed them after `breakfast` Nov 04 11:59:51 let me see that dt Nov 04 12:00:03 lunch just propses some standard stuff https://paste.ubuntu.com/p/FXRkWpNjQJ/ Nov 04 12:00:06 did you use n7.1 or n7.1-aosp? Nov 04 12:00:53 this is my manifest: https://gist.github.com/doniks/828569b28c173c81e8ee9ec47696b56b Nov 04 12:01:01 n7.1 Nov 04 12:03:14 create a vendorsetup.sh in this dt Nov 04 12:03:31 and paste … `add_lunch_combo lineage_amami-userdebug` Nov 04 12:03:45 no idea if that would work but might as well try Nov 04 12:06:56 @dohniks, what is your default python version?? Nov 04 12:07:26 $ python --version … Python 2.7.15rc1 Nov 04 12:09:18 r you sure, cause roomservice.py should be execute using python2, type which python on your terminal, msg the output Nov 04 12:09:59 it doesn't like any combination that I can think of https://paste.ubuntu.com/p/mWqGTfmFDx/ Nov 04 12:10:44 wait a sec Nov 04 12:11:45 I'm not sure, but how can I confirm any better ... https://paste.ubuntu.com/p/ptXC6CP3Vn/ Nov 04 12:12:04 ^ @Err0r_extinct Nov 04 12:12:28 cp full_amami.mk lineage_d5503.mk Nov 04 12:12:35 maybe this? :thinking: Nov 04 12:12:42 fwiw, sony calls it d5503 https://github.com/sonyxperiadev/device-sony-amami/blob/n-mr1/vendorsetup.sh Nov 04 12:12:52 I can try :) Nov 04 12:13:02 also include d5503 in vendorsetup then Nov 04 12:13:06 we will try everything xd Nov 04 12:13:21 it's in there with cm lineage and aosp Nov 04 12:13:25 just for good measure Nov 04 12:14:48 @dohniks, line 46 to 57 , the roomservice.py using python3 some how and 74 to 79 there is some problem with your remote or manifest Nov 04 12:14:55 i think so Nov 04 12:14:56 B1dle Fr3dl I think you used sony aosp trees for suzu port, am I right? Nov 04 12:16:55 https://raw.githubusercontent.com/beidl/halium-devices/halium-7.1/manifests/sony_suzu.xml Nov 04 12:16:58 yeah looks like he did Nov 04 12:33:22 mhm. even after staring at beidls commits and at roomservice.py I don't know how to proceed Nov 04 12:33:38 I've created a porting issue for now Nov 04 12:33:55 maybe someone still has an idea ... Nov 04 12:34:09 https://github.com/Halium/projectmanagement/issues/106 Nov 04 12:45:25 oh Nov 04 12:45:27 maybe this Nov 04 12:45:28 add_lunch_combo full_amami-userdebug Nov 04 12:48:06 chchchch. seems to be compiling somethink :) Nov 04 12:48:16 [Edit] chchchch. seems to be compiling something :) Nov 04 12:49:07 @dohniks type in your terminal this … sudo ls -la /usr/lib | grep python Nov 04 12:50:26 http://paste.ubuntu.com/p/Pv8pzCnbcX/ Nov 04 12:51:45 this output not showing the links, type correctly Nov 04 12:52:37 they are all real dirs Nov 04 12:52:43 do you want /usr/bin ? Nov 04 12:52:52 I've got links there Nov 04 12:53:20 https://paste.ubuntu.com/p/y35BQQ7qxX/ Nov 04 12:53:23 yes sorry for the mistaking not lib it is bin Nov 04 12:53:52 http://paste.ubuntu.com/p/T8HV2C2nbC/ Nov 04 12:56:42 ahh your default python is python 2, … ok start from beginning … type this one by one … repo sync --force-sync … source build/envsetup.sh … export ALLOW_MISSING_DEPENDECIES=true … export LC_ALL=C … then lunch Nov 04 12:58:12 I can try ... but ... I'ts building something right now after: Nov 04 12:58:27 Fwd from dohniks: add_lunch_combo full_amami-userdebug Nov 04 12:58:43 I wanna wait for that result Nov 04 12:58:51 ok Nov 04 13:16:48 my android container runs, but all tests fail - i guess i just need to start fixing all the errors in dmesg and logcat and keep on trying ? Nov 04 13:39:59 hmm my /dev is full, how do i resize that? Nov 04 13:43:20 what exactly is full? Nov 04 13:44:19 https://paste.ubuntu.com/p/wKCW7dQHTX/ Nov 04 13:44:25 df -h output Nov 04 13:45:58 ok. I see the 0%, is that an actual problem? Nov 04 13:46:20 in dmesg, i get errors like: [ 129.098916] init: Starting service 'vold'... [ 129.105905] init: couldn't write 709 to /dev/cpuset/foreground/tasks: No space left on device Nov 04 13:46:41 so i would assume so Nov 04 13:47:07 can you paste the whole dmesg Nov 04 13:47:55 https://paste.ubuntu.com/p/nXsXGJZ9S7/ Nov 04 13:47:58 it's masisve Nov 04 13:48:47 [Edit] it's massive Nov 04 13:58:18 not sure ... if nobody else has a better suggestion ... I hink I remember that vold isn't really needed, so you might want to try to comment that out in the init of the android container Nov 04 13:58:27 but I'm not even sure how much it matters Nov 04 13:58:42 you've got a bunch of "Permission denied" in your dmesg Nov 04 13:59:25 did you do the udev rules? Nov 04 13:59:49 yeah, let me verify that though Nov 04 14:00:12 apart from error messages, what's the actual status? Nov 04 14:00:13 ssh? Nov 04 14:00:41 yeah, it's there Nov 04 14:00:53 i got access to ssh, lxc runs (and doesn't crash), none of the tests work Nov 04 14:01:02 haven't tried the plasma-caf rootfs yet Nov 04 14:01:08 in halium rootfs? Nov 04 14:01:12 yeah Nov 04 14:01:47 working on s4mini (3.4.1xx kernel version) Nov 04 14:01:53 yeah, maybe try pm? or ut? not sure the status of ut nowadays Nov 04 14:03:30 sure, will try pm Nov 04 14:13:45 basically the same happens Nov 04 14:13:51 same loopback crash, same lack of space Nov 04 14:14:48 I think the "lack of space" isn't the actual problem. I kinda doubt taht "/dev" can run out of space. it's not like /dev is stored on some disk Nov 04 14:15:08 also same permission denieds ... Nov 04 14:15:16 but maybe it complains as if it were out of space because it can't write to it ... but the error is somewhere else Nov 04 14:15:20 yeah Nov 04 14:15:26 so what about those udev rules? Nov 04 14:15:41 i probably need to generate them here too :) Nov 04 14:16:43 getting exceptions generating them on the phone, let me try pushing Nov 04 14:21:09 when i push the udev rules i get: sudo: unable to resolve host localhost.localdomain: Connection refused Nov 04 14:21:15 that's probably a hint ;) Nov 04 14:21:57 it did copy the rules. also, the other rules all have size 0? Nov 04 14:23:42 apparantly that error is tied to using sudo; also happens when i sudo for something else ... Nov 04 14:27:26 ... and then after reboot it boots in plasma UI (and told me it's gorgeous) ... Nov 04 14:28:00 ... and touch works ... Nov 04 14:28:11 oh, so it works! Nov 04 14:28:14 thnx @dohniks :) Nov 04 14:28:24 I don't think I actually did anything :) Nov 04 14:28:56 (Photo, 960x1280) https://irc.ubports.com/0ZrJdplS.png Nov 04 14:29:07 nice :) Nov 04 14:30:08 scaling is completely off, but in general it does respons Nov 04 14:32:34 errors in log are also exactly the same Nov 04 14:32:55 still the permission errors? Nov 04 14:33:06 yeah, kernel bug, permssion errors, out of space, etc Nov 04 14:33:16 i guess this is where the infamous sadism starts Nov 04 14:34:01 cmon, you've got moving pixels on your screen. I think you're past the sadism :) Nov 04 14:34:08 or, well, some of it anyway Nov 04 14:34:51 logcat is full of stuff like 1-17 05:18:56.938 0 1168 E qdhwcomposer: isValidDimension: layer handle is NULL … 01-17 05:18:56.938 0 1168 E qdoverlay: getRotDevFd failed to open rotator device Nov 04 14:35:02 :) Nov 04 14:35:10 does it rotate? Nov 04 14:35:54 eh, no Nov 04 14:37:02 i guess that picture belongs in the github issue? Nov 04 14:37:43 do we have a version of the mer kernel checker that automagically fixes the config? Nov 04 14:45:35 Nope Nov 04 14:46:29 I think it does if you run it with some argument Nov 04 14:46:44 :( Nov 04 14:46:54 But it overwrites some values that might break your defconfig Nov 04 14:46:56 I've got a test that fails, but I don't know how to fix it now Nov 04 14:46:58 https://paste.ubuntu.com/p/g24HsdxbjK/ Nov 04 14:47:05 allowed value "" Nov 04 14:47:10 sooo Nov 04 14:47:47 It wants it to be missing Nov 04 14:47:49 I guess Nov 04 14:48:19 Only a warning, so you're fine Nov 04 14:48:35 👍 Nov 04 15:04:36 @VeryOriginalUsername the Fastboot description here looks a bit strange to me Nov 04 15:04:38 http://docs.halium.org/en/latest/supplementary/devices/nicki.html#device-specifics Nov 04 15:04:47 off, up, connect usb ?! Nov 04 15:05:25 on my device I'd say: off, up, on, blue, ... Nov 04 15:06:46 I can propose a PR, unless your device is very different than mine ... Nov 04 15:14:20 Yes Nov 04 15:14:30 You connect usb to a device that's powered down Nov 04 15:14:44 And hold vol+ in meantime Nov 04 15:15:35 but does the booting into fastboot depend on connecting the usb? Nov 04 15:15:38 I turn off Nov 04 15:15:42 hold up Nov 04 15:15:44 turn on Nov 04 15:15:51 wait for it to vibrate Nov 04 15:15:56 let go off power Nov 04 15:15:59 wait for blue led Nov 04 15:16:04 let go of up Nov 04 15:16:12 then I can `fastboot devices` Nov 04 15:16:19 all the time it is connected to usb Nov 04 15:16:46 Lol Nov 04 15:17:06 Just turn off, hold vol+ and plug usb Nov 04 15:17:13 It will boot directly into fastboot Nov 04 15:17:43 without pressing power to turn it on? Nov 04 15:18:33 Yeah Nov 04 15:18:44 Your solution is basically turning it on and off Nov 04 15:18:47 actually I don't even know how to reliably turn it off ... I just hold power until it reboots Nov 04 15:18:50 So wasting like 13s Nov 04 15:19:02 @dohniks, Hold power 10s and it cuts power off Nov 04 15:20:59 @VeryOriginalUsername, true! magic Nov 04 15:21:28 @VeryOriginalUsername, doesnt' work for me. the only *off* is when I boot into adroid and use the shutdown menu Nov 04 15:21:37 any way, something else: Nov 04 15:21:45 Either cuts power or force shutdowns Nov 04 15:21:52 Not sure on amami Nov 04 15:22:22 @VeryOriginalUsername, what was the exact optiion you used? Nov 04 15:22:44 I am at the point where it advertises as storage device in host dmesg Nov 04 15:23:14 https://github.com/konradybcio/android_kernel_sony_msm8x27/blob/1cde0306be4cd04a310388b37ee4d738322393b8/arch/arm/configs/cyanogenmod_nicki_defconfig Nov 04 15:23:18 hmm so i have no /dev/cpusets (which is why permissions get denied) :)\ Nov 04 15:23:23 Check all networking and usb options Nov 04 15:23:28 even though declared in /proc/filesystems Nov 04 15:23:29 Check last 3 commits Nov 04 15:23:34 @VeryOriginalUsername, Don't mind the names xd Nov 04 15:23:59 hehehe asdfasdfadsf :) Nov 04 15:25:23 Hello, I am getting this error during boot, what I am doing wrong https://pastebin.com/mTTBeaxR Nov 04 15:26:13 I am trying run halium image on redmi note 3 Nov 04 15:26:18 ls -l Nov 04 15:30:21 [Edit] Hello, I am getting this error during boot, what I am doing wrong? https://pastebin.com/mTTBeaxR Nov 04 15:30:30 what happened earlier in the kernel log? is this with hybris-boot? do you get telnet? Nov 04 15:32:30 yes, with hybris-boot https://pastebin.com/hXPEbtUA Nov 04 15:32:56 it reboots every 5s Nov 04 15:44:47 what does your fix-mountpoints look like? Nov 04 15:52:25 https://pastebin.com/e0nZB6Pv Nov 04 15:53:02 It's wrong Nov 04 15:53:06 Too much partitions Nov 04 15:53:55 it was there allready Nov 04 15:54:09 http://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints Nov 04 15:54:17 @Daniel, It came from sailfish Nov 04 15:54:37 thanks, i am going to check it Nov 04 15:54:45 (Sticker, 512x412) https://irc.ubports.com/HQnK0vLO.webp Nov 04 17:31:43 ugh, seems my sony has a locked bootloader. and now I'm faced with an internet full of weird windows programs and unlock code sellers ... all in broken english ... so annoying :( Nov 04 17:33:18 Lol Nov 04 17:33:40 https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ Nov 04 17:33:45 There you go Nov 04 17:34:59 open the dialer and enter *#*#7378423#*#* [...] If Bootloader unlock allowed says [...] No, [...] your device cannot be unlocked. Nov 04 17:48:18 hı Nov 04 17:48:25 how open ssh for ut? Nov 04 17:50:36 @dohniks, Is your device non unlockable? Nov 04 17:51:31 It says "Bootloader unlock allowed: No" Nov 04 17:51:41 Well, I'm sorry.. Nov 04 17:51:59 You can unlock it but you will have to pay for it Nov 04 17:52:12 If someone has a setoolbox he can unlock your bootloader Nov 04 17:52:43 so maybe if I walk into one of those shady mobile phone shops ... Nov 04 17:52:57 Yeah that'd be your best bet Nov 04 18:56:09 psycho_mods was added by: psycho_mods Nov 04 19:24:58 https://paste.ubuntu.com/p/pHhrsZ4DF5/ Getting this error when building right after trying to add a kernel module Nov 04 19:25:16 the config is in arch/arm64/ Nov 04 19:27:29 @kaibsora, kernel modules dont work yet if i am not wrong Nov 04 19:27:42 i think you are Nov 04 19:27:43 am i right @bhushanshah ? Nov 04 19:27:54 the guide states that you can use them to load wifi Nov 04 19:28:00 and thats exactly what i am doing Nov 04 19:28:25 i think some path is wrong Nov 04 19:28:28 idk Nov 04 19:28:29 meh Nov 04 19:28:35 thats what i thought too Nov 04 19:29:10 @kaibsora, no not with your kernel, but in halium Nov 04 19:29:14 nvm Nov 04 19:29:16 wait what? Nov 04 20:41:45 https://paste.ubuntu.com/p/N6wrv7Jb28/ … error while attempting to build. not sure what to do **** ENDING LOGGING AT Mon Nov 05 03:00:00 2018