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
Greetings!
My name is Daniel Sloof and together with a group of volunteers we have recently been working on a project called Mangler: a Ventrilo compatible client for linux. Mangler is driven by a C library called libventrilo3 and over the past couple of weeks I have been working on making this library compile with the Android-NDK. I am currently succesfully able to build libventrilo3 as a native library that can be used in Android applications. The JNI wrappers are a little lackluster, but they are being worked on.
The main reason for me posting on this forum (amongst others) is because I am looking for skilled Android/Java developers to assist us in working on this open-source project. We're mostly C programmers that have very little Android experience. I expect we could have something functional up within the month, most of the work has already been done: we're pretty much just writing a GUI for an existing backend (and some audio stuff, which is just feeding PCM to one of the native functions).
Thanks for reading! If by this point you're interested in participating or have any specific questions you can just post them here or drop by on IRC. You can find me on freenode #mangler (alias: danslo).
Im so excited for this project! I hope this goes well.
Time for an update and a quick *bump*.
More progress has been made making libventrilo suitable for Android usage. This primarily involves audio stuff, such as upsampling to rates that Android's AudioRecord doesn't support. Buffering in the Android App is still required but this can be done with minimal effort. Of course all of this (and future) progress can be found on our website.
There have also been some android developers peaking around in the IRC channel but no active developer has yet been found, feel free to drop by.
(PS: To moderators: I am cross-posting this on several Android Forums. If this is considered spam, please feel free to take appropriate measures.)
What is your website, I'd like to track your progress.
tridge said:
What is your website, I'd like to track your progress.
Click to expand...
Click to collapse
To prevent spam to the forums, new users are not permitted to post outside links in their messages. All new user accounts will be verified by moderators before this restriction is removed.
Click to expand...
Click to collapse
You can find us at mangler (dot) org though
<-- so happy to see this!~!!
*bump* - still looking for developers
Bump & small update!
I've just managed to record audio on my android device and send it to our ventrilo test server. Even with just 8khz quality (for testing purposes) the transmission sounds loud and clear on my ventrilo client! There is a small bit of delay but that doesn't seem to be caused by either the connection or the speed of the device (HTC Magic); it can probably be fixed with relative ease.
That being said, looks like we've found an Android developer willing to work on the project, but nothing is for certain so we're still looking for decent Java/Android developers to help out.
And up up we go!
Current revision in our repository can now play received audio transmissions! Once that is worked out nicely, all we'll really need is a decent GUI and some minor modifications (process more library events, etc) and we're good to go.
That spot for Android/Java developer is still available
danslo said:
And up up we go!
Current revision in our repository can now play received audio transmissions! Once that is worked out nicely, all we'll really need is a decent GUI and some minor modifications (process more library events, etc) and we're good to go.
That spot for Android/Java developer is still available
Click to expand...
Click to collapse
Way to go keep up the good work, can't wait to give it a whirl.
People dont seem to understand the potential of this, what a shame. there should be 100 guys clamoring to do this. if i coded i would be all over this.
Looking forward to seeing what comes of this!
xanaviarai said:
People dont seem to understand the potential of this, what a shame. there should be 100 guys clamoring to do this. if i coded i would be all over this.
Click to expand...
Click to collapse
Unfortunately those are the responses we get most of the time Thanks for the support!
I noticed on your website that you recommend Mumble, which I've been a huge fan and contributor since 2007. Any reason not to make Mumble for Android? It's my #1 most wanted app (I've got money on it) and I've heard from quite a few other people who want it, but hardly anyone with the skills/resources to make it happen. Then again it looks like you're in a similar situation, yet still the most qualified.
Pilot_51 said:
I noticed on your website that you recommend Mumble, which I've been a huge fan and contributor since 2007. Any reason not to make Mumble for Android? It's my #1 most wanted app (I've got money on it) and I've heard from quite a few other people who want it, but hardly anyone with the skills/resources to make it happen. Then again it looks like you're in a similar situation, yet still the most qualified.
Click to expand...
Click to collapse
Several reasons:
1) I've never worked on Mumble. (I am very familiar with the ventrilo protocol and written quite a chunk of our ventrilo library)
2) It's written in C++, which is not by default supported by the Android NDK. (unlike libventrilo3 which is written in plain C)
3) Mangler seperates a ventrilo library from its GUI interface, which makes it easy to write seperate interfaces to the same library. As far as I know this is not the case with Mumble.
Don't get me wrong, I (we?) think that Mumble is one of the better alternatives for desktop environments.. but Android places some restrictions that are difficult to overcome with the way Mumble was designed.
I hope that answers your question.
Fair enough. I will continue my search.
As I hear from some developers in the Mumble community, the main limitation is the lack of Qt support for Android, but there may be a way to work around the need for Qt. I'm not a programmer (I hope eventually), so I wouldn't know how difficult such a task would be by any standard.
Pilot_51 said:
Fair enough. I will continue my search.
As I hear from some developers in the Mumble community, the main limitation is the lack of Qt support for Android, but there may be a way to work around the need for Qt. I'm not a programmer (I hope eventually), so I wouldn't know how difficult such a task would be by any standard.
Click to expand...
Click to collapse
There's pretty much a lack of any GUI toolkit on Android (that includes Qt, but also Gtk, wxWidgets, etc). You are pretty much confined to writing it in Java with the Android SDK. Which isn't really a big issue; you want your stuff to feel like -actual- android apps anyway. The real problem with Mumble integration is the Android NDK's lack of proper (official) C++ support and a way of interfacing with the Mumble network protocol without touching any of the audio/gui stuff.
Pilot_51 said:
Fair enough. I will continue my search.
As I hear from some developers in the Mumble community, the main limitation is the lack of Qt support for Android, but there may be a way to work around the need for Qt. I'm not a programmer (I hope eventually), so I wouldn't know how difficult such a task would be by any standard.
Click to expand...
Click to collapse
There is a Qt port for Android underway, so this might help the port once it gets completed.
I've gone off-topic for long enough, but couldn't resist to post. Some dude named pcgod in our mangler IRC channel is working on a Mumble port for Android.. Git repository can be found here:
http://github.com/pcgod/mumble-android
In regards to Mangler... only thing we really still need is a GUI.
Checking out the svn of the project it seems that some work has already been done. Do you only need the GUI now? or the audio stuff too like you wrote in your first post?
EDIT: I just tried it, it manages to login and I can see that there are some users in the test server but how do I start a conversation?
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
Hey everyone, I'm looking for a developer who will be willing to help and teach me how to make a kernel! I would like to be able to add anything I want; meaning I'm looking for someone to teacher how to edit and add things to make it my own, not just teach me how to compile. I've never made anything deal with a source code, meaning I've never made an AOSP ROM nor kernel; I have made some touchwiz based ROMs, but that's a bit different. I would like to start by making something for the nexus 7 (WiFi only) then moving my way to the GsIII (d2spr). I'm currently using opensuse 12.3 KDE 64-bit, on its own HDD. Please, if anyone could help me and teach me, it would be greatly greatly appreciated!!!
What hourly rate are you willing to pay? LOL
What I would recommend you do is to start simply by:
a) installing the current NDK
b) downloading a complete stock kernel build tree as a tarball (.tgz)
c) setting up a build environment and successfully build the kernel
d) unpack an existing boot image, stuff your kernel in there, & re-pack it
e) boot it on your device. Does it run? Congrats! You are a kernel-builder!
The reason that I suggest this outline plan above is that it initially avoids learning git & associated tools until after seeing something you've built running on the device; that's a confidence-booster. That's the good news.
The bad news is that becoming a *good* kernel dev from scratch means that you simultaneously are learning kernel coding conventions, build tree structuring, and kernel APIs *plus* achieving an excellent understanding of how git & gerrit work.
In addition to some amount of original source code mods authored by a kernel dev, they spend a fair amount of time integrating patch sets (commits) coming from unrelated kernel projects (e.g. Linux kernel mainline or kernel mods from unrelated devices). Learning simple operations (commits) in git is easy enough, but understanding branch creation & multi-way merge strategies in the face of cherry-picks coming from arbitrary places is a bit of a mind bender the first time through it.
And there is the issue of compliance with the GPL. As soon as you decide to make public your work, you have an obligation to publish your sources.
There is at least one way to do this simply: don't worry about git/gerrit/github at all - use whatever source code control system you want, including none at all. When you are ready to publish, you publish a patch kit that transforms a specific commit on some other developer's (or google!) tree to your tree. That should satisfy the GPL.
Another thing to consider is to build these skills in an incremental fashion: if you have in mind a very specific kernel modification of original authorship as a first project, why not consider submitting your kernel patches as pull requests to an existing developer's kernel tree? If your patch/mod rocks, other devs will incorporate it - and probably be much more willing to answer twisty questions from you. You scratch their back, they scratch yours.
The point of the above two strategies is that they allow you to build skills incrementally rather than needing to know everything before you can begin doing anything. Don't try to learn it all simultaneously.
cheers
bftb0 said:
What hourly rate are you willing to pay? LOL
What I would recommend you do is to start simply by:
a) installing the current NDK
b) downloading a complete stock kernel build tree as a tarball (.tgz)
c) setting up a build environment and successfully build the kernel
d) unpack an existing boot image, stuff your kernel in there, & re-pack it
e) boot it on your device. Does it run? Congrats! You are a kernel-builder!
The reason that I suggest this outline plan above is that it initially avoids learning git & associated tools until after seeing something you've built running on the device; that's a confidence-booster. That's the good news.
The bad news is that becoming a *good* kernel dev from scratch means that you simultaneously are learning kernel coding conventions, build tree structuring, and kernel APIs *plus* achieving an excellent understanding of how git & gerrit work.
In addition to some amount of original source code mods authored by a kernel dev, they spend a fair amount of time integrating patch sets (commits) coming from unrelated kernel projects (e.g. Linux kernel mainline or kernel mods from unrelated devices). Learning simple operations (commits) in git is easy enough, but understanding branch creation & multi-way merge strategies in the face of cherry-picks coming from arbitrary places is a bit of a mind bender the first time through it.
And there is the issue of compliance with the GPL. As soon as you decide to make public your work, you have an obligation to publish your sources.
There is at least one way to do this simply: don't worry about git/gerrit/github at all - use whatever source code control system you want, including none at all. When you are ready to publish, you publish a patch kit that transforms a specific commit on some other developer's (or google!) tree to your tree. That should satisfy the GPL.
Another thing to consider is to build these skills in an incremental fashion: if you have in mind a very specific kernel modification of original authorship as a first project, why not consider submitting your kernel patches as pull requests to an existing developer's kernel tree? If your patch/mod rocks, other devs will incorporate it - and probably be much more willing to answer twisty questions from you. You scratch their back, they scratch yours.
The point of the above two strategies is that they allow you to build skills incrementally rather than needing to know everything before you can begin doing anything. Don't try to learn it all simultaneously.
cheers
Click to expand...
Click to collapse
Wow, okay, thank you! I'll start with that. Honestly I like having someone just point me in the directions then me teach myself the rest! That is probably the best thing to do all around. I just have somethings:
1.) If I get lost somewhere and am not able to find answer for something anywhere; do you mind if I PM you?
2.) Almost everywhere I read---including from source.android.com---it say, use Ubuntu; why? Do I have to? Ubuntu doesn't support my graphics card---and isn't easy to set up, even when using things from other OSes or just other stuff someone made---which is kinda needed because of my monitors.
jamcar said:
2.) Almost everywhere I read---including from source.android.com---it say, use Ubuntu; why? Do I have to? Ubuntu doesn't support my graphics card---and isn't easy to set up, even when using things from other OSes or just other stuff someone made---which is kinda needed because of my monitors.
Click to expand...
Click to collapse
I've used Unix/Linux for quite a long time, and if there is one thing that seems to never change is package dependency differences from distro to distro. Getting them resolved is mandatory (when you are stopped out by them), but typically quite a distraction from whatever it is you are trying to accomplish.
By using Ubuntu you will be following the footsteps of many others in front of you (including Google developers), and that means that when you encounter a problem, it will be very likely that exact problem has already been encountered and resolved, and you can find the solutions on the internet. That may not be the case for some other arbitrary distro. So, why make your life more difficult?
As far as kernel development goes, you can do anything you want inside a VM, assuming your machine has enough ram (say 4+ GB) and disk space (say 100G free). So get VirtualBox and create an Ubuntu VM.
There are small downsides to using a VM, but for code-building they are just fine - their performance in doing kernel builds is probably 95% of native metal.
jamcar said:
1.) If I get lost somewhere and am not able to find answer for something anywhere; do you mind if I PM you?
Click to expand...
Click to collapse
I would never commit to something open-ended like that - esp. since you said you have never coded anything before. You are free to PM me though, so long as you understand that I am free to choose not to reply. Given those ground rules, it might be better for you to just post your questions in public (say stackoverflow.com) so more eyeballs will see what you are asking.
cheers and good luck - you've chosen a pretty steep mountain to climb.
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.