And finally Our device, Redmi 3S (Land), with Treble ported... @TeamMex has brought in initial Treble support to Redmi 3S just like it was done on Redmi Note 4, using Cust as the Vendor partition... Hope He has great success in it...
Source: https://plus.google.com/u/0/+klozzjesus/posts/5REcrMxfq67
Let Us all hop into discussion and questions related to it here, rather than pollute other Development Threads...
Keep things polite and simple, varying opinions are all expected but lets not end up hurting anyone with Our Words... Be Responsible Guys...
Wow great news hope to see android p based roms without much problem in near future
amazing
Wow amazing
Wow ?
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Ash225 said:
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Click to expand...
Click to collapse
Can't get you
fxsheep said:
Can't get you
Click to expand...
Click to collapse
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Ash225 said:
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Click to expand...
Click to collapse
maybe you mean CAF(Code Aurora Forum)?
fxsheep said:
maybe you mean CAF(Code Aurora Forum)?
Click to expand...
Click to collapse
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Ash225 said:
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Click to expand...
Click to collapse
caf is the offical release of qualcomm's opensource
@TeamMex you are simply awesome dude
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Dont demand... You are not paying Him anything to ask Him like that... It will be done when He does it... Be patient...
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Just wait for him to do the magic
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
I working in something's but I can release the old version xD presented in my screens
But have some message every boot and the camera take some time until the daemon is released
Sent from my Motorola Moto Z Play using XDA Labs
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
GoldeneyeS2 said:
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Click to expand...
Click to collapse
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
Can somebody explain me what is treble for?
vandasche said:
Can somebody explain me what is treble for?
Click to expand...
Click to collapse
Just Google it... You can find a lot of really good explanations in it... I'll link a few in the OP very soon...
Related
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
It is the full source for the Xperia C. :good:
dev0xteam said:
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
Click to expand...
Click to collapse
I believe the config file is device dependent so will be different for a116......
still if anyone takes up the project of building it for a116 he has to modify the config :fingers-crossed:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Dj_Ignatius said:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Click to expand...
Click to collapse
Is it complete?
dev0xteam said:
Is it complete?
Click to expand...
Click to collapse
i think yes..
Ok. The sony source is not fully complete but.enough to build a kernel. Still there is some problem in config or something else which is not allowing the kernel to compile..
Sent from my A116 using xda app-developers app
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
A general question :- i previously had mmx a75 which of course didn't had the sources but overclocking through mtkcpu from playstore was achieved..!! So why our device can't be overclocked using the same app..??
Sent from my A116 using xda premium
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
axis.meister said:
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
Click to expand...
Click to collapse
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
konnorrigby said:
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP and got my hopes high. Read your post now and ...
lets hope Mediatek actually releases full sources in the future.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
http://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.Ui5G3sanojp
can this be the full source? i am not a dev so idk anything about it there is a link in the link i gave u maybe u can see it and tell us
so any good news about custom kernel?
Is this enough to build a custom kernel atleast?
Sent from my Micromax A116 using Tapatalk
I have a chinese tablet I ported a ROM for that tablet I have flashed the ported ROM but now I am having bootloop because i don't have the kernel so can I use kernel from different device having same CPU?
You will have to edit the kernel. Each devices kernel is built just for that device. That is why there is no universal kernel.
zelendel said:
You will have to edit the kernel. Each devices kernel is built just for that device. That is why there is no universal kernel.
Click to expand...
Click to collapse
I can't figure out why there doesn't exist an universal kernel. Which parts of kernel should be modified or added for a specific device?
JasonKidd said:
I can't figure out why there doesn't exist an universal kernel. Which parts of kernel should be modified or added for a specific device?
Click to expand...
Click to collapse
That's because each device has different hardware and is programmed differently. Same thing goes for Linux. The kernel that works for my setup won't work on yours.
To be honest I have no idea. You will have to rip the kernel apart and fix the errors one by one. Most likely start with the graphics drivers and such. Their are great tut all over the site.
The lack of kernel source is one well known issue of China based devices.
zelendel said:
That's because each device has different hardware and is programmed differently. Same thing goes for Linux. The kernel that works for my setup won't work on yours.
To be honest I have no idea. You will have to rip the kernel apart and fix the errors one by one. Most likely start with the graphics drivers and such. Their are great tut all over the site.
The lack of kernel source is one well known issue of China based devices.
Click to expand...
Click to collapse
Thanks for your instant response. I think the HAL of android is aimed to solve the problem of compatibility of different devices. But the vendor must open thier souce of kernel if they modified it.
Can't we put all specific drivers at HAL?
JasonKidd said:
Thanks for your instant response. I think the HAL of android is aimed to solve the problem of compatibility of different devices. But the vendor must open thier souce of kernel if they modified it.
Can't we put all specific drivers at HAL?
Click to expand...
Click to collapse
No because they will conflict with each other. Yes the vendor must open the source. You are gonna be pretty stuck without kernel source for the device.
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know
First of all, yes, we can now run 64bits ROM on our phone.
But actually we have to run app_process (system server) as 32bits, mainly cause of sensors non working actually with a 64bits system server.
More to come next, vendor tree is still missing many 64bits blobs, and some of our proprietary services still run in 32bits mode too.
What's needed:
Device Tree : https://github.com/BoulzorROM/android_device_motorola_potter/tree/bzr-64bich
Kernel Tree : https://github.com/BoulzorROM/android_kernel_motorola_msm8953/tree/bzr-64bich
Vendor Tree : https://github.com/boulzordev/android_vendor_motorola_potter/tree/bzr-64bich
Check commits history of those repos to grab needed changes.
A 64bits TWRP is available here : https://drive.google.com/file/d/1RQL-RaZh5BeBq8ARg8EBrvma4RtnhGtk/view?usp=sharing (mandatory to flash 64bits ROM)
A 64bits MultiROM TWRP is available here : https://drive.google.com/open?id=0B6-Tz_7kDyxsNGp2V2ZBRV9TV1U (thx to @GtrCraft)
BoulzorROM is available here : https://drive.google.com/file/d/1AQxlUSxrzH1Sq6L5c_ItZI_qtihfUUtM/view?usp=sharing
Validus is available here : https://drive.google.com/open?id=1-aNOD0ef3a1hqnUEeDaNs0GSgKMFBVgy (thx to @GtrCraft)
Some ROMs are almost ready to be shared here soon, stay tuned !
FAQ :
Q : I have an error regarding armv8-a not supported
A : Switch TARGET_2ND_ARCH_VARIANT to armv7-a-neon
Wow! Impressive... Exceeding Motorola/Lenovo in making firmware for their phones! [emoji106]
Subscribed. This is epic!!!
so what do testers say?
my g5+ is still locked and I am too busy to unlock flash and test but 64bit rom may be worth time
Added Validus and MultiROM to the list.
No amount of thanks will be enough for this. I seriously want to donate but I am a student with nothing to donate with. But man!! Thanks!!
The boulzor rom is nougat or oreo?
skooter32 said:
The boulzor rom is nougat or oreo?
Click to expand...
Click to collapse
It is oreo, as i tested it it works nice
Nevermind, thanks @vache!
Tysm Vache ... Best Dev I have ever seen .... Blessed to buy Moto G5 Plus and now I won't regret that I couldn't Buy Moto G5S Plus as it doesn't have any Development ONN!!
ckret said:
so what do testers say?
my g5+ is still locked and I am too busy to unlock flash and test but 64bit rom may be worth time
Click to expand...
Click to collapse
You definitely need to plan some alone time with your phone. For everything that it does for you do not neglect it. Don't you think your phone wants a 64-bit ROM just like all the other flagships.. so yes definitely set aside some time unlock your bootloader flash TWRP and get this ROM. Don't forget we are on arm64 gapps
Sent from my XT1687 using Tapatalk
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
But sir why??? The normal people around know who does the hard work in bring up the device tree, etc.....why let one egotistic brat think he owns the world because he can do a repo sync of and already build devicee tree and sources....most of us know who does the hard work...just ignore the krackflashers...
Sir i sold my Pixel because you were here turning my cheap moto g5 wit sd625 into a pixel....
You even covered for Lenovos incompetence & brought 64bit to a 32 bit device...thats next level dedication..why leave that bc of some ignorant self-righteous prick....ur letting em win...
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
With all due respect sir, you're the only reason I bought phone.. I'm seriously not kidding... The specs didnt matter.. development from a person like you did... Please don't abandon us... We always know you're the guy who does the hard work... I'm sure the guys who try to bring you down can do nothing without you.. Please have a change of heart
Sent from my XT1686 using Tapatalk
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
w the hell? I am sorry that trolls trying to ruin your day.
thanks for the work you have done on maintaining this device
I bought you some beer
market88 said:
Sorry for noob question. What's the advantage of using 64-bit from? Thank you
Click to expand...
Click to collapse
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
CreasingMass Dev said:
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
Click to expand...
Click to collapse
Not everything is working, at least what I tried. Slowmo crashes the app and panorama as well. What is the version you are using?
CreasingMass Dev said:
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
Click to expand...
Click to collapse
Which ROM you flashed?
Vache if you keep building and need any speedy build hardware let me know, I can give some ssd VM space on my 3.9ghz 1700 lol. Love the work, ignore the plebs. Still looking for that paypal link btw
karlmorgan92 said:
Not everything is working, at least what I tried. Slowmo crashes the app and panorama as well. What is the version you are using?
Click to expand...
Click to collapse
i haven't tested slowmo nor panorama in the app (i never use that) but everything else is working for me, i'm using this one https://drive.google.com/open?id=1zg3J0_NIccghtdj3nKuyyuHKs5VEegxh
market88 said:
Which ROM you flashed?
Click to expand...
Click to collapse
BoulzorROM, the one in OP with nano 8.0 arm64 opengapps and supersu
CreasingMass Dev said:
i haven't tested slowmo nor panorama in the app (i never use that) but everything else is working for me, i'm using this one https://drive.google.com/open?id=1zg3J0_NIccghtdj3nKuyyuHKs5VEegxh
BoulzorROM, the one in OP with nano 8.0 arm64 opengapps and supersu
Click to expand...
Click to collapse
Is video recording buggy? I might try this out later..
How can I port for the with the same processor? in vendor.img which files do i need to change? which lib? etc. thx
0
Seppppx said:
There isn't a specific guide for this. You will have to use your creative thinking to create solutions for problems. But you can follow these steps.
1. If you want to port your vendor to a new android version. See what was changed with phones with the same SoC.
2. Replace old files with new files from the other device vendor.
3. Be careful. You can mess up your phone.
Click to expand...
Click to collapse
I want to try this for gsi roms. Because current GSI roms send me to the recovery part. can't boot.
As you said number 2 I don't know which old files to replace
if it's easy for you maybe one day help with teamviewer
You'd build a GSI system image and change that. You don't need to use /vendor as it contains blobs for the device and doesn't need to be changed.
0
Seppppx said:
You won't need to port a vendor partition if you want to try GSIs.
Unless your phone is not treble. Have you checked if your phone is treble? You can do that by installing treble check from the Google Play store.
Which GSIs have you tried?
What device do you have?
What Android version do you have.
Devices that ship with Android 8 must be treble because of requirements by Google. (Unless your phone isn't google certified or VTS certified, I'm not sure)
You can see which files to add and delete (this won't be the same for your phone) by looking at the diff between treble and non treble proprietary-files.txt, proprietary-files-qc.txt, proprietary-files-qc-perf.txt.
https://github.com/ArrowOS-Devices/android_device_asus_zenfone3/compare/arrow-9.x...9.x-non-treble
Click to expand...
Click to collapse
Again hi. Phh gsi roms work fine. I want to try Ertan gsi. erfan gsi does not boot. That's why I thought maybe porting would be the solution. I have gm9 pro. Sp660 SoC. I want try a2 vendor port but ı cant
aykutfb93 said:
Again hi. Phh gsi roms work fine. I want to try Ertan gsi. erfan gsi does not boot. That's why I thought maybe porting would be the solution. I have gm9 pro. Sp660 SoC. I want try a2 vendor port but ı cant
Click to expand...
Click to collapse
No it's with how the system.img is built. Sometimes takes a bit more work to get things booting
TheExploitedOne said:
No it's with how the system.img is built. Sometimes takes a bit more work to get things booting
Click to expand...
Click to collapse
oh okey understand. I think there is no any solution :/
aykutfb93 said:
How can I port for the with the same processor? in vendor.img which files do i need to change? which lib? etc. thx
Click to expand...
Click to collapse
Ihave The Same Question but with different processor