Database Users

[Operation "this sh*t is bananas"] Gingerbread Sources 7/29! [UPDATE]

Moto mde a stament http://sourceforge.net/motorola/atrix/discussion/general_comments/thread/9f80b745/
gb source by 7/29
So with the official 4.5.91 finally being populated to everyone through regular channels (not our awesome quicker than the maker methods ). We gain the right to demand from motorola to release the source, as according to GPL, if someone ask for the source they must release it.
Thanks joe for finding all the info on the specific lincese
Android Open Source Project license
http://source.android.com/source/licenses.html
GPL http://www.gnu.org/copyleft/gpl.html
GPL V2 http://www.gnu.org/licenses/gpl-2.0.html
LGPL http://www.gnu.org/copyleft/lesser.html
Apache License V2 http://www.apache.org/licenses/LICENSE-2.0
ubuntu licensing http://www.ubuntu.com/project/about-ubuntu/licensing
Q: Why should I care if moto releases the source or not?
A: Do you want AOSP rom, and CM7, maybe MIUI. all of this are dependent on the source. otherwise is super mega complicated to create them. And available source guarantees more devs.
So what is the plan?
Simple, the plan is to demand the source, a lot, A LOT! So they dont pull the same stunt they did with 4.1.83 update. The source for that became available last week!
So we are going to do this 2 ways! The official way, and the troll way.
The official method to request source is by writing a letter to motorola mobile to the following address.
Motorola Mobility, INC.
OSS Management
600 North US hwy 45
Libertyville, IL
60048, USA
The letter of course:
I ___________ write to request the release of the source code for the following software:
The 4.5.91 firmware update for motorola Atric 4g, the webtop included in the update, and any particular software included in this update that follows GPL licensing.
The second method, the troll way. Is simply to flood the motorola forums and requested there!
Tell everyone about this effort, we need source code right away!
on twitter use this hashtag #tsib #gpl

I love these ****ing topic names lmao
Sent from my MB860 using XDA App

neer2005 said:
I love these ****ing topic names lmao
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Me to haha i dont even have the atrix but saw this as soon as i opened the xda app haha but HTC is pulling the same **** with the evo. We got this damn ota like a month and a half ago and we still dont have the ****ing source
Sent from my PC36100 using XDA App

samcripp said:
So with the official 4.5.91 finally being populated to everyone through regular channels (not our awesome quicker than the maker methods ). We gain the right to demand from motorola to release the source, as according to GPL, if someone ask for the source they must release it.
Q: Why should I care if moto releases the source or not?
A: Do you want AOSP rom, and CM7, maybe MIUI. all of this are dependent on the source. otherwise is super mega complicated to create them. And available source guarantees more devs.
So what is the plan?
Simple, the plan is to demand the source, a lot, A LOT! So they dont pull the same stunt they did with 4.1.83 update. The source for that became available last week!
So we are going to do this 2 ways! The official way, and the troll way.
The official method to request source is by writing a letter to motorola mobile to the following address.
Motorola Mobility, INC.
OSS Management
600 North US hwy 45
Libertyville, IL
60048, USA
The letter of course:
I ___________ write to request the release of the source code for the following software:
The 4.5.91 firmware update for motorola Atric 4g, the webtop included in the update, and any particular software included in this update that follows GPL licensing.
The second method, the troll way. Is simply to flood the motorola forums and requested there!
Tell everyone about this effort, we need source code right away!
on twitter use this hashtag #tsib #gpl
Click to expand...
Click to collapse
Do we flood the Motorola support tread? Or their Dev tread? I'm on board.

Gr8Danes said:
Do we flood the Motorola support tread? Or their Dev tread? I'm on board.
Click to expand...
Click to collapse
the dev thread!

Link to the dev tread anyone?

Sam,
Are you taking initiative to write a letter to Motorola? If you do, I'm sure the XDA community would be obliged to take care of the flooding.

mpalatsi said:
Sam,
Are you taking initiative to write a letter to Motorola? If you do, I'm sure the XDA community would be obliged to take care of the flooding.
Click to expand...
Click to collapse
well considering i took the initiative to spread the word of finding the unlock, and then my handle got submited to a few international gadget sites as responsible for finding the unlock from the test servers. maybe writing to moto myself could be a bad idea. i def dont want to face any legal problems. but i will encourage anyone who wants to write them to do so, ill even write the letter and paste it for you guys, a stamp is only 45 cents!

