Hi I'm a newbie into android custom rom development. I'd like to know more about it and utilize a Notion Ink Adam as my test device. I want to port the latest version of android (maybe ubuntu or win 8 would also do) I just want to see that the Notion Ink Adam 1 works as a usable device and all peripherial devices work as well eg. Camera and the pixel Qi Screen etc. However I do not know where to start. I went through a youtube video which talks about android internals .. So far I have collected the below queries.
1) Why is it that installing android on devices is not the same as installing a regular operating system on a machine.?
2) Is my device really a paper weight if it gets hard bricked. It cannot be recovered Period ?
3) Since the Notion Ink Adam is based on a Tegra 2 process, would it be correct to assume that if a cyagenmod android os works on another device with a similar processor by some other company it will work on the Adam. Thanks.
Hello there,
I am looking for a Android TV box with vanilla stock android. Are there any available and for sale? I tried searching everywhere but could not find any. The reason I am looking for one is, because I am looking for a development machine and deployment machine for apps. The machine will have to work with different hardware (USB) and I will have to recompile the kernel and need to modify HID drivers anytime.
Most distributions on AMlogic devices make use of custom kernels and some modifications are just plain bad and half done, not to mention the half rooted quirkiness on some devices with modified rom versions.
So is there an TV Box like device available with clean vanilla android out of the box? I really hope someone could help me with my search.
Thanks in advance and really appreciate this community.
Hello everybody. I love this community and I have been lurking for a long time.
I have noticed on a foreign language forum that some people were offering a custom rom for my android 9 TV box.
The chinese box is based on a s905x3 CPU and has a mediatek wifi chip for which it is hard (if not impossible to find the wifi drivers).
The site claims that the image was made by modifying the stock rom that came with the box. Is this possible or do all custom roms need to be build from the source?
The custom rom I want to make is going to replace the launcher with kodi.
I am prepared to build the whole rom from source but I do have a couple of questions.
Since the mediatek wifi drivers cannot be found how would I go about including the binary for the wifi?
I have noticed that the box that I have uses a .ko (kernel object) module to drive the wifi chip.
Can I include these kernel objects in build? It is a shame that the kernel is built as a 32bit system. Would that mean that I can only compile a 32bit kernel if I were to reuse those kernel modules and binaries?
Another idea is to perhaps use the kernel from coreelec in my build since it seems to include a lot of drivers.
Is it possible to use a kernel from something like coreelec but use the source from AOSP for the rest of my build?
Is there anything else that I should be aware of?
Thank you all!!!!
Can anyone give me any hints to any of the questions?
Essentially I want to swap out the stock launcher for Kodi. What is the easiest way to do so?
I do realize that Virtualbox has Android x86 VM compatibility.
What do experts and intermediates use to learn and test andorid custom roms & features?
I mean for a beginner, making mistakes on their regular device could lead to fatal consequences, constant reflashing and being unable to use stock rom for general purposes.
Should a novice aiming to learn how to create custom roms and features use their own device, despite the consequences or is there a better approach to this?
Additionally, in case virtualization is recommended, what software should be used to resemble a real device as much as possible (especially firm specific phones like Oneplus)
VirtualBox - and all emulators based on it, yes almost all wellknown emulators are based on it - is x86 / x86_64 specific, the Android images run on it have to be compiled as x86 / x86_64 ports. Emulators designed to be run on x86 / x86_64 computers aren't meant to be used as a tool for creating / testing an Android ROM, IMHO.
Virtualization ( read: Hardware Assisted Virtualization - HAV ) is a x86 / x86_64 CPU specific feature ( what you enable / disable in computer's BIOS ) - it simply allows different OS to be run simultaneously on computer: No real ARM-CPU based Android device has this feature. That's why you don't have to worry about it when developing an Android ROM.
jwoegerbauer said:
VirtualBox - and all emulators based on it, yes almost all wellknown emulators are based on it - is x86 / x86_64 specific, the Android images run on it have to be compiled as x86 / x86_64 ports. Emulators designed to be run on x86 / x86_64 computers aren't meant to be used as a tool for creating / testing an Android ROM, IMHO.
Virtualization ( read: Hardware Assisted Virtualization - HAV ) is a x86 / x86_64 CPU specific feature ( what you enable / disable in computer's BIOS ) - it simply allows different OS to be run simultaneously on computer: No real ARM-CPU based Android device has this feature. That's why you don't have to worry about it when developing an Android ROM.
Click to expand...
Click to collapse
You're right, ARM is the right cpu arch.
I dont understand your last sentences, Why does HAV matter in terms of developing android ARM roms?
Also if I am developing for arm(v8) devices, yet virtualize x86_64 on my pc to test my first custom rom, how does that port well? It shouldnt work right?
Now it is up to me who does not understand what role HAV should play in the development of a custom ROM for Android. It's an x86 / x86_64 emulator which makes use of this feature, if ever.
Look inside here to get an idea what HAV is, how it works.
Hello to everyone.
I would like to understand how to emulate a recent version of Android on my jetson nano with qemu / kvm. I already have some experience with linux,with the jetson nano and with the arm64 platform,but a very little one with Android. But I have already asked some crucial informations about the most important requisites that Android should have to run with qemu-kvm. Basically these :
An Android image with Mesa DRM/KMS support.
Android kernel with the appropriate Virtio-gpu modules enabled.
Modified Jetson nano kernel to add support for KVM
compiled Virgilrender and qemu with virgilrender support
I have already configured point 3 and 4. Point 1 and 2 are missing 'cause I have a little Android knowledge. Someone said to me "It needs to be one targeted for Qemu with virtio-gpu support enabled. There are images around with it configured but don’t have ones that I can share". Ok. for me its better to understand how to configure Android from the beginning like it should be,but I'm pragmatic,so I don't say no if someone wants to give me a recent Android image already configured . In any case,since I don't know where to start,I would like to get some detailed documentation from you,because I want to learn the workflow. Thanks in advance.
no one wants to help here ?