Thursday, 2020-12-03

MTRNordNot sure but could knox still do weird stuff even after no stock system left? as note 2 had pretty nasty knox problems with cyanogenmod at the start00:01
T42<elros34> don't know maybe @edp_17 knows something about it00:02
MTRNordas if I remember correctly it was some kind of thing running even before boot. (Samsung page itself says it is a hardware chip based full system encryption)00:05
MTRNordSo while it still does not start this time it did change the brightness twice. I guess thats good? ^^00:07
MTRNordoh yeah00:07
MTRNordnew logs00:07
T42<elros34> yeah00:07
MTRNordsystemd logs00:08
MTRNordseems like it actually did boot00:08
MTRNordbut failed to start the ui00:08
T42<elros34> if you use same kernel as for i9100 then you could try with EGL_PLATFORM=fbdev in droid-hal-device.conf. Also use -b0 switch now or disable persistent logging00:09
MTRNordyeah same kernel but not 100% same defconfig due to device specifics. But I guess that flag should still do its job00:10
MTRNordthats something changed on the rootfs right? (Just making sure to compile the correct parts)00:11
T42<elros34> change it on device: /var/lib/environment/compositor/00:11
MTRNordah ok00:11
T42<elros34> also remove :/dev/input/event0 which looks like wrong node00:12
MTRNordyeah thats most likely from the default example in the pdf as I didnt know what it would be in reality00:13
MTRNordafter that rebooting?00:13
T42<elros34> if you leave only evdevtouch then it should find correct node automatically00:14
T42<elros34> reboot or restart user@10000000:14
MTRNordah ok00:14
MTRNordI GOT A UI :D00:16
MTRNordno touh however00:16
UmeaboyShould I change $ANDROID_ROOT/.repo/local_manifests/$DEVICE.xml to $ANDROID_ROOT/.repo/local_manifests/beyond2lte.xml ?00:19
UmeaboyI know how it works in Lineage, but I want to make sure I don't make the wrong name.00:19
UmeaboyThe HADK says $DEVICE.xml, but I'm used to using the modelname.xml00:21
MTRNordtouch works too now :)00:22
T42<elros34> so your code name is not beyond2lte? what 'echo $DEVICE' prints?00:22
Umeaboyelros34: It is.00:23
malUmeaboy: $DEVICE means codename as mentioned somewhere early in the hadk pdf00:23
UmeaboyJust wanting to make sure I'm doing it correctly.00:23
maland that naming doesn't matter at all00:23
malI mean repo loads all xml files from that folder afaik00:23
UmeaboyI'm using hybris-16.0 branch instead and hope it goes OK.00:23
MTRNordwlan works too :3 oh thats sooo awesome :3 elros34 edp_17 BIG thanks for the help! Very big thanks :300:24
T42<elros34> @MTRNord I'm wondering about watchdog. Maybe your 5s timout set in bootparams is too small for dsme:
MTRNordwell thats something I will check after I had my first sailfish os experience ever :3 (Never used it before and as none of my old devices were supported I figured to just port one xD)00:34
T42<elros34> sure just an idea00:35
Umeaboymal: I can't find a device repo for beyond2lte. Should I make one out of the stock rom?00:35
UmeaboyThere is a device repo for Android 10, but not 9.00:36
MTRNordI will check that. doesnt harm to check obviously as I now got a stable system.00:36
UmeaboyThe ones I found that had a branch named android-9.0 said it was for recovery which I guess is to build TWRP.00:36
UmeaboySo I'm at a loss here.00:37
MTRNordok but my journey doesnt end. gps crashes the ui :)00:38
MTRNordwhat does a wild red and blue blinking led mean? :D00:39
UmeaboyMTRNord: It's Christmas. :)00:41
UmeaboySoon any way. :)00:41
UmeaboyNo harm meant.00:41
MTRNordhaha thats a good one ;P Someone who used sailfish for years told me most likely the UI just loopcrashed :)00:42
MTRNordmakes sense00:42
MTRNordoh nvm gps works. just switching it crashes the system. thats... funny00:43
malUmeaboy: you probably need to wait until hybris-17.1 is ready if you don't have suitable branch00:49
UmeaboyI'll check to see if I can find a branch that's named a bit different. You never know.00:50
MTRNordI am honestly impressed how well this works. camera, sound and gps(kinda) do work. Wlan works but looses the password on reboot. And that without any modifying00:53
T42<Michael %lastname%> Fwd from Michael Caine:
MTRNordfunny now that I am in the system usb stopped working/being detected as connected01:17
MTRNordalso no charger detection01:17
T42<elros34> you should check edp17 repos, he has some samsung devices and might contains fixes for you issues01:20
MTRNordyeah I based already stuff on it :)01:22
MTRNordok gps just tells me it would work but actually does not01:39
UmeaboyIs there a chance to get export LC_ALL=C to be used in the entire HADK?01:42
UmeaboyRight now I can't get my last name working for the git config --global command.01:42
UmeaboyIt's like when the locale is unset only english letters are accepted.01:43
MTRNordI am wondering => will that work in sailfish os too?
T42<elros34> edp17 yeah managed to get working s-pen on his device as mouse but few hacks are needed to get this working01:45
MTRNordah ok nice :D01:46
T42<elros34> then enable evdevmouse in droid-hal-device.conf, install mousetracker patch and fix sailfish-browser01:49
MTRNordI will check that out probably on saturday. But First going to work on fixing some of the basics.01:51
T42<ot_kurva> Hi! I have a trouble with calls. Xiaomi ido, los-14.1 (Android 7) port. In csd tool it's all good. All speakers and microphones are working. But when I'm calling I don't hear anything and the interlocutor doesnt hear me.04:16
T42<ot_kurva> audiosystem-passthrough-dummy-af was used04:26
T42<ot_kurva> SFOS v.
T42<elros34> anything i journal?04:34
T42<birdzhang> ido or mido?04:38
T42<ot_kurva> ido04:42
UmeaboyI've made an effort with starting a project called haddck (which is a shorter form of the name Haddock) that I've placed on gitlab.05:25
UmeaboyI just have to change it from Private to Public.05:53
UmeaboyIt should be Public now.05:57
UmeaboyTake Odin/Jodin/Heimdall/ and similar programs and cram the instructions from the HADK into a program called Haddock.05:59
UmeaboyThe idea is to use these solutions and merge them into a universal program to make it even easier to port to the current existing devices.06:00
UmeaboyI admit that this is a huge task, but rome wasn't built in 1 day.06:01
UmeaboyThe Heimdall program is pretty much dead anyway.06:01
UmeaboyLast merge for Heimdall was 2 years ago.06:02
UmeaboyI also made 3 seperate branches called Testing, Development and Stable so please use them accordingly.06:36
UmeaboyAnd please don't change the directory names for any of the OS's to keep the structure working.06:37
UmeaboyI'm off to bed.07:01
T42Těléаgrаm ♀ members Рrivаte and group Рromotio♀ %lastname% was added by: Těléаgrаm ♀ members Рrivаte and group Рromotio♀ %lastname%07:30
T42<edp_17> MTRNord, @elros34 : I don't know much about knox. For me it has never caused any issues. I am glad that the i9100 work helped. 😃 Regarding the S-Pen, based on Elros' work, I made the right click also work. I forgot to push this into github but now I just did. (Left click works in SFOS UI and many apps, the right click works in any des08:58
T42ktop Linux distro installed on a LXC container) The change is available here:
T42<edp_17> MTRNord: I just have double checked and realised that I have unset CONFIG_KNOX_KAP in my treltexx (Note 4) kernel config. I think this was when I tried to stop the KNOX message flood in the log. It didn't help though. What helped was commenting out knoxvpn_uidpid in kernel net/netfilter/xt_connmark.c09:35
T42<edp_17> These two commits (you can do in one if don't make the mistake I done 😜):
T42<edp_17> and09:39
T42simondvic was added by: simondvic10:18
T42<ankaos> hı. ı use this command10:24
T42<ankaos> but not see bluetooth10:24
T42<ankaos> ı send log 2 days later10:44
T42<elros34> did you follow first point in 10.3?10:47
T42<Rawlings %lastname%> Fwd from Rawlings J.:
T42<ankaos> elros: yes ı do14:04
T42<edp_17> @elros34 : Sorry, have not responded on your question regarding the hdmi. I've got distracted by the PinePhone and an SFOS app development so I'll come back to this hdmi thingy for the hammerhead later. Then, once started again, I will be able to give you some logs. Thanks your support so far and in advance! 😃14:19
T42<elros34> @ankaos  so did you have that driver already or you had to add it?14:19
T42<elros34> @edp_17 just try older libhybris and use a31 branch. I was able to fix it for photon q but can't rotate it.14:20
T42<ankaos> @elros34 [@ankaos  so did you have that driver already o …], add driver14:21
T42<elros34> did you confirm that it was compiled? zcat /proc/config.gz | grep -i BT_HCISMD14:22
T42<ankaos> sh-3.2# zcat /proc/config.gz | grep -i BT_HCISMD14:24
T42<ankaos> CONFIG_BT_HCISMD=m14:24
T42<ankaos> elros: send gruop output14:25
T42<elros34> so reboot, try to enable bluetooth and provide full journal14:27
T42<elros34> did you modprobe it before running Maybe set it be builtin instead14:28
T42<ankaos> sh-3.2# ls -la14:31
T42<ankaos> total 4414:31
T42<ankaos> drwxr-xr-x    2 root     root          4096 Dec  1 21:47 .14:31
T42<ankaos> drwxr-xr-x    3 root     root         16384 Dec  3 13:46 ..14:31
T42<ankaos> -rwxr-xr-x    1 root     root          3432 Nov 28 23:43 droid-hal-shutdown.sh14:31
T42<ankaos> -rw-r--r—    1 root     root           450 Nov 28 23:43 droid-hal-startup.sh14:31
T42<ankaos> -rw-r--r—    1 root     root          1176 Dec  1 23:34 droid-hcismd-up.sh14:31
T42<ankaos> -rwxr-xr-x    1 root     root          2724 Nov 28 23:43 droid-init-done.sh14:31
T42<ankaos> -rwxr-xr-x    1 root     root           814 Nov 28 23:43 droid-load-firmware.sh14:31
T42<ankaos> -rwxr-xr-x    1 root     root            63 Nov 28 23:43 get_partition.sh14:31
T42<ankaos> elros: this is problem?14:31
T42<ankaos> sh-3.2# chmod +777 droid-hcismd-up.sh14:33
T42<ankaos> chmod: invalid mode '+777'14:33
T42<edp_17> @elros34 [@edp_17 just try older libhybris and use a31 b …], Will try. Thanks!14:34
T42<ankaos> @ankaos [sh-3.2# chmod +777 droid-hcismd-up.sh14:38
T42<ankaos> chmod: …], @elros34 how use?14:38
T42<elros34> you want chmod a+x /path/to/file14:51
T42<ankaos> what do ı use command?15:08
T42<ankaos> sh-3.2# systemctl status bluetooth15:20
T42<ankaos> ● bluetooth.service - Bluetooth service15:20
T42<ankaos>    Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)15:20
T42<ankaos>    Active: inactive (dead)15:20
T42<ankaos>      Docs: man:bluetoothd(8)15:20
T42<elros34> first check whether droid-hcismd-up.service finished without error15:22
T42<ankaos> how?15:23
T42<ot_kurva> Xiaomi ido. Problem with voicecalls
T42<elros34> same as you check bluetooth.service15:25
T42<ankaos> @ot_kurva [Xiaomi ido. Problem with voicecalls https://pa …], please ubuntu paste15:25
T42<ankaos> ı dont open pastebin :(15:25
T42<elros34> looks similar to your issue: audiosystem-passthrough] Unknown code (21)15:27
T42<ot_kurva> I'm sorry
T42<ankaos> sh-3.2# systemctl status droid-hcismd-up.service15:27
T42<ankaos> ● droid-hcismd-up.service - Enable Bluetooth HCI over SMD15:27
T42<ankaos>    Loaded: loaded (/usr/lib/systemd/system/droid-hcismd-up.service; enabled; vendor preset: enabled)15:27
T42<ankaos>    Active: activating (start) since Thu 2020-12-03 17:52:26 +03; 34min ago15:27
T42<ankaos>  Main PID: 2520 (sh)15:27
T42<ankaos>    CGroup: /system.slice/droid-hcismd-up.service15:27
T42<ankaos>            ├─ 2520 /bin/sh /usr/bin/droid/droid-hcismd-up.sh15:27
T42<ankaos>            └─11829 sleep 115:27
T42<ankaos> Dec 03 18:25:40 mi_max2 rfkill[11595]: unblock set for all15:27
T42<ankaos> Dec 03 18:25:41 mi_max2 rfkill[11597]: unblock set for all15:27
T42<ankaos> Dec 03 18:25:42 mi_max2 rfkill[11599]: unblock set for all15:27
T42<ankaos> Dec 03 18:25:43 mi_max2 rfkill[11601]: unblock set for all15:27
T42<ankaos> Dec 03 18:25:45 mi_max2 rfkill[11605]: unblock set for all15:27
T42<ankaos> @ot_kurva [I'm sorry …], call sound problem?15:28
T42<ot_kurva> Yes15:28
T42<ankaos> @ot_kurva [Yes], edit /etc/sysconfig/pulseaudio15:28
T42<elros34> @ankaos did you follow advice and replace script with that one I gave you?15:28
T42<ankaos> add: AUDIOSYSTEM_PASSTHROUGH_IDX=1815:29
T42<ankaos> @elros34 [@ankaos did you follow advice and replace scri …], which?15:29
T42<ankaos> I added whatever is in the narration.15:29
T42<ankaos> @ot_kurva [Yes], read?15:30
T42<ot_kurva> @ankaos [read?], Yes. I'll try now. Thanks15:30
T42<elros34> and I told you few days ago that script from faq has infinity loop and you should change it. Not the first one, same was for your other device15:31
T42<ankaos> bluetoot second problem.15:31
T42<ankaos> not important for me. but required for headphones.15:32
T42<ankaos> @ot_kurva [Yes. I'll try now. Thanks], ?15:52
T42<ot_kurva> @ankaos [?], Yeah!!!! It works16:05
T42<ankaos> you bluetooth work?16:05
T42<edp_17> @elros34 : I use EGL_PLATFORM=fbdev on my i9100. Am I uderstand correctly that you said if I use the -b0 switch that will disable the logging? If so, how to use this switch exactly? Thanks.16:25
T42<elros34> what? you mix up something. -b0 is for journalctl and it wasn't for you16:46
T42<ot_kurva> @ankaos [you bluetooth work?], no17:34
T42<ot_kurva> im trying to fix with FAQ HADK. But there is error in droid-hcismd-up.sh17:36
T42<ot_kurva> hciconfig - command not found17:36
T42<ankaos> yeah ı problem this file17:50
T42<adampigg> (Photo, 1920x2560)
piggzrinigus: ^^22:16
Thaodanbtw could you maybe set some defaults/reuse icons in amazfish? For example IM apps like IRC could reuse the message icon.22:18
T42<edp_17> @elros34 [what? you mix up something. -b0 is for journal …], I know it wasn't for me. Just thought if I can reduce the logging that can help with the battery life an such. I thought the -b0 was a trick in droid-hal-device.conf.  Perhaps I was misreading the lines and understood how I wanted to rather than what it said. 😁22:23
T42<edp_17> Now, it is clear, thanks.22:23
T42<adampigg> @Thaodan [btw could you maybe set some defaults/reuse ic …], True, i already do some mapping...need some more for the new telegram apps too22:42
ThaodanThat would be great.22:47
ThaodanMaybe add communi too ;D22:47
T42<Magnus %lastname%> Fwd from Magnus John:

Generated by 2.17.1 by Marius Gedminas - find it at!