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
Related
(Note posting in this topic as to dev category for obvious reasons)
This whole incident has taken me by surprise with the actions of Google against Cyanogen. Now the actions from my understanding so far are likely the result of the early release of the Market app with his new Donut based releases. There is a valid argument for Google in which it is their own proprietary code in which they want to release on their terms I would assume, however I prefer to take the side of the community. The community around XDA has supported and nurtured the development of the Android OS and the devices based upon it, with the developers pushing the limits on what they can do and implementing smarter and better solutions. We the community in a sense become beta testers for the latest and greatest Android has to offer, how many applications do you think have already added support for 1.6 due to Cyanogen's mods and our feedback?
In summary, I believe while Google does have a valid argument against, but it would better serve them to not continue with this course of action. I invite you all to write and use all social networks available to you to spread the world, submit to every news site, raise awareness of the problem. Don't waste your time with petitions, just spread the word, go viral with it.
Digg search for cyanogen:
http://digg.com/search?s=cyanogen
Original article:
http://androidandme.com/2009/09/hacks/cyanogenmod-in-trouble/
Facebook group:
http://www.facebook.com/group.php?gid=144634407186&ref=nf
Send tweets to @google also, flood the information stream.
Email the people at Engadget, Slashdot, Gizmodo, all the major blogs just to keep focus upon it.
Someone should put it up on reddit too, get some visibility on wired.com!
Listen, this situation is really cut and dry. Cyanogen had NO LICENSE to distribute the CLOSED SOURCE APPS. The rest of it is perfectly fine.
The solution:
Develop the roms, DELETE the closed source apps, sign, publish. When someone installs the roms, let them install the closed source apps themselves -- i.e., *somebody* (who won't be linked back to cyanogen) will likely post a simple "closed-source-google-apps-for-cyanogenmod-4.xx.xx.xx.zip" which can be installed from recovery mode.
Problem solved.
wont that person then be "under-fire"?
gospeed.racer said:
wont that person then be "under-fire"?
Click to expand...
Click to collapse
Only if the person gets caught.
tool to extract non free files and create a update image
If the binary files in a existing ROM can be used by cyanogenMod, what we need is a tool to reuse them in cyanogenMod. Am I wrong?
Or is it rebuild from source code ?
lbcoder said:
Listen, this situation is really cut and dry. Cyanogen had NO LICENSE to distribute the CLOSED SOURCE APPS. The rest of it is perfectly fine.
The solution:
Develop the roms, DELETE the closed source apps, sign, publish. When someone installs the roms, let them install the closed source apps themselves -- i.e., *somebody* (who won't be linked back to cyanogen) will likely post a simple "closed-source-google-apps-for-cyanogenmod-4.xx.xx.xx.zip" which can be installed from recovery mode.
Problem solved.
Click to expand...
Click to collapse
Are you a lawyer? no. So don't give your interpretation of what Cyanogen's license was and wasn't. You already started a thread about it and you're spamming the hell out of another. Don't mess with legal guesses, it's a bad bad idea. As I am someone who is studying law (and also a programmer/generally tech-smart), I am doing and suggesting to stay the hell away from that part when possible. Law -> politics -> flamewars -> ad hominem/bad posts. This is not tvtropes.
Meanwhile, can you even get past the start/initialization page without having the closed source apps, as they are market/gmail? This question is to actual modders.
Google has made a mess of thus, if they stop him from distributing with the apps it's only going to get *waaaay* messier.
You, are an IDIOT.
What happens when you *assume*? I'm sure that if you are, in fact, a law student (as you imply yourself to be, though you really only call yourself a "student" of the law, which could mean that you simply watch CNN from time to time), that this would have been answered on the first day of your first class.
Cyanogen's license *IS EXACTLY* the same as the license granted to *ALL OTHER USERS*. You want to read it? Its in your phone under About Phone --> Legal Information --> Google legal. Until you have read and understand *it all*, you should immediately cease offering your suggestions.
Edit: I just noticed your post count... 3.
Amazing, the audacity of some people. Whenever things start to get beyond the understanding of the average, all the chicken-littles come out from the woodwork and start crying about how evil the big company is. It is a direct function of a lack of understanding of the issues.
My advise: FORGET ABOUT IT. This has nothing to do with you and most likely won't have any (significant) impact on your life. At worst, you will have to add ONE SMALL STEP to the process of flashing the latest modrom.
Let me repeat: THIS IS NOT A BIG DEAL! IT DOESN'T REALLY MATTER! Your phone is NOT about to catch on fire or start spying on you.
Oh, and for you information: regarding how I know what Cyanogen's license was....
1) the fact that it is included with the phone.
2) the fact that he received a c&d order (which they wouldn't send if he was licensed, or if they had, it would be the simplest matter to resolve).
3) the fact that he said so himself.
designerfx said:
Are you a lawyer? no. So don't give your interpretation of what Cyanogen's license was and wasn't. You already started a thread about it and you're spamming the hell out of another. Don't mess with legal guesses, it's a bad bad idea. As I am someone who is studying law (and also a programmer/generally tech-smart), I am doing and suggesting to stay the hell away from that part when possible. Law -> politics -> flamewars -> ad hominem/bad posts. This is not tvtropes.
Meanwhile, can you even get past the start/initialization page without having the closed source apps, as they are market/gmail? This question is to actual modders.
Google has made a mess of thus, if they stop him from distributing with the apps it's only going to get *waaaay* messier.
Click to expand...
Click to collapse
gospeed.racer said:
wont that person then be "under-fire"?
Click to expand...
Click to collapse
At this point we're talking warez, and though I won't advocate warez, when was the last time you saw Ahmed Ahmed Ahmed from Iran get persecuted for distributing warez?
Remember that the US government can't even find Bin Laden....
Or the apps can be pulled by the users from *legitimate* images, like ADP1. This, at least, is legal for owners of ADP1's for use on ADP1's.
Frankly, adding a step to complicate the process would probably go at least a little way in getting the super-noobs out of the game. They get *really* annoying.
Oh FYI: I got that board you sent me more-or-less cleaned up now, going to start mapping it out soon.
setupr said:
If the binary files in a existing ROM can be used by cyanogenMod, what we need is a tool to reuse them in cyanogenMod. Am I wrong?
Or is it rebuild from source code ?
Click to expand...
Click to collapse
Exactly. It is incredibly simple.
unzip (official-update.zip) /path/to/file1toextract /path/to/file2toextract ... /path/to/filentoextract
zip -g (mod-rom-update.zip) /path/to/file1extract /path/to/file2extract ... /path/to/filenextract
java -jar testsign.jar (mod-rom-update.zip)
Then just copy file to /sdcard/, recovery, flash, done.
Yeah, I know that us modders will continue to be doing the same thing and continue on, I know they aren't going after the entire community. It was for distributing the new Market app before its release as I understand currently. Hell, all I would do I an adb pull from a rom and push it into a new release. Just like I will be doing with the Market app if he can't put it in another release haha.
However the point of this thread was not to see if Google had the right to do that, they did. It is that simple. It is their proprietary code that was released early, by cyanogen, but I think it is unnecessary. The point of it was to support cyanogen for more ideological reasons, this community pushes the development at a rapid pace. My Dream would have been a nightmare without the likes of JF, haykuro, cyanogen, Dude, etc. With cyanogen releasing Donut in his builds, our community has been pushing developers to up their support to it and fix bugs relating to 1.6 before it is pushed as an update. The same thing with the Market app applies, how many of those apps have screenshots already? Why alienate the true heart of the device, we are basically beta testers for those of us running experimental roms. I understand the Google position, I just wish they would see that no harm, no foul.
And don't equate the amount someone posts to the boards to their understanding of a situation. There are quite a few people that just get the ROMs, run them and can use a search button if they have problems.
holy cow batman, flame much? Some people lurk for a long time before registering such as I.
I agree it's a small issue, and cyanogen is probably already working on it at least based off of his twitter. However, it doesn't matter what you or I feels about the licensing, nor even what the courts would interpret were it to get to that point.
It however, is very inappropriate to be ad hominem and/or bar threatening to people over this issue, basically getting worked up yourself. Honestly, playing seniority and insulting my schooling? I was not trying to be threatning to you, simply pointing out that you are not a spokesperson for interpreting a software license. Really, it's like you went into an emotional rage the minute cyanogen got the C&D.
Cyanogen in trouble
I can't believe Google is pulling this crap. I can only hope that Google is smart enough to work something out with Cyanogen so he may continue to share his awesome developments. I would expect some restrictions, but they need to work with him and let him do his thing. Otherwise, where's the incentive for anyone else following in his footsteps to make programs better for Google?
setupr said:
If the binary files in a existing ROM can be used by cyanogenMod, what we need is a tool to reuse them in cyanogenMod. Am I wrong?
Or is it rebuild from source code ?
Click to expand...
Click to collapse
Maybe this is the answer?
cyanogen : And regarding the keep-proprietary-apps-on-device-for-custom-rom install, with all the odexing and resource id mismatches... Ugh.http://twitter.com/cyanogen/status/4384352484
First of all I'm no trying to troll nor spam, I am a T-mobile G2x user and over at the G2x forums we started a thread, http://forum.xda-developers.com/showthread.php?t=1360051 this thread is to get nvidia to release the source code for the tegra 2 chip, this way we can get more stable roms and yes fully functional ICS build.
I'm only doing this because the Atrix uses the same tegra 2 chip, thanks for your understanding.
I sent mine!
http://developer.nvidia.com/contact
Just to let you know, Nvidia is in no way required to release drivers for their SoC. That stuff is completely proprietary and doesn't fall under the GPL.
i sent mine!
Submitted!
Occupy ?
Dont think so, we're not pirates. I've sent an email to nvidia.
Hello,
Please release source code for the Tegra2, so the developers can support our mobile devices and tablets better and faster. I want to take more advantage of the Tegra2 chip inside my Motorola Atrix 4g and hoping that you could give the community a hand about this.
Regards, Sinan.
Click to expand...
Click to collapse
edgeicator said:
Just to let you know, Nvidia is in no way required to release drivers for their SoC. That stuff is completely proprietary and doesn't fall under the GPL.
Click to expand...
Click to collapse
We are all aware of this, but maybe with a shot of luck they decide to help developers, and release at least some code.
Even Microsoft has released some of their code to the GPL.
Sent from my LG-P999 using XDA App
Also submitted. Regardless of what may come out of this, at least we tried.
Submitted!
I don't want to hijack the other thread. But I think the best action you can take is generate some publicity from the media.
Go to Engadget. http://www.engadget.com/
There should be a red 'Tip US' on the right hand side of the webpage. Let the problem get on the main page of Engadget.
Thank you/
Email sent.
Email sent - also if anyone is wondering what to say, here is what i sent to them...may not be perfect but it gets the job done:
Hello. I am writing today to ask that you please release the source code for the Tegra 2 chip to the public.
As you most likely know, the android os has a very large developer community. With this community comes ground breaking software development and can also make an already great product become an even bigger product.
An example would be Samsung hiring the lead developer of the CyanogenMod7 custom Rom for Android.
They also gave the team one of their latest devices for further testing.
Now that device is one of the most sold Android phones of 2011.
The Tegra chip has a following already because of the little bit of development that we have been able to squeeze out of it with out the help of Nvidia. (source code)
But we believe and know that we can develop upon it even further and show Nvidia and others what the Tegra is really capable of. Which in turn will bring more interest to the chip and devices that carry the chip and that just means more sales.
It is only a win-win situation.
Thank you for reading.
Sincerely
a Nvidia customer.
you guys are asking for specific stuff in a very generic matter. nvidia has a git hub with tons of stuff already! and im sure if you ask them for ics tegra2 drivers for the atrix or g2x they will deliver.
as for nvidia helping devs, its happend!
sent mine
i did sent mine.
hope this count.
Sent it, couldn't copy the message though...
---------- Post added at 07:50 PM ---------- Previous post was at 07:28 PM ----------
Oh yea change the thread title to:
"Release the Tegra" Movement Thread [& how you can help] [Atrix]
Click to expand...
Click to collapse
Then fix your post. Make it look professional so If any of the Nvidia Dev's see it, they'ed take it seriously...
Hey Guys,
I am a T-mobile G2x user and over at the G2x forums we started a thread, [ics2g2x] [occupy nvidia]how you can help!. This request thread is to get Nvidia to release the source code for the tegra 2 chip, this way we can get more stable roms and yes a fully functional ICS build.
You can help in multiple ways. It doesn't matter how you help, as long as you did that becomes a +1 support for this thread!
1. Call them at (408) 486-2000 and ask for developer relations.
2. Email them at http://developer.nvidia.com/contact. Make sure your info is accurate so that they'll accept it.
3. Advertise this thread at places like Engadget or some other well known information website.
4. Get creative do something that we haven't listed up here, anything counts... (As long as it's good)
I'm only doing this because the Atrix uses the same tegra 2 chip, thanks for your understanding.
Support Count:
1. cervantesjc
2. WiredPirate
3. edgeicator
4. picaron1
5. OSNPA
6. Semseddin
7. vinay427
8. cption
9. Jibraldor
10. J-Roc
11. hormosapiens
12. Alaq
Click to expand...
Click to collapse
Copy and paste this into your post if you feel lazy. And update the Support Count every 1-2 days to keep this going.
I agree with changing the title in case anyone from nvidia see the thread.
however, I would leave any sort of "occupy" verbiage out. due to the recent media coverage of everything "occupy" related, it's not entirely a positive way to bring about change to what we want as far as code.
it seems a tad bit brutish to use that word to request something at this point.
imo.
Sent from my MB860 using XDA App
ifalldownalot said:
I agree with changing the title in case anyone from nvidia see the thread.
however, I would leave any sort of "occupy" verbiage out. due to the recent media coverage of everything "occupy" related, it's not entirely a positive way to bring about change to what we want as far as code.
it seems a tad bit brutish to use that word to request something at this point.
imo.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yea it might cause some problems.... Fixed:
"Release the Tegra" Movement Thread [& how you can help] [Atrix]
Click to expand...
Click to collapse
Semseddin said:
we're not pirates.
Click to expand...
Click to collapse
Speak for yourself lol.
Yeah, the thread title is a bad (polarizing) choice imho. I have enough trouble occupying my own space. And I certainly don't want to be seen in any sort of occupy movement. I work for what I have/want/need (and as an added bonus, to support the wants/needs of the occupiers, hurray for me!). But since the spirit of the thread isn't that sort of nonsense, I'm in. Message sent.
And no griping at me because I bit at the title... It was just sitting there staring at me with those "I want your stuff" and "Are you crazy? No I don't want to work for it" eyes...
Since I never do anything at work I will send them an email, spread this around, contact engadget, gizmodo, and more. I really want the ATRIX to become active. Its been dead around here a little.
Sent from my MB860 using XDA App
If developers have source code, they will make 100% functional roms. I try sending multiple times emails to LeEco asking for this, but the server always give me spam reply. Because of that I've created a thread in LeEco forum.
Please help doing a coment and voting in the poll.
This is the link to the thread: http://forum.le.com/in/index.php?threads/source-code-for-lemax2.14951/
Regards.
IMPORTANT UPDATE! Now we have a petition in change.org to do the max press possible to the brand. And the signs are for ALL the devices with Qualcomm processors.
Here it is!: https://www.change.org/p/leeco-letv...ents_action_panel_wrapper&utm_medium=copylink
great specs but the development is not so good. if they only release the sources.
Someone mentioned that they are releasing sources in September.
sanke1 said:
Someone mentioned that they are releasing sources in September.
Click to expand...
Click to collapse
Yup, in the official forum, but who knows if is true or a fake...?
I read that they are selling these phones at less than cost as a loss leader to sell people their content services. If so, I very much doubt they are interested in supporting the dev community as that makes it easier for people to get rid of their apps and services from the devices.
We need to achieve that fast!!
Did you get source code from Le? Why don't you share for us?
Anyone has updates about the source code questions?
I didn't find any update on the change.org site.
BTW' we need more votes!!
I sign!
More people need to sign!!
does anyone confirm source code release soon???
i signed.
Signed.
I got response but still no plan for releasing...
https://twitter.com/LeEcoGlobal/status/782992367280422913
I have not (yet) bought the phone b/c there will be no proper development in the absence of a source code release. I will probably go for the Axon 7 although I would like to have a bigger screen. (I will also not buy the Le Pro 3 although it is an interesting phone. Developer-unfriendly phone companies like LeEco are an absolute no-go for me. So sad ... )
Signed
Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...
I doubt they will release the source code
Do not purchase le Max2. Most of the phones have finger print sensor issues.
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app
mikeysteele said:
Every tweet they post about their USA launch should get a comment about how their crappy source code policy is...
Click to expand...
Click to collapse
Yup, do it guys. I will put it in my petition, that people send tweets with that.
Do you have new news about letv's codes? Why didn't share with us about it?
Maybe the US launch change something I really like the phone my fingerprint has no issue except some times unresponsive but I only had it for a month LOL so fingers crossed
Maybe they'll release the source code and the worth of this phone will double
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!
anks329 said:
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!
Click to expand...
Click to collapse
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.
Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?
Syssx said:
Thats a L04 version, will this work with L09 Dual Sim (32gb EU) version?
Click to expand...
Click to collapse
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.
Glad it's in a buildable state. Now, let's see what else Huawei is going to release.
--I think I should wait until I post my reply --
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 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
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
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
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)
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
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.
XePeleato said:
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)
Click to expand...
Click to collapse
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/
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
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).
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
From this list, what are the "must-haves"?
Would be nice for others to chime in.
svetius said:
From this list, what are the "must-haves"?
Would be nice for others to chime in.
Click to expand...
Click to collapse
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).
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
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.
XePeleato said:
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.
Click to expand...
Click to collapse
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.
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.
anks329 said:
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.
Click to expand...
Click to collapse
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.
All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?
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
Setup a page on their website for developers like what SONY has been doing.
scafroglia93 said:
All this is pure marketing . How can you be a thread of a phone that does not own the source kernel ?
Click to expand...
Click to collapse
Of course We have the kernel source, go ahead and build CM with it.
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
So far good but im music lover and like to snap photos, honor is good taking pictures but it sucks audio loud speaker specially watching videos on YouTube ?????
Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
Why should any body on XDA do anything to help Honor ?
Honor made an aggreement with XDA saying that the Honor 8 was going to be a great phone for us when you know that what we want in a phone is updates and prompt response to releasing kernel source code.
You guys have done neither.
I'm running my Honor 8 on EMUI 5 with it's stock 380 update.
This update is terrible.
It's buggy and the battery life is terrible.
We have been asking for you to release kernel source code for months now and have received no answer.
Were stuck on an outdated version of EMUI 5.
You have released EMUI 5.1 but won't give it to us.
It's now April and were stuck on January security patch.
Honor you do your bit and then you can ask us to help you.
John
If you looking on XDA then you must have read just how unhappy people are.
You must have read the ROM's and kernel's thread and must have read how close we are in getting a fully working Lineage 14.1 and must have read how if you released your EMUI 5 kernel source code.
If you reading all this why are you not helping ?
@op that survey has nothing to do with the Honor 8. Stop spamming and get to the real matter as others have advised, we need quicker turn around for updates and Hotfixes be it Honor/Huawei or Google Hotfixes. Kernel source CODE is badly needed ASAP we need at least a engineer from Honor to help out in the Freedom of building Roms which install and run properly..
All in all its a great phone but socks like many Honor / Huawei devices for support...
Nyssa1104 said:
@op that survey has nothing to do with the Honor 8. Stop spamming and get to the real matter as others have advised, we need quicker turn around for updates and Hotfixes be it Honor/Huawei or Google Hotfixes. Kernel source CODE is badly needed ASAP we need at least a engineer from Honor to help out in the Freedom of building Roms which install and run properly..
All in all its a great phone but socks like many Honor / Huawei devices for support...
Click to expand...
Click to collapse
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.
faizalotai said:
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.
Click to expand...
Click to collapse
Totally agree with you there..
Damn shame as I do like the device just wished Rooting and mods were fare easier that what they are at the moment.. Had my device from Dec 2016 and we're at April 2017 and no changes from Honor to date..
faizalotai said:
Seems like huawei are in race releasing new devices rather maintaining an updates for their devices.
I think now they're only cared about how much of their devices sale's.
Click to expand...
Click to collapse
That's exactly what's going on.
All these manufacturers want is to sell phones.
If they just took a step back and looked at what Google do different that sell so many phones.
Release source code and updates promptly
Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
This: https://forum.xda-developers.com/showpost.php?p=71815504&postcount=3
Start making good on your promises and maybe you'll get some help. It would be one thing if Honor had never promised anything, then it would just be an unfortunate delay. The problem is that Honor said that certain things would happen and they have never happened.
Nyssa1104 said:
Totally agree with you there..
Damn shame as I do like the device just wished Rooting and mods were fare easier that what they are at the moment.. Had my device from Dec 2016 and we're at April 2017 and no changes from Honor to date..
Click to expand...
Click to collapse
Doing the path of Xiaomi. They went from n.1 seller in China to down the table. Only pleasing the stockholders is a short term vision. They had probably the lowest customer retention in the last years.
Rox_Honor said:
Hey all,
What do you think about your phone? Below is an online survey from honor team to get more insights on your needs. :highfive:
Survey link - https://www.surveymonkey.com/r/6R3QT58
Click to expand...
Click to collapse
@Rox_Honor
At least take the time to read and reply to these messages.
You posted on here yesterday asking us to do something for you guys.
Least you could do is take the time to reply.
Ur the Honor rep
johnhux7 said:
@Rox_Honor
At least take the time to read and reply to these messages.
You posted on here yesterday asking us to do something for you guys.
Least you could do is take the time to reply.
Ur the Honor rep
Click to expand...
Click to collapse
Nope, one way communication.
Whatever, honor and Huawei don't actually care about the north American market other than sales.
Well, that's fine. We'll show them the same dedication by simply not buying anymore Huawei or honor devices.
Lots of other great manufacturers out there making excellent devices, and actually stick to their promises.