HTC ICS Kernel & Drivers Sources - Android General

Dear All,
Are you as pissed off as I am by how HTC promised for open source and hasn't kept its promise?
I have asked their support line, on their ics blog and were in touch with HTC Officials personally. Never got an answer for that.
So here's an open letter to HTC that I am thinking.
What is the criteria to decide on which phones receive updates in what order, why some phones are given deadlines while others are "sometime later this year"
What happened to HTC's promise for open source? Why do you not release kernel and driver sources for ICS?
Why the unlocking is limited and will you provide a true unlock solution.
If there is enough attention, I would like to use social media to draw HTC's attention.
Who's with me?

Join the crew man! There are several people who are trying to contact HTC daily for these things. Also, a true unlock solution should be on your list!
Sent from my PC36100 using xda premium

hceylan said:
Dear All,
Are you as pissed off as I am by how HTC promised for open source and hasn't kept its promise?
I have asked their support line, on their ics blog and were in touch with HTC Officials personally. Never got an answer for that.
So here's an open letter to HTC that I am thinking.
What is the criteria to decide on which phones receive updates in what order, why some phones are given deadlines while others are "sometime later this year"
What happened to HTC's promise for open source? Why do you not release kernel and driver sources for ICS?
If there is enough attention, I would like to use social media to draw HTC's attention.
Who's with me?
Click to expand...
Click to collapse
Well for the most part the drivers are not theirs to offer as open source. They belong to another company that will never release the source for them. The kernel sources are posted normally with in a fair amount of time.
Alot of time the carriers (For US phones) have more control over the updates then the OEM. Take the Desire HD and the US version the Inspire. The Desire HD has gotten 2 updates, one for a sercurity issue and one for a Sense version update. While the Inspire got nothing.

Give this a read and feel free to post it or add to it and make HTC hear us!
http://goo.gl/3T4NK
Sent from my PC36100 using xda premium

imheroldman said:
Join the crew man! There are several people who are trying to contact HTC daily for these things. Also, a true unlock solution should be on your list!
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I know that I am not the only one. But to draw a big attention we need to get together and today the answer for that is social media. AFAIK, there is no social media group currently to address the issue.
On the other hand, yep you are right, adding the true unlock issue.

zelendel said:
Well for the most part the drivers are not theirs to offer as open source. They belong to another company that will never release the source for them. The kernel sources are posted normally with in a fair amount of time.
Click to expand...
Click to collapse
"Will never release the source code" is a bold statement. 25 years ago one wouldn't think an enterprise would ever release the source codes. But the times changed and the demand from the community got bigger so they were forced to and adopted a new way doing business.
This was a wave in Linux case, first the kernel was open source, now *almost* every driver is now open source, including companies like Intel.. An exception to that would be Nvidia. But with the nouveau project, sooner or later they will start to cooperate. As in Nvidia PC business most of the customers are non-Linux customers that is not yet an issue for them. On the other side, they are too under pressure on the mobile land with their tegra line.
Provided the above is correct, if there were an enough *united* community demand, first the OEMs / Carriers will be on the front line then they will turn to their hardware providers to opensource the drivers.
Correct me if I am wrong but a driver is merely a bridge between the kernel and the hardware, so I really do not get it the reason to keep it closed.
As for the kernel sources, I still do not see and 3.x.x source for devices other then Sensation and One line. ICS was released mid November. I am sure OEMs like HTC got their hands on it before that, so it is over 5 months they haven't released updates. I know that updates aren't produced overnight, yet 5+ months is quite disappointing. So I disagree with "fair amount of time" part.
zelendel said:
Alot of time the carriers (For US phones) have more control over the updates then the OEM. Take the Desire HD and the US version the Inspire. The Desire HD has gotten 2 updates, one for a sercurity issue and one for a Sense version update. While the Inspire got nothing.
Click to expand...
Click to collapse
I don't see the point here. I see the sources for "Carrier's devices" on htcdev.com. So it is not a "being open issue". On the other hand, releasing updated sources and pushing updates to devices I think are not the same things.

imheroldman said:
Give this a read and feel free to post it or add to it and make HTC hear us!
http://goo.gl/3T4NK
Click to expand...
Click to collapse
Great write up! But the main point I am trying to make a *united* move. So with all the respect, a blog shouldn't be the point to gather up. Having said that a text like your's would constitute the detail of the open letter I am envisioning...

Feel free to use it, the quote in the middle is from toastcfh, the rest is mine. I am fully behind what ever move there is to get HTC to really unlock their phones and give true open source codes. They are putting up a front to developers that they are friendly but the process is so hindered we have to rely on leaks and crazy s-off methods, and even with source you can no longer flash a kernel or boot image with our a pain in the neck. There are plenty of people who want these things and we do need to approach HTC as a community!
Sent from my PC36100 using xda premium

