Related
Hello i would like to know if it's possible to install SonyEricsson's Interface on HTC Hero instead of Sense UI.
Has anyone ever tried to do so?
I cannot say that i am an experienced android user but i think it should not be that hard right???
Thanks in advance
nicknls said:
Hello i would like to know if it's possible to install SonyEricsson's Interface on HTC Hero instead of Sense UI.
Has anyone ever tried to do so?
I cannot say that i am an experienced android user but i think it should not be that hard right???
Thanks in advance
Click to expand...
Click to collapse
Wrong
That would be very difficult to do, as the frameworks are totally different due to them being totally different devices
Hmmm I never thought that..... you're right......
Thanks anyway
Sent from my HTC Hero using XDA App
it is possible, but as said itd be very difficult. I guess it would require source code modification, a massive amount of T&A and alot more stuff too.
As good as sonys system may be (no flaming from those who hate it), its just not worth the effort
If SE release an android 2.2 version of the software it is more likely to be ported. But due to the fact it is based upon android 1.6 (last i checked) it is old and outdated - meaning despite it's fancy looks it is very limited in features and speed.
Just a general thought/question about Android:
What really stops us from using newer versions of Android on our devices, without the need for a dev making a custom rom?
I know the short answer is compatibility. (i.e. drivers etc.)
But what would it take from manufactorers to allow us to uprgade to vanilla versions of Android ourselves?
Consider a desktop/laptop for example: It can continue to run many different versions of ubuntu. No need for customization for each PC. Today driver issues are becoming fewer and fewer as well.
Why can't my phone do the same thing?
Sent from my HTC Vision
different people like different things
some like how CM give you different options
some like MIUI allow you to change theme / icons / other stuff easily
some like the HTC sense widgets / layout
its just very difficult to combine all those into one rom, and retain the speed on all those
then there are manufacturer / carrier restriction a rom needs to add to "prevent us having too much control and brick the phone for warranty purposes"
just think HOW can you combine the miui folders into CM and add all those HTC widgets and other options available
if you can do it, you have made yourself a new ROM people will sought after,
maybe thats the ultimate rom for all ... and we dont need to keep looking forward to a new ones ....
From a development standpoint it could be done. Combining all the roms that is.
The development time on that would be astronomical though, you'd basically be creating a rom almost from scratch and unless you had a HUGE team working for you - updates would be in tiny increments at best, 1.00.00.01 updated to 1.00.00.03 for example. The worst case would be that they'd take forever. Look at how long it takes for a stable release of CM, and that a fairly modest team. Let's not even get started on size, yes most current phones could handle a rom of 250MB+ without any custom MTDs' but damn (sorry) - that's huge. To combine all the main desirable functions of each rom would end up being at least that big.
I did my homework, and have come up mostly empty. Read what I could find on the CM site; wikipedia; blogs; newsgroups; and a lot more. Probably at least 2 hours trying to get a comparative handle on CM vs. stock release derived ROMs.
After all that, I'm only a tiny bit closer to understanding what I gain, and what I give up, going to CM.
If there if a good, detailed articulation of this somewhere, please help us CM noobs with a pointer; Otherwise, I'd like to start a thread to capture as much detailed information about comparing CM to stock-based ROMs so people can make informed choices.
Sent from my mind using telepathitalk
http://wiki.cyanogenmod.com/index.php?title=What_is_CyanogenMod
Thanks, that's a start, but in truth it's information like that that prompted my starting this thread.
That's generic information. Only moderately helpful in judging specifically for the Epic whether I should go CM, or with another custom ROM.
For example, info like this: CM does not include the accelerated Samsung video player, and doesn't handle many video formats and codings well in comparison. So, if playing h264 coded video in mkv containers is important to you, CM will be a challenge, where Bonsai, ACS, Midnight, etc. will be a much simpler choice to meet your needs.
Sent from my mind using telepathitalk
Think about it like this. If you buy a PC from a big company (HP, Dell, etc) it comes with a fully functional install of software. Windows + drivers + all other crap they decide you should have. That is equivalent to the Samsung ROM that comes stock on Epic.
What if you build your own PC from components? You will install Windows, then you will dig up the drivers you need separately, and then load your own applications.
Android AOSP in this comparison is the "base" install of Windows. Nothing else added in.
The drivers and other changes required to make the base Android work with your hardware is CyanogenMod.
So basically, Samsung based roms will have all the functioning drivers and everything else in them. Dev's tear them apart and remove/change what they don't want, but don't have to worry much about hardware cause the drivers are straight from Samsung.
AOSP based roms (CyanogenMod) will be utterly broken and have no hardware support at first. Developers have to write real lines of code into the software to make it support the Epic or any other phone. The are built from the ground up. That is why it is so amazing what Team CM7 has already got working in so little time!
Again, thanks for the sincere attempts to answer this qualitatively. However, that's not the issue. See my example above.
What you describe above with the custom PC example, while true, isn't informative enough for most people to make an informed decision.
Knowing that CM is free of carrier bloatware doesn't help me understand in any way that the video player with CM had some important limitations when compared to the optimized video player Samsung includes. For some people, this may be a critical issue in making a decision.
It is those sort of specific differences that I thought would be helpful to enumerate and capture. Of course anyone can simply install the ROM and discover for themselves... Judging by my own struggle to find enough information to make an informed choice myself, I thought others might benefit from nailing this stuff down.
So far, it looks like I may have been mistaken?
Sent from my mind using telepathitalk
dwallersv said:
Again, thanks for the sincere attempts to answer this qualitatively. However, that's not the issue. See my example above.
What you describe above with the custom PC example, while true, isn't informative enough for most people to make an informed decision.
Knowing that CM is free of carrier bloatware doesn't help me understand in any way that the video player with CM had some important limitations when compared to the optimized video player Samsung includes. For some people, this may be a critical issue in making a decision.
It is those sort of specific differences that I thought would be helpful to enumerate and capture. Of course anyone can simply install the ROM and discover for themselves... Judging by my own struggle to find enough information to make an informed choice myself, I thought others might benefit from nailing this stuff down.
So far, it looks like I may have been mistaken?
Sent from my mind using telepathitalk
Click to expand...
Click to collapse
So, you're looking for a more hand held description of what CM7 doesn't have?
....
Sent from my SPH-D700 using XDA App
I can give you the best piece of advice....
This is a development site, not a front end rom publishing site..
If there's not already documentation, test the differences yourself, and report the findings for the next gentleman who comes along with your same questions...
Then before too long you're not a "noob" anymore..
But to answer your question, cyanogen is a more bare bones android experience.. it is built off of the AOSP (ANDROID OPEN SOURCE PROJECT).. It is stripped of any carrier or manufacturer additions (like HTC Sense or Touchwiz).. and is usually a cleaner and less buggy experience... Then the cyanogen team customizes and polishes features... (like menu infused theming instead of flashable zips..)
If you're too scared of bricking during experimental build testing, etc, this isn't the place for you...
Sent from my Samsung-SPH-D700 using XDA Premium App
Will Cm7 on the epic have no CIQ?
Sent from my SPH-D700 using XDA Premium App
Sorry for the double post, the xda app submitted when open the physical keyboard. I too have been wondering what the big deal is with cm.. I can't find any concrete info that tells me what is so great about it. I'm on acs now and love it.
Sent from my SPH-D700 using XDA App
Overstew said:
Will Cm7 on the epic have no CIQ?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
It will not have CIQ. That is from Sprint, and this will have no traces of sprint whatsoever.
CM is completely customizable, it comes with all kinds of tweaks to make the phone a whole lot smoother, it gets updated constantly, and since its based on AOSP you can really do what ever you want with it. Whereas a stock samsung ROM you have to be careful what you do cause so many things rely on frame work and what not. The CM team is absolutely amazing the wrote code completely from scratch for $g and full HDMI mirroring to work on the evo. Also the size of the rom, CM is around 80 mb where most stock roms are 200, so you will have that much more space on the phone.
To set the record straight, I am hardly a "noob" in the sense that some here seem to think. I'm building kernels for my own use, and am working on a rewrite of the keyboard driver to more completely fix the problem so skillfully determined and patched by mkasick.
What I'm "noob" at is understanding in detail what I gain, and give up, by installing CM over the other custom ROMs based on stock releases. I have the broad strokes -- I need more specifics to decide if it's worth the hassle to give it a try.
We now have two new pieces of valuable information not obvious in any of the general info out there: Compromised video support (negative), no CIQ (positive). So, a little progress.
Sent from my mind using telepathitalk
i doubt anyone actually knows what you're asking....
Cyanogenmod is just pure android no bloatware from sprint/sammy
the way android was meant to be.
Pretty simple: If it is software that is added by a carrier or a manufacture (Sprint ID, touchWhiz, Samsungs Video Codecs) It will not be there. What it does have:
CM UI Tweaks, CM Hardware Tweaks, CM Performance enhancement options (adjustable heapsize) Default install location, Screen On Animation, Surface Dithering, Locking the Homescreen App in memory (so it doesn't rebuild it self when you press home), locking the messaging app in memory, DSP Audio Manager for Custom EQ setups over BT, Speaker, and head phones, Lock screen gestures, Lock screen music controls....
This is all of the top of my head.
Kcarpenter said:
Pretty simple: If it is software that is added by a carrier or a manufacture (Sprint ID, touchWhiz, Samsungs Video Codecs) It will not be there. What it does have:
CM UI Tweaks, CM Hardware Tweaks, CM Performance enhancement options (adjustable heapsize) Default install location, Screen On Animation, Surface Dithering, Locking the Homescreen App in memory (so it doesn't rebuild it self when you press home), locking the messaging app in memory, DSP Audio Manager for Custom EQ setups over BT, Speaker, and head phones, Lock screen gestures, Lock screen music controls....
This is all of the top of my head.
Click to expand...
Click to collapse
O O Don't forget the BJ's Feature
i even dumped my GF
There's a lot of misinformed posting going on in here.
First of all, CyanogenMod is NOT AOSP. It is, however, more AOSP than Samsung's or HTC's stock ROMs. It is based on AOSP and built from the ground-up, but AOSP it is not.
AOSP is the bones on which everything you see on Android is built. Some phones have true, pure AOSP builds, but we do not. The CyanogenMod project, once completely, will allow a build of AOSP to run on the Epic since they share all the same drivers, but, once again, that doesn't make CyanogenMod completely AOSP, as people so willingly say.
Now, what IS CyanogenMod?
The goal is quite simple: It aims to achieve a single user-experience across multiple platforms through the use of open-source software and alternatives. One thing you can expect from the base CyanogenMod experience is that if you are running CyanogenMod7-RC2 on your MyTouch 3G Slide, you can talk to you friend who is using CyanogenMod7-RC2 on his HTC Evo 4G and be able to completely understand everything each other's phone can provide (sans hardware differences, such as CPU speeds and front-facing camera).
It is also meant to open new doors for developers to completely customize their user experience. Every last part of the CyanogenMod experience is open source. That's how new features are almost constantly being added.
Another goal is to keep every phone up-to-date with the newest version of Android as it is rolled out. Providing a basic starting ground for every phone means that patching the Android system to the latest version is considerably easier. That's why, several times, I've mentioned that the work done by noobnl on CyanogenMod6 has helped us getting where we are with CyanogenMod7. While we are not using it verbatim, the work points us in the right direction and shows us how to easily fix what is broken.
People are asking questions like "Will program X be left in" or "Does this add X". The answers are a lot more complicated than just yes or no. The fact of the matter is that, for the most part, NOTHING from the stock Samsung software is included. Apps may resemble what was in your stock experience, but that's only because Samsung based their own software after their AOSP counterparts. With that said, none of Sprint's bloatware is on CyanogenMod. I'm not even sure the most of them would even work. Things like Nascar, Sprint TV, and the like just are not there because the system is not built around them, plain and simple.
Because of this lack of bloat, you are gaining much in the way of speed, performance, and usability. Carrier IQ isn't there to bog your phone down. Useless DRM services aren't running in the background, eating your battery. The Sprint Apps aren't taking up valuable space in your phone's memory. It's clean.
Another thing CyanogenMod will provide to the community is a basis to provide some real meaty ROMs. Right now, for the most part, the ROMs are reskins and rehashes of other ROMs, save two or three. Fight as you might, but that's the truth. CyanogenMod is completely different and will allow developers more control over what they are doing. A lot of cool features can be made, such as autoupdaters and random system tweaks, and they can all be built in. For example, if you look at CyanogenMod now, you'll notice that ADW is the default launcher, and its settings are integrated into the phone's settings instead of being a standalone.
And the beauty of it all is that everything can be made to work how you please. For those worried about the video codec problem, it's a problem that can be solved simply by making those codecs work on CyanogenMod, which shouldn't involve too much trickery.
I hope this answers your question.
I concur. You are really thinking too far into things. There are very few limitations that cm7 will bring. For all of these, there are other apps that rectify it.
Sent from my Samsung-SPH-D700 using Tapatalk
Thanks Devin for a great response. Why is it we needed development to come give a nice answer... and the rest of the users just wanted to be know it all jerks?
skywalkr2 said:
Thanks Devin for a great response.
Click to expand...
Click to collapse
agreed, thanks
Why is it we needed development to come give a nice answer... and the rest of the users just wanted to be know it all jerks?
Click to expand...
Click to collapse
aww man, don't do that.. it doesn't really help anything, it just invites people to get all butt hurt about your being butt hurt about whatever the ****.. Just let it go.
My only question about CM is the obvious one.. "Is it done yet? (for my phone obviously)"
This is a request to all the developers developing for HD2, If you want a fully working, fully stable build on HD2 with top performance you would have to stop treating your device as Bravo, everywhere i look from recoveries to kernel i see Bravo, Evo, Passion. For God's sake the phone is different from all other snapdragon phones.The display, the drivers etc are different. Also please stop keeping the source of your edited files to yourself, if you open source them, they can be improved upon and HD2 can be made faster and better device. Also developers thing beyond overclocking. There are other things HD2 needs in the kernel. If you waste your energy in just overclocking then i would say its pretty dumb. Just a kind request to everyone. Your device is htcleo/leo not bravo/passion/supersonic. They are similar but not same. use htcleo as device name in build, init rather than bravo/passion/supersonic. Your device isnt a mix of device anymore, its a different device that stands apart
im not a dev but ... yes , is time when all work must be unified.
+1 on this.
All devs should work together and share their results.
Bump.
This thread needs to be looked at and acknowledged. Charansingh is trying hard to get our device working to its best possible method and not just patch everything constantly. If some kernel developers (Tytung, rafpigna, iamgpc, etc.) set up conversations with charansingh, I'm pretty sure all outstanding issues could be worked on and we could even fix issues we didn't know we had. Come on, devs! Work together to bring our HD2s to truly compete with android devices out there as a native solution!
Definitely worth a bump
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
rottenjello138 said:
Super bump. Seems like a lot of these roms are sort of half-baked ports of other devices. It's extremely difficult to find a stable rom to use as a daily driver. Coming from the Nexus One, the difference in rom development is staggering. If you go to the Nexus forum you can find tons of stable, fully functional roms optimized for the Nexus. I still haven't found a rom that's come close to the usability, speed, and stability of those for the Nexus. I don't mean to knock t he devs on the board, because they do great work, but I think the HD2 has the potential to be amazing.
Just my 2 cents.
Click to expand...
Click to collapse
The Nexus is a native Android device. Of course the ROM development will be different. It's a miracle we have Android on the HD2 at all. It was always going to be a painful development process. That said, wise words from charnsingh.
Keep rocking, Devs.
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
mzebrowski13 said:
I'm not a dev, and this topic is not addressed to me but I think you should correct the name of the thread to "A request to All developers' except Pongster. Perhaps not only Pongster but I'm sure that He uses the real name our phone in bulid.prop for example and His bulid's it's not just a port from Bravo, Evo etc, etc. Correct me if i'm wrong.
Click to expand...
Click to collapse
if you read craefully pongster thread,his build still use desire base..from source of desire
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Hhhmmm I don't want to be a Pongster lawyer And I hope that HE will not feel offended but let me quote some parts of tread Hyperdroid CM7
Drawing inspiration from the Desire AOSP based Custom ROMs
Click to expand...
Click to collapse
Again, THIS is NOT a PORT... its Completely Built FROM SOURCE, Fully Optimized and Tweaked for the HD2!
Click to expand...
Click to collapse
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
The source is built from the following: Base is Pure AOSP, Framework Tweaks and Settings is Redux, Cool Features & Functions from CyanogenMod.
Click to expand...
Click to collapse
from the gbx thread.
ardianz said:
if you read craefully pongster thread,his build still use desire base..from source of desire
Click to expand...
Click to collapse
Have you bothered checking the source I use? and the device specific stuff by charan for the HD2 in there? I don't use the desire base. The source of the ROM is something any device can use, given the right kernel and proprietary libs the device may need. Just like CM7 is not just for the HD2, but for a myriad of different devices, the source can be used by anyone with the right device specific stuff.
In my ROM, I use the device specific stuff that charan has done for CM7 HD2 (with a few edits for GBX overlays and HD2 specific Settings).
Like charan has mentioned, most of what we currently have here (ROMs) are ports/kangs from other devices. In fact my old SD build was one of them.
His hard work paved the way for a device specific ROM, that being the CM7 RC's he builds (and you can build, which I also do for testing, from source) and the GBX I build now. If you take the source and add the device specific stuff (drivers, ramdisk, kernel, libs) you can build a ROM for other devices using the the device specific stuff available in the CM7 git. (Desire HD, Nexus One, etc. can be built using the source on Git)
As I understand it, from my limited knowledge on this, the device specific stuff is where the difference lies, from the 2D and 3D drivers, to the overlays for every device, down to the kernel for each device.
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
pongster said:
I don't know much about the kernel development at this point and how we came about using what we do now, but there is definitely room for improvement and we're lucky to have charan, tytung and the rest of the HD2 devs to help us out in this regard.
Click to expand...
Click to collapse
Well said pongster
Sent from my HTC HD2 using XDA Premium App
Hes right,we have to treat our HD2 like a native android device otherwise were not gonna advance that far if we treat it like anougher device.Our HD2s are amazing so lets advance and be happy
I'm in no way a dev, but its great to see common sense prevailing. I wish I had more time to get my head into these ROM's/kernal's etc but I don't. And I for one am eternally grateful for all the hard work done on this site to keep the likes of me interested in the HD2. It's a crackin phone, lets keep it that way!
i agree with you in lots of things but some roms just have to be ported.
htc won´t release a sense build for the hd2 or just a rom to get ported.
guys that want sense just need a ported rom.
and sorry buti dont´t think this is right in the development section.
maybe you should contact them on irc
I agree it would be nice if everything was done just for the LEO, but Im not going to say anything bad about Typoon his ports rock, are uber stable, and anything but half baked.
The reason why the bravo/passion base is used is:
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
d) Sense ROM's aren't open source.
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal.
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!
DarkStone1337 said:
The reason why the bravo/passion base is used is:
Click to expand...
Click to collapse
a) Some apps only show up on the android market for known official Android devices. The LEO is not an official Android device.
Fixed- We only need to change the fingerprint of the build, same is done for bravo etc using passion fingerprint for gingerbread
b) There's no official/main AOSP/CM7 repository with LEO specific changes in them.
EDIT: https://github.com/CyanogenMod/android_device_htc_leo I guess this can be the closest thing to official.
Fixed - It works
c) In terms of compatibility, the bravo is the hardware closest to our own hardware. Yes there ARE differences which is expected. We do not have a ROM designed for our own hardware that we can refer to.
Fixed - The CM7 nightlies and RC i am compiling.
d) Sense ROM's aren't open source.
Fixed - For sense Roms it isnt an option
I completely agree on the overclocking front. We need improvements in kernel, not just kicking up the CPU clock-speed.
Yes, sources should be shared, however, chefs tend to keep changes to themselves. This is an issue.
In my opinion, an 'official' AOSP/CM7 ROM/repository would be ideal. It is there lol
That said, I can't think of any bugs/issues now with bravo/passion based ROM's Most issues stem from using ROM's from other devices/chipsets. I'm personally happy with GingerBread based on Passion sources!
i am not a dev but there are some roms in this forum that we must give credit to as not being half baked like motomans mytouch rom everything work on it and it is very snappy and responsive also typhoons rom is really good too i can see from there rom that there are those who really treat hd2 like a really android phone
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