Database Users

Omni Rom For MTK Devices

Many rom projects like Cyanogen mod, Paranoid droid rom and many others were released only for renowned company phones like Galaxy Series, Nexus series etc etc, where as millions & billions of MTK soc phones that contribute alot to the daily millions of Android activations are left out. Many MTK phones developers started request threads for cyanogen mod and other rom communities to build/release a rom for MTK phones but those request were neglected till date.
Now with the start of new rom project "Omni", MTK phone devs are hoping that this rom will also be compiled & released for MTK phones. We want Omni pioneers to release this rom for millions & billions of MTK phones.
We are willing to help you guys making Omni rom project better & grow.
Regards

Wouldn't have it been easier to read some posts in the forum?

This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.

jerdog said:
This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.
Click to expand...
Click to collapse
There are a lot of things in the way. Also, any MTK devices that ship without kernel sources (there are a lot of them) are still out of luck.
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.

Entropy512 said:
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.
Click to expand...
Click to collapse
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.

I too have two MTK phones .....they are a powerful if it got development projects like this ...it will be the no.1 vendor in chip set marketing and ...I support for OMNI PROJECT
Sent from my Fly IQ451 using XDA Premium 4 mobile app

C-o-M said:
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.
Click to expand...
Click to collapse
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.

Entropy512 said:
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.
Click to expand...
Click to collapse
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app

XperianPro said:
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app
Click to expand...
Click to collapse
Nobody can predict what happens in the future.
In terms of working with OEMs, not sure what your question is, but one thing we do bring to the table with Omni is considerable experience in working with OEMs. And that should be rather beneficial for everyone

Will you be allowed to release all sources needed to build the ROM?

There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.

darkguy2008 said:
There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.
Click to expand...
Click to collapse
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589

pulser_g2 said:
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589
Click to expand...
Click to collapse
So with this you mean that those sources work for MT6577 devices?

I wish you guys the best of luck, but conserning MTK and their closed sources policy, i really don't believe those sources (and im talking about the framework /RIL) will be Open Source.
If we are lucky enought we may get some working builds for some of the phones (if an brand gives you support), but concerning the MTK licenses, well its an MINE FIELD.
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
B.Regards

superdragonpt said:
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
Click to expand...
Click to collapse
AFAIK, you are wrong:
chasepoes said:
Well I know of one dev. who is develloping CM port voor MTK658x devices (usinf Faea mobile). For now he has to operate under a NDA agreement, but once finished his source will be come available.
Click to expand...
Click to collapse

darkguy2008 said:
So with this you mean that those sources work for MT6577 devices?
Click to expand...
Click to collapse
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.

Entropy512 said:
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.
Click to expand...
Click to collapse
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/

darkguy2008 said:
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/
Click to expand...
Click to collapse
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...

XperianPro said:
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...
Click to expand...
Click to collapse
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.

Entropy512 said:
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.
Click to expand...
Click to collapse
How very true. I have high hopes for this project as my current device is an OPPO R819. I chose OPPO because exactly they try to be open with the developers, having the experience of Motorola and their locked bootloaders the past years while the Motorola DEFY was my main device. It took a long time for the DEFY to get its first custom kernel and it only happened thanks to some very persistent people. It shouldn't be like this, so as long I have a choice I'll opt for unlocked (and cheap...) devices.
Sent from my Nexus 7 using xda app-developers app

Copperhead OS

Can someone port the copperhead os to moto g4 plus.. which is the most secure android ever used by google itself... in their pixel series of phones.. :highfive:

stkpxl said:
As much as I would love to see it ported, the G4 doesn't support it. These are the types of phones that are supported currently: Devices directly supported by the Android Open Source Project are candidates, meaning the Nexus and Pixel lines. Only devices with a 64-bit CPU architecture, full verified boot and LPDDR4 memory with TRR will be considered. Devices also need guaranteed security updates from the hardware vendor for device-specific components like firmware.
Pretty sure that leaves us out.
Click to expand...
Click to collapse
on their website they mentioned as.. it's an open source project. it should have been developed for 32 bit.. bcoz more than 90℅ devices are 32bit based system... but why they are not developing for other Android.. even though other android phones are the majority..

