| T4 | <Hound77> @austenite How do I fix this ? gralloc.default.so not found. | 03:20 |
|---|---|---|
| T4 | <austenite> @Hound77 is gralloc.default.so present in /vendor/lib/hw ? | 04:24 |
| T4 | <austenite> or there should be something like garlloc.sdm630.so | 04:26 |
| T4 | <austenite> the last joined person in this group is a bot | 04:33 |
| T4 | <Hound77> @austenite I couldnt find any. But there is this "./payton/proprietary/vendor/lib/libgralloc1.so". | 04:38 |
| r0kk3rz | where do you see that error? | 04:53 |
| T4 | <Hound77> https://0x0.st/zbZ6.txt | 04:55 |
| r0kk3rz | lol | 04:56 |
| r0kk3rz | you're way too early for checking hwcomposer | 04:56 |
| r0kk3rz | are you in 232 telnet? that seems to say otherwise | 04:57 |
| r0kk3rz | *2323 | 04:57 |
| T4 | <Hound77> Yes | 04:57 |
| r0kk3rz | ok, how is the init process going? dhi completing? | 04:58 |
| T4 | <Hound77> https://0x0.st/zbPn.txt | 04:58 |
| r0kk3rz | thats not what im talking about | 04:59 |
| r0kk3rz | the systemd init process, journalctl | 04:59 |
| T4 | <Hound77> https://0x0.st/zbZB.txt | 05:00 |
| r0kk3rz | Sailfish droid-hal-init: Failed to initialize property area | 05:01 |
| r0kk3rz | ok so you need to fix that first | 05:02 |
| T4 | <Hound77> I did this https://github.com/mer-hybris/droid-hal-sony-nile/blob/master/droid-hal-common.inc#L38 … I added "%define makefstab_skip_entries /" to droid-hal-payton.spec | 05:04 |
| T4 | <Hound77> <r0kk3rz> Any other this before I rebuild the zip ? | 05:05 |
| T4 | <Hound77> other *errors | 05:05 |
| r0kk3rz | try to avoid doing multiple things at once | 05:06 |
| T4 | <Hound77> What about gralloc.default.so ? | 05:07 |
| r0kk3rz | ignore that for now | 05:08 |
| r0kk3rz | focus on getting droid-hal-init to complete successfully | 05:08 |
| T4 | <Hound77> Is this right ? https://0x0.st/zbTj.spec | 05:09 |
| r0kk3rz | looks ok | 05:10 |
| T4 | <Hound77> I'll proceed to making zip then. | 05:10 |
| T4 | <Hound77> Made the changes and tooks the logs, … dmesg: https://0x0.st/-k.txt … init:https://0x0.st/zbT_.log … journal:https://0x0.st/zbT2.txt | 05:45 |
| T4 | <Hound77> *dmesg:https://0x0.st/zbT9.txt | 05:50 |
| wdehoog | spiiroin: on my phone (oneplus one) a long time ago I patched statefs-providers to fix detecting battery full | 07:02 |
| wdehoog | spiiroin: however a few versions back the led stopped blinking at battery full. I think it is caused by 10mce.ini loading the | 07:03 |
| wdehoog | spiiroin: battery-udev module. can I load battery-statefs instead and if so how? | 07:03 |
| spiiroin | wdehoog: just change the plugin from the ini-file, but ... that statefs plugin is deprecated. so if you have some fix, I'd like to take a peek and try to see if udev plugin can be fixed | 07:14 |
| wdehoog | spiiroin: thanks. here are my changes: https://api.merproject.org/package/view_file/nemo:devel:hw:oneplus:bacon/statefs-providers/provider_power_udev.patch | 07:16 |
| * Mister_Magister is still waiting for when spiiroin will finally completes task | 07:22 | |
| * spiiroin thinks Mister_Magister might as well name the task | 07:36 | |
| spiiroin | wdehoog: There is usually some delay between reaching "100%" and actually hitting battery full. But I gather the problem is that battery full is never declared? | 07:40 |
| spiiroin | I've seen one device like that, but for now it has been regarded as kernel bug | 07:41 |
| spiiroin | wdehoog: what version of mce you are using? | 07:42 |
| wdehoog | spiiroin: indeed, full was never detected since the status remains "Charging" | 07:42 |
| wdehoog | spiiroin: running sailfishos 3.0.2.8 | 07:42 |
| wdehoog | spiiroin: mce 1.99.8 | 07:44 |
| spiiroin | wdehoog: can you check if this helps? https://git.merproject.org/spiiroin/mce/tree/wdehoog_oneplus_battery_full | 08:05 |
| wdehoog | spiiroin: thanks. I'll try tonight. | 08:07 |
| spiiroin | wdehoog: also.. about that "qpnp-dc" power supply device. chances are that you might need to blacklist that/others. ref: https://git.merproject.org/mer-core/mce/blob/master/inifiles/battery-udev-devices.ini | 08:11 |
| spiiroin | and for debugging checking this might be useful too https://git.merproject.org/mer-core/mce/blob/master/inifiles/battery-udev-properties.ini | 08:11 |
| T4 | <DSstill01> mals: i got 15.1 working after that patch | 09:22 |
| T4 | <DSstill01> esketit | 09:22 |
| mal | good | 09:31 |
| T4 | <DSstill01> well, now, well, i created this file https://bpaste.net/show/0a3b08e369f1 , like nile, which is the lipstick config in sparse. how can i tell lipstick to use it? | 09:48 |
| mal | if you place it in the same place as it was on nile repo it will be used | 10:00 |
| T4 | <DSstill01> but that doesnt get used | 10:00 |
| T4 | <DSstill01> do i have to rebuild configs and rootfs or add it to some dbus db? | 10:01 |
| T4 | <vvreddy> @NotKit sur … Did u release a new version for santoni ? | 10:10 |
| T4 | meltygram was added by: meltygram | 10:33 |
| T4 | <adampigg> mal: hows your camera PR? | 11:31 |
| mal | @adampigg sorry, I haven't looked into that recently, maybe I should | 11:38 |
| T4 | <adampigg> mal: maybe you should :) | 12:40 |
| mal | @adampigg too many projects | 12:43 |
| Mister_Magister | mal: you have mce-plugin-libhybris 1.12.3 in fairphone but when i updated it to 1.12.3 (on the device on which proximity sensor wasn't working) all sensors stopped working | 13:31 |
| mal | are you sure it was about that package, that has nothing to do with sensors | 14:13 |
| Mister_Magister | mal: updating the one you told me about did nothing (phone didn't even pick up update) | 14:43 |
| mal | logs logs logs | 14:47 |
| mal | how do you expect anyone to help if you provide no information | 14:47 |
| T4 | <adampigg> Different day, same issues :D | 14:58 |
| T4 | <eugenio_g7> @adampigg: upgraded my latte to 3.0.3, we should rebuild/update on OBS qtbase, lipstick-qt5, pulseaudio-modules-droid-keepalive, sensorfw once the 3.0.3 target appear :D | 15:14 |
| T4 | <eugenio_g7> (browser still doesn't work, btw :P) | 15:15 |
| T4 | <Hound77> @elros34 What should I do next ? … initlog:https://0x0.st/zbT_.log … journal:https://0x0.st/zbT2.txt … dmesg:https://0x0.st/zbT9.txt | 16:13 |
| T4 | <Hound77> When can start 12.1? | 16:13 |
| T4 | <Hound77> [Edit] When can I start 12.1? | 16:14 |
| mal | what are supposed to look in those, you just give random logs without any information what the situation is | 16:14 |
| T4 | <elros34> Charlie: init logs is not needed anymore and journal is incomplete. What is 12.1? | 16:15 |
| T4 | <Hound77> The port guide "Modifiacations and Patches". | 16:19 |
| T4 | <elros34> If you mean 12.1 in HADK then it's already done. You don't need to worry about it. | 16:25 |
| T4 | <Hound77> https://0x0.st/zbag.txt | 16:28 |
| Mister_Magister | mal: i kno i kno it's just hard to debug while "in run" | 16:32 |
| T4 | <Hound77> @elros34 I didnt do anyting that is mentioned modifications to "bionic", "system/core" and others. I didnt go through any of it. But I did the selinux part as it was mentioned on 9.3.1 | 16:35 |
| T4 | <elros34> this modifications are already in mer-hybris repos | 16:37 |
| T4 | <elros34> Does log hang at "Started udev Wait for Complete Device Initialization." even if you wait longer? upload your droid-* repos to github and explain what you did | 16:39 |
| T4 | <Hound77> journalctl : https://0x0.st/zban.txt | 16:42 |
| mal | no point giving the same log if there is now change | 16:43 |
| T4 | <Hound77> Its the second time. Still I ended up with the same result. | 16:44 |
| T4 | <Hound77> I have already uploaded them to the github but not the line "%define makefstab_skip_entries /" to droid-hal-payton.spec" as you specified. | 16:47 |
| T4 | <Hound77> https://github.com/WinterHound/ | 16:48 |
| T4 | <elros34> Are you sure that your device is not 64bit? https://github.com/WinterHound/droid-hal-payton/blob/master/droid-hal-payton.spec#L9 | 16:56 |
| mal | I was about to say that also | 16:56 |
| mal | based on logs it is aarch64 | 16:56 |
| mal | and that define is wrong anyway | 16:57 |
| T4 | <Hound77> @elros34 Yes it is. I have mentioned armv7hl. | 16:58 |
| mal | @Hound77 this line https://github.com/WinterHound/droid-hal-payton/blob/master/droid-hal-payton.spec#L9 should be: %define droid_target_aarch64 1 | 16:58 |
| mal | unless your android is for some reason pure 32-bit build which I highly doubt | 16:58 |
| T4 | <Hound77> I gave a wrong arguement. | 16:59 |
| T4 | <elros34> but is your android really 32 bit? | 16:59 |
| mal | why would anyone build 32-bit android for 64-bit device | 17:00 |
| T4 | <Hound77> No no you are right. Its 64. I didnt know how to define so I thought this was right "%define droid_target_armv7hl armv7hl". | 17:01 |
| T4 | <Hound77> I'll change that. | 17:02 |
| mal | @Hound77 how would that be right, armv7hl is 32-bit | 17:02 |
| mal | the instructions did tell to use droid_target_aarch64 if you have 64-bit device | 17:02 |
| T4 | <Hound77> Oh. | 17:04 |
| mal | in that place at least, the target arch is different this | 17:04 |
| mal | *thing | 17:04 |
| T4 | <Hound77> I thought it has to be same as Platform-SDK-Target which was armv7hl. | 17:06 |
| T4 | <elros34> mal: does dm_verity has to be disabled? https://github.com/WinterHound/android_kernel_motorola_msm8998/blob/7a3f64488efcb5e70f4351aef67a310fa314adfb/arch/arm64/configs/lineageos_payton_defconfig#L1528 | 17:10 |
| mal | sometimes yet | 17:11 |
| mal | depends on the device | 17:11 |
| T4 | <Hound77> And in 4.1 its is mention that it set PORT_ARCH="armv7hl" if you want to port for 64bit. | 17:11 |
| mal | yes, that's what I said | 17:12 |
| mal | those are different PORT_ARCH is sfos arch, the one in droid-hal spec is android arch | 17:12 |
| T4 | <Hound77> @elros34 Is this the reason I get "varity is set it disabled" every time my phone reboots. | 17:15 |
| T4 | <elros34> I have no idea. So your device reboots now? | 17:18 |
| T4 | <Hound77> This is new after I flash the zip. It was there before flashing. The phone just boots and stays on boot logo. | 17:21 |
| T4 | <elros34> what if you wait couple of minutes. Did you get further logs in journal? | 17:29 |
| T4 | <Hound77> Same error. | 17:35 |
| T4 | <elros34> I never did port for a/b device. Is this correct to define both a and b partitions in fixup-mountpoints? https://github.com/WinterHound/hybris-boot/commit/d56db778867ee0b0321b2d91dd5e90f9bd793f30 | 17:35 |
| T4 | <elros34> maybe systemctl —nopager could reveal something | 17:41 |
| T4 | <Hound77> This is what I for list patitions https://0x0.st/zbBK.txt | 17:42 |
| T4 | <Hound77> https://0x0.st/zbBb.txt | 17:47 |
| T4 | <Hound77> Currently I get varity mod is set to logging. | 17:47 |
| T4 | <Hound77> [Edit] Currently I get varity mode is set to logging. | 17:47 |
| *** OhYash1 is now known as ohyash | 17:49 | |
| T4 | <adampigg> @eugenio_g7 [@adampigg: upgraded my latte to 3.0.3, we shou …], how did you do that without rebuilding PA modules? local build? | 17:52 |
| T4 | <elros34> Charlie: can you manually mount system partition? what files it contains? | 17:55 |
| T4 | <eugenio_g7> @adampigg: kept old PA version because I'm lazy, then dist-upgraded my local target and rebuilt the rest | 17:58 |
| T4 | <adampigg> @eugenio_g7 im too lazy for that, will wait until its on obs1 | 18:17 |
| T4 | <adampigg> any browser improvement? | 18:17 |
| T4 | <eugenio_g7> Nope | 18:38 |
| T4 | <eugenio_g7> But I'm looking into it | 18:38 |
| T4 | <adampigg> have you found anything? clues? | 18:41 |
| T4 | <adampigg> @eugenio_g7 also, i found a bug ... i was having poor performace, so i ran top, and it was 'find' from our iio script | 18:44 |
| T4 | <adampigg> seems it can start up randomly, and run forever! | 18:44 |
| T4 | <DSstill01> Why aliendalvik starts if i run it from bash shell but not if i start the service? | 18:56 |
| wdehoog | spiiroin: I could not build your tree on OBS, used SDK and added your Quick Hack to mce 1.100. | 19:47 |
| wdehoog | spiiroin: battery full detection now works | 19:48 |
| wdehoog | spiiroin: when connected to a pc the battery became immediately full blacklisting device 'usb' makes things work | 19:48 |
| wdehoog | hop you read the logs | 19:48 |
| lanodan | Probably not the right channel but does SailfishOS has Push Notifications or some kind of way to have it for a notification server (writing an app would be fine if not)? | 20:44 |
| lanodan | Related to https://git.pleroma.social/pleroma/charisma btw (go again on the URL if it gets you on the homepage, gitlab is weird) | 20:45 |
| *** PragmaticAnarchi is now known as Unbegriff | 22:51 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!