Tuesday, 2020-07-28

Qiangong2[m]Does the pinephone flashing script have the latest changes from the past two weeks? I'd like to try the camera00:15
T42Rachel %lastname% was added by: Rachel %lastname%01:50
T42<edp_17> @piggz [i cant add my jolla account or use warehouse u …], Sorry for the late response. I have this issue on my Note 4 (treltexx) port. (I thought this was somehow connected to sfos version because I didn't get this with 3.2.x.x.)06:43
T42Carr %lastname% was added by: Carr %lastname%07:48
T42Myra %lastname% was added by: Myra %lastname%11:00
Mister_Magistertfw i've been here for 5 years now11:41
* Mister_Magister annoying mal since 2015-08-0611:44
malMister_Magister: :D11:45
T42Danilo %lastname% was added by: Danilo %lastname%11:57
T42<Danilo %lastname%> 236511:57
T42<Danilo %lastname%> Hi guys, I just installed on my one plus one the sailfish. I'M very amazing but the camera doesn't work. Can you suggest me some solutions?12:01
piggzQiangong2[m]: no, the camera stuff hasnt landed yet12:25
piggzpketo: hi, can i request store access for a new device?  what details are needed?12:36
pketopiggz: the "Device model" line from ssu s output12:41
piggzpketo: one moment whilr i change that, it looks weird atm12:42
piggzcurrently, vendor = Volla and device = Phone (for Volla Phone) but Phone just looks wrong, so will change pretty device to Volla Phone12:42
pketowell the pretty name doesn't matter much, the (foo / bar) part at the end is more important, which is model / designation or something like that from the ssu variables12:45
malpketo: still having a proper pretty name is a good thing12:46
pketoyes, sure12:46
piggzpketo: Device model: Volla Phone (yggdrasil / yggdrasil)12:54
piggzand my id is the first imei12:55
pketopiggz: added13:04
piggzpketo: many thanks :)13:05
Mister_Magisterpiggz: u working on volla phone?13:52
Mister_Magisterpiggz: we r so trusted that pketo doesn't even ask to verify IMEI's xd13:52
piggzMister_Magister: yup ... its a pita mtk!15:03
Mister_Magisterpiggz: my friend was working on it too iirc15:05
Mister_Magisterthat's y im asking15:06
piggzoh, who15:06
Mister_Magisterpiggz: i was actually fixing android ota in volla phone xd15:08
Mister_Magistermoto z calls for me, hopefully i'll have gui today15:09
Mister_Magistermal: in systemctl i have user@0.service failed and i'm wondering what went wrong that it even tried to run user@0 (user@10000 is running even tho i don't have gui but i think i'm on 0 cause systemctl --user doesn't show lipstick etc)15:31
Mister_Magisterautologin@100000.service failed hmm15:33
Mister_Magisterahh i don't have CONFIG_VT cause of some issues15:35
ghosalmartinthere are 3 certain things in life, death, taxes and needing CONFIG_VT to get to UI16:06
Mister_Magister@elros34 ping u were fixing CONFIG_VT, can u show me how you reverted problematic commit?16:29
T42<elros34> no, I just know which commit needs to be reverted. It was somebody else: osum4est I guess and ghosalmartin16:31
Mister_Magisterghosalmartin: ohhh so it was you!16:36
Mister_Magisterghosalmartin: can u do that?16:36
T42<NotKit> @Mister_Magister [ahh i don't have CONFIG_VT cause of some issue …], we had that issue on Halium16:37
T42<NotKit> is it griffin?16:37
Mister_Magisterit is griffin indeed16:37
T42<NotKit> then I'm wrong, it was an issue with kernel 4.416:40
T42<NotKit> https://github.com/MotoZ-2016/android_kernel_motorola_msm8996/commits/halium-9.016:40
T42<NotKit> nothing related to CONFIG_VT there16:40
Mister_Magistermhm i'm using 15.1 branch from there16:41
T42<elros34> doesn't looks very hard, just 4 commits https://github.com/LineageOS/android_kernel_motorola_msm8996/commits/lineage-15.1/drivers/tty16:41
Mister_Magister"just 4"16:42
Mister_Magisteri see 5 commits16:43
Mister_Magisterthanks @elros34 i reverted all of them and it's workign16:45
Mister_Magisteroki doki, no gui and no user@016:48
Mister_Magisterthere is progress16:48
Mister_Magistercouldn't find an OpenGL ES implementation >:(16:50
Mister_Magisterthere is no /vendor partition but there is /system/vendor what will happen if i symlink it hmmmmmmmm16:53
Mister_Magisterno luck but there is opengles at least16:54
Mister_Magister"Failed to open ion device"  udev rules16:55
Mister_Magistermhm vendor ueventd.rc was missing. damn i'm smart xd17:03
* Mister_Magister jk me dumb17:03
Mister_Magisterhoho i got gui. For some reason /dev/mdss_rotator is rw-rw-r-- and from user you can't really open it17:17
T42<adampigg> what group is it, and are you in that group?17:17
T42<adampigg> nemo is nol onger in system in 3.317:18
Mister_Magisteri'm not cause i don't have access17:18
T42<adampigg> you need to modify init.rc17:18
Mister_Magisterand what group should i set17:18
T42<adampigg> just like vibrator17:18
T42<adampigg> graphics group? ..... there is a patch to fix vibrator device to system:input17:19
Mister_Magisteryeah graphics or input could do17:20
Mister_Magister@adampigg fortunately i just need to edit ueventd.rc in device repo :)17:22
Mister_Magistermal: do you have a second? i have quite a problem. first wizard crashes when i click language and rild seems to be waiting for Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default.  but it's running and i don't really see it crashing17:33
Mister_Magisterwell no i lied /vendor/bin/hw/android.hardware.sensors@1.0-service is running, can't find sensormanager17:34
Mister_Magisterfunnily enough there is bootctl but CANNOT LINK EXECUTABLE "/usr/libexec/droid-hybris/system/bin/bootctl": library "android.hardware.boot@1.0.so" not found17:35
Mister_Magisterand i ca'nt find that file either lol17:35
Mister_Magisterdroidmedia, got it17:37
Mister_Magisterdon't add libminisf without droidmedia bois17:40
Mister_Magisterthat… didn't help17:40
maldroidmedia has some sensor thingy17:43
Mister_Magisteryeah thats why i installed it but it didn't help17:43
Mister_Magisterand for some reason wizard is crashing on touch17:44
Mister_Magisteryeah… somehow sfos ended up with bootctl even tho android doesn't have it lmao17:46
maland you have new enough droidmedia?17:48
Mister_Magistermaybe not17:48
malhow old?17:49
Mister_Magisterwas at 52143f217:50
malthat should have had sensor service in it17:55
Mister_Magistermal: latest droidmedia didn't help either17:55
Mister_Magistermal: https://paste.opensuse.org/4d0f468117:57
Mister_Magisterfor reference, maybe you will see something that i don't17:57
Mister_Magisterafter clicking language startup wizard segfaults17:57
malyou seem to have same error I have seen17:59
Mister_Magisteroh? which one18:00
malMister_Magister: to /var/lib/environment/compositor/droid-hal-device.conf add these lines18:01
malif that doesn't help increase those a bit more18:02
Mister_Magisteryessi… okay18:02
Mister_Magistermal: shouldn't i put my screen size there?18:02
malwe hack around a bug by setting too big screen size :D18:03
Mister_Magisterwell mine is 256018:03
malyour log says you have 1440x256018:03
malso we increase it a bit to make kernel happy18:03
malhowever this will cause 16 pixel rows to be missing from the bottom of the screen18:04
Mister_Magisterokay, i was going meanwhile to droid-config to fix pixel ratio but it turned out i already changed it so was woindering why everything is so tiny18:04
Mister_Magistermal: ohno can't we do something about it?18:04
malfiguring out why kernel is not happy, most likely some issue with hwcomposer plugin18:04
malor something18:05
Mister_Magistermal: other than broken screen for a second, no difference18:05
malsame error?18:05
Mister_Magisterthe wizard is crashing idk about any other error18:05
malcheck log18:05
Mister_Magisterditto and no idea what error are you talking about18:08
maldid you even read the log you pasted earlier18:09
mal04-21 20:41:58.981  3665  5074 E SDM     : HWDevice::Commit: ioctl MSMFB_ATOMIC_COMMIT, device = 0 errno = 22, desc = Invalid argument18:09
maland the lines after that18:10
Mister_Magisteri did but i have different perception of what is important error18:10
Mister_Magistermal: https://paste.opensuse.org/2df144c018:15
Mister_Magisterseems okay…?18:15
Mister_Magistermal: got any other ideas? :)18:18
malthat shows no messages fro startupwizard18:40
Mister_Magistertrue i just wanted to show that it changed18:44
malthe real error could be somewhere else18:47
Mister_Magisterofcourse, lemme add those variables back and i'll be back with full log18:47
Mister_Magistermal: https://paste.opensuse.org/075d137b18:50
Mister_Magistermal: hmmm maybe that sensorservice is stopping some other services from running /guess/18:53
malmost likely something is missing from adaptation, like symlink /firmware -> /vendor/firmware_mnt18:59
malassuming you have such a mount18:59
Mister_Magister /firmware is mounted18:59
Mister_Magisterhmm i had to symlink /system/vendor to /vendor19:00
malshow output of "mount"19:01
malalso journal lg19:01
malwhat device is that?19:02
Mister_Magistermal: moto z griffin19:05
Mister_Magisterhttps://paste.opensuse.org/c9cad281 mal19:05
Mister_Magisteralso mal https://github.com/MotoZ-2016/android_device_motorola_griffin/blob/lineage-15.1/rootdir/etc/fstab.qcom19:05
Mister_Magisterif this kernel looks like having seizure to you too then i won't complain about that19:08
Mister_Magisterssh is causing WARNING: CPU: 0 PID: 5297 at ../../../../../../kernel/motorola/msm8996/net/core/skbuff.c:616 skb_release_head_state+0xe4/0xec()19:09
malMister_Magister: are you sure you didn't use some old .ks file?19:09
Mister_Magisteri did in fact19:09
Mister_Magisteri forgot it changed19:10
maljolla-startupwi[4558]: unable to open file '/etc/dconf/db/nemo': Failed to open file “/etc/dconf/db/nemo”: open()19:10
malthat is caused by old .ks19:10
malMister_Magister: there is now a thing called "build_packages.sh --mic"19:10
malwhich will build an image19:11
malafter creating new .ks and processing patterns19:11
Mister_Magistermal: i know i did build_packages.sh -ic19:11
malthen how did you have old .ks19:11
Mister_Magisterno i thought i had, didn't know mic updates ks, so no i don't have old ks unless i have old dcd19:12
ghosalmartinMister_Magister, wasn't it some android devs that broke CONFIG_VT due to pthread stuff?19:12
Mister_Magisterghosalmartin: fixed already thanks19:12
Mister_Magistermal: nope doesn't seem like there was any update to ks in dcd19:13
maldo you have latest submodules?19:13
maland correct target and platform sdk?19:13
maland tooling19:13
Mister_Magistertarget and tooling are latest19:14
Mister_Magisterdhd and dcd are latest19:14
ghosalmartinMister_Magister, was this the fix? https://github.com/ghosalmartin/android_kernel_google_marlin/commit/1331a23835cce8d80ae5ec9c62d90cbec9140355 or something like it?19:14
Mister_Magisterghosalmartin: i reverted 5 commits from tty dir :P19:14
ghosalmartinah fair enough19:14
ghosalmartinam guessing also this https://github.com/ghosalmartin/android_kernel_google_marlin/commit/aa7072ead1e24917dad8b30fa6947cae04ea01aa19:15
Mister_Magisterincluding that one19:15
Mister_Magisterghosalmartin: those 2 + 3 more19:15
ghosalmartinam finally unemployed again with free time so i may start porting again19:15
Mister_Magistermal: ks is definitely old19:15
malMister_Magister: just in case also update platform sdk19:15
Mister_Magistergood idea19:15
malMister_Magister: ok, make sure you have new .ks also19:16
Mister_Magisterbut it's
malok, then it's probably fine19:16
Mister_Magisterthen hecc idk why i have old ks19:16
Mister_Magisteroh… mystery solved i updated dcd but didn't rebuild it19:18
* Mister_Magister dumbass19:18
Mister_Magisterno… it's still generated wrong >:(19:20
Mister_Magistermal: how is droid-configs/installroot/usr/share/kickstarts/Jolla-\@RELEASE\@-griffin-\@ARCH\@.ks generated? i have latest dcd and yet it's generating old one even if i remove it19:24
T42<elros34> are you sure you have target? Wwhat sb2 ssu re returns. Latest target points to 3.2.x19:25
Mister_Magister>:( its still not updated?19:26
T42<elros34> maybe when 3.4.0.x will be out :)19:26
Mister_Magistergeez i trusted youuu19:26
Mister_Magistertho does target really matter?19:26
T42<elros34> for dconf issue: yes19:27
Mister_Magisterbrb then19:27
malyeah, latest in targets.json is still 3.2.119:30
malso you need to grab the correct one manually or update locally afterwards19:31
Mister_Magistergeeeez somone fix that plz19:31
piggzive mentioned it a few times19:44
Mister_Magistermal: i reinstalled target and now i'm getting ssu: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory like wtf19:47
malmaybe mismatch with tooling?19:48
malI usually use: sdk-foreach-su -l ssu re
Mister_Magisteri removed tooling too and got latest one19:48
maland then sdk-assistant update target_name19:48
Mister_Magisterno, i got latest target and tooling19:49
Mister_Magistermal: latest target was switched to
Mister_Magisteroh no19:53
Mister_Magisterwrong target19:53
malwhat did you use?19:54
Mister_Magisteri removed target to wrong device19:57
Mister_Magisterfinally proper ks20:16
Mister_Magisterrebulding droid-hal and mw against new target is for weak20:17
Mister_Magistermal: guess who has working wizards20:45
malok, did you need to graphics hack or not?20:47
Mister_Magisterno, i didn't20:48
Mister_Magistersecond wizard failed20:48
maldo you see the error in logs?20:48
Mister_Magisterrestart helped, probably one time thing20:50
Mister_Magisterye gui works now20:50
Mister_Magistersensormanager thingy is still here20:51
T42Ma7moud_kamel_3 was added by: Ma7moud_kamel_321:11
Mister_Magistersensorservice might be not working because /usr/libexec/droid-hybris/system/bin/minimediaservice: Waited one second for android.hardware.camera.provider@2.4::ICameraProvider/legacy/0. Waiting another...21:44
Mister_Magisterand /vendor/bin/mm-qcamera-daemon: Waited one second for android.frameworks.sensorservice@1.0::ISensorManager/default. Waiting another...21:45
Mister_Magistertho it might be that mm-qcamera-daemon is not the one providing camera21:45
Mister_Magisteridk anymore21:46
piggzMister_Magister: so, you are back porting?21:52
Mister_Magisterpiggz: was i away?21:52
piggzwell, not that active lately21:53
Mister_Magisteri know, burnout21:53
Mister_Magisterjust found out some motivation21:53
Mister_Magisterloosing it as we speak21:54
Mister_Magisternothing makes sense at this point21:55
Mister_Magisterhah so it's not mm-qcamera-daemon, progress21:56
Mister_Magisteror maybe it is21:59
Mister_Magisterthere is motorola.hardware.camera.provider@2.4-service but there's no android.hardware.camera.provider@2.4-service22:00
Mister_Magistertechnically motorola.hardware.camera.provider@2.4-service should provide android.hardware.camera.provider@2.4-service but it doesn't for whatevere reason22:26
Mister_Magister /system/bin/hwservicemanager: getTransport: Cannot find entry motorola.hardware.camera.provider@2.4::ICameraProvider/legacy/0 in either framework or device manifest.22:28
Mister_Magisterin manifest there is only android.hardware.camera.provider and motorola.hardware.camera.provider should register as this i tihnk but it doesnt. why binary eh22:36
mal@adampigg I also had the first boot network issue23:10

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!