Google's Project Treble for OnePlus 3(T)?

Please suggest a way to make our device get the Project Treble officially.
More details on Google Project Treble,
Thanks.

This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best. ?

pitrus- said:
This can only be accomplished by the manufacturer of the phone (Oneplus) in corporation with the SoC manufacturer (Qualcomm). But we can always say pleeease with a big nice smile in the Oneplus forum and hope for the best.
Click to expand...
Click to collapse
As per the official OnePlus forums from I visited, I have read them saying "Treble is interesting, we will keep close an eye on it.."
Which is like killing me all the time...
Could someone from XDA OnePlus team reach out to OnePlus official and represent our request???

Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.

orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Dint quiet get you there mate...
you mean Treble is not a good move?

orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk

dante_67 said:
Incoherent, confused, and totally off the point, what after next year there is no Android update, would that kill the phone, I still have wildfire s, it's on ginger bread, it runs youtube, Facebook and what's app, this phone will be usable till it is not broken
Sent from my ONEPLUS A3010 using Tapatalk
Click to expand...
Click to collapse
I like turtles.

Is it possible for devs to port the kernel to 4.4+ once OP release sources for Oreo?

Well, given that OEM support for our device will end by mid next year, Project Treble implementation is not really worthwhile for our devices. It won't be useful to OnePlus for long (for the 3/T), and also it'll be quite expensive to be worked on.
But if OnePlus decides to pull an OPO, and grant us our wishes, we'd all be happy.

It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.

orange808 said:
Project Treble would be expensive and difficult to implement. Given what OnePlus did with the OP2, it's clear where this is going.
The OP3/3T hardware will be likely be completely abandoned by next Summer. One year, folks.
Of course, Google poorly designed Android from the start and created this problem. Hardware abstraction and support for official AOSP should have been baked in from the start--or (at least) implemented before Gingerbread.
I don't use the physical buttons on this device. There's not much to wear out. This next upgrade will be forced by software. I don't give a darn about benchmarks, games, or huge pdf's; hardware isn't compelling anymore. I am going to wait and see about x86 on ARM. Even with limited performance, it would be nice to carry one device and just plug into the hotel television hdmi. Also, the updates would flow for a solid five years--longer than I would use a new device (as it should be).
There will be some broken buggy ROMS floating around for a while after next summer, but those are for kids.
Click to expand...
Click to collapse
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?

thes3usa said:
x86 or ARM? Jesus, that's some pretty old CPU architecture right there. Care to elaborate as to why you want it to go further?
Click to expand...
Click to collapse
I like turtles.

orange808 said:
I like turtles.
Click to expand...
Click to collapse
Makes sense. Thanks for your informative explanation xD

OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk

HampTheToker said:
OnePlus 3, 3T, 5, and 5T are all missing out on Project Treble, but will be updated to Android 8.1.
I'd rather have Treble.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.

Not only "OnePlus" doesn't give project treble,
Stop complaint about "Project Treble"

there is a petition going to support Project Treble for OnePlus devices
feel free to sign the petition and make a difference
We (the community) would like to ask Oneplus to support Project Treble in OOS

casual_kikoo said:
And if OnePlus had release Project Treble but not Android 8.1, you would have also complained.
Stop complain about everything you don't have, and enjoy what you have: should I remind you that Android 8.0 should have been the last update for the OnePlus 3(T)? Plus, Project Treble targets all devices launched with Android 8.x, which is not the case for actual OnePlus phones.
Click to expand...
Click to collapse
Project Treble is compulsory for devices launching with Oreo, but can be enabled when a device is updated (see OG Pixel/XL and Essential Phone), so OnePlus can do it if they want to.

