**** BEGIN LOGGING AT Thu Jul 26 03:00:01 2018 Jul 26 06:38:48 Morning! Jul 26 06:39:00 elvispre: well I didn't put any SIM yet :) Jul 26 07:26:57 Tofe: I'm not sure where the build.prop comes from? Jul 26 07:27:48 There's a system.prop in the device repo Jul 26 07:35:20 Herrie|Laptop: I'll try to compare with mido or rosy, which should be quite similar Jul 26 07:35:43 Tofe: This tissot-dev stuff was really messy for CM 14.1 Jul 26 07:35:49 Needed to add quite some things to get it working Jul 26 07:35:55 That normally is OK in CM14.1 Jul 26 07:36:11 So I'm really not surprised it's missing things Jul 26 07:36:22 Though "funny" Halium succeeded Jul 26 07:42:47 yes, it's quite weird Jul 26 07:42:57 and no ramdisk image is weird too Jul 26 07:45:49 It could be something is just missing from a makefile here or there Jul 26 08:02:20 I don't any striking difference regarding system.prop treatment Jul 26 08:03:19 system.prop is used to generate build.prop right/ Jul 26 08:03:20 ? Jul 26 08:03:22 Or....? Jul 26 08:09:39 I think so **** BEGIN LOGGING AT Thu Jul 26 08:30:46 2018 Jul 26 11:11:29 build.prop is a generated file in the onyx (halium) build. Jul 26 11:34:02 ok, so we'll have to figure out why it isn't created by "mka systemimage" on tissot Jul 26 13:30:58 Tofe: This has some info on build.prop generation: http://manoftoday.wikidot.com/android-build Jul 26 13:31:41 "android build/core/Makefile defines INSTALLED_BUILD_PROP_TARGET, which is generated by:" and "bash $(BUILDINFO_SH) >> $@ <---- re-direct the output into build.prop file" Jul 26 13:35:44 Herrie|Laptop: so it should work, but doesn't Jul 26 13:37:50 https://github.com/Herrie82/android_device_xiaomi_tissot/blob/cm-14.1/BoardConfig.mk#L172 does define it correctly Jul 26 14:10:24 Tofe: Yes... This whole Android build stuff always puzzles me Jul 26 14:17:22 In the end it's just a big Makefile... very, very big... Jul 26 16:05:58 Herrie: to switch device for Halium, I made myself a little script: https://bpaste.net/show/7689b2a97759 Jul 26 16:52:18 Herrie: in the build's output I get system/boot/android-ramdisk.img and system/build.prop, but I can't find these in the final image Jul 26 17:19:27 Tofe: Well that makes things a bit easier to debug I guess Jul 26 17:19:49 There should be something in a makefile I guess to pack it in the image Jul 26 17:20:25 something like that, but I'd have thought it to be generic Jul 26 17:21:02 Tofe: I think each device has something in the root .mk files for this Jul 26 17:21:11 Not 100% sure Jul 26 17:21:31 Like I said this is a bit of a franken CM from tissot-dev Jul 26 17:21:36 I'll try to understand how it works :p Jul 26 17:21:48 So things are not like we'd normal have with proper CM Jul 26 17:32:00 ah wait, no it's there... just it's in /system, not in / Jul 26 17:36:09 ok, everything ends up in a /system subfolder Jul 26 17:49:03 ok so the system image, or at least what we'd like to use, lies now entirely in the /system subfolder of system.img Jul 26 17:49:13 maybe it's cause by the A/B partitioning? Jul 26 17:58:59 Herrie: it seems related to https://github.com/Herrie82/android_device_xiaomi_tissot/blob/cm-14.1/BoardConfig.mk#L42 Jul 26 17:59:10 When I comment it out, the image is back to "normal" Jul 26 18:00:47 so I guess there are two ways around it: either change BoardConfig, or change Halium's initrd script Jul 26 20:44:06 I have unlocked my A1 now and had a poke around inside it "as is". Jul 26 20:46:10 I'll get myself a (another) micro SD card - hopefully tomorrow - so I can keep backups somewhere handy and safe before starting to flash new things. Jul 26 20:55:41 elvispre: you can also begin downloading a stock rom, like the 7.1 one (first one here: https://forum.xda-developers.com/showpost.php?p=75711835&postcount=2 ) Jul 26 20:56:18 It'll be handy if nothing else works Jul 26 20:56:41 I used it twice to restore my userdata partition Jul 26 20:57:29 Tofe: Wasn't there a PR pending for Halium to deal with a/b? Jul 26 20:57:33 I remember I saw it Jul 26 20:57:37 I don't think it got merged yet Jul 26 20:58:02 Tofe: Thank you. That looks like the equivalent of what I had to use to recover my onyx (without having to scour the Internet to find it). Jul 26 21:00:38 Herrie: there is; but I'm not sure it deals with the system.img being organized differently Jul 26 21:11:42 Tofe: Have you run "adb diable-verity" at all? (I am just discovering what dm-0 / dm-1 are all about.) Jul 26 21:11:59 s/diable/disable **** ENDING LOGGING AT Fri Jul 27 03:00:01 2018