Please some direction to help, @ or#
Swyped from 'mount' Olympus

Going on dev forum now, commence troll method.
Sent from my MB860 using XDA Premium App

https://supportforums.motorola.com/thread/54476 in the support tread too.

Lemme first be a little polite.
Dear Motorola,
You have already done your best to turn the Atrix into a dead bird. The GS2 and G2X have better fan following because you locked the bootloader, now we request you to release the source of the GB update ASAP so we can get to work with the code and bring some CM magic to the Atrix
Click to expand...
Click to collapse

Where in the Dev forums do you post? Can someone link?
Edit: here is the link for those that would like to add
https://sourceforge.net/motorola/atrix/discussion/

is it possible to build AOSP on a beta source? ... cuz befor 2 days they release 2.3 to beta testers

I've also started trolling their Developers facebook page. You guys should help me.
http://www.facebook.com/motodev?sk=wall

this does not apply to only folks on att, international users need to help to get source as well. we can compile cm for everyone globaly if we get this source. so please lets make an effort everybody!

T-t-t-t-trollin' everywhere I can

Joe did a bit of research and found every license moto has to comply with!
Android Open Source Project license
http://source.android.com/source/licenses.html
GPL http://www.gnu.org/copyleft/gpl.html
GPL V2 http://www.gnu.org/licenses/gpl-2.0.html
LGPL http://www.gnu.org/copyleft/lesser.html
Apache License V2 http://www.apache.org/licenses/LICENSE-2.0
ubuntu licensing http://www.ubuntu.com/project/about-ubuntu/licensing

Sounds uneducated and stupid.

Rikuumi said:
Sounds uneducated and stupid.
Click to expand...
Click to collapse
What does?

Calling all htc one owners PLEASE READ

HTC has been releasing new kernel bases and have not bothered to release source. According to the GPL this is unacceptable. This is not only important to developers but to we the users as well. I know a lot of you love to use custom kernels and they have improved all of our phones. Let's band together send them an e-mail and remind them that the source should be released with new kernels. Letting them get away with this will only reward this type of behaviour.
http://www.htc.com/www/contact/email/ here is the link to the e-mail even if only a little bit of people send it it still says something thank you and lets make it happen!
Sent from my HTC One using xda premium

Sent from my Black HTC ONE

Response -
Sent from my Black HTC ONE

Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium

cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Correct but there has been like two base updates and still no kernel source so a little push wont hurt
Sent from my HTC One using xda premium

cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Absolutely.

That response email just shows how ignorant of GPL HTC is. They have to supply source to anyone who submits a request in writing if I'm not mistaken.

Where did u see that rule?
Op is just a busybody who doesnt even know what to do with the source but screams for it lol.
This is what happens, when u fed too much they become too dependent on u. A tad bit late and they will start screaming.
Kinda reminds me of the horde.
Remember when the one first came out, then the source follows in a week? Thats called feeding too much.
When the horde realized that the source for 2.17 is slow, they start screaming.
Sent from my HTC One X using Tapatalk 2

I think the sources will be released when 4.2.2 is official carried out. The 4.1 sources were avaiable really quickly so I'm looking forward

HTC has gotten better than they used to be. If the op is looking for 2.17 source then lol.
---------- Post added at 07:11 AM ---------- Previous post was at 07:09 AM ----------
gunnyman said:
That response email just shows how ignorant of GPL HTC is. They have to supply source to anyone who submits a request in writing if I'm not mistaken.
Click to expand...
Click to collapse
I just spent a little while reading the gpl and I'm wrong. Htcdev is complying properly.

As already stated, they haven't "released" 4.2.2 yet, so they are not required to release the source.
We see this every time they release an update. People start crying for the source. Give them time...it WILL appear, just not always straight away.

