Hey - it's super cool to see a video like this. I've subscribed, and I hope you really do like HIDL->AIDL :) Some small notes here: AIDL is not necessarily more stable than HIDL, but due to the versioning scheme, it's easier to write stable code. Stability ultimately relies on a combination of the runtime APIs and how the application uses them. Both AIDL and HIDL are fully stable if used properly, but AIDL is easier to work with. Additionally, one major reason for AIDL is simply that the binaries are smaller. HIDL was a bit bloated. Though, ultimately, the most important benefits come from having a single IPC language: improvements are felt everywhere, and code is maximally portable. Thanks again for the video.
Amazing series! If possible, can you create a few videos explaining the Input Framework. How the input propagates from the drivers to the framework to ultimately being dispatched to the user etc. Thank you.
Lets say we moved from HIDL to AIDL for a vendor binary. Can a user app also would be able to communicate with vendor binary using AIDL. Earlier only systems apps was only able to talk to vendor using HIDL.
Yes user app can also communicate using AIDL. This is the major reason for this change. All the communication from App layer to hardware layer can follow same AIDL common mechanism
![TEEDEE TADA - DIAMOND NARAKORN X LEGO LYKN [Special Dance Performance]](http://i.ytimg.com/vi/QgtZedFeumA/mqdefault.jpg)
Hey - it's super cool to see a video like this. I've subscribed, and I hope you really do like HIDL->AIDL :) Some small notes here: AIDL is not necessarily more stable than HIDL, but due to the versioning scheme, it's easier to write stable code. Stability ultimately relies on a combination of the runtime APIs and how the application uses them. Both AIDL and HIDL are fully stable if used properly, but AIDL is easier to work with. Additionally, one major reason for AIDL is simply that the binaries are smaller. HIDL was a bit bloated. Though, ultimately, the most important benefits come from having a single IPC language: improvements are felt everywhere, and code is maximally portable. Thanks again for the video.
Thanks a lot Steven
Do we have to add the AIDLs in the three of the folders..?
Amazing series! If possible, can you create a few videos explaining the Input Framework. How the input propagates from the drivers to the framework to ultimately being dispatched to the user etc. Thank you.
Hi Moon, Thank you . Please find th-cam.com/video/EusxdlcyJF8/w-d-xo.html
Hi,
Can you please explain about stable AIDL
Lets say we moved from HIDL to AIDL for a vendor binary. Can a user app also would be able to communicate with vendor binary using AIDL. Earlier only systems apps was only able to talk to vendor using HIDL.
Yes user app can also communicate using AIDL. This is the major reason for this change. All the communication from App layer to hardware layer can follow same AIDL common mechanism
Hi mam, how to store custom system application string data into settings.global table. Thanks in advance.
Hi , you have to use adb command to put data in settings table: here is an example of wifi : adb shell settings put global wifi_on 0
Thanks Dimple
Waiting for upcoming details video.
Sure 👍