yashsingh1/xdaforums huggingface dataset:
[Honor 8 Guides, News, & Discussion] mgbotoe:
I've never developed for the device or own it for that matter so I am on the learning ship as I go and play with the device you know?

I feel a bit intimidated by it because there is just nothing out there I can see to help me put AOSP on it at full force. I am a reader and a dower...not a dower first when it comes to this. It is a bit frustrating because as nice as the software is I want AOSP on it...but it does not seem like I will be given the appropriate blobs to make that happen.

---------- Post added at 09:59 PM ---------- Previous post was at 09:52 PM ----------

I am down to do some work on this, it's only my time that's making it hard. My c++ and my java project for my master kicking my ass...that and I work full time.

So sadly all my time to.sit and stare at codes is being used on my school work (resulting in brain farts ????????????).

Time is my issue to take this heads on, resulting in small steps on my end to do anything productive.
[Honor 8 Guides, News, & Discussion] XePeleato:
Exactly, We also felt a little bit overwhelmed, because the only device that We had as reference was the Honor 6.

About the time issue, I also have a busy schedule, it's enough to upload some work to github or solve some doubts to the P9 Lite guys, but not to keep up working regularly on my CM14.

Anyway, you can help without actually downloading the source, building Android and dealing with all that work. Working on individual modules or researching about some specific function can help immensely to development in the future.
[Honor 8 Guides, News, & Discussion] iaa85:
Maybe it can be a goid oportunity to begin to learn... Lets try when my honor 8 arrives...

Enviado de meu SM-G935F usando Tapatalk
[Honor 8 Guides, News, & Discussion] jerryhou85:
Just to point out that HiSilicon is fully owned by HUAWEI... So it all depends on HUAWEI's willing...
[Honor 8 Guides, News, & Discussion] DigiGoon:
I mean Huawei did released Vendor Blobs for Nexus 6P, then they should release those for their own device too. :D

We have to put up a good argument with them so that they can understand the requirements to make a custom ROM possible.
[Honor 8 Guides, News, & Discussion] XePeleato:
They did because the SoC is manufactured by Qualcomm, and Google surely forced them to.
[Honor 8 Guides, News, & Discussion] DigiGoon:
Yea, I know, was just kidding. :D

I think the HiSilicon won't be permitting Huawei or Honor to release the Docs, as Qualcomm does that them self, no one has to force them to do that.

