Related
I hope this post does not get too long and you bear with me...
This idea came to me recently - thinking about ICS and what the vendors are calling "legacy" devices. I even started a thread at qualcomm developer forum, asking them nicely to give us the needed binaries, or even better source code for the user space drivers. I really doubt that it will happen, but it does not cost much to try.
Anyway - here is the idea - instead of begging the vendors to release the source (or binaries, or unlock the bootloaders) lets give them an incentive to do so by introducing community (XDA) certified devices. We could come up with lets say 3 levels of community compliance for the devices - with grades:
A - the vendor has made it possible to unlock the bootloader of the device
A+ - the vendor has made binaries needed for compiling AOSP, Cyanogenmod and other open source projects for the device available and made the bootloader unlock-able
A++ - the vendor has released source code and binary drivers for all of the hardware components of the device, and made the bootloader unlock-able
A committee of recognized developers and community members (I am thinking guys like tytung, texasice, azrienoch, etc... - do not feel left out guys) - would receive sample devices from the manufacturers to test and certify the level of community compliance.
A special section of the XDA site would be set up showcasing the community certified devices, and ad space on the portal would be dedicated to showcase latest devices to recieve certification.
Heck, the community could even make money - by allowing (selling the right to) the vendor of the certified device to put an XDA certified device on the packaging or on the device itself (the money could be used to help support the website costs or fund development projects - bounties and such...)
It may sound like a lot work, but this way we could allow the community friendly vendors to get a chance to show their devices, and smaller vendors trying to ways to differentiate themselves could find a fast-track to the hearts of enthusiasts. The community members looking for a new device would make their minds easily by browsing the certified devices section.
I know I would participate in a program like this (Samsung if you are reading this I am willing to certify the N7000 right now - please PM me so I can send you my address)
It's a cool idea, but I think it's a tough sell to device makers.
If we get the community on-board, the vendors will come by themselves.
If the community showcases these devices, and the community members buy devices based on these grades - the vendors will want to come on board.
The vendors like Xiaomi and Meizu could be the first to be interested in this type of publicity - and this is really the type of vendors we should try to get interested.
Once the smaller ones are in, the bigger ones are sure to follow
But community awareness is the first step - we need to choose for ourselves and recommend to others devices that already fall into this category - like SE and HTC devices that are already bootloader unlock-able, and to not buy and not recommend devices like the locked-down Motorola's.
srle said:
If we get the community on-board, the vendors will come by themselves.
If the community showcases these devices, and the community members buy devices based on these grades - the vendors will want to come on board.
The vendors like Xiaomi and Meizu could be the first to be interested in this type of publicity - and this is really the type of vendors we should try to get interested.
Once the smaller ones are in, the bigger ones are sure to follow
But community awareness is the first step - we need to choose for ourselves and recommend to others devices that already fall into this category - like SE and HTC devices that are already bootloader unlock-able, and to not buy and not recommend devices like the locked-down Motorola's.
Click to expand...
Click to collapse
This will be hard to do as each OEM will need to get all the source from other manufacturers and they will never release the source for their drivers. Not to mention alot of peoples choice on buying a device is the price from their carriers. The carriers won't jump on board as any Modding voids warrenty and they will refuse to support it. Not to mention their stand on how not everyone should have access to certain things. (Can't say I disagree with them). Then you mentioned the MIUI phone. They won't get far as alot of people are upset they stole most of the coding from CM and are now trying to make money off of it. Not cool. Don't get me wrong I would love to see an XDA approved phone. Just don't see the OEMs having any interest as there will not be as much money to be made and in the end that is all they care about. Besides once Samsung finishes buying MIUI then that will be a proprietary os. They already have CM. Notice the bot went down shortly afterwards? Odd? Just a little lol
I would not worry a lot about that - the Apache 2.0 licence allow reuse of code in closed source projects - it's a choice Google and OHA made.
Project and ROM makers will come and go - today it's Cyanogenmod, tomorrow it will be someone else with a different project (think WebOS on our Android devices). The point here is to have an option to buy a device that's free to be modified and free to support which ever OS the community decides to run on it (maybe some new version of Ubuntu even).
Phones are also only a part of this problem (and the part that's dependent on carriers) - there are also tablets and probably media players to consider here.
I think that this certification could help the vendors and even carriers which want to stand out and show that they are different by giving them means to do so. In the end, even subsidized devices are payed by you - and not the carrier, so you should have a choice to do what ever you want with it.
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Does the noise reduction of the camera is supported ?
snaky90 said:
Does the noise reduction of the camera is supported ?
Click to expand...
Click to collapse
For now there is no camera
br
J
jerpelea said:
For now there is no camera
br
J
Click to expand...
Click to collapse
Hmm, not having a camera is really bad =/
I mean, the Sony's Android™ Concept has a working camera right?
I guess we will have to wait until there is a workign camera!
There is any road map for camera release?
It would really help custom ROMs and etc!
Thanks
jerpelea said:
Sony Mobile is committed to supporting the open developer community,
Click to expand...
Click to collapse
It would be great to have some news regarding the project, as mentioned above.
Or, maybe a clear outline on what Sony is willing to deliver and what not.
As open device project has been active for a year now for this device at least.
And even though aosp source is fairly stable, there is no camera nor a workaround until a proper fix takes place.
It would be nice if Sony can show they are committed with the project,
As now it seems like they are not very committed and are relying mainly on volunteers to extend functionality: http://developer.sonymobile.com/2015/02/25/could-you-be-our-next-hero-open-source-developer/
Not having camera available is disheartening, since one of the attractions of choosing Sony is the camera. All the way back to Sony walkman phone and X10mini pro - Sony had a good camera.
And one of the reasons for choosing a z3-compact was the announcement of the Sony open developer project, but it had been almost a year without camera.
The worst thing is that Sony camera sensors are being used on devices not made by Sony showing better results, (Motorola , Samsung, even iPhone use them)
m0d said:
It would be great to have some news regarding the project, as mentioned above.
Or, maybe a clear outline on what Sony is willing to deliver and what not.
As open device project has been active for a year now for this device at least.
And even though aosp source is fairly stable, there is no camera nor a workaround until a proper fix takes place.
It would be nice if Sony can show they are committed with the project,
As now it seems like they are not very committed and are relying mainly on volunteers to extend functionality: http://developer.sonymobile.com/2015/02/25/could-you-be-our-next-hero-open-source-developer/
Not having camera available is disheartening, since one of the attractions of choosing Sony is the camera. All the way back to Sony walkman phone and X10mini pro - Sony had a good camera.
And one of the reasons for choosing a z3-compact was the announcement of the Sony open developer project, but it had been almost a year without camera.
The worst thing is that Sony camera sensors are being used on devices not made by Sony showing better results, (Motorola , Samsung, even iPhone use them)
Click to expand...
Click to collapse
The article you linked is an initiative to get people excited about development and help out. Sony's open source team (and many other volunteers who do not mind contributing, because that's the essence of open source) are working on fixes and workarounds, but on the outside, the usual "Soon™" sign is visible, as it always is with developers (check, for example, the AOSPA team).
As for the camera, many people find it lackluster even on stock ROMs. Camera performance, however, has nothing to do with what your expectations should be (not what they are, because that's clearly a wholly different thing) regarding the AOSP project Sony has going on -- the goal of the initiative is to provide a working AOSP base similar to that of Nexus devices (though in more than one way, the Sony team responsible for this has far exceeded that goal). This does not mean that things will just work (quite the contrary, really). When you bought the device, the Open Developer project should not have been a reason to be excited about the end result of the developers' efforts, but rather a sign of encouragement that you should contribute, and are indeed welcome to do so.
tl;dr: this project, like the rest of XDA, isn't about the goal, but about the journey. (except for maybe the new bootloaders but that's another thing)
someone755 said:
The article you linked is an initiative to get people excited about development and help out. Sony's open source team (and many other volunteers who do not mind contributing, because that's the essence of open source) are working on fixes and workarounds, but on the outside, the usual "Soon™" sign is visible, as it always is with developers (check, for example, the AOSPA team).
As for the camera, many people find it lackluster even on stock ROMs. Camera performance, however, has nothing to do with what your expectations should be (not what they are, because that's clearly a wholly different thing) regarding the AOSP project Sony has going on -- the goal of the initiative is to provide a working AOSP base similar to that of Nexus devices (though in more than one way, the Sony team responsible for this has far exceeded that goal). This does not mean that things will just work (quite the contrary, really). When you bought the device, the Open Developer project should not have been a reason to be excited about the end result of the developers' efforts, but rather a sign of encouragement that you should contribute, and are indeed welcome to do so.
tl;dr: this project, like the rest of XDA, isn't about the goal, but about the journey. (except for maybe the new bootloaders but that's another thing)
Click to expand...
Click to collapse
I believe, too, that the intiative by Sony is great and a good path to follow. I also understand that the volunteers do not mind, as you say.
I just wanted some clarification on Sony's commitment. If for example, Sony would provide a working camera base for developers to improve/enhance or do they expect the volunteers to use what is already provided to figure things out.
I believe that if the camera works, however basic implementation, more developers would be helping in creating something better and enhancing it.
Whereas now, developers are waiting for Sony to provide something which they might not be planning to provide, hence some clarification.
Regarding the camera, I am a little disappointed, that is all. As Sony used to have great cameras on their devices; however, recently other Manufacturers use Sony sensors with better results than Sony themselves (Stock included).
as a matter of fact, there are no custom roms right now with good enough camera, which means without the well known (contrary) fish eye bug, that can be used if you need a basic working camera. this is stopping most of the z3c users (like me) that like aosp feel to switch to custom. so imho either sony is not helping that much with camera code, or we don't have a single very good dev capable of providing a camera fix, don't know. either way, this is very very sad.
I've always used custom roms in my previous phones, with bugs here and there of course, but never had so big bugs preventing me using custom roms like in sony phones i had (sudden reboots affecting my old xperia T that took ages to be fixed, this camera bug now in z3c). this is "funny" considering sony is known to be dev friendly. so again i think we are just unlucky with development going on for this phone probably (like i was when i used the T)
so right now people who hate all the bloat coming in stock FW and need good enough camera must stay with stock, and find already debloated solutions (like mine for example).
on this argument, really hope sony concept rom will arrive to z3c too soon at least...
not blaming anyone of course, as I'm the first one who can't help with development unfortunately.. it is just sad that many other ****ty phones like many Samsung ones for example, much worse than sony's, have tons of good development going on.. but well we know most of the user base are just sheeps thinking the only existent phones to be bought are samsung or iphones, which means less user base for Sony and other more deserving manufacturers....
moly82 said:
as a matter of fact, there are no custom roms right now with good enough camera, which means without the well known (contrary) fish eye bug, that can be used if you need a basic working camera. this is stopping most of the z3c users (like me) that like aosp feel to switch to custom. so imho either sony is not helping that much with camera code, or we don't have a single very good dev capable of providing a camera fix, don't know. either way, this is very very sad.
I've always used custom roms in my previous phones, with bugs here and there of course, but never had so big bugs preventing me using custom roms like in sony phones i had (sudden reboots affecting my old xperia T that took ages to be fixed, this camera bug now in z3c). this is "funny" considering sony is known to be dev friendly. so again i think we are just unlucky with development going on for this phone probably (like i was when i used the T)
so right now people who hate all the bloat coming in stock FW and need good enough camera must stay with stock, and find already debloated solutions (like mine for example).
on this argument, really hope sony concept rom will arrive to z3c too soon at least...
not blaming anyone of course, as I'm the first one who can't help with development unfortunately.. it is just sad that many other ****ty phones like many Samsung ones for example, much worse than sony's, have tons of good development going on.. but well we know most of the user base are just sheeps thinking the only existent phones to be bought are samsung or iphones, which means less user base for Sony and other more deserving manufacturers....
Click to expand...
Click to collapse
Not knowing anything about sony's product politics to me it seems quite a strategy that sony is pursueing. something like "we give almost everything to the freaks what they need in order to do some developement (on which we, sony, can benefit too). BUT almost means NOT everything ...". So there is no real alternative to using sony's "company rom"... if this is the case then all the developer friendly blabla is just fraud! they release aosp kernel and they do have all necessary software parts for camera sensor, of course ... so come on sony!
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
https://plus.google.com/112116692753844849623/posts/GsD7K8kDpnm
Good news ! Thanks @davidteri91 !
Experimental Open Camera HAL for AOSP available !
http://developer.sonymobile.com/201...p-camera-available-for-experienced-developers
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
jerpelea said:
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Click to expand...
Click to collapse
Enjoy what? By Sony's own addmission, a half-assed framework that will render sub-par photos and cause crashes?
Look, no one is asking for code for special processing algorithms or hacks for DRM keys. Hobbyist developers need a functional AOSP code base so they can go from there. This isn't it.
Sony has given little more than lip-service to the AOSP program, and this is a typical example. IMO, come back with something useful, or don't come back at all. So far, the entire program has been a steaming load of crap.
jerpelea said:
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
Click to expand...
Click to collapse
No, I don't, per terms and conditions, because I live in a place Sony chooses not to have a market in.
More half-assed Sony hype.
Sony has released an open-source camera to AOSP rom
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
attn1 said:
Enjoy what? By Sony's own addmission, a half-assed framework that will render sub-par photos and cause crashes?
Look, no one is asking for code for special processing algorithms or hacks for DRM keys. Hobbyist developers need a functional AOSP code base so they can go from there. This isn't it.
Sony has given little more than lip-service to the AOSP program, and this is a typical example. IMO, come back with something useful, or don't come back at all. So far, the entire program has been a steaming load of crap.
Click to expand...
Click to collapse
attn1 said:
No, I don't, per terms and conditions, because I live in a place Sony chooses not to have a market in.
More half-assed Sony hype.
Click to expand...
Click to collapse
You act like Sony owes you anything lol. Sony is having the best developer support, and yet you cry like a little girl. Did you ever consider that A company is not able to release software due to licenses?
Is there any other vendor providing ANY help with AOSP? No! Is there any other vendor giving free phones to developers for working on AOSP sources? No! Yet, other provides do not grant you the warranty you deserve for a broken HW button because your Software currupted it.. Yeah sure.
Stop crying. You're a freaking RD, one should expect you to KNOW how to act.
Actually, the camera have been released like it is because it's meant as a preview for developers, like you can read on the official blog post.
Download and see what you can find in there, the compare it with Sony stock ROMs. If you are an experienced developer, you will understand how much work was needed to get that.
Preview for developers actually means "showing you the actual progress to get help, instead of working alone and releasing when perfect and complete".
C'mon, don't flame. It's not necessary.
Peace!
-- kholk
kholk said:
Actually, the camera have been released like it is because it's meant as a preview for developers, like you can read on the official blog post.
Download and see what you can find in there, the compare it with Sony stock ROMs. If you are an experienced developer, you will understand how much work was needed to get that.
Preview for developers actually means "showing you the actual progress to get help, instead of working alone and releasing when perfect and complete".
C'mon, don't flame. It's not necessary.
Peace!
-- kholk
Click to expand...
Click to collapse
Yeah. I really don't know how he doesn't understand what "developer preview means". Some of the Android dev previews were pretty crappy too - is he going to flame Google for that too?
This is the first time, in history, that any OEM has released a camera HAL specifically designed for AOSP-based projects (other than Nexus devices, of course). It's the first time in history an official representative of an OEM has solicited constructive feedback from the community on improving a closed-source component. Yeah, I know everyone would love for these blobs to be open source, but the reality is - Even after they stumbled with the 808/810, Qualcomm has the entire mobile industry by the balls by virtue of having the only viable chipsets out there for most devices, and if they want mm-camera to be closed source, mm-camera will be closed source and right now there's not much anyone can do about it. It's sad to say that Qualcomm is the most open-source friendly SoC manufacturer out there... Which isn't saying much. (If you want to know why David's video color corruption fix was not immediately integrated into the AOSP project - blame Qualcomm. The blobs he used to fix the issue are under a redistribution license that prevents Alin from distributing them. Technically David can't legally give out those blobs to anyone, they're for personal use, but Qualcomm rarely goes after individuals.)
To everyone complaining - rather than *****ing, try to come up with specific feedback that can improve the next release.
I'm going to be trying soon to see if RAW support is working - if it isn't, that IS planned. If you're able to capture DNG images with your device, then get cracking on profiling the optical system!
http://lensfun.sourceforge.net/calibration/ - Some information on distortion profiling of a lens. Also, if you use hugin and take multiple photos properly arranged for a panorama, hugin will also perform photometric (vignetting) profiling too. A proper vignetting/distortion profile for each sensor will be a major step forward - short-term it means you can correct photos to look good using lensfun and a RAW converter, long-term the profiles will hopefully be integratable into the camera HAL. (what would be REALLY awesome is if Alin can figure out a way to implement a lensfun profile loader)
Get a colorchecker - I have http://www.amazon.com/gp/product/B005IUBU2O arriving tomorrow for example. It will allow you to determine your camera's color calibration matrix (referred to simply as "color matrix" in ufraw). I'll try to provide some proper tutorials on this once I've done it on my Z3.
Will Huawei mate 9 support which android oreo's feature project treble?
Sent from my MHA-L29 using Tapatalk
Don't count on it. They already removed the stock ROM images from the official downloads page. Seems Huawei is moving towards more closed source, and I don't think they care about updates.
arminbih said:
Don't count on it. They already removed the stock ROM images from the official downloads page. Seems Huawei is moving towards more closed source, and I don't think they care about updates.
Click to expand...
Click to collapse
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
droidbot1337 said:
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
Click to expand...
Click to collapse
Not all. They just need to release the kernel source. Which they have (though it breaks the stock camera app...).
The firmware/updates are up to them.
And for your question, I'm just speculating here, but they'd not make any money at all if they release one phone then keep updating it for a few years.
Custom roms is the reason many old devices are still being used. That and some people are cheap and don't care about security. Or they just can't afford a new phone every year.
They've publicly made a commitment to prompt OS and monthly security updates going forward within the last month. They've pledged Oreo in December.
They have made a commitment to be one of the first manufacturers to adopt Project treble. Project Treble is confirmed, and they have promised it for all devices going forward.
I realize this is an old thread now, but this still I suppose could be of use for someone so I'll leave it up.
Project Treble
bunt1691 said:
They've publicly made a commitment to prompt OS and monthly security updates going forward within the last month. They've pledged Oreo in December.
They have made a commitment to be one of the first manufacturers to adopt Project treble. Project Treble is confirmed, and they have promised it for all devices going forward.
I realize this is an old thread now, but this still I suppose could be of use for someone so I'll leave it up.
Click to expand...
Click to collapse
Project Treble is mandatory from Android 8 on according to Google (for devices shipping with Oreo), and from the manifest.xml in the Huawei Oreo update it is fully enabled in the upcoming Oreo releases. This is going to make updates and custom roms a lot easier as long as they don't rely on custom kernels and low level libraries. Treble will insulate the Android framework from the low level stuff. They have already built booting AOSP Android from Google ASOP sources (using the Huawei Oreo kernel). According to Google, implementing treble will enable phone manufacturers to update Android without having to update kernels and low level SoC stuff it will be a while before there are any AOSP based custom ROMs, but with project treble it sure will be a bunch easier
Sources
droidbot1337 said:
thats horrible bs on huaweis part. huawei is legally obligated to release all sources since they use android. google should really enforce the gpl on all oems. project treble would fix huaweis **** software problem.
sadly it seems that everyone who owns a huawei device is either brainwashed or a shill because they seem to be okay with using old outdated software without the possibility of having an update.
i hope huawei does grow here in the US. it might lead to some kind of legal action against them for not releasing sources. if anything it could result in some kind of small payday for not complying.
btw, doesnt anyone care about longevity? many phones are being released with 6GBs of RAM and very fast processors nowadays. these can last years with proper software updates. why upgrade hardware when all that is needed is newer software?
Click to expand...
Click to collapse
First off, the only source that Huawei is "legally" obligated to provide is there source for Android itself, which is and always has been freely available, they are not obligated to release source for any of their libraries or drivers. Anything having to do with the hardware is closed source and will probably remain that way. Old outdated software? On a phone that has only been out a year you must be kidding, there are phones or there that are still shipping with Android 6 (KitKat). At least Huawei will be one of the quicker phone manufacturers at rolling out Oreo to their devices, even on some of their older devices, I've had the other major manufacturers phones and they are not any better at updates than Huawei, worse on major updates actually as their updates have to get bounced back and forth between carrier and manufacturer before finally getting pushed to the user. If you're so unhappy with your device and it's **** software as you put it, sell the damn thing and buy a Samsung or LG.
https://www.xda-developers.com/stock-android-oreo-huawei-mate-9-project-treble/
Just picked up my new Honor 6x(BLN-L24) from Best Buy because I'm tired of only having 2GB RAM on my Honor 5x. Unfortunately I didn't come here before ordering because if I had I would have noticed only a fraction of dev support compared to what is available for the 5x, and I would have not purchased the 6x.
Anyway, I tried flashing HassanMirza01's LineageOS 14.1 but after letting it sit 3 times on animated boot logo screen for over 30 minutes each time I wiped everything and read through the rest of the ROMs in the dev section. Either the ROMs have currently reported install problems, or in the case of all Meticulus ROMs the download links are gone. None seem to be working correctly or near stable for daily use unless I'm missing something here.
At this point I'm following the dload method to go back to latest stock and honestly thinking about just returning the phone to Best Buy. It's quite disappointing seeing such a small amount of support for it. Is that because there is something wrong or difficult with this phone when it comes to development?
The weak development is because Huawei/Honor hasn't released source code yet (I guess, but I've seen a link for my BLL-L23 source code some time ago).
A thing I don't like about H6X devs is that lately they have (strangely) "spammed" their ports from other Huawei devices, maybe without improving the ported codes. I mean, about 6 ROMs in just a few days, with the same ported S.C... That's suspicious
But, since I'm not a dev (sad reaction only) I can't judge their work without considering all the variables involved into their work.
I guess all this happened because of the unreleased S.C, but I'm confident this has a near end.
Cheers to all devs btw, ur work is really appreciated
I can't even return to stock. I tried the dload method, and then I tried the full return to stock where I fastboot flash boot/recovery/system and then dload the update.app. Keeps saying Software install failed! on the part where I do vol+/vol-/pwr and try the dload flash of update.app.
Have I completely bricked this phone?
johnnyrichter said:
Just picked up my new Honor 6x(BLN-L24) from Best Buy because I'm tired of only having 2GB RAM on my Honor 5x. Unfortunately I didn't come here before ordering because if I had I would have noticed only a fraction of dev support compared to what is available for the 5x, and I would have not purchased the 6x.
Anyway, I tried flashing HassanMirza01's LineageOS 14.1 but after letting it sit 3 times on animated boot logo screen for over 30 minutes each time I wiped everything and read through the rest of the ROMs in the dev section. Either the ROMs have currently reported install problems, or in the case of all Meticulus ROMs the download links are gone. None seem to be working correctly or near stable for daily use unless I'm missing something here.
At this point I'm following the dload method to go back to latest stock and honestly thinking about just returning the phone to Best Buy. It's quite disappointing seeing such a small amount of support for it. Is that because there is something wrong or difficult with this phone when it comes to development?
Click to expand...
Click to collapse
You live in Missouri? :laugh: The Honor 5x is a Qualcom Snapdragon device and that chipset has plenty of official support from LineageOS. The Honor 6x is a Kirin 655 device and has absolutely NO official support what soever. You asked if there is "something wrong or difficult with this phone when it comes to development". Yes there is and for the same reason that it will NEVER had any official support from custom ROMs like Lineage: no source code.
So, if you bought your Honor 6x with expectation that your "custom rom experience" would be the same as your 5x, I'm afraid that you probably made a mistake.
As for "Where are the download links?". I mean absolutely no disrespect when I say that, if you can not find them, then it's probably for the best. :laugh:
Huawei/Honor should do something related to Kirrin processor, considering their massive advertisements on XDA- they're not caring any development
sreekantt said:
Huawei/Honor should do something related to Kirrin processor, considering their massive advertisements on XDA- they're not caring any development
Click to expand...
Click to collapse
I do not know the 'deal' that Huawei/Honor has with XDA but it seems likely to me that Huawei/Honor pays XDA to help make Huawei/Honor devices more popular by sponsoring Honor branded contests and giving away phones to 'openkirin'. I can not say for certain but I don't think that Huawei/Honor cares about 'custom ROM' development at all. It is just a vehicle, by which, XDA can make Huawei/Honor devices more popular, help increase sales and help them build their brand.
Panchoso4D said:
The weak development is because Huawei/Honor hasn't released source code yet (I guess, but I've seen a link for my BLL-L23 source code some time ago).
A thing I don't like about H6X devs is that lately they have (strangely) "spammed" their ports from other Huawei devices, maybe without improving the ported codes. I mean, about 6 ROMs in just a few days, with the same ported S.C... That's suspicious
But, since I'm not a dev (sad reaction only) I can't judge their work without considering all the variables involved into their work.
I guess all this happened because of the unreleased S.C, but I'm confident this has a near end.
Cheers to all devs btw, ur work is really appreciated
Click to expand...
Click to collapse
These ROMs came about because I decided to bring up my code base to operate on EMUI 5. While I was doing that I noticed the way Huawei does things in an abstract way so that the same code base can be used to build ROMs for many devices. I decided to do things in a similar way. In doing so, other quickly found out that this ROM runs on all hi6250 devices. However it is true that I do not own an Honor 6x and where this device differs from the devices that I do own, you come in. If you help me help you I might be able to fix issues. If not, well ... the choice is yours ...
Meticulus said:
I do not know the 'deal' that Huawei/Honor has with XDA but it seems likely to me that Huawei/Honor pays XDA to help make Huawei/Honor devices more popular by sponsoring Honor branded contests and giving away phones to 'openkirin'. I can not say for certain but I don't think that Huawei/Honor cares about 'custom ROM' development at all. It is just a vehicle, by which, XDA can make Huawei/Honor devices more popular, help increase sales and help them build their brand.
Click to expand...
Click to collapse
Yeah absolutely- thats d strategy
But for any device to appeal for XDA public - it should have impressive development or promising atmosphere(releasing sources,support etc)
Advertisements on XDA gonna do more harm than good if they have nill dev support as every user who purchases phone seeing ad on XDA hoping good development like OP would badly be disappointed and it hurts brand value indirectly. Basically majority phones which get advertised on XDA has excellent dev support already like One plus. Huawei is missing this point.
---------- Post added at 01:25 PM ---------- Previous post was at 01:22 PM ----------
Meticulus said:
These ROMs came about because I decided to bring up my code base to operate on EMUI 5. While I was doing that I noticed the way Huawei does things in an abstract way so that the same code base can be used to build ROMs for many devices. I decided to do things in a similar way. In doing so, other quickly found out that this ROM runs on all hi6250 devices. However it is true that I do not own an Honor 6x and where this device differs from the devices that I do own, you come in. If you help me help you I might be able to fix issues. If not, well ... the choice is yours ...
Click to expand...
Click to collapse
Yeah observed this- Feels like Huawei had implemented Project treble like functionality already in all kirrin devices
sreekantt said:
Yeah absolutely- thats d strategy
But for any device to appeal for XDA public - it should have impressive development or promising atmosphere(releasing sources,support etc)
Advertisements on XDA gonna do more harm than good if they have nill dev support as every user who purchases phone seeing ad on XDA hoping good development like OP would badly be disappointed and it hurts brand value indirectly. Basically majority phones which get advertised on XDA has excellent dev support already like One plus. Huawei is missing this point.
Click to expand...
Click to collapse
I am not a "business expert" and I willing to bet that you are not either. We have no idea what the nature of the business relationship is, with Huawei and it's hardware partners such as Hisilicon. Perhaps Huawei is unable to be more forth coming with its source code because of agreements they have with Hisilicon. Perhaps, Hisilicon, being relatively new to the market-place has decided that keeping their userspace code closed is in their best interest, in the face of older companies like Qualcom. Who knows? I think that companies do things by the numbers and if having "good development at XDA" could produce bigger profits for them, I'm sure they would encourage it. I willing to bet that 'custom ROM' development's impact on Huawei's bottom line is negligible. XDA is more useful to them for helping to spread the word about the brand. Also, XDA also generates revenue by advertising and although it is an unfortunate fact. When a ROM is running perfectly their is less reason to come here and post. When a ROM is half working and has lots of bugs, ppl are checking constantly while waiting for bugs to get fixes. If a ROM works well, then you just flash it and go on. No reason to stick around here....
I'm just spit balling anyway.... I could be all wrong...:laugh:
Meticulus said:
You live in Missouri? :laugh: The Honor 5x is a Qualcom Snapdragon device and that chipset has plenty of official support from LineageOS. The Honor 6x is a Kirin 655 device and has absolutely NO official support what soever. You asked if there is "something wrong or difficult with this phone when it comes to development". Yes there is and for the same reason that it will NEVER had any official support from custom ROMs like Lineage: no source code.
So, if you bought your Honor 6x with expectation that your "custom rom experience" would be the same as your 5x, I'm afraid that you probably made a mistake.
As for "Where are the download links?". I mean absolutely no disrespect when I say that, if you can not find them, then it's probably for the best. :laugh:
Click to expand...
Click to collapse
Yep, about 20 minutes from Springfield. :good:
So with Kirin, is it that they just haven't opensourced what you devs need? Has there been any 'official' discussion on that from them that would give any hope towards easier development
I didn't see links in your rom threads, and your threads don't have the Downloads tab on them like other rom threads do. Guessing you're hosting the files directly from your website you have linked in your threads?
johnnyrichter said:
So with Kirin, is it that they just haven't opensourced what you devs need? Has there been any 'official' discussion on that from them that would give any hope towards easier development.
Click to expand...
Click to collapse
I like to think I've done pretty well despite any lack of resources from Huawei. On the devices I own, to me at least, my ROMs are full daily drivers. Perhaps they are not perfect but without source it was never gonna be but, afaict the bugs are minor. I have never heard anything from Huawei on publishing their source. They publish their GPL stuff which is more than some companies do. I will admit that my ROMs probably run better on the P9 Lite and the P10 Lite because I own those devices and when they have problems, I can get information personally. Something I can't do for devices I don't own.
Meticulus said:
I like to think I've done pretty well despite any lack of resources from Huawei. On the devices I own, to me at least, my ROMs are full daily drivers. Perhaps they are not perfect but without source it was never gonna be but, afaict the bugs are minor. I have never heard anything from Huawei on publishing their source. They publish their GPL stuff which is more than some companies do. I will admit that my ROMs probably run better on the P9 Lite and the P10 Lite because I own those devices and when they have problems, I can get information personally. Something I can't do for devices I don't own.
Click to expand...
Click to collapse
Well if you're nearby in SPFD you can always hit me up if you need a phone to test stuff on, haha.
One thing that can help revive the development is an Oreo update with treble support
What do you think of this news?
https://m.gsmarena.com/analysts_pre...ion_target_of_smartphone_sales-news-31822.php
They tend to be ambitious with their target but did not consider providing support to open source community. It is Samsung's common response to the community after they present new flagship. Though it changed in Samsung S9 and Note 8 because of treble, i wonder how they respond to support the open source community. Even though, it still Android OS they are using in ther devices.
What is your view to this?
Note 8 does not support treble
What does the article have to do with your post? They have nothing in common.
ebautista said:
What do you think of this news?
https://m.gsmarena.com/analysts_pre...ion_target_of_smartphone_sales-news-31822.php
They tend to be ambitious with their target but did not consider providing support to open source community. It is Samsung's common response to the community after they present new flagship. Though it changed in Samsung S9 and Note 8 because of treble, i wonder how they respond to support the open source community. Even though, it still Android OS they are using in ther devices.
What is your view to this?
Click to expand...
Click to collapse
The open source community makes up such a small number of sales.Take XDA around 8.5 million users If every one of those had a Samsung that isn't even 10 % of sales
majority wins on this as development has such a small impact on sales that this isn't even arguable as Samsung could drop its whole mobile division tomorrow and wouldn't hurt one bit as Me and others have had this very discussion medical equipment,Construction of buildings,And ship building is there big income...
Mobile is like a side job
And this day in age It is apparent Not just any one but anyone can make a good decent phone.....
Either way threads like these always end badly so im closing it now:good: