[Xiaomi Mi 5s Guides, News, & Discussion] rizahakam:
1. sGSI means semi GSI (Generic System Image, if I'm not wrong). when Google released Android 8.0 Oreo, Google incorporated Treble Project. this project basically separate system partition and vendor partition. this means OEM can update Android version without waiting vendor to update the code.

Google mandated that any phone launching with Android 8.0 Oreo must have Treble Project included. the requirement from Google is any phone with Treble Project must be able to boot AOSP when GSI is flashed.

our phone received Treble update from unofficial method by developers from this forum. therefore when our phone already updated to have Treble, you can flash any GSI and your phone will boot without you need to do anything. however this doesn't mean it won't have bug, it's just you can boot and using your phone almost for daily driver.

sGSI is created from Google Pixel system image, tweaked by developers so it can be flashed in any device. the problem is Google just released Android Pie yesterday, therefore the correct GSI not yet produced. that's why we have sGSI.

2. PR1 means Public Release 1. as this sGSI already produced since Android P Beta development, the previous release of sGSI is based on Android P Beta version. that's why when Google release Android Pie to Google Pixel devices, developers produce new sGSI based on full release on Google Pixel

3. due to this is sGSI, you need this three zip in order to make this sGSI boot in your device

4. you don't need to flash the provided kernel, however it's really recommended to flash this kernel as this kernel will make your phone become usable as daily driver.

also what you said CNFirmware actually isn't a kernel, it's a update to persists partition. you can flash both of this zip and won't have a problem

5. the magisk module is to make our phone more stable

6. yes it is stable enough to be used as daily driver

7. I don't know for OTA update, actually I also wondering the same things. maybe [MENTION=795625]JIGS[/MENTION]w4killer can answer for us

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

1. sGSI means semi GSI (Generic System Image, if I'm not wrong). when Google released Android 8.0 Oreo, Google incorporated Treble Project. this project basically separate system partition and vendor partition. this means OEM can update Android version without waiting vendor to update the code.

Google mandated that any phone launching with Android 8.0 Oreo must have Treble Project included. the requirement from Google is any phone with Treble Project must be able to boot AOSP when GSI is flashed.

our phone received Treble update from unofficial method by developers from this forum. therefore when our phone already updated to have Treble, you can flash any GSI and your phone will boot without you need to do anything. however this doesn't mean it won't have bug, it's just you can boot and using your phone almost for daily driver.

sGSI is created from Google Pixel system image, tweaked by developers so it can be flashed in any device. the problem is Google just released Android Pie yesterday, therefore the correct GSI not yet produced. that's why we have sGSI.

2. PR1 means Public Release 1. as this sGSI already produced since Android P Beta development, the previous release of sGSI is based on Android P Beta version. that's why when Google release Android Pie to Google Pixel devices, developers produce new sGSI based on full release on Google Pixel

3. due to this is sGSI, you need this three zip in order to make this sGSI boot in your device

4. you don't need to flash the provided kernel, however it's really recommended to flash this kernel as this kernel will make your phone become usable as daily driver.

also what you said CNFirmware actually isn't a kernel, it's a update to persists partition. you can flash both of this zip and won't have a problem

5. the magisk module is to make our phone more stable

6. yes it is stable enough to be used as daily driver

7. I don't know for OTA update, actually I also wondering the same things. maybe [MENTION=7325575]jigs4wkiller[/MENTION] can answer for us

---------- Post added at 02:08 PM ---------- Previous post was at 01:59 PM ----------

sorry for double post but to make sure that my question is seen. I don't know whether this one is bug or not, but when I'm using Bluetooth Earphone, when in call the sound didn't go through to Earphone, however if for media and music it's working normally.

do you also have problem like this [MENTION=7325575]jigs4wkiller[/MENTION]