Database Info

[HELP] Porting Treble to a Relatively Old Device

Before I start, here's what I have and what I don't have:
What I have:
BLU R1 PLUS
BLU R1 PLUS Kernel Source
A possible port device (An Intex Infie 3, to use the vendor from)
Experience with the linux command line
What I DO NOT have:
A kernel source for the Intex Infie 3
Now for the explaination:
I found several ARM64 devices and vendors, however the kernel source for my device is ARMv7 (even though the SoC is ARMv8).
I soon learnt that trying to build an ARM64 kernel would be a waste of time, so I decided to go searching for the needle in a haystack (which of course was another device, with android Oreo and an ARM kernel+vendor) I eventually found this Intex Infie device which I noticed did not have any arm64-related prop lines and ONLY had the zygote32 in boot.img
However I then discovered that even if the vendor would work, Marshmallow drivers in the stock kernel for the BLU R1 Plus will cause issues to boot any GSI because of the many changes between android versions AND I need "Binderised HALs"
I intend to use my cache partition as the vendor partition (which of course, I'll have to add early mount to the DTB in the kernel for)
I struggle with kernel editing and compiling as this is my first shot at developing for an unknown or unpopular device.
What I'm asking for:
I'm not asking for it to be done for me, but rather a hand that can point me in the right direction that would at least allow me to boot a GSI.​

How to port libs to Android x86

Hi! Take a look at this situation: I have an Android x86 tablet (model Multilaser M7i Nb190) Intel, Android 4.4, but the internal emmc memory i'snt working anymore, but the rest of the device still 'works', Generic Android x86 boot up, even Ubuntu n' ZorinOS Lite, but I can go after setup screen because there's no touchscreen support for my device, I have the original rom, but the structure of the device rom and of the Android x86.iso seems to be different. How to port the device drivers (libs) to the Android x86 generic.iso rom? I have version of Android x86 4.4, its better to use it because it is the same version of the device rom (in general)? Thanks for any help. ... And why xda app still giving network error after trying to upload an image?!

I'm just curious I don't know much about phones in general, just a question

Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?

andreas_xs said:
Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
Click to expand...
Click to collapse
Installing custom roms and custom recovery maybe complicated at first but once u get the hang of it it wouldn't be as complicated anymore

As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up ).

Simple question: Does a custom kernel need to compatible with the ROM or the phone?

Just want to know, when selecting a custom kernel, do I have to check if the custom ROM supports the kernel or if the phone model supports the kernel or if I have to check for both.
I dont know if this is a dumb question or not..but pls help..am noob

A phone's kernel - what is the go between of phone's ROM and phone's hardware - is a Linux port, a phone's ROM is Android OS customized by manufacturer.
The kernel provides the basic drivers what are used to communicate to phone's hardware. The ROM is basically an interpreter between the Android ( user ) and the kernel.
So the ROM must match kernel.

jwoegerbauer said:
A phone's kernel - what is the go between of phone's ROM and phone's hardware - is a Linux port, a phone's ROM is Android OS customized by manufacturer.
The kernel provides the basic drivers what are used to communicate to phone's hardware. The ROM is basically an interpreter between the Android ( user ) and the kernel.
So the ROM must match kernel.
Click to expand...
Click to collapse
Thanks alot!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Flashing a custom Android on a no-name tablet / phablet

Hi,
I just bought a cheap no-name phablet (tablet with SIM card slot) on eBay (used, I want to use it for my doorbell system). It has an Android 8.1.0 on it and the settings say it's a model "K4", serial number
Code:
0123456789ABCDEF
(which perplexed me a bit in the first place), the boot screen says "MediaTek" which I found out seems to be the CPU's manufacturer. Build number is
Code:
O11019 test-keys
and kernel version is
Code:
3.18.79
. The ebay article said the tablet manufacturer was Padgene which I couldn't find any information about (except for this Amazon article).
Now I somehow fear (for the serial number alone) that this is some kind of weird Chinese Android ROM no one knows what it really does in background. And so, I want to flash a custom ROM on the tablet.
Now my questions:
1. How is it possible to find out the real hardware manufacturer to find out which Android ROM I would need?
2. Are there even custom Android ROMs out there for those Chinese no-name tablets at all?
3. How do I flash it, should I use TWRP for it or choose a different way?
Thanks in advance, taiBsu

Not the manufacturer is of any interest, but device's hardware.
For MTK devices a tool called Mediatek Auto TWRP Porter exists:
Mediatek Auto TWRP porter v1.7; TWRP v3.4, Android 10 support - Hovatek Blog
Our Mediatek Auto TWRP porter has received a Beta update to v1.7. This tool enables you easily port TWRP custom
blog.hovatek.com