So after checking the internal specs I found out project Treble is supported, but I don't know how to enable it or how to use it. Has anyone figured it out yet?
Rebelwolf4622 said:
So after checking the internal specs I found out project Treble is supported, but I don't know how to enable it or how to use it. Has anyone figured it out yet?
Click to expand...
Click to collapse
Project Treble is automatically enabled on any Google certified Android device that ships with 8.0+, it allows one generic system to work on any device. Kinda how one Windows installation disk work for any computer.
It's mostly used for Manufacturers to update their devices faster without having to wait for the chip vendor to update their drivers and stuff, but we use it to install custom ROMs without having to build/bundle a new kernel for every new release.
I wrote a guide here if you wanna read into how to install one
https://forum.xda-developers.com/mo...de-how-to-flash-generic-image-moto-g-t4131199
Related
If the vendor (in this case Vodafone) don't provide sources, does it mean I'm unable to create a ROM for it?
Put it another way, is it possible to create a ROM using only a running device?
The Original Leppa said:
If the vendor (in this case Vodafone) don't provide sources, does it mean I'm unable to create a ROM for it?
Put it another way, is it possible to create a ROM using only a running device?
Click to expand...
Click to collapse
Yes, if you want to build a "true" custom ROM you will need the stock source code for your device.
If you can root, you can use adb or Terminal Emulator to do a "ROM dump", or dump just a copy of your system.img, then modify that system.img and then use adb to push the modified system.img to your device. It will be considered a modified stock ROM, it won't be a "custom" ROM but you can modify it quite heavily with things like Xposed, Gravity Box, and a few other good mods and themes.
Or you can get a copy of your stock firmware(not the same as source code), then find other devices with the exact same hardware that have a better version of Android than yours, then use your stock firmware to port the better version to work on your device.
Building a true custom ROM is "possible" without stock source code but it would require VERY extensive programming and developer knowledge to do it because you'd have to do every bit of it from scratch with no resources to work with.
Sent from my SM-S903VL using Tapatalk
So, I'm screwed, in terms of porting?
The Original Leppa said:
So, I'm screwed, in terms of porting?
Click to expand...
Click to collapse
It would help if you had stock firmware for your model then you can find another device with the same hardware architecture(chipset), if they are similar enough you can port it.
It's possible to port between devices that aren't exactly the same chipset but that also requires extensive developer knowledge.
If you aren't experienced then you're pretty much out of luck.
If you want to customize android devices then you need to get less obscure devices. Next time, research the device first to see if there is a known rooting method for it and whether there is custom development available for it before you get it. Or if you get a device that just came out, get a device that you are certain that developers will support, typically a flagship/popular device.
The cheap low-mid range devices usually don't get support from developers and the ones that do get support are not supported by real develoers, they are supported by members that took it on themselves to learn how to build android just so they can update their device but their work usually isn't exactly right due to their lack of experience.
Sent from my SM-S903VL using Tapatalk
I'm trying to build Android on my machine, and everything is going well, but there is one thing I am missing, and that is the binary drivers for the OnePlus 6. The Android build guide only has the drivers for the Nexus and Pixel phones, and after doing some major Googling, I can't find them anywhere.
Since people are already releasing custom ROMs for the OnePlus 6, I assume they are out there, but I haven't been able to find a download location for them at all.
To be clear; I'm looking for the drivers that are on the phone itself, not the USB drivers you install on your PC.
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
jabbermacy said:
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
Click to expand...
Click to collapse
I'm pretty sure that is just the drivers to connect it to the PC and keep it synced with the PC. What I am talking about is the drivers for the hardware inside the phone such as the GPS chip, GPU etc.
jabbermacy said:
i noticed when I pulled my OP6 first time, a CD gets mounted with drivers, did you see it?
Click to expand...
Click to collapse
is this a joke? :laugh:
TheMuppets Repo used to be my go-to proprietary vendor repository for huge number of OEM and devices. I see that Oneplus6 isnt there yet. May be wait until they add or may be someone else might help you out to get it at the earliest
vijai2011 said:
TheMuppets Repo used to be my go-to proprietary vendor repository for huge number of OEM and devices. I see that Oneplus6 isnt there yet. May be wait until they add or may be someone else might help you out to get it at the earliest
Click to expand...
Click to collapse
Thanks for the link. I've starred the repository. I guess I'll have to wait then or investigate some of the custom ROMs to see if I can extract them by hand. That might be a little difficult for me though as I'm entirely new to Android operating system development.
Are you talking about device tree? It's not available yet, but OP promised to release it.
Also, the current roms available use oxygen OS as the base ie. Modified Oxygen OS or take advantage of treble as device tree is not needed for that.
Shouldn't there be a pull-files.sh script that pulls all the files?
That's what I did on my 3T
Actually I don't even think the source code for ROMs is available yet, I saw this article: https://www.xda-developers.com/qualcomm-snapdragon-845-kernel-source-code/
As you all know GSI image alone not sufficient to get fully functional robust stable OS running on Lenovo p2. There are many flashable zip files which need to be flashed individually to get most of the features working. Which makes GSI image meaning less.
So post/discuss all the available GSI and device specific features for Lenovo P2 here.
It will be helpful for Devs and users.
** Requesting Devs to work on device specific feature support over GSI image. **
So far our Dev helped us getting up to this level. We need little more effort to make the GSI image successful on our device.
Expecting Users active support for Devs.
Edited: request only to make device specific features which lacks in GSI image.
Refer post #3.
What do you mean by device specific GSI? What's the point of doing this while GSI (Generic) means (for us) that you can actually flash it over multiple Treble devices out there?
If you recompile system image with device specific patches it will be basically device specific standard ROM (but with Treble which is basically not needed now) and not GSI anymore.
I don't get why are you people actually need "Treble" compatible ROM while existing standard ROMs are working great for now. Because they're Treble ROMs? What does it change? GSIs created using phhusson scripts are one big hack at the moment and their state is experimental. Of course they will work but they're lacking of device specific build.prop's.
Oreo one's are actually fully compatible with Lenovo P2 and stable because I tested them myself. Probably all of them (but all I tested) share the same device specific bugs. Even FP gestures works but this function needs to be activated by "setprop persist.sys.fp.navigation 1" after boot. The fix zip provided in P2 Mods subforum is actually copying script to system which will actually do that after every boot, nothing more. Google told on their AMA that they will make official documentation of making GSIs in the near future so I believe that will fix our current problems and device specific build.props could be generated and added to ROMs without touching system partition integrity state and recompiling them.
Until Android Pie ROMs will be stable as GSIs you will also not benefit too much from creating device specific system image because you will need to wait for Mike or someone else to create compatible vendor image and kernel (Probably Mike will be the first so you will need to wait for official release of LOS16).
Recompiling ROMs just for adding few fixes is a waste of resources. You need approx ~250GB of memory to compile and maitain one ROM, time (depending on memory you are using) and a lot of electricity.
In my personal opinion, creating Magisk module for P2 devices which will fix build.prop systemless-ly and add that command for activating FP gestures will be better alternative for now. I could personally look into it when I get some time.
If you still think that you need these device specific system images for every ROM at all costs, you could build them and maitain yourself or ask someone who will do this. Maybe Fullbustah will be eager to do some requests because he already built some popular ROMs on Mike's sources lately. You could also extract system.img's from his last builded ROM's and they will be device specific system images you are looking for . The only problem is that I don't think he is willing to maitain all of them at once.
I'm sorry if my previous post conveyed wrongly.
All we need is GSI images should be flashed directly. I didn't conveyed anywhere to build a sperate image from GSI.
May be I asked to maintain device specific vendor/system tweaks in a one place which will be flashed on top of any GSI image to get all the features working in our device.
Hope this helps!
MAILUS said:
I'm sorry if my previous post conveyed wrongly.
All we need is GSI images should be flashed directly. I didn't conveyed anywhere to build a sperate image from GSI.
May be I asked to maintain device specific vendor/system tweaks in a one place which will be flashed on top of any GSI image to get all the features working in our device.
Hope this helps!
Click to expand...
Click to collapse
Ah, okay. It changes a lot. I tested few Oreo GSIs about a month ago an everything was working fine and stable for me. The only tweak needed was FP gesture fix but it was messing with the system partition and I was too lazy to make to improve it so I just gave up using it. And another missing thing was build.prop because device is named "Phh's Treble ARM64" or something like that after installing GSI. Also build fingerprint is always messed up so I had problems passing SafetyNet even with Magisk.
Only these fixes are required for making Oreo GSI's working perfectly or almost perfectly (like official LOS) so I'm going to do Magisk module that will cumulate all of these fixes into one, easy to install solution. If I missed something just let me know.
I have an old Samsung phone running on Marshmallow. I want to build android and flash it on the old phone. Many take Google Pixel to show how to do it and say it’s not possible to do it on non-Google device. Is there a way to get around it?
KrishnaD3V said:
I have an old Samsung phone running on Marshmallow. I want to build android and flash it on the old phone. Many take Google Pixel to show how to do it and say it’s not possible to do it on non-Google device. Is there a way to get around it?
Click to expand...
Click to collapse
Sure. Here's some reading material on how to build a custom Android operating system. https://www.androidauthority.com/build-custom-android-rom-720453/
If it all seems too much, you could instead install a custom Android operating system prebuilt by others. One such example is LineageOS which has its own website and installation instructions.
You will have to first determine the exact model and sub-variant of your Samsung phone.
Then determine whether it is network carrier unlocked.
Then determine whether the bootloader is allowed to be unlocked (allow oem unlocking).
LineageOS Downloads
download.lineageos.org
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
KrishnaD3V said:
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
Click to expand...
Click to collapse
Depends on the the exact device model? (Go to settings =>About phone) (or in the dialler, type *#0*# then tap on 'version'). Then search the XDA forum for that device, then spend some time scrolling through the posts to find the info you're searching for. https://forum.xda-developers.com/c/samsung.11975/
*#0*# doesn’t give any option for version. So I thought to see in settings. What ‘version’ should I look for?
Go to settings =>About phone
Look for a code which which looks similar to SM-GTI9100
KrishnaD3V said:
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
Click to expand...
Click to collapse
Either extract them from phone's Stock ROM file, or pull them out of phone.
zpunout said:
Go to settings =>About phone
Look for a code which which looks similar to SM-GTI9100
Click to expand...
Click to collapse
It’s SM-A800I running android 6.0.1 . And it’s not on the list that you sent. What can I do?
jwoegerbauer said:
Either extract them from phone's Stock ROM file, or pull them out of phone.
Click to expand...
Click to collapse
I do have the stock rom file but I can’t find guide on how to do so. I found a video where person extracts it from lineage os. Is the process going to be the same? And by the way does it matter which version of stock rom I have because the phone came with android 5 and I updated it to 6 with official update.
KrishnaD3V said:
It’s SM-A800I running android 6.0.1 . And it’s not on the list that you sent. What can I do?
Click to expand...
Click to collapse
Yeah, there's not much development on that device, I read somewhere that Samsung supposedly never released the source code. It is hard to search for, but I did find this link: https://forum.xda-developers.com/t/...al-cyanogenmod-13-for-galaxy-a800f-i.3344081/
I did find out that the nickname of your SM-A800I model is "a8hplte" which might help you in search engines.
Looks like a dead end to me though.
KrishnaD3V said:
I do have the stock rom file but I can’t find guide on how to do so. I found a video where person extracts it from lineage os. Is the process going to be the same? And by the way does it matter which version of stock rom I have because the phone came with android 5 and I updated it to 6 with official update.
Click to expand...
Click to collapse
The so-called binary blobs are kinds of hardware drivers, you can't simply extract them of a Custom ROM, you have to extract them from a phone's original Stock ROM, as I told you this already earlier.
These binary blobs typically are found under /vendor/lib(64), some also under /system, /etc and /bin.
Most of the blobs are executable files or libraries, run as independent services on phone's boot.
jwoegerbauer said:
The so-called binary blobs are kinds of hardware drivers, you can't simply extract them of a Custom ROM, you have to extract them from a phone's original Stock ROM, as I told you this already earlier.
These binary blobs typically are found under /vendor/lib(64), some also under /system, /etc and /bin.
Most of the blobs are executable files or libraries, run as independent services on phone's boot.
Click to expand...
Click to collapse
Thanks for the info
zpunout said:
Yeah, there's not much development on that device, I read somewhere that Samsung supposedly never released the source code. It is hard to search for, but I did find this link: https://forum.xda-developers.com/t/...al-cyanogenmod-13-for-galaxy-a800f-i.3344081/
I did find out that the nickname of your SM-A800I model is "a8hplte" which might help you in search engines.
Looks like a dead end to me though.
Click to expand...
Click to collapse
Not so beginner friendly I guess . I try my luck extracting the blobs as described by
jwoegerbauer.
Hello
I will perhaps keep my S22U instead of upgrading to s23u , I will then most probably root it as my warranty will soon come to an end and I won't care about knox flag. But is there any AOSP based custom rom for the S22U snapdragon ? If yes can you use Expert Raw app?
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
V0latyle said:
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
Click to expand...
Click to collapse
Thanks
Though it looks like an update thread for Pixel phones no?
vegetaleb said:
Thanks
Though it looks like an update thread for Pixel phones no?
Click to expand...
Click to collapse
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
V0latyle said:
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
vegetaleb said:
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
Click to expand...
Click to collapse
I don't think so - I'm pretty sure features like that are not core Android mechanics, so they wouldn't be included in AOSP. I don't know for sure. Keep in mind that the whole idea behind a GSI - Generic System Image - is that it can run on pretty much any device. Google has been using this model since the Pixel 3 - instead of having different system builds for each device, they use a generic common system image, while device specific features are contained in other partitions such as /product. This way, when they provide the monthly update for Pixels, they don't have to completely rebuild the firmware; they can just use the AOSP GSI for the "core", and any device specific changes are separate in /system_ext and /product. It's a modular design that really helps streamline the update process; it also means that devices that no longer receive updates can still potentially run the latest AOSP core.
I imagine you could extract the product.img from the Pixel 7 factory zip and flash it to /product on your device, but because it's device specific, it most likely wouldn't work properly.