| T42 | <smatkovi> so this file called arm-linux-androideabi-4.9/bin/arm-linux-androidkernel-gcc is a python script and it didn't work well with the os module so i wrote the line differently with the subprocess module. now it works but it wanted a real-arm-linux-androidkernel-gcc, i copied 4.9 and 7.x version of gcc there but now it says real-arm-linux-androidkernel-gcc: error: unrecognized command line option ‘-mshort-load-bytes’ | 00:58 |
|---|---|---|
| T42 | <smatkovi> i redownloaded prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9 and now it seems to be working | 01:42 |
| T42 | <smatkovi> #### build completed successfully (56:29 (mm:ss)) #### | 02:17 |
| T42 | <smatkovi> i checked the kernel and now i have to resolve the errors before i can use it as a mb2 build target? | 02:35 |
| T42 | <smatkovi> because it says it doesn't know this target. anyway i modified the kernel options and recompiling now | 03:01 |
| T42 | <smatkovi> this is the only error i cannot get rid of, although i specified it in the defconfig: ERROR: CONFIG_IKCONFIG_PROC is invalid | 03:17 |
| T42 | <smatkovi> and this: Fatal: 'samsung-j5xnlte-aarch64' is not a known build target | 03:19 |
| T42 | <smatkovi> i was successful with mb2 -t SailfishOS-latest-armv7hl | 10:07 |
| T42 | <elros34> but this target name will not work in build scripts, you must create correct build target, read again that part hadk pdf (Notice) | 10:22 |
| T42 | <smatkovi> what do you mean by (Notice)? | 10:29 |
| T42 | <smatkovi> good morning btw :) | 10:30 |
| T42 | <smatkovi> i used this command sdk-assistant create SailfishOS-latest-aarch64 Sailfish_OS-latest-Sailfish_SDK_Target-aarch64.tar.7z | 10:33 |
| T42 | <smatkovi> or do you mean something else? | 10:33 |
| T42 | <elros34> morning. Read again that chapter, it has big warning box about target name | 10:34 |
| T42 | <smatkovi> i thought it was to use somewhere else | 10:35 |
| T42 | <smatkovi> would you use aarch64 or armv7hl? | 10:36 |
| T42 | <smatkovi> i'm trying with aarch64 now and it at least goes without errors | 10:37 |
| T42 | <elros34> you can only use arm because like we alread figure out your device is arm. See kernel it's compiled with arm toolchain | 10:37 |
| T42 | <smatkovi> unfortunately it failed building the package, i have the feeling that this is because of the CONFIG_IKCONFIG_PROC error, but i don't know where to put it, i already put it at various places in the device defconfig | 11:13 |
| T42 | <smatkovi> this is the full log https://pastebin.com/tu8dKTuS | 11:13 |
| T42 | <smatkovi> and this is the defconfig https://pastebin.com/qifRLf6n | 11:24 |
| deathmist1 | @smatkovi always look in .config for the actual set of enabled config options, kernel config options have dependencies as in this case seen on https://cateee.net/lkddb/web-lkddb/IKCONFIG_PROC.html both CONFIG_IKCONFIG=y and CONFIG_PROC_FS=y should be set before you can enable that one | 11:29 |
| deathmist1 | typically you'd not edit defconfig files directly like you're doing but android builds kinda encourage this kind of crap because there isn't a simple way to bring up https://en.wikipedia.org/wiki/Menuconfig afaik | 11:30 |
| T42 | <smatkovi> oh thanks, that one i couldn't know | 11:31 |
| T42 | <TheVancedGamer> actually, you could just go into out/target/product/device name/obj/KERNEL_OBJ | 11:32 |
| T42 | <TheVancedGamer> and ru n menuconfig there | 11:32 |
| T42 | <smatkovi> it says command not found, but i won't bother about that, because i still can edit the file | 11:37 |
| T42 | <smatkovi> it complained about an unknown variable compiling the kernel, so i did make clean, now i have to wait 1h again. i will go to uni studying for the exam today, so i will continue working on that in the evening | 11:39 |
| T42 | <smatkovi> it was PATH_OVERRIDE_SOONG | 11:41 |
| T42 | <edp_17> I use this to manually check dependencies in kernel: https://cateee.net/lkddb/web-lkddb/ | 12:03 |
| T42 | <neochapay> Who can help me with start /sbin/droid-hal-init ? | 12:16 |
| T42 | <neochapay> ``` | 12:16 |
| T42 | <neochapay> Jun 27 00:52:50 T1100 sh[1399]: CANNOT LINK EXECUTABLE "/sbin/droid-hal-init": invalid ELF file "/system/lib64/bootstrap/libdl.so" load segment[4]: p_offset (0x3000) + p_filesz (0x0) ( = 0x3000) past end of file (0x28e0) | 12:16 |
| T42 | <neochapay> Jun 27 00:52:50 T1100 sh[1399]: linker: CANNOT LINK EXECUTABLE "/sbin/droid-hal-init": invalid ELF file "/system/lib64/bootstrap/libdl.so" load segment[4]: p_offset (0x3000) + p_filesz (0x0) ( = 0x3000) past end of file (0x28e0) | 12:16 |
| T42 | <neochapay> Jun 27 00:52:50 T1100 systemd[1]: droid-hal-init.service: Main process exited, code=exited, status=1/FAILURE | 12:16 |
| T42 | <neochapay> Jun 27 00:52:50 T1100 systemd[1]: droid-hal-init.service: Failed with result 'exit-code'. | 12:16 |
| T42 | <neochapay> Jun 27 00:52:50 T1100 systemd[1]: Failed to start droid-hal-init.``` | 12:16 |
| Mister_Magister | fast ball, do i build backports before or after kernel | 12:29 |
| T42 | <smatkovi> wow the kernel is built with this option now :) | 12:36 |
| T42 | <smatkovi> strange build_packages.sh exits with this error: cp: cannot stat './out/target/product/j5xnlte/system/apex/com.android.runtime.release/lib/bionic/libdl_android.so': No such file or directory | 12:40 |
| T42 | <Mister_Magister> sitting here debugging camera on victara because i'm bored and it's fun | 13:16 |
| T42 | <Mister_Magister> never thought i would say that | 13:16 |
| T42 | <elros34> actually it's not that hard to use menuconfig and even xconfig | 13:24 |
| T42 | <Mister_Magister> i really don't know why nobody here is using it | 13:30 |
| T42 | <Mister_Magister> make ARCH=arm menuconfig | 13:30 |
| T42 | <Mister_Magister> after you're done make mrproper | 13:31 |
| mal | @neochapay you are sure your android side /system and hybris-hal builds are the same version? | 13:31 |
| T42 | <elros34> little more than ARCH=arm: https://pastebin.com/vXgWvv2u | 13:34 |
| T42 | <Mister_Magister> no srsly you just need ARCH=arm (re @elros34: little more than ARC...) | 13:35 |
| T42 | <Mister_Magister> you don't need all that | 13:35 |
| T42 | <Mister_Magister> go to kernel directory and run make ARCH=arm or arm64 menuconfig and thats all | 13:36 |
| T42 | <elros34> and how it will know which defconfig file to use and where to put .config instead in kernel directory. Of course it's possible but that scripts handle everything | 13:37 |
| T42 | <neochapay> same (re @SailfishFreenodeIRCBridgeBot: <mal>@neochapay you ...) | 13:37 |
| T42 | <Mister_Magister> you tell it (re @elros34: and how it will know...) | 13:38 |
| T42 | <elros34> @neochapay don't you have some bootstrap/libdl.so built in out/? Maybe you need to use these instead | 13:53 |
| T42 | <elros34> btw did you remember to rebuild and install droid-config after fixing android_version_major? | 13:54 |
| T42 | <neochapay> ``` | 13:55 |
| T42 | <neochapay> * Building rpm/droid-hal-tb8788p1_64_bsp.spec | 13:55 |
| T42 | <neochapay> + echo '%dir /apex' | 13:55 |
| T42 | <neochapay> + art_path=./out/soong/.intermediates/art/build | 13:55 |
| T42 | <neochapay> + apex_path=apex/com.android.runtime.release/android_common_com.android.runtime.release/image.apex | 13:55 |
| T42 | <neochapay> + '[' '!' -f ./out/soong/.intermediates/art/build/apex/com.android.runtime.release/android_common_com.android.runtime.release/image.apex/lib/bionic/libc.so ']' | 13:55 |
| T42 | <neochapay> + art_path=./out/target/product/tb8788p1_64_bsp/system | 13:55 |
| T42 | <neochapay> + apex_path=apex/com.android.runtime.release | 13:55 |
| T42 | <neochapay> + '[' '!' -f ./out/target/product/tb8788p1_64_bsp/system/apex/com.android.runtime.release/lib/bionic/libc.so ']' | 13:55 |
| T42 | <neochapay> + art_path=./out/target/product/tb8788p1_64_bsp | 13:55 |
| T42 | <neochapay> + apex_path=apex/com.android.runtime | 13:55 |
| T42 | <neochapay> + rm -f /home/neochapay/work/f+/alps/installroot/usr/libexec/droid-hybris/system/lib/libdl.so /home/neochapay/work/f+/alps/installroot/usr/libexec/droid-hybris/system/lib/libdl_android.so /home/neochapay/work/f+/alps/installroot/usr/libexec/droid-hybris/system/lib/libc.so /home/neochapay/work/f+/alps/installroot/usr/libexec/droid-hybris/system/lib/libm.so | 13:55 |
| T42 | <neochapay> + cp -a ./out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libdl.so ./out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libdl_android.so ./out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libc.so ./out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libm.so /home/neochapay/work/f+/alps/installroot/usr/libexec/droid-hybris/system/lib | 13:55 |
| T42 | <neochapay> cp: cannot stat './out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libdl.so': No such file or directory | 13:55 |
| T42 | <neochapay> cp: cannot stat './out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libdl_android.so': No such file or directory | 13:55 |
| T42 | <neochapay> cp: cannot stat './out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libc.so': No such file or directory | 13:55 |
| T42 | <neochapay> cp: cannot stat './out/target/product/tb8788p1_64_bsp/apex/com.android.runtime/lib/bionic/libm.so': No such file or directory | 13:55 |
| T42 | <neochapay> error: Bad exit status from /var/tmp/rpm-tmp.JqZwJE (%install)``` | 13:55 |
| T42 | <neochapay> hmm | 13:55 |
| T42 | <elros34> did you strace droid-hal-init to see which libs it tries to load first? check droid-hal-device.inc, I think it was modified few times to handle correctlythat libc/m copying because different devices/bases use different place | 13:57 |
| T42 | <neochapay> https://pastebin.com/B6YJDZGg (re @elros34: did you strace droid...) | 14:06 |
| T42 | <elros34> hm, did you found some bootstrap directory in /out to compare that libdl.so with /system/*bootstrap one? | 14:14 |
| mal | @neochapay that looks like some issue with symlink targets being missing? | 14:34 |
| Mister_Magister | Yo, anyone here with hammerhead (not the fish kind) | 15:52 |
| T42 | <edp_17> I have a Nexus 5 ( hammerhead). How can I help? | 16:10 |
| T42 | <Mister_Magister> when you have camera on do you get messages like "msm_camera_cci_i2c_write_seq_table: number of bytes 16896 exceeding the max supported 256"? (re @edp_17: I have a Nexus 5 ( h...) | 16:20 |
| T42 | <edp_17> I'll check that and let you know. | 17:34 |
| T42 | <edp_17> Where? In journal, logcat or console? | 17:34 |
| T42 | <Mister_Magister> dmesg | 18:29 |
| Mister_Magister | hmmm… which code would talk to camera's ioctl | 20:34 |
| Mister_Magister | could be a blob | 20:52 |
| T42 | <edp_17> @Mister_Magister : When jolla-camera is on, the dmesg | grep msm_camera_cci_i2c returns with nothing on my hammerhead with sfos 4.4 | 20:54 |
| T42 | <Mister_Magister> okai thank | 20:54 |
| T42 | <edp_17> Np | 20:54 |
| T42 | <Mister_Magister> so maybe i'm not barking the wrong tree | 20:54 |
| T42 | <Mister_Magister> hammerhead is also using imx135 no? (re @edp_17: Np) | 20:54 |
| T42 | <edp_17> Idk. How can I check? | 20:55 |
| T42 | <Mister_Magister> got link to defconfig? | 20:56 |
| T42 | <edp_17> https://github.com/edp17/android_kernel_lge_hammerhead/blob/hybris-12.1-edp17/arch/arm/configs/cyanogenmod_hammerhead_defconfig | 20:58 |
| T42 | <edp_17> Imx135 is not set | 20:59 |
| Mister_Magister | ahh | 20:59 |
| Mister_Magister | internet lied to me then | 21:00 |
| T42 | <edp_17> What does that imx135 do? | 21:00 |
| Mister_Magister | it's camera | 21:00 |
| Mister_Magister | camera sensor/driver | 21:01 |
| T42 | <edp_17> I see. Camera works somehow else then. :) | 21:01 |
| mal | android usually does camera differently and doesn't use kernel drivers, of course depends on the device | 21:11 |
| T42 | <Mister_Magister> this one does (re @SailfishFreenodeIRCBridgeBot: <mal>android usually...) | 21:12 |
| T42 | <Mister_Magister> mm-qcamera-daemon calls ioctl on kernel's driver | 21:12 |
| T42 | <Mister_Magister> and i suppose other devices do the same | 21:12 |
| T42 | <Mister_Magister> hmm mm-qcamera-daemon comes from system :/ | 21:14 |
| T42 | <Mister_Magister> i just hit a dead end | 21:15 |
| T42 | <Mister_Magister> if it comes from android then the error must exist on android too | 21:15 |
| T42 | <Mister_Magister> so thats not the issue i guess | 21:16 |
| T42 | <Mister_Magister> QCamera2HWI: static void* qcamera::QCameraCbNotifier::cbNotifyRoutine(void*) : cb message type 32768 not enabled, this is coming from minimedia… | 21:50 |
| T42 | <Mister_Magister> bruhh outta ideas | 22:03 |
| T42 | <Mister_Magister> https://paste.opensuse.org/pastes/10e2729b1890 it really looks like it might be the problem | 22:07 |
| T42 | <Mister_Magister> i wonder who sets up/sends the callbacks | 22:08 |
| T42 | <Mister_Magister> seems that the callbacks end at 0x2000 and 0x1000/0x2000 is some qualcomm special callback, mine is 0x8000 so some motorola proprietary stuff? | 22:21 |
| T42 | <Mister_Magister> according to another enum 0x1000 is vendor start and 0x8000 is vendor end so i was close | 22:42 |
| T42 | <Mister_Magister> tho that doesn't give it any more sense | 22:47 |
| mal | what issue are you trying to fix? | 23:05 |
| Mister_Magister | camera recording xd | 23:05 |
| mal | so still pictures work? | 23:06 |
| Mister_Magister | yep | 23:06 |
| Mister_Magister | well… front camera doesn't work in piggz's camera but work in jolla's | 23:06 |
| mal | I remember some devices had issues what maximum reported resolution did not really work when recording videos | 23:08 |
| mal | like xperia x https://github.com/mer-hybris/droid-config-f5121/commit/cfea9265d9ca5509637c01b32c690fbdf9f17f9d | 23:08 |
| mal | maybe try something like that on your device? | 23:09 |
| Mister_Magister | i tried bumping down the res and it only slighty helps | 23:09 |
| mal | hmm | 23:09 |
| Mister_Magister | apparently this sensor can do only 15fps at 4k, but iirc stock android can do 4k | 23:09 |
| Mister_Magister | there's some issue with setting camera parameters but thats all blobs | 23:10 |
| mal | did you try that 1920x1080 resolution? | 23:10 |
| Mister_Magister | gimme a sec | 23:12 |
| Mister_Magister | oh i can't change resolution in settings anymore | 23:13 |
| mal | only very limited way | 23:13 |
| mal | like that max resolution for video | 23:13 |
| mal | for jolla-camera app | 23:13 |
| Mister_Magister | nah can just change aspect ratio | 23:14 |
| Mister_Magister | mal: same thing | 23:26 |
| Mister_Magister | https://paste.opensuse.org/pastes/756392b37041 thats all im gettin | 23:27 |
| mal | anything in logcat? | 23:27 |
| Mister_Magister | ye mostly what i described already xd | 23:28 |
| Mister_Magister | but imma get you log | 23:29 |
| Mister_Magister | https://paste.opensuse.org/b1ae69f38bb3 enjoy the book | 23:32 |
| Mister_Magister | i've noticed that it might be trying to do 4160x3120 while max res is 3840x2160 | 23:36 |
| Mister_Magister | but i might be reading it wrong | 23:37 |
| mal | hmm | 23:37 |
| Mister_Magister | yep decided i would sit on it today, learned bunch of stuff about kernel, how camera works | 23:42 |
| mal | yeah, it's a bit late now, need to check those more closely later this week | 23:43 |
| Mister_Magister | dw it's not new port | 23:43 |
| Mister_Magister | was jsut bored | 23:44 |
| Mister_Magister | mal: smol question does modules-droid-jb2q have profiles like modules-droid? | 23:45 |
| mal | hmm | 23:46 |
| Mister_Magister | like according to this readme https://github.com/mer-hybris/pulseaudio-modules-droid i can use pactl set-card-profile droid_card.primary voicecall to switch to voicecall mic | 23:46 |
| Mister_Magister | oh nvm jb2q has same readme | 23:47 |
| Mister_Magister | gotta figure out how to reliably switch mic/speaker to earpiece | 23:47 |
| Mister_Magister | imma also get logcat from newer android on same phone to see what is error and what is not | 23:49 |
| Mister_Magister | altho newer android is probably using differne camera api isnt it | 23:49 |
| Mister_Magister | now why the heck did vibrator stop working lol | 23:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!