JoinTheRealms said:
It has almost nothing to do with Oneplus, if Qualcomm update the reference msm8996 kernel to linux 4.4 then its trivial to port oneplus modifications over.
Qualcomm has practically zero motivation to do this, infact it works against their interests.
Click to expand...
Click to collapse
Correct me if I'm wrong, just guessing here, but isn't the Google Pixel 1 getting treble? It has the same SOC, so getting the required kernel references shouldn't be a problem right?
EDIT: This is ofcourse only applicable to the 3T, so they'd have to split the OTA's from the OP3. Highly doubt that they'd do that though.

[Discussion] Project Treble

To all those who want to know more about Project Treble please use this thread to discuss about it.
What is Project Treble?
Ans. Treble is the most significant low-level change to the Android platform to date. To simplify heavily, it separates the vendor implementation from the Android framework in an effort to avoid lengthy waits for updates. . Let’s break things down a bit more:
The full update process to bring a new Android version to devices is a long and complex topic.
The “vendor” usually refers to silicon-manufacturers such as Qualcomm, but can also refer to the maker of any other proprietary hardware found in a device. The “device maker” or “OEM” usually needs to wait for the vendor to update their code so the proprietary hardware works with the Android OS framework in a newer version of Android.
However, what is happening with Project Treble is that Google is requiring that any vendor-specific code be separated from the Android OS framework and instead live in its own vendor implementation. Usually this means that there is now a separate /vendor partition on Treble-enabled smartphones that contains a bunch of HALs (Hardware Abstraction Layers).
Furthermore, vendors must implement code that lets the Android OS framework communicate with HALs in a standardized way. This is done via HIDL (HAL Interface Definition Language). With this in place, an OEM can work on an Android update without having to wait on vendors to update their HALs. Theoretically, this should speed up the entire Android update process as vendors can update their code at any time through the Play Store.
For indepth information check out this pagehttps://www.androidauthority.com/project-treble-818225/
Devices with Treble support:
- Essential PH-1
- Google Pixel
- Google Pixel XL
- HTC U11 Plus
- Huawei Honor 8 Pro
- Huawei Mate 9
- Huawei Mate 10 Pro
- Sony Xperia XZ1
- Sony Xperia XZ1 Compact
- Asus Zenfone 4 (ZE554KL)
- Honor V10
- Huawei P10/ P10 Plus
Devices which will ship with Android 8.0 Oreo will be Treble compatible by default.
Older devices will become treble compatible if the OEM creates a vendor partition via OTA update, like the Honor 8 Pro.
Custom Roms:
As of now @phhusson is working hard to make his AOSP rom boot as a fully functional rom on all the Treble supported devices, go check out the rom thread here https://forum.xda-developers.com/pr...evelopment/experimental-phh-treble-t3709659"]
Check Treble Compability
Open a terminal app on your device and simply type the following command:
getprop ro.treble.enabled
Click to expand...
Click to collapse
If it returns a boolean value true, your device supports Treble and if false it doesn’t.
[NOTE: New devices with Treble support are launching so its not possible for me to update the supported device list, so they'll not make their name on my list, but you can surely ask about your device on the discussion thread]

My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).

AsItLies said:
My understanding of Treble is, from the *big picture* anyway, that the responsibility for hardware access shifts from Google to the individual device mfgs.
The hope for us is that new versions of Android can be distributed much more rapidly, because testing of new hardware (or changes to existing hdw) won't have to wait for the new OS to be done, and that the interface to the hdw will be separate from the OS.
Another hope would be that a devices 'life span' would increase? (or at least stay current longer).
Click to expand...
Click to collapse
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. Now the manufacturers will only require to make the Software bug free so that the user dosent face any problems in day to day usage. From @phhussons AOSP treble rom we can get a clear picture that by separating the vendor source, the Treble based AOSP roms will run on any Treble compatible device regardless of the SOC/hardware configuration.

