Sunday, 2023-11-05

*** amccarthy is now known as Guest580101:06
*** amccarthy_ is now known as amccarthy01:06
T42<A_T_R> what is latest version number ?where to check about latest release number?03:49
T42<batmanofweb> Hello everyone,06:38
T42<batmanofweb> I'm porting saiflish of 4.5.0.18 to Google pixel 4a (sunfish) - lineage 18.106:39
T42<batmanofweb> I have compiled the kernel successfully and now onto the step of building droid-hal.06:39
T42<batmanofweb> I see in the HADK FAQ there is no entry for hybris 18.1. I have thought applied the appropriate patches from the hybris patcher's 18.1 branch.06:39
T42<batmanofweb> Even after all this my build keep failing for one reason or another. like it failed for not able to find init.zygote*.rc file.06:39
T42<batmanofweb> I feel like I am missing something.06:39
T42<batmanofweb> help would be appreciated06:39
T42<batmanofweb> thanks06:39
T42<elros34> @A_T_R in forum->announcements->Release thread06:39
T42<elros34> @batmanofweb here you have few hybris-18 entries:  https://sailfishos.wiki/books/hadk/page/hadk-hot. Did you finish make hybris-hal without errors?06:50
T42<batmanofweb> Thanks for  the reply, no I'm in the process of building droid-hal using the command  rpm/dhd/helpers/build_packages.sh --droid-hal06:51
T42<elros34> make hybris-hal is before droid-hal because droid-hal packages what hybris-hal builds06:52
T42<elros34> hybris-hal builds/copy kernel and android part of build like mentioned init*rc files06:54
T42<A_T_R> 4.5.0.24 is latest? (re @elros34: @A_T_R in forum->ann...)06:54
T42<elros34> yes06:55
T42<A_T_R> Thanks06:55
T42<batmanofweb> by  hybris-hal you mean hybris-boot.img and others? as I'm not able to find the term 'hybris-hal' in the HADK.06:56
T42<A_T_R> 4.5.0.24 also a stop release?06:57
T42<elros34> yeah all major releases are Stop Releases for quiet a time06:58
T42<batmanofweb> I'm following the instructions in HADK guide, and I'm at 7.2 Packaging droid-hal-device06:58
T42<elros34> What pdf version do you use? it must be there06:59
T42<batmanofweb> SailfishOS-HardwareAdaptationDevelopmentKit-4.5.0.19.pdf06:59
T42<elros34> chapter 5.407:00
T42<batmanofweb> oh I have done that07:00
T42<batmanofweb> I didn't know it was called hyrbis-hal07:00
T42<batmanofweb> make -j$(nproc --all) hybris-hal droidmedia - completed succesfully07:01
T42<batmanofweb> created the out directory - succesfully07:01
T42<batmanofweb> anyways, thanks for you help, Elros07:01
T42<elros34> without any error?07:02
T42<batmanofweb> much appreciated07:02
T42<batmanofweb> no errors, for now I got the init.zygote*.rc files from the device itself (re @elros34: without any error?)07:02
T42<batmanofweb> I got a new error after fixing some more error:07:37
T42<batmanofweb> 07:37
T42<batmanofweb>   Installed (but unpackaged) file(s) found:07:37
T42<batmanofweb>    /usr/lib/debug/boot/update-binary-0.0.6-202311050728.aarch64.debug07:37
T42<batmanofweb> and many more .debug files07:37
T42<batmanofweb> but these files do not exist and if I add them in straggler_files, then it says file not found error07:37
T42<batmanofweb> This is while building droid-hal07:37
T42<batmanofweb> https://pastebin.com/BhbzdH8R07:40
T42<elros34> doesnt looks like whole file. show $android_root/droid-hal-<device>.log07:50
T42<elros34> without adding any of these debug files to stragglers07:51
T42<batmanofweb> after adding them to stagger_files I'm getting file not found error07:54
T42<batmanofweb> https://pastebin.com/0tTpgRhg07:54
T42<batmanofweb> the files are there though07:54
T42<batmanofweb> If i go into the directory, then I can see the files there07:55
T42<batmanofweb> I found the problem, the file present in the direct is named "libz.so-0.0.6-202311050756.aarch64.debug" while the file not found error shows ""libz.so-0.0.6-202311050705.aarch64". This is happening for many files. the dates in the files are different08:00
T42<batmanofweb> not sure what to do though08:02
T42<batmanofweb> This is the full log droid-hal-sunfish.log, without the debug files in stragglers.08:09
T42<batmanofweb> 08:09
T42<batmanofweb> https://pastebin.com/aXX12rES08:09
T42<adampigg> whats the easiest way to "scale down" all UI components .... on the PT2, with the 1.0 scaling, and normal font sizes .. everything is a bit too large08:22
T42<elros34> 0.8 scale?08:37
T42<elros34> @batmanofweb for sure adding these debug files to stragglers is incorrect08:42
T42<batmanofweb> @elros34 thanks, but any suggestion to solve this?08:43
T42<elros34> not sure what is wrong. Did you build hybris-hal after applying hybris-patches, not before?08:44
T42<elros34> what version of droid-hal/confg submodules do you use?08:44
T42<elros34> did you build some debug version of android parts or something like that?08:46
T42<batmanofweb> i think I did build the hybris-hal after kernel patches, but I'll run the build command again just to be sure, thanks08:51
T42<elros34> how output of breakfast $DEVICE looks like08:54
T42<batmanofweb> https://pastebin.com/T4MtcYnG - output of droid-hal-sunfish.log after  building the hybris-hal again, its similar to old one09:07
T42<batmanofweb> output of breakfast $DEVICE09:09
T42<batmanofweb> https://pastebin.com/5q11vsGa09:09
T42<batmanofweb> for droid-hal/config, I'm using master branch09:10
T42<batmanofweb> I'm not sure, though, I believe it automatically pulled the master branch09:10
T42<batmanofweb> I did not build debug version of android parts09:11
T42<elros34> maybe try changing "build --no-check" to "build --no-check -d" here https://github.com/mer-hybris/droid-hal-device/blob/743edffbba56326e1a249dee6765eb1f9b19ae01/helpers/util.sh#L345. Definitely not a solution but I always build like that09:17
T42<elros34> you could add somewhere ad the top of droid-hal-device.inc: "%undefine _missing_build_ids_terminate_build" and see if that helps09:25
T42<elros34> hm you probably already have this so maybe: "%define debug_package %{nil}"09:32
T42<adampigg> so, leave icon-res as 1.0 and set theme_pixel_ratio to 0.8 yeah? will test (re @elros34: 0.8 scale?)09:33
T42<elros34> I used pixel_ratio 0.8 in droid-config spec but I do not remember what happened with icon but for sure it will use 1.0 icons set09:35
T42<elros34> There was a good patch for fine control of icons (rows) in luncher but not sure if this still works09:37
T42<A_T_R> i am upgrading sdk-target-toolings t o 4.5.0.24 but it showing 4.4.0.48  line 26 https://pastebin.ubuntu.com/p/N3PMr6spjv/10:32
T42<A_T_R> sdk-foreach-su -ly ssu re 4.5.0.2410:32
T42<A_T_R> sdk-foreach-su -ly zypper ref10:32
T42<A_T_R> sdk-foreach-su -ly zypper dup10:32
T42<A_T_R> i am upgrading sdk-target-toolings t o 4.5.0.24 but it showing 4.4.0.58  line 26 https://pastebin.ubuntu.com/p/N3PMr6spjv/10:32
T42<A_T_R> sdk-foreach-su -ly ssu re 4.5.0.2410:32
T42<A_T_R> sdk-foreach-su -ly zypper ref10:32
T42<A_T_R> sdk-foreach-su -ly zypper dup (edited)10:32
T42<elros34> isn't that a name of your tooling? sdk-assistant list10:35
T42<A_T_R> PlatformSDK atr@atr-G41D3C:~$ sdk-assistant list10:35
T42<A_T_R> SailfishOS-4.4.0.5810:35
T42<A_T_R> └─asus-x00td-aarch6410:35
T42<elros34> I am not aware of any way to change tooling/target name10:36
T42<A_T_R> but it should change while upgrading sdk targets  and toolings?10:37
T42<elros34> "it should" but no, it will not change10:38
T42<elros34> unless you install fresh target/tooling10:38
T42<elros34> so you need to check target release with "ssu re"10:39
T42<A_T_R> PlatformSDK atr@atr-G41D3C:~$ ssu re10:39
T42<A_T_R> WARNING: ssu.ini does not seem to be writable. Setting values might not work.10:39
T42<A_T_R> Device release is currently: 4.5.0.2410:39
T42<elros34> platform sdk is NOT target/tooling10:40
T42<elros34> you can use this "sdk-foreach-su -y ssu re"10:41
T42<A_T_R> https://pastebin.ubuntu.com/p/KrnvYwY3B9/10:42
T42<elros34> you don't need to show me this, its for your information so you know how to check it10:43
T42<A_T_R> Ok10:44
*** sskras_ is now known as sskras14:23

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