Hi Dimple, really a good explanation video, only one thing is missed, in video till 16:15, hardware folder is not there in Your UA-camDimple folder, but at 18:23, hardware folder we can see, how it generated or added here, can you please explain this. Thank You
At 15:17 in default Android.bp we need to change cc_library_shared to cc_binary and also need to change service name from -impl to -service in default Android.bp if we want to make it binderized hal... Also, don't we need service.cpp in default folder and rc file ? In device specific folder we need to add that binderized service name in PRODUCT_PACKAGES of target.mk file.. Also we need to take care of adding selinux permissions if we run it in enforce mode..
Hi Dev thank you for ur inputs.. yes we need to add service.cpp and RC file if we want to use binderized approach .. and yeah I did not cover abt selinux in this video ...
Hi Dimple, First of all a big Thanks to you for covering up this topic, I have few quarries. 1 I can see the hardware folder along with default, what it contains? 2 Which hardware (driver) you are targeting to read, write and where exactly we are doing that? 3 What about sepolicie? 4 I know its tough to gather all the information in one place, could you please share any link or documents for Android 10 or latest version if you have, it will be very helpful?
Hi Dimple, Thank you so much, can you please tell us how HIDL further communicates with System service? I heard, will have to do HAL customization in vendor folder, can you please tell me why all processes happen in hardware/interface folder? Thankyou!
Hi , all the hardware and it's customizations are maintained in these two folders hardware and vendor .. it's a standard followed by Google so evrything is at one place and not scattered around .. Hidl uses calls and connects to aidl wch. In turn talks to system services
If I am not wrong I see there is one current.txt file in my aosp repo which contains hash key value of a project so that it will prevent any accidentally change in any repo. Once you have made any changes in any hal file you have to update the new generated has key in the current.txt file.
Yes Sushil you are correct you need to update the current.txt after changes in your Hidl implementation. You can you hidl-gen command to generate the hash i guess.
Hi Dimple, really a good explanation video, only one thing is missed, in video till 16:15, hardware folder is not there in Your UA-camDimple folder, but at 18:23, hardware folder we can see, how it generated or added here, can you please explain this.
Thank You
Big wala thanksss, it really helped.
Better if you can provide the client application using this hidl.
East or West, Dimple Framework is the best👌
Hi Dimple, good explanation on custom HIDL.Great job
Hi,
I dont have words to say thanks to you, to make this sooo simple
Thank you soo much
Your welcome 🤗
At 15:17 in default Android.bp we need to change cc_library_shared to cc_binary and also need to change service name from -impl to -service in default Android.bp if we want to make it binderized hal...
Also, don't we need service.cpp in default folder and rc file ?
In device specific folder we need to add that binderized service name in PRODUCT_PACKAGES of target.mk file..
Also we need to take care of adding selinux permissions if we run it in enforce mode..
Hi Dev thank you for ur inputs.. yes we need to add service.cpp and RC file if we want to use binderized approach .. and yeah I did not cover abt selinux in this video ...
Thanks for showing the difference
Hi Dimple,
First of all a big Thanks to you for covering up this topic, I have few quarries.
1 I can see the hardware folder along with default, what it contains?
2 Which hardware (driver) you are targeting to read, write and where exactly we are doing that?
3 What about sepolicie?
4 I know its tough to gather all the information in one place, could you please share any link or documents for Android 10 or latest version if you have, it will be very helpful?
Hi, Hardware folder im not aware of it, need to check . Currently since this is demo, i have not targeted any hardware. , I followed Opersys by Karim
Hi Dimple, Thank you so much, can you please tell us how HIDL further communicates with System service? I heard, will have to do HAL customization in vendor folder, can you please tell me why all processes happen in hardware/interface folder?
Thankyou!
Hi , all the hardware and it's customizations are maintained in these two folders hardware and vendor .. it's a standard followed by Google so evrything is at one place and not scattered around .. Hidl uses calls and connects to aidl wch. In turn talks to system services
Nice job! I have always wondered how that works
Thank you! Cheers!
Good , It helps a lot, God bless you with success.
Glad it helped. Thank you
If I am not wrong I see there is one current.txt file in my aosp repo which contains hash key value of a project so that it will prevent any accidentally change in any repo. Once you have made any changes in any hal file you have to update the new generated has key in the current.txt file.
Thanks Sushil, i was not aware of this
Yes Sushil you are correct you need to update the current.txt after changes in your Hidl implementation. You can you hidl-gen command to generate the hash i guess.
Good Work Dimple.
Thank you
Hello!!
Can you please upload a video on Android S Migrations & How to create my own Android HAL AOSP Architecture
Will try
which terminal or tool are you using to run these commands
Mobaxterm if you are working on windows... In Linux machines u can use normal terminal
U can also use putty
Can I use oracle virtual box to run linux machine in windows
Hii dimple you didn't show how you have genrated hardware folder in UA-camDimple/2.0 .
Manually
New .hal will not work from android 12.
Only new .aidl can be added.
Yes
Yes you are correct as I know version is not required for devices having OS less than 11.
I think that is enforced from android 13.
@@bluesman3612 it's from Android 12