We should ask Honor to force them too. :D :D
[Honor 8 Guides, News, & Discussion] PalakMi:
We should force them, asking would have got us something by now.
[Honor 8 Guides, News, & Discussion] XePeleato:
And how are We supposed to do that? Dealing with this kind of big enterprises, I don't think that to threaten them is a good idea. I'd never reply to an email written by furious people who demand something from me.
[Honor 8 Guides, News, & Discussion] PalakMi:
I didn't mean to threatn them, I'm just saying that we should remind them about the partnership with XDA ( which means they should provide everything the community needs, or this partnership will have no meaning) :(
[Honor 8 Guides, News, & Discussion] XePeleato:
I don't know about the exact agreement, but I highly doubt that Honor agreed to release everything we wanted.
[Honor 8 Guides, News, & Discussion] PalakMi:
From what I've read, it says "...to help creating a healthy development scene for the honor 8", at least this means dev community should get what it takes to make a Custom ROM.

I hope the situation will change in the near future
[Honor 8 Guides, News, & Discussion] jerryhou85:
I think maybe it's still too early to request anything yet since most of guys here didn't get their Honor 8 yet. I believe a list of files missing during Custom ROM compiling is more than general request to HUAWEI, like "we need these files, 1. abc.lib 2. bcd.so..."
[Honor 8 Guides, News, & Discussion] hackslash:
Why HiSilicon should even release them? They aren't obliged to release them. HiSilicon is an independent division of Huawei who develop SoC for Huawei/Honor phones. However the Kirin 620 is the only Kirin SoC which has seen light of true AOSP and CM (and also Ubuntu, Fedora) but that's for the HiKey board. the boards however are completely different as the HiKey is a mini board for enthusiasts to build and develop on it and test other stuff thus it's pretty pointless and useless. What we really need is the HiSilicon proprietary implementations that exist every where. For Balong modem, from rild binary to all ril libs in system, the audio stack, camera, Huawei's own WiFi chipset's implementations, the Mali GPU stack which includes libEGL, hwcomposer, gralloc implementations, then the proprietary fingerprint scanner, the IR blaster, NFC, and so many other things that I might have forgotten. We can't force Huawei/Honor to release them (and we have no right to do it, its their own code and they hold all license and rights over it). Imagine yourself in the same position as HiSilicon, the Kirin chipset have one of the best Multi Core performances (better than Qualcomn). Would you release such code so that your competitors can implement it on their own SoC? (It's just a rough example, don't brag over it, just get the idea). It is probably why Apple don't release their source code. The point is, Huawei released what they had to. They released everything what was released under GPL. Finish. It's Huawei's own will to see if they can provide the proprietary source code. If they are unable to do it, then we can't force them. The whole problem is China. And as far my experience with Chinese is concerned, Chinese people are conservative and like keeping things to themselves (so as most of us are).
[Honor 8 Guides, News, & Discussion] XePeleato:
Alright, so can you write that list? That way we'll include it to the document that will be sent to honor.
[Honor 8 Guides, News, & Discussion] DigiGoon:
Yes, but Honor should ask them for the sake of this XDA+Honor partnership to release the proprietary files, like balong modem, mali's gpu libs etc.

Still a question: Can we try to use these proprietary libs directly after pulling them from the device? I mean to say, will these directly work with AOSP or CM? Should we give it a shot. I know you said the code is bad, libs for mali is 24 MB instead it should be 3 to 5 but what do you say if we give it a try?
[Honor 8 Guides, News, & Discussion] XePeleato:
We already have them.

Is there any other option? No, those libraries won't work straight "out of the box" but that is why this section is called "Development". The 24MB issue is not related to compatibility, but to poor coding practices, and We can make such statement because We have disassembled it and know what's going on there.
[Honor 8 Guides, News, & Discussion] hackslash:
What do you think we have been doing? We can add them but the problem is that even if those libs are crucial we are also importing some EMUI specific code (some of the imp implementations are also specific to EMUI which don't work well with AOSP) which is useless and will result in a broken system (in my CM builds logcat clogged with libc warnings all about missing undefined addresses, functions). Huawei could maybe sell the code (that's what MTK has been doing with their paid development program). But any ways, not releasing source code won't hurt their sales or image.
[Honor 8 Guides, News, & Discussion] DigiGoon:
Do you have those which are compatible with AOSP and CM? I was talking about those. :)

That's what I wrote bad code, yea I know you disassembled the libs. :)

That's why I asked if we can try to put those directly in. And from the comments it seems you already tried that.

Thanks. :)

---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------

So you already made the tree, and has been experimenting with CM and AOSP. :D COol. :)
[Honor 8 Guides, News, & Discussion] XePeleato:
That libs you're asking for, simply don't exist, and it would take weeks if not months for Honor developers to prepare such libraries, so I'd forget about it.

I didn't because I haven't worked on any Honor 8 ROM. (unless you are talking about other device).
[Honor 8 Guides, News, & Discussion] DigiGoon:
Exactly. :)
[Honor 8 Guides, News, & Discussion] mgbotoe:
The debate getting hot in here, did anyone else add to the document letter?

Here it is again

https://docs.google.com/document/d/1EyDRUzRBBui2k6f_c8ODWr9C2jODCCAniXGo5zRFHQw/edit
[Honor 8 Guides, News, & Discussion] jerryhou85:
I add in a point from [MENTION=7354786]XePeleato[/MENTION] previously.

http://xdaforums.com/showpost.php?p=68794688&postcount=49
[Honor 8 Guides, News, & Discussion] svetius:
Hey everyone. I've been out of the office on vacation, now am back. :D

Reading through this thread, I still sense some disagreement about exactly what is needed. Again, I want to make a strong request to Honor with EXACTLY what we need, not just the "nice-to-haves" but the stuff that is imperative for development. Some here have stated that HiSilicon licenses Kirin to Huawei/Honor, and it'd be in breach of the license for Honor to reveal certain information about the SOC. I'm worried that this might be the heart of the issue, why Kirin is so locked-down. But, again, we have a shot at changing that.

Thanks for reposting this document, [MENTION=5039686]mgbotoe[/MENTION] but I don't think it's specific enough. For example, under the first bullet, we are asking:

What "information" do you need about it?

Then bullet 2 is crossed out, and then 3 and 4 are self-explanatory.