venom928 said:
Treble means separating the vendor source from the software source, the treble devices will have a separate vendor partition, in which the vendor source will be. <snip>
Click to expand...
Click to collapse
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?

AsItLies said:
Ah yes that makes sense, it's not only the hardware source (vendor specific), it's also the vendors software (their mods and bloatware) that will be in the separate partition.
It really does sound as though this should speed up the time it takes for users to get updates of all kinds. It also seems pretty certain, non-Treble enabled devices will fall by the wayside. Doesn't seem there's any way around that?
Click to expand...
Click to collapse
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition, but OEMs won't do(except some recent flagships) that bcz they want sales of newer devices with Treble support. As far as time is concerned, suppose it takes 2-3months for an OEM to build a fully bug free update, but it will require 3-4weeks for the OEM to build that same update

venom928 said:
For non-treble devices the only way is that the OEMs must release an OTA update which will create a separate Vendor partition
Click to expand...
Click to collapse
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.

AsItLies said:
Yes, it seems the consensus is that mfg's won't risk bricking the phones by doing that kind of an OTA update? We'll see fairly soon what they'll do with the older devices.
It's good that google is calling the shots with this and is insisting new Oreo devices have it. It's bad though that devices just a few months old that cost mucho bucks may go without it.
Click to expand...
Click to collapse
The honor 8 pro got Treble via OTA because it was one of the best selling device, but some OEMs will prefer not to do that so that customers will shift to newer devices. Like OnePlus could have easily added Treble to atleast 5/5T but they thought of not doing it, just depends upon the OEM

venom928 said:
The honor 8 pro got Treble via OTA because it was one of the best selling device
Click to expand...
Click to collapse
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date

AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
yep surely

Mate 9 as well
AsItLies said:
Wow, I did not know that, thanks. I better read more of the Treble threads to keep up to date
Click to expand...
Click to collapse
Mate 9 got treble as well with the Oreo update, major repartitioning as well.

revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Mate 9 is in the list bro, check OP

revjamescarver said:
Mate 9 got treble as well with the Oreo update, major repartitioning as well.
Click to expand...
Click to collapse
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.

AsItLies said:
Thanks Neighbor. Huawei is rapidly moving to the top of my list of phone mfg to buy. It doesn't look like the kirin processors have much los support, but with treble... well, it seems previous prerequisites are being turned upside down.
For sure, when one evaluates (buying) a phone, many factors are relevant. But for most (if not all) of us, how long the phone will stay up to date is probably at the top of that list.
Hope the other mfg's follow Huawei's lead here, else we'll have a lot of recently mfg phones with outdated sftwr soon.
Click to expand...
Click to collapse
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display

venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Very good point. So even with Treble, which SOC (the phone has) will still be relevant in some respects. I have a G6 and think a wide angle lens is da bomb, but could easily do without all the glass 'bling'.

Kirin SoC
venom928 said:
Huawei is the 3rd most fastest growing OEM after Apple and Samsung. What stops me from buying a Honor Device is the Kirin SOC and apps like Google Camera port dosent work on the devices except devices with Snapdragon SOC, so will wait for a device with the specs like the Mi A1 and a 18:9 display
Click to expand...
Click to collapse
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.

