More devices - LineageOS Questions & Answers

How often will it be that newer devices are added to the compatability list i guess for lineage OS?

Related

Will we get Android O on the x86 ZF2s?

Just that, what are the odds?
An official version. I doubt it. But a LinOS version is possible.
Since Intel dropped x86 support for mobile devices, I don't think Android O would have support on a x86 devices, that includes our Zenfone 2.
However, I might be very wrong.
@SleepingAran I have x86 Android O build on my Android Studio, so we would have something like Lineage OS but i don't think ASUS build official release for ZF2 (there is no Nougat to ZF2 so...)
I'm assuming custom ROM here since we didn't even get official nougat and the idiots at asus are already planning the ZF4 so they don't care about supporting the ZF2 and soon neither will they care about the ZF3
The question is if the current maintainers for the ZF2 will even bother to continue support when Lineage 15 (android O) comes out
Didn't they drop support before nougat? and yet we got it
No way asus will get O on the ZF2, in fact I don't think the ZF3 will get it either
No. They dropped after Nougat.
---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------
Running on an emulator is very different from running natively.
Yes they dropped before nougat. The only N we have is LinOS
Asus have announced that ZF3 and ZF4 series will get O by next year.

8.1 and 9.0 vendor

I have a ques.
How are 8.1 vendor files different from 9.0 vendor files? I mean vendor partition should suppose to have hardware related files from the vendor( like bluetooth, audio etc) , so they should be same irrespective of the android version, coz hardware is same, i suppose.
And if they are different, then whats the use of this whole treble thing when you still need an updated vendor partition from your manufacturer and you are stuck with old android version only. Sorry if I am missing something.
i am not sure if this is correct but i believe 8.x treble was sort of beta test and any phone launching with android 9.0 has proper treble support
Any how the vendor partition does need to be updated the better suite the newer OS, but not necessary, what android is trying to achieve is have the same kind of upgrade-ability as a windows computer, you can update from win 7 to win 10, all drives may or may not work and if the fail there are basic driver implementation in place
if there is a decent support from OEMs they can update their vendor partitions(or open-source them)for 5 years or more if they want to while developer communities or hopefully google themselves in the future can release android version globally somewhat usable.
this will greatly help ex-flagships last longer, budget phones unlike budget laptops will still die out as they dont feature removable ram and storage.

Question [A52s] possibility to install GSIs (like the 13 dev beta)?

Hey guys, I noticed that G released the GSIs for the dev preview/beta of 13. Would it be possible to install this on an A52s 5G?
Arobase40 said:
This is for Pixel phone !
Then are you a developer ???
Click to expand...
Click to collapse
The whole idea of treble and GSIs is to have an easier way to push updates of android to multiple devices while having to rely less on manufacturers and their cooked rom (General System Image, serperated from all the manufacturer drivers/bloatware/android flavours which ideally should be in /vendor/)
And yes I am a dev of sorts, albeit inactive/without project right now

General GSI thread - April 12, 2023 UPB1.230309.014 available for the Pixel 6 Pro [Raven]- Android 14 GSI binaries and release notes

