Honor Open Source Program - Honor View 10 Guides, News, & Discussion
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey everyone,
We at Honor want to grow our community and following.
So in doing so, we are opening/releasing the AI source, kernel source and bootloaders for the Honor View 10 to developers to be able to have access not only the AI APIs but also root and give the opportunity for rom's to be developed. We want to see what some of you can do by having access to our AI eco-system.
This is extremely exciting for us at Honor and proud to invite 1000 developers, as our sign of commitment to the community to join the Honor Open Source program.
We plan to release this program by end of January 2018. There are still details to iron out but will definitely keep everyone informed with more info.
Please visit https://store.hihonor.com/us/ to sign up to be notified. Also stay tuned to this thread as well.
Being apart of the XDA community myself as a consumer for 8 years, XDA has a close place in my heart. I appreciate and thank all the developers here, personally. I am really excited to share this news to you all.
I will reach out to the LoS and AOSPA team and others, myself as I know how important they will be.
I'm all ears from you all regarding feedback. I believe this news will be well received.
Cheers!
Chris
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 1: To register for recruitment, please sign up here and share: https://goo.gl/forms/GEmYu75TnxUCeRu53
I've compiled a list of documents and source that developers need:
1. Kernel Source
2. Fastboot Factory images
3. NFC and Audio Amp source
4. Device trees
5. AI APIs
This is a list that I will request and also stress that any Chinese needs to be translated to English.
If there is anything else that devs may need, please feel free to let me know so I can ensure we make it happen
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 2:
Hope everyone is well
Big update with some exciting news to share!
We have selected the first initial developers to receive the Honor View 10. These developers are key building blocks for future development for the View 10. We're really happy to have these devs and their appropriate team on board and willing to participate with the Honor Open Source Program.
Yes, there are other important teams and developers in the community and we will provide devices to the other team members as well (LOS, AOSPA, AOSIP, DU, etc).
This is just the first, small phase of many more to come.
This should greatly jump start development once we release the kernel source publicly to download
First 9 Developers are:
@LuK1337
@topjohnwu
@franciscofranco
@luca020400
@rovo89
@OldDroid
@phhusson
@Myself5
@Dees_Troy
If all goes according to planned, kernel source should be available in the next week or two (for the EU model).
Thanks for all of your support! Hang in there and I'll keep everyone updated as more info is available
Cheers!
Chris
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 3:
Hope everyone had a great weekend!
I have some big news to start off the week...
Kernel Source has been posted for Honor View 10!
See here: https://goo.gl/1aNqGT
I'll be shipping the first 10 devices today or tomorrow, to those key devs I announced last week.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 4:
@topjohnwu has officially brought us Magisk root support for View 10
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 5: @Dees_Troy has Officially released TWRP for the View 10
https://forum.xda-developers.com/hon...overy-t3752397
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update: 5
Another batch of developers have been selected. Email for shipping info going out
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update: 6
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Here is the link to download the following images for BKL-L04 (US):
- System
- Ramdisk
- Recovery_ramdisk
- Vendor
- Kernel
This sounds amazing! I wasn't even aware that this was in the works. Can we nominate a particular developer to receive one? If so, I nominate XDA Senior Member phhusson so he can continue his work on generic, AOSP Treble ROMs.
P.S. I'll keep in touch with the AOSPA team and update the community on how things go!
MishaalRahman said:
This sounds amazing! I wasn't even aware that this was in the works. Can we nominate a particular developer to receive one? If so, I nominate XDA Senior Member phhusson so he can continue his work on generic, AOSP Treble ROMs.
P.S. I'll keep in touch with the AOSPA team and update the community on how things go!
Click to expand...
Click to collapse
Absolutely! We want to hear feedback and I can reach out to them if tagged. Ideally we're wanting to stay in the USA, but I'll find out more info.
I have already posted on the AOSPA G+ group and have gotten in contact with the LOS team as well.
Great to hear! I'd love to subscribe to the open source program when it's available.
I'd like to nominate @chadouming to receive a device for his contributions to upstreaming the use of toolchains used when compiling Android and for having taken on the Uber project as a whole when Chet Kener left development. He puts so much time into projects and his work to make it stand out. I can't stress his contributions enough. Check out his GitHub profile:
https://github.com/chadouming
[email protected]_USA said:
Hey everyone,
We at Honor want to grow our community and following.
So in doing so, we are opening the AI source and bootloaders for the Honor View 10 to developers to be able to have access not only the AI APIs but also root and give the opportunity for rom's to be developed. We want to see what some of you can do by having access to our AI eco-system.
This is extremely exciting for us at Honor and proud to invite 1000 developers, as our sign of commitment to the community to join the Honor Open Source program.
We plan to release this program by end of January 2018. There are still details to iron out but will definitely keep everyone informed with more info.
Please visit https://store.hihonor.com/us/ to sign up to be notified. Also stay tuned to this thread as well.
Being apart of the XDA community myself as a consumer for 8 years, XDA has a close place in my heart. I appreciate and thank all the developers here, personally. I am really excited to share this news to you all.
I will reach out to the LoS and AOSPA team and others, myself as I know how important they will be.
I' all ears from you all regarding feedback. I believe this news will be well received.
Cheers!
Chris
Click to expand...
Click to collapse
Nicely said Chris! Now I definitely want to get my hands on the View10! However, if I am not mistaken, the one that was released does not have US LTE bands correct? If I purchase the chinese version, can the LTE bands be unlocked or do I have to wait for the US/Global version? Also when will it be released?
+1 Chris. The Honor view 10 sold in India has no support for LTE bands used by USA carriers. So if I purchase my view 10 from India can additional LTE bands be unlocked manually. I am eager to get my hands on view 10 (sold in India and not Chinese version )but the lack of LTE bands used by USA carriers is the only thing holding me back.
I'd like to nominate @mosimchah for his work on aicp, and for his kernel work
GitHub.com/mosimchah
I would like to nominate @Cozzmy13 (demon000) for his work on Lineage infrastructure and amazing device development. His Github is here: https://github.com/Demon000
You absolutely need @Entropy512 in your team.
Not only does he love the Huawei, but absolutely adores it.
He is the wizard.
dear chris
i would like to nominate the whole open kirin team. olddroid, xpeleato, surdu_petru
This is tremendous news and i think having developers have access to bootloader and ai will really expand the potential for this device and the user experience. Look forward to being involved.
I'm in. I'm a former cyngn employee, lineage recovery developer, general lineage contributor, and aokp lead.
The open kirin team surely deserve this.
@xyyx check this out. You deserve to have this free device for developer.
For you excellent and smooth Nitrogen OS 8.1
That is an amazing news.
I would like to nominate @miststudent2011 for being an active member and a rom compiler.
[email protected]_USA said:
Hey everyone,
We at Honor want to grow our community and following.
So in doing so, we are opening the AI source and bootloaders for the Honor View 10 to developers to be able to have access not only the AI APIs but also root and give the opportunity for rom's to be developed. We want to see what some of you can do by having access to our AI eco-system.
This is extremely exciting for us at Honor and proud to invite 1000 developers, as our sign of commitment to the community to join the Honor Open Source program.
We plan to release this program by end of January 2018. There are still details to iron out but will definitely keep everyone informed with more info.
Please visit https://store.hihonor.com/us/ to sign up to be notified. Also stay tuned to this thread as well.
Being apart of the XDA community myself as a consumer for 8 years, XDA has a close place in my heart. I appreciate and thank all the developers here, personally. I am really excited to share this news to you all.
I will reach out to the LoS and AOSPA team and others, myself as I know how important they will be.
I' all ears from you all regarding feedback. I believe this news will be well received.
Cheers!
Chris
Click to expand...
Click to collapse
One of the biggest issue with the honor source for the kernel was the fact that a lot of it was in un-translable Chinese. If you guys help with the translation I am sure Honor devices would get far more custom rom development. It's one of the things that prevented me from getting the device. I only buy devices I can build aosp for.
I would like to nominate @Anik_khan he is team of lineageOs and this is his GitHub profile github.com/Anik1199
As contributor / maintainer / director of LineageOS I would like to nominate myself :3
I will nominated @Anik_khan..He is ones of member LineageOS/maintainer for some devices too and he is good developers..Hope u will count on him..
This is his github link github.com/Anik1199..Cheers from Indonesia!!!
Related
Moral code of DEVs
Yea whatever let this sub forum die as well...
Hai there In most ROM threads i see "credits" , and i guess they all work together but they have their own style of modding ROMS. As u can see we actually have 3 base ROM's ginger , honey , froyo and few teams working together and modding , upgrading , etc them. When dualtouch was relased in few days all roms got dualtouch hotfix , now in few days all roms will have flash lite hotfix etc. That would not be possible if teams hide source from each others.
Bavilo said:
I've been a member of XDA for quiet some time now and in no sub forum has the moral code been so low as here.
It's fine to work on your own projects, but it's not ok to make it closed source.
I have NOT seen one single project on this sub forum that includes the source code.
[...]
Click to expand...
Click to collapse
Hello Bavilo,
Taken from nobodyAtall's original post:
nobodyAtall said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Visit Project's page @ google code
Sources @ github
Click to expand...
Click to collapse
Now you have seen at least one project with available source code.
Regards, D_d
And the MultiTouch Module, its sources are also on github.
..........
Hi there, As I can see about Apache License on wikipedia, I don't see any part discussing about source request. Can you provide some more info about that? Thanks.
...........
Bavilo said: Good...too bad thats the wrong subforum. Also giving credit to someone is not equal to publishing the source. Like I said, several requests to publish the source, have been ignored and will always be ignored. Just look at the xrecovery sources. I don't see them anywhere. Click to expand... Click to collapse 1st check "[email protected]"... 2nd afaik xrecovery is part of "free xperia project" so check their github, but i never saw apache licence or any other licence on the thread of xrec...
Bavilo said: http://www.apache.org/licenses/LICENSE-2.0.txt Click to expand... Click to collapse Here is the part of redistribution 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. Click to expand... Click to collapse I don't see anything related to the force of publishing source when requested?
.............
............
I know that Apache License V2 is compatible to GPL, but I don't see its (Apache License V2's) requirements having such things like "you sure as hell are required to post it if someone asks for it". "Compatible" doesn't mean "the same". It is Apache License, not GPL. Can you quote the part from Apache License that contains your idea? It's very important. You just say it requires, but where is that requirement in the License? Btw, I definitely agree with you about "One must understand the agreement first."
...........
I'm learning about Licenses, and I'm asking you where did your idea come from. You didn't answer my question (simply because there isn't such thing in the Apache License V2), instead, continue to flame people. What is that attitude anyway? To make war?
doixanh said: I'm learning about Licenses, and I'm asking you where did your idea come from. You didn't answer my question (simply because there isn't such thing in the Apache License V2), instead, continue to flame people. What is that attitude anyway? To make war? Click to expand... Click to collapse I'm not flaming anyone, I'm just telling you how it is. This is supposed to be a open-source community, If people decide to take open-source, modify it and then make it their own proprietary software. Well then, good luck. I don't know what your problem is. But I don't need to put up with this anymore. Enjoy. Mods close this if you wish. It's useless anyway.
So how do you explain what Sh!t Ericsson did to us? They modified Android, and kept the source closed. It's still legal. If we have such thing in Apache License, we could have their f**kin source and build Gingerbread ourselves. Also, where do you get this info? This is supposed to be a open-source community Click to expand... Click to collapse I looked on XDA's about section and I don't see such a thing like that also. You're assuming things yourself, subjectively. /edit: or are you being jealous of people's ability while you can do nothing? I saw you have only have 2 "thanks". /edit #2: this is taken from Apache License on wikipedia: Compatibility in this case means that since the GPL version 3 is considered a superset of the Apache License 2.0, a project combining GPL version 3 and Apache License 2.0 code will need to be licensed under the GPL version 3 Click to expand... Click to collapse GPL 3 is a superset of AL 2, not equal /edit #3: you came from nowhere and argued about what devs must do. This section is quiet because we have only some devs here. X10 Mini pro is not popular, unlike your G1.
If you want source... Just pm us? We will decide if you can have it or not... On slade, dx, racht and D4 his roms topics i don't see any source download... But i am sure if i pm one of them all they would just send the sources to me and kindly ask if i can give them credits It is just that simple just send an pm and ask us for sources 8/10 times we would give it (atleast if you are not someone who don't know **** about nothing)
Hey colombian coffee addict, he was complaining that we violated Apache License V2. He believed that AL V2 forces us to publish the source when someone asks for it. I just don't understand where he got that idea from.
doixanh said: Hey colombian coffee addict, he was complaining that we violated Apache License V2. He believed that AL V2 forces us to publish the source when someone asks for it. I just don't understand where he got that idea from. Click to expand... Click to collapse im not an addict !!! ok i admit im addicted to coffee screw you dx well now i understand his point all his post are now just ............................. but we have nothing to do with the license?
owain94 said: im not an addict !!! ok i admit im addicted to coffee screw you dx well now i understand his point all his post are now just ............................. but we have nothing to do with the license? Click to expand... Click to collapse Colombian coffee addict ? wow wow wow nice! lol i got the damn power btw.. it's right, if someone ask a dev sources im almost sure it will send you all sources
Be A Part of Team Pongnamu!
Be A Part Of Team Pongnamu! We are going to develop many cool ROMs and more! So, I made a team and the current members are: pongnamu and muhammed cambaz. We are going to look for your passion for developing more than your skill. In here, all of you have chances to get selected! So, EVERYONE CAN REGISTER EVEN YOU ARE NEW OR NOT GOOD AT DEVELOPMENT IF YOU THINK YOU CAN HELP US. What are you waiting for? Please go to HERE to register and find out more information. I will accept registration until JAN 31. We will send you email if you got selected and advanced to Q2 (Almost every people advanced to Q2 will get selected). We are waiting for you!
Thread closed as cross-posting isn't allowed. Please use the thread in Android General instead.
[ROM][CM][Nightly/Release] CarbonRom KitKat [hammerhead]
About Carbon CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy. Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit. We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository. Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know. While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC. Features All of our features can be found on our site here: Carbon Features Here are some screenshots: Carbon Screenshots Carbon Updates Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users. Download Carbon All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website. Carbon Downloads Changelog For a detailed changelog, check out the changes made each night here: Carbon Changelog Support We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following: 1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this. 2) Read our FAQ, which can be found on our website. Carbon FAQ 3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself. 4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite. Who is Team Carbon? Find out here: Carbon Team Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon! XDA:DevDB Information [ROM][CM][Nightly/Release] CarbonRom KitKat [hammerhead], ROM for the Google Nexus 5 Contributors CarbonDev, winner00 ROM OS Version: 4.4.x KitKat Based On: AOSP Version Information Status: Beta Created 2014-02-03 Last Updated 2014-10-21
Reserved
Reserved
Reserved
Also reserved
Welcome, been waiting for this!
I'm excited for this! Welcome!!!!
OMG YES!!! Sent from my Nexus 5
Major brand is in the house.. ?
:highfive::good:
great job. simply great rom ever I am ob 31 1 nightly its smooth some graphical glitch there all over very cool.
Hell Yeah. Flashing Time!!
I've been running this ROM since yesterday with Elemental's CM kernel, and it's been rock solid. Can't wait to see how it develops.
Haha I'm reading this from my 5s at 2AM because even though I couldn't wait any longer for carbon and took my SIM out of the N5, I still check back here regularly hoping for this thread! Congrats on the release, guys!
Any plans for a Theme Engine ?
Notechis said: Any plans for a Theme Engine ? Click to expand... Click to collapse Settings--> personalization Gesendet von meinem Nexus 5 mit Tapatalk
Just flashed todays nightly and it's working flawlessly so far but I'm just wondering that under Personalization -> Carbon Fibers -> Device tunables nothing is displayed. What is supposed to be displayed there?
Er...what kernel can be used? AOSP or CM Caffy thingy one? Oh and btw: hell yeah! Tapatalked from my Franco Xposed Gravitational Hammerhead
jUst to report a bug if you use a black theme in theme engine like thyrus dark theme. the messaging app is themed if you open a message letters are black so you can read it. Thank s for your great rom.
Development Project
We’re looking for developers! We’re a part of a new developers platform (going live in about one month), and we must contact developers to present some business proposals. We’re looking specially for those who create full games and other apps to the AppStore. Can you guys post here your e-mail addresses? Or at least send us an email to [email protected]? You can also follow us on twitter under @NgoGames so that you can check some leaks about this "worldwide” project. Stay tuned and give it a try! Best Regards, NGO Games Team PS: This can be truly a great opportunity for you. Contact us.
[rom] lineage os 15.0 android 8.0
DESCLAIMER Your warranty is now void. I am not responsible for bricked devices, dead SD cards or thermonuclear war. WARNING This rom is quite stable, but with a red glitch in the corner offline the screen and also bug sometimes. This rom have all the feature of android Oreo in stable versione. MOD EDIT: Link removed Credits Rashed
First off this MUST be marked unofficial Second you are not the builder of these do you have @Rashed97 permission to post Lastly the red flash is because these are eng builds for debugging not public use
Posting the work of others before it has been released by them is a despicable act. It is the sole reason why so many ROM teams have left XDA. Do NOT post the work of others just to be a 'me first' thanks hoarder. As per the Forum Rules: 12. Sharing XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others. In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following: 12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question; 12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think); 12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim; 12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances: - in-process builds start showing up on forums when the developer is not yet ready to release the work; - cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging); - unofficial builds where an official build is already available; In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way. Click to expand... Click to collapse Thread closed.