revjamescarver said:
Nothing at all wrong with the Kirin SoC, performance is on par with the Qualcomm SoC, only real downfall is that Huawei doesn't sell the Kirin to other oems, otherwise it would be more widespread. The Kirin 970 with its built in NPU and and gigabit LTE modem is going to give the Qualcomm 835/845 a run for their money. Of course the port of the new Google camera app is not going to give you more than the basic functionality as it was written specifically for Google pixel devices (it doesn't give you all the features on older Google or snapdragon devices either), I installed the port on my mate 9 and it was acceptable for basic camera functions but no matter what you do you're never going to get a port of something written for another device to have the same features or performance as the stock app written for your device.
Click to expand...
Click to collapse
I agree that the Kirin Processors are good, and the reason is Kirin is Huawei's home made processor so the pairing between Hardware and Software is perfectly optimisez for better performance and as far as Better Processing is concerned, after Apple Qualcomm holds the 2nd position no doubt, yeah in near future Kirin might surpass Qualcomm interms of performance no idea.
As far as the ported app is concerned I prefer stock android/custom roms over stock roms(MIUI/EMUI) and if someone ports the stock huawei camera for Los/RR running on Huawei devices itself, I'll surely go with a Kirin device but right now thats not available so after installing a custom rom I'll prefer Google camera app, if not the ported one, I'll go with the one available in Apkmirror, though this is my own preference as I'm addicted to using stock android and google apps suite, lets see how much development the Honor 7X gets, if it gets Treble support via OTA I'll go with it else the Mi A1 as of now is my 1st choice

I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year

