Tuesday, 2019-04-09

*** keithzg__ is now known as keithzg_00:01
MeowDudehow solid is hybris11 in 2019?01:05
r0kk3rz11? likely to be unchanged since the last time you tried01:11
T4<Hound77> What do I need to do in 5.3 Configure Mount Point.01:28
T4<birdzhang> austenite already gave you the answer01:30
T4<birdzhang> run ls -l /dev/block/bootdevice/by-name/  via adb01:30
T4<birdzhang> @Hound77 https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints01:32
T4<Hound77> I did that but what do I do it after that. Do I have to do something with that data.01:33
T4<birdzhang> then you can make hybris-hal01:34
r0kk3rzso you added your device to the script?01:34
T4<Hound77> No01:39
r0kk3rzwell, you need to do that01:41
MeowDudeI was tempted to port sailfish OS to the Nexus S but I am unsure how that will work out01:56
r0kk3rztoo old to bother with02:01
r0kk3rzold exynos, powervr gpu, 512mb of ram, yeah you probably wont have the easiest of times02:02
MeowDudeoh well, android 4.0 runs great on it. Capactive devices look bad with sailfish anyway02:08
MeowDudecapacitive key* devices02:08
T4<Hound77> @birdzhang When I ran the command "ls -l /dev/block/platform/*/*/by-name" the result in adb I get 68 lines but I run it on TWRP terminal I get 78 lines. So do I have to use the result from TWRP.03:25
T4<birdzhang> i not tried run on TWRP, i suggest use 68 lines03:27
T4<Hound77> Okay03:29
r0kk3rztwrp might mount all kinds of random things03:32
r0kk3rzyou'll soon know if its wrong, it wont boot or things wont work03:32
T4<Hound77> @birdzhang I got the result from "ls -l /dev/block/platform/*/*/by-name". Most of the format looks this way "oem_a -> /dev/block/mmcblk0p63 … " and "vendor_a -> /dev/block/bootdevice/by-name/oem_a". What format do I have to use it for fixup-mountpoints ?03:40
T4<birdzhang> https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints03:40
T4<Hound77> I saw that but some of them start with "block/bootdevice" and some "block/platform". Whats the prefix path do I have to use ?03:42
r0kk3rzthe one your device uses03:43
T4<birdzhang> block/bootdevice/by-name/ is better03:43
r0kk3rzits ultimately a sed script03:44
r0kk3rzso the first part of the string needs to match03:44
T4<Hound77> So, " vendor_a -> /dev/block/bootdevice/by-name/oem_a …  " to " block/bootdevice/vendor_a oem_a  " and, … " xbl_a -> /dev/block/mmcblk0p1 " to " block/bootdevice/xbl_a mmcblk0p1 ".03:50
T4<Hound77> And I have missed "/by-name/ ".03:52
T4<austenite> @Hound77 what device?03:53
T4<Hound77> Moto X4.03:56
T4<austenite> how is it in android fstab file?03:56
T4<Hound77> (Document) http://3das7vpgt73yxclb6agz4sz2a2bt7bqqfjucjhhbb5jnndxcd4o4lfid.onion/0m98QsEGal.txt03:57
T4<austenite> @Hound77 there should be persist in /dev/block/bootdevice/by-name04:09
T4<austenite> in the directory /dev/block/bootdevice/by-name/04:09
T4<Hound77> I did that I just wanted to claify the prefix that is need to be given on fixup-mountpoints.04:13
T4<austenite> by-name04:14
T4<austenite> for your device as it is in fstab04:14
*** Piece_Maker is now known as Acou_Bass07:58
T4<Err0r_extinct> should i need to install the tooling??19:08
T4<Err0r_extinct> yes i need to19:14
piggzevening all19:23
piggzrinigus: is pure maps broken in 3.0.3?19:23
wdehooghi, for me it is a very frustrating upgrade to the startup wizard acts weird, currently I have to boot 3 times to get most stuff working19:25
wdehoog1st time startupwizard skips language chooser (allthough it looks like it is shown very very shortly),  1st thing is enter security code19:26
wdehoog2nd time language chooser is shown, then license agreement, then starting..., then security code, then wlan (I skip), then timezone, then tutorial19:27
wdehoogthis is without a sim, when enabling wlan in the wizard I have to reboot a 3rd time to get things working19:28
wdehoogmal: I updated droid-media, that did not help, I copied some stuff from droid-config from fp2 and now a UI appears when the startup wizard is launched19:29
vknechtnot sure it's really related, but do you boot LOS at least once before flashing SFOS ? found it helped here for wlan stability19:30
wdehoogmal: in case you have time to look at some journals: 1st boot http://ix.io/1FMg, 2nd boot http://ix.io/1FMi, sorry no dmesg (seemed ok) or logcat19:30
malwdehoog: what issue are you trying to solve19:31
wdehoogmal:  always flash a new image, the startup wizard is 'broken'19:31
malbroken how?19:31
wdehoogsee my remarks above19:32
malMar 12 22:24:42 Sailfish jolla-startupwizard-pre-user-session[1669]: [D] unknown:0 - eglHybrisLockNativeBuffer failed, error: 300019:33
malMar 12 22:24:42 Sailfish systemd[1629]: jolla-startupwizard-pre-user-session.service: Main process exited, code=killed, status=11/SEGV19:33
malwdehoog: you will not need the camera detect stuff, that is specific only to fp219:35
wdehoogmal: ok,thanks19:35
malwdehoog: since fp2 has two different camera module types which user can change I needed that for changing camera configs at boot19:36
piggzmal: howdoes that work with p-o-v ?19:36
malno other device has camera modules that user can change19:36
malpiggz: I haven't tried19:37
wdehoogmal: so only the %pre stuff can go? the droid-camres is still needed?19:37
malwdehoog: you do not need anything related to droid-camres19:37
malwdehoog: normal device just have hardcoded configs the usual way19:37
wdehoogmal: ok, I thought it was needed for the new camera app you guys are working on19:38
malwdehoog: anyway that change you added is actually missing most of the things19:38
malbut since it's not needed just remove the whole commit19:38
wdehoogmal: any idea why eglHybrisLockNativeBuffer did fail?19:38
malwdehoog: some droid-hal-init race-condition maybe?19:39
malpiggz: we need to add a check that value read from nemo configuration is actually value i.e. compare it to caps, not sure if that is done everywhere19:39
piggzmal: it is done in settings.resolution() where it checks against the model19:40
malpiggz: but is that always used?19:40
malneed to check19:40
piggzwhereatleast, the code exists, so we just need to check it is used every19:40
piggzoops, cursor moved!19:41
T4<Err0r_extinct> hey there LIPSTICK_OPTIONS=-plugin evdevtouch:/dev/input/event0 -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap is the line should be like this or there are no space between plugin and evdev?19:56
wdehoogvknecht: no I never boot LOS, weird thing is that this is the first release where wlan and the startupwizard act so bad19:57
malwdehoog: things don't just randomly break like that20:01
wdehoogmal: I also get these 'eglHybrisLockNativeBuffer failed, error: 3000' errors when trying to open a photo in the gallery20:21
wdehoogused Advanced Camera, very nice app20:21
vknechtindeed, and big up for video recording :-)20:24
T4<Err0r_extinct> hey there when trying to build packages (rpm/dhd/helpers/build_packages.sh) got an error some devices in your Android tree are 64bit targets. If your device is aarch64, …             please define droid_target_aarch64 in your .spec, otherwise define droid_target_armv7hl20:25
T4<Err0r_extinct> any solution??20:25
malit says what to do, depends whether your device is 32 or 64 bit20:29
T4<Err0r_extinct> 64 bit20:29
malso you add "%define droid_target_aarch64 1" to droid-hal spec like this https://github.com/mer-hybris/droid-hal-sony-nile/blob/master/droid-hal-common.inc#L5 note that you need to add it anywhere before the last include20:31
T4<Err0r_extinct> ok20:34
riniguspiggz: no way to check for me, no access to 3.0.3. Heard that ubidi open call was missing for some reason. Don't know the details though20:38
piggzrinigus: i complained about libicu being upgraded and breaking abi ... and someone commented that it also broke puremaps20:40
T4<Err0r_extinct> it's asking to build libhybris should i build it (while running rpm/dhd/helpers/build_packages.sh))20:41
vknechtunless you've a good reason to say no, say yes (or even "all", if it's your first time), the script is just polite :-)20:43
T4<Err0r_extinct> ok20:44
riniguspiggz: broken icu api probably also means broken osm scout server due to mapnik backend. For pure maps, its mapboxgl qml plugin that fails. So, will have to somehow provide new rpms for 3.0.3 users. Fortunately, its all compiled through obs, although openrepos doesn't allow me to differentiate users by sfos version20:49
piggzrinigus: i have method for brute-forcing the old libicu to be installed, but it isnt pretty!20:51
piggzzypper --download-only ....20:51
piggzrpm -i --nodeps20:51
riniguspiggz: not pretty, indeed. Maybe opening separate repo for 303 will do, until most users update20:53
vknechthacks upon hacks, upon hacks... from kernel up to the UI leafs :-)20:53
piggzrinigus: i still maintain libicu allows multiple versions to be installed, so it was unnescessary for jolla to add the Obsoletes: paramter to the new version20:54
piggzbut alas20:55
riniguspiggz: we can drive that point through by updating to 3.0.3 api only after main ports have updated to it. :)20:56
piggzyes, i think thats what i'll have to do20:57
rinigusWell, 303 is quite far for me right now. We are still on 301 with onyx and there is no rush :) . So, let's see when we get there and will probably have to point fingers at this obsoletes statement21:02
vknechta good point for meeting perhaps ?21:03
piggzvknecht: rinigus: maybe, though they already replied here https://together.jolla.com/question/203300/cbeta-maybe-a-bug-libicu-upgraded-to-63-in-3031-obsoletes-52/?comment=203676#comment-20367621:21
piggzreason is to keep size down ... but, meh21:21
piggzif the obsoletes: wasnt there, we could ship it on openrepos without issue21:21
T4<Err0r_extinct> what is the extra name part should i give any thing to the EXTRA_NAME tag ??21:28
malif you mean in mic build that can be anything, it just ends up in the filename21:38
osum4esthello! i'm attempting to port google/marlin using lineageos 15.1, but i keep getting an error when running "repo sync --fetch-submodules", revision stable/lineage-15.1 in LineageOS/android/kernel_google_marlin not found. heres my manifest.xml: https://hastebin.com/fegezovexe.makefile22:11
osum4estand i cant seem to figure out how to list available revisions22:16
malrun once without --fetch-submodules22:23
osum4estah, thanks! i change LineageOS in my manifest back to CyanogenMod and it seems to be working. guess i wasn't supposed to change that!22:24
malis the manifest really that, the error you gave had different path22:25
malosum4est: ah, the real error is that the revision should be lineage-15.122:25
malso remove the stable/ from those22:25
malbtw, hybris-15.1 is a bit broken now22:26
osum4estborken how?22:29
osum4estmal, if i use just lineage-15.1, it also doesn't seem to work revision lineage-15.1 in LineageOS/android_kernel_google_marlin not found22:36
malosum4est: you can see that the revision is there https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-15.123:03
malso you must be doing something wrong23:03
osum4estim running repo sync without the submodules right now, and it seems to be downloading lots of stuff now, so hopefully that will work23:04
maland hybris-15.1 won't build right now because of repository version mismatch, I have rebased it but I haven't pushed the changes because I haven't been able to verify the rebased repos23:04
osum4estoh, shoot. is it an easy change i can make? 15.1 is the only lineageos version available for marlin23:05
r0kk3rzmal: just push it :P if its already broken then its ok23:06
malwell it's rebasing all hybris patched repos23:06
malr0kk3rz: I need to check some patches first, there might be one or two new ones missing maybe23:07

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