**** BEGIN LOGGING AT Mon Oct 26 02:59:57 2020
Oct 26 03:34:34 <ubptgbot> <Dale> (Photo, 783x612) https://irc.ubports.com/RPvBoYdJ.png 币圈电报微信群炸群、电报群指定群私聊、Twitter/Facebook点赞加粉等需要请私聊  @cindybtc
Oct 26 06:48:15 <ubptgbot> Joe was added by: Joe
Oct 26 07:15:04 <ubptgbot> Udbdwpqcc was added by: Udbdwpqcc
Oct 26 11:46:23 <ubptgbot> Gavin was added by: Gavin
Oct 26 12:05:20 <ubptgbot> kjones23 was added by: kjones23
Oct 26 13:14:35 * Tooniis uploaded an image: Screenshot from 2020-10-26 17-01-27.png (179KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/RWRVaTwKTrLuZIpYxsSHZFAh/Screenshot from 2020-10-26 17-01-27.png >
Oct 26 13:14:36 <Tooniis> I've wanted to do this for ages now
Oct 26 13:15:24 <ubptgbot> <dohbee> huh
Oct 26 13:17:03 <ubptgbot> <RealDanct12> that's a meme about ubptgbot
Oct 26 13:17:20 <ubptgbot> <RealDanct12> anyone that joined on their own (without invites) will show the following
Oct 26 13:17:33 <ubptgbot> <dohbee> yes i know how the bridging works
Oct 26 13:17:44 <ubptgbot> <RealDanct12> speaking of the bot, is the source code for that available?
Oct 26 13:18:33 <ubptgbot> <dohbee> i don't know which bot it is, but probably
Oct 26 14:28:33 <ubptgbot> Sohil876 was added by: Sohil876
Oct 26 15:11:36 <nergzd723[m]1> <Tooniis "I've wanted to do this for ages "> lol
Oct 26 15:11:45 <nergzd723[m]1> That's actually funny xD
Oct 26 18:50:58 <Kaderohr> Hi, im trying to port Halium 9 to Galaxy Note 9. When i trying to build halium-boot, i get the netx error: [223/539] including halium/libhybris/compat/camera/Android.mk ...cat: frameworks/av/media/libmediaplayerservice/Android.mk: No such file or directory[226/539] including halium/libhybris/compat/media/Android.mk ...cat:
Oct 26 18:50:58 <Kaderohr> frameworks/av/media/libmediaplayerservice/Android.mk: No such file or directory[319/539] including hybris/hybris-boot/Android.mk ...hybris/hybris-boot/Android.mk:71: warning: ********************* /boot appears to live on /dev/block/platform/11120000.ufs/by-name/BOOThybris/hybris-boot/Android.mk:72: warning: ********************* /data appears to
Oct 26 18:50:59 <Kaderohr> live on /dev/block/platform/11120000.ufs/by-name/USERDATACould not determine android architecture. Please pass it as 2nd argument using gettargetarch.Could not determine android architecture. Please pass it as 2nd argument using gettargetarch.[539/539] including vendor/samsung/zeroltexx/Android.mk ...build/make/core/Makefile:1607: error:
Oct 26 18:51:00 <Kaderohr> hardware/samsung/mkbootimg.mk: No such file or directory19:21:21 ckati failed with: exit status 1Please, can anyone help me?? Thanks :)
Oct 26 18:55:03 <nergzd723[m]1> I think erfan ported halium to starlte, so maybe you can use something from there
Oct 26 19:00:23 <Kaderohr> Ok, im going to try to find something about it to see if I can fix it. Thank you very much :)
Oct 26 19:15:37 <ubptgbot> <aribk> Anyone here familiar with slimport? When I connect an external monitor via slimport on my device running Ubuntu touch, I get a series of these in logcat: … 01-01 00:01:38.233     0  5756 E libEGL  : validate_display:99 error 3008 (EGL_BAD_DISPLAY) … 01-01 00:01:38.241     0  5756 E libEGL  : validate_display:99 error 3008 (EGL_BAD_DISPLAY)
Oct 26 19:15:37 <ubptgbot> … 01-01 00:01:38.255     0  5756 E libEGL  : validate_display:99 error 3008 (EGL_BAD_DISPLAY) … Any clues as to what I should do?
Oct 26 19:16:05 <nergzd723[m]1> What is your device?
Oct 26 19:17:28 <nergzd723[m]1> I think that might be related to caf-specific things, but idk
Oct 26 19:18:31 <ubptgbot> <aribk> @nergzd723[m]1 [What is your device?], My device is LG G4 (h815)
Oct 26 19:18:31 <nergzd723[m]1> Ah no, thats BAD_SURFACE
Oct 26 19:18:40 <nergzd723[m]1> Iiinteresting
Oct 26 19:18:54 <nergzd723[m]1> I have sony-sumire on same msm8994 chipset
Oct 26 19:19:04 <nergzd723[m]1> I get those BAD_DISPLAY errors too
Oct 26 19:19:07 <nergzd723[m]1> But it seems to work
Oct 26 19:19:39 <ubptgbot> <aribk> Well lots of things work fine on mine, just not connecting an external display via slimport.
Oct 26 19:20:10 <nergzd723[m]1> Can you write anything to external screens framebuffer?
Oct 26 19:20:18 <nergzd723[m]1> On my device its /dev/fb1 iirc
Oct 26 19:20:36 <nergzd723[m]1> Hm, that error might be the cause of miraclecast breakage on my device too
Oct 26 19:21:05 <ubptgbot> <aribk> @nergzd723[m]1 [Can you write anything to external screens framebuffer?], How do I do that?
Oct 26 19:21:29 <nergzd723[m]1> cat /dev/urandom /dev/fb1
Oct 26 19:21:41 <nergzd723[m]1> I'm not sure if it's fb1 or fb2 or fb0 tho
Oct 26 19:22:13 <ubptgbot> <aribk> OK. And I do this with the external display connected?
Oct 26 19:23:58 <ubptgbot> <aribk> @nergzd723[m]1 [cat /dev/urandom /dev/fb1], ...or not connected? And what should I be looking for as a result?
Oct 26 19:24:47 <nergzd723[m]1> External screen filled with noise
Oct 26 19:25:03 <nergzd723[m]1> Thats just to check if it even werks
Oct 26 19:30:00 <ubptgbot> <aribk> @nergzd723[m]1 [Thats just to check if it even werks], I don't get anything on the external screen.
Oct 26 19:30:54 <ubptgbot> <aribk> Plenty of noise in the terminal on the device though. Tried all three.
Oct 26 19:31:57 <nergzd723[m]1> <ubptgbot "<aribk> Plenty of noise in the t"> That's with fb0 I guess
Oct 26 19:32:15 <nergzd723[m]1> Can you check dmesg if the display is actually recognized and connected by MHL chip?
Oct 26 19:32:32 <nergzd723[m]1> btw some devices only initialize USB devices on boot, like sumire
Oct 26 19:32:38 <ubptgbot> <aribk> @nergzd723[m]1> <ubptgbot "<aribk> Plenty of noise in the t" [That's with fb0 I guess], No, with all three.
Oct 26 19:33:22 <nergzd723[m]1> I mean usually fb0 is screens framebuffer, so that's fine
Oct 26 19:37:02 <ubptgbot> <aribk> @nergzd723[m]1 [Can you check dmesg if the display is actually recognized and connected by MHL c …], Trying to decipher dmesg, but having some trouble. I'll post here in a sec...
Oct 26 19:41:45 <ubptgbot> <aribk> Here's the last portion of my dmesg right after: … - disconnecting from my pc … -connecting to external display with slimport, then disconnecting … - reconnecting to pc to print and extract dmesg. … https://pastebin.ubuntu.com/p/FtMMVq4WW5/
Oct 26 19:42:25 <ubptgbot> <dohniks> @nergzd723[m]1 [cat /dev/urandom /dev/fb1], I guess that should be `cat /dev/urandom > /dev/fb1`  … note the redirect
Oct 26 19:43:16 <ubptgbot> <aribk> That makes sense... I can test that, too, but so far absolutely nothing is happening on the external display.
Oct 26 19:45:47 <ubptgbot> <aribk> @dohniks [I guess that should be cat /dev/urandom > /dev/fb1  … note the redirect], Well, I tested using the redirect with each of the three (fb0...fb2) and got the same error with all three, namely: … cat: write error: No such device
Oct 26 19:46:51 <ubptgbot> <aribk> Without the redirect I got a steady stream of noise in the terminal with all three.
Oct 26 19:46:59 <ubptgbot> <dohniks> do any of those frame buffers show up/disappear when you plug in/out?
Oct 26 19:47:16 <ubptgbot> <aribk> How would I know?
Oct 26 19:47:28 <ubptgbot> <dohniks> ls -l /dev/fb*
Oct 26 19:47:36 <ubptgbot> <dohniks> with and without the monitor plugged in
Oct 26 19:47:44 <ubptgbot> <aribk> Will check...
Oct 26 19:49:08 <ubptgbot> <aribk> All 3 show up in both cases.
Oct 26 19:50:13 <ubptgbot> <aribk> Could this be a udev issue? Some missing udev rule maybe?
Oct 26 19:52:00 <ubptgbot> <aribk> Or some service that is not specified in my init.qcom.rc or the likes?
Oct 26 19:53:25 <ubptgbot> <dohniks> @aribk [Here's the last portion of my dmesg right after: … - disconnecting from my pc … -con …], do you literally mean "after", then you're not really capturing what happens "while" you plug in, right?
Oct 26 19:54:28 <nergzd723[m]1> <ubptgbot "<dohniks> @nergzd723[m]1 [cat /d"> Ahh yes
Oct 26 19:54:45 <nergzd723[m]1> btw try booting with screen plugged in, might be same dwc3 lowpower mode issue
Oct 26 19:55:45 <ubptgbot> <aribk> @dohniks [do you literally mean "after", then you're not really capturing what happens "wh …], That's right. But my original post further up was from logcat while I was plugging in.
Oct 26 19:56:31 <ubptgbot> <aribk> @nergzd723[m]1 [btw try booting with screen plugged in, might be same dwc3 lowpower mode issue], I'll try this now, then I've got to run.
Oct 26 20:00:56 <ubptgbot> <aribk> No luck with that either. I'll pick this up again in an hour or two.
Oct 26 20:43:51 <nergzd723[m]1> Interesting
Oct 26 21:53:55 <ubptgbot> Wessel was added by: Wessel
Oct 26 22:01:07 <ubptgbot> <aribk> On my LG G4 port I'm having this annoying issue. Every time I switch it off, it's impossible to restart it without removing the battery and replacing it. No combination of buttons works before you have removed and replaced the battery. But then it starts up when you press the power button.
Oct 26 22:01:16 <ubptgbot> <aribk> Any idea how I could fix this?
Oct 26 22:01:56 <nergzd723[m]1> There should be some key combo(handled by PMIC) which turns off the phone
Oct 26 22:02:07 <nergzd723[m]1> For sumire it's volup+power
Oct 26 22:04:12 <ubptgbot> <aribk> But you're supposed to be able to press the power button and then confirm in the on-screen dialog that you want to power-off. There must be a way to make that work correctly...?
Oct 26 22:04:55 <ubptgbot> <aribk> ...or for that matter choose restart.
Oct 26 22:04:59 <nergzd723[m]1> Ahh I didn't understand you correctly
Oct 26 22:05:07 <ubptgbot> <aribk> ok
Oct 26 22:05:31 <nergzd723[m]1> So when you choose power off in UT menu, the screen goes black, right?
Oct 26 22:05:43 <nergzd723[m]1> And it doesn't turn off
Oct 26 22:08:58 <ubptgbot> <aribk> Well, it certainly looks like it has turned off, but I suspect it hasn't.
Oct 26 22:09:24 <nergzd723[m]1> Does it turn off if you do sudo shutdown now in terminal?
Oct 26 22:09:42 <ubptgbot> <aribk> I'll try.
Oct 26 22:11:48 <ubptgbot> <aribk> I did 'sudo shutdown -h now' and the screen immediately went black. Impossible to restart it though.
Oct 26 22:12:19 <nergzd723[m]1> Interesting, then it should be on kernel side I think
Oct 26 22:13:01 <ubptgbot> <aribk> So possibly a kernel config setting of some sort could solve it?
Oct 26 22:13:30 <ubptgbot> <aribk> Having removed and replaced the battery, it started normally again.
Oct 26 22:15:14 <ubptgbot> <dohniks> @aribk [Having removed and replaced the battery, it started normally again.], what if you hold the power button long when it is in screen-off-unbootable state?
Oct 26 22:15:22 <nergzd723[m]1> <ubptgbot "<aribk> So possibly a kernel con"> Probably vendor messed something up, but if it works on Android it should work here too
Oct 26 22:16:31 <ubptgbot> <aribk> @dohniks [what if you hold the power button long when it is in screen-off-unbootable state …], Nothing happens. I've tried holding it for 30 seconds.
Oct 26 22:56:07 <ubptgbot> <aribk> Interesting... With the device on I can press the power button indefinitely without the device ever switching off. I just get the dialog on the screen, but nothing else happens.
Oct 26 23:10:53 <ubptgbot> <konradybcio> Vol+ or vol- and power are for hard reset
Oct 26 23:13:50 <ubptgbot> <aribk> @konradybcio [Vol+ or vol- and power are for hard reset], Well, none of those work either.
Oct 26 23:14:12 <ubptgbot> <konradybcio> Can't you remove the battery in G4?
Oct 26 23:14:17 <ubptgbot> <konradybcio> Pretty sure you can in G5
Oct 26 23:17:17 <ubptgbot> <aribk> Sure. But that's just it. That's the only way I can turn off this device. I'm trying to get help to find out what I have to do to make it work normally.
Oct 26 23:21:52 <ubptgbot> <konradybcio> Google says vol- and pwr for like 13s
Oct 27 02:56:08 <ubptgbot> <Natividad> (Photo, 763x557) https://irc.ubports.com/ZX07p408.png 电报增粉，群发，私聊，推特，脸书，油管，youtube点赞/增粉
**** ENDING LOGGING AT Tue Oct 27 02:59:57 2020