Related
I noticed that kernels for android are released under GPL, and that anyone using them has to provide full source of the kernels built on them and such.
Isn't HTC and possibly t-mobile inviolation of GPL by not releasing the source for both the MyTouch 3G Limited Edition and MyTouch 3G v1.2 ?
I noticed there's a website to report such violations http://gpl-violations.org/ , and an email to send info about possible abuse [email protected] but would anything useful come of it?
Android is released under the Apache Licence, the kernel under the GNU GPL
OP is talking about the kernel, if there are no sources it's a violation.
Definitly GPL violation.
I don't think they're ready to release the Fender version kernel yet although I doubt it varies much from the Magic and is (I didn't actually check through the code) most likely a configuration you set before compilation. Also, having looked through the Tattoo source a while back, it seems void of apps and other userland components, just hardware related goodness so it won't be complete but should be compliant. Either way...
http://developer.htc.com/
enatefox said:
I don't think they're ready to release the Fender version kernel yet although I doubt it varies much from the Magic and is (I didn't actually check through the code) most likely a configuration you set before compilation. Also, having looked through the Tattoo source a while back, it seems void of apps and other userland components, just hardware related goodness so it won't be complete but should be compliant. Either way...
http://developer.htc.com/
Click to expand...
Click to collapse
You haven't been following all the MT3G LE/1.2 threads have you. There's at least a difference in wifi, bluetooth, touchscreen and headphone jack in terms of drivers. So even if you could manage to get a Magic 32A rom onto a Fender/1.2 and boot it, you wouldn't have a touchscreen, bluetooth, wifi or headphone jack, and there's also a number of other little issues. Also without the kernel source, no custom roms.
So clearly it's not a Magic 32A.
kbeezie said:
You haven't been following all the MT3G LE/1.2 threads have you. There's at least a difference in wifi, bluetooth, touchscreen and headphone jack in terms of drivers. So even if you could manage to get a Magic 32A rom onto a Fender/1.2 and boot it, you wouldn't have a touchscreen, bluetooth, wifi or headphone jack, and there's also a number of other little issues. Also without the kernel source, no custom roms.
So clearly it's not a Magic 32A.
Click to expand...
Click to collapse
Drivers are not GPL'd, these are closed source and the kernel is most likely the same as the mytouch 32B. Drivers are modules that are loaded by the kernel.
Jedipottsy said:
Drivers are not GPL'd, these are closed source and the kernel is most likely the same as the mytouch 32B. Drivers are modules that are loaded by the kernel.
Click to expand...
Click to collapse
This is correct. nVidia and ATI do the same thing with their 3D video drivers on PC. There is no GPL violation here.
Still, I do wish HTC would release all their driver source so people could cross-port ROMs between the Dream/Magic/Hero/Tattoo
Super Jamie said:
This is correct. nVidia and ATI do the same thing with their 3D video drivers on PC. There is no GPL violation here.
Still, I do wish HTC would release all their driver source so people could cross-port ROMs between the Dream/Magic/Hero/Tattoo
Click to expand...
Click to collapse
... they still haven't released the kernel source
kbeezie said:
... they still haven't released the kernel source
Click to expand...
Click to collapse
The link I posted before has all of the ones that are released so far.
Modules are device specific but you should be able to grab them from the stock ROM, given the base number is the same as what you're flashing. Or you could compile them yourself with the sources for your target board.
I don't see any violation here since the kernel is probably the one released as Magic. And even if there is a violation i don't believe anything good would come out reporting it. The last thing we want is making things difficult for HTC and delay any development for their devices. Let's just enjoy what they provide us with as much as possible!
Even if the drivers are modules they would still be linked against the kernel and because the kernel is GPL2 linked in "infectious".
The GPL2 is first and foremost a distribution licence and the linking clause can be worked around by linking the drivers on the phone the first time you boot it up. I believe Ubuntu has some rather nifty tricks for doing this with their Nvidia and ATI drivers.
If HTC is in violation (which I doubt) they should most certainly be reported. If we don't point it out - someone else will and it will be trouble sooner or later.
HTC is in violation in GPL with the Magic 1.2
- Touchscreen drivers are in-kernel. There's no source for these
- While camera and bluetooth drivers are not in-kernel, they have a kernel interface which is not avaible at the moment, so another violation right there. (nVidia and ATI closed source drivers are in the same ballpark - they have a binary blob and a kernel interface that must be open source)
Also, the GPL states that you need to release the kernel so that it can be compiled, as in they can't say that some stuff is in one place, the other somewhere else. At the very _least_ they need to supply a working tarball, so that a compile of that will boot and be usable.
HOWEVER, the code might have been dumped to the aosp source here
I don't own that device so it's not exactly a thing i've been looking over. However, a code dump to the htc developers area is in order.
movikun said:
HTC is in violation in GPL with the Magic 1.2
- Touchscreen drivers are in-kernel. There's no source for these
Click to expand...
Click to collapse
How sure are you about this? Don't get me wrong, but some proofs are needed.
- While camera and bluetooth drivers are not in-kernel, they have a kernel interface which is not avaible at the moment, so another violation right there. (nVidia and ATI closed source drivers are in the same ballpark - they have a binary blob and a kernel interface that must be open source)
Click to expand...
Click to collapse
NVidia at least provides the open source interface and there is no violation there, I'm pretty sure HTC does so otherwise the opensource foundation would already be suing them
Also, the GPL states that you need to release the kernel so that it can be compiled, as in they can't say that some stuff is in one place, the other somewhere else. At the very _least_ they need to supply a working tarball, so that a compile of that will boot and be usable.
HOWEVER, the code might have been dumped to the aosp source here
I don't own that device so it's not exactly a thing i've been looking over. However, a code dump to the htc developers area is in order.
Click to expand...
Click to collapse
At which point does GPL states that the sources should compile out of the source?
Also please note here that there are also many developers in these forums that haven't released any source for their modified kernels.
gbil said:
How sure are you about this? Don't get me wrong, but some proofs are needed.
Because all of the previous ones were in-kernel. I don't have one of these devices, but looking over the rom, i see no obvious .so in /lib that would be specific to the touchpad. If you can see something in the likes of /sys/modules/synaptics then it's in the kernel
NVidia at least provides the open source interface and there is no violation there, I'm pretty sure HTC does so otherwise the opensource foundation would already be suing them
Click to expand...
Click to collapse
It did, for all phones released up to the droid eris (newest code dump from them). Most probably the code from the old magic works, but again, i don't have it, so it doesn't concern me.
At which point does GPL states that the sources should compile out of the source?
Click to expand...
Click to collapse
Paragraph 3, after section c. Here, let me show you
For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable.
Click to expand...
Click to collapse
Also please note here that there are also many developers in these forums that haven't released any source for their modified kernels.
Click to expand...
Click to collapse
If they modified the kernel more than in the configuration, they are required to give the source code IF ONE ASKS THEM TO. Most of them don't go that far, and the ones that do (cyanogen, wes garner to name a few) have their nice own githubs set up. There are some that don't (Sanpei, kingklick), but no one really cares. Please read the GPL carefully next time.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HTC has been a pretty nice company regarding this site and devs. It's possible that if anything is missing that it was either not theirs to distribute, it was reasonable to assume you can find the sources or it was left to the AOSP to release-- specifically developers working on it. Is the Magic kernel on their site not enough? What else do you need?
enatefox said:
HTC has been a pretty nice company regarding this site and devs. It's possible that if anything is missing that it was either not theirs to distribute, it was reasonable to assume you can find the sources or it was left to the AOSP to release-- specifically developers working on it. Is the Magic kernel on their site not enough? What else do you need?
Click to expand...
Click to collapse
It might be T-Mobile's doing seeing as the differences from the usual Magic was made specifically for T-Mobile.
movikun said:
Because all of the previous ones were in-kernel. I don't have one of these devices, but looking over the rom, i see no obvious .so in /lib that would be specific to the touchpad. If you can see something in the likes of /sys/modules/synaptics then it's in the kernel
Click to expand...
Click to collapse
so no proofs here really moving on
It did, for all phones released up to the droid eris (newest code dump from them). Most probably the code from the old magic works, but again, i don't have it, so it doesn't concern me.
Click to expand...
Click to collapse
moving on again
Paragraph 3, after section c. Here, let me show you
Click to expand...
Click to collapse
You haven't quoted the whole paragraph which states that some parts can be excluded from the distribution, maybe that it why it doesn't compile right out of the box?
If they modified the kernel more than in the configuration, they are required to give the source code IF ONE ASKS THEM TO. Most of them don't go that far, and the ones that do (cyanogen, wes garner to name a few) have their nice own githubs set up. There are some that don't (Sanpei, kingklick), but no one really cares. Please read the GPL carefully next time.
Click to expand...
Click to collapse
Mate you are trying to make a point based on your own assumption here. Please check the threads where all these people were asked to give their source code and the most common reply is that they will do it someday somehow. Thus they DO violate GPL. So your last sentence doesn't really make sense. My advice, try to read better what I write and don't concentrate only on what you want to write.
everyone start tweeting nvidiategra to get teh source code
If you cant read it all those tweets say this
You guys need to release the source code for the tegra 2 thats inside the g2x,you guys dont know how to code give it to XDA nOW
Done
10chars
will do
done---hapy to help in any way I can.
Will do when I get on my PC tonight!
Sent from my LG-P999 using XDA Premium App
this should be stickied so eeryone can see it and we get that source code
Pointless. XDA are .2 percent of all users, they don't give a rat's ass. We've been through this on the Epic fora.
Sent from my LG-P999 using Tapatalk
killjoy much
Vendors don't release proprietary driver source code unless you are covered by an NDA. You aren't going to get it. I got Marvell to give me source code once but under an NDA and it was extremely difficult to do and took a long time. Also, since I was under an NDA it which meant I had the code but could not disclose any of it or give it to anyone else, period. Sorry, but those tweets will just be wasted key presses.
sorry, guys, nagging nvida will get you nowhere!
I'm curious as to why people imagine this might happen? Is there a precedent that h/w vendors for Android platforms have released source for drivers? Or released specs (like register maps) for hardware? Some h/w vendors don't even write drivers for h/w - that's what gives embedded C programmers like me job security (I've been involved in plenty of NDAs like mentioned above).
So what is the "norm" for the Android platform?
Maybe, Just Maybe
we can bug the hell out the CIA and find out who killed JFK! Was there really a UFO at Roswell?
You guys need to release the source code for the tegra 2 thats inside the g2x,you guys dont know how to code give it to XDA nOW
Click to expand...
Click to collapse
So you really think that after sending them the above message they are going to say what? "Sure, we know we can't code so here, take all of our hard work and make it work cause we are idiots!" You have a better chance of getting the answers from the CIA.
probably right
dkb218 said:
we can bug the hell out the CIA and find out who killed JFK! Was there really a UFO at Roswell?
So you really think that after sending them the above message they are going to say what? "Sure, we know we can't code so here, take all of our hard work and make it work cause we are idiots!" You have a better chance of getting the answers from the CIA.
Click to expand...
Click to collapse
and we all know the shot really came from roswell not the bush.
But i heard all the same things when people complained about locked bootloaders
they dont care you make up 1/2 a percent etc.
you dont get anywhere without trying.
I think this helped us to get ginger bread... Worth a try.
Sent from my Blue Steel Weapon!
Done I hope this helps
KingDavid63 said:
I think this helped us to get ginger bread... Worth a try.
Sent from my Blue Steel Weapon!
Click to expand...
Click to collapse
Agreed. I posted on Facebook.
hmmm seems interesting
Did you get the source code yet?
hey, head on over to the nvidia developer zone at the link below and post a comment, I'm never going to buy another tegra powered device until they release the HAL source for at the very least the A2DP
Nvidia developers page, thread about opening the HAL
Sad how this is the only thing keeping my phone from being perfect, this too will be my last nvidia device...
Sent from my LG-P999 using Tapatalk
Yeah I think imma leave nvidia alone after this also.
Cross-posting this from the LG G2X Cyanogen forums.
In case you missed it there is now a bounty on issue 4105 aka "no bluetooth stereo". As of this writing it's over $100 and though that probably won't cover the hours it takes to track down the Bluetooth driver and port it, it will buy a few cases of beer to celebrate.
I'd post a link, but I can't yet because I'm a newb - so you'll have to trust me.
Is this even possible??? Would they have to make a driver from scratch??? If it is possible and legit im down for adding to the pot.
It was my understanding that nVidia needed to release the source code for their drivers to get this to happen? I'm not holding my breath on that happening. I would really like to see the Bluetooth issues worked out though.
DECIM8 said:
It was my understanding that nVidia needed to release the source code for their drivers to get this to happen? I'm not holding my breath on that happening. I would really like to see the Bluetooth issues worked out though.
Click to expand...
Click to collapse
..maybe NVidia wants the $100
Anything is possible. It's not easy, and very Time consuming, to reverse engineer drivers.
Sent from my LG-P999
dreggs said:
..maybe NVidia wants the $100
Click to expand...
Click to collapse
Lol that's awesome
That is the pretty ****ty thing about NVidia. If they are going to keep their doors closed then at least provide updated drivers frequently.
Maybe when Tegra 3 comes out they'll release Tegra 2.
I've seen so many devs so so many near impossible things here are XDA that I know someone will crack it. I think they are just being lazy now (which is smart) because why waste time and energy if NVidia will release it shortly? But now that we're finding out that it probably won't happen that hopefully they'll start crackin' on it.
I would add to the pot if someone can provide a link
Sent from my LG-P999 using Tapatalk
player911 said:
That is the pretty ****ty thing about NVidia. If they are going to keep their doors closed then at least provide updated drivers frequently.
Maybe when Tegra 3 comes out they'll release Tegra 2.
I've seen so many devs so so many near impossible things here are XDA that I know someone will crack it. I think they are just being lazy now (which is smart) because why waste time and energy if NVidia will release it shortly? But now that we're finding out that it probably won't happen that hopefully they'll start crackin' on it.
Click to expand...
Click to collapse
That will be next to impossible. Nvidia is not open source friendy.
I think this will work. If many are doubting, better check out hd2 android...
Sent from my Calculator with Android.
To write a driver, you need a register set. Apparently that is part of the IP NVidia isn't up-ing, at least not without an NDA. Without a register set, have fun...
So if you signed the NDA, get the register set description (which may come with sample code), wrote a lib, and posted the lib (but not the source code) here, would that violate the NDA?
I would add to the pot as well. I would LOVE to see this happen.
namklak said:
To write a driver, you need a register set. Apparently that is part of the IP NVidia isn't up-ing, at least not without an NDA. Without a register set, have fun...
So if you signed the NDA, get the register set description (which may come with sample code), wrote a lib, and posted the lib (but not the source code) here, would that violate the NDA?
Click to expand...
Click to collapse
No, that should not violate the NDA. The NDA covers the source code they provide to you to develop your products. The work product is okay to distribute as long as you don't disclose the source code.
I will donate of we find somone that is capable. Maybe we can drag another dev into a g2x as a result as well. Love this phone. Hopefully more will realize its superior smoothness to the crapsation.
Sent from my LG-P999 using XDA App
Ill trow down $30 on the pot.
I would definitely chip in for the bounty as well if someone could get a2dp/bluetooth to work. I've been pretty disappointed with my g2x and it's because of this.
CM_arcee tweeted it is working on 2x, i think we have a2dp thanks to the fine devs here!
http://tinyurl.com/66zc8un
fcisco13 said:
CM_arcee tweeted it is working on 2x, i think we have a2dp thanks to the fine devs here!
http://tinyurl.com/66zc8un
Click to expand...
Click to collapse
Ummmmmm...... wow.
If this is coming out in a CM7 rom soon then where do I sign up to donate!!!!
maciek82 said:
Ummmmmm...... wow.
If this is coming out in a CM7 rom soon then where do I sign up to donate!!!!
Click to expand...
Click to collapse
It will soon be in cm7! CM_arcee is the man to thank/donate.
This will make cm7 complete and my g2x perfect.
fcisco13 said:
It will soon be in cm7! CM_arcee is the man to thank/donate.
This will make cm7 complete and my g2x perfect.
Click to expand...
Click to collapse
In the next release list, a2dp workaround is aready there. Probably come out within the week, maybe tomorrow. Check out the CM7 changelog page of g2x p999.
Sent from my Calculator with Android.
jose makalolot said:
In the next release list, a2dp workaround is aready there. Probably come out within the week, maybe tomorrow. Check out the CM7 changelog page of g2x p999.
Sent from my Calculator with Android.
Click to expand...
Click to collapse
Already used it at work, thanks fits!
Hi all,
Please let us know what you think.
http://www.youtube.com/watch?v=P-q5CEfiyQk&feature=youtu.be
Thanks!
SamsungJohn
Twitter:SamsungJohn
How about release some source or at the very least something that will help devs speed things up with ice cream? We paid for the phone, we want everything we can get.
+1
very interesting...
sign me up Scotty
Somewhat interesting, I have registered on the new Developer site, however it seems to be geared more towards app developers, with little of use to those doing platform work (AOSP bringups including Cyanogenmod porting, kernel development, etc.)
There are no IC datasheets, and no source code for test firmwares such as UCKL2 for the Infuse (SGH-I997).
Stickied for the time being
Thanks for the news. I will check it out to see if it is a good choice for beginning devs. It might also be interesting for me to learn more specifically regarding my Samsung phone.
does it mean,
some people develop ROM or app together?
make money?
you don't make ROM for money, if you do, you don't belong in XDA
AllGamer said:
you don't make ROM for money, if you do, you don't belong in XDA
Click to expand...
Click to collapse
Well said!
AllGamer said:
you don't make ROM for money, if you do, you don't belong in XDA
Click to expand...
Click to collapse
True. But it is a chance to get know and apreciated. And that could lead to money!!!
Entropy512 said:
Somewhat interesting, I have registered on the new Developer site, however it seems to be geared more towards app developers, with little of use to those doing platform work (AOSP bringups including Cyanogenmod porting, kernel development, etc.)
There are no IC datasheets, and no source code for test firmwares such as UCKL2 for the Infuse (SGH-I997).
Click to expand...
Click to collapse
AllGamer said:
you don't make ROM for money, if you do, you don't belong in XDA
Click to expand...
Click to collapse
Very well said! It seem like Samsung have just discovered all the free work force to produce code that is much better than their own. Now they wanna tap into this, without giving anything of value in return.
How about dropping some spec-sheets on the HW level and some source code to their drivers, instead!?
Damnit, i'll have to learn some programming now! To the Batmobile!
+1 for "spec-sheets on the HW level and some source code to their drivers"
..especially for devices like Galaxy 3 (i5800/i5801), which (apparently), you are not going to update now on.
Sounds Cool
sounds pretty interesting, ill check out the youtube video.
Thanks for the news.
Would be nice if the video talked specifically about developing ROMs, especially AOSP-based...
useful info
merge samsung and htc rom?
hi i somewhat enjoy my samsung charge except for the predictive txt sucks i want exactly how the htc has theirs can anyone give me some info on merging these things i want to build or tweak a rom for the charge also currently downloading all the sdk stuff about to run over to samsung dev site and see if i can get into that also.
Great
great stuff, keep up the good work!
Seems like a great initiative from Samsung
Anyone Interested?
As our mobile devices are getting more and more locked-up and harder to maintain, it's is surprising that so little effort has been done in vulnerability research of the Qualcomm Hexagon DSP's. After all, these beasts have been roaming around freely in our phone cores for nearly 8 years already. (In all Snapdragons since 2006). But very few, to none of our security experts have had a good look at what's hiding inside.
So what I propose, is that we start an effort to build an Open Source Hexagon Disassembler for public security research of mobile baseband firmware.
The only effort I know of to this date is that made by Jan Willem Hengeveld (itsme), who wrote an IDA module (here) to the best of his abilities. I don't know what is the current status of that today, but the IDA Hexagon module is now hosted at Github HERE by Ralf-Philipp Weinmann (rpw), who reverse engineered parts of the baseband (shown in THIS video) and recently helped expose the insecurity of TOR hidden-services.
I'm not going to answer why this is important at this point, but I'd rather like to know more about what mobile developers in the security field think about this. Highly technical talk is welcome and preferred.
If you have any additional information on how to do this, or what would be required, please chime in!
E:V:A said:
Anyone Interested?
If you have any additional information on how to do this, or what would be required, please chime in!
Click to expand...
Click to collapse
PUSH! I recommend you to have a chit-chat with developer @c0rnholio, who developed the awesome HushSMS.
That is very interesting topic. I think it will be hard to disassemble the modem/baseband DSP, but it will be easier accessing the multimedia DSP which is open for user programming. There is even a linux project running on hexagon cores
E:V:A said:
Anyone Interested?
Click to expand...
Click to collapse
Hi E:V:A, I'm interested. I sent you a PM regarding a similar project, if you're still interested in this subject PM me.
QCOM proprietary & modem sources.
Type in google/bing:
Code:
AU_LINUX_ANDROID_JB_MR1_RB1.04.02.02.050.175_msm8974_JB_MR1_RB1_CL3847824_release_AU
remittor said:
QCOM proprietary & modem sources.
Type in google/bing: "AU_LINUX_ANDROID_JB_MR1_RB1.04.02.02.050.175_msm8974_JB_MR1_RB1_CL3847824_release_AU"
Click to expand...
Click to collapse
Who am I going to have to buy dinner for and make out with to get the last 42.4% of this file to come through? lol
EDIT: nevermind, got it. Very interesting stuff!