There's no such thing as propriety in the the current HTC One's linux kernel. All the codes in there are GPL licensed.
The camera fix + the back button sensitivity fix are all in a GPL licensed driver. And I quote.
The GPL states that anyone who modifies GPL licenced code is required to make available the sources used to compile it. This is to further improve and encourage collaborative work, as well as to ensure that the best code possible is produced, and to encourage peer-review of all work. This benefits both developers and end users in numerous ways, including:
Allowing anyone to verify the code they are trusting with their data, and its authenticity
Encouraging community collaboration to produce faster fixes and updates, and better code
Helping bring new developments from other devices and fields to your own, letting you benefit from new code that wouldn’t have been available without this sharing.
The GPL imparts great freedom for GPL end users. It ensures innovation is never stifled and no project is dependent upon any single developer.
Click to expand...
Click to collapse
alphamale99 said:
Response -
Sent from my Black HTC ONE
Click to expand...
Click to collapse
cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
4.2.2 is leaked but 1.29.***.12, 1.29.***.13, 1.29.***.16, 1.29.***.16R are official releases with new kernel revisions and they should be obligued to release what they have modified on those revisions.
shiningarmor said:
Where did u see that rule?
Op is just a busybody who doesnt even know what to do with the source but screams for it lol.
This is what happens, when u fed too much they become too dependent on u. A tad bit late and they will start screaming.
Kinda reminds me of the horde.
Remember when the one first came out, then the source follows in a week? Thats called feeding too much.
When the horde realized that the source for 2.17 is slow, they start screaming.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Read GPL for the rules. The OP might not have direct benefit over this but we developers have and end users in return benefit from us.

Is there a specific time limit mentioned in the GPL? I don't think they are obliged to provide it on the spot as soon as someone requests it.

the_scotsman said:
Is there a specific time limit mentioned in the GPL? I don't think they are obliged to provide it on the spot as soon as someone requests it.
Click to expand...
Click to collapse
@the_scotsman
There is no specific time limit in the GPL license as you are suppose to be obligued to release the source code as soon as the binary is distributed to the public.
Link is here. http://www.gnu.org/licenses/gpl-2.0.html
Refer to #3
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
Click to expand...
Click to collapse
Letter A should be the one applicable to HTC's kernel license. As
B - If you're selling the software
C - If the licensor limits the license.

Thanks for that. My next point is then, if HTC are violating GPL so badly as people seem to ALWAYS be claiming, why haven't they been contacted about it? The fact they haven't is good enough for me not to stress over it.

the_scotsman said:
Thanks for that. My next point is then, if HTC are violating GPL so badly as people seem to ALWAYS be claiming, why haven't they been contacted about it? The fact they haven't is good enough for me not to stress over it.
Click to expand...
Click to collapse
@the_scotsman
They already have been contacted for numerous times. But once they receive a valid complaint they then comply to it and release the source code so the claimant then decides to discontinue the case.
Although if we really enforce this strictly when one company violates GPL he then get's blacklisted and is not allowed anymore to use any GPL licensed source code unless the company makes an appeal and no GPL licensor would oppose to the appeal.
Here's a good example
http://lists.gpl-violations.org/pipermail/legal/2011-February/002645.html
even an official from google took action in there.

There's no time limit specified... I guess the spirit is at the same time as the binaries. I doubt this has been tested in court. Usually it's settled, or they're forced to release after the fact. The timing is unlikely to have been tested, but I'd love to be informed otherwise.

Done.
Sent from my HTC One using xda app-developers app

-IMPORTANT UPDATE!- Petition to LEECO for source code release, now in change!

If developers have source code, they will make 100% functional roms. I try sending multiple times emails to LeEco asking for this, but the server always give me spam reply. Because of that I've created a thread in LeEco forum.
Please help doing a coment and voting in the poll.
This is the link to the thread: http://forum.le.com/in/index.php?threads/source-code-for-lemax2.14951/
Regards.
IMPORTANT UPDATE! Now we have a petition in change.org to do the max press possible to the brand. And the signs are for ALL the devices with Qualcomm processors.
Here it is!: https://www.change.org/p/leeco-letv...ents_action_panel_wrapper&utm_medium=copylink

great specs but the development is not so good. if they only release the sources.

Someone mentioned that they are releasing sources in September.

sanke1 said:
Someone mentioned that they are releasing sources in September.
Click to expand...
Click to collapse
Yup, in the official forum, but who knows if is true or a fake...?

I read that they are selling these phones at less than cost as a loss leader to sell people their content services. If so, I very much doubt they are interested in supporting the dev community as that makes it easier for people to get rid of their apps and services from the devices.

We need to achieve that fast!!

Did you get source code from Le? Why don't you share for us?

Anyone has updates about the source code questions?
I didn't find any update on the change.org site.
BTW' we need more votes!!

I sign!
More people need to sign!!
does anyone confirm source code release soon???

i signed.

Signed.

I got response but still no plan for releasing...
https://twitter.com/LeEcoGlobal/status/782992367280422913

