Hi,
i am pending between Desire and the N1 my doubts are:
1- How about the extra ram benefits of the Desire RAM: 576 MB versus the 512 MB RAM of the Nexus?
2- i know that HTC have a very strong XDA community so i am concerned that in the future XDA Roms and hacks for N1 are more faster droped then the HTC desire because although it is known that both use the same hardware but the Desire have more RAM, radio and perhaps a a better camera ("offering a solid 30 frames per second at D1 quality. The Nexus One only has D1 recording at a minimum of 20 frames per second") and perhaps other stuff so in the future let´s say when Android 2.3 gets out one can´t put it on N1 although there is a cooked rom for Desire because there are slight hardware differences
1. Yes, the desire has more ram, some will be required for Sense UI to run well, some more might be used for running programs
2. i think developers will naturally be attracted to the nexus one over the desire because the nexus one is a developer phone, it is easily hackable, and very flexible. the sense UI is proprietary which adds an extra problems when trying to fiddle with it.
Thanks for the fast response liam.lah
I mean if the the extra ram of the Desire RAM: 576 MB versus the 512 MB RAM of the Nexus will make a significant difference?
Have you considered the fact that n1 will get instant updates when google releases a new version of android? htc will make you wait a bit before they release their updated senseui+rom. i think that would also annoy devs.
the extra ram will benefit the sense ui interface, by making it smoother, but n1 doesnt have sense ui so that 64mb ram isnt making a difference to n1's speed.
edit: the desire also looks alil uglier - in my opinion (the buttons at the bottom ruin the sleek look)
mythamp said:
edit: the desire also looks alil uglier - in my opinion (the buttons at the bottom ruin the sleek look)
Click to expand...
Click to collapse
I completely agree
Don't forget that sometimes HTC seems to artificially hold back updates to help sales of new models.
Look at the Hero/Legend. Same damn phone pretty much, but HTC isn't pushing an update to 2.1 to the Hero so it doesn't cannibalize sales of the Legend, which is sitting at 2.1 with identical guts inside. Totally artificial roadblock.
Who knows if that will happen with the Desire and some future HTC model.
Also..The desire does not have North American 3G, so that would be a dealbreaker for me personally.
the RAM makes no difference in my opinion. its virtually identical.
Thanks all
i already order my Nexus One
I already seen an review where the Desire was a little slower compared to the N1 because because of the sense ui. The reviewer said that the Sense ui in the HD mini was more fluid and the mini has an 600 mghz Qualcomm CPU/GPU. I can´t remember if it´s the first time that HTC puts its ui in an Android phone i know that they do that in Winmo phones since the Kayser so maybe it´s more optimized for this OS. But the reviewer didn´t tell also who many colors each cphone was using.
Tech9000 said:
Thanks for the fast response liam.lah
I mean if the the extra ram of the Desire RAM: 576 MB versus the 512 MB RAM of the Nexus will make a significant difference?
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but doesn't HTC often include the modems RAM in its total RAM. So the ram is actually the same. It makes sense. Why would HTC add 64 mb extra RAM it's just kind of weird, they would have to add a whole new chip for just 64 mb.
I already seen an review where the Desire was a little slower compared to the N1 because because of the sense ui. The reviewer said that the Sense ui in the HD mini was more fluid and the mini has an 600 mghz Qualcomm CPU/GPU. I can´t remember if it´s the first time that HTC puts its ui in an Android phone i know that they do that in Winmo phones since the Kayser so maybe it´s more optimized for this OS. But the reviewer didn´t tell also who many colors each cphone was using.
One thing to be aware of regarding the GN1 is that it actually ***IS*** an HTC phone, which means that the updates are STILL in the hands of HTC. Direct from the horse's mouth, google again screwed up and failed to insist that HTC hand over the full source code and specifications.
Just like HTC DREAM support was dropped prematurely, GN1 will suffer the exact same fate.
whatwhat456 said:
Why would HTC add 64 mb extra RAM it's just kind of weird, they would have to add a whole new chip for just 64 mb.
Click to expand...
Click to collapse
It does seem odd, especially since the 512MB RAM and FLASH of the N1 are both in a single chip, I don't know if that's true for the Desire too?
I was thinking that perhaps the additional 64MB was "bundled" in some other chip on the phone(s), but only enabled on the Desire?
mythamp said:
edit: the desire also looks alil uglier - in my opinion (the buttons at the bottom ruin the sleek look)
Click to expand...
Click to collapse
Next to the Nexus One, the Desire looks like it was designed by those Volvo engineers canned in the 80's for making their cars so ugly!
Just kidding, the Desire is still a nice looking piece of harware, but I like the lines of the Nexis One better.
And yes, the N1 is a Dev phone, dirt simple to modify and updates will be available for it faster. Rooting the Desire so far is a lot more involved. (Paul @Modaco.com) just completed the task today for SOME of them.
The upside for Desire development is that it's likely to sell 25 times better than the N1, meaning that there are going to be plenty of people (including Paul) tinkering with it.
I don't think you can go wrong with either one, but my personal preference is still the N1 over anything currently available. In time, I am sure that will change.
lbcoder said:
One thing to be aware of regarding the GN1 is that it actually ***IS*** an HTC phone, which means that the updates are STILL in the hands of HTC. Direct from the horse's mouth, google again screwed up and failed to insist that HTC hand over the full source code and specifications.
Click to expand...
Click to collapse
Unless you're the horse, I'd like to see the link to the horse's mouth.
Tech9000 said:
I already seen an review where the Desire was a little slower compared to the N1 because because of the sense ui. The reviewer said that the Sense ui in the HD mini was more fluid and the mini has an 600 mghz Qualcomm CPU/GPU. I can´t remember if it´s the first time that HTC puts its ui in an Android phone i know that they do that in Winmo phones since the Kayser so maybe it´s more optimized for this OS. But the reviewer didn´t tell also who many colors each cphone was using.
Click to expand...
Click to collapse
Not the first for SenseUI in Android - only the first time in Eclair.
hey guys,
as one who gave up on iphone 3g and got htc magic...
I can tell that all roms i've tried up to this date includes 710Mhz OC wont give me the smoothness I've had in iphone in terms of slide interface and browser....
I can go into web site, and zoom, slide wont be smooth as it was in iphone...
Any rom exist that can give me this smooth experience?
thanks!
First off Wrong section.
Secondly Wait for the official 2.1 the browser is much improved.
when should be the official 2.1 for magic?
thanks!
Taknarosh said:
-- Wait for the official 2.1 the browser is much improved.
Click to expand...
Click to collapse
When official HTC 2.1/2.2 will be released for Magic?
Any day now.... Hopefully
Even the eclair browser isn't much improved, it just isn't as slick, and it probably wont ever be.
i dont think that will ever happen
but we can hope so
Same here just can not stand the "Jerkyness" of android.
hmm...if want iphone-like smoothness my advice : buy an iphone
yes browser and other features can be improved in new android version (2.1, 2.2, etc) but dont forget magic/touch3g come with limited hardware specs (528mhz pross,512rom 288ram, etc) so we cant expect much from that..
+ the rom itself (for example htc rom) is loaded with so0 much things that require more memory and higher spec, unless we r willing to use vanilla/plain rom...
For me it's now smoother than ever before. Lags only with big sites like desktop Facebook etc.
Details:
HTC Magic 32A
FroyoRedux 1.9.5
pershoot OC kernel @ 576Mhz (With SetCPU calibration for amount of use)
Startup cleaned
Compcache, JIT, surface dithering, VM heap size at 16m
ADW Launcher, stock browser
Would it be possible for someone to port over an android 2.2 sense Rom from the desire such as
This
http://forum.xda-developers.com/showthread.php?t=768703
or this
http://forum.xda-developers.com/showthread.php?t=791315
I'm not a ROM building expert by any means, but my guess is that this idea would be VERY difficult if not impossible, because the Desire has a 1 GHz processor and a 480 x 800 screen. So porting this over to our Hero would involve a ton of work in kernel modification, not to mention editing probably every single apk to fit our smaller screen size. It's the same reasons we can't port the 2.2 Sense EVO build.
Our best bet for a Sense 2.2 port is from the HTC Legend, which uses the same size screen as the Hero (320 x 480) and a 600 mhz processor. A lot less work involved in that port.
Thanks for the reply I guess I should've looked up the specs for the desire. I was under the impression it was about the same as the hero.
Sent from my HERO200 using XDA App
The title says it all. Can my captivate run Ubuntu as smooth as it does here?
(and there are more examples)
I KNOW it's possible to run it too... i already saw a lot of tutorials.. (all with CHROOT.. is there other way?)
The HD2 has 1 GHz Qualcomm Snapdragon and GPU: AMD z430 OpenGL ES 2.0 Support ... isnt better the captivate?
I know Cappy has only 300, 340 Mb of ram (with CRoms .. while HD2 has 576Mb)
But c'mon... it MUST be a way to run it as smooth on Captivate!
Esteban.
Mn ... I already found http://blog.coralic.nl/2010/08/17/ubuntu-on-samsung-galaxy-s-android/ (Coralic been user of XDA) . I know it runs "smooth".. but maybe lags a bit because VNC... what type of comunication between VM and WinMo there is in the HD2 that makes it even MORE smooth? =0
And also, it says "made porting code from android"... I dont understand xD
Only reason I am putting this is because I want devs to possibly answer this one.
HTC Desire C specifications have been outed.
http://www.gsmarena.com/htc_desire_c-review-785.php
It uses a Cortex A5 core. But graphics are still Adreno 200.
Would it possibly share OMX libraries with the Nexus One's QSD8250/Adreno 200 so we can finally fix those issues we have?
Dsire V is similar.
RUU links (from http://forum.xda-developers.com/showthread.php?t=1710312):
Desire C:
http://www.hotfile.com/dl/156147909...H_1.05.98.08M2_release_260338_signed.exe.html
Desire V:
http://down2.zhangku.com/htcrom2/De...34D.29_20.21.30.23U_release_264969_signed.zip
Desire V has same screen resolution. Or is it a simple ROM port? A5/A8 are supposed to be are supposed to be application compatible.
I was definitely having a look at those 2 new phones for China market!
But, take in mind that Desire C have a different, maybe downclocked I think, Adreno 200 gpu, while Desire V has Adreno 200 gpu as ours!
Désire c has different screen resolution
Sent from my Nexus One using Tapatalk 2
xaueious said:
Only reason I am putting this is because I want devs to possibly answer this one.
HTC Desire C specifications have been outed.
http://www.gsmarena.com/htc_desire_c-review-785.php
It uses a Cortex A5 core. But graphics are still Adreno 200.
Would it possibly share OMX libraries with the Nexus One's QSD8250/Adreno 200 so we can finally fix those issues we have?
Dsire V is similar.
RUU links (from http://forum.xda-developers.com/showthread.php?t=1710312):
Desire C:
http://www.hotfile.com/dl/156147909...H_1.05.98.08M2_release_260338_signed.exe.html
Desire V:
http://down2.zhangku.com/htcrom2/De...34D.29_20.21.30.23U_release_264969_signed.zip
Desire V has same screen resolution. Or is it a simple ROM port? A5/A8 are supposed to be are supposed to be application compatible.
Click to expand...
Click to collapse
Reading from the Desire forum, DK Zero said he is already using the new Adreno driver.
Wrong section. This is a question, not a dev thread.