P.S. We have an Honor 8 in the hands of [MENTION=912474]Dees_Troy[/MENTION] and [MENTION=1289361]Mazda[/MENTION] :cowboy:
[Honor 8 Guides, News, & Discussion] PalakMi:
That's great, [MENTION=7354786]XePeleato[/MENTION] you can tell him what is needed :D
[Honor 8 Guides, News, & Discussion] XePeleato:
I need information about the HAL implementation. Here's an example, https://mega.nz/#!EgxAyQCC!I64Un4kltksKLQzdj2wjP0nIwNC_Jy-Q_17PulW1tSg about the camera HAL, it kind of explains which libraries are touched. (even tough its in Chinese). Can we figure out how to make it work without that info? Yes. Can we invest our time into more something more valuable? I guess we should.

But maybe we should reconsider where the problem is. And in my opinion if we want this project to succeed we have to talk to HiSilicon. Because as people have already proved, it's not about Huawei, but about HiSilicon (Huawei Nexus 6P, Honor 5X...).

And about not being specific enough, it's impossible for me to know what's needed for sure, now it's the turn for an Honor 8 owner to get started and do the required research.
[Honor 8 Guides, News, & Discussion] BBLN:
What's your opinion about opening a chat for the development?

I think Discord would be pretty good for us (https://discord.gg/3zPWH)

[MENTION=7354786]XePeleato[/MENTION] I do agree the optimal solution would be Huawei releasing standalone libs, but at least we should start the development and boost up the community involvement for the time being
[Honor 8 Guides, News, & Discussion] XePeleato:
And, what would you like to discuss in a chat?
[Honor 8 Guides, News, & Discussion] PalakMi:
Any updates yet?!
[Honor 8 Guides, News, & Discussion] XePeleato:
No updates since as far as I know, We sent them nothing.
[Honor 8 Guides, News, & Discussion] PalakMi:
Let's hope it gets better by the time :)
[Honor 8 Guides, News, & Discussion] BBLN:
We can discuss what's we actually need to research.

I am pretty new to android development, and that would be nice to have history of the development process through chat.

For example, I don't really understand your comment about the HAL camera. The camera.hi3650.so implements Camera HAL3, and I do not really understand what's wouldn't be stable if we took that (without the EMUI app or additional "beauty modes").

If you could point that, I would hop on and start spliting the libraries to what we exactly need.

If anyone knows from previous Honors how to make a basic cyanogenmod device tree and start from there, that would be perfect.
[Honor 8 Guides, News, & Discussion] XePeleato:
I can't help there, I already did what I could.

Because how do you know that camera.hi3650.so doesn't have proprietary dependencies?

You can't 'split' a shared library like if it was a compressed file.
[Honor 8 Guides, News, & Discussion] DigiGoon:
[MENTION=7354786]XePeleato[/MENTION] What do you need the Honor 8 users to do exactly to start the development? :)
[Honor 8 Guides, News, & Discussion] XePeleato:
I don't need anything, you are the ones that have to get it up and running, you have the kernel, the telephony code, and a HiSilicon SoC to mess with.
[Honor 8 Guides, News, & Discussion] DigiGoon:
I also ain't an honor 8 user as of now.
[Honor 8 Guides, News, & Discussion] BBLN:
That depends on what exactly you are calling a proprietary depdendency. If the camera.hi3650.so is importing function or two from emui, that don't really needs anything besides that, you CAN create a small shared library containing only that functions. (By modifying a little the assembly, or by reimplementing the function in code)

I am just asking from your experience why we got to understand the board at all, and can't extract we already have. What makes this libs unstable.

So by split I mean gathering all the libraries that are needed for a AOSP build, with small emui library to fill up the so called "utils".
[Honor 8 Guides, News, & Discussion] svetius:
Correct. :mad:
[Honor 8 Guides, News, & Discussion] XePeleato:
I'd love to prove with facts that the camera, has some dependencies (but I can't because every Huawei device is filled with more surprises so who knows...). Imagine that it depends on a file, that depends on the Camera Server (libcameraserver.so) then, you'd need to replace the full library, and so on, it isn't that simple (or maybe it is), that's why some stuff takes time and effort, but why don't you try and tell us if it works as-is?
[Honor 8 Guides, News, & Discussion] hackslash:
I have been silently reading this thread for some time and unfortunately it is filling up with useless posts, with people shouting about implementations without really knowing why they actually need. [MENTION=2235607]svetius[/MENTION] why don't you ask a person who is a developer and has a Honor 8? That person will be able to guide you better and will be able to construct robust feedback and requests on what is needed to ensure continuous development. I am giving requests based on my previous experience with Kirin devices and the scene could be completely different for Honor 8.