I have not (yet) bought the phone b/c there will be no proper development in the absence of a source code release. I will probably go for the Axon 7 although I would like to have a bigger screen. (I will also not buy the Le Pro 3 although it is an interesting phone. Developer-unfriendly phone companies like LeEco are an absolute no-go for me. So sad ... )

Signed

Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...

I doubt they will release the source code

Do not purchase le Max2. Most of the phones have finger print sensor issues.
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app

mikeysteele said:
Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...
Click to expand...
Click to collapse
Yup, do it guys. I will put it in my petition, that people send tweets with that.

Do you have new news about letv's codes? Why didn't share with us about it?

Maybe the US launch change something I really like the phone my fingerprint has no issue except some times unresponsive but I only had it for a month LOL so fingers crossed
Maybe they'll release the source code and the worth of this phone will double

Queries for Honor

I know we have a thread to discuss source code, but I wanted to make a separate thread to solely address and discuss the queries and requests put in place to honor through @svetius.
I agree with @hackslash that it will be nice to have group of developers who are familiar with Kirin devices and are in good position to make appropriate requests.
I will like for this thread to remain solely about the requests and queries and nothing else. I will be updating as I go with @svetius communication outcomes, as he provides it.
Discussion thus far:
svetius said:
Hey Guys,
Just so you know, I have a direct line at Honor and am able to make requests as it relates to releasing sources and specific documentation. I am not a developer myself, but you guys can feel free to make requests here and I'll bring it back to Honor. It's really important that we get to the point where custom ROM development and full modification is possible on the Honor 8!
Click to expand...
Click to collapse
Requests
anks329 said:
Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!
working kernel code - kinda have this XePeleato's work
device tree
full firmware images (for backup/restore use)
proprietary vendor files
documentation on the SoC
Click to expand...
Click to collapse
XePeleato said:
Cool, I'd love to talk to them personally, but since that doesn't look possible, I'd like to ask for some things (It feels like Christmas lol)
Specific documentation (Code snippets, a document... you know) about:
Their OpenGL implementation​The Hi110X communications IC (Integrated Circuit)​The Audio system​The Camera, other companies with the same sensor released their drivers source so it isn't Top Secret​The SePolicy​
That would be a good starting point and in my opinion it's pretty reasonable.
Click to expand...
Click to collapse
anks329 said:
My thought was, if we're asking, might as well go all out and get something like what OnePlus released for the 3. A full working device tree, kernel, etc.... http://www.xda-developers.com/onepl...-3-device-trees-and-kernel-sources-available/
Click to expand...
Click to collapse
hackslash said:
One Plus did went forward and released proprietary blobs for Dash charging that were supported on AOSP based ROMs. If Huawei don't want to release source codes for their OpenGL, Hi110x, composer, camera, etc implementations, then at least proprietary blobs free from EMUI crap that work with AOSP (this is the least I want; source code is always good as it means we don't have to depend on Huawei if things break or if we want to develop future versions of Android which if aren't released officially by Huawei).
Click to expand...
Click to collapse
hackslash said:
The most important things we need are:
Proper documentation about the SoC and if possible, a Board Support Package for Kirin which will greatly boost development.
Proprietary blobs which don't include EMUI crap and Huawei's mistakes.
We already have the kernel source which thanks to Huawei was zipped in a non-case sensitive OS and the stock firmware images to extract vendor blobs (which don't work well with AOSP/CM).
Click to expand...
Click to collapse
hackslash said:
I guess I was dreaming way too much. I'm expecting too much from someone who has delivered nothing in the past. We'll keep it simple then. Honor, please release Kirin documentation, schematics and Board Support Package.
Click to expand...
Click to collapse
Updates
#1
svetius said:
Here is my most recent email to them:
There is a thread going on here about what the community needs for development on Kirin:
http://forum.xda-developers.com/hono...-code-t3456225
As you can see, here are some of the requirements:
1. Proper documentation on the SOC
2. Proprietary blobs
3. Board schematics
Click to expand...
Click to collapse
Additionally, I've asked for them to fix the bootloader unlock function so we can get it to work on Honor 8.
Click to expand...
Click to collapse
#2
svetius said:
Guys,
I just got the following from Honor, and I don't know what it means and could use some help dissecting it and refining my requests to them.
https://drive.google.com/open?id=0Bw3YYHFxKQxVaDItY0ZCSzMzT2xzRWl6T0t3ZW90azVvaEJF
@anks329 @XePeleato @hackslash @jerryhou85 @Houge_Langley @mgbotoe @DigiGoon
Also, Honor says bootloader unlock tool will work by end of month.
Click to expand...
Click to collapse

Thanks for creating this thread. Hope we get some quick responses now

anks329 said:
Thanks for creating this thread. Hope we get some quick responses now
Click to expand...
Click to collapse
I think it will be nice to organize it per what is attainable and should be released to xda per the partnership we have going on. A kernel source is nice, but more is needed.

mgbotoe said:
I think it will be nice to organize it per what is attainable and should be released to xda per the partnership we have going on. A kernel source is nice, but more is needed.
Click to expand...
Click to collapse
Indeed, but I don't think that linking Honor to this or other thread is the best way to catch their attention. In my opinion, We should send them precise and concrete requests, maybe with a little description, to be more specific or maybe to explain why is it necessary.
This thread is a great starting point, everyone that wants to get involved could send their requests and whenever We have all of them, We can discuss and finally, send them. It's just an idea.

XePeleato said:
Indeed, but I don't think that linking Honor to this or other thread is the best way to catch their attention. In my opinion, We should send them precise and concrete requests, maybe with a little description, to be more specific or maybe to explain why is it necessary.
This thread is a great starting point, everyone that wants to get involved could send their requests and whenever We have all of them, We can discuss and finally, send them. It's just an idea.
Click to expand...
Click to collapse
Currently, per the last update i put up, an email was already sent out in regard to:
1. Proper documentation on the SOC
2. Proprietary blobs
3. Board schematics

mgbotoe said:
Currently, per the last update i put up, an email was already sent out in regard to:
1. Proper documentation on the SOC
2. Proprietary blobs
3. Board schematics
Click to expand...
Click to collapse
About the documentation of the SoC, the data sheet is already out, and almost everything is explained, so I don't know what will they send. (If you mean documentation about the inner ICs like the audio amplificator, communications, etc... Then it's a good choice)
About the blobs, those can be found inside emui and are already posted here.
About the board schematics, the schematics can be useful if you are an electrical engineer and want to hook up your Jtag cable, another useful application can be to figure out the GPIOs, but that isn't really going to help someone who wants to build a rom.
Please understand that this isn't a rant, I appreciate what you guys are doing in order to help us, but the communication with Honor is crucial.

