Related
At the Google Press conference they announced that Google will be releasing the 2.1 source code in just a few days. Does that mean our Devs can cook us up some CDMA Hero 2.1 ROMS way before the phone carriers can get them to us? I know the ROMS would probably be vanilla android (ie: no Sense UI), but I'd be down to play with 2.1 if it would work on our heros.
Am I wrong in this assumption? or wil our Devs be able to cook us up some 2.1 ROMS in a couple of days?
alexthearmo said:
At the Google Press conference they announced that Google will be releasing the 2.1 source code in just a few days. Does that mean our Devs can cook us up some CDMA Hero 2.1 ROMS way before the phone carriers can get them to us? I know the ROMS would probably be vanilla android (ie: no Sense UI), but I'd be down to play with 2.1 if it would work on our heros.
Am I wrong in this assumption? or wil our Devs be able to cook us up some 2.1 ROMS in a couple of days?
Click to expand...
Click to collapse
Seems like we would still have issues without the Kernel source code.
crunchybutternut said:
Seems like we would still have issues without the Kernel source code.
Click to expand...
Click to collapse
Still need CDMA kernel source. Drivers and what not. Android != Kernel.
Dang it...so HTC are being butts and not giving us what they are legally obliged to give us. I forgot about that dilemma.
Posted on android central a little while ago. One step closer to new sense for the DI. I only see kernel and webkit source code, but better than nothing.
http://developer.htc.com/
The kernel is basically the only code they post. They will never post the source code for Sense UI because it is their rendition of AOSP and have it copyrighted, hence their power to issue a C and D to anyone who tries to release anything involving Sense (Fancy Widget for example). I'm surprised LauncherPro has lasted this long using an off-shoot of their widgets. The kernel source is all we need though because porting an OS is easy enough, but the kernel holds the drivers for some of the hardware to function properly with the software and the source code is necessary for manipulating this.
Thanks good to know
maybe eventually could lead to working cam on desire hd/z port though
djh816 said:
maybe eventually could lead to working cam on desire hd/z port though
Click to expand...
Click to collapse
Yea the kernel definitely carries the drivers for that so it should help out quite a bit.
mb02 said:
Yea the kernel definitely carries the drivers for that so it should help out quite a bit.
Click to expand...
Click to collapse
yea i hope this leads for a fix for the Z Rom cam. that rom is so snappy
bluewave53 said:
yea i hope this leads for a fix for the Z Rom cam. that rom is so snappy
Click to expand...
Click to collapse
Me too thats the one thing from making that my daily driver.
Wasn't the froyo OTA source code released for the incredible?
http://htcdev.com/
What does this mean for us HD2 users?
It means we might have to wait a bit longer for the actual source to come available.. But there might be some interesting things in this ROM. We will know shortly
Sorry to keep asking questions, but what source is needed? I see the source for the GB kernels for various phones - what exactly is missing?
Just trying to understand better.
MikeG4936 said:
Sorry to keep asking questions, but what source is needed? I see the source for the GB kernels for various phones - what exactly is missing?
Just trying to understand better.
Click to expand...
Click to collapse
Asking questions is never wrong .. The source files contain drivers for the different phones, which is why they are all released seperately. Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
What has been released on HTCdev.com (if I understand correctly), is the ROM upgrade itself, and not the actual kernel source. It may seem weird, because it is the only 'official' ROM upgrade that has been put up on HTCdev.com yet. They are not releasing it OTA (over the air) to all Desires, so they had to put it somewhere easy to be found by devs. This is why it has been put up on that page, which might have been confusing (because many would think it actually is the kernel source). As far as I can see, the package only contains the upgrade itself and 2 APK's. Usually it takes a while longer for this to become available, but per Linux license they are obliged to release it. Eventually.
I think there will be some interesting APK's in this ROM nevertheless.. We'll just have to wait until someone (one of the dev's) has explored the ROM thoroughly.
but it can't be to long from now till the sources are released.
BLAST3RR said:
Asking questions is never wrong .. The source files contain drivers for the different phones, which is why they are all released seperately. Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
What has been released on HTCdev.com (if I understand correctly), is the ROM upgrade itself, and not the actual kernel source. It may seem weird, because it is the only 'official' ROM upgrade that has been put up on HTCdev.com yet. They are not releasing it OTA (over the air) to all Desires, so they had to put it somewhere easy to be found by devs. This is why it has been put up on that page, which might have been confusing (because many would think it actually is the kernel sournce). As far as I can see, the package only contains the upgrade itself and 2 APK's. Usually it takes a while longer for this to become available, but per Linux license they are obliged to release it. Eventually.
I think there will be some interesting APK's in this ROM nevertheless.. We'll just have to wait until someone (one of the dev's) has explored the ROM thoroughly.
Click to expand...
Click to collapse
Excellente. Couldn't have said it better. The update's been out for almost a week. And from videos that I've seen, HTC did not upgrade the Sense version to 2.1 or 2.0 for the matter.
But of course all we need is the kernel source.
I'd also like to ask any of the devs:
Will a new kernel need to be compiled when the Desire gingerbread source is released? Hint hint: Rafpigna 2.1?
Also, I'm not familiar with the OC deal, but is it possible to overclock over 1.5 ghz on our HD2? I've seen 1.9 ghz on Desire Z/G2, and almost 1.8 ghz on the DHD.
BLAST3RR said:
Every device has different hardware, and the Desire has the closest resemblence to the hardware found in our HD2. This is also why many think the Desire source will really help in the development of Gingerbread ROM versions on the HD2 (like it did before on the previous Android releases, for example the camera).
Click to expand...
Click to collapse
Does this mean that the the HD2 is on it's "last breath" with Android? Since the Desire isn't getting updated past Gingerbread...
What about Nexus One then? It is pretty much a redesigned Desire.
Or is this necessary for Sense ROMs only, and AOSP ROMs will still work?
Wouldn't it be possible to port something like Leedroid HD then? Since it's on the Desire and it works perfectly..
SilverHedgehog said:
Does this mean that the the HD2 is on it's "last breath" with Android? Since the Desire isn't getting updated past Gingerbread...
What about Nexus One then? It is pretty much a redesigned Desire.
Or is this necessary for Sense ROMs only, and AOSP ROMs will still work?
Wouldn't it be possible to port something like Leedroid HD then? Since it's on the Desire and it works perfectly..
Click to expand...
Click to collapse
With Sense builds it is the end of the road I guess.. At least for any Android releases after Gingerbread. With the other builds I am not sure.. We have quite some driver source available, and with that we can probably simply compile them on the newer AOSP and non-sense ROMS. Sense is really a problem when it comes to source, because it is proprietary software written by HTC (no full source for Sense to simply cross-compile their libs). This is also why it is so hard to make decent Sense-builds whenever a new major Android release comes out. I could be wrong here though.
Let's wait for a dev to come over and shed some light ..
Grr... It's a bad day to own both the Desire and the HD2.
SilverHedgehog said:
Grr... It's a bad day to own both the Desire and the HD2.
Click to expand...
Click to collapse
True.. But I for one never could have dreamed my HD2 to be top-notch more than a year later.. It certainly was one of my best buys ever. Imagine life when we'd still be stuck on that creepy WM6.5
BLAST3RR said:
True.. But I for one never could have dreamed my HD2 to be top-notch more than a year later.. It certainly was one of my best buys ever. Imagine life when we'd still be stuck on that creepy WM6.5
Click to expand...
Click to collapse
Haha, that's true, I guess... I never even got to touch WM6.5 on my HD2, I bought it from Ebay with WP7. Tried it and didn't like it that much. So now I'm wondering which phone should be my primary, HD2 or Desire..
BLAST3RR said:
With Sense builds it is the end of the road I guess.. At least for any Android releases after Gingerbread. With the other builds I am not sure.. We have quite some driver source available, and with that we can probably simply compile them on the newer AOSP and non-sense ROMS. Sense is really a problem when it comes to source, because it is proprietary software written by HTC (no full source for Sense to simply cross-compile their libs). This is also why it is so hard to make decent Sense-builds whenever a new major Android release comes out. I could be wrong here though.
Let's wait for a dev to come over and shed some light ..
Click to expand...
Click to collapse
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.
captainreynolds said:
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.
Click to expand...
Click to collapse
It's just the Sense development that will be near to impossible to be perfect.. The rest will be continued as long as there are developers interested in our HD2.
captainreynolds said:
I'm confused - why would the HD2 be on it's last legs?
People are still developing ROMs for my G1 - hell, there's even a honeycomb rom for my G1. Until people quit developing for the HD2, I guarantee it will be on par with other devices.
Click to expand...
Click to collapse
The hd2 development won't die, merely the Sense ROM development unless HTC make an ice cream sandwich update for the Desire (which is unlikely but possible as Google have stated ics has been designed to work on all Android devices to date). AOSP ROMs will probably continue as long as the device stays popular.
Sent from my HTC HD2 überphone
I just went on this sure cause I got an email from htc saying the site launched. Now I know we need the kernel source, but I just noticed this in the kernel source page:
Android 2.3 (Gingerbread) Upgrade for HTC Desire
Or is that not enough?
Sent from my HD2 using XDA App
Great news sony is just like xperia s working on aosp project
http://developer.sonymobile.com/201...r-xperia-z-on-sonys-github-open-source-video/
This would definitely help us!
Yep. Some of the devs doing apps and kernels for the device would probably be helped even more than us, and if they send fixes to the repo Sony could be helped as well.
Open source. It works, *****es!
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
As I understand it, CM usually uses proprietary blobs (binaries) extracted from the device they are building for, rather than open source alternatives coded by the community.
AOSP aims to use all open source code.
Someone correct me if I'm wrong
Sent from my C6603 using Tapatalk 2
Hi Entropy, could you help answer a question that was brought up in another thread while were on this AOSP topic. I'm curious to your thoughts on this.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Entropy, while were on this topic,could you enlighten us for this question that was brought up in another thread.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
Perfectly clear and nice answer, thanks.
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
profete162 said:
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
Click to expand...
Click to collapse
In some cases, our handling of blobs is a pretty serious grey area. That is, for example, why our official build instructions use the extract-files approach. Also, why our blob repos used for builds are maintained separately from our main source repos.
That reminds me, I need to look through the manuals/stock software for my device to see what sorts of legal terminology there is - e.g. what is actually said about the blobs in about->legal.
In some cases (such as modem and camera), the OEM has weirdo restrictions in terms of permission to release binaries. Qualcomm has some especially arcane rules for some items (mostly modem-related).
Also, in the case of AOSP master, blobs must be compatible with the current codebase - as a result, some of our backwards-compatibility hacks to work with released blobs aren't valid for "official upstream" AOSP.
If I am not completely stupid and understood previous post, can we summarize like this:
1) "drivers" for camera and modem are proprietary compiled files on the device that nobody can edit
2) Sony has the right to include these files on a Sony Rom (I guess they paid for these files?)
3) Sony cannot include these files on other Rom than the one shipped with the device, like an AOSP ROM. (even as a separate package?)
4) Cyanogen include these files on CMxx but (is? // is not?) allowed to
Is that right?
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Gitaroo said:
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Click to expand...
Click to collapse
Will still require time to adapt it. But it'easier for the community devs and chances to get it are much higher than on other phones.
Sent Form my CM powered Sony Xperia Z.
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
All Snapdragon S3 (Scorpion) devices are in the same boat there. Samsung Scorpions just saw 4.1 only in the last week or so.
I hope they can retain Bravia engine!
I'm dowloading the source code now, let's see what I can do
Sent from my C6603 using xda app-developers app
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
I was about to create a thread to share the news hehe
http://developer.sonymobile.com/201...or-xperia-z-on-sonys-github-open-source-video
I hope by doing this xperia z will turn to a nexus phone *grins*
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
wouldnt Z be different. The S didnt have on screen navi keys and on top of that it was using a snapd 3 chip with 1gb of ram. Touch up was clearly needed for the S, however...
The Z is nearly the same as a Nexus 4 in nearly every way.
paperWastage said:
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
Click to expand...
Click to collapse
Read my post again.
Just wanted to know why this variants is not getting Roms/love from Dev's be it sense based or GPE Rom come to think of it M7 and M7C are pretty identical in hardware SOC,we used to have Sense based Rom from maximus HD but that has been abandoned we even have a great kernel thanks to @bgcngm we also have Sense 7 port thanks to @artur0588.
I'll be willing to be a tester if anyone would be kind enough to venture into it.thanks to all who have made contributions to M7C development thus far:good:
Although I can't promise it will be officially supported by CM because I obviously can't maintain a device without having it, I'll give it a look today to see if I can come up with an alpha release. Please remind again, which variant do you have, is it 802w?
bgcngm said:
Although I can't promise it will be officially supported by CM because I obviously can't maintain a device without having it, I'll give it a look today to see if I can come up with an alpha release. Please remind again, which variant do you have, is it 802w?
Click to expand...
Click to collapse
802w
Sent from my HTC One dual sim using Tapatalk
Nahhhh, forget it. There are huge differences in source code and I have only looked into kernel code. Merging source for dug, dwg and dtu is not an easy task, even more without having the device for testing.
bgcngm said:
Nahhhh, forget it. There are huge differences in source code and I have only looked into kernel code. Merging source for dug, dwg and dtu is not an easy task, even more without having the device for testing.
Click to expand...
Click to collapse
Can't you look into dug first then later the rest? as for testing just tell me what to do anyways thanks for your help
Sent from my HTC One dual sim using Tapatalk
Of course, I looked first into M7CDUG. Adding the source code over actual CM's kernel is a hell. Nothing compared to M8DUG, where one just need to pull in the additional DTSI files.
bgcngm said:
Of course, I looked first into M7CDUG. Adding the source code over actual CM's kernel is a hell. Nothing compared to M8DUG, where one just need to pull in the additional DTSI files.
Click to expand...
Click to collapse
So basically you mean it's difficult for M7CDUG and possible for M8DUG?,but i haven't seen any aosp Rom on M8DUG or even GPE
Sent from my HTC One dual sim using Tapatalk