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