Related
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
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
mariotme said:
Hello guys
May i ask if OmniROM will ever make it to the Xperia Z2 (Sirius)?
Been missing it for ages now
Keep up the great work
Click to expand...
Click to collapse
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Entropy512 said:
I normally just report device requests, but since I've done a lot of the Sony bringups:
I wanted a Z2. I really, really wanted one.
However I don't buy greymarket imports, and Sony refused to sell the Z2 in North America until after the Z3 was launched. Even now, the purchasing link is nearly impossible to find (it is not listed for sale anywhere on sonymobile.com)
Z3 is a possibility if it goes on sale unlocked in North America in a timely fashion. (Which is unlikely...) Z2 is a possibility if some maintainer picks it up, of course, but considering the device's successor is out now, that's pretty unlikely.
Click to expand...
Click to collapse
I totally understand Entropy512! Thanks for your input buddy. Appreciate all your efforts man. Keep it up :good:
Entropy512 said:
I wanted a Z2. I really, really wanted one.
Click to expand...
Click to collapse
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
May I Taste said:
Thanks for your answer, yes that's the best smartphone I've ever got! Why the hell do they think they don't need to sell their devices in america??
As I know you are a major developer of OmniRom, I really hope you will be able to get an Xperia Z4, and hopefully port the ROM on it..
Thanks for your work!:good:
Click to expand...
Click to collapse
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Entropy512 said:
I'll probably skip the Z4 thanks to Sony's crazy 6-month product cycle.
I have a Z3 but so far it's stock. This device is holding a record for the longest I've gone without root/unlocking the BL.
Sony did an awesome job with the stock firmware on the SIM-unlocked Z3.
Click to expand...
Click to collapse
Thanks for your kind answer and I can understand you. It seems however that the Z4 will now last for one year as flagship. Anyway I'll make sure to stay tuned if by chance you work on OmniROM for it.
Have a wonderful year, you and your whole family!
There some unofficial builds for the Sony Sirius floating around...
http://infectedbuilds.net/downloads/sirius/omni_lp/
From my very brief play with it, there's no Cam or NFC but everything else seems pretty useable.
A number of Omni team members are working with the Sony AOSP guys. Short-term it means a lot of things are broken that aren't in CM since Sony AOSP is reworking a bunch of stuff onto a newer unified kernel that will support a large variety of devices. Long-term it'll allow us to support more Sony devices with less effort.
I think one of the guys working this has a sirius... I forget who.
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
mikeysteele said:
I just synced all the Omnirom repos and compiled for the Z2. It works ok, just no Camera, recovery and there seems to be a bug around internal storage, as it thinks there is no space left.
I'd be interested in helping to fix these things, I'm pretty comfortable using git and gerrit and know some Java and C++ but I have no idea where to start.
Code:
adb logcat | grep camera
- waiting for device -
E/CameraService( 373): Could not load camera HAL module
W/ResourcesManager( 1057): Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
I/CameraManagerGlobal( 1057): getCameraService: Reconnecting to camera service
E/CameraService( 373): getCameraVendorTagDescriptor: camera hardware module doesn't exist
W/CameraManagerGlobal( 1057): Failed to set up vendor tags: The camera device is removable and has been disconnected from the Android device, or the camera service has shut down the connection due to a higher-priority access request for the camera device.
So I'd guess I'd have to find out why the camera HAL module can't be loaded?
Click to expand...
Click to collapse
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Entropy512 said:
Camera is far away from being supported. The blobs are completely missing, because they simply won't work with our kernel.
There's work being done, however a lot of it has to be done by someone within Sony and that results in stuff having to go through a legal approval process.
In theory it might be possible with some work to get 5.0 camera blobs working with a lot of kernel hacking, but most people are focusing on a cleaner approach that will take longer and unfortunately has dependencies on Sony's lawyers.
Click to expand...
Click to collapse
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
mikeysteele said:
Thanks for the update. I noticed there weren't any camera blobs in the source, so I assumed it wasn't as simple as just adding them in. I see on github the CM guys hacked their kernel to be able to use the old Jellybean camera blobs which looks painful. Hopefully Sony's lawyers aren't too obstructionist. Although to their credit the Sony stock rom isn't actually too bad. Nothing compared to Omni Rom though.
Click to expand...
Click to collapse
Yeah. They used a kernel backcompat hack, and are using old 4.3 rhine blobs because those are the last ones that were completely 100% DRM-free.
DRM issues have caused all sorts of problems with rhine/shinano cameras ever since 4.4 - Workarounds for many of these have been found, but not all. But the kernel backcompat hacks would still be needed (potentially multiple hacks for each device supported by the Sony AOSP kernel) and that gets nasty.
So the current plan is to have a unified set of sensor drivers in the kernel, with blobs provided as part of the Sony AOSP project. However I think this is going to be easier said than done - it's not just Sony lawyers, but Qualcomm lawyers. It really sucks that the entirety of Qualcomm's mm-camera subsystem is proprietary and there's no way for an opensource developer to write modules for it, which prevents any of the community side of the Sony AOSP project from working on some things. Otherwise it would probably be not too difficult to replace Sony's noise reduction algorithm (likely with a better one... Sony's NR algorithm got slammed for being too aggressive and killing sharpness over in a dpreview review... All that DRM protection for something some people actually prefer to have gone.)
Edit: And yes, Sony's stock firmwares are amazing. My Z3 holds the record for longest I've ever owned a device without even bothering to root it.
Another thing, my phone is the China Mobile version (L50t) and OmniRom runs perfectly on it, I just have to change the radio and wlan firmware. I can supply the required files and be a tester if you wanted to add official support for this varient.
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
If Vulkan API is implemented at our phone it would be fantastic. Hope Asus will work on the API and make the best for our phone, let's see in a couple of months of so
Too good to be true man, too good to be true.
hi, I'm very interested in everything about vulkan since i could see some videos about it. But my knowledge about api, android and rom's is not that good, so i would thank you if i could get some answers.
1 - Is this implementation of API a work for ASUS or Intel?
2 - Since i saw that PowerVR Rogue has now SDK(i dont know what it is) for Vulkan, Is ANYONE able to make a custom rom that could use Vulkan?
3 - I've heard that Android N will have native support for Vulkan. Does it mean that if i download a custom rom, like a cyanogenmod, for Android N to my Zenfone 2 i will have the benefits of using Vulkan?
4 - Does anyone know if that Galasy S7 that had 135k+ on antutu was using Vulkan? Because my Zenfone 2 is a great phone and only scores 65k, it's scary to thing that a S7 should have more than the double of hardware capacity that my Zenfone has. I thing that should be because of vulkan, but i need to hear it from someone who knows what's talking.
I hope to get answers for this questions. Thank you all.
SSJMatt said:
)Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
Click to expand...
Click to collapse
Sorry, that's not how ASUS usually manages fixes and updates. That would take time and money and we've already spent our money so they have nothing to gain, therefore nothing will happen. Only future customers are a priority for ASUS.
A happy ASUS customer is one with low expectations.
Well, at least It'd give Asus a good excuse for being so late...
Vulkan is something that would need to be implemented at the OS level on Android (mainly the kernel, no idea what other bits Google is including in the rest of the OS). And support for each hardware would need to be provided by the OEM or manufacturers. It MAY be possible for a custom ROM to implement Vulkan support in some fashion in a current version of Android (harder and more "impossible" things have been accomplished) but it's not likely due to too many technical challenges. Besides, it wouldn't happen until after Android N is released and the AOSP code is posted. Only then would someone attempt to backport Vulkan.
I'm not 100% sure, but I do believe that Vulkan support will be a requirement by Google for devices to run Android N. So if Asus does plan on upgrading the phones then they will need to include a kernel for the hardware that supports Vulkan and those drivers would come from Intel. So the chance of the Zenfone supporting Vulkan is 100%, provided Asus upgrades it to N.
SSJMatt said:
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
Click to expand...
Click to collapse
So is the VULCAN API present in the M update?
Is Vulkan something like the Mantle for Desktops?
EDIT:
Vulkan Drivers for Nexus Player
Google’s Android Image
As part of the Android N Developer Preview 2 release, Google released an Android N image for the Nexus Player that includes Vulkan drivers. You can find out more about the Android N Developer Preview here and can download the image here. As this image is officially supported by Google, we recommend using it for Vulkan Android development.
Click to expand...
Click to collapse
https://community.imgtec.com/developers/powervr/vulkan/
There is two possibilities:
1- Vulkan added in Android N's mainline code, and CM14 (maybe) will do this too.
2- Vulkan driver will be only in manufacters Android N's source. In this case, will be needed to be backported.
In both possibilites, isnt impossible to do it, even without Asus help. But would be awesome if some official MM give it to us (not in the first version, obviously).
Its GPU manufacturer job to implement vulkan, they provide the drivers to OEM manufacturer implement it on their otas. Nvidia already did that on latest MM update to shield TV and shield tablet.
Google has made it mandatory for devices launched with Android Oreo to have Linux Kernel 4.4 and Project Treble but
Older Android devices released prior to Android O but that will be upgraded to Android O can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
From AOSP/Google (I can't yet put links to source as I don't have 10 posts yet)
Which includes our OnePlus 3T. As OnePlus has already said Android Oreo will be the last major update for our device (officially) we might not get Project Treble (like Nexus 5X and 6P) and Linux kernel 4.4 (a major update from our current 3.18) making it very difficult for the developer community to port future updates as Android P and above might only have Treble base unlike Android Oreo.:crying:
That would be a another bummer after there limited support announcement for 3t. For know I keep my fingers crossed for a better message on this front.
Still if images are released for AOSP you still will get development for our phone though. ?
Goku80 said:
Still if images are released for AOSP you still will get development for our phone though. ?
Click to expand...
Click to collapse
Exactly. Honestly I don't see why Project Treble matters to the average ROM user. I just want my phone to work and perform well and have a decent battery life. Besides that I don't really care. Currently I have a Nexus 6 and just replaced the battery in it but I'm perusing the forums for various devices (this was one of them) that I may be interested in. I want to see how the development community is for each one before I decide. Reason I may be considering this over the OP5 is I have heard bad things about the screen and jelly scrolling.
rjmxtech said:
Honestly I don't see why Project Treble matters to the average ROM user.
Click to expand...
Click to collapse
You don't see why?
Let me help you out:
Ars Technica said:
Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released. On Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.
Click to expand...
Click to collapse
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
I totally agree this !
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Exactly! Development and porting of Custom ROMs will become easier than ever before and porting of future versions of Android will also become way lot easier (if possible at all as future versions of Android might become completely dependent on Project Treble unlike Android Oreo which is compatible with both)! And porting Project Treble is very very difficult if not impossible (unless you are the Silicon Manufacturer) !
So lets together spread the information about the importance of Project Treble and pressure OnePlus to provide Project Treble with #WeWantTreble
We shall Never Settle!
#WeWantTreble
Sent from my ONEPLUS A3003 using XDA Labs
Lets spam Carl Pei twitter with questions regarding this..
(Well not really spam, that would be rude, more like a lot of people asking him same question in shorts period of time)
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
i have red somewhere that pixel devices support treble. Same Soc, should have supported. idk.
From my experience as a Junior Android developer and reading the papers about the project treble, i could say that if there is a little group op3t developers who want this, this can be possible.
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Interesting. But I assume there would still be issues even if they tried to make a universal solution.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
DelicatePanda said:
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
Click to expand...
Click to collapse
Friggin' derp. How did I forget about the Pixel?
That being said, we'd still need to see how its implemented on the Pixel...As far as I know Treble also relies in a specific type of device partitioning which may be problematic for existing device adaptations. The Pixel phones already used the /vendor partition how it's supposed to be used so adapting Treble is almost a non-issue. I don't think our phone uses the same partition layout.
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
DelicatePanda said:
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
Click to expand...
Click to collapse
That sucks .. even for OnePlus 5?
why the heck Carl is not replying officially on it, anywhere???
So i know that everybody has been requesting that camera 2 API to be enabled by default. There have been multiple requests made to Xiaomi from social (mainly twitter) to MI forums and even in Google bug tracker to request the feature to be enabled in the next OTA. Thankfully one of Google employees asked their DEV teams directly and this is the response he got :
vi.. @google.com <vi.. @google.com> #9 Nov 2, 2018 05:44AM
Please find the below comment received from our development team:
"We continually talk with various Android manufacturers about camera quality and work to improve performance and features available to camera applications across the Android ecosystem. Starting with Android Pie, newly launching devices are expected to have newer camera HAL versions, which will enable better support for camera2."
Bug tracker issuetracker.google.com/issues/117853983 link
Thanks for the effort everyone :highfive:
We did it
I fail to see where the "confirmation" for the Mi A2 is , baited and outsmarted
Let's hope the A2 is included in "newly launching devices"
bartoloandre98 said:
I fail to see where the "confirmation" for the Mi A2 is , baited and outsmarted
Click to expand...
Click to collapse
In the issue tracker, the response was to this thread ( Mi A2 Camera2 API support request )
Now we just need fingerprint gestures....
obilisk said:
So i know that everybody has been requesting that camera 2 API to be enabled by default. There have been multiple requests made to Xiaomi from social (mainly twitter) to MI forums and even in Google bug tracker to request the feature to be enabled in the next OTA. Thankfully one of Google employees asked their DEV teams directly and this is the response he got :
vi.. @google.com <vi.. @google.com> #9 Nov 2, 2018 05:44AM
Please find the below comment received from our development team:
"We continually talk with various Android manufacturers about camera quality and work to improve performance and features available to camera applications across the Android ecosystem. Starting with Android Pie, newly launching devices are expected to have newer camera HAL versions, which will enable better support for camera2."
Bug tracker issuetracker.google.com/issues/117853983 link
Thanks for the effort everyone :highfive:
We did it
Click to expand...
Click to collapse
aww man it's a really great news now people see the power of mia2 Camera ? #Sonyimx486
But I already unlocked enabled camera2api with no OTA update loss. It's great news though!
[email protected] said:
But I already unlocked enabled camera2api with no OTA update loss. It's great news though!
Click to expand...
Click to collapse
Great Brother But i don't want to unlock now?
Sohailsamdani said:
Great Brother But i don't want to unlock now?
Click to expand...
Click to collapse
Good news for you then! Hope we get the pie update soon
hope that also brings with it the arcore support.
Sorry but this is neither a confirmation nor proof we will see this enabled by default. Xiaomi will simply tell us that the A2 didn't launch with PIe so we dont give a *
Benjamin_L said:
Sorry but this is neither a confirmation nor proof we will see this enabled by default. Xiaomi will simply tell us that the A2 didn't launch with PIe so we dont give a *
Click to expand...
Click to collapse
Sohailsamdani said:
Great Brother But i don't want to unlock now?
Click to expand...
Click to collapse
Same here man ?
Benjamin_L said:
Sorry but this is neither a confirmation nor proof we will see this enabled by default. Xiaomi will simply tell us that the A2 didn't launch with PIe so we dont give a *
Click to expand...
Click to collapse
Absolutely, in my opinion this is gonna happen, but also we don't lose anything keeping the hope
IjazCI said:
They never did it for Mi A1 despite being an android one device.
Don't keep your hope's high.
Click to expand...
Click to collapse
A1 didn't get pie though yet so we'll have to wait and see. But it's Xiaomi after all..
this thread is click bait
Well I have the Pie update for the Mi A2, and tried to installed the lastest apk from CelsoAzevedo, and it didn't work. Keep stopping. So I guess they didn't enabled it yet.
I updated my mi max 3 to android pie . unfortunately camera 2 api is not enabled.
this thread needs to be closed.