Can someone please explain to me what is vendor? - Samsung Galaxy S9 Questions & Answers

I don't know what is vendor and how to check what version i have... Please someone explain

I feel you man

A Vendor image contains device-specific hardware drivers and universal for all apps within a smartphone or tablet. A ROM developer can create universal ROMs for multiple devices, then users can apply the appropriate vendor images for their own devices.

Related

mitoc mio p 350

can i install wm6 on this? i need a rom or something to do that? please help me a little with that
No, there is no way to install WM 6 on this device.
why? not even a rom update or something?
Look, no offense but your message is exactly the kind of thing that started the 'n00b bashing' thread on the 'About' forum.
If you read the site introduction and the WiKi you would know the following:
1) ROM is the operating system + drivers specific for the device bundled together - they are not available separately.
2) The only place to find an official ROM update is on the manufacturers site (Mitac in your case) because only the manufacturer can create the ROM image needed for your device (and they did not do it).
3) This site is dedicated to devices manufactured by HTC, we do not have / cook ROMs for Mio (not sure if it is even possible, because the tools are not available).
4) There is no 'something'.

[Q] Build ROM straight from Google Source (AOSP)

Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.

[Q] Requirements for AOKP on serranoltexx

Hey guys!
I just got my serranoltexx and am fairly happy. However, I really would like to try and get AOKP running. Could any devs point me in the direction of where to start, you know, just bootstrap me with some reading? I have a background in Linux and UNIX, have developed some networking stack API projects on windows and have written a ****load of bash, perl etc. scripts in the past. I've also worked on the Matroska container format. Compiling etc. pose no challanges for me. However, I have never fumbled around with Android and I have no idea what drivers and other components might be needed. And how to start finding out what's missing...
I do know how to bootstrap my source repository and sync it... and in theory also how to compile AOKP - for supported devices, that is. What I don't know is: how do I start resolving unmet dependencies, and, you know, generally port a rom to a new device?
Please don't post if you haven't even compiled your own ROM yet. More likely than not, you'd be wasting your time.
I've posted on xda-dev as well, not sure which is the more suitable forum, possibly this one... Link to the other thread:
http://forum.xda-developers.com/showthread.php?t=2501539
And please don't post me to this guide right here as it is only of limited help. As I said, I know how to do it in general... You know, this guide:
http://aokp.co/learn/so-you-want-to-build-aokp-jb-ubuntu-1204
I tried to build it, but many things are missing once i flashed the *.zip.
Maybe i messed up with sources and patches.
Tell us if you have success! :good:

Kernel modifying

Hi
I have asked this before but I haven't gotten the answer and some things have changed.
My goal is to edit the kernel of my device to include rtl8192cu driver.
I have the sources from http://gitgub.com/puresoul/android_kernel_lge_d605 (I hope I got the link right) I am currently stuck at creating the .config file and getting the right files to include the driver. Could anyone help me out, any links to tutorials that actually tell me how to? The guides online are almost all specific to a certain device or their goal is different.

Which version of Android (GSI) can I run on a device with VNDK 27.0?

My plan is to flash a GSI image (LineageOS) for android 9. Specifically the following
- https://github.com/LineageOS/android/tree/lineage-16.0
- https://github.com/AndyCGYan/lineage_build_unified/tree/lineage-16.0
Is there a chance of getting this to run on my device? Please see the attached file for the output of the Treble Info app.
I cannot find any information about the impact of VNDK version 27.0 so any help is much appreciated.
Device info:
- Processor: Rockchip 3399
jossdb said:
My plan is to flash a GSI image (LineageOS) for android 9. Specifically the following
- https://github.com/LineageOS/android/tree/lineage-16.0
- https://github.com/AndyCGYan/lineage_build_unified/tree/lineage-16.0
Is there a chance of getting this to run on my device? Please see the attached file for the output of the Treble Info app.
I cannot find any information about the impact of VNDK version 27.0 so any help is much appreciated.
Device info:
- Processor: Rockchip 3399
Click to expand...
Click to collapse
I have the same issue, only thing I could find out, some features not gonna work, (who know what), if you install a newer vndk you wont be able to return to an older one. Be honest, Project Treble is made for seamlessly update phones, but it is a mess, versions, vndks, legacy phones, A-B-A/B images, etc. it doesnt do what it meant to do.
The XDA forum was a good place to ask questions like this, it was, still remember to get answer about my 10 years old phone, however things really changed over the years. Members change their phones on montly basis, so dont expect any professional answer.
Hi, you ma find usefull information in:
Frequently Asked Questions (FAQ)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com

Categories

Resources