• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help Team HTCDEV!

I've been nailing them every day or two and all that I've gotten so far are the usual canned responses so hopefully things are starting to get going. :D:thumbup:
 
Great work guys. Let's keep it up. I really feel like we are making some real progress here. Keep the emails coming to HTC
 
g60madman said:
ramjet,

No clue at all, but the break down is if you head to htcdev.com and check out carrier Virgin Mobile and search they don't have the Evo V 4G listed. I just downloaded the

EVO 3D Sprint WWE CRC 3.0.16 v4.0 97.7 MB 2.89.651.2

Lucky for me my Wife's new Evo V 4g just showed up (it's not activated yet) and I did an 'adp pull /proc/config.gz' after downloading that kernel and doing a compare from config to config they are totally different as you can see by meld.

Edit: If you have never used meld before the green lines on each side represent differences in the files. When we got the Triumph source code the differences from one file to another where (3). After doing a build there was a few updates from the stock config which then put them inline with one another.

meld.png
Click to expand...

g60,

I am not doubting your findings either however you did download the Sprint OTA so that would be different. The file that you should have downloaded is the on that has 1.14.652.0 as the description. That is the latest OTA that was released to the VM phones. It is possible that they made a mistake and listed it as the wrong carrier. I just noticed that you downloaded a file that has been there for sometime and the 1.14.652.0 is newer and never released for Sprint but it was for Virgin. That is my 2 cents and I could be wrong.
 
krowley3 said:
g60,

I am not doubting your findings either however you did download the Sprint OTA so that would be different. The file that you should have downloaded is the on that has 1.14.652.0 as the description. That is the latest OTA that was released to the VM phones. It is possible that they made a mistake and listed it as the wrong carrier. I just noticed that you downloaded a file that has been there for sometime and the 1.14.652.0 is newer and never released for Sprint but it was for Virgin. That is my 2 cents and I could be wrong.
Click to expand...
Good catch! And if you check the names of the source zip files that are actually downloaded from htcdev.com you will see that they match the build numbers for the respective kernels as well:

........... VM ICS 1.14.652.0 Kernel: 3.0.16-g4211684

....... Sprint ICS 2.89.651.2 Kernel: 3.0.16-g294f767

Note that the kernel and hboot versions did not change with the VM OTA.

ramjet73
 
ramjet73 said:
Good catch! And if you check the names of the source zip files that are actually downloaded from htcdev.com you will see that they match the build numbers for the respective kernels as well:

........... VM ICS 1.14.652.0 Kernel: 3.0.16-g4211684

....... Sprint ICS 2.89.651.2 Kernel: 3.0.16-g294f767

Note that the kernel and hboot versions did not change with the VM OTA.

ramjet73
Click to expand...

Yeah I am pretty sure that is the one that we need.
 
g60madman said:
Same issue
Click to expand...
Perhaps you could forward your comparison via the htcdev contact form and ask why that source doesn't match the config for the actual kernel with that build number, although I didn't see any place for attachments on that form. Maybe you could use an email address from one of the responses you've received instead?

Someone should report HTC to the GPL police since they don't seem to be distributing the proper source code.

j/k ;)

ramjet73
 
I am so ticked. and sadly disappointed.... I hope you guys keep the emails flowing to HTC. That's our only hope. I really just don't understand this. I mean wouldn't it only take a couple of clicks of the mouse to just give us the damn code. WTF
 
Guys, don't get too worked up about this. They will release the code; they have to. At least they understand that now, time was that companies would release GPL/Linux based products without realizing their legal obligations. Then when they did, they did not have a process in place to deal with it. Most companies now have a process for this. They can't just dump out their code to an FTP server; they have to comb through it to make sure they aren't releasing anything that they shouldn't be. That said it's not okay that this phone has been out as long as it has and no GPL release. But rest assured it will come.
 
Maybe you guys should re-inform them that the GPL agreement requires releasing the source(especially if someone wants it), and legal actions can be taken against them(we probably wouldnt actually take legal action, but the threat might wake them up).
 
We should also inform them that when they do release the code, it needs to be working. Because I'm pretty sure non functioning code is also a GPL violation.
 
You must log in or register to reply here.
Back
Top Bottom