Android Now OPEN SOURCE - Windows Mobile Development and Hacking General

http://source.android.com/
does this help speed up getting andoid on our nice lil phones? discuss

its always been open source bud (or atleast planned).... that was what was the big deal with it

Yes, but I believe the buzz is that the actual code is available for us to edit, today. And yes, this means better drivers for getting our devices to work with android.

joel2009 said:
its always been open source bud (or atleast planned).... that was what was the big deal with it
Click to expand...
Click to collapse
It's open source since 6 hours ago.
This site is new, just like the first post in it.]
sry for the english.

berchielli said:
It's open source since 6 hours ago.
This site is new, just like the first post in it.]
sry for the english.
Click to expand...
Click to collapse
the site is new yes but android was always open source.... google just finally released the code for it... the development kit has always been out there and android and the open handset alliance has known its been ported (or atleast mostly) to some phones already.... So to make myself more clearly it has always been open source, but with the release of the code it will be easier on developers

http://forum.xda-developers.com/showthread.php?t=438268
that guy phrased it right

Yay... the source to an open source os... big news

Related

Incredible Users HTC has release your SOURCE!

first link on the page! http://developer.htc.com/
ENJOY!
wow, that was fast!
Un-Effin'-Believable!
This video game voice (Ridge Racer, I think) just popped in to my head: "It's a new World Record!"
Well, I guess a big WOOHOO is in order...WOOHOOOOOOO!
EDIT: Oh, and I forgot one thing -- Thanks HTC! Now *that* is exactly how you are supposed to do it. Release a phone = release the source. Cheers!
This is great news, but don't we still need a datasheet of the snapdragon registers / etc. to be able to write to /system?
all your source r belong to us!
Here goes the link for the source code. It seems some people are having issues seeing it on the developer website.
http://member.america.htc.com/download/RomCode/Source_and_Binaries/incrediblec_cc1c2268.tar.bz2
Nice, we should send a card to HTC with a "thank you" balloon.
skrowl said:
This is great news, but don't we still need a datasheet of the snapdragon registers / etc. to be able to write to /system?
Click to expand...
Click to collapse
under arm there's a incrediblec_defconfig. In it is this:
CONFIG_ARCH_QSD8X50=y
Need some other tools to compile for this architechture, and it's only a matter of a short time between rooting and custom images.

[Operation "this sh*t is bananas"] Gingerbread Sources 7/29! [UPDATE]

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?

[CM10.X] Developing Question !

