Related
why on earth did they not launch this phone with Kitkat?
anyway I have a question regarding Oppo's software support, is it good? will they quickly update Find 7 to Kitkat? I have heard that Oppo's software are rather somewhat unreliable, is it true?
about Color OS, is it good? is it full of bloatwares or not? how deep is the customization?
will Find 7 have official Cyanogenmod support? how about other custom ROMs?
thanks for answering!
Oppo listen very much to their user base and they will update it to KitKat. You can flash other roms to Oppo using their stock recovery, they're partnered with CyanogenMod so Cm roms should run well on their devices.
As for other custom roms, it depended on if the Dev want to develop for it or not, if you purchase a Find 7 for them, they probably will. Hint: Take a look at the Find 5 and N1 development section.
sent via tapatalk
The oppo stock recovery flashes CM. OPPO are developer friendly,they even got OMNI Mediatek sources for the R819 (not an easy feat Mediatek are NOT willing)
They did not launch with kitkat because they are still adding features (ColorOS 2.0). They do that. If you are concerned about latest android version get on a custom rom like CM from the start,because OPPO don't move up the Android version until the previous ROM is stable enough to discontinue. The ROM itself is quite nice for a manufacturer skin,not bloated at all,and has some nice features built in you really miss if you go custom,but some people just hate the colorfulness so to each their own.
Allanitomwesh said:
The oppo stock recovery flashes CM. OPPO are developer friendly,they even got OMNI Mediatek sources for the R819 (not an easy feat Mediatek are NOT willing)
They did not launch with kitkat because they are still adding features (ColorOS 2.0). They do that. If you are concerned about latest android version get on a custom rom like CM from the start,because OPPO don't move up the Android version until the previous ROM is stable enough to discontinue. The ROM itself is quite nice for a manufacturer skin,not bloated at all,and has some nice features built in you really miss if you go custom,but some people just hate the colorfulness so to each their own.
Click to expand...
Click to collapse
Did you say I can just use CM from the start even without proper official version? how? which version?
nap007 said:
Did you say I can just use CM from the start even without proper official version? how? which version?
Click to expand...
Click to collapse
CM will probably have builds out within a month of release...
My concern with running CM on this phone is, will it lose features? Like the 50MP super zoom mode?
Yes you'll most likely lose SuperZoom and Maxxaudio with any AOSP ROM. You'd need stock based for that.
Allanitomwesh said:
Yes you'll most likely lose SuperZoom and Maxxaudio with any AOSP ROM. You'd need stock based for that.
Click to expand...
Click to collapse
what? but didn't n1 retain it's features with cyanogen?
and can't you just install specific phones apps to get it's features?
Yes, because CM built the phone with OPPO,far as I know,they're making the OnePlus One ATM. So yeah, it'll be like on Find 5 most likely.
seriousneo said:
CM will probably have builds out within a month of release...
Click to expand...
Click to collapse
I haven't heard any news regarding a Cyngn partnership for the Find 7.
Remember, after last year's events, when talking about CM, there are really two different entities which are semi-connected:
CM - the original CyanogenMod open source software project. The Find5 was originally maintained by community members who were solely involved on this side of things. All of that team left for Omni as a result of the Focal relicensing fiasco (This is why the Find5 never saw official CM10.2)
Cyanogen Inc - Referred to from here on in this post as "Cyngn" - The corporate entity created by some of the Cyanogenmod leads
Cyngn was partnered with Oppo for the N1 so that Cyngn could gain experience with taking a device through GMS (Google Apps) certification. There has been little to no CM community involvement with the N1 - it's a purely Cyngn affair. All community efforts on the device are focused on other projects (Oppo sent preproduction N1s to people involved with CodefireXperiment, Omni, Paranoid Android, and a few others)
Cyngn is currently partnered with OnePlus to focus on their launch device. They aren't even putting much effort into the N1 now if you read any of the user reviews. (Both official 10.2 updates are full of bugs, and CM11 has had broken location services for two months now with not a single word from the development team.)
So the support of the Find7 by CyanogenMod is unknown and indeterminate. It will likely involve community effort if it happens, but all "community" contributors with current Oppo devices are working on other projects. Omni support is HIGHLY likely, I would not be surprised if, like the Find5 and N1, it proves to be one of Omni's best supported devices. CodefireXperiment and PA support are also highly likely (Actually I'd say pretty much guaranteed in the case of CFX, Oppo and Anders get along as well as the Omni team gets along with Oppo). (While PA usually focuses on Nexus devices, there usually have been exceptions for Oppos due to Oppo providing excellent support to Aaron from PA.)
Its the best phone out without a doubt right now .. Might even beat all new HTC one .. It's a no compromise phone .. Except speakers idk if they are good or bad .. Also you can choose your own software oppo skin or cm(later) and paranoidandroid. I'm very impressed .
returning to the color os talk, do you think it will be a long time before oppo move to kitkat based color os?
and as I asked before, is it true regarding color os instability and incompatibility with common android apps?
and I'm glad if Paranoid Android will indeed come to Find 7!
nap007 said:
returning to the color os talk, do you think it will be a long time before oppo move to kitkat based color os?
and as I asked before, is it true regarding color os instability and incompatibility with common android apps?
and I'm glad if Paranoid Android will indeed come to Find 7!
Click to expand...
Click to collapse
About the apps yeah,there was a thing about Lightflow not working,but its usually a one app thing,especially if it works by identifying the phone,mostly coz OPPO is so unique. As a plus ANY Chinese app works without a hitch when they give other manufacturers incompatibility issues
Omni is confirmed,Maxwen is getting a Find 7.
Unless i'm wrong ColorOS 2.0 should be kitkat.
CHlCKEN said:
Its the best phone out without a doubt right now .. Might even beat all new HTC one .. It's a no compromise phone .. Except speakers idk if they are good or bad .. Also you can choose your own software oppo skin or cm(later) and paranoidandroid. I'm very impressed .
Click to expand...
Click to collapse
Well I would consider the battery a moderate compromise. 3k mah is not really sufficient for a 5.5" 2k screen. I was really hoping for 3500mah or more.
I'm wondering how the screen compares to the Note 3 OLED screen. The Note 3 has an extra .02", extra 200mah, but Samsungs OLED's aren't as efficient as SLCD's.
The batt life is the defining factor here for me and I would assume a great many others. If HTC can deliver on this, they'll take a good few percent of the upgrade market. Damn Sony for not bringing their Z2 to the US. It would dominate the tech-savvy market completely.
last time I heard the screen use new low power tech so let's wait for a review first before calling the battery is a flop.
mhl, hdmi?
Does anyone know of any video output port on this device such as HDMI or MHL or any other?
Wyzco said:
Does anyone know of any video output port on this device such as HDMI or MHL or any other?
Click to expand...
Click to collapse
likely not but during the unveiling they used a find 7 to output audio using huge cable, maybe it was just a huge stereo cable though.
I heard the lower-end version Oppo Find 7a is better than Oppo Find 7 in many sectors, like screen, performance, etc. I really hope that Oppo equips this phone with that brilliant touch-less voice command just like on Moto X. It's gonna be really awesome for this phone. In fact, i think all of the new phones in 2014 should also have this feature. I mean, the real touch-less voice control when the phone is still locked. Unlike Google Nexus 5's "Ok Google" voice control that can only be used when the phone has been unlocked.
nap007 said:
likely not but during the unveiling they used a find 7 to output audio using huge cable, maybe it was just a huge stereo cable though.
Click to expand...
Click to collapse
Really??? You're telling me about Audio output?
Every phone has that! Smh
nap007 said:
likely not but during the unveiling they used a find 7 to output audio using huge cable, maybe it was just a huge stereo cable though.
Click to expand...
Click to collapse
Supports a bunch of wireless outputs
DLNA and Miracast off the top of my head,and Wifi Display
I have asked this question elsewhere but didn't get an answer so I'm trying here.
I've had 3 generations of Samsungs and I really want to switch to something different, possibly the LG G3. What would really convince me is if I could reasonably anticipate a rock solid AOSP ROM for it at some point in the future. I'm sick of Samsungs bulky and laggy Touchwiz, and I've fallen in love with the pure Google experience that AOSP roms offer; but while they work OK on the Samsung, they suffer from a drop in quality and performance because I am told Samsung drivers are not open source and they have to use open source alternatives.
I've noticed that LG have an open source code distribution page with software for phones on it. Now I'm no developer, so the question I am asking is - do LG release their code open source? And does this mean that original developers are able to drive the LG hardware properly? What were AOSP roms like for the G2?
astralbee said:
I have asked this question elsewhere but didn't get an answer so I'm trying here.
I've had 3 generations of Samsungs and I really want to switch to something different, possibly the LG G3. What would really convince me is if I could reasonably anticipate a rock solid AOSP ROM for it at some point in the future. I'm sick of Samsungs bulky and laggy Touchwiz, and I've fallen in love with the pure Google experience that AOSP roms offer; but while they work OK on the Samsung, they suffer from a drop in quality and performance because I am told Samsung drivers are not open source and they have to use open source alternatives.
I've noticed that LG have an open source code distribution page with software for phones on it. Now I'm no developer, so the question I am asking is - do LG release their code open source? And does this mean that original developers are able to drive the LG hardware properly? What were AOSP roms like for the G2?
Click to expand...
Click to collapse
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc
hello00 said:
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc
Click to expand...
Click to collapse
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!
astralbee said:
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!
Click to expand...
Click to collapse
I was also wondering about this. On the Htc one xl the aosp camera was significantly worse than the sense one.
Is there any way to know if when the g3 gets aosp there will be any driver issues? The g3 on paper seems absolutely fantastic but the possibility of no aosp or aosp with less functionality is terrifying to me.
I wish there was a GPE version of the G3.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
astralbee said:
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!
Click to expand...
Click to collapse
I THINK a lot of code is shared from these manufacturers but camera stuff may not be on that list . Just got the LG G3 yesterday and i don't like it at all besides the camera , finding it kinda laggy in comparison to N5 ( if u use the resents button a lot u'll notice ) and its not the same build quality as my G2 , feels cheaper to me . I'm a fan of AOSP, all my devices have some form of it, this G3 may be going back to the store for a new M8 its pretty easy convert to full GPE . and i love my M7
hello00 said:
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc
Click to expand...
Click to collapse
Where can I download the AOSP builds for g3? If they don't exist, where will I go to find them when they do exist?
Thanks!
distancesprinter said:
Where can I download the AOSP builds for g3? If they don't exist, where will I go to find them when they do exist?
Thanks!
Click to expand...
Click to collapse
They don't exist yet. From what I understand the boot loader hasn't even been unlocked yet. I guess there are people working on it tho. As far as where you can find the builds, they'll be here on XDA, either in the Android Development section of this G3 forum, or in the carrier specific G3 sections (which have yet to be created).
Never mind, I guess they just created the carrier threads.....
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.
Source already available
We should wait for devs to build it ?
AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.
Yap, waiting for you too @joel.maxuel for working on it
allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.
Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0
Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk
The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,
So I was all up and ready to buy a Moto G5 plus and then saw the Honor 8 Pro will be out soon. Everything about it looks great - The display (isn't amoled - thankfully!) and the size, the Kirin 960 looks like it competes with the Snapdragon 835 in many ways. And the price of course is very reasonable.
I'll be coming from the Nexus 5 so I've been in and around XDA a long time, flashing ROMs etc. I don't expect the Honor 8 Pro to be anywhere near as Dev friendly as the Nexus 5. But I was wondering if anyone can tell me what it's actually like for Devs with Huawei phones and getting hold of the sources needed to make custom ROMs or even get LineageOS and all the hardware working? I get the sense (but I'm not sure) that at the moment it's a *real* challenge because Huawei, like most manufacturers don't really believe that engaging with the Dev community can provide a great boost to brand visibility and "geek cred" which will then filter out into recommendations to friends and family etc: It can be a very strong marketing tool essentially. But companies rarely understand that it would actually benefit them in a business sense. So...
Do Huawei provide all the "sources" and resources needed for developing custom ROMs *eventually* or do they just not bother at all in some cases or make it very hard in others? I saw on a Honor 8 (not pro) thread that there are "ambassadors" around. Can these guys interact with Huawei/Honor to encourage them to help out with the necessary technical stuff to make building ROMs a viable possibility, and is that likely to get a good response or is it already in process?
I mean if I get the Honor 8 Pro, I'll use it "as is". EMUI is not bad but still quite amateurish/90s in many ways and I'm thinking I can go along way to fixing it by using a custom launcher. But if there's a good chance Honor/Huawei will suddenly become much more helpful with Dev stuff it would make it a dream phone for sure. Any info?
I've been looking in to this too. It seems you can unlock the bootloader on EMUI devices in an official way so that's a good start.
Have you had a look around the other Huawei and Honor forums? There do seem to be ROMs and unofficial Lineage OS builds, but I haven't found much info on sources, etc.
I have actually pre-ordered an Honor 8 Pro, it looks awesome and at £474 I couldn't resist. I think the major manufacturers have lost the plot in terms of flagship pricing.
alsheron said:
So I was all up and ready to buy a Moto G5 plus and then saw the Honor 8 Pro will be out soon. Everything about it looks great - The display (isn't amoled - thankfully!) and the size, the Kirin 960 looks like it competes with the Snapdragon 835 in many ways. And the price of course is very reasonable.
I'll be coming from the Nexus 5 so I've been in and around XDA a long time, flashing ROMs etc. I don't expect the Honor 8 Pro to be anywhere near as Dev friendly as the Nexus 5. But I was wondering if anyone can tell me what it's actually like for Devs with Huawei phones and getting hold of the sources needed to make custom ROMs or even get LineageOS and all the hardware working? I get the sense (but I'm not sure) that at the moment it's a *real* challenge because Huawei, like most manufacturers don't really believe that engaging with the Dev community can provide a great boost to brand visibility and "geek cred" which will then filter out into recommendations to friends and family etc: It can be a very strong marketing tool essentially. But companies rarely understand that it would actually benefit them in a business sense. So...
Do Huawei provide all the "sources" and resources needed for developing custom ROMs *eventually* or do they just not bother at all in some cases or make it very hard in others? I saw on a Honor 8 (not pro) thread that there are "ambassadors" around. Can these guys interact with Huawei/Honor to encourage them to help out with the necessary technical stuff to make building ROMs a viable possibility, and is that likely to get a good response or is it already in process?
I mean if I get the Honor 8 Pro, I'll use it "as is". EMUI is not bad but still quite amateurish/90s in many ways and I'm thinking I can go along way to fixing it by using a custom launcher. But if there's a good chance Honor/Huawei will suddenly become much more helpful with Dev stuff it would make it a dream phone for sure. Any info?
Click to expand...
Click to collapse
I'm in the same boat. I love the H8Pro but all I see outside of stock based roms, is one unofficial Lineage build for the Honor 8. The camera is currently listed as not working still. It's like that on a lot of phones that aren't too well known. My Le Pro 3 for example didn't have working camera on the marshmallow roms for a while and then when they got it working the 7 roms didn't have it until very recently. So it's a maybe it will at all. The problem is that while a lot of these companies allow bootloader unlocking, no they don't release sources. That's a big problem. That means devs have to build things like camera drivers from scratch, and without them being that popular devs working on it aren't usually too plentiful. Also not too much kernel support for that Kirin chipset either.
Well let me ask you guys. How much custom ROMs do you use these days ? I myself found that after changing to custom ROM I found back to stock ROM. These days stock roms has become so good that they actually brings the true character of a phone
Apparently I'm not the only one facing this decision. I've owned the Moto 2nd gen, G3, and G4 and frankly every time I've moved up a model, I like them a little less. For that reason alone, I'm trying to look past the Moto G5. Now that the Honor 9 is coming out, I'm taking a look at the Honor 8, hoping the cost will come down. I've always carried my phone in my front pocket so the size difference over the G4 I have now has me a little worried, but the weight really doesn't matter. I'm really looking very hard at the Honor 8 Pro though since price wise, it looks pretty close to the best bang for the buck.
ehh ..
alsheron said:
So I was all up and ready to buy a Moto G5 plus and then saw the Honor 8 Pro will be out soon. Everything about it looks great - The display (isn't amoled - thankfully!) and the size, the Kirin 960 looks like it competes with the Snapdragon 835 in many ways. And the price of course is very reasonable.
I'll be coming from the Nexus 5 so I've been in and around XDA a long time, flashing ROMs etc. I don't expect the Honor 8 Pro to be anywhere near as Dev friendly as the Nexus 5. But I was wondering if anyone can tell me what it's actually like for Devs with Huawei phones and getting hold of the sources needed to make custom ROMs or even get LineageOS and all the hardware working? I get the sense (but I'm not sure) that at the moment it's a *real* challenge because Huawei, like most manufacturers don't really believe that engaging with the Dev community can provide a great boost to brand visibility and "geek cred" which will then filter out into recommendations to friends and family etc: It can be a very strong marketing tool essentially. But companies rarely understand that it would actually benefit them in a business sense. So...
Do Huawei provide all the "sources" and resources needed for developing custom ROMs *eventually* or do they just not bother at all in some cases or make it very hard in others? I saw on a Honor 8 (not pro) thread that there are "ambassadors" around. Can these guys interact with Huawei/Honor to encourage them to help out with the necessary technical stuff to make building ROMs a viable possibility, and is that likely to get a good response or is it already in process?
I mean if I get the Honor 8 Pro, I'll use it "as is". EMUI is not bad but still quite amateurish/90s in many ways and I'm thinking I can go along way to fixing it by using a custom launcher. But if there's a good chance Honor/Huawei will suddenly become much more helpful with Dev stuff it would make it a dream phone for sure. Any info?
Click to expand...
Click to collapse
personally, i am a fan of their emui5, amazing ui tho,
and their harware is solid,
camera is good too,
battery lives are excellent (thanks to emui optimisations)
but my only regret is that i dont have much of a custom roms to play with, given that their kirin chip is not open sourced
offcourse, their is open kirin team unofficially, but they are not working on every device, so only complaint will be kernel sources,
many honor devices has no development at all,
thilak devraj said:
personally, i am a fan of their emui5, amazing ui tho,
and their harware is solid,
camera is good too,
battery lives are excellent (thanks to emui optimisations)
but my only regret is that i dont have much of a custom roms to play with, given that their kirin chip is not open sourced
offcourse, their is open kirin team unofficially, but they are not working on every device, so only complaint will be kernel sources,
many honor devices has no development at all,
Click to expand...
Click to collapse
1. kernel source from p10 plus works on duk
2. resurrection remix will follow soon .. it is booting already, but still has some major bugs we have to fix first
EDIT: I just saw you are talking about kirin devices in general, sorry
OldDroid said:
1. kernel source from p10 plus works on duk
2. resurrection remix will follow soon .. it is booting already, but still has some major bugs we have to fix first
EDIT: I just saw you are talking about kirin devices in general, sorry
Click to expand...
Click to collapse
don't worry, we are always greatfull for open Kirin and the hard work of devs like you
Source code is just released! Check HERE. Since the phone is new, source is released early. OpenKirin Team can now develop for this device.
adriansticoid said:
Source code is just released! Check HERE. Since the phone is new, source is released early. OpenKirin Team can now develop for this device.
Click to expand...
Click to collapse
wooow... source released ?? :cyclops:
thilak devraj said:
wooow... source released ?? :cyclops:
Click to expand...
Click to collapse
Yeah. That's what I just said.
adriansticoid said:
Yeah. That's what I just said.
Click to expand...
Click to collapse
wasnt expecting huawei to do this
thilak devraj said:
wasnt expecting huawei to do this
Click to expand...
Click to collapse
Rox_Honor said it will be released mid-June. A bit delayed but it's good.
adriansticoid said:
Rox_Honor said it will be released mid-June. A bit delayed but it's good.
Click to expand...
Click to collapse
finally, i could play with custom roms , hope it woud happen for the 6x too
thilak devraj said:
finally, i could play with custom roms , hope it woud happen for the 6x too
Click to expand...
Click to collapse
Yeah. Everybody's hoping for that.
adriansticoid said:
Yeah. Everybody's hoping for that.
Click to expand...
Click to collapse
imagin , if huawei bedev friendly, and their phones will be like snapdragons, no one would stop em
thilak devraj said:
imagin , if huawei bedev friendly, and their phones will be like snapdragons, no one would stop em
Click to expand...
Click to collapse
They'll see this in the future. Yeah that future again.
adriansticoid said:
They'll see this in the future. Yeah that future again.
Click to expand...
Click to collapse
if that happens, huawei's gonna beat sam
thilak devraj said:
if that happens, huawei's gonna beat sam
Click to expand...
Click to collapse
Of course. So it's important that they decide for this.
Hi.
I'm using EU MIUI 7.3.30 and it's not bad, but I would much prefer using a non-MIUI ROM such a LineageOS.
However, all the AOSP variants using the stock kernel (LOS,RR...) until now have had mediocre to faulty camera implementations and I've tested many camera apps at that - Piximod mark IV, stock LOS, stock RR, Google camera, a better camera, open camera, manual camera... None of them are able to hold a candle to the stock camera app under MIUI in terms of having everything (video,RAW,HDR,panorama...) working flawlessly under one app.
I'm not even sure if this will change now that we have the released kernel for the mi5s, so please help me understand the following:
1. Does having the released kernel potentially help in getting a better camera experience under LOS, RR or a similar ROM versus using the stock kernel from MIUI? How so?
2. Does having the released kernel potentially help in porting the stock MIUI camera app under LOS/RR?
3. Does having the released kernel potentially help in getting a *better* camera implementation than currently under stock camera app MIUI by better utilizing the camera2API (from my understanding the stock camera app in MIUI doesn't use V2 of the camera API)?
4. Does having the released kernel potentially allow one to port the Pixel camera app?
Thanks all
I think you should create this thread into the Question & Answer Section.
But for your question regarding the kernels and implementation for los / rr, yes indeed it'll help for dev to use new released kernel from xiaomi, since the kernel is made specifically for mi5s hardware optimization and function.
Yes and yes, the bottom line is the kernel will give us huge advantage rather than use stock kernel like we use right now if we use los / rr, for the camera of course there will be some improvements, not only the camera, fingerprint, ambient display, multi touch, etc will improve.
As far as I understand the source doesnt contain every information.
Open source sounds cool yeah. But take Amazons FireTV as an example. There is a source code available because of GPL, however they only share the source of the stuff they have to share and nothing else. So source doesnt mean, the source code of everything.
As a better example you can take the Google Pixel. You would expect that the VERY Android device itself should have source code of everything available. Like the Google Camera Software and algorithm that could be used for the Mi5S since both share the same Sony Sensor. Sounds awesome right? Sadly Google, doesn't share this particular piece of source code/drivers.
And when I talked with LuK about source, he was not very optimistic. It is because the Qualcomm Fingerprint reader is also closed. Which is why he said "Qfp will still be a mess"
So.. Long story short. It will still be a custom rom with its disadvantages. But I believe that it will contribute a lot in terms of stability. Phone calling , no force closes and sudden reboots.
I mean after all these years on xda , everyone should already got used to "everything works. Stable build. not working : camera etc"
This will not change I think. In fact it will get more complicated and the list of troublesome things will get longer as phones get more and more features with closed source. Fingerprint reader is such a thing for instance. and More advanced sensors in the future etc..
So there are two options:
1) Either you stick with your current phone and try to make it work and live with its downsides. Maybe after 3 to 5 years, almost everything will be supported or maybe not. Although by then the phone will most likely be obsolete and any 100$ phone will beat it.
Go back 5 years. Would you still bother with a Samsung Galaxy S2 or S3?
2) Just get a phone that has proper company support from the start and use the phone at its full potential right away. Like the Google Pixel. However it costs more. So you have to weigh the Pros and Cons. Do you want to spend more money or more time and headaches. Everyone has to make a decision there.
As for me: I know that I drop and break expensive stuff. So I buy cheap phones. xD