Monday, 2019-12-09

T42<Miklos %lastname%> Good morning,06:48
T42<Miklos %lastname%> I am porting Sailfish to Galaxy S7 (herolte) with CM-14.1 base and the hybris-hal creation fails:06:48
T42<Miklos %lastname%> command: rpm/dhd/helpers/build_packages.sh06:48
T42<Miklos %lastname%> Error: Bad exit status from /var/tmp/rpm-tmp.1SbHnk (%install)06:48
T42<Miklos %lastname%> Log:
T42<Miklos %lastname%> Any help is appreciated!06:48
r0kk3rzfyi someone attempted a port to this device before, and this could be useful to check
r0kk3rzyou're building the hal inside the ubuntu chroot? it looks like it doesnt like the find command06:52
T42<Miklos %lastname%> Oops. Probably you are right. Thank you.06:53
r0kk3rzyou are supposed to build it in the ubuntu chroot06:59
T42<Miklos %lastname%> No, it didn't work in tge ubuntu chroot either. The hadk says I need to do this command in the platform, not in ubuntu chroot.07:38
T42<Miklos %lastname%> The make hybris-hal is done. I have done that in ubuntu chroot. This is the next step: packaging droid hal07:40
T42<elros34> its incompabilty between gnu and busybox find tool. Try to install find in platform sdk07:40
T42<Miklos %lastname%> Sorry for the confusion.07:41
T42<Miklos %lastname%> Thanks, I'll try that.07:41
T42<Miklos %lastname%> There is no find package. :(07:42
T42<Miklos %lastname%> And the findutils is aready installed07:43
T42<Miklos %lastname%> There is a busybox-symlinks-findutils package. It this what I need?07:44
T42<elros34> you need findutils not busybox symlink07:45
T42<Miklos %lastname%> Thanks for confirming. Find is installed.07:46
T42<Miklos %lastname%> I have reinstalled findutils, but the same error happens.07:48
T42<Miklos %lastname%> I also tried to add the '%define droid_target_aarch64 1' into droid-hal-herolte.spec, but that didn't help either.07:51
T42<elros34> are you sure you have up to date submodules?07:54
T42<Miklos %lastname%> No, I am not. How can I be sure in that? I have startedceverything from scratch a few days ago. So in theory I should have the latest of everything.07:56
T42<elros34> loooks like not, you are missing
T42<elros34> here is instruction:
T42<Miklos %lastname%> Yes, you are right. I am just wondering how this can be, but anyway I am applying that patch, retry and report. Thank you!08:01
T42<elros34> do not apply this patch, update whole submodule lilke in instruction instead08:02
T42<Miklos %lastname%> Ok. Thank you.08:07
T42<Miklos %lastname%> I tried to pull the master from mer-hybris but got some conflicts08:10
T42<Miklos %lastname%> 👍 Now the first package is successfully done. 😁 Thank you @Elros08:20
T42<Miklos %lastname%> and it is building the rest too.08:20
NeoChapaymal: how you fix BINDER_SET_CONTEXT_MGR bad uid 0 != 100008:27
NeoChapayMister_Magister: ^ ping too08:27
T42<Miklos %lastname%> Hmm, now I got another error: can't open droidmedia-0.20191025.0.tgz08:42
T42<Miklos %lastname%> and indeed in hybris/mw/droidmedia-localbuild/RPMS this file is not there.08:42
T42<elros34> do you use some old droid-config/hal repos?08:50
T42<Miklos %lastname%> How can I check?08:51
T42<elros34> did you create them like explained in HADK 7.1 or use existing one08:52
T42<Miklos %lastname%> 7.1? I am following hadk for release (Sep 30, 2019)08:53
T42<Miklos %lastname%> But maybe my local manifest was wrong.08:54
T42<elros34> chapter 7.1 in pdf, anyway if you use old repos expect more such a small issues.08:55
T42<Miklos %lastname%> I have copied over this missing tgz from my recent hammerhead port.08:55
T42<Miklos %lastname%> Yes, you probably are right. I will ditch this and start over folliwing strictly the hadk and not putting more into the local manifest.08:56
T42<Miklos %lastname%> Thank you!08:57
T42<Miklos %lastname%> Yeah, in thevrepo I used, the droid-config-device is not the latest master from mer-hybris but branch d19f643222.09:04
T42<Miklos %lastname%> The droid-hal-version is also from an older tree d5ea8a60a9.09:04
T42<Miklos %lastname%> Can I just refresh these two somehow?09:04
T42<Miklos %lastname%> Of course. Thanks.09:06
Mister_MagisterNeoChapay: i read logs/instructions09:13
NeoChapayMister_Magister: mal send you some patches in pastbin but i cant read it09:14
NeoChapayMister_Magister: have you some solutions ?09:14
Mister_Magisteri do. Those patches are the solution09:15
NeoChapayMister_Magister: can you get me link on patches ?09:15
Mister_Magisterthose patches you were talking about are the once09:16
NeoChapayMister_Magister: i can't find on pastpin die09:17
Mister_Magisterwell too bad09:17
NeoChapayMister_Magister: maybe you save patches somewere?09:18
NeoChapaybaaaaaaaaaad.....ok still waiting mai hehe ^_^09:19
T42fire_night was added by: fire_night11:29
T42<fire_night> Does Redmi note 4  latest port supports android apk too now?11:30
T42<adampigg> pls dont discuss AD here, it is proprietary sw12:54
T42hexc0de was added by: hexc0de14:41
UmeaboyHi! Are there any plans to actually release a hybris-16.0 branch at
UmeaboyI have just bought the Samsung Galaxy S10+ and it already has a unofficial version of Lineage working.15:17
Umeaboy15.1 only, but 16.0 is coming soon.15:17
malUmeaboy: hybris-16.0 has already been released, just not added to local_manifests repo, I forgot there even is such a repo15:20
UmeaboyWhere can I find a repo to add the device to? I normally use xperiasailors15:21
UmeaboyFor Sony devices.15:21
UmeaboyFor Samsung I don't know of any.15:21
malnot sure what you mean, there should be repos listed in some place where you get the lineage for that, unless they are annoying people and don't give the sources15:22
UmeaboyI'll check.15:33
UmeaboyWe stopped using device specific manifests?15:33
malthose have been rarely used, people can use if they want15:37
malalso it seems people rarely push repos to mer-hybris, they usually have their own github projects15:37
Umeaboymal: Android Q would be hybris-17.0 right?16:00
malI don't know about those letter codenames, is that android 10?16:10
UmeaboyI'm setting up my own repo so I have to know what hybris-version that Android corresponds to/with.16:19
UmeaboyAndroid 10.16:19
UmeaboyIf it's 16.1 or 17.0.16:20
T42<elros34> it's same as your lineage version: hybris-16 = lineage-1616:22
vknechtwhat to check/try when fails ?
vknechtchanged first entry of FIRMWARE_FOLDERS to read /system/vendor/firmware/, to no avail17:48
vknechtcommenting the udev rule running at least allowed the brcmfmac one to load it seems, but not much change...
T42<elros34> could be related to enabled selinux? You should at least have "Attempting to load firmware" in logs when script start18:57
vknechtdon't have any of the logger lines, even before disabling the script ; maybe those lines go only to dmesg ? only have journal retrieved offline by rebooting to official recovery and copying to sdcard19:05
T42<elros34> I have "Attempting to load" in journal but maybe this is not important. Why dont you use telnet?19:11
vknechtno usb at all19:12
T42<Miklos %lastname%> Hi @Elros, my S7 build has completed successfully and I flashed it on the device. Unfortunately it doesn't boot. I stucks at the Samsung logo. Cannot ssh, cannot telnet to the phone. Do you think this is kernel or sfos issue? Thanks.20:01
T42<elros34> check host dmesg, does it reboot?20:02
T42<Miklos %lastname%> No, it doesn't reboot. Cannot be switched off either. I can reboot with pressing buttons20:15
T42<Miklos %lastname%> into recovery.20:15
T42<elros34> what about host dmesg? you can also check in recovery whether you have /data/.stowaways/sailfishos/init.log20:18
rinigusvknecht & deathmist: nfc toggle bug -
rinigusas vknecht suggested, its permissions which were wrong. can be resolved by simple chown20:32
T42<Miklos %lastname%> @Elros, thanks I will check those.20:34
T42<Miklos %lastname%> @Elros, I have checked the init.log. It says telnet is started but cannot access from pc. The last line in init.log is: + exec /sbin/preinit --log-level=debug --log-target=kmsg21:38
T42<elros34> try telnet 2323. If it fails then show your init.log and dmesg21:41
T42<Miklos %lastname%> How can I access dmesg?21:41
T42<elros34> type dmesg -w on your pc, power on device and connect it21:42
T42<Miklos %lastname%> The problem is that if I reboot to recovery cannot access the file system from ubuntu, because when I click on the internal storage, the pc says : the folder content could not be displayed.21:43
T42<elros34> you don't need it, in recovery you have adb. You can also try: touch /data/.stowaways/sailfishos/init_enter_debug2 and try telnet again21:46
T42<Miklos %lastname%> Thanks. Here is the init.log:
T42<elros34> looks good if you create file I mentioned above you should be able to telnet21:55
T42<Miklos %lastname%> Oh, so I need to create a file init_enter_debug2. Sorry it wasn't clear. 😳21:59
T42<elros34> touch /path/to/file will create empty file22:00
T42<Miklos %lastname%> Thanks.22:00
T42<Miklos %lastname%> I have created the file but telnet still doesn't work. Should I restart the phone? I try.22:01
T42<Miklos %lastname%> Yes, I need to restart as I was in recovery. :)22:01
T42<Miklos %lastname%> Telnet still not able to connect.22:03
T42<elros34> read this:
T42<Miklos %lastname%> Thank you. Here is the dmesg -w:
T42<Miklos %lastname%> It looks like there is no mac address for usbnetwork. Well, no usbnetwork at all.22:10
T42<Miklos %lastname%> Segfault in libc-2.27.so22:11
T42<elros34> so read that halium instruction, it has all needed commands you need to execute22:12
T42<Miklos %lastname%> When I tried to manually assign the mac address as the halium doc says, I got Operation not permitted error from RTNETLINK22:21
T42<Miklos %lastname%> I have tried another mac address from an online generator. The same error message.22:24
T42<Miklos %lastname%> Yeah, I needed to do that as root. Sudo helped. :)22:25
T42<Miklos %lastname%> Yeah, now I am in with telnet!22:27
T42<Miklos %lastname%> .... and struggling what to look for.22:28
T42<elros34> follow instrution how to continue booting to systemd or you can remove  init_enter_debug2 and reboot. Now you need to grab journalctl --no-tail -f22:30
T42<Miklos %lastname%> I typed that command, it says: No journal files were found.22:31
T42<Miklos %lastname%> How can I continue booting to systemd?22:32
T42<elros34> like I said remove mentioned file or read instruction which you see in terminal22:33
T42<Miklos %lastname%> I removed the file and injected the echo continue...22:35
T42<Miklos %lastname%> Now the phone is still on samsung logo and in the console: + exec /bin/preinit --log-level=debug --log-target=kmsg22:37
T42<Miklos %lastname%> and nothing else is happening.22:37
T42<Miklos %lastname%> I have tried to reboot the phone from command line, but it is not doing that.22:40
T42<elros34> try with reboot -f22:41
T42<Miklos %lastname%> That works22:41
T42<Miklos %lastname%> I assigned a mac address and started the network. No I am in with telnet. It says on the console : to make post-switch_root halt before starting systemd, perform touch /init_enter_debug222:47
T42<Miklos %lastname%> I am in somekind of loop here.22:47
T42<Miklos %lastname%> Created that file, rebooted and injected the continue ...22:50
T42<Miklos %lastname%> And the same. Samsung logo on the phone and no movement in the console.22:51
T42<elros34> oh comon just type journalctl —no-tail -f after you echo continue, thats all22:52
T42<Miklos %lastname%> I did. Loads of error regarding power_supply max77854-fuelgauge: driver failed to report status property -2222:54
r0kk3rzpost logs22:54
T42<Miklos %lastname%> @Elros. Don't worry about it now. I make a new build as spotted a problem in one of the scripts in the dhd/helpers. My fault. Apologies for wasting your time.23:13
T42<elros34> I have nothing to worry as you didn't showed journal log :)23:15
T42<Miklos %lastname%> Sorry. It was only that power supply related stuff in there. I will try again with a new build. (hope with better luck) Thank you for your support so far.23:17
T42<Miklos %lastname%> Probably I'll be back.😁23:18
T42<elros34> so you need to be fast: reboot and try again or fix that error in kernel23:19
T42<Miklos %lastname%> I try with a second build once it is generated. Then, if it fails agan I will look for a fix for the kernel. Thanks.23:21
T42<Miklos %lastname%> Thank you for showing me how to bring up ip and telnet!23:22
T42<Miklos %lastname%> By the way, while I am building the ne image for S7, can I ask a questiin regarding Nexus5, please?23:25
T42<elros34> dont ask to ask just ask23:27
T42<Miklos %lastname%> Ok.23:28
T42<Miklos %lastname%> The MTP doesn't work. When I plug the cable in and select MTP connection, the message appears at the to of the screen 'Preparing USB mode' but nothing is happening on the pc. Where should I see the root cause, could it be kernel or sfos related?23:30
r0kk3rzkernel sounds like23:33
r0kk3rzpossibly an issue with the android gadget driver23:33
r0kk3rzdoes it work with lineageos?23:33
T42<elros34> do you have functionfs in usb gadget?23:35
T42<Miklos %lastname%> I don't know. How can I check?23:35
T42<elros34> in drivers/usb/gadget/android.c search for ffs23:37
T42<Miklos %lastname%> Not found.23:38
T42<elros34> so you need this patch:
T42<Miklos %lastname%> Thank you. I will try after I finished with the S7. :)23:42
T42<Miklos %lastname%> Got another one. Also hammerhead the same cm12.1 base. The video recording doesn't work. When I tap on the red button, the jolla-camera freezes and the app cannot be restarted (needs to restart the device if want to use camera again) Shooting pics works fine.23:45
T42<elros34> video playback works? if yes then check /usr/libexec/droid-hybris/system/bin/logcat and GST_DEBUG=droidvdec:5 jolla-gallery23:48
T42<Miklos %lastname%> Yes playback works.23:48
T42<Miklos %lastname%> Thank you I will try this too.23:49
T42<Miklos %lastname%> Now the packaging of S7 failed because cp: will not overwrite just-created $ANDROID_ROOT/hybrys/mw/droidmedia-localbuild/installroot/usr/libexec/droid-hybris/system/lib/libdroidmedia.so23:52
T42<elros34> sorry of course I mean jolla-camera not gallery23:52
T42<Miklos %lastname%> I got that, thanks ;-)23:53
T42<Miklos %lastname%> The output of gst_debug:23:58
T42<Miklos %lastname%> (Photo, 720x1280)

Generated by 2.17.1 by Marius Gedminas - find it at!