| T42 | <b100dian> I disconnected for the evening, will be looking into your advice now | 09:18 |
|---|---|---|
| T42 | <b100dian> I do have rndis.rndis under stock a14, let's see | 09:21 |
| rinigus | @b100dian: had to go back to stock to reply regarding android health issue. anyway, checked its recovery and you cannot access it as well with adb | 09:50 |
| rinigus | something you can when you are on aosp | 09:50 |
| T42 | <b100dian> Ah, should've asked what you needed about health on stock.. But good info | 09:51 |
| T42 | <b100dian> Seems I need to build r67 then :) | 09:51 |
| rinigus | @b100dian: or wait few days till they merge PRs | 09:54 |
| rinigus | and use aosp13 images you have already? | 09:54 |
| T42 | <b100dian> good idea | 09:58 |
| *** phlixi is now known as Guest8301 | 10:05 | |
| *** phlixi_ is now known as phlixi | 10:05 | |
| *** phlixi is now known as Guest8309 | 12:20 | |
| *** phlixi_ is now known as phlixi | 12:20 | |
| T42 | <b100dian> ok, got a first init.log saved to /data https://pastebin.ubuntu.com/p/bHYsVrdn74/ | 13:03 |
| T42 | <b100dian> sorry if the script is already changed a bit as here https://github.com/mer-hybris/hybris-boot/compare/master...sailfishos-sony-nagara:hybris-boot:master | 13:04 |
| T42 | <b100dian> I think the first thing is dmesg's last line "UDC core: couldn't find an available UDC or it's busy: -19" | 13:05 |
| T42 | <b100dian> and the fact that `echo "$G_USB_DEVICE" > $GADGET_DIR/g1/UDC` says "sh: write error: No such device" | 13:06 |
| rinigus | @b100dian: and the first success in copying stock lib to aosp14 blob - after copy of missing libcld80211.so, I have wifi and bt. except can't test them as aosp keyboard is crashing! | 13:12 |
| rinigus | great to see the first logs from your boot! | 13:12 |
| T42 | <b100dian> Good. Keyboard.. Maybe you can connect an external one..:)? | 13:14 |
| T42 | <b100dian> the kernel changes are temporarily here https://github.com/b100dian/android_kernel_sony_msm | 13:15 |
| T42 | <b100dian> rinigus: is this a good name for the repo to create it under nagara org? (repo name inspired from mer-hybris). Or suggestion for branch name | 13:16 |
| rinigus | @b100dian: looks good! I had the same in tama https://github.com/sailfishos-sony-tama/android_kernel_sony_msm | 13:18 |
| rinigus | for branch, as the names are really hard to remember, I used hybris-10.0-4.14 . we can maybe use hybris-14.0-5.15 | 13:18 |
| T42 | <b100dian> Good, will do that soon | 13:19 |
| rinigus | I had also special links in hadk to automatically compare with jolla's and sony's kernels. that was very handy | 13:19 |
| rinigus | see https://github.com/sailfishos-sony-tama/main/blob/hybris-10/hadk-sony-xz2.md#kernel-or-hybris-hal-update | 13:20 |
| rinigus | we willa make those as well when we get to writing up hadk :) | 13:20 |
| mal | @b100dian do you have that udc hardcoded in init script now? seems it's wrong one | 13:21 |
| T42 | <b100dian> you have a different one? | 13:22 |
| T42 | <b100dian> hang on, I am removing the hardcoding, it wouldn't be the first time self inflicted errors crop up :) | 13:22 |
| T42 | <b100dian> I've written a bit how I cycle from hybris-boot to aosp recovery here https://github.com/sailfishos-sony-nagara/main/wiki/Hybris%E2%80%90boot-without-full-SFOS-SDK | 13:33 |
| T42 | <b100dian> clearly that `ls /sys/class/udc/` doesn't return anything now on hybris-boot so we need to search more android .rc scripts for what is enabling stuff. Hopefully not some module ;) | 13:39 |
| T42 | <b100dian> Actually, we could mount vendor_boot I guess..? Anyway, I'll be AFK a while | 13:40 |
| rinigus | @b100dian: reading the doc - nice! so you have to flash boot every time... pity that we cannot just boot it directly without flashing | 13:41 |
| T42 | <b100dian> that, and the fact that a recovery partition is not used anymore.. | 13:44 |
| mal | @b100dian wait, what kind of kernel is that? | 14:09 |
| mal | unpack the vendor_boot.img and check what the init ramdisk there contains | 14:09 |
| T42 | <b100dian> I think it is from AOSP r55 checkout, from the folder kernel/sony/msm-5.15 | 14:10 |
| T42 | <b100dian> And another /kernel subfolder of that | 14:11 |
| T42 | <elros34> have you check what it's in /sys/bus/platform/devices/a600000*? | 15:35 |
| T42 | <elros34> I am thinking about your previous /sys/bus/platform/devices/a600000.ssusb/mode | 15:39 |
| T42 | <b100dian> Interesting, at least in android recovery, /sys/class/soc/a600000.dwc3 -> ../../devices/platform/soc/a600000.ssusb/a600000.dwc3/udc/a600000.dwc3 | 17:30 |
| T42 | <b100dian> gonna set that mode next, and looking into vendor_boot disk | 17:31 |
| mal | maybe just dump some ls -lR stuff from device to data/sdcard to see what stuff you have | 17:32 |
| T42 | <b100dian> yes, gonna add those too | 17:34 |
| T42 | <b100dian> vendor_ramdisk00 has avb/ with a couple of pubkeys, a first_stage_ramdisk with a fstab in it and a system with /bin/toybox + links and lib64 with a dozen of libs | 17:35 |
| T42 | <b100dian> This is from AOSP14. Anything specific I should look into? It doesn't have modules, and the Aosp build doesn't produce vendor_dlkm.img | 17:35 |
| mal | if it doesn't contain modules then it doesn't matter to us | 17:38 |
| T42 | <b100dian> Ok. I've echoed mode to .ssusb and I get exactly three new kernel dmesg outputs more than before | 17:48 |
| T42 | <b100dian> [ 5.618277] dwc3 a600000.dwc3: Adding to iommu group 49 | 17:48 |
| T42 | <b100dian> [ 5.644548] sps_register_bam_device: sps:BAM 0x000000000a704000 is registered | 17:48 |
| T42 | <b100dian> [ 5.644720] msm-dwc3 a600000.ssusb: dwc3 msm iommu fault handler registered | 17:48 |
| T42 | <b100dian> This is looking promising, but the /sys/class/udc folder is still empty | 17:49 |
| T42 | <b100dian> I should go back to echoing the hardcoded value to /config/usb_gadget/g1/UDC :D | 17:50 |
| T42 | <b100dian> nope, same "UDC core: couldn't find an available UDC or it's busy: -19" as before, time for some more rc grepping + kernel.. | 18:18 |
| rinigus | @b100dian: I couldn't figure out what's with keyboard, opened an issue. BT on testing is rather moody (was able to connect but the disconnected immediately). wifi couldn't test. lots of errors in logcat regarding many services | 19:10 |
| rinigus | so, not the best state. far from it. I'll be afk for tonight | 19:10 |
| T42 | <elros34> @b100dian you still have these "dwc3_gadget_* return -2"? | 19:14 |
| T42 | <b100dian> yes | 19:36 |
| T42 | <b100dian> good spotting | 19:36 |
| T42 | <b100dian> this is the last init log https://paste.ubuntu.com/p/9BHny3VCc3/ | 19:40 |
| T42 | <b100dian> and this is dmesg from recovery https://pastebin.ubuntu.com/p/nQTVFG5nvS/ | 19:40 |
| T42 | <b100dian> which also has some -2 rets | 19:40 |
| mal | @b100dian are you sure your hardcoded stuff are ok? I see both a600000.ssusb and a600000.dwc3 in that log | 19:48 |
| T42 | <b100dian> yes, there is a message above that shows that the /sys/class/udc file is a link to /sys/devices/platform/soc/a600000.ssusb/a600000.dwc3/udc/a600000.dwc3 | 19:50 |
| T42 | <b100dian> so, the mode setting of peripheral happens in a600000.ssusb/mode | 19:50 |
| T42 | <b100dian> which I found in recovery default.prop to be `ro.boot.usb.dwc3=a600000.ssusb` and also used for mode setting to periperal | 19:51 |
| T42 | <b100dian> while `sys.usb.controller=a600000.dwc3` from that same prop is used for e.g. echoing it into UDC | 19:51 |
| T42 | <elros34> this is interesting: processing init.recovery.pdx224.rc and then dwc3 exited from low poer mode | 19:59 |
| T42 | <elros34> power mode* | 19:59 |
| T42 | <b100dian> yes, the file on ro.boot.usb.dwc3 just sets mode = peripheral on that ssusb thing. I have that line output on dmesg in my last init.log too | 20:07 |
| mal | could you try removing that rndis.usb0, not sure why but on fp5 I had replaced it with rndis.rndis | 20:10 |
| T42 | <b100dian> sure, let me remove that | 20:23 |
| T42 | <elros34> isn't <usb0/rndis0> just name which can be anything? | 20:26 |
| mal | not sure | 20:33 |
| mal | I thought the driver sets that | 20:34 |
| T42 | <b100dian> no change, but I have an idea, i'm gonna add some sleep :) there's the UDC error _before_ the peripheral set messages, should be the other way around :D | 20:40 |
| T42 | <b100dian> progress, different error! https://pastebin.ubuntu.com/p/QDqtsgKmmt/ :P | 20:59 |
| T42 | <b100dian> that was a stupid typo of mine that was skipping "ln -s" part | 21:39 |
| T42 | <b100dian> rinigus: got telnet ;) | 21:40 |
| T42 | <Mister_Magister> what u portin | 21:46 |
| T42 | <Mister_Magister> hopefully not another asoos xd | 21:46 |
| T42 | <b100dian> this time its a Sony. Mine's 5 IV | 21:50 |
| T42 | <Mister_Magister> my condolences | 21:50 |
| T42 | <b100dian> do you have an alarm on "got telnet" :)? | 21:50 |
| T42 | <b100dian> Because I would set one, good idea | 21:51 |
| T42 | <Mister_Magister> nah i've seen activity for a while now | 21:51 |
| T42 | <Mister_Magister> if you type in here you're on the top of my chat list so hard not to notice | 21:51 |
| T42 | <b100dian> Yes but this happened before :)) https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2023-03-27.txt#line8 | 21:51 |
| T42 | <Mister_Magister> well | 21:52 |
| T42 | <Mister_Magister> coincidence | 21:52 |
| T42 | <b100dian> no worries, I am also the one asking which device when people progress | 21:52 |
| T42 | <b100dian> rinigus: pusing unclean now, will clean-up and retest tommorrow | 21:56 |
| T42 | <b100dian> *pushing | 21:57 |
| T42 | <b100dian> mal and @elros34 thanks again for the handy advice! | 21:57 |
| mal | so what was the solution? | 22:05 |
| T42 | <b100dian> A sleep between setting mode peripheral and starting using the configs | 22:19 |
| T42 | <b100dian> Last log was broken because I have accidentally edited another line so symlinks weren't running | 22:20 |
| T42 | <bruuuh121> guyd | 22:25 |
| T42 | <bruuuh121> i have prb | 22:25 |
| T42 | <bruuuh121> when i want to install apps from file browser cant install but in notification msg is install sucssefuly | 22:26 |
| T42 | <bruuuh121> https://irc.thaodan.de/.imgstore/05a7ecd3/file_6692.jpg | 22:27 |
| T42 | <bruuuh121> that what i z | 22:27 |
| T42 | <bruuuh121> see | 22:27 |
| T42 | <b100dian> @bruuuh121 maybe you want to join the Sailfish OS Fan Club telegram channel for the question? | 22:29 |
| T42 | <bruuuh121> nvm | 22:35 |
| T42 | <bruuuh121> i have solve prb | 22:35 |
| mal | @bruuuh121 what was the reason? | 23:11 |
| T42 | <bruuuh121> i install armv7 not aarch 64 | 23:18 |
| mal | ah | 23:18 |
| mal | still that seems like a bug if it claimed the installation worked | 23:18 |
| T42 | <bruuuh121> that what i think | 23:19 |
| mal | I will report that internally at jolla tomorrow | 23:20 |
| T42 | <bruuuh121> k | 23:20 |
| T42 | <bruuuh121> phone is ginkgo | 23:20 |
| mal | should not matter which device, unless we can't reproduce that on other devices, we'll see once we test that on other devices | 23:20 |
| T42 | <bruuuh121> how i can get android app support | 23:21 |
| mal | official app support is not available for community ports but there is possibility to use waydroid on those, others can help with that because I have no experience with that | 23:51 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
