When building custom images in Android 10 the dexpreopt.zip and the
associated odex and vdex files don't get created. This results in dex2oat
running on first boot for apks in the custom image partitions.
The dexpreopt.sh and dexpreopt.config get created in the right place.
--
--
You received
> but it's old and may only be available used.
"Old" is Android 8, Karim's can be considered as wisdom of the ancient in
fact xD, as it refers to AOSP 2.3.4.
But his courseware is more up-to-date, and dude is still quite active -
e.g. he did some great talk @
> Thanks for the information. But it would be great if you could suggest
any book regarding this.
Karim Yaghmour's "Embedded Android: Porting, Extending, and
Customizing" is *THE
book*, released in 2003 but still actual (I use it as a part of developer's
onboarding @ work anyway), couple other
The classic book
is
https://www.amazon.com/Embedded-Android-Porting-Extending-Customizing/dp/1449308295
but it's old and may only be available used.
On Tuesday, September 15, 2020 at 8:16:21 AM UTC-7, Igor Kukushkin wrote:
>
> Duh try narrowing the question down, way too much possibilities
Thanks for the information. But it would be great if you could suggest any
book regarding this.
On Tuesday, 15 September 2020 at 20:46:21 UTC+5:30 igo...@gmail.com wrote:
> Duh try narrowing the question down, way too much possibilities there.
>
> Try building the basic targets first
Duh try narrowing the question down, way too much possibilities there.
Try building the basic targets first (Cuttlefish, emulator image, generic
GSI, some Pixel/Nexus targets, Auto if curious). Then start looking into
how makefiles (.mk)/Bazel is working. Then try the same thing with any
custom
I am new to Android ROM Development before that i was an Android
Application Developer.
The link you have provided is for the setting up the environment in your
system which is already done on my side. My Question is from where could i
learn the things i need to know regarding ROM development.
Scratch that.
Actually seems like libhidltransport is no longer needed, libhidlbase, so
go this module Android.mk or Android.bp file and change the shared
libraries to include libhidlbase, and unlink with libhidltransport
On Mon, Sep 14, 2020 at 11:10 PM Gent Binaku wrote:
> Try to add this
Try to add this module to vendor partition
Please read this:
https://source.android.com/devices/architecture/vndk/build-system#module-definition
On Mon, Sep 14, 2020 at 6:37 PM Eduard K wrote:
> Hello,
>
> I am a little new on this topic developer. And start with Build an Image
> for a Sony
