Related
So when the kernel is released what will that mean for us. What kind of things can we look forward to?
Is pending some license/certification completion issues.
Thats what my email from elocity said in my latest response from them. Hoping it's sooner than later. Even explained in the email why getting the kernel released would be good for thier business. They need to deliver something whether it be the A10, the kernel or upgrade options. Wonder how possible that would be. Send your A7 in to get the multitouch screen put in. Anyways when I hear anything I will post more.
With kernel source every developer could:
- make a full ROM (kernel + any version of Android from released sources)
- improve stability and performance
- fix issues before official techsupport
- add new features
That's so important!
If we would get kernel source in summer - that might be too late. Many eLocity owners might change their devices to new Xooms, Flyers, Asus eeePads, Samsung 8.9s and etc...
That is basically how I worded it in my email, pointing out that everyday more people are selling thier a7's and getting a different device. And that if they released the kernel it would practically eliminate that. Also that thier company needs to release something soon, yet to see any branded accessories a10 is delayed and our a7 we want the kernel. give us something before you lose your future market.
I think they have to much on there hands with a10, maybe after they will release something for the a7, keep your fingers crossed
smallba said:
I think they have to much on there hands with a10, maybe after they will release something for the a7, keep your fingers crossed
Click to expand...
Click to collapse
Zipping files and emailing them takes about 2 minutes ... doing so will relief them from working more on the A7 has the community will be able to developpe stuff for the A7, otherwise the A7 will just die there.
I suggest we all email [email protected] and ask for those files to be released ASAP.
I would even say that someone just write an email template to copy and paste that email
If they care about having a future market the sooner they release the kernel the better.
masterfred said:
I would even say that someone just write an email template to copy and paste that email
Click to expand...
Click to collapse
Here.
Code:
Code:
<a href="mailto:[email protected]?subject=Petition for release of A7-040 kernel&[email protected]&body=This message is a petition to release the A7 kernel for independent development.%0A%0AThis will show good faith to your existing customers, and keep them around for the release of your future products.%0A%0AIf there is a issue with a petition being carried out this way please let us know on the A7 section of the XDA forums.">
Result yielded:
To: [email protected]
BCC: [email protected]
Subject: Petition for release of A7-040 kernel
Body:
This message is a petition to release the A7 kernel for independent development.
This will show good faith to your existing customers, and keep them around for the release of your future products.
If there is a issue with a petition being carried out this way please let us know on the A7 section of the XDA forums.
----------------------------------------------------------------
I am not going to make this live, I don't know what kind of legalities would be involved if eLoicty found a flood of e-mails harassing.
You might want to add that XDA and Dexter are even in big reseller's review (Aka Tiger Direct) ... wich is mainly why people would buy an A7 has of today ...
masterfred said:
You might want to add that XDA and Dexter are even in big reseller's review (Aka Tiger Direct) ... wich is mainly why people would buy an A7 has of today ...
Click to expand...
Click to collapse
I am not publishing it anywhere, I just made the template and created a Gmail account to track how many people use it, if any.
Like I said in the post, I don't know what kind of legalities would come into play should eLocity deem it harassing. With the whole thing being able to be composed and sent in 2 clicks I can see it being easily abused. I don't plan on being the fall guy should it result in thousands of messages.
Not to sound like an idiot but how do I post this.
rombold said:
Not to sound like an idiot but how do I post this.
Click to expand...
Click to collapse
1.Copy contents of code window.
2. Paste into HTML document.
3. Remember that you are the one responsible when eLocity gets angry.
Dexter what are your thoughts on this?
Here is an encouragement from eLocity Team :
Regarding the kernel information, I have been working to get our overseas team to release it so developers can really take the A7 to new heights. I am hoping to be able to share the kernel info soon and will certainly reach out to Dexter, the XDA community and others so they'll have a new tool to make exploring and developing easier.
Click to expand...
Click to collapse
Don't abuse those emails, but for sure, we're making a difference, if it's done properly, I can't imagine a company being mad for receiving interest in their products ...
Sorry, I didnt see this thread when I posted the other new thread...but there is some slightly newer info there.
Kernel
If they release the code does that have any impact on anny new releases of the OS for the A7? Are we assuming the eLocity is done? Is there any chance for a major upgrade before they are done?
@masterfred: your quote from them confirms all my suspicions.
"Over seas development team" my ass. eLocity is just a reseller, at most installing a different launcher and fielding (not to the best of their ability btw) the tech calls. Compal has been the ones pulling the strings the whole time.
So where does it go from here? I have very little faith that Compal will be on any rush to help the development community. They even backed out of marketing this tab under their own branding. I don't trust companies that operate from.the shadows like that.
elocity a7 source code
If you google the whats above you will find many places that reps stated elocity plans to release the source/kernel so keep smiling and be patient.
rombold said:
elocity a7 source code
If you google the whats above you will find many places that reps stated elocity plans to release the source/kernel so keep smiling and be patient.
Click to expand...
Click to collapse
Yeah, they are probably waiting for Compal to release it to them.
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?
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 implementationThe Hi110X communications IC (Integrated Circuit)The Audio systemThe Camera, other companies with the same sensor released their drivers source so it isn't Top SecretThe 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
Hi Guys,
yesterday i sent an email to Huawei if or when they release the kernel for our phone. I don't know if there is some other news but here's my mail.
CodeRR said:
Hi Guys,
yesterday i semt an email to Huawei if or when they release the kernel for our phone. I don't know if there is some other news but here's my mail.
Click to expand...
Click to collapse
hi
nice they write huawei in an other way
greetz benji
LOL well spotted
Sent from my MHA-L29 using XDA Labs
I guess that answers my own question. The Mate 9 is going back.
That decision is counter to the Written Offer that is stated within the phone itself, under Settings>About Phone>Legal Information>Open Source Licenses.
I've emailed Huawei two times using the email address provided in the above section and haven't received a response yet. I think they cannot legally proceed without publishing the kernel source.
The kernel source is even listed in the written offer text.
So they're breaking the GNU GPL. Nice...
@hondajohn88 @ante0
Your arguments are in my opinion very strong. I'll give them a call in the next days! Updates coming.
Edit: I've send them a new mail with the screenshot provided by @hondajohn88. Updates will follow.
CodeRR said:
Hi Guys,
yesterday i sent an email to Huawei if or when they release the kernel for our phone. I don't know if there is some other news but here's my mail.
Click to expand...
Click to collapse
The csr spelled Huawei wrong, why would anyone think they know anything that's going on ?
CodeRR said:
@hondajohn88 @ante0
Your arguments are in my opinion very strong. I'll give them a call in the next days! Updates coming.
Edit: I've send them a new mail with the screenshot provided by @hondajohn88. Updates will follow.
Click to expand...
Click to collapse
It could just be that they won't publish it on their site. But you should still be able to request it and they must comply. Unless they're doing a Xiaomi and just delay it for eternity.
So I got back mail from Huawei.
I think he's trying to tell me that every kernel is the same from the source, but I quite don't understand this sentence...
CodeRR said:
So I got back mail from Huawei.
I think he's trying to tell me that every kernel is the same from the source, but I quite don't understand this sentence...
Click to expand...
Click to collapse
Unfortunately, but this is biggest problem of brand-companies. Every department knows only about self. Every region does not know what HQ is doing. If HQ told that this file must be placed on regional site, regional-IT will do it. But they never will ask this file from HQ first.
I have worked out the confusion here. The Huawei rep is believing the OP is after the kernel as in the built kernel included in the software not the source code. Try re-phrasing the email and include the words source code
If someone speaks Chinese they should send an email requesting the kernel source code from Huawei of China.
They are forced to release the kernel source code by Agreement with Google.
BUT Huawei doesn't release it unless it's being requested, but THEY MUST if they got request for it
LastStandingDroid said:
They are forced to release the kernel source code by Agreement with Google.
BUT Huawei doesn't release it unless it's being requested, but THEY MUST if they got request for it
Click to expand...
Click to collapse
I requested it a couple of weeks ago, still no answer from them.
Going to send a new email now.
This is my exact wording, which should be enough. Maybe I should change 'request' to 'demand... or else'.
"I would hereby like to request the Linux Kernel source code (including modifications) for my Huawei Mate 9 (MHA, Android 7.0, EMUI 5.0) in accordance with the GNU General Public License v2 section 2.
A download link is fine.
The current "download" link on your site simply links to a readme.txt file which tells me to email you to request the source code."
Edit: And sent. Included full model now too (MHA-L29C432). But I will probably not get an answer.
Heh. Excellent.
At least they have to answer some direct questions.
We want sources, no answers.
Has anyone tried emailing Google directly stating that Huawei is failing to abide by GNU General Public License v2 section 2 and see if they can assist?
Just trying to think outside the box...
Crazypinoy9 said:
Has anyone tried emailing Google directly stating that Huawei is failing to abide by GNU General Public License v2 section 2 and see if they can assist?
Just trying to think outside the box...
Click to expand...
Click to collapse
They are =working on it.
How much they work on it is another story. Maybe their upload speed is 10kb/s idk
Sent from my CUBOT_MANITO using Tapatalk
If not release in next month I'm switching phones... this is the whole point of android for me.
Sent from my iPad using Tapatalk
Hii to all Huawei 8 owners,
Maybe some good news afterall, but maybe .. we will see
This is the info I got today and I said it I will report it back to all of you guys...
This is it what I have got
Just did copy paste from my inbox and attached a picture so that you can see that this is real messege sent to me
Re: Regarding the XDA community and Honor 8 partnership
Hi there,
I can give you an explanation for everything. Can you please post it so everyone can see? Here it is:
Quote:
Hi everyone! I just wanted to give you an update on Honor and the release of their kernel source, as well as our efforts to encourage development on Honor devices on XDA.
We started working with them in August 2016. One of the stipulations of our partnership was that they make kernel source available, to encourage development.
By October, they had released kernel source for the Honor 8. As a result, we had healthy development with early builds of CyanogenMod (now LineageOS, of course), as well as RR, working TWRP, and more. This was thanks in large part to a small team of Honor developers we assembled, comprised of @surdu_petru, @XePeleato, and @hackslash. This team also submitted to me a request to Honor to fill in some missing spots in their kernel source release, specifically the Trustzone driver, and precompiled libraries compatible with AOSP. Around that time, our partnership with Honor was ending.
Since early 2017, all kernel source has disappeared from Huawei's website, much to our disappointment, and yours. We are in contact with Honor, and soon to renew our agreement, and they claim that kernel source will be back online by the end of May. Since Huawei is such a big company and things are very slow, it might take longer than that. Also, we're not sure if they will re-release the MM kernel source, or that for Nougat. We are awaiting their answer but we are heavily pushing them to do what the community wants.
We made significant progress with Honor in 2H 2016 thanks to our agreement, and we hope that starting in June, we will resume this progress with the goal of opening up Honor devices, including the new Honor 8 Pro, so that developers have what they need and users can enjoy customization of their devices.
Please PM me anytime with any questions or concerns.
Quote:
Originally Posted by brljak83
Hii
I have been reading about Honor 8 here on XDA since I got the phone
We all Honor 8 users are very satisfide with the phone it self
But a big number of us are just disappointed with the
Huawei Honor 8 agreement between Huawei and XDA community
to give us not just better support but also the source code..
I am here not as a developer couse I am not one
I am here couse I want to speak in the name of
all Honor 8 users ( allmost all of us are disappointed )
with someone from the XDA community
I want that someone form the XDA community who can and is willing to
give me ( over the mail ) some answer or to all of us in the forum of Honor 8
if Huawei and XDA community agreement is just some kind of a lie..
And if not when will we get what is promised to us.. give us some timeline or something..
Please give us something, or do something for what is promised to us
Couse many Honor 8 users are thinking that this is just some sort of a lie
And they are very disappointed and thinking that never will be anything happening
I thing they are so much disappointed that they lost evan the will to ask you on XDA community and are thinking that it is just some sort of a lie
for what is said and promised.. but I am one of the optimist and I am still saying that
the best is yet to come
Hope for some answer and that we still will be getting the support that is promised
And I am hoping not to get disappointed too like many already are
Please give me as soon as possible some answer from either Huawei ( by contacting them as XDA community becouse of the agreement you guys had made for us ) or either some answer just
from the XDA community if you happen to know anything about the things that are promised
by that agreement if and when they will happen..
Thanks for taking your time and reading this
Best regards
Brljak83
svetius
-----
User Experience Admin
xda-developers
I've had smoke blown up my ass many times. Same old song and dance.
Sent from my FRD-L04 using XDA Premium HD app