And a message to everyone, please avoid posting useless posts to gain points and win a Honor device. Remember, that is like spamming and is disturbing the quality of threads here at XDA. Please quote when you feel you have a real point in addition to that post or you contradict it, etc.

Anyways, [MENTION=2235607]svetius[/MENTION] get a group of people (chose at your own will) and arrange a Hangouts meeting, IRC chat or anything between that group and Honor. This partnership has made no progress and 1 month has already passed. I understand that it isn't easy, but we should make our position clear to Honor and ask them for any implementations the developer community needs. But before you do that, please please get in touch with persons who have a Honor 8 and are developing for it to get a better picture and exact requests (which you have been complaining). We are trying our level best to form a request document but most of us here (including me) don't own a Honor 8 so we couldn't help you in that regard.
[Honor 8 Guides, News, & Discussion] DigiGoon:
In fact this one is also a useless one, as you all already stated before to gather devs and make a group who knows kirin better, and contact Honor. ;)
[Honor 8 Guides, News, & Discussion] PalakMi:
You're right, a group of devs who knows Kirin will know what to do.
[Honor 8 Guides, News, & Discussion] BBLN:
I have a Honor 8 and could help with getting vendor libs or whatever from the device.

Anyhow, P9 lite CM13 is under development. This guy: http://www.meticulus.co.vu/2016/09/new-update-cyanogenmod-13-for-huawei-p9.html shares his thoughts and what's getting him stuck right now.

For example, the HWComposer comment: "The hardware composer must be build with a static libbinder. I suspect that the hwcomposer is creating ION memory heaps and surfaceflinger is treating the like standard memory heaps. Surfaceflinger neglects to unmap graphics buffers when the are free so we quickly run out of graphic memory and crash."

If [MENTION=2235607]svetius[/MENTION] could pass that to some Huawei dev who would share their insights, that would be perfect!

I checked a little and it seems the device trees should be similiar (slight differences like cortex a72 vs a53, but libs seems about the same!)

I believe we can help each other with adopting AOSP.
[Honor 8 Guides, News, & Discussion] 551790:
I think there will be no development, because Huawei. Sorry Huawei, no money from me. I thought about buying a H8, before i read this Forums. For ME it's: No CM, no Money for the device.
[Honor 8 Guides, News, & Discussion] PalakMi:
My thoughts are like yours, I'm gonna give it a month and see what happens
[Honor 8 Guides, News, & Discussion] timwelter:
I'm not sure if I'll be of any help, seeing as I have no clue how to develop anything but can I help in any way? I actually own the phone unlike some of the people here.
[Honor 8 Guides, News, & Discussion] ajwillingham:
Hi. I was wondering if it was at all possible to get the source for the Honor Note 8. There are many that like the larger version. I am one of them :D. The phone is amazing but would 100% be made better through custom roms. XDA hasn't given the Honor Note 8 and official forum so for now we are here:

http://xdaforums.com/general/general/huawei-honor-note-8-t3457185

Any help would be appreciated!
[Honor 8 Guides, News, & Discussion] XePeleato:
No way, they haven't even answered, and no Honor phone received that treatment ever.
[Honor 8 Guides, News, & Discussion] ajwillingham:
Bummer. Thanks for the info.
[Honor 8 Guides, News, & Discussion] isaak:
If you have Honor 8, you can ask help to the unofficial CM13 developer of Huawei P9, because any cooperation would be useful:

http://xdaforums.com/p9/development/rom-t3483134

And I suggest to read these guides too (first one is a bit outdated but useful):

http://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

https://nathanpfry.com/how-to-setup-ubuntu-16-04-lts-xenial-xerus-to-compile-android-roms/

https://try.github.io/
[Honor 8 Guides, News, & Discussion] PalakMi:
[MENTION=2235607]svetius[/MENTION] any updates yet?! :)
[Honor 8 Guides, News, & Discussion] svetius:
Bootloader unlock should work, waiting to get the device tree from Honor, which [MENTION=1289361]Mazda[/MENTION] says will allow him to port Dirty Unicorns to the Honor 8.
[Honor 8 Guides, News, & Discussion] PalakMi:
Yeaaaah, thanks a lot [MENTION=2235607]svetius[/MENTION] and [MENTION=1289361]Mazda[/MENTION] for those great news :)

