Source Code

[anks329]

Looks like Huawei has posted some source code online: http://m.huawei.com/enmobile/consumer/support/downloads/index.htm with the label: FRD-L04_MM_EMUI4_1_opensource

I'm downloading it now, hopefully it's something good and useful!

 

[XePeleato]

Looks like Huawei has posted some source code online: http://m.huawei.com/enmobile/consumer/support/downloads/index.htm with the label: FRD-L04_MM_EMUI4_1_opensource

I'm downloading it now, hopefully it's something good and useful!

It's broken (as always, bunch of liars), I have uploaded it to github so you can download it at a decent speed: https://github.com/XePeleato/android_kernel_huawei_FRD-L04 (ignore build.sh, it's the script I use to build it)

EDIT: Fixed, as always, check github, I haven't tested it, but if you want me to upload a flashable .zip, I'd need your fstab file.

 

[Syssx]

Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?

 

[XePeleato]

Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?

There's just one way to know! But honestly, the kernel as it is now, doesn't have any improvement, however it might be useful for a developer who wants to code a custom kernel or something like that.

 

[anks329]

Glad it's in a buildable state. Now, let's see what else Huawei is going to release.

 

[hackslash]

--I think I should wait until I post my reply --

 

[svetius]

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!

 

[anks329]

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!

Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!

1. working kernel code - kinda have this XePeleato's work
2. device tree
3. full firmware images (for backup/restore use)
4. proprietary vendor files
5. documentation on the SoC

 

[XePeleato]

Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!

1. working kernel code - kinda have this XePeleato's work
2. device tree
3. full firmware images (for backup/restore use)
4. proprietary vendor files
5. documentation on the SoC

Why would you need a "device tree"? I can create a working one for you in 5 minutes. (I know what you mean, the HAL drivers are not inside the device tree, I'd try to be more specific if you want them to understand what you are asking for)

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!

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.

 

[anks329]

Why would you need a "device tree"? I can create a working one for you in 5 minutes. (I know what you mean, the HAL drivers are not inside the device tree, I'd try to be more specific if you want them to understand what you are asking for)

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/

 

[hackslash]

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/

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).

 

[svetius]

Svetius, here's what I think we would need, @XePeleato or anyone else, please chime in also!

1. working kernel code - kinda have this XePeleato's work
2. device tree
3. full firmware images (for backup/restore use)
4. proprietary vendor files
5. documentation on the SoC

From this list, what are the "must-haves"?

Would be nice for others to chime in.

 

[hackslash]

From this list, what are the "must-haves"?

Would be nice for others to chime in.

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).

 

[XePeleato]

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).

While in my opinion this is totally correct, it's also crucial to ask for reasonable stuff or Honor will think that We are just noobs asking for a 'git pull && make' solution, (that they will obviously not support).

I know this was anks' idea, but by asking for binary blobs ready to use with stock android, you are really telling them to code again a big part of their drivers and libraries. They won't do that since they are not going to put that much effort just to please us. Maybe We can suggest them to 'organize' their code for future phones.

 

[hackslash]

While in my opinion this is totally correct, it's also crucial to ask for reasonable stuff or Honor will think that We are just noobs asking for a 'git pull && make' solution, (that they will obviously not support).

I know this was anks' idea, but by asking for binary blobs ready to use with stock android, you are really telling them to code again a big part of their drivers and libraries. They won't do that since they are not going to put that much effort just to please us. Maybe We can suggest them to 'organize' their code for future phones.

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.

 

[anks329]

Both @hackslash and @XePeleato make great points. I guess I was going for a wish list, dream case option where they would be willing to put in some work for us. Realistically, I agree, good documentation and organized code will go a long way. Would it be possible to keep the lines of communication open? If there's an issue developers run into with the released code, if we can go back and ask for something additional/clarifications.

 

[hackslash]

Both @hackslash and @XePeleato make great points. I guess I was going for a wish list, dream case option where they would be willing to put in some work for us. Realistically, I agree, good documentation and organized code will go a long way. Would it be possible to keep the lines of communication open? If there's an issue developers run into with the released code, if we can go back and ask for something additional/clarifications.

I also have the same question. Since @svetius is going to be a middle man and he will carry our queries to the Honor, it would have been much better if a group of members at XDA who have experience with Kirin devices were selected and were allowed to do the talking. This way, that group could better address the problems faced in developing and the stuff which is need to implement Kirin's proprietary stuff.
Atleast there should be a separate thread here in XDA which is solely for the purpose of addressing all queries to @svetius which he would carry on to Honor. At this point, I am clueless what's happening with the partnership and if there has been even some communication regarding this between the two partners.

 

[Deleted member 2357893]

All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?

 

[jerryhou85]

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!

Setup a page on their website for developers like what SONY has been doing.

 

[XePeleato]

All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?

Of course We have the kernel source, go ahead and build CM with it.