Android version and Libhybris
-
@poVoq In UT you can run
getpropwhich will dump many info regarding your device including the SDK version.
In Android you can use apps like Treble checker.Alternatively, use the
unpack_bootimg.pyscript from the porting notes. -
@ikoz I see. But those guides seem to indicate nowhere which SDK versions are working with Halium9.
My device seems to run on "SDK_INT:35" if I read the data correctly.
Edit: or Treble VNDK version 30
-
@poVoq The VNDK version is the one you are looking for (I confused SDK and VNDK previously but now edited the post). VNDK version 30 means android 11.
The porting notes are for Android 9+, they are mostly (excluding GKI) the same for even the latest version (currently 14). The script needs as input the
boot.imgof the partition, which includes the kernel. -
@ikoz Interesting. The device in question (FP5) never had Android 11, but rather was released with Android 13 and is currently on Android 15 here.
But ok, so I assume as long as this VNDK is on version 30 the UT installer should have no issue installing UT as ultimately that is what counts?
-
@poVoq That is correct, there shouldn't be any incompatible changes across updates that affect UT.
-
I think that I can plug my questions here, don't seem to be incompatible with the topic.
I have looked up treble on the internet, I have seen it on f-droid but not on google store, so it's not a standard android feature I understand ?
Also, what's up with vndk deprecation for Android 15 ? Has libhybris any chance of being updated to use the new-fangled apexes ? Maybe it's a question that should be asked on the Q&A - or maybe it has already been discussed ?
TIA
-
@gpatel-fr AFAIK It is usually called "Project Treble" which is what allows running GSI, see: https://developer.android.com/topic/generic-system-image/
-
Also, what's up with vndk deprecation for Android 15 ? Has libhybris any chance of being updated to use the new-fangled apexes ?
New devices use GKI (generic kernel image) which is part of the effort by Google to standarize the kernels used by devices. For us this means that the first boot will be harder to achieve, but it will be easier to get more phone hardware working due to the similarities. Halium 14 is already working to some extent so there shouldn't be any issue.
(Sorry for the late reply, couldn't respond when I first read it and forgot it later.)
-
from this link my understanding that to check the vndk version, it's necessary to enable debug mode on the phone, connect a computer through usb and use adb. It's easy once the phone is bought, I was hoping for something that could be done with any Android phone demoed in a shop before buying it :-).
-
@ikoz said in Android version and Libhybris:
New devices use GKI (generic kernel image) which is part of the effort by Google to standarize the kernels used by devices. For us this means that the first boot will be harder to achieve, but it will be easier to get more phone hardware working due to the similarities. Halium 14 is already working to some extent so there shouldn't be any issue.
Thanks, however there is still much to understand IMO - from
https://source.android.com/docs/core/architecture/vndk
Vndk deprecation happens in Android 15, not 14 - unless Halium 14 means Android 15 ? if yes, it's really confusing
-
Vndk deprecation happens in Android 15, not 14 - unless Halium 14 means Android 15 ?
I think the only thing UT has to do with VNDK is mount the correct partitions to be read by the android container, which handles the rest. Ask in the porting group for more detail, there are already some short discussions around it.
to check the vndk version, it's necessary to enable debug mode on the phone, connect a computer through usb and use adb
You can install an app called Treble Info from F-Droid.