Looking forward to help for the development
[Honor 8 Guides, News, & Discussion] timwelter:
Get hype!
[Honor 8 Guides, News, & Discussion] XePeleato:
Let's see if I got it right. Have they agreed to share the device tree? Does that mean that they will release the source of their proprietary implementations? Because the 'device tree' is just a bunch of directories with configurations of the phone...
[Honor 8 Guides, News, & Discussion] adriansticoid:
I hope that's the case.
[Honor 8 Guides, News, & Discussion] hackslash:
I believe we are circling the same track again and again. We don't need the device tree. As I have mentioned before, we can't ask anything until or unless we don't know what to ask. Give the device to a developer (...) to kick-start development and get the real deal started.
[Honor 8 Guides, News, & Discussion] anks329:
Releasing something is better than nothing. If developers so that Honor is willing to do more than just kernel sources they might be more interested in developing for the phone. So, I hope they release something soon!
[Honor 8 Guides, News, & Discussion] adriansticoid:
We are all praying for this.:highfive:
[Honor 8 Guides, News, & Discussion] zinko_pt:
I don't think they will give devices for development. From what i´ve seen so far, no.

And since sales are going so well, why again the investment. To the numbers guys managing the budget it´s hard to justify.

This decision will only have consequences in the long run, if any at all.

It´s a pitty.
[Honor 8 Guides, News, & Discussion] Ascertion:
I disagree. They've already shown that they're wanting to partner with XDA which means they value the community here. What would be better than gifting the device to a well known dev that would be willing to start making ROMs? It's the same thing as giving out review units to well known reviewers.
[Honor 8 Guides, News, & Discussion] zinko_pt:
Hope you're right. But until I see some evidence I remain sceptical. Partnership so far goes until beta testing.

Also since the company is agile as a tank ship, it may take some time to see something noticeable.
[Honor 8 Guides, News, & Discussion] FcukBloat:
can't you collect money to get this phone to a skilled dev? if i get this phone, i would be glad to contribute.. others? the more would contribute, the less money each one would have to donate..
[Honor 8 Guides, News, & Discussion] PalakMi:
[MENTION=2235607]svetius[/MENTION] it looks like there's an OFFICIAL TWRP for honor 8 by [MENTION=912474]Dees_Troy[/MENTION]

Do this mean that honor have released the device tree for honor 8?!
[Honor 8 Guides, News, & Discussion] adriansticoid:
Looks like it.

---------- Post added at 01:37 PM ---------- Previous post was at 01:37 PM ----------

The devs are not the problem. The problem is Huawei not releasing neccessary stuff for devs to use.
[Honor 8 Guides, News, & Discussion] XePeleato:
Not really, that tree was made by Dees_Troy in order to boot to recovery, and the added binary blobs, just allow to decrypt the internal storage. While it may be a great starting point, it isn't complete for CM, AOSP or whatever.
[Honor 8 Guides, News, & Discussion] FcukBloat:
thanks. but another user before you said the opposite

hence my question ;) :o

btw good luck for development for this device!
[Honor 8 Guides, News, & Discussion] adriansticoid:
Yes. Luck. This device need much of it.
[Honor 8 Guides, News, & Discussion] zinko_pt:
Just a matter of will from Huawei. Nothing to do with luck. ? ?
[Honor 8 Guides, News, & Discussion] dkionline:
Sorry for my post here. [MENTION=2235607]svetius[/MENTION], Can you request Huawei to release the actual Nougat 7.0 Kernel source for P9 and Mate9?
[Honor 8 Guides, News, & Discussion] nowheredev:
Has anyone tried to contact them to get the sources of the version 7.0 nougat ?
[Honor 8 Guides, News, & Discussion] johnhux7:
I'm going to ask via Google + see what they say

---------- Post added at 12:49 AM ---------- Previous post was at 12:11 AM ----------

I have posted the question. Said how important it is for the development of custom ROMs for our phone.

Lets see what they say

John
[Honor 8 Guides, News, & Discussion] adriansticoid:
I hope they respond positively. I will get my phone this week.
[Honor 8 Guides, News, & Discussion] Dimontiman:
Any updates yet? Or can I finally throw my Honor 8 away?

I've seen developement on lineage 14.1 for honor 8, does this mean that we dont't need anymore the required .information?

Thx
[Honor 8 Guides, News, & Discussion] adriansticoid:
Check the LOS thread for more info.
[Honor 8 Guides, News, & Discussion] BigBrad75:
Sorry to resurrect a dead head thread... But do u have any news whatsoever from Huawei about the Krein 950 nougat KERNAL source code?
[Honor 8 Guides, News, & Discussion] svetius:
I *think* by the end of this month. I should know more soon.