I think another request that would attract people to play with their Honor 8 is the warranty void upon rooting.
If possible, please ask them to not void our device's warranty upon rooting it.
UPDATE: Agreed with @XePeleato, we don't need schematics if we are building a ROM, schematics are for those who wants to make it modular (LOL). TBH no schematics or design of the PCB is required if we just want to build ROMs.

XePeleato said:
About the documentation of the SoC, the data sheet is already out, and almost everything is explained, so I don't know what will they send. (If you mean documentation about the inner ICs like the audio amplificator, communications, etc... Then it's a good choice)
About the blobs, those can be found inside emui and are already posted here.
About the board schematics, the schematics can be useful if you are an electrical engineer and want to hook up your Jtag cable, another useful application can be to figure out the GPIOs, but that isn't really going to help someone who wants to build a rom.
Please understand that this isn't a rant, I appreciate what you guys are doing in order to help us, but the communication with Honor is crucial.
Click to expand...
Click to collapse
For the SoC, I was thinking more in line with what you have stated, amplificator, communications, and things of that matter...I think it will be a good addition personally.
For the blobs, thank you for that inside info! So to understand, those are things we can grab from xda already from previous devices?
And ya, I can definently get your point about the board schematics.
Definitely sitting down and figuring out what is what will be a good start up and gives us a plausible standpoint to argue for the appropriate sources.
It seems you are familiar with emui? What are things that you feel we need personally?

My personal grip right now is the simple things...given the situation i feel having a stable and confirmed way for unlocking bootloader is a must. Additionally, having the firmware available for the u.s models should be a must.
It is not as though it was a simple device released in the wild and xda users decided to try their luck, no. Xda advertised for them...they conversed with them, for them to refuse to unlock users bootloaders is not acceptable.

Company wont release schematics for their board because Chinese fake manufacturers could copy it. I work for Asus and I'm repairing Notebook MB and ZenPads /eeePads motherboards and there's your PC IP and time with Asus logo watermark on schematics so you can't just screen it and post it somewhere. I agree with @mgbotoe that we need stock firmwares and easy way to unlock bootloader first (Edit: easy way like fastboot oem unlock and that's it, waiting for a code from Huawei to unlock can take some time but still hey we can at least unlock it and not to try work around it like for example on S7).

