**** BEGIN LOGGING AT Thu Feb 13 02:59:57 2020
Feb 13 11:02:20 <rasva> dTal: zip file with linux also contains rooted android image
Feb 13 11:02:54 <dTal> awesome
Feb 13 11:03:00 <rasva> and as written above, the only dif boot image, rest is same as stock android
Feb 13 11:03:47 <rasva> *the only difference is
Feb 13 11:17:59 <TauPan> I'm wondering if the rooted image contains the backup of the non-rooted boot in the correct location this time, so rooting can be reversed temporarily to receive OTA updates.
Feb 13 11:27:10 <rasva> OTA is about partition layout mainly, so if you modify this you will not be able to receive OTA
Feb 13 12:44:05 <TauPan> Really? Ok, that was a misconception I had then. I know that OTA also fails when boot.img was modified and the OTA contains a binary patch for the image. I didn't think it failed because of partition layout as well.
Feb 13 12:52:09 <rasva> well, it will most likely fail as well, but main obstacle is partition layout
Feb 13 12:52:32 <rasva> it expects layout which does not exist
Feb 13 12:55:55 <dTal> I feel like the exact conditions under which screwing around with the OS will brick the phone / render it unable to update is kind of vital info
Feb 13 12:59:41 <TauPan> There's another reason the boot image backup should be on the device: Otherwise Magisk is not able to update itself.
Feb 13 13:00:20 <TauPan> Well, actually I'm not sure that's the reason the update fails on my Gemini.
Feb 13 13:00:30 <TauPan> (But it's a plausible candidate.)
Feb 13 13:03:39 <dTal> any early thoughts on Debian?
Feb 13 13:04:51 <dTal> Someone on the OESF forum says "calls, SMS, bluetooth and mobile data don't work at present."
Feb 13 14:45:28 <TauPan> (I think that someone might have been mifritscher ;) ...)
Feb 13 15:34:46 <mifritscher> the root android kernel is stored in another partition than the "normal" android kernel - so I expect no problems here.
**** ENDING LOGGING AT Fri Feb 14 02:59:59 2020