GSIs​
April 12, 2023:
Generic System Image releases | Platform | Android Developers
developer.android.com
Android 14 GSIs (Preview)​
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zipfebd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380fARM64aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95ax86_64+GMSgsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76x86_64aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zipd25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8
Known issues with Android 14 GSIs​Android 14 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Spoiler: Old News/Releases
March 15, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 15, 2023
Build: T3B1.230224.005
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B1.230224.005-9723149-85eb7259.zip85eb725917e4b05e7e66c0898e94fd78e5f4ce1b530d09b10627e67c2c4bf190ARM64aosp_arm64-exp-T3B1.230224.005-9723149-6f182cba.zip6f182cbad4fc1c9c92e01538346c16771da641caa7499efc92b5b9b2d02f00c0x86_64+GMSgsi_gms_x86_64-exp-T3B1.230224.005-9723149-1773dc5c.zip1773dc5c80bee4b127e9fd491a7215dfebeedea9f2de7e5ff4b00b6b38791d2ex86_64aosp_x86_64-exp-T3B1.230224.005-9723149-78e6bc0f.zip78e6bc0f94b8fd33c77701948098b3732af6618f24ddf68f379ac4945e7d3549
February 1, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​bookmark_border
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR2 as well as discover and report OS and framework issues until Android 13 QPR2 is officially released.
GSI binaries for Android 13 QPR2 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: February 1, 2023
Build: T2B3.230109.002
Build type: experimental
Security patch level: January 2023
Google Play Services: 22.46.17
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T2B3.230109.002-9523436-539488e0.zip539488e0638b879b9212567d57049c8178d173f8d0b90ce627fbb763ddbc1fd6ARM64aosp_arm64-exp-T2B3.230109.002-9523436-98a648ca.zip98a648ca2edb2ac1719998eab31e0de4901ab6ef974ab91257f3e25f36c2317ax86_64+GMSgsi_gms_x86_64-exp-T2B3.230109.002-9523436-cd37ecd0.zipcd37ecd060add9d1d5aca20fcea7af5ad9776dbd81a464933efa3d4d9e3b4525x86_64aosp_x86_64-exp-T2B3.230109.002-9523436-22691864.zip22691864640bcfa2b215c6548df45e37ba49a8898923d412ca5d29471a6a0313
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Click to expand...
Click to collapse
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Click to expand...
Click to collapse
Downloads​
Date: September 8, 2022
Build: T1B1.220819.006
Build type: experimental
Security patch level: September 2022
Google Play Services: 22.28.13
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T1B1.220819.006-9012527-0b3ddd9e.zip0b3ddd9e315af1a320aa129081c8b715820b3f67e6dbfd5c895814046f5a16a9ARM64aosp_arm64-exp-T1B1.220819.006-9012527-bb83c478.zipbb83c47865fe5bf336d33df6a259a213e375eb8734ef2284cb624e122d27a63cx86_64+GMSgsi_gms_x86_64-exp-T1B1.220819.006-9012527-3899de5e.zip3899de5eb11187401df67ac26e4f622df61cd8138b5dd2aad131b37fe8c85d60x86_64aosp_x86_64-exp-T1B1.220819.006-9012527-3a7b91f3.zip3a7b91f34a71e61f536c911074f8f65e045e6846c9e94d1bef9f7ad51054aad1
Click to expand...
Click to collapse
Post #3.
Post #4.
Post #5
Post #6
@roirraW "edor" ehT Thank you for finding this! Something like this kind of release tends to supercharge things, so this was a very nice present to see today!
GSIs
February 1, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​bookmark_border
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR2 as well as discover and report OS and framework issues until Android 13 QPR2 is officially released.
GSI binaries for Android 13 QPR2 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: February 1, 2023
Build: T2B3.230109.002
Build type: experimental
Security patch level: January 2023
Google Play Services: 22.46.17
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T2B3.230109.002-9523436-539488e0.zip539488e0638b879b9212567d57049c8178d173f8d0b90ce627fbb763ddbc1fd6ARM64aosp_arm64-exp-T2B3.230109.002-9523436-98a648ca.zip98a648ca2edb2ac1719998eab31e0de4901ab6ef974ab91257f3e25f36c2317ax86_64+GMSgsi_gms_x86_64-exp-T2B3.230109.002-9523436-cd37ecd0.zipcd37ecd060add9d1d5aca20fcea7af5ad9776dbd81a464933efa3d4d9e3b4525x86_64aosp_x86_64-exp-T2B3.230109.002-9523436-22691864.zip22691864640bcfa2b215c6548df45e37ba49a8898923d412ca5d29471a6a0313
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 15, 2023
Build: T3B1.230224.005
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B1.230224.005-9723149-85eb7259.zip85eb725917e4b05e7e66c0898e94fd78e5f4ce1b530d09b10627e67c2c4bf190ARM64aosp_arm64-exp-T3B1.230224.005-9723149-6f182cba.zip6f182cbad4fc1c9c92e01538346c16771da641caa7499efc92b5b9b2d02f00c0x86_64+GMSgsi_gms_x86_64-exp-T3B1.230224.005-9723149-1773dc5c.zip1773dc5c80bee4b127e9fd491a7215dfebeedea9f2de7e5ff4b00b6b38791d2ex86_64aosp_x86_64-exp-T3B1.230224.005-9723149-78e6bc0f.zip78e6bc0f94b8fd33c77701948098b3732af6618f24ddf68f379ac4945e7d3549
March 29, 2023:
Android 13 GSI binaries and release notes | Android Developers
Notes and downloads for Generic System Images for Android 13 QPR beta builds.
developer.android.com
Android 13 GSI binaries and release notes​bookmark_border
Android Generic System Image (GSI) binaries are available to developers for app testing and validation purposes on supported Treble-compliant devices. Developers can use these images to address any compatibility issues with Android 13 QPR3 as well as discover and report OS and framework issues until Android 13 QPR3 is officially released.
GSI binaries for Android 13 QPR3 are built from the same AOSP and GMS sources as the corresponding Google Pixel builds. These binaries contain the same API and SDK, have a similar CTS result, and have been validated on the following Pixel devices:
Pixel 4a and 4a (5G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a
Pixel 7 and 7 Pro
See the GSI documentation for device requirements, flashing instructions, and more information on choosing the right image type for your device. To find GSI binaries for already-released, stable versions of the platform, see the Generic System Image releases page.
Note: File GSI bugs for any system-related issues you encounter. Make sure to attach a full bug report and clearly indicate that you are using a GSI buildin your bug description to help us find your issues and address them more quickly. For app-related issues found when using a GSI, we recommend reproducing the issue on a Pixel device before contacting the app developer directly.
General advisories​GSI binaries offer core OS and framework functionality that is common to all Android 13 QPR beta builds, but they might be missing specific functionality as listed and are not intended for commercial use.
Please be aware of the following general advisories:
GSI binaries are an experimental tool intended only for use by developers who want early access to test and validate their apps. They are not intended for general use.
Using a GSI might void the warranty for your device, erase all data on your device, and might brick your device.
Using a GSI requires a bootloader-unlocked, Treble-compliant device that originally launched with Android 9 (API level 28) or higher.
Apps embedded in GSIs are for evaluation usage; some apps might not function as expected.
GSI releases aren't Compatibility Test Suite (CTS)‑approved. Apps that depend on CTS-approved builds might not work normally.
Known issues​Android 13 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.
Downloads​
Date: March 29, 2023
Build: T3B2.230316.003
Build type: experimental
Security patch level: March 2023
Google Play Services: 23.02.14
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-T3B2.230316.003-9794841-bf9fb488.zipbf9fb488bcdabcb4dbf4cf381ddd28858af96ab50ad6c53298c55cbe25835dbbARM64aosp_arm64-exp-T3B2.230316.003-9794841-5c9b2ecf.zip5c9b2ecf5dea44680b442ead3a14f97b7ddb5d3893bfc7e018ce701bb3736168x86_64+GMSgsi_gms_x86_64-exp-T3B2.230316.003-9794841-77ebefd1.zip77ebefd182f985bfb0e85359eba2b088f480f9a149a21ac20ef338f53f44ef63x86_64aosp_x86_64-exp-T3B2.230316.003-9794841-5d809315.zip5d809315ebf1015733cdcb93aad058f1d130be48e9dbcb0cc8bb1c6b9456b116
Hello. How can I fix this problem?
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Alligator-r said:
Hello. How can I fix this problem?
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Click to expand...
Click to collapse
I honestly don't know if there's anything that can be done to fix that issue, since it's a known issue. The only most likely sure fix I can think of is to use the Stable firmware instead of the GSI, but I'm guessing that's not the solution you're looking for. You might be able to get away with dirty flashing the Stable firmware - removing the -w, so it doesn't wipe your data, although if you still have issues on dirty-flashed Stable firmware, I'd do a factory reset.
Generic System Image releases | Platform | Android Developers
developer.android.com
Android 14 GSIs (Preview)​
Date: April 12, 2023
Build: UPB1.230309.014
Build type: experimental
Security patch level: April 2023
Google Play Services: 23.09.12
TypeDownload LinkSHA-256 ChecksumARM64+GMSgsi_gms_arm64-exp-UPB1.230309.014-9890577-febd421e.zipfebd421e2fa182fa7a3e30ff64417f0da342b825535fc0eef90028679f72380fARM64aosp_arm64-exp-UPB1.230309.014-9890577-2c116021.zip2c11602154a507b8bd50d0e8a0e3b631ef24e1af70e1bc5e6932700f649cf95ax86_64+GMSgsi_gms_x86_64-exp-UPB1.230309.014-9890577-0aef912d.zip0aef912d0bbab412fe4bc6d7fc9408579197af936ee84d17be10eb1117edae76x86_64aosp_x86_64-exp-UPB1.230309.014-9890577-d25c18bc.zipd25c18bc77d5ff6eea176c399fc6411c66d20a5a796cb691929c1012298e82e8
Known issues with Android 14 GSIs​Android 14 GSI binaries have the following GSI-specific known issues:
Phone Audio: When using the integrated dialer, you might not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
Power Cycle: Rebooting GSI might fail on some devices. To work around it, reboot the device into recovery mode, erase user data, perform a factory reset, and then reboot the device.
System partition size: GSI + GMS file size (images named _gsi\_gms\_arm64-*_) might be bigger than the default dynamic system partition size on your device. To work around this issue, you can delete some non-essential dynamic partitions, such as the product partition, and flash the GSI again. For more information, see the flashing GSIs documentation.

Question Is it possible to enable pKVM support for the Poco F3 manually using root, or does it require custom kernels to be made by ROM developers?

The title pretty much, the pixel 6 and 7 support pKVM, which allows us to boot Windows 11 ARM or ARM64 Linux images in a virtual machine.
I saw somewhere that it either requires root to enable, or it must be enabled when the kernel is compiled, is it possible for this to work on the F3?
Interesting question.
I think we won't get pKVM-support, unless someone gets GKIs (Generic Kernel Images) working on Alioth (or perhaps more accurately, on the Snapdragon 870 sm8250).
Our device's 4.19 Kernel is too old, and doesn't have Rust-support, which I think is needed to run the crosvm VM Manager. It's part of Android 13's Virtualisation-Module, under the package-name "com.android.virt"
The Pixel 6 and 7 are running a much newer kernel, and it's GKI.
I don't know about pKVM-Support of other GKI devices. There could be more requirements for pKVM-support (besides arm64, GKI-based Kernel and Android 13).
Here are some articles I checked out:
How the Android 13 Virtualization module uses pKVM to boot virtual machines
Android virtual machines are changing in Android 13, here is everything you need to know about VMs in the newest version.
blog.esper.io
How to run a Linux VM on Android 13
Android 13 adds a virtualization feature. Here's how to use it to run Linux in a VM.
blog.esper.io
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
Getting started with Protected Virtual Machines
https://twitter.com/i/web/status/1492754683445669893

Categories

Resources