AsItLies said:
I'm wondering, and the answer may be 'We don't know yet', but...
Many of us have used custom ROM's to avoid using an OEM's UI, bloatware, etc. Because Treble enabled phones will have a 'Vendor' partition (which will include these UI's etc), will that then mean the mfg's specific stuff can't really be (completely) removed the way an after market ROM does?
Of course, there's always ways of disabling mfg stuff, but Roms like Los just do it all in one fell swoop (much easier).
Do we know at this point how this will work with Treble?
Cheers and Happy New Year
Click to expand...
Click to collapse
The SOC source code will reside in the vendor partition, for example The Pixel XL has SD835 so the source code of the SOC will be there in itz Vendor partition. So if you are using a Treble enabled device such as the Huawei Mate 9 which has its own custom UI, if u flash a custom rom on it, the stock OS will get completely removed and the run ROM will run on it.
The Mgf's UI is a part of the system nd not of the vendor partition.

I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!

indigo110 said:
I am planning to buy Honor 7x, I found a thread on 7X forum which has Mount points and partition layout details for 7x. In the details, i can see below line, does this mean that phone supports Treble once updated to Oreo?
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
Orignal thread link
https://forum.xda-developers.com/honor-7x/development/mount-partition-layout-profile-xml-t3727990
Thanks:good: in advance!!
Click to expand...
Click to collapse
It is evident from past experiences that the Honor 7X might get Treble via OTA update as the case was with Honor 8 Pro. The Honor 7X's source code got released a few weeks ago and I got some info that the Open Kirin team will also support the 7X so I guess the Open Kirin team will also release a Treble supported rom

do you think project treble will ever be supported?

So I'm watching the treble news for the galaxy 9 and it's like a knife is turning in my back. I love the s8 hardware but the software, not so much. I have always preferred aosp but I don't like the pixel 2 xl's screen and I want a 2k display so no OnePlus. I hoped that the Oreo update for the s8 will bring project treble support like other OEM's did, but ofc Samsung screwed us one more time before the s9 launch. My question is: do you think that treble will ever come to the s8? Via official update from Samsung? or an xda developer port? :crying:

Because of how the system needs to be repartitioned, the only way to have treble is for the phone to come from the factory with treble set up.

eregev said:
Because of how the system needs to be repartitioned, the only way to have treble is for the phone to come from the factory with treble set up.
Click to expand...
Click to collapse
But phones that launched with nougat and got updated to Oreo support treble. Some Huawei and Sony devices. The essential phone too

vladtdr said:
So I'm watching the treble news for the galaxy 9 and it's like a knife is turning in my back. I love the s8 hardware but the software, not so much. I have always preferred aosp but I don't like the pixel 2 xl's screen and I want a 2k display so no OnePlus. I hoped that the Oreo update for the s8 will bring project treble support like other OEM's did, but ofc Samsung screwed us one more time before the s9 launch. My question is: do you think that treble will ever come to the s8? Via official update from Samsung? or an xda developer port? :crying:
Click to expand...
Click to collapse
I'm very pessimistic when it comes to Samsung and upgrades. There is no money in putting the extra work to bring Project Treble on another "old" phone.
So bad is Samsung software update strategy that I'm on October 2017 Security patch while March 2018 is already out!
(Australian non-branded XSA S8+ here). They haven't even released Oreo update for non-branded phones! These phones are meant to get updates first as they don't require telco "certification".
Having said that all that, I'm sticking to with Samsung as their hardware "just works". If Google released a phone of Samsung quality and with a Samsung AMOLED screen I'd switch in a heartbeat.

samsung probably won't add treble support because there is nothing to gain for them. they'd rather you buy a s9. there's a lot of software-only feature in these phones where they want you to buy new hardware, even thus they could easily do it on the old hardware. but it cost money (effort) and they don't get revenue for it (sales), and they're already one of the leading android phone maker, so they don't have to care. All this make it very unlikely.
community might add it somehow, eventually, who knows. I guess you could interface oreo drivers to wrappers or something like that...

vladtdr said:
But phones that launched with nougat and got updated to Oreo support treble. Some Huawei and Sony devices. The essential phone too
Click to expand...
Click to collapse
Those companies care about its user, samsung on the other hand doesn't.

I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho

I think yes, because google demands companies to do so, and that means if they are going to use google's software, they have to respect their rules. But it probably will be supported after android pie update. At least s9 does support project t.
---------- Post added at 06:32 PM ---------- Previous post was at 06:29 PM ----------
vladtdr said:
I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho
Click to expand...
Click to collapse
I think it is only possible for some devices with non-necesarry but existing special partitions. Redmi note 4 had a special partition for miui to store some specific data. And dev used that partition to bring project treble support. As i know sammy devices don't have any other partition except ordinary ones.

Nope. Not going to happen. It wouldn't help USA Snapdragon devices anyway, as Samsung isn't signing non stock images. For 95XF/FD & 95X0 you can probably fake it, which I'll explain below.
vladtdr said:
I saw that some Xiaomi phones got treble support un oficial( from Devs here on xda) maybe they can do the same for s8? I think the phone has to have a vendor partition tho
Click to expand...
Click to collapse
For exynos and non usa/canada phones only this is possible now, if someone reverse engineers the pit file format, or if the one someone came out with years ago still works.
An easier solution though is to just make hybrid images from existing gsi ROMs. Just open up a gsi image, paste in the vendor from a rom and voila! Samsung already moved all the config files around and simplified /vendor to /system/vendor so this should work just fine. I've been meaning to try but haven't gotten around to it yet

Im willing to try
partcyborg said:
Nope. Not going to happen. It wouldn't help USA Snapdragon devices anyway, as Samsung isn't signing non stock images. For 95XF/FD & 95X0 you can probably fake it, which I'll explain below.
For exynos and non usa/canada phones only this is possible now, if someone reverse engineers the pit file format, or if the one someone came out with years ago still works.
An easier solution though is to just make hybrid images from existing gsi ROMs. Just open up a gsi image, paste in the vendor from a rom and voila! Samsung already moved all the config files around and simplified /vendor to /system/vendor so this should work just fine. I've been meaning to try but haven't gotten around to it yet
Click to expand...
Click to collapse
Im willing to try this out, any chances of bricking my g955f. could you give me a step by step instruction on how to accomplish this seeing as no one seems to want to do this

DalmAsian said:
Im willing to try this out, any chances of bricking my g955f. could you give me a step by step instruction on how to accomplish this seeing as no one seems to want to do this
Click to expand...
Click to collapse
I gave this a shot on a bl unlocked snapdragon a bit ago and had no luck. At least with snapdragon, there is more to it than that.
So no, this isn't something that I or anyone else can give you a set of exact steps to accomplish. There is way too many unknowns to possibly predict them all, as this would up being much more a development/porting project than I suspected.
I still think it's doable for my device, especially after learning a few things through running gsis on a device with full treble support, but it will still take understanding what is happening and being able to make decisions based upon logs and other development practices.