Hey lovely community !:laugh:
so guys after the "fight" in the [DEV] thread about developing CM 10.x ...
The thread got closed ! So whats now ?
Will shaaaaan or any other DEV's going on working on this or not ?
I hope you get the the things in the right way ... :highfive:
LOVE YOU <3
Let's forget about CM for a while. Shaan from the first time is speaking for his Samsung Galaxy S Advance and he's got some problem too. Even if he success build the CM for his device, we need someone to port it into GS 3 Mini, so we're far from fully workng CM. So let's wait oliver and the other who really concern about our device GS 3 Mini.
Hey!
Sincerly from my opinion that "fight" was really child`ish. I didnt make a backgroung check on Mac and i dont care what he did in the past as long as he can make something viable for our phones. We can all be "condemned" for not folowing the GNU licence agrement at some point. Anyway its bad that we lost a DEV because some ppl have pride. Afaik the licence doesnt obligate anyone to share, it give you the right to share.
PS: English is not my native language so dont flame about my speling mistake.
PS2: This is just my opinion so take it as is.
Really upset to see that the devellopers where almost done with the first operationnelle version and now everything is gone due to personal ego's!
Unfortunatly I do not have developer skills
AW: [CM10.X] Developing Question !
ztandroid said:
Let's forget about CM for a while. Shaan from the first time is speaking for his Samsung Galaxy S Advance and he's got some problem too. Even if he success build the CM for his device, we need someone to port it into GS 3 Mini, so we're far from fully workng CM. So let's wait oliver and the other who really concern about our device GS 3 Mini.
Click to expand...
Click to collapse
I'm very unhappy to hear this but ok ...so we have to wait now
But I'm also an owner of the Galaxy Ace device and if I remember rightly there were a lot of Problems too with Maclaw ... but in anyways he is a good Dev.
Enjoy your week!
And sorry for my english ...
Sent from my GT-I8190 using xda app-developers app
Lol, it was kind of fun. But to bad we have no cm.
Sent from my GT-I8190 using xda premium
Search about Maclaw and GNU first, then judge..
Maclaw break the rules
Enviado desde mi GT-I9070 usando Tapatalk 2
robilaur said:
Hey!
Sincerly from my opinion that "fight" was really child`ish. I didnt make a backgroung check on Mac and i dont care what he did in the past as long as he can make something viable for our phones. We can all be "condemned" for not folowing the GNU licence agrement at some point. Anyway its bad that we lost a DEV because some ppl have pride. Afaik the licence doesnt obligate anyone to share, it give you the right to share.
PS: English is not my native language so dont flame about my speling mistake.
PS2: This is just my opinion so take it as is.
Click to expand...
Click to collapse
I respect your opinion, but GNU and GPL clearly state that you HAVE TO SHARE THE SOURCE!
I do not respond to tech support via PM
galdosS3mini said:
Really upset to see that the devellopers where almost done with the first operationnelle version and now everything is gone due to personal ego's!
Unfortunatly I do not have developer skills
Click to expand...
Click to collapse
Had maclaw given any proof to prove that he had a operational build? Screenshots or something?
I do not respond to tech support via PM
As a matter of fact he did on his webpage, but he removed it because the thread got closed meaning he's stopped the development.
Yes he had pictures with S3 mini booting CM 10 on his website.
Regarding the GNU-GPL licence...well after taking a closer look and reading carefuly i can say I was wrong and u was right. My appologies.
Anyway we could of given him some time .... maibe he whould of shared it. IDK.
Here is the passage from the GNU-GPL licence to make everything clear to everyone :
"When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
Best regards.
Benzonat0r said:
As a matter of fact he did on his webpage, but he removed it because the thread got closed meaning he's stopped the development.
Click to expand...
Click to collapse
Not pics about cm booting. Afaik, oliver made a booting cm.
Did he post pics of the stuff he said he fixed?
robilaur said:
Yes he had pictures with S3 mini booting CM 10 on his website.
Regarding the GNU-GPL licence...well after taking a closer look and reading carefuly i can say I was wrong and u was right. My appologies.
Anyway we could of given him some time .... maibe he whould of shared it. IDK.
Here is the passage from the GNU-GPL licence to make everything clear to everyone :
"When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
Best regards.
Click to expand...
Click to collapse
Well. He isn't new to xda. He should have followed the rules.
As i already said in the thread, i had no problems if he shared the source when he released the rom. But then, there was no use ot the thread!
If he didn't want to share the source before releasing the rom, he shouldn't have had made that thread in the first place. If he did create the thread, it means he was seeking attention.
Also, did he or did he not ask for donation, before even releasing a single build?
I have seen his ways. That's why i resented.
Also, if he is a real dev, such petty things shouldn't stop him from contributing to the community!
./rant
If you are reading this text, it means that i am too busy currently and won't be tendering any support questions via PM
./rant-end
leave it at that
thread was closed
we should do the same and move on
end of the day we should all be here for the same reason
to help out to improve and add functionality to our phones
don't let one bad apple ruin the whole bunch move on
Shaaan said:
Not pics about cm booting. Afaik, oliver made a booting cm.
Did he post pics of the stuff he said he fixed?
Click to expand...
Click to collapse
RIL (call/messages/3G) were fixed from the looks of it.
hi shaaan....i saw that you are from galaxy s advance (same hardware of galaxy s3 mini).....in this evening i will re-start develop from cm10 and stop kernel develop.....(hope that i don't must work)...tomorrow i have 4 days free and i will spend to develop cm10. As i can see Oliver did a great work so i will start from that sources and every change i will publish on his repository. anyway....can you start doing some modifies with your work? The point is this: maclaw after a first compilation had various things working SO he must did something really simple.....such as changing something in BoardConfig.mk. After searching some i founded that we are missing something in this file for RIL problems that can work for our devices (start from there it is the main problem for now). add these in your boardconfig and see if work ( i am at work now and i can't test )
# RIL
BOARD_MOBILEDATA_INTERFACE_NAME := "pdp0"
#SPECIFIED SECRIL(need this to work??/)
BOARD_USES_LIBSECRIL_STUB := true
Benzonat0r said:
As a matter of fact he did on his webpage, but he removed it because the thread got closed meaning he's stopped the development.
Click to expand...
Click to collapse
Well that was a very mature move. He cand allways open a new one and post a build if he wanted.
Sent from my GT-I8190 using xda app-developers app
lupohirp said:
hi shaaan....i saw that you are from galaxy s advance (same hardware of galaxy s3 mini).....in this evening i will re-start develop from cm10 and stop kernel develop.....(hope that i don't must work)...tomorrow i have 4 days free and i will spend to develop cm10. As i can see Oliver did a great work so i will start from that sources and every change i will publish on his repository. anyway....can you start doing some modifies with your work? The point is this: maclaw after a first compilation had various things working SO he must did something really simple.....such as changing something in BoardConfig.mk. After searching some i founded that we are missing something in this file for RIL problems that can work for our devices (start from there it is the main problem for now). add these in your boardconfig and see if work ( i am at work now and i can't test )
# RIL
BOARD_MOBILEDATA_INTERFACE_NAME := "pdp0"
#SPECIFIED SECRIL(need this to work??/)
BOARD_USES_LIBSECRIL_STUB := true
Click to expand...
Click to collapse
Hey lupohirp, I've just noticed your Acer Liquid repo! Do you still have that device? :laugh:
- sorry for the OT ^^"
lupohirp said:
hi shaaan....i saw that you are from galaxy s advance (same hardware of galaxy s3 mini).....in this evening i will re-start develop from cm10 and stop kernel develop.....(hope that i don't must work)...tomorrow i have 4 days free and i will spend to develop cm10. As i can see Oliver did a great work so i will start from that sources and every change i will publish on his repository. anyway....can you start doing some modifies with your work? The point is this: maclaw after a first compilation had various things working SO he must did something really simple.....such as changing something in BoardConfig.mk. After searching some i founded that we are missing something in this file for RIL problems that can work for our devices (start from there it is the main problem for now). add these in your boardconfig and see if work ( i am at work now and i can't test )
# RIL
BOARD_MOBILEDATA_INTERFACE_NAME := "pdp0"
#SPECIFIED SECRIL(need this to work??/)
BOARD_USES_LIBSECRIL_STUB := true
Click to expand...
Click to collapse
We have already fixed RIL in cm10.
Yes. The boardconfig values are needed for RIL to work.
./rant
If you are reading this text, it means that i am too busy currently and won't be tendering any support questions via PM
./rant-end
Pezmet said:
Well that was a very mature move. He cand allways open a new one and post a build if he wanted.
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Yeah very, It makes me sick to think how that guy operates, steals Oliver's sources, fixes a few things and wham!! Calls Oliver's surces his own.
lupohirp said:
hi shaaan....i saw that you are from galaxy s advance (same hardware of galaxy s3 mini).....in this evening i will re-start develop from cm10 and stop kernel develop.....(hope that i don't must work)...tomorrow i have 4 days free and i will spend to develop cm10. As i can see Oliver did a great work so i will start from that sources and every change i will publish on his repository. anyway....can you start doing some modifies with your work? The point is this: maclaw after a first compilation had various things working SO he must did something really simple.....such as changing something in BoardConfig.mk. After searching some i founded that we are missing something in this file for RIL problems that can work for our devices (start from there it is the main problem for now). add these in your boardconfig and see if work ( i am at work now and i can't test )
# RIL
BOARD_MOBILEDATA_INTERFACE_NAME := "pdp0"
#SPECIFIED SECRIL(need this to work??/)
BOARD_USES_LIBSECRIL_STUB := true
Click to expand...
Click to collapse
For S3 Mini? For real?
Benzonat0r said:
Yeah very, It makes me sick to think how that guy operates, steals Oliver's sources, fixes a few things and wham!! Calls Oliver's surces his own.
Click to expand...
Click to collapse
I am not saying that he did not use sources from oliver. But where is the proof that he did use them?
You cant be sure.
Sent from my GT-I8190 using xda premium

-IMPORTANT UPDATE!- Petition to LEECO for source code release, now in change!

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

Source Code

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 implementation​The Hi110X communications IC (Integrated Circuit)​The Audio system​The Camera, other companies with the same sensor released their drivers source so it isn't Top Secret​The SePolicy​
That would be a good starting point and in my opinion it's pretty reasonable.
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.

Categories

Resources