Been spamming them on Twitter already for weeks. Bloody HTC, I hate them now
Sent from my HTC Desire S using xda premium

imheroldman said:
There are plenty of people who want these things and we do need to approach HTC as a community!
Click to expand...
Click to collapse
That's the spirit we need!
Now I am not %100 knowledgeable about XDA rules. Would it be OK to post a link to this thread to every HTC device Android forum?

Related

Lets put the pressure on nVidia [UPDATED 10/07]

Hy guys and gals, i have done some digging on the nVidia developers forums and have found a thread requesting info on if/when nVidia plans to drop the source for the HAL that we need so our amazing developers can get A2DP working
I'm posting the link below, maybe if enough of us go into the thread requesting this info nVidia will comply
EDIT: nVidia updated their forum and our topic was tossed into the archive and not brought over, to remind them that this is still a valid issue I have re-created the thread, please if you want to try at getting A2DP to work with non OTA based rom's go voice your opinion
New nVidia developers Forum
Sent from my Transformer TF101 using XDA Premium App
Link not working, im all for it a2dp would make cm7 perfect.
This would be great! Then I could finally buy a Bluetooth Stereo Headset.
Sent from my LG-P999 using XDA Premium App
I'd love to see this happen, but I don't see it anytime soon. Nvidia has been historically bad at releasing their source code.
fcisco13 said:
Link not working, im all for it a2dp would make cm7 perfect.
Click to expand...
Click to collapse
Link worked perfectly fine for me, both on my TF101 earlier and just now on my g2x.....not sure why it didn't work for u
Sent from my LG-P999 using XDA Premium App
Lets get this moving
Sadly, they aren't required by any license to release their source code, which is why I have no idea if/when it'll ever happen. Their drivers for their own chips are definitely not gpl, so bugging them will not put any pressure on them at all.
lawsuit??? Lol worked for lg...
It'll never work. You can't sue them because they won't release their source code. That's like saying "Hey let's sue microsoft because they won't release the source to their kernel." It's their property, and they can do what they like with it. If android didn't run on top of the linux kernel, which is gpl licensed, I'd almost guarantee that no vendor would ever release the source for it.
Not trying to be a buzz-kill or anything, I want the source code as much as anyone else. But no amount of threatening lawsuits, bugging them through email, forums, or phone calls will change their minds. If they intend on releasing the source, they'll do it in their own time, if not, we're SOL.
mstrk242 said:
Sadly, they aren't required by any license to release their source code, which is why I have no idea if/when it'll ever happen. Their drivers for their own chips are definitely not gpl, so bugging them will not put any pressure on them at all.
Click to expand...
Click to collapse
Then it is probably a bad move to use Nvidia hardware on an open source platform like Android.
Spread the word...
I was kidding about it, we can wait for 2.3.4-5 ota...
It may be Nvidia's right to keep it's code proprietary, but I can't imagine buying another Android device with one of their chips in it unless something changes.
We are evolving very fast, I don't know if nVidia can assume the Windows GPU market will always be there for them. If Android dominates the next decade or so the way that Windows did the last then manufacturers are obviously going to have to adapt or perish.
No way, there will always be a market for high end video cards on windows, simply for gaming if nothing else. Sure, they may not make it in the cell phone market (although I doubt that too, just because they are very good with hardware, they'll work out the kinks.)
You have to remember, the vast majority of people who buy these phones don't even know what a rom is, let alone the fact that they can customize it. The modding community is a small (albeit very vocal,) minority.
Also, please no one read between the lines on these posts I've made. I'm no insider, I have no information what so ever from nvidia. I'm really only basing these educated guesses based on my experience with nvidia and linux drivers. They may very well open the source, but I'm just trying to say don't hold your breath, and screaming at nvidia is absolutely pointless.
bump for updated link
None of the companies release their proprietary drivers to the public. It is their right as the intellectual property owner to keep it secret. The only thing that is open source is the Android Kernel and the AOSP files. Everything else is proprietary and not made public. Even Google Apps are proprietary and Google never releases the source code for them. Also, only members of the Open Handset Alliance can license them and legally put them into their rom builds. Any efforts contrary to this (i.e., getting companies to release proprietary driver source) is simply futile and a waste of time. They could care a rat's ass about hackers. If you don't like it don't buy their products, but then you have to stop buying everyone's product as they all have proprietary code that is never released.
Spyvie said:
Then it is probably a bad move to use Nvidia hardware on an open source platform like Android.
Spread the word...
Click to expand...
Click to collapse
You are right-on here. I will be looking at this when I eventually upgrade down the road, and will probably select a lesser device with different hardware (as long as the manufacturer doesn't ship it with a locked bootloader - lol).
Real open source is the only way to go. But as many posters have mentioned. we represent a very small group of potential customers - most whom would never dream of messing around with their devices.
gaww said:
You are right-on here. I will be looking at this when I eventually upgrade down the road, and will probably select a lesser device with different hardware (as long as the manufacturer doesn't ship it with a locked bootloader - lol).
Real open source is the only way to go. But as many posters have mentioned. we represent a very small group of potential customers - most whom would never dream of messing around with their devices.
Click to expand...
Click to collapse
Then you want to get the MI Millet MIUI phone when it is available in your country. It is a dual core 1.5Ghz Scorpion processor and they expect you to update it weekly with new MIUI builds. It is an awesome device for the low price point (1,999 Chinese Yuan or about $300.00 US).
http://product.xiaomi.com/features.html
Go salivate.
jboxer said:
None of the companies release their proprietary drivers to the public. It is their right as the intellectual property owner to keep it secret. The only thing that is open source is the Android Kernel and the AOSP files. Everything else is proprietary and not made public. Even Google Apps are proprietary and Google never releases the source code for them. Also, only members of the Open Handset Alliance can license them and legally put them into their rom builds. Any efforts contrary to this (i.e., getting companies to release proprietary driver source) is simply futile and a waste of time. They could care a rat's ass about hackers. If you don't like it don't buy their products, but then you have to stop buying everyone's product as they all have proprietary code that is never released.
Click to expand...
Click to collapse
Not refuting what your saying but why do other phones seem to not have this problem if they all do this. Only tegra 2 devices have development ****ed because of this.
Sent from my LG-P999 using xda premium
They deleted my account. WTF?
xsteven77x said:
Not refuting what your saying but why do other phones seem to not have this problem if they all do this. Only tegra 2 devices have development ****ed because of this.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'd imagine its for the same reason our devices and other tegra devices can only play the tegra games hence incentive tobuy a tegra phone. I think if they released code then any dev could hack their phone and play tegra games without having a tegra chip. Just a hunch.
Sent from my LG-P999 using XDA App

[REF]Help To Release Kernel Source Code (Released 10/19/2011 Thanks to all!)

We need to bomb HTC's website with comments to encourage them to release the kernel source code for our device. I suggest we all go to the following link daily and request its release;
http://htcdev.com/contact
HTC just sent me a link to take a survey, another good tool to blast them with.
http://survey.htc.com/worldwide
Code has been released, I like to think all our complaints helped. Feel free to lock this thread if need be!
http://www.htcdev.com/devcenter/downloads
We have been. I've sent them several notices on a near daily basis.
Sent from my myTouch_4G_Slide using xda premium
I doubt that that link is anything more than a placebo.
http://www.htc.com/us/about/contact-by-email
Say something along the lines of "you're in violation of GPLv2 which requires that source be released along with binary. GPLv2 does not allow for anything besides release of source NOT being ANY LATER than binary distribution."
I.e., though GPLv2 doesn't specify an exact time frame, the implication of this is that the source must be made available by the EXACT MOMENT that the binary is distributed. It *does* allow for the source to be released BEFORE the binary, but does NOT allow for the binary to be released before the source.
IMO, the kernel source archive should be included within the system partition of the phone, at least for early releases while there is sufficient storage space for it all to fit. This would greatly simply source distribution.
Even though I went to that page and asked for the kernel source code to be released, it looks like they're on a pretty routine schedule as far as what and when they release things and we're probably still a little ways out on the source code. But it can't HURT to keep trying, right?
Submitted. Hopefully they'll listen up.
BiggJurk said:
We need to bomb HTC's website with comments to encourage them to release the kernel source code for our device. I suggest we all go to the following link daily and request its release;
http://htcdev.com/contact
Click to expand...
Click to collapse
Yeah, we have been. As unclespoon said they are on a fairly set release schedule that they must be comfortable with [legal-wise].
Read my replies here, there is another link that got me a response that was from a human:
http://forum.xda-developers.com/showthread.php?t=1247374
HTC does this **** on purpose. They have a bunch of new devices coming out and if they were to release the code that would impact there profit margins. This processor can handle 1.5 ghz as a daily driver. The new HTC amaze has exact same processor but is overclocked 300mhz more then our device. And it has a 1gb of RAM. Samsung has gotten great at releasing there code within 1 week or even earlier. HTC PLEASE TAKE NOTES FROM SAMSUNG.
Sent from my myTouch_4G_Slide using xda premium
FYI
I filled out a customer service survey from HTC and gave them all bad ratings in regards to their non-response for the kernel source code. A representative just personally called me and is trying to get an eta on the release if not email me a copy of the code. I would suggest everyone completes a survey with negative comments at the following location:http://survey.htc.com/worldwide. I know surveys like this affects their metrics and gets managements attention. The guy on the phone also said that Android is released under the Apache license agreement.
Regards,
Filled out the survey.
Let's see if they respond.
cal3thousand said:
Filled out the survey.
Let's see if they respond.
Click to expand...
Click to collapse
I think it took them 2 weeks to get back to me.
BiggJurk said:
I think it took them 2 weeks to get back to me.
Click to expand...
Click to collapse
My guess is that they'll "get back to you" in a month or however long until they would have normally released the source code. I think they're too big to be bothered by people complaining about lack of source code. Bottom line is there probably won't ever be any "consequences" as a result of them taking their time on releasing kernel source. We only complain because we want it, but it's not like they are really doing anything wrong by just releasing it on their own schedule.
BiggJurk said:
The guy on the phone also said that Android is released under the Apache license agreement.
Click to expand...
Click to collapse
I've heard that before, but I don't see how that's possible since Android is based on Linux. If it were based on BSD that'd be another matter.
BiggJurk said:
The guy on the phone also said that Android is released under the Apache license agreement.
Click to expand...
Click to collapse
Wow, congrats to phone guy!! Unfortunately, either he was trying to get you to shut-up or misunderstood what you wanted them to release. Google mostly licensed Android with the Apache 2.0. This allows others to customize Android and they don't have to release their changes i.e. customizations made by phone manufacturers (it means other things too but this was Google's main reason for this license). HTC doesn't have to give us their Android source. The Linux kernel is GPL - there is no way around that. The GPL states that the source must be released at the same time as the binary is released to the end-user (it even states that the source should be no harder to obtain than the binary is i.e. we should get the kernel source with our devices - on the sd card or something). Still have no idea where HTC gets 90-120 days from the GPL wording.
I sent a note to EFF asking if they were aware of whats going on. They said they were and were researching the situation.
---------- Post added at 06:50 PM ---------- Previous post was at 06:37 PM ----------
unclespoon said:
but it's not like they are really doing anything wrong by just releasing it on their own schedule.
Click to expand...
Click to collapse
They are though. They are directly violating the GNU GPL but you are right - there are too few of us who actually want the kernel source for them to really worry. Can't believe one of the actual Linux kernel devs hasn't caught wind of this and made a statement.
I sent a couple of requests. Let's hope they move their asses.
Source has been released:
http://www.htcdev.com/devcenter/downloads
HebrewToYou said:
Source has been released:
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
I think you were the first one to find it. I thanked you elsewhere you've mentioned it as well.
Maybe the OP can come through and update the thread title.
Edit to add - download reads 94.0MB on the HTC page, but my download over Tmo 4g is saying out of 89.6MB and my home pc is saying 89.7MB...so we'll see what's up when I get it.
YES!!! Time to OC this bad boy..
Please get on it Devs..!!!
RazoE said:
YES!!! Time to OC this bad boy..
Please get on it Devs..!!!
Click to expand...
Click to collapse
All ready on it
Sent from my Senseless Doubleshot using xda premium
That's funny.
I just received the HTC reply to my request. I'm going to play like my request was the straw for that camel's back... Your Welcome Everybody!!!
j/k. This is wonderful news though. I'm stoked
Thread locked by OP request

HTC delaying on posting kernel source code

So I've been attempting to get HTC to comply with the GPL license and release the source code for the One S (one x needs it too), and I got the standard 90-120 day response. However, this isn't acceptable, as that's 90-120 violations of the GPL license, which requires that they provide it to you upon request, not "in 90-120 days".
I've responded to them again, reminding them of their duty to lawfully abide by the terms. I urge each of you to do the same, and in a calm, collected manner.
I'm not sure where your open source community requirements came from, but with all due respect, 90 to 120 days is not acceptable. I think it's important that I point out to you HTC's lawful obligation to abide by the terms of the General Public License (GPL) v2, as the Linux kernel that HTC uses for its Android phones requires that HTC release its source code immediately. As this device has now been released in at least 2 countries, HTC must follow that obligation, and in a timely manner. 90 to 120 days is in no way a timely manner, and accounts for a significant percentage of the device's realistic life as a current HTC product.
If you'll note in the GPL v2 License, there is no 90-120 day grace period for releasing source code. If HTC has provided the Linux kernel binary to any single customer (in this case, it has been delivered via many HTC One S's), then HTC is obligated to provide a copy, upon request, of that specific source code (in this case, the T-Mobile USA HTC One S). Section 3 of TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION makes clear note of these terms.
HTCdev.com has been a definite improvement on HTC's stance regarding source code distribution and openness, but there is much work that is needed to be done. In particular, the timeliness of providing source code is still troubling. HTC makes great phones, but still has a duty to the open source community. There is certainly something to gain by abiding by these terms and distributing the source code to the community. Many technology enthusiasts and developers are eager to get their hands on the code and make their own improvements. The HTC One V model, which has been released alongside the One S and One X, already has its source code posted on the HTCdev website. However, the One S and One X (all variants) are STILL lacking, and each day that HTC delays is a willful violation of the GPL.
I respectfully request that you release the source code for my device in a timely manner. It would be in the best interests of both HTC and the open source software community, and can only serve to strengthen HTC's relationship with the community.
Thank you kindly.
Click to expand...
Click to collapse
Well, looks like they're eager to play ball, and I don't mean that in a good way. Any of you EU folks care to remind them that the device has been out over a month over there across the pond? The more pressure the better.
Dear Nick,
I appreciate your input concerning the availability of the kernel source codes for our Android devices. I realize that you are eager to get the source code for your device; but this device is a recent release in the US market. I would recommend you keep an eye on the HTC Developer website for further source code release information.
Click to expand...
Click to collapse
well written that !!
Mind if i copy and paste it ? and re send it to them ?
Sure, my letter is "open-sourced" . Feel free to modify and make any improvements. They're trying to use the excuse that it's a recent release, yet you EU guys have had it for several weeks now, so I'm interested to see how they'll respond to you. Make sure you use your EU model in your letter.
The thing that kills me is that they think that 90-120 days is acceptable. That's 3-4 months. In 3-4 months, HTC will already be over 50% complete with some sort of new phone, and the One S will no longer be in its youthful stages. When a phone lasts you 2 yrs on average, 90-120 days is a significant period of time. One of the things that attracts developers to a phone community is the availability of the source code. Until then, interest will continue to remain what it is now.
Oh man, my first post here. Coming from a Legend, stuff's new
So, I guess I'll translate that WoT and write it to the german HTC Support, let's see their response!
bump.
bump. maybe we could get this stickied until they release the code? Its currently a major development issue.
How long does HTC usually need to respond? Sent my request yesterday, let's hope they'll get the code to the devs as fast as possible ._.
I received a response in about 2 days.
phin586 said:
I received a response in about 2 days.
Click to expand...
Click to collapse
Telling you to please wait 90-120 days? If so, respond back, remind them every single day is a willful violation of the GPL license. If they've distributed the kernel in binary form to ANY SINGLE CUSTOMER (as it is on the phone), then they're obligated to provide the source code for that specific binary. And we've got plenty of binaries out in the wild, in both the EU and US, and under multiple versions.
HTC is playing games once again, and their approach to developers is once again becoming a joke. I don't understand what's so difficult about following the rules.
Sometimes they'll even play the "it's not in a readable format" card. Only problem there is -- if it's not readable, then how on Earth did they develop it? It's gotta be readable in order to make it in the first place.
Let's see what the german support has to say about this
I'd love to see my One S being S-Off. I want that stock ICS
@nickmv, Of course I did. Hopefully it helps.
---------- Post added at 11:31 PM ---------- Previous post was at 11:26 PM ----------
Oh. I also reported the violation to gnu.org
I suggest you all do the same.
http://www.gnu.org/licenses/gpl-violation.html
bump.
Keep hammering them, folks.
nickmv said:
bump.
Keep hammering them, folks.
Click to expand...
Click to collapse
Someone needs to link this thread in the one X forum
Sent from my HTC One X using XDA
Once I get my hands on my very own One S tomorrrow I will contact the Dutch HTC. Even though I dont dislike sense at all development is in everyones best interest!
Sent from my GT-S5660 using XDA
Ah, my generic reply...
Thank you for your reply. I understand your concerns with the situation John, but rest assured that we will release the kernel source within 90 to 120 days John. We thank you for your patience while awaiting the sources to be posted, and thank you for being a part of the HTC community.
If this answers your comment or question, please click here to complete the process.
To submit another comment, please click here.
Sincerely,
The HTCDev Team
Click to expand...
Click to collapse
Ok so i emailed them yesterday and this is their reply
Thanks for contacting HTC.
Reagrding your email about One X kernel source code, HTC are currently in the process of providing the HTC One X and One S Kernel Source Codes via the HTCDev website.
We have already uploaded the One V code and hope to provide the One X and One S very soon. Please keep checking the HTCDev site, http://htcdev.com, over the coming weeks for the source codes you are after.
I hope this information meets with your approval, please don't hesitate to reply if you require further assistance.
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Jason
HTC
Click to expand...
Click to collapse
I have replied to that above message with this.
Thanks for the quick reply, However i do not understand why it is taking HTC so long to release this, The One S has been available for several weeks now, It was released before the One V and yet the Kernel source code for that phone is available.. The android community is open source, And with HTC delaying the release of the source code is breaching the conditions mentioned in the GPL. You have the code otherwise the phone wouldn't have been released, So why cant you just release it immediately? Why are you delaying it ? The longer HTC hold it, The slower development for this device is, Which is not fair on people like me who want to speed development up for this device. Telling me that the codes will be released 'in a few weeks' is barbaric I would like an estimated time frame. The main thing i want to know is why you haven't released it already. Thank you
Click to expand...
Click to collapse
EDIT: Their reply to the above is:
Dear aaron maher,
Thansk for your reply.
I do appreciate your need for this data, but am not permitted to enter into speculation or personal discussion.
We have to wait for the Dev teams to upload it to the website, I can only apologise this is causing you frustration.
Please be assured, it is something there working towards and will be avaiable there soon.
Click to expand...
Click to collapse
I find that extremely rude ! dont you ??
azzledazzle said:
Ok so i emailed them yesterday and this is their reply
I have replied to that above message with this.
EDIT: Their reply to the above is:
I find that extremely rude ! dont you ??
Click to expand...
Click to collapse
Absolutely. Gotta remember, half of this is complete bull****. At least they're not going overboard and pulling the "it's not in readable format" crap.
azzledazzle said:
Ok so i emailed them yesterday and this is their reply
I have replied to that above message with this.
EDIT: Their reply to the above is:
I find that extremely rude ! dont you ??
Click to expand...
Click to collapse
Yes, quite rude, I assume this person is the Jason who replied your first email. He must have not been trained properly regarding what customer satisfaction means nor how to reply in a professional language without copy/paste existing answers.
However, just don't piss off because of this, I have had the "honour" to visit one call centre (not HTC) and chatted to the senior manager in CS department and the front line support staff. It is a common problem that the front line customer service staff most of time do not know exactly what they are talking about nor have enough knowledge to answer non-standard question. I assume the team replying email is the same. So basically unless they ask their manager your question, you won't get satisfied answer. However, they won't because it will show that they are lack of knowledge and directly affect their appraisal.
Shame... but do send email to them so they will eventually understand how to satisfy this question.
Keep hammering at them guys!

Request to Release Kernel Source; HTC's Response

I sent a request to HTC regarding their timeframe for releasing the kernel source code for the ATT/Rogers One X. This is,what they said:
"I love customizing my device and I will be glad to advise you regarding the source code for the One X. HTC will typically publish on http://developer.htc.com or htcdev.com the Kernel open source code for recently released devices as soon as possible. HTC will normally publish this within 90 to 120 days. This time frame is within the requirements of the open source community."
Looks like we have a while to go gang! Fortunately we some resourceful folks here that make magic happen with available information!
Sent from my HTC One X using xda premium
90-120 days - is "as soon as possible"??? HTC, you do realize that time frame is 1/4 - 1/3 of the year, right?
IMO the strategy here is by that time a new device will be born and people would forget about old one...
This may be a stretch, but it could also be that they want to give users a time to use the device as is in order to discover any bugs that may be present and would need to be patched in a future update. No one is more adept at finding bugs than users...thousands of them.
Tell them that is a complete lie.
The HTC Sensation received the ICS source code within 15 days of its release. They got the ICS update on the 16th and they received the source code not long after.
Read what I wrote to them
http://forum.xda-developers.com/showthread.php?t=1679112
Hey Guys, we are working on the same issue in the Desire C community. I see you have plenty of custom ROMs, but let me ask if HTC has released the full source for you, and if yes how did happen, what was the process?
Thanks a lot in advance, I'm really curious about your case. Click on my signature if you want to see our email thread
And actually, we are currently sending organised emails to HTC, if you have a couple of minutes free it would be a huge help if you sent some of our templates to them.
Here are the details:
http://forum.xda-developers.com/showthread.php?p=40051652
Thank you and see you later!
neoyoli said:
Hey Guys, we are working on the same issue in the Desire C community. I see you have plenty of custom ROMs, but let me ask if HTC has released the full source for you, and if yes how did happen, what was the process?
Thanks a lot in advance, I'm really curious about your case. Click on my signature if you want to see our email thread
And actually, we are currently sending organised emails to HTC, if you have a couple of minutes free it would be a huge help if you sent some of our templates to them.
Here are the details:
http://forum.xda-developers.com/showthread.php?p=40051652
Thank you and see you later!
Click to expand...
Click to collapse
I believe we have source for all Jelly Bean bases except AT&T.
My guess is that HTC pays no attention to these petitions and letter-writing campaigns.
It's a bit more complicated in our case, since we don't have very experienced devs, and did not even know what was going on with our kernel, and we started to roll the issue up only recently, partly due to the info we got from HTC through our emails. They are more communicative now and the case got escalated, thanks to the community effort
HTC sometimes wait up to 90days(or slightly over) to release source code.
It would be an extremely rare case that after 90 days source is not released.
HTC appear to prioritize source releases based on the sales volume of the device. The more a device sells, the faster its source tends to arrive.
Also similarities in hardware to existing devices also seems to help. The newer never before seen platforms tend to take longer.
High end phones always tend to get more love.
You have source for 4.0(2.xx ROM's), what source are you waiting on?
Has you device received 4.1? If so when? Has it been 90 days yet?
Last I head Desire C will not receive Jelly Bean from HTC due to 512mb RAM. I just checked numerous of the carriers and none show updates for 2.00 ROM's, the 2.00 have source released.
You are right, we ruled out the possibility of the official JB. Although some say it would be even faster, but I'm not expert on this. What I understood so far is even if it is so, they are not doing it because it is an entry-level device. Fair enough (well, given the conditions), we can do it for ourselves.
The problem is the WiFi driver "ath6kl_sdio.ko", it fails to compile with any other ROMs then a Sense-based. It creates the folder but will be empty. However we are trying to patch it atm, and some more experienced devs joined recently.
What we still don't know is, that there might be a problem with the source of which HTC might not even aware of, since they did not test it with custom ROMs, and atm they say (in a credible, non-brush-off manner) the source is full, but escalated the case further. So we are waiting for that as well.
So things just started to cook lately. Actually if you have an experienced kernel dev, it would be a huge help if he could look into our source and tell what is going on with it:good: So that we can communicate it effectively to HTC or maybe even solve the issue directly.

90 day marker - ICS Source code!

OK HTC ITS BEEN 90 DAYS, YOU KEEP SAYING YOUR SORRY FOR A CRAPPY PHONE HOW ABOUT YOU REDEEM YOURSELVES AND RELEASE THE DAMN SOURCE CODE NOW?
im just saying....
Patience. They can't release until its been 90 days since ota. Now that it has been 90 days they can but it doesn't mean they will. They can wait however long they desire. All I know is were getting closer.
Sent from my HTC Thunderbolt
ang1dust said:
OK HTC ITS BEEN 90 DAYS, YOU KEEP SAYING YOUR SORRY FOR A CRAPPY PHONE HOW ABOUT YOU REDEEM YOURSELVES AND RELEASE THE DAMN SOURCE CODE NOW?
im just saying....
Click to expand...
Click to collapse
It will be OK there Catwoman.
Sent from my Infected HTC Rezound using Tapatalk 4 Beta
Its 90-120 days people.....
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Its 90-120 days people.....
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
They have 45 more days. They will drop the source. But when the update went out they said 45 days to complete. Add that to the 90 by law.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
People, there is no 90-day "rule". Why do people keep repeating this like it's a fact ?
hallstevenson said:
People, there is no 90-day "rule". Why do people keep repeating this like it's a fact ?
Click to expand...
Click to collapse
I think the point is HTC is trying to position themselves as "developer friendly". I'm not sure what the rules are, but it seems pretty unfriendly for them to withhold the code for this long. If they want to be seen as developer friendly, let them start releasing code for all devices at the same time as the OTA, or at least within a couple weeks. I can see them pointing fingers at Verizon for months of delay on the OTA, but delaying the release of the source code is on HTC. It just seems mean spirited as well.
If HTC really wants to indicate they are sorry for how Thunderbolt issues have been handled, they should release the source code.
hallstevenson said:
People, there is no 90-day "rule". Why do people keep repeating this like it's a fact ?
Click to expand...
Click to collapse
HTC is the one that stated that they can wait anywhere for 90-120 days to release their source code to ensure it is of the utmost quality. So all this repetition of it is merely because they made that statement. In response to the other quote about them about adding another 45 days because of the second update. I don't think that they will reset since the second update didn't do anything to the kernel at all.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
HTC is the one that stated that they can wait anywhere for 90-120 days to release their source code to ensure it is of the utmost quality.
Click to expand...
Click to collapse
They clearly don't give a sh*t about the GPL as it doesn't allow 90 days or 120 days and that's all that really matters. When they say they can wait any period of time, they're effectively telling people "we'll do it if we feel like it".
Source will be available when HTC decides to publish it. Counting down the supposed days until release won't accomplish anything, nor will creating threads like this one and beating the topic to death. If one wants source, he or she would be better served by harassing HTC on Twitter, Facebook, Reddit, etc... Source will eventually be released though, that is certain...
Go to the link in this thread and ask them directly.
http://www.forums.infectedrom.com/showthread.php?p=74402
Sent from my ADR6400L using Tapatalk 2
There is no 90 day rule. The GPL requires release of source at the same time the binary is distributed, no ifs, ands, buts.
One of these days, a kernel developer (i.e. someone who holds copyright on part of the kernel) is going to sue them, win, and they will never be able to use the kernel again, per the terms of the GPL. HTC is playing with fire, since a significant part of their business requires use of the Linux kernel.
"You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. "
The GPL provides NO mechanism to regain those lost rights.
The kernel for the thunderbolt contains proprietary information that relates to the svdo technology therefore they can wait.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The kernel for the thunderbolt contains proprietary information that relates to the svdo technology therefore they can wait.
Click to expand...
Click to collapse
No, they can't. You obviously haven't read, or don't understand, GPL2. If they modified the kernel, or linked to it for "the svdo technology," they still have to release it, and that code is not proprietary, but also falls under GPL2.
"when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
Some light GPL reading and an explanation about the "free" parts of Android and the "non-free" parts.
Check it out!
Excerpt from the article:
Important firmware or drivers are generally proprietary also. These handle the phone network radio, WiFi, bluetooth, GPS, 3D graphics, the camera, the speaker, and in some cases the microphone too.
On some models, a few of these drivers are free, and there are some that you can do without—but you can't do without the microphone or the phone network radio.
Click to expand...
Click to collapse
mike.s said:
No, they can't. You obviously haven't read, or don't understand, GPL2. If they modified the kernel, or linked to it for "the svdo technology," they still have to release it, and that code is not proprietary, but also falls under GPL2.
"when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it."
Click to expand...
Click to collapse
The code related to svdo is a non free part. You will notice that the rezound also suffers from the same waiting period as the bolt since it to has svdo.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The code related to svdo is a non free part. You will notice that the rezound also suffers from the same waiting period as the bolt since it to has svdo.
Click to expand...
Click to collapse
So what? It may make a difference to what developers are able to do with it (e.g. kernel without the proprietaries doesn't allow a working system to be created), but it doesn't in any way remove their obligation to release the kernel source at the same time they release the kernel binary.
And, I'll admit I don't know how the kernel and the svdo stuff interact. But basically, if it's linked to the kernel (vs. working in userspace), then it's not non-free, as it is required to be released under GPL.
mike.s said:
So what? It may make a difference to what developers are able to do with it (e.g. kernel without the proprietaries doesn't allow a working system to be created), but it doesn't in any way remove their obligation to release the kernel source at the same time they release the kernel binary.
And, I'll admit I don't know how the kernel and the svdo stuff interact. But basically, if it's linked to the kernel (vs. working in userspace), then it's not non-free, as it is required to be released under GPL.
Click to expand...
Click to collapse
Sue them then and quit *****ing because they wait 90 days to release source code. Since you obviously know more about the gpl than those of us who work with the stuff then you should even take the lead and make the case for the rest of us. Radio technology is in the kernel or else the antennas wouldn't work. Since this device has svdo technology that is proprietary to Verizon and HTC then yea I would have to say that is a non free license. At any rate go file complaints with HTC and the gpl. It has already been don and it won't do you any good. Have fun with that.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Sue them then and quit *****ing because they wait 90 days to release source code. Since you obviously know more about the gpl than those of us who work with the stuff then you should even take the lead and make the case for the rest of us. Radio technology is in the kernel or else the antennas wouldn't work. Since this device has svdo technology that is proprietary to Verizon and HTC then yea I would have to say that is a non free license. At any rate go file complaints with HTC and the gpl. It has already been don and it won't do you any good. Have fun with that.
Click to expand...
Click to collapse
For someone who works with "the stuff," you're pretty clueless as to how it works. Maybe you should lay off "the stuff" for a while.
mike.s said:
For someone who works with "the stuff," you're pretty clueless as to how it works. Maybe you should lay off "the stuff" for a while.
Click to expand...
Click to collapse
Whatever you say chief. I'm guessing you've compiled some kernels and looked through kernel source. I guess we should take your lead and just whine about it the same thing that has plagued the bolt since day one some more just like you seem to do. Quit worrying about the day that kernel source drops and let those that are actually going to do something with the source do the worrying. You clearly don't understand that there is proprietary code in the thunderbolt source code which allows HTC to take their time with the release. I suppose you know that since you are so well versed in kernel source code though....
Sent from my ADR6400L using Tapatalk 2

Categories

Resources