Hey everyone. So, kernel source isn't out yet. That is a bit disturbing to me... So because of the sheer popularity of this device, everyone submit a request for all models of the m8 Kernel source. A forum letter would be as follows
Hello, my name is _____. I own the HTC one M8. As required by copyright law, htc is required to release the Linux kernel source code the day of release. The lack of kernel source is therefore breaking copyright laws, and I hereby request all Linux kernel sources be released for all released models of the HTC One M8. Many people desire this kernel source. These are all your paying customers too.
thank you, (name)
Now another thing to know is they will likely tell you "htc releases all legally required sources" do not take this answer. Require that your case be elevated, and help us get the development going properly.
Link:
http://www.htcdev.com/contact
EDIT:
GPE leaked sources:
http://www.androidfilehost.com/?fid=23329332407583185
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Actually the exact wording is released along side of the release of a kernel. I have talked with many Linux kernel maintainers who all agree this is equal to the same day. (Linux Kernels are my specialty, as such I've met great people along the way who worked very close with Linus)
Sent from my C525c using Tapatalk
123421342 said:
Done. Just FYI, the GPL requires you release the code in a reasonably timely manner, not the day of release.
Click to expand...
Click to collapse
Not only that it's not release day yet, official release is somewhere in April no?
xReaper7x said:
Not only that it's not release day yet, official release is somewhere in April no?
Click to expand...
Click to collapse
Release date was Tuesday. For sprint, AT&T, Verizon, gsm unlocked and the developer edition. Google play is 2 weeks from last Tuesday. Other carriers come on at different times.
Sent from my C525c using Tapatalk
This par for the course with HTC. They have never been good about releasing kernel source in a timely fashion.
According to the GPL, kernel source must be available as soon as the accompanying software is in use by the public. The "in a timely manner" aspect provides some flexibility in delivering the source, as far as distribution. Within 24 hours is acceptable, time to upload the file and make it available on the site. It needs to be available day 1. 90-120 days later is not even close to complying.
What's even more annoying than having to wait, is that there is absolutely no reason to hold it back. They obviously have it before the device is released. All they do is annoy their LOYAL customers. It's just stupid and bad business at this point.
Sent from my HTC One using xda app-developers app
Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.
BenPope said:
Surely it's not copyright law, but the licence under which the Linux source is released, i.e., GPL v2.
Click to expand...
Click to collapse
The GPL license is a form of a copyright. This makes it part of copyright laws
Sent from my C525c using Tapatalk
thats the only thing stopping me from going back to HTC.. they are horrible at releasing kernel source.. sad cause i have seem many users and kernel devs leave HTC because of this issue..
it will come in time. we don't even have s-off yet.
Pretty sure they have 90 days to comply
~Jflteusc runnin' latest Carbon Nightly
Latest KToonsez Kernel 2.1;189;480
Pegasusq
Row
Thermald:
Mpdecision:
You don't need soff to unlock. Just a unprotected unlock partition or one that's exploitable
Also they do not. If you don't agree ask any Linux mantainter. Most even see it offensively that oems do this
Sent from my HTC M8WHL
Done.
Sent from my 831C using XDA Premium 4 mobile app
The phone hasn't even been out a week... Kernel source for the M7 has been released releatively quickly after updates.
The phone has been out for 5 days...
Sent from my HTC One using Tapatalk
That doesnt matter. Kernel source should be released within 24 hours of it being public.
HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.
flar2 said:
HTC always releases source immediately for the Google Play Edition, which means a couple weeks. They always take forever to release source for their Sense kernels.
Click to expand...
Click to collapse
Google told them that they had to do that if they wanted to call it a Google play device. It may be something we can work with. Let's hope that HTC senses, no pun intended, the desire.
Sent from my HTC M8WHL
MassStash said:
Pretty sure they have 90 days to comply
Click to expand...
Click to collapse
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app
c5satellite2 said:
Pretty sure that is stated NOWHERE in the GPL.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh for sure, definitely not in the stated license, not sure where the hell I heard that. Then n that note, 1) really pain in ? there isn't a time frame stated in the license to high source needs to be made available for person requesting, and 2) pretty sure these companies could charge us for distrbuting source to us, so that's kool they don't at least.
~S-Off LTEvo; Back on the Always Solid Viper4G Latest;
Expletive Deleted Kernel
cpu0/1: 1.5ghz ¦ 384mhz ¦ sleep: 486mhz max
ondemand
fiops
thermald: dynamic
With tapatalk4
Related
Haven't posted much here and read through the threads under the Evo board. Im not familiar with how HTC handles Android releases. My only Android and open source experience has been with Samsung and the moment.
Any rough ideas how long HTC has historically taken to release the open source for an android phone after its public launch? 2-3 weeks? 2-3 months?
Does anybody know if they will release kernel source (2.6.29) and Android 2.1 source or just their modified kernel source?
Hope these questions aren't too far off...
I think you may have to wait a while for that.
david279 said:
I think you may have to wait a while for that.
Click to expand...
Click to collapse
i'm curious if anybody has any information which i wasn't able to find regarding this. the answer would either be based on previous information, inside information, or speculation. as i inquired previously and to combine your answer, is "a while" 2-3 weeks or 2-3 months? if nobody has any idea, that wouldnt surprise me either...
joeykrim said:
i'm curious if anybody has any information which i wasn't able to find regarding this. the answer would either be based on previous information, inside information, or speculation. as i inquired previously and to combine your answer, is "a while" 2-3 weeks or 2-3 months? if nobody has any idea, that wouldnt surprise me either...
Click to expand...
Click to collapse
Well it took what, 5-6 months for the release of the kernel for the hero, so a while could be a long time.
the htc increadable source is already out, I don't think it will take that long at all
The problem with the Hero was due to GSM and CDMA variants.
-------------------------------------
Sent via the XDA Tapatalk App
kyleblakepeters said:
The problem with the Hero was due to GSM and CDMA variants.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Not really. HTC had the Kernel source, they just sat on it. Most of the Android devices HTC has released has taken about 6 months to get the kernel source. I would expect no different with this device. However, considering the Incredible source is indeed already released maybe they are changing that. Regardless, is the kernel version actually still 2.6.29 or do the newer devices have a newer kernel? I thought the N1 used 2.6.31.
chuckhriczko said:
Not really. HTC had the Kernel source, they just sat on it. Most of the Android devices HTC has released has taken about 6 months to get the kernel source. I would expect no different with this device. However, considering the Incredible source is indeed already released maybe they are changing that. Regardless, is the kernel version actually still 2.6.29 or do the newer devices have a newer kernel? I thought the N1 used 2.6.31.
Click to expand...
Click to collapse
android 2.1 released for the samsung moment is on 2.6.29. idk how accurate of a gauge this is for the EVO.
thats unfortunate it took them so long to release the source code. i thought there was a time constraint on the GNU open license giving them a short time period between public release and deadline to release the open source. i could be wrong though...
HTC just released the Incredible's and Eris's source codes 5 minutes, ago via Twitter, so I don't think we will wait long.
htc
Because we know how much you developers love source code...Legend, Incredible, Desire, and Eris(2.1) kernels are online. http://ht.ly/1MODf
Click to expand...
Click to collapse
TheBiles said:
HTC just released the Incredible's and Eris's source codes 5 minutes, ago via Twitter, so I don't think we will wait long.
Click to expand...
Click to collapse
It's been up on their developer site for a couple weeks at least
chuckhriczko said:
It's been up on their developer site for a couple weeks at least
Click to expand...
Click to collapse
Eh, well it was news to me.
http://groups.google.com/group/android-building/browse_thread/thread/091172a81604c8a0?pli=1
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
I'll give more details once the source code is available. However,
there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some
points in time when the master branch doesn't build. Sorry about that.
If you're working on the master branch, I recommend that you don't
sync until I send an "all clear" when I'm done and things look good.
Other branches are expected to work fine as soon as their manifests
are created.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
If you're not going to immediately work on porting Gingerbread to
devices with the intent of distributing the result to end-users, I'm
kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Thanks for being patient.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
Yay!
Let's bombard Cyanogen's Twitter! J/K``
Hope something good for my incredible comes out of this
Sent from my ADR6300 using XDA App
Can't wait! The quicker the source is released the faster we will have Gingerbread baked into our roms
First one to get an AOSP build of 2.3 running on the G2 will be my new hero.
lol @ the software engineer having two Nexus B's already ;D
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Wowo!!!!! Can't wait! I've been on the virtous for some time now, because I really like the sense shell, but it's strait over to CM again (been there many times allready) when 2.3 comes!!!
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
@cyanogen
Prepare for spam!!
I just looked at aosp and I see next to nothing updated yet so I dunno
@cyanogen WILL come through quickly for the G2. I'm sure of it.
Shady Gambino said:
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
Click to expand...
Click to collapse
Why wouldn't you permroot now? Nearly double CPU clock, the ability to disable throttling, superuser access.
In my experience, the first implementation of new code is often quite buggy. While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
tornado9015 said:
While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
Click to expand...
Click to collapse
That's half the fun
Follow cmrsc on twitter for updates on compiling a blue-berry flavored gingerbread.
Sent from my HTC Vision using XDA App
sino8r said:
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Come on msm7x30 support!
Blades said:
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Click to expand...
Click to collapse
He probably has a stack of cell phones and probably tries to brick some of them on purpose. He probably just gives back the bricks to Samsung.
ctraywick1 said:
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
Click to expand...
Click to collapse
Thanks, I guess... hard to detect sarcasm in writing My point was... bricks happen!
Just flashing the proper way, epecially packed ones with a bootloader, you can brick even when you do everything correctly. I've flashed over 500 phones (may be more) and it will happen. The nice thing is though, when you are a cell tech, just pop out the board and get another one. Manufacter's warranties for carriers are surprisingly lax... so, yeah we did brick some on purpose, lol
Cyanogen via twitter:
My G2 seems to have Gingerbeard on it. How did that happen?
Click to expand...
Click to collapse
I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005
Yea sounds like its coming sometime in 2011....not holding my breath
Have you really been bugging these people for this?
Sent from my PC36100 using XDA App
I was asked to by some Evo Developers who want the source code updates to look at. I have experience with getting manufacturers (specifically Samsung in the past) to actually commit and release the opensource code protected by the GNU GPL v2.
DirtyShroomz said:
Have you really been bugging these people for this?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
most developers are curious how HTC removed the 30 fps cap (took methods developers here created or some alternative way).
also, having the real drivers from HTC for the new hardware 4 phones, basically diff hardware camera is used and i dont think anybody has released a working custom kernel with the correct drivers for the hw 4 camera. it would be nice to see the source code to know for sure whether or not any other hardware changed in ver 4.
among other things, its always great to have the latest source code for the kernel they release as it allows us to keep creating custom kernels either based on HTC's latest drivers or at least be able to use their source code as reference.
hope that helps satisfy your curiosity as to why we are very very happy to finally hear a response from HTC, who hasnt released any of their linux modified kernel source code which falls under the GPL v2 license, for the last few months.
Glad to see you're on it numus I've been wondering what's taking them so long and why more people haven't been complaining about it.
^ 5 bru!!!!!
numus said:
I have been contacting HTC and different departments and contacts to find out when all the backlog source data will be released...
This is specific to:
3.29.651.5 updated kernel to 2.6.32.15-ge2fb08e [email protected]
3.30.651.2 updated kernel to 2.6.32-15-g0f673ed kernel #10
3.70.651.1 updated kernel to 2.6.32-17-gee557fd kernel #15
I finally got the final confirmation e-mail back from my contact.
All information about the contact has been removed due to confidentiality statements at the bottom of the e-mail.
So keep your eyes peeled on the HTC source site for these releases. If i get anymore info i will let you know
We are in the final Stages of releasing the data, as soon as we know an exact date we will let you know.
******
Technical Support Specialist
T +1 xxx.xxx.xxxx
13920 SE Eastgate Way Suite 400
Bellevue, WA 98005
Click to expand...
Click to collapse
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.
twin001 said:
They are Tech Support....they will tell you what you want to hear. Don't hold your breath on this one.
Click to expand...
Click to collapse
I actually talked to some developers at HTC... they wont directly email anything to me tho so they are using this guy as the relay.
Good job. This its essential.
Sent from my PC36100 using XDA App
"Soon" in HTC or Valve Time usually translates to "three to eighteen months."
Looks like it's finally out!
http://developer.htc.com/
HTC EVO 4G (Sprint) – Froyo MR2.5 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR2.51 – 2.6.32 release
HTC EVO 4G (Sprint) – Froyo MR3 – 2.6.32 release
Yea yea.....yea for beer.
Sent from my PC36100 using XDA App
Wonder how long before rom devs start incorporating this into their kernels and roms
Samsung conforms to source 100% better than HTC now. But HTC actually updates their software
I hope soon. I need some custom kernels on my evo. I got that new cam in mine.
Sent from my PC36100 using XDA App
WHo you telling. I'm living without my camera now because I NEED the better battery life.
This is awesome! Been waiting to oc to see what this thing can do.
Sent from my PC36100 using XDA App
I am amazed 50 threads have not been posted.
Sent from my iPhone with the bigger Gee Bees.
Been on a security detail the past few days.. Glad to see they finally released!
Well via to an article over at Android Central, and Bloomberg: Business Week, its been said by Google that they wont be releasing the source code for Honeycomb. The reasoning behind it apparently is to keep your small time, crap companies, from trying to put 3.0.x onto a device and giving android a bad rep. So I dont think we will be seeing any ROMs until Ice cream.
Source: http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
http://www.androidcentral.com/google-not-open-sourcing-honeycomb-says-bloomberg
Google Holds Honeycomb Tight
It will delay distribution of new Android tablet source code to outside programmers
We'll get it eventually..
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
jmc2543 said:
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
Click to expand...
Click to collapse
+1
running Tiamat .1.1.6 for the OCing & USB
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
When it comes to preventing carriers from putting money sucking spamware on your phone googles "that would jepordize the very definition of open source". But when it comes to releasing the source code for developers to smooth out and patch their half baked OS so each consumer (who paid an unwarranted premium for their device in the first place) can have the free choice of how they would like their "open source" OS to function googles.
Say it aint so.
MOD EDIT: Language
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
orionshock said:
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
Click to expand...
Click to collapse
Not if they have already distributed product using it. AKA Xoom.
colbyb25 said:
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I believe this is not just a simple issue.. leaked <> AOSP
one thing for sure, if we don't have HC AOSP, never expect custom rom..
this android open source is going into nightmare .. Google please remember this "Don't be Evil" ..
this is ur second Evil move after c&d letter to cyanogen..
peace all..
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
So if I type assassinate and then.....Google, do u think they will send a team of nerds and lawyers to get me. Be a martyr...start a revolution..Viva la Zoom
...j/k. Not serious
Sent from my ADR6300 using XDA App
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
whitedragon33 said:
+1
running Tiamat .1.1.6 for the OCing & USB
Click to expand...
Click to collapse
Ftw
Kcarpenter said:
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
Click to expand...
Click to collapse
Bauxite said:
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Here's the deal guys. The legend JesusFreke has stated that he needs source to update his programs smali / baksmali. The are the base tools for decompiling framework and apk.
we cannot deodex rom without those tools. Thus we cannot modify smali and XML. So we are stuck with a stock rom. But we have kernel source which is far more important.
So, its all good for now
Is it still possible to theme the Stock ROM without deodexing? I thought I read somewhere that you could but it was not as easy.
Samsung probably pissed them off for putting their craptastic TouchWiz on the new Galaxy Tabs.
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
th0r615 said:
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
Click to expand...
Click to collapse
3 weeks after io..I think that's how long it took for froyo source.
Sent from my Samsung-SPH-D700 using XDA App
My guess is Google is probably more worried about all the bagnasty China tabs that have flooded the market all running earlier versions of Android.. Imagine the cheap China crap that would hit the streets if they released the HC Source.. No way the masses would pay the big bucks for the Google sanctioned Tablets when they could pick up a China tab for pennies on the dollar..
While I don't think Google is doing themselves any favors by taking this approach, I would point out that folks would probably make more headway spending time porting Ubuntu or one of the other Linux distributions to the Xoom than trying to prevail on Google to change their ways.
Let's Take A Deep Breath Folks
I'm going to keep this short because I'm not a developer yet, so I'm only qualified to speak as a user and as a grateful member of this forum. As I understand it, in order to be "open" the code has to eventually be released (kind of like non-packaged Linux, i.e. CentOS, Ubuntu, etc.).
From what I've experienced, the only people that DON'T want code coming to us are the carriers. When you folks develop way better ROMs than the crap with bloatware that they try to pass off to us, it hurts their wallets - BFD!!
I'm honored and proud of you guys and I KNOW that the Google probably held it for legitimate problems that they're going to fix for us. Once that's done, they KNOW that once you get a hold of it, more people are going to be exposed to it which only makes more people want future versions. that's how I got snagged by you folks, first with Windows Mobile and then with Android.
I have faith in parts of the system. I have faith in Google to deliver their end, it's the carriers and their greedy practices that I don't trust. Keep the faith folks, take a deep breath and relax. XOOM has been here for only a minute, but we KNOW that it's unlocked, it's rooted and as soon as the 4G hardware and the SD card issues are resolved, we're going to be hip-deep in better versions of the ROMs. I believe that with all my heart because you folks have shown it to me time and again.
It's gonna be great - just wait and see.
So, you see headlines like this:
"Samsung Releases Conquer 4G Kernel Source Code Before The Phone Even Hits Shelves"
http://www.androidpolice.com/2011/0...urce-code-before-the-phone-even-hits-shelves/
And I can't help but think to myself..."OK, so Sammy is starting to see the benefit of getting source code out for its devices, this is good", and then I sit back and reflect upon the fact that the Epic still doesn't have the source code we're looking for (amirite?).
Now, I'm not going to piss and bemoan the fact, BUT, I am going to wonder why it is so. Is there some sort of secret sauce there? Or perhaps is there something VERY embarrassing in their source code? OR, is Sammy really that schizo?
In all, I've been pleased with the steps Sammy has taken. Sure, it would be nice to have me some GB, or even better some CM7, but hey, the Epic is still a great device despite some of the quirks that need to be straightened out.
Thoughts?
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
musclehead84 said:
Its probably because gb is not being built yet so they don't have it complete. The phone you referenced to the build is probably complete. Yes it us nice to see Sammy doing this though.
"The greatest respect you can earn is self respect" Louie Simmons
Click to expand...
Click to collapse
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
the reason CM7 isn't fully functional for our phones is a kernel and drivers issue. Without GB source for those, we have a hacked together partially working port.
Got it.
Well, if that didn't make your head asplode, then this surely will:
http://www.homestarrunner.com/sbzone.html
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
MeetFace said:
Yes, but isn't the problem the CM7 squad is having with our device related to source code for our drivers?
Click to expand...
Click to collapse
Plus driver source isnt open source so they don't have to give it to us
it ships with GB, what do you mean it's not being built yet? I think they are not releasing source for us because our phones are reaching EOL and they want us to buy new ones.
theduce102 said:
Plus driver source isnt open source so they don't have to give it to us
Click to expand...
Click to collapse
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
CapsLockKey said:
It's source code for a finished product. Not exactly the same situation as wanting source code for leaked builds.
Click to expand...
Click to collapse
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
mkasick said:
Yes. To clarify, to my knowledge Samsung has released the kernel and GPL platform component sources for every official Epic firmware version a day or two prior to its release.
They don't release sources for leaked builds because those builds were never officially released in the first place.
Click to expand...
Click to collapse
This makes rational sense. Would be nice if they released those driver sources this next time around. Would be a good measure to producing goodwill & brand loyalty IMO.
No phone company has ever released driver sources and nor will they. Its open kernel source not open driver source. There is some other reasons they don't release driver source but it would be nice if all phone manufacturers did but that's a perfect world
Phone companies haven't but what about component companies like Nvidia they released Nvflash
Sent from my Transformer TF101 using XDA Premium App
xopher.hunter said:
What happens if thy never give it to us? Are we screwed?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
No. As stated 1000 times, it is 100% possible to write drivers, a kernel and etc from scratch just much more labor intensive than using source code.
Sooo, just wondering if since the conquer 4g is VERY similar to the epic since its gb source code was released would it help us at all?
I'm just asking cause my moment ran on a frankenstein froyo port that came mostly from the transform and a little bit from the intercept and it was awesome.
Sent from my SPH-D700 using XDA Premium App