Wednesday, 2023-05-24

T42<Fingus> @Elros Good Morning, i did write: boot.img    recovery.img  system.img  userdata.img  vendor.img04:47
T42<Fingus> and cache.img04:48
T42<elros34> I do not know much about but what about these binaries which you download from sony and flash?08:04
T42<elros34> point 7: oem partition08:09
T42<Fingus> @Elros: Doesn´t exists. Meanwhg08:11
T42<Fingus> @Elros: Meanwhile i go for the Lineage 18.1 Android11 dump (lineage-18.1-20230519-UNOFFICIAL-lilac) which is booting successfully, Hardwaretests are all successful done08:12
T42<Fingus> @Elros:08:12
T42<Fingus> 08:12
T42<Fingus> Working:08:12
T42<Fingus> 08:12
T42<Fingus> - Display/Touch08:12
T42<Fingus> - Fingerprint08:12
T42<Fingus> - Frontcamera, Backcamera, Fotomode, Videomode08:12
T42<Fingus> - SIM-Card/uSD-Card reconizion08:12
T42<Fingus> - WLAN Connection08:12
T42<Fingus> - BT-Connection08:13
T42<Fingus> - Mobile Data (
T42<Fingus> - Calling (no audio echo) (
T42<Fingus> - Light-Sensor08:13
T42<Fingus> - Nearing-Sensor08:13
T42<Fingus> - Earpiece Speaker08:13
T42<Fingus> - Main Speaker08:13
T42<Fingus> - Charging08:13
T42<Fingus> - Data-Cable08:13
T42<Fingus> - Vibration08:13
T42<Fingus> - Camera-Key08:13
T42<Fingus> 08:13
T42<Fingus> Did i miss something?08:13
T42<elros34> ok, at least you don't need to build whole android.08:16
T42<Fingus> @Elros: So i can start Porting?08:17
T42<elros34> I allow:)08:22
T42<elros34> if you have kernel and lineage sources then sure08:23
T42<Fingus> @Elros: And thats the mean part: i doesn´t have. It seems i made the classical beginner-faults.09:17
T42<b100dian> This one maybe?
piggzNote for future self ... usb-moded config to enable cable tracking12:02
piggzextcon_tracking      = 112:02
piggzmal: error 1 with camera was easy, unable to find
piggznext error is17:18
piggz05-24 19:16:51.163     0  7348 E DroidMediaCamera: Failed to connect to camera service17:18
piggz05-24 19:16:52.003     0  4376 W AudioParamParser-vnd: utilMkdir(), mkdir fail (/data/vendor/audiohal/audio_param/)17:18
piggz05-24 19:16:52.204     0  7348 W CameraBase: An error occurred while connecting to camera 0: Status(-8, EX_SERVICE_SPECIFIC): '1: validateClientPermissionsLocked:1425: Untrusted caller (calling PID 7348, UID 100000) trying to forward camera access to camera 0 for client droidmedia (PID 100000, UID -1)'17:18
T42<Papoucifle> Hello ! I have an error "minimediaservice.rc" not found ( when launching —gg . It used to work but I changed droid-hal-device and droid-hal-configs to older version to match the ones mentionned in hadk-hot.20:53
T42<Papoucifle> 20:53
T42<Papoucifle> I found the missing files in "./external/droidmedia/init/" and "./hybris/mw/droidmedia-localbuild/droidmedia-0.20220929.0/external/droidmedia/init/" and tried to copy them manually in the desired folder, but they get removed everytime I launch the script.20:53
T42<Papoucifle> 20:53
T42<Papoucifle> Any idea ?20:53
malwhich revision of dhd submodule do you have?20:54
T42<Papoucifle> Revision 960d6af856c1ccc082d6a078c402d5d04ce2791e20:55
malmaybe you could test the latest version of the submodule? I fixed some packaging issues recently20:56
T42<elros34> did you remove droidmedia from hybris/mw/ after changing revisions and actually build droidmedia not just package it?21:00
T42<Papoucifle> I did not...21:01
T42<Papoucifle> I removed it and now it works, thank you !21:02
T42<Papoucifle> BTW, thanks to your help the other day, I made my phone to boot the kernel, so I was able to connect through telnet. I had an error "Failed to start The lipstick UI.", so that's why I changed dhd and droidmedia revisions, hopping it would solve the problem21:05
T42<elros34> there was some simple commit in droid-config which could cause it but this can be checked on device easily21:08
T42<Papoucifle> How can I check that ? I reflashed my device but without any difference. I still have a whole lot of errors in journalctl21:19
T42<elros34> IIRC something about --hwc-restart in logs but I think you have more seriousy issues like lack of mounted partitions, search for "droid mount" in whole journal and read "Generating logs" section in hadk-hot21:22
T42<elros34> this "dev-block-platform-soc-7824900.sdhci-by\x2dname-system.device timout" looks like common fixup-mountpoint21:24
T42<elros34> mistake21:24
T42<Papoucifle> It doesn't appear in my fixup-mountpoints (that I left untouched because addison was already referenced in it)21:40
T42<Papoucifle> But it's actually the path of the "by-name" directory21:41
T42<Papoucifle> (I pasted this from a working lineage 18.1)21:41
T42<elros34> but that path is irrelevant, you need to check android's fstab, search in hadk-hot for fixup-mountpoints21:42
T42<elros34> then you will see the difference:
T42<elros34> old addision port used different android base and different fstab21:45
T42<Papoucifle> Ok I think I get it, I should have checked the other devices in the file. I misunderstood the purpose of this file. I'm going to try that tomorrow, thank you very much !21:54
T42<elros34> of course you can fix systemd mount units on device instead reflashing whole image21:55

Generated by 2.17.1 by Marius Gedminas - find it at!