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
Related
I have seen it asked, I have NOT seen it answered and maybe it should be, we are not all Android literate .... whats the difference between the builds. what makes Froyo differant then Evo, what makes Desire so special ? should be a sticky if people do answer... how do you have an Android QA and not have that front and center
ok im not going to get into too much detail on this because the information is readily available all over these forums....
froyo = the version of android (2.2) the one before was eclair (I think) the next one will be gingerbread..... google decided it would be a good idea to name them after food for some reason....
my guess is that the company is secretly run by a 4 year old.....
desire / evo = different models of android phones that the android builds are taken from......
Froyo means Android v2.2. This can be EVO or Desire. Desire and EVO builds are made of the HTC RUUs of the devices "EVO" or "Desire".
Please correct me if I'm wrong xD...
was too slow
nah my fault..... was too quick
Sorry I'm also new to all this. So apart from the apparent sources of the builds, how are they different in terms of functionality and compatibility to our HD2?
I have tried both the desire build and the evo build, and didn't notice much different.
However, I have heard people (including Darkstone) saying that the desire builds work better overall due to hardware similarities. As far as I know, MDJ has also stopped updating his only evo build, and is currently actively working on 3 desire builds. I'm running his evo build right now and loving it.
I'm just wondering what are the specific underlying differences between an evo and a desire build? Why would some users and clefs prefer the desire build over an evo build?
Thanks!
jparity said:
Sorry I'm also new to all this. So apart from the apparent sources of the builds, how are they different in terms of functionality and compatibility to our HD2?
I have tried both the desire build and the evo build, and didn't notice much different.
However, I have heard people (including Darkstone) saying that the desire builds work better overall due to hardware similarities. As far as I know, MDJ has also stopped updating his only evo build, and is currently actively working on 3 desire builds. I'm running his evo build right now and loving it.
I'm just wondering what are the specific underlying differences between an evo and a desire build? Why would some users and clefs prefer the desire build over an evo build?
Thanks!
Click to expand...
Click to collapse
ahh haaa see this guy gets my question =P I know that the builds are based on Official android releases ... duh, but whats the REAL difference in what they are capable of. I to have installed many different builds here and have favorite chefs and builds I use daily, but I am still not sure what the real difference is other then minor cosmetics in most cases ....
Android 3.0 Preview SDK is now available
More infos you can find here:
http://developer.android.com/sdk/preview/index.html
Saw that yesterday.
But as far as I know it is Tablet only.
Yes,but multiple screen support is there,but needs developing
again!
Well since it is not going to work on a Hero, Don't see the use in posting it here, but maybe better for general dev?
Some similar threads about Gingerbread,Android 2.1 SDK
here to,so think we can stay here!
Android 2.3 works,maybe 3.0 too,Devs can make it possible!
I'm not a developer, but Honeycomb would be difficult even for the likes of Desire. It is very tablet orientated. The next Android for mobile phones is 2.4 Ice Cream, by the time it comes out a lot of the devs would've moved to a different phone.
Sent from my Hero using XDA App
As i understand it google have anounced it there not goung to be any hardware ristrictions on android 3.0. I have a feeling that differnt features will atomatically enabe/disable themselves dependind on the specs of the divice running it. You can already see an example of this in latest google maps which checks the gles version in build.prop to decide weather or not to implement tilt and compass.
Sent from my HTC Hero using Tapatalk
Their maybe no hardware restrictions, but there will be minimum requerements.
And you say devs can make it possible.
You see devs around??
Its a warzone out there....
Most of em are gone, so I am just focusing on 2.3,
and I don't get the comment you made on well there is a 2.2 SDK topic. Duh, but we all knew that is definitly possible to run on the Hero. 3.0 99% That it will never been 100% same as the 2.2 Sense is.
But we will see. The Hero is almost a dead device. So.
And you say it yourself
HTC Hero sold- not a real Gingerbread and Power to low for new Android
Sooo BTW That statement is so wrong...
If you knew anything about android, you would know honeycomb is TABLET ONLY. there is no chance of seeing this on rmthe hero. Wait for 2.4 ice cream but I can't see that on the hero either seeing as there's no devs left.
I think a mod should delete this thread
sjknight413 said:
If you knew anything about android, you would know honeycomb is TABLET ONLY. there is no chance of seeing this on rmthe hero. Wait for 2.4 ice cream but I can't see that on the hero either seeing as there's no devs left.
I think a mod should delete this thread
Click to expand...
Click to collapse
Noo needs to
rdejager said:
Their maybe no hardware restrictions, but there will be minimum requerements.
And you say devs can make it possible.
You see devs around??
Its a warzone out there....
Most of em are gone, so I am just focusing on 2.3,
and I don't get the comment you made on well there is a 2.2 SDK topic. Duh, but we all knew that is definitly possible to run on the Hero. 3.0 99% That it will never been 100% same as the 2.2 Sense is.
But we will see. The Hero is almost a dead device. So.
And you say it yourself
HTC Hero sold- not a real Gingerbread and Power to low for new Android
Sooo BTW That statement is so wrong...
Click to expand...
Click to collapse
No its not only for tablets, this has already been established.
All of the apps have multiple DPI res folders in them (MDPI, HDPI, Extra Large, NoDPI) so it will work on phones - not just tablets.
And Yes,I see Devs for 2.3 so the same Devs maybe developing/porting 3.0
http://pocketnow.com/android/android-30-honeycomb-how-it-might-work-on-smartphones-video
And Yes I said Power to low for new Android versions
does not mean this will not works.
Perhaps not so smooth and not with all functions.
but
you might be right, however 2.4 is I think going to be pretty much the same OS as 3.0 however the 2.X codeline is for phones while the 3.x codeline is for tablets.
Which is definitely the stupidest thing I've heard of in a very long time.
Any developer would twitch at the concept of two different OS codelines to maintain which would otherwise be very similar, unless of course google's keeping some bizarre building structure where it's all one shared resource except whatever is unique to each release line. But that isn't something I personally have seen done before.
Mostly the way they broke up the numbering by a huge value of, wait for it, ONE (2.x versus 3.x) to differentiate between phones and tablets... well that's pretty silly too. Numbering shouldn't be relevant. It should be called two different things, like Android versus AndTab or something like that. But then that would mean we're all talking on our Roids (versus ours tabs) which is, admittedly, kind of rude ;-)
I'm more interested in how they solve this over 20 years. Are we going to expect an Android 2.200.9132 for my phone and 3.7.20 for tablets?
riemervdzee said:
I'm more interested in how they solve this over 20 years. Are we going to expect an Android 2.200.9132 for my phone and 3.7.20 for tablets?
Click to expand...
Click to collapse
and 4.89.20 for laptops?
They will stop changing the whole OS sooner or later, and just provide smaller focused updates. It's very stupid to have 10 different major android versions running at the same time. If 80% of the devices are running Android 2.4.x, things should be easier. They're just following the Ubuntu-like releasing schedule: 2 versions a year. That's the way I see it. They WILL have to stop doing this, they can't go on improving forever.
goodnews xD
im expected.
Android 3.0 Honeycomb won’t be Coming to Smartphone, just for Tablets,says Google:
http://www.pcmag.com/article2/0,2817,2379271,00.asp
Ganii said:
Android 3.0 Honeycomb won’t be Coming to Smartphone, just for Tablets,says Google:
http://www.pcmag.com/article2/0,2817,2379271,00.asp
Click to expand...
Click to collapse
yea
it'll be 2.4 for us phone ppl
RaduG said:
They will stop changing the whole OS sooner or later, and just provide smaller focused updates. It's very stupid to have 10 different major android versions running at the same time. If 80% of the devices are running Android 2.4.x, things should be easier. They're just following the Ubuntu-like releasing schedule: 2 versions a year. That's the way I see it. They WILL have to stop doing this, they can't go on improving forever.
Click to expand...
Click to collapse
Hardware moves fast, demand for said hardware even faster. They have to keep up, if not ahead!
I had a feeling this would be the case since we first saw shots of 3.0 running on a then-unidentified Motorola tablet. Looking at it now, there's absolutely no way that this is plausible to run on handsets; for one, it likely demands a decently high hardware spec to run efficiently, and even if you've got something like the Optimus 2X for example, the screen's far too small to allow for efficient usage.
In all honesty, it's likely we'll see divergence of Android into 2 distinct OSes; handset-based (2.3 onward) and tablet-based (3.0).
so....
HTC EVO 4G, Nexus One, Desire HD and Incredible joined the Honeycomb world....
it seems that, in this joyous family, missing only our HD2 ....
is possible or not ?
....that's the question
lorezz said:
is possible or not ?
....that's the question
Click to expand...
Click to collapse
Yes.
...............
Honey Monster
What is Honeycomb, I've heard (read) a few posts refering to this, but the only Literature I can find refers to Android 3.0 which is supposedly Tablet only. Can someone show me the way to enlightenment so I too may share the dream. I would love to add more OS to the seemingly endless capabilities of my HD2.
It is meant for tablet only. However some have modified the roms to run on Phones.
However, apparently the current phone Honeycomb ROMS are flakey to say the least.
I am so used to a stable working gingerbread I'd be hesitant to jump ship until its been through a few iterations on the HD2
GG
Hansel & Gretel
Is Google trying to fatten us up by feeding us all these sweets before throwing us into the oven?
What is Gingerbread, Android 2.x??
GodsGift said:
It is meant for tablet only. However some have modified the roms to run on Phones.
However, apparently the current phone Honeycomb ROMS are flakey to say the least.
I am so used to a stable working gingerbread I'd be hesitant to jump ship until its been through a few iterations on the HD2
GG
Click to expand...
Click to collapse
Well my interest would simply be for trying it out for fun and curiosity more then as a daily OS.
Its primerily for tablets but would be nice to try on our HD2 screens, bit like the ubuntu UI.
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
I am using HTC HD2 with android nand roms. After Froyo wich was really good on HD2 i installed some gingerbread ROMs.
I love HTC sense so i always use Roms with sense UI.
Like all other using gingerbread i have the typical graphic glitches. There is a fix of this, but using this will bring the camera to stop working.
My Question to the developers:
Is there a real chance, that this bugs will be fixed and camera and graphics will do fine?
Can we support the developers fixing this issues?
Will there be a fix from HTC/when?
I am very happy with android and appreciate the lots of work of the developers. Thank you, its great.
I am thinking about giving my HD2 away and buy a Samsung Galaxy S2.
If there will be fixes of this bug in short time i will keep my HD2 on.
If there is no possibility of fixing this, i will change to Galaxy S2.
Thanks for your hints.
Definitly not the proper section, it should be in Q/A...
BUT :
I'd love to see a dev/chef offering a fully working Froyo Sense. No 2.1 or 3.0. Sense is only experimental now, there is no more stable and up to date version of Froyo Sense which is a shame.
RafDroid is out of date and Incredible S (imilka) buggy with many apps FC...
should post this in Q&A
as for imilkas incredible s build, never had any issues with it and wqas running it for at least a month and half before changing never had any force closes
Try the game Cordy...
fix for graphic glitches?
I installed HTC HD2 Android Gingerbread on Nand. The typicel GB-graphic glitches suck very much.As far as I understand, is it possible for the devs to fix this bugs as soon as HTC releases the Kernel Source Code of GB.
When will HTC release this source?
I am sad about this bugs and thinking of sell my HD2 and buy a Galaxy S2.
Anybody who can give some details?
thommygay24 said:
I installed HTC HD2 Android Gingerbread on Nand. The typicel GB-graphic glitches suck very much.As far as I understand, is it possible for the devs to fix this bugs as soon as HTC releases the Kernel Source Code of GB.
When will HTC release this source?
I am sad about this bugs and thinking of sell my HD2 and buy a Galaxy S2.
Anybody who can give some details?
Click to expand...
Click to collapse
Everything is possible and almost all things made possible on HD2. I don't think fix for this issue will be impossible. Just its about time. Don't worry, Android isn't a windows mobile or windows phone for someone to protect.
Keep hopes!
Thanks...
Best Regards
thommygay24 said:
I am using HTC HD2 with android nand roms. After Froyo wich was really good on HD2 i installed some gingerbread ROMs.
I love HTC sense so i always use Roms with sense UI.
Like all other using gingerbread i have the typical graphic glitches. There is a fix of this, but using this will bring the camera to stop working.
My Question to the developers:
Is there a real chance, that this bugs will be fixed and camera and graphics will do fine?
Can we support the developers fixing this issues?
Will there be a fix from HTC/when?
I am very happy with android and appreciate the lots of work of the developers. Thank you, its great.
I am thinking about giving my HD2 away and buy a Samsung Galaxy S2.
If there will be fixes of this bug in short time i will keep my HD2 on.
If there is no possibility of fixing this, i will change to Galaxy S2.
Thanks for your hints.
Click to expand...
Click to collapse
Dude, have patience. just wait of this problem to be fixed as well. however, if u planned to by galaxy s2 there will not as much support with it as compared to hd2 cuz there are so much developers working on hd2 roms, and i hope that the time is near for a stable sense 3.0 rom for hd2.
CRACING said:
Everything is possible and almost all things made possible on HD2. I don't think fix for this issue will be impossible. Just its about time. Don't worry, Android isn't a windows mobile or windows phone for someone to protect.
Keep hopes!
Thanks...
Best Regards
Click to expand...
Click to collapse
Source Code For Gb kernel are releset Now plz plz fix the gitches
che3ton said:
Source Code For Gb kernel are releset Now plz plz fix the gitches
Click to expand...
Click to collapse
where did you get this information from? there is no source code for desire on the official page http://developer.htc.com/
che3ton said:
Source Code For Gb kernel are releset Now plz plz fix the gitches
Click to expand...
Click to collapse
they will probably fix the glitches once the DESIRE GB kernal source is released
which it seems they have forgotten to do,or they just dont plan on releaseing it
I'm a noob, but... this seems to be desire HC gingerbread source code...
(copy&paste from htc developer download page)
"HTC Desire HD – GB MR – 2.6.35 kernel source code"
here is the link:
http://dl4.htc.com/RomCode/Source_and_Binaries/ace-2.6.35-gb-MR.tar.gz
nushuth said:
I'm a noob, but... this seems to be desire HC gingerbread source code...
(copy&paste from htc developer download page)
"HTC Desire HD – GB MR – 2.6.35 kernel source code"
here is the link:
http://dl4.htc.com/RomCode/Source_and_Binaries/ace-2.6.35-gb-MR.tar.gz
Click to expand...
Click to collapse
Reread your post. HTC Desire HD...
We need the original desire.
Nigeldg said:
Reread your post. HTC Desire HD...
We need the original desire.
Click to expand...
Click to collapse
let me understand...
out HD2 seems to be very similar to desire HD in hardware (the only difference seems to be original OS and Camera, 5 vs 8 MPx) same CPU and same graphic processore.
desire HD already have a gingerbread + Sense official rom. It's only sense 2.1, but we have same glitches problem on any gingerbread + sense rom. the problem seems to be the same...
why we need a desire (not HD) kernel source code? there is no way to use desire HD source?
nushuth said:
let me understand...
out HD2 seems to be very similar to desire HD in hardware (the only difference seems to be original OS and Camera, 5 vs 8 MPx) same CPU and same graphic processore.
desire HD already have a gingerbread + Sense official rom. It's only sense 2.1, but we have same glitches problem on any gingerbread + sense rom. the problem seems to be the same...
why we need a desire (not HD) kernel source code? there is no way to use desire HD source?
Click to expand...
Click to collapse
I thought this at first as well but I can't explain this to you, only a dev or someone more experienced can. But in short, the hardware is not close enough, the DHD has a 2nd generation CPU vs the HD2's 1st gen or something like that, whereas the original desire has the same hardware as the HD2.
TBH, I have no clue in other words.