Afaik Vendor is a partition with some sort of proprietary drivers/software for device specific hardware or functions.
I see the terms "R Vendor" and "Q Vendor" on custom Roms, but idk what they mean or how they are used?
Earlier the Android versions have names from eating stuff like Cupcake.....but its Q for Android 10 R for 11 P for 12 and so on.....!!!Cheers!!!
Related
Now that we can unlock the bootloader and root the galaxy tab a T510 It would be cool to see custom roms developed for it
I would love to see AOSP android running on the T510
Is there anyone in the custom rom development able to do
Does nobody want to see a custom rom on this device
I'm Interested too !! A debloated Rom please !!!!!
I posted my TWRP build here, so I'm hoping that enables more custom ROM development for the SM-T510. Unfortunately, my initial attempts with GSIs were unsuccessful, even with NoKnox to disable most of the Samsung security features. Seems I'm still missing something, but Galaxy S10 owners have had some success after making minor changes to the generic image.
Has anyone tried this GSI guide for the Galaxy A8, which shares the same Exynos 7885? It's got the rw-system.sh fix noted above.
I may purchase.this very soon. I have high hopes for this device getting lineage
Would love to see a custom firmware release as there's only a 32 bit version of android and I'd like to get 64 bit support. Great little tablet aside from that downside
Interesting note here in the @phhusson's Treble Wiki:
Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+.
So, I'm thinking that we should be using ARM for A/B...and not many custom GSI ROMs are built for that target.
Okay, I had some limited success with the latest AOSP 9.0 GSI build from @phhusson. The note above from his Wiki was spot on: We need an ARM A/B configuration for the SM-T510/T515...which is unfortunately a rare combination. You must also this updated /system/bin/rw-system.sh script. I used the build with GApps (system-arm32_binder64-ab-gapps-su.img.xz), but this generates a ton of error notifications because the device is not Play Protect certified.
We're getting much closer, though.
Okay, here's a quick-n-dirty custom ROM build based on the AOSP 9.0 GSI mentioned above: https://forum.xda-developers.com/ga...om-nexus-stock-2019-galaxy-tab-10-1-t3944222/
Since this phone is fully treble compatible it should be possible to install something like the Google android 10 GSI (directly from google) and provided you flash the android 10 vendor beforehand. Now are there any differences between those GSIs and the Roms specifically made for this phone?
I saw someone post that androi 10 is working on exynos 7870 device and until today im still not seen anyrom about it
Try proget spaghet with gsi android 10?? not stable but still its android 10
sakshya619 said:
Try proget spaghet with gsi android 10 not stable but still its android 10
Click to expand...
Click to collapse
I installed Spaget X and GSI ROM. Everything works good including Camera and etc. But Spaget X cannot mount /preload that causes all patches cannot be installed. So LED patch to enable the LED cannot be installed.
Spaget X has been discontinued. And I have no clue to fix this issue. Do you have some more suggestions for any new Treble project?
Good News! You No Longer Need To Downgrade To Color OS to FLASH CUSTOM ROMS.
Well, if you're Lazy to read like me, then watch the video else, it could be long read...
On 14th June 2020, the first Lineage OS 17.1 for Realme X2 based on Android 10 (Realme UI Vendor was publicly released, most other Realme X2 Custom Roms started rebasing from Color OS 6.1 Vendor to Realme UI Vendor and Android 10 firmwares.
What that means is before now, Developers had to make do with Android Pie Vendor (In color OS 6.1) to build a functional ROM. Not just the Vendor, the Kernel was also based on Android 9 then.
And why is it so?
Realme (or Realmeme - as I fondly call them sometimes) didn't even give out a single Realme X2 device for development, and worse than that, no flash tool that can work in EDL mode (when phone is completely off) and some of their crazy code arrangement then means that you could break the fingerprint function by unlocking bootloader - I mean, who does that?
Few of the developers bricked the device they bought with their hard earned money trying to make things happen for all Realme X2 users.
Some users came together and crowdfunded new device(s) for development.
Developers still have to wait for Realme to sort out their codes and allow fingerprint function with unlocked bootloader in Realme UI which happened from updates C.14 for RMX1991 C.08 for RMX1992 and C.04 for RMX1993 which happened not so long ago, now these devs started working harder and rebasing the device tree to Android Q, cleaning up the kernels, improving the UX and all that.
So, what it means now is that any custom Rom you flash after June is Most likely Based on Android 10.
What's the implications?
For starters, if you are still on Color OS 6.1, You have to upgrade to the Latest Realme UI or at least the version mentioned above before you can flash Android 10 Based Custom Roms.
You don't need to downgrade anymore to Color OS 6.1 to flash Custom Roms.
The Good news is, all the known bugs are ALL GONE like me that went back to RUI because of WiFi display (Wireless Cast) I am ot back to Android 10 Based Roms and I am so loving it.
OH! I haven't said anything about CUSTOM VENDOR!
You got to give it up to all these Wonderful Realme X2 Devs, they've built a Custom vendor.
Custom Vendor is the only way to escape Realme UI annoying Encryption problems which means you don't have to format data every time you switch to another Rom that uses custom vendor too.
HOW TO FLASH ANDROID 10 BASED CUSTOM ROMS
#1 BE on the latest Realme UI
#2 unlock bootloader and Flash TWRP and vbmeta
#3 make a full backup of your partition (including Persist partition - very important)
#4 Wipe caches, data, system
#5 DO NOT WIPE VENDOR even if the Rom You are flashing has custom Vendor.
#6 if you are coming from RUI format data and Reboot.
That's it.
Links to some Android 10 Based Roms in the video description or just check the development section.
All credits to the Devs:
* Team Phantom For Testing The Builds
* @dev_harsh1998 and @Sukrut4778for your trees.
@SiddharthBharadwaj
@th3_gunn3r
@KuranKaname
And lots of others I may have forgotten to mention.
Has S21U any treble / GSI rom yet ?
ounila said:
Has S21U any treble / GSI rom yet ?
Click to expand...
Click to collapse
I think you misunderstand the point of Trebleized devices and GSIs.
A GSI, or Generic System Image, is a system image designed to be used with any device, usually with the original kernel.
Project Treble is the idea behind "modular" software such as GSIs and GKIs (generic kernel images), where the "product specific" code is divorced from the kernel and system code and kept in its own partition.
So, to answer your question, I believe the S21U is Treble enabled, which means you can use any GSI.
thanks for reply.
I understand the subject well since i installed the GSI based roms for xiaomi phones (curtana. mojito . vayu . alioth ...) So, my real question is: Why there is no (pixel xperience . evolution. arrowOS ....) roms yet ?
ounila said:
thanks for reply.
I understand the subject well since i installed the GSI based roms for xiaomi phones (curtana. mojito . vayu . alioth ...) So, my real question is: Why there is no (pixel xperience . evolution. arrowOS ....) roms yet ?
Click to expand...
Click to collapse
I dont understand this question. Why should be a gsi device specific thread..?
Just Google PHHUSSEN treble experimentions or click this Link. This list is almost daily updated with much of gsi roms like PE or Evo.
Look for haridhayal11's gsi project for exynos 2100, I can't remember if he posted here before but he's the one that enabled us to use GSI on S21s with good stability.