**** BEGIN LOGGING AT Sun May 09 03:00:50 2021 May 09 03:56:11 w1z was added by: w1z May 09 03:59:24 Sorry lynx looking at ubports pixel4 and halium 10 May 09 04:20:21 bhuvaneshduvvuri was added by: bhuvaneshduvvuri May 09 12:48:31 I just realised what I did wrong! May 09 12:48:46 its prob the vendor.img May 09 12:48:53 cause I can compile a vendor May 09 12:59:36 Hey May 09 12:59:55 Herrie I've been able to make a build work on Pixel 2 XL one of my other devices. May 09 13:00:07 That device had a vendor.img so I'm trying to do some updates. May 09 13:06:18 ZenialLynx: Nice I saw the GitHub notifications! May 09 13:07:46 Im doing a lot of work I really want this device to run linux. it would be my entire life completed. May 09 13:07:55 Ive also been doing research at mainline May 09 13:08:16 phablet@ubuntu-phablet:~$ ifconfig May 09 13:08:16 lo Link encap:Local Loopback May 09 13:08:17           inet addr:127.0.0.1 Mask:255.0.0.0 May 09 13:08:19 So far i got this on cheryl May 09 13:08:28 (no GUI) May 09 14:01:23 hybris/hybris-boot/Android.mk:71: warning: ********************* /boot appears to live on May 09 14:01:23 hybris/hybris-boot/Android.mk:72: warning: ********************* /data appears to live on /dev/block/bootdevice/by-name/userdata Getting this warning May 09 14:01:28 not too sure what it means or it is telling me May 09 14:05:10 ib1889 was added by: ib1889 May 09 15:10:34 nothing important May 09 15:11:14 I did not fix my mount points May 09 15:11:23 https://github.com/Freemoon-Project/freemoon-mountpoints/edit/main/ls.cheryl theses are my partitions May 09 15:22:24 You don't need to May 09 15:22:34 You don't? May 09 15:22:36 What if i do? May 09 15:22:43 Does it do difference May 09 15:26:56 lol May 09 15:27:02 It's used for hybris-boot May 09 15:27:03 ? May 09 15:27:12 Ah ok so halium-boot does not use it May 09 15:27:12 Shouldn't affect halium-boot stuff May 09 15:27:18 have you ported before? May 09 15:34:43 I can't say I did, but I've spent a lot of time figuring out stuff for my port, and I've been using UT for a while(not as a daily-driver, just for fun :D) May 09 17:04:57 Im currently making a system.img May 09 17:05:28 I just dont have a way to run the install script for halium cause well it does not let us do fastboot boot TWRP.img May 09 17:05:29 Razer disabled that command May 09 17:11:36 @LynxZenial[m] [I just dont have a way to run the install script for halium cause well it does n …], you can always do fastboot flash recovery TWRP.img May 09 17:11:58 Yeah May 09 17:12:06 But how would i do the halium install script? May 09 17:12:10 I have to flash the boot img May 09 17:12:45 em, same as usual? the script only handles rootfs, it doesn't care about boo May 09 17:12:53 [Edit] em, same as usual? the script only handles rootfs, it doesn't care about boot May 09 17:13:06 Basicly I could flash twrp first May 09 17:13:09 then run script May 09 17:13:13 Then flash boot.img May 09 17:13:15 yep May 09 17:13:20 Sweet! May 09 17:13:30 Also was the fixing mount points require May 09 17:13:30 * Also was the fixing mount points required May 09 17:13:44 no May 09 17:14:44 Ah ok so I can just keep it as normal May 09 17:14:56 should I build a vendor img May 09 17:15:01 using mka buildvendor May 09 17:15:11 use the one from LOS 16 if possible May 09 17:15:20 Im using this vendor May 09 17:15:20 or stock Android 9 May 09 17:15:30 not 10 and higher May 09 17:15:31 https://github.com/Freemoon-Project/vendor_dragon May 09 17:15:59 its forked from android 9 muppets May 09 17:16:23 or stock Android 9"> You mean like flashing Stock rom before flashing halium? May 09 17:16:52 yes, or at least just vendor May 09 17:17:04 ok so no full repartion required May 09 17:17:10 Im running LOS 18.1 rn May 09 17:17:36 The halium-boot.img doesnt fuck with fastboot right? May 09 17:17:53 or any repartitioning May 09 17:22:29 it doesn't modify partition table May 09 17:22:52 Cause im not sure if the device will reboot into fastboot once i flash. May 09 17:23:03 Idk if fastboot requires something from boot.img May 09 17:26:27 should not, but some devices have ingenius implementations where flashing wrong boot.img may break bootloader May 09 17:26:57 how do i know if my device is one of them May 09 17:27:10 If i end up in EDL mode im quite screwed May 09 17:27:32 its an A/B device May 09 17:33:15 by trial and error I guess May 09 17:36:32 I dont think halium would be a bad boot img tho May 09 17:36:52 Is Halium completely depends on Android kernel ? May 09 17:38:22 Why I am asking this because. I doubted. Because I tried Ubport halium on my oneplus with Chinese touchscreen , it worked flawless. May 09 17:38:47 Is Halium completely de"> yes May 09 17:38:53 As usual like Android working. May 09 17:39:03 well, it can be because that chinese touchscreen works the same way as the original one May 09 17:39:20 The boot image finished building May 09 17:39:36 But when I tried mainline Linux on it. It didn't worked the touch. No response. May 09 17:39:44 * LynxZenial[m] posted a file: (18328KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/eoUsTPwAWmLWNGSIPcHfCogH/cheryl-halium-boot.img > May 09 17:39:45 This is what it gave me. May 09 17:40:03 It detected as u unknown in manufacturer (rmi4 ) May 09 17:40:16 @LynxZenial[m] [The boot image finished building], Yes. May 09 17:40:28 when you extract it May 09 17:40:30 does it look normal May 09 17:40:49 I build from source from gitlab. May 09 17:41:21 I want to know what touchscreen driver you guys has used in ubport halium for op6. May 09 17:41:34 I did a test on my pixel 2 xl May 09 17:41:40 Flashed cheryl boot img on it May 09 17:41:44 and it boots into fastboot May 09 17:42:22 Sometimes miracles happen. Sometimes not. May 09 17:43:14 Flashed the correct one now it boots (Pixel) May 09 17:43:22 Can anyone help me with working drivers for Chinese touchscreens. May 09 17:45:35 Maybe I should just try it May 09 18:11:03 So i flashed it May 09 18:11:05 and it keeps bootlooping May 09 18:11:18 it just goes back to splash over turns off and goes reboot May 09 18:27:57 it does not even generate a pstore file May 09 18:37:18 I can't figure it out May 09 18:40:23 Usually go to TWRP and pull logs would be my recommendation May 09 18:40:36 Which device and kernel version? May 09 18:41:59 Cheryl May 09 18:42:02 5.4 May 09 18:42:23 But when I tried mainli"> Something must be broken then :P May 09 18:42:40 sorry May 09 18:42:50 4.4 May 09 18:43:05 -_- that isn't going to boot May 09 18:43:44 Ik i just wanted to see how the device acts May 09 18:43:52 I flashed the cheryl boot img on cheryl May 09 18:44:03 and it just kept bootlooping to powered by android May 09 18:44:23 which im unsure why May 09 18:44:39 its like the bootloader does not accept the kernel May 09 18:45:40 if that was the case, you'd likely observe similar behavior like on pixel 2, when you flashed Cheryl image on it May 09 18:46:23 but i flashed the correct device things on it May 09 18:46:32 which is weird and it does not make a pstore file. May 09 18:47:04 Well, for pstore logs to stay, you need to make sure that no reboot occurs between booting the faulty kernel and booting the recovery May 09 18:47:21 There's a reboot when booting in the faulty kernel May 09 18:47:33 Which makes me impossible to debug May 09 18:47:35 pstore logs are stored in RAM, and if RAM is powered down and stopped refreshing, it loses its contents very quickly May 09 18:47:51 hm May 09 18:48:52 I have not tried halium 7 May 09 18:49:09 but my device is terble and a/b May 09 18:49:13 so halium 7 prob wont work May 09 18:49:29 Well, halium-boot part is pretty similar on 9 and 7 halium May 09 18:49:47 Does system.img need to be flashed May 09 18:49:54 for the device to boot with halium-boot May 09 18:49:58 One reboot is probably fine May 09 18:49:59 or it just checks for it in /userdata May 09 18:50:35 ideally, you need a following chain: bootloader starts "bad" kernel->bad kernel reboots the machine-> you make the bootloader start recovery May 09 18:50:48 I'd say then you have a very high chance of recovering pstore logs May 09 18:50:49 There's no recovery on halium-boot May 09 18:50:57 and I can't do fastboot boot TWRP.img May 09 18:51:03 i need to do fastboot flash boot TWRP.img May 09 18:51:17 Wait, uh, there isn't a recovery partition? May 09 18:51:25 sec May 09 18:51:32 https://github.com/Freemoon-Project/freemoon-mountpoints/blob/main/ls.cheryl May 09 18:51:36 this is list of parts May 09 18:51:44 Well, usually recovery is installed into recovery partition and booted with a key combo May 09 18:51:47 on older devices May 09 18:51:55 well its a boot.img May 09 18:52:07 wouldent twrp overwrite halium May 09 18:52:20 this device is quite new May 09 18:52:22 its 2017 May 09 18:53:05 huh, no recovery May 09 18:53:17 nope its inside the boot.img May 09 18:53:20 Well, my 2018 tablet still has recovery partition May 09 18:53:28 is it treble? May 09 18:53:38 it's treble a-only May 09 18:53:43 I have ab May 09 18:53:51 maybe that's why May 09 18:53:54 Maybe they changed stuff with ab, yeah May 09 18:54:06 maybe the mountpoints fix May 09 18:54:15 was a important thing? May 09 18:54:35 halium-boot does autodetect mountpoints May 09 18:55:04 argg idk why it doesnt boot then May 09 18:55:43 Maybe i built it wrong May 09 19:21:43 This is still the same Razer Cheryl right? May 09 19:23:26 Yeah May 09 19:23:35 I have no clue why it does that May 09 19:26:05 the kernel versio nis 4.4.267-perf+ May 09 19:27:36 Well the not having a proper recovery is a bit of a pain May 09 19:29:47 i wonder how lineageos devs did it? May 09 19:31:18 I think what could help me a lot is making a build for taimen (my secondary device) May 09 19:31:26 then trying to see what i did on taimen that worked well and what did not May 09 19:31:41 Cause razer phoen (cheryl) and taimen are quite simillar up to the partitions and evreything else May 09 20:13:44 I am trying to build https://github.com/Halium/android/tree/halium-10.0 May 09 20:13:49 Let's see how it goes May 09 20:15:51 It won't solve your issue most likely May 09 20:16:04 Well android 9 acts weird on razer phone May 09 20:16:09 I doubt Halium build is the issue, once it builds it's usually pretty OK May 09 20:16:25 At least in my experience... Issue more seems to be the kernel somehow May 09 20:16:35 I build using LOS kernel May 09 20:16:38 not stock kernel May 09 20:16:58 https://developer.razer.com/razer-phone-dev-tools/kernel-source-code/ The stock kernel is here May 09 20:21:35 what kind of issues the kernel could cause? May 09 20:21:47 The only thing i can think of is partitions May 09 20:22:48 @LynxZenial[m]> See what's wrong and fix May 09 20:23:00 But without logs it's hard May 09 20:25:21 kernel 4.4? May 09 20:25:42 try to disable CONFIG_VT in defconfig May 09 20:26:30 or even better, revert all defconfig changes from config-checker if you ran that and enable only CONFIG_DEVTMPFS=y for testing May 09 22:06:46 ok May 09 22:53:19 It still didint work I think at this point its just a waste of time May 10 00:42:14 LynxZenial, it's not easy, that's it, don't expect things just to magically work May 10 00:42:26 Oh im aware dont worry May 10 00:42:37 Just I dont see a lot of apps on it right now for it being my main driver May 10 00:42:46 I have it working on a pixel 2 (somewhat) and im fine with it **** ENDING LOGGING AT Mon May 10 02:59:56 2021