**** BEGIN LOGGING AT Sat Jan 27 03:00:03 2018 Jan 27 04:25:20 @Mattia990, For which device arm or arm64 ? Jan 27 08:17:22 Bhushan is there any way that we can add udev rules early, so that we dont have to add them later using ssh, well if that is possible, we can just make flashable zips to install the halium, coz it will be easy to distribute that way Jan 27 08:41:04 One could add that function to the install script maybe, so that it copies the udev rules file into the rootfs.img on installation Jan 27 09:01:43 https://paste.ubuntu.com/26469280/ Jan 27 09:02:31 @SALPHA8506, now getting new problem Jan 27 09:24:35 @SALPHA8506, Arm Jan 27 09:49:04 @SALPHA8506 is the rootfs 64 of 32? Jan 27 10:00:46 @Flohack, sure i joined it Jan 27 10:16:01 @dohniks, every rootfs is 32bit as of now Jan 27 10:17:33 I think @SALPHA8506 was around the block with this trying to build a 64 bit rootfs since all his vendor libraries are 64 Jan 27 10:18:17 I'm currently making a build of the debian rootfs for arm64. It will be quite experimental though :) Jan 27 10:19:10 @dohniks, yes vendor libraries are 64 bit Jan 27 10:24:43 and .... the rootfs you are using is .... ? Jan 27 10:35:50 Guys, i found this in logcat during the hwcomposer test: https://paste.ubuntu.com/26469535/ Jan 27 10:38:03 Have you added CAF repo and libhybris? Jan 27 10:39:46 caf repos yes, but libhybris i think no... Jan 27 10:40:11 @bhushanshah, With apt-get ? (libhybris) Jan 27 10:41:47 @Mattia990, Yeah just run apt upgrade Jan 27 10:42:20 @bhushanshah, Ah, during the update i got "28: No space left on device" Jan 27 10:42:35 With just CAF repos it won't work, you'll need to upgrade libhybris too Jan 27 10:43:20 @Mattia990, Well time to fix it I guess Jan 27 10:43:45 From recovery using resize2fs you can resize /data/rootfs.img Jan 27 10:44:12 But still it's strange that disk is already full Jan 27 10:44:25 'df -h' output please Jan 27 10:44:26 @bhushanshah, Ahhhhh, wow so easy... How much space i have to add? Jan 27 10:44:50 @bhushanshah, https://paste.ubuntu.com/26469570/ Jan 27 10:46:44 Uhhhh Jan 27 10:47:02 ls -lah /var/log please Jan 27 10:48:21 @bhushanshah, For me, probably is rsyslogd because it use 100% of cpu Jan 27 10:48:25 @bhushanshah, https://paste.ubuntu.com/26469586/ Jan 27 10:49:04 I'd say just rm syslog and kern.log Jan 27 10:49:22 And also try to figure out what's spamming this logfile and fix it Jan 27 10:49:34 What's most repeating stuff in dmesg? Jan 27 10:51:34 @bhushanshah, This: https://paste.ubuntu.com/26469597/ Jan 27 10:52:05 @bhushanshah, Done, now i've free 2Gb Jan 27 10:52:17 @Mattia990, ah is /firmware mounted? Jan 27 10:52:46 @bhushanshah, No, it isn't mounted Jan 27 10:53:58 time to fix it Jan 27 10:56:20 @bhushanshah, Thanks for help! If i use a script to mount it everytime the device turns on, or if i modify init script, could be a great idea? Jan 27 10:56:46 @Mattia990, well for starters it should be automounted Jan 27 10:57:03 `systemctl status android-mount` please Jan 27 10:59:12 @bhushanshah, Here you are: https://paste.ubuntu.com/26469621/ … Also i'm doing the updates Jan 27 10:59:58 Great, show me your fstab please? Jan 27 11:00:03 (device fstab) Jan 27 11:01:25 @bhushanshah, Here you are: https://paste.ubuntu.com/26469626/ Jan 27 11:02:51 uh Jan 27 11:02:57 there is no /firmware mount point at all Jan 27 11:02:59 o_O Jan 27 11:03:52 @bhushanshah, wtf hahah, also in fixup-mountpoint there isn't Jan 27 11:04:22 No fixup-mountpoint doesn't "edit" fstab Jan 27 11:06:03 @bhushanshah, Yeah, i know, but also in fixupmountpoint there isn't the voice firmware Jan 27 11:06:19 it doesn't need to be Jan 27 11:06:28 fixup-mountpoints just needs /data Jan 27 11:06:43 @bhushanshah, Ahhhhhh Jan 27 11:06:56 So now i have to add in fstab? Jan 27 11:06:57 is it possible for you to get dmesg and `mount` output from android? Jan 27 11:07:17 @bhushanshah, Yes, give me 5 minutes Jan 27 11:07:33 Thanks for help! Jan 27 11:22:04 YESSSS after the upgrade graphics workssss!!!!! Jan 27 11:22:19 \o/ Jan 27 11:22:50 Only hwcomposer works, other graphics test no (segmentation fault) Jan 27 11:24:06 Now on dmesg i haven't got the firmware error Jan 27 11:40:55 @bhushanshah Here you are the android mount: https://paste.ubuntu.com/26469816/ Jan 27 11:41:21 hmm Jan 27 11:41:37 Yeah, i see it... If i add it to fstab ? Jan 27 11:41:52 can you cat /fstab.* from android Jan 27 11:41:53 ? Jan 27 11:43:20 @bhushanshah, Here you are.. There isn't … https://paste.ubuntu.com/26469825/ Jan 27 11:43:56 lol wat Jan 27 11:44:03 `ls /` please Jan 27 11:44:21 no firmware, no cache how dose it work ? Jan 27 11:44:35 exactly lol Jan 27 11:44:37 But this is Android Oreo Jan 27 11:44:40 @bhushanshah, https://paste.ubuntu.com/26469833/ Jan 27 11:44:42 Oh Jan 27 11:47:48 In fstab there aren't some partitions but with mount we see that they're mounted Jan 27 12:17:05 @Mattia wild guess : https://forum.xda-developers.com/oneplus-3/help/oreo-fstab-qcom-ramdisk-t3711781 Jan 27 12:21:55 I haven't got fstab.qcom in that directory Jan 27 12:22:38 Also here there isn't: https://github.com/ShivamKumarJha/android_device_xiaomi_cancro/tree/lineage-15.1/rootdir/root Jan 27 12:27:43 grep firmware $( find -type f -iname '*fstab*' ) Jan 27 12:27:44 ? Jan 27 12:31:16 @dohniks, In system/vendor/etc ? Jan 27 12:31:33 I have no clue haha Jan 27 12:31:56 Just suggesting some desparate measures to find anything in android :) Jan 27 12:32:12 maybe simply in the rootfolder and then go for lunch Jan 27 12:32:22 @dohniks, ahahahah😂😂 Jan 27 12:33:12 depending on the level of despair you could resort to grep -R /firmware :) Jan 27 12:34:18 @dohniks, Ok, i'm trying thx :) Jan 27 12:40:40 Seven was added by: Seven Jan 27 12:44:59 Tell your arabic friends to join the group now : … @Halium_Arabic Jan 27 15:16:47 I finally got a clean log by getting journald to write everything to the rootfs: https://paste.ubuntu.com/26470809/ Jan 27 15:18:15 I also added a 1s sleep to the driver who spammed the whole log (in the code path where he logs the message) Jan 27 15:42:11 Hallo everyone. I am trying to port my Sony Xperia L. I succeded already in building and installing the halium reference rootfs, thanks to IBB und Ellenjot. But it won't start. dmesg does not show anything and I cannot reach it via telnet when using hybris-recovery. Jan 27 15:42:48 Here is what I got so far, including an explanation of how I installed the halium reference rootfs: https://github.com/jonnius/docs/blob/master/supplementary/devices/taoshan.rst Jan 27 15:43:49 @jonny, My phone took ~5 minutes ti boot... Try to wait for a little Jan 27 15:54:30 @jonny, When booting goes forward from telnet stage then you can ssh in. Maybe its booted roots but graphics not working properly. You tried ssh ? Jan 27 15:55:17 I was told the reference rootfs had no GUI. Does it? Jan 27 15:56:00 But without seeing anything on dmesg, how do I know where to ssh to? Jan 27 16:00:43 This is what Ellenjot told me how to achieve ssh connection. Jan 27 16:00:44 Fwd from Ellenjott: sudo ip address add 10.15.19.100 dev $RNDIS_DEVICE … sudo ip route add 10.15.19.82 dev $RNDIS_DEVICE … ssh root@10.15.19.82 Jan 27 16:01:07 But I don't know what to put as $RNDIS_DEVICEs Jan 27 16:01:29 Check in "ip link" Jan 27 16:01:43 @Mattia990, I waited for 10 minutes now. It did not show anything else. Jan 27 16:02:05 enp3s*** something will show up Jan 27 16:02:36 @Satyam2345, I only have enp1s0f1, which should be my computers ethernet interface. Jan 27 16:03:29 @jonny, Your ethernet should be eth0 if you are not using tethering or mobile broadband type connection Jan 27 16:03:48 @jonny, This is your device maybe Jan 27 16:04:36 Also i found … https://github.com/JBBgameich/halium-install/blob/master/connect.py Jan 27 16:05:05 I think the interface names have changed with systemd. My wifi interface is wlp2s0 for example Jan 27 16:05:29 @jonny, . Jan 27 16:05:48 Try with you enp1s Jan 27 16:08:36 @Satyam2345, This is how I tried to telnet into the device. Jan 27 16:10:30 @Satyam2345, I did and get: ssh: connect to host 10.15.19.82 port 22: No route to host Jan 27 16:10:46 From dmesg: [ 3343.026348] IPv6: ADDRCONF(NETDEV_UP): enp1s0f1: link is not ready Jan 27 16:12:13 Hmm .. You have to wait for someone else to respond, I don't have any info on this Jan 27 16:12:41 @Satyam2345, Ok. Thanks anyway! Jan 27 16:17:13 does anyone know where I can add/change the kernel command line? I need to run systemd in debug mode. Somehow it gets stuck before it can start ssh Jan 27 16:17:48 for systemd debug, hybris-boot/init-script Jan 27 16:18:51 (you don't want to modify kernel command line.. just change init arguments where init is called Jan 27 16:19:02 ok Jan 27 16:20:52 ah dere is also a config file Jan 27 16:25:29 @jonny, This is ok, its about ipvz6 and expected. Try dmesg -w during device boot, any output? Jan 27 16:25:52 You should see log lines about usb an rndis Jan 27 16:26:56 No. the last lines are from fastboot: … [ 3452.797183] usb 2-1: Product: S1Boot Fastboot … [ 3452.797186] usb 2-1: Manufacturer: Sony Mobile Communications AB … [ 3452.797188] usb 2-1: SerialNumber: ZH8002NPSY … [ 4360.748083] usb 2-1: USB disconnect, device number 11 Jan 27 16:27:39 The LED keeps flashing red slowly. Jan 27 16:28:33 I flashed hybris-recovery btw Jan 27 17:52:06 JoshuaAshton was added by: JoshuaAshton Jan 27 18:32:55 man this is hard to debug... it seams that there is a very high chance that the journal is corrupt if I force a reset so I can read it from recovery Jan 27 18:39:15 hmm Jan 27 18:39:47 Maybe something could be implemented Jan 27 18:40:21 Like "push power three times to reboot" Jan 27 19:14:03 Guys, my systemctl status says that is starting and 3 units are faild... Where i can find the errors? Jan 27 19:39:36 https://github.com/TeamButter/android_device_samsung_mint2g Jan 27 20:13:07 Also in /usr/lib/lxc-android i found other rules, i need to apply in that folder and in /etc/udev/rules.d ?? Jan 27 20:15:18 Question : … Why , UBports installer cannot see the adb device list ( any handset ) will it's connected on the pc operating system ? … I trying it on my device Samsung GT-S5282 ... … it only give me letter " wait adb to attached the device " , I wait for 1 hour nothing happened ... … Really it should give me a massage or letter like " Your device is Samsung GT-S5282 , Sorry we cannot install ubuntu touch on it now " Jan 27 20:15:42 @sudanisayfree, please don't multi-post in 2 chats Jan 27 20:22:35 @vanyasem, Ok Jan 27 21:54:30 How early will dropbear run? I don't seam to sind a unit file, just an initscript. Jan 27 21:54:38 *find Jan 27 21:55:09 Dropbear is started in the rootfs by systemd (at least in the reference rootfs) Jan 27 21:56:27 I use the rootfs, and systemd gets stuck somewhere along the line. I wonder if it would be possible to make it start earlier Jan 28 00:57:55 staticmethod was added by: staticmethod **** ENDING LOGGING AT Sun Jan 28 03:00:02 2018