The Board Support Package is a must if we want true custom ROMs for our device. The Board Support Package is the proprietary source code the SoC vendor (HiSilicon) gives to the manufacturer (Huawei, in this case). The manufacturer tweaks the code to implement their stuff and packs those stuff in libraries. Huawei can open source some portion (if not all , HiSilicon won't allow it) of this BSP and this could really boost development. Documentations on how Huawei implements stuff is helpful and if coupled with Board Support Package, this could turn the tables for the development scene for Kirin devices.

I will do my best to give a general summation at chances given.
So the MUST thus far:
Board Support Package?
Official Firmware for all Models provided by Honor, (Specially U.S)?
Official Unlock of the bootloader through Honor, not a third party?
In the spirit of the partnership, and the honor hub...I think it doesn't hurt to push our luck haha

mgbotoe said:
For the SoC, I was thinking more in line with what you have stated, amplificator, communications, and things of that matter...I think it will be a good addition personally.
For the blobs, thank you for that inside info! So to understand, those are things we can grab from xda already from previous devices?
And ya, I can definently get your point about the board schematics.
Definitely sitting down and figuring out what is what will be a good start up and gives us a plausible standpoint to argue for the appropriate sources.
It seems you are familiar with emui? What are things that you feel we need personally?
Click to expand...
Click to collapse
The blobs can be extracted from the stock rom, that is already posted here, and some of them are suitable for rom development, but some aren't, because some have missing dependencies that are available just in EMUI. For example, in order to enable the modem in the P8 Lite/Honor 4C, We needed to include a Java class that was reversed from the C++ libraries, the same happens with hardware graphic acceleration (We are currently working on it) because it needs some pieces of code, that are proprietary and not compatible with AOSP/CM.
I have written some basic documentation about the experience, and it might be useful to future developers.
About what I think it's necessary, at the OP I made a brief enumeration, and I still think it's reasonable.
EDIT: Saw your last post, the BSP would be more than enough.

mgbotoe said:
I will do my best to give a general summation at chances given.
So the MUST thus far:
Board Support Package?
Official Firmware for all Models provided by Honor, (Specially U.S)?
Official Unlock of the bootloader through Honor, not a third party?
In the spirit of the partnership, and the honor hub...I think it doesn't hurt to push our luck haha
Click to expand...
Click to collapse
Wait a minute, hold on. You can't unlock the bootloader through Honor? As it has been for all Huawei devices, you have to go here: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail and sign in with a phone account or an email account that has been used on an EMUI device for more than 15 days. I have requested 2 bootloader unlock codes from Huawei in the past and had no problems whatsoever. The unlock code is also provided immediately.
Official firmwares are only needed to restore to stock ROM if something bad happens. If you're rooted you can always use dd to extract all images manually from a running device.

hackslash said:
Wait a minute, hold on. You can't unlock the bootloader through Honor? As it has been for all Huawei devices, you have to go here: https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail and sign in with a phone account or an email account that has been used on an EMUI device for more than 15 days. I have requested 2 bootloader unlock codes from Huawei in the past and had no problems whatsoever. The unlock code is also provided immediately.
Official firmwares are only needed to restore to stock ROM if something bad happens. If you're rooted you can always use dd to extract all images manually from a running device.
Click to expand...
Click to collapse
See that's the thing... It doesn't work and I have ran it by couple of xder with the device where the option for honor 8 and the setup just does not go through. I brought it to honor attention and they sent me in a lot of circle just to tell me they do not support the unlocks of honor 8. Has it changed since? I do not know but third parties has been the option to unlock since last I was active in the forum. As for the firmware, I feel having a direct availability of it from honor will be nice in the spirit of the partnership and the hub.
If the user mess up process of rooting it will be nice to have, I feel it slowed a lot of people down initially and it should have been provided from the getko

I was able to unlock my phone through the Chinese version of the website (using google translator). The US site would just redirect back to the main page and not let you enter your information to unlock the phone. So it works, just needs to be a better process.

anks329 said:
I was able to unlock my phone through the Chinese version of the website (using google translator). The US site would just redirect back to the main page and not let you enter your information to unlock the phone. So it works, just needs to be a better process.
Click to expand...
Click to collapse
Will have to log back in my account on the chinese main and give it another shot. Otherwise was too much hoopla for me to get it unlocked with a direct unlocked codes.

If nothing works, we have to pay to DCUnlocker then. As they support unlocking Honor 8's bootloader.
Sent from my Huawei Honor 7 using Tapatalk

mgbotoe said:
I will do my best to give a general summation at chances given.
So the MUST thus far:
Board Support Package?
Official Firmware for all Models provided by Honor, (Specially U.S)?
Official Unlock of the bootloader through Honor, not a third party?
In the spirit of the partnership, and the honor hub...I think it doesn't hurt to push our luck haha
Click to expand...
Click to collapse
So far there is only one, the Firmware (US model)

I wonder if @svetius ever got a response

What do you think about your phone? Here comes a survey from Honor

Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58

Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
So far good but im music lover and like to snap photos, honor is good taking pictures but it sucks audio loud speaker specially watching videos on YouTube ?????

Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
Why should any body on XDA do anything to help Honor ?
Honor made an aggreement with XDA saying that the Honor 8 was going to be a great phone for us when you know that what we want in a phone is updates and prompt response to releasing kernel source code.
You guys have done neither.
I'm running my Honor 8 on EMUI 5 with it's stock 380 update.
This update is terrible.
It's buggy and the battery life is terrible.
We have been asking for you to release kernel source code for months now and have received no answer.
Were stuck on an outdated version of EMUI 5.
You have released EMUI 5.1 but won't give it to us.
It's now April and were stuck on January security patch.
Honor you do your bit and then you can ask us to help you.
John
If you looking on XDA then you must have read just how unhappy people are.
You must have read the ROM's and kernel's thread and must have read how close we are in getting a fully working Lineage 14.1 and must have read how if you released your EMUI 5 kernel source code.
If you reading all this why are you not helping ?

@op that survey has nothing to do with the Honor 8. Stop spamming and get to the real matter as others have advised, we need quicker turn around for updates and Hotfixes be it Honor/Huawei or Google Hotfixes. Kernel source CODE is badly needed ASAP we need at least a engineer from Honor to help out in the Freedom of building Roms which install and run properly..
All in all its a great phone but socks like many Honor / Huawei devices for support...

Nyssa1104 said:
@op that survey has nothing to do with the Honor 8. Stop spamming and get to the real matter as others have advised, we need quicker turn around for updates and Hotfixes be it Honor/Huawei or Google Hotfixes. Kernel source CODE is badly needed ASAP we need at least a engineer from Honor to help out in the Freedom of building Roms which install and run properly..
All in all its a great phone but socks like many Honor / Huawei devices for support...
Click to expand...
Click to collapse
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.

faizalotai said:
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.
Click to expand...
Click to collapse
Totally agree with you there..
Damn shame as I do like the device just wished Rooting and mods were fare easier that what they are at the moment.. Had my device from Dec 2016 and we're at April 2017 and no changes from Honor to date..

faizalotai said:
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.
Click to expand...
Click to collapse
That's exactly what's going on.
All these manufacturers want is to sell phones.
If they just took a step back and looked at what Google do different that sell so many phones.
Release source code and updates promptly

Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
This: https://forum.xda-developers.com/showpost.php?p=71815504&postcount=3
Start making good on your promises and maybe you'll get some help. It would be one thing if Honor had never promised anything, then it would just be an unfortunate delay. The problem is that Honor said that certain things would happen and they have never happened.

Nyssa1104 said:
Totally agree with you there..
Damn shame as I do like the device just wished Rooting and mods were fare easier that what they are at the moment.. Had my device from Dec 2016 and we're at April 2017 and no changes from Honor to date..
Click to expand...
Click to collapse
Doing the path of Xiaomi. They went from n.1 seller in China to down the table. Only pleasing the stockholders is a short term vision. They had probably the lowest customer retention in the last years.

Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
@Rox_Honor
At least take the time to read and reply to these messages.
You posted on here yesterday asking us to do something for you guys.
Least you could do is take the time to reply.
Ur the Honor rep

johnhux7 said:
@Rox_Honor
At least take the time to read and reply to these messages.
You posted on here yesterday asking us to do something for you guys.
Least you could do is take the time to reply.
Ur the Honor rep
Click to expand...
Click to collapse
Nope, one way communication.

Whatever, honor and Huawei don't actually care about the north American market other than sales.
Well, that's fine. We'll show them the same dedication by simply not buying anymore Huawei or honor devices.
Lots of other great manufacturers out there making excellent devices, and actually stick to their promises.