Related
Which software to use?
In my humble opinion: None......for the Qualcomm there is no software availalble to overclock it....but in time it will come...
try this out guys. application specific.
All this seems to be doing is to change the priority of the threads running certain applications. It does not overclock the CPU like OMAP did.
anyway does this work?
or its like the sktools optimization?
Any progress out there on a safe program to overclock a Kaiser? WM6 is definitely faster than WM5, but alot slower than my old Palm OS Treos.
thanks,
d
I'm also waiting for a piece of software that will allow me to overclock my Kaiser, but still there is no progress at all. As they say - patience is gods' virtue (-:
has anyone tried htc performance?
I believe I read helmi had a hand in creating it???I know this has been used on a few different devices and is very low on batti draw but no one quite knows how it works.Really makes a difference on my device but Im not sure if it would be safe to use or even work with the proccessor on the kaiser.
With the battery life as borderline as it is with the Tilt/Kaiser, I'd shy away from overclocking. You'll get lightening fast speed for the 5 minutes of battery life
ya but...
ya but... with the video drivers we're missing and an overclocker the phone would be lightning quick.Also I was reading that the reality is with the right programmers the next gen phones kaiser , dream and a few others a playstation 2 emulator on the ppc would be possible. imagine being on a plane cut off 3g and phone functions and play ps2 games on your phone. plus with extended and/or extra batteries that are now becoming available...
I do not see the logic. The Kaiser is so fast and has so much memory, why would you risk bricking or prematurely damaging your phone? Just my opinion
punkhawaiian said:
I do not see the logic. The Kaiser is so fast and has so much memory, why would you risk bricking or prematurely damaging your phone? Just my opinion
Click to expand...
Click to collapse
Glad to learn that my Kaiser is so fast ! I guess you don't use games or heavy graphical applications, because then you would see that the Kaiser is not faster than an HTC Prophet wich is overclocked at only 240 Mhz ! (380 Mhz for the Kaiser...). Also if you want to play VGA videos, the speed is not good enough (wich it should be if you look at the Qualcomm processors capabilities, but as everyone know here, HTC did'nt make the drivers for that).
I am very disapointed by the fact the Kaiser is not a VGA device, but even more disapointed when you see that it is not even faster than a VGA device !!! So at this low speed, where is the interest of having a QVGA screen compared to VGA ?
Definitly, an overclocker tool may help me to consider keeping my Kaiser (even if I think that at this device price, it's a shame to be obliged to overclock it to have a decent speed ...).
The prophet is slower in my opinion, I don't own a Kaiser, but whenever i use it everything happens faster than on my overclocked WM6 Prophet (overclocked to 286MHz normally).
How does the speed compare to the TyTN, mine should be here on Wednesday... I can't wait!
someone found a tool that really works ?
WOW! and I thought we had enough problem threads on here with overheat and battery deaths!
Look out for many more!!
I upgraded to kaiser from a Tmob Wing, for that I played with an overclocker called Fl0wt. Which did seem to work BUT the battery becames a flamethrower of heat and the battery life was sucked away in no time. this wasnt a big clock speed step either. The parts just arnt suited for the additional heat it seems. plus it felt dangerously hot...like "hit the dirt its going to blow" hot. not worth the risk in my oppinion...but hey thats just me
Can you post a link to "Fl0wt" ive searched far and wide and found nothing. Please post a link.
Cheers !
dizzy33 said:
Glad to learn that my Kaiser is so fast ! I guess you don't use games or heavy graphical applications, because then you would see that the Kaiser is not faster than an HTC Prophet wich is overclocked at only 240 Mhz ! (380 Mhz for the Kaiser...). Also if you want to play VGA videos, the speed is not good enough (wich it should be if you look at the Qualcomm processors capabilities, but as everyone know here, HTC did'nt make the drivers for that).
I am very disapointed by the fact the Kaiser is not a VGA device, but even more disapointed when you see that it is not even faster than a VGA device !!! So at this low speed, where is the interest of having a QVGA screen compared to VGA ?
Definitly, an overclocker tool may help me to consider keeping my Kaiser (even if I think that at this device price, it's a shame to be obliged to overclock it to have a decent speed ...).
Click to expand...
Click to collapse
I beg to differ.
I play LOTS n LOTS of games on my TyTN II AND I watch full feature movies and I use Outlook AND I use GPS AND I use internet (Netfront v3.5) and I have yet to find a speed problem as mentioned in this here cheese and whine forum.
Some of the games I have on my TyTN II are:
Cybersaurus
Warfare Inc
Machines at War
Bejeweled 2
Zuma
Ackys XP Breakout
Shattered Worlds
Call of Duty 2
Darxide EMP
gfDoom
Fast Future Race
G-Prime Extreme
Interstellar Flames
Skyforce Reloaded
Quake & Quake 2
Sinbad Return of the Legends
Flux Challenge
Is this a good enough sample for you?
THE KAISER NEVER CLAIMED TO BE A VGA DEVICE. IT IS STRICTLY QVGA....NOW GET OVER IT!!!
I am starting to believe that AT&T roms are fraught with problems.
I don't have that problem here in SA.
My TyTN 2 is MUCH faster than my iMate KJam....MUCH MUCH FASTER!!!
So I don't know what you are referring to.
MACkjam said:
I beg to differ.
I play LOTS n LOTS of games on my TyTN II AND I watch full feature movies and I use Outlook AND I use GPS AND I use internet (Netfront v3.5) and I have yet to find a speed problem as mentioned in this here cheese and whine forum.
Some of the games I have on my TyTN II are:
Call of Duty 2
Is this a good enough sample for you?
Click to expand...
Click to collapse
I have Call of Duty 2 too, and it's really slow on the Kaiser compared to other devices. You should see how it runs on other PPC's...
MACkjam said:
I am starting to believe that AT&T roms are fraught with problems.
I don't have that problem here in SA.
My TyTN 2 is MUCH faster than my iMate KJam....MUCH MUCH FASTER!!!
So I don't know what you are referring to.
Click to expand...
Click to collapse
I have an T-mobile Kaiser and it's definitely not much faster than a Magician. The difference is really, really small.
And we're referring to the fact that there are no drivers for the ATI Imageon hardware. Thanks to this, everything needs to be rendered by the CPU.
I hade both phones in my hand so I decided to make small test. We all know about drivers problem on S730 but this is worst then I thought.
Both phones where running wm6, and both phones where restarted before testing.
Total RAM:
S710: 49.3 MB
S730: 43.6 MB
S710 wins here...
Why is here a difference I don't know, but I think that missing memory of 64MB RAM is reserverd for phone or graphic operation.
Free RAM after power on:
S710: 25.2 MB
S730: 17.0 MB
Again S710 wins...
As I didn't have any programs for graphic performance testing I tested pure user experience. Menu browsing is a little bit faster on S710, drawing homescreen by pressing home button is a much faster on S710, allmost instantaneous.
And now the real test. I loaded on both device pretty large web page in ie. Page was combined of photos and text. I scroled from top to bottom and maesured time needed for scrolling. S730 was more then 2 times slower and he has 400Mhz process vs 200Mhz procesor on S710, total disaster. So based on hardware, S730 is 5 times slower then S710, this is a big shame for HTC.
I hope HTC will fix this driver issues soon, because in this state this devices is
shame for HTC company...
my S730 can playback most video files without conversion compared to the S710
also, the bluetooth stereo audio quality is much improved with the S730
i changed my S730 homescreen from the default to my own custom one, and it loads much faster now
i use opera webbrowser and everything is much quicker
the S710 still has better RAM handling though
but i'd still take my S730, only because I use it more for media/video playback
for the drivers issue:
everyone should participate!!!+ http://www.htcclassaction.org/
That's actually just the type of info I've been looking for! Thanks! I have been seriously debating whether to upgrade to the HTC S730 or the HTC Touch Cruise, but your review just about confirms it for me.
My freaking over that a year old HTC Tornado (Qtek 8310) plays movies perfectly and running WM6 on a custom ROM has listed:
48.69 MB RAM Total
25.52 MB RAM Free (upon startup)
If HTC would just get their act together!!! Otherwise please Apple release a 2nd gen IPhone with 16GB and an open SDK, and I'll be an immediate convert.
sonus said:
That's actually just the type of info I've been looking for! Thanks! I have been seriously debating whether to upgrade to the HTC S730 or the HTC Touch Cruise, but your review just about confirms it for me.
My freaking over that a year old HTC Tornado (Qtek 8310) plays movies perfectly and running WM6 on a custom ROM has listed:
48.69 MB RAM Total
25.52 MB RAM Free (upon startup)
If HTC would just get their act together!!! Otherwise please Apple release a 2nd gen IPhone with 16GB and an open SDK, and I'll be an immediate convert.
Click to expand...
Click to collapse
well... actually the touch cruise has the same "problem" as the s730, lack of proper graphic driver.
concerning the 710 vs 730... well not certainly a huge improvement, but i would not hesitate a sec to go for the latter. actually you can find proper comparison tests, even in this section of the forum if you look back at the first posts.
cheers
Thanks vrolok. I guess my concern is that if I'm going to spend over $500 on an HTC device, I want a legitimate upgrade from my last device... As far as my last statement, I guess I spoke too quickly, 16GB IPhone was announced today<<<It still needs A2DP, and SDK, and Skype for me to switch over tho ;-)
For now, I guess I'll just continue on with my lowly Qtek until either HTC or Apple provide some more impetus.
I really hope for new drivers. update firmware in my opinion can solve the problem with s730. I think that htc will perform something about s730, actually if you see in the official site, the relative s730 part is under construction, because without any download like the other product, actually it's N E W !!!
Precisely. Optimised firmware can turn the situation into oposite.
Or HTC will concentrate to new models without updating the firmware on old ones ;-)
According to my experiences with Wings and Qtek 8310, event this "slow" ROM gives me almost twice more speed at activesync and copying data (~450KB/s), as well as with Card Export i can copy almost at 800KB/s speed..
omadon99 said:
I hade both phones in my hand so I decided to make small test. We all know about drivers problem on S730 but this is worst then I thought.
Both phones where running wm6, and both phones where restarted before testing.
Total RAM:
S710: 49.3 MB
S730: 43.6 MB
S710 wins here...
Why is here a difference I don't know, but I think that missing memory of 64MB RAM is reserverd for phone or graphic operation.
Free RAM after power on:
S710: 25.2 MB
S730: 17.0 MB
Again S710 wins...
As I didn't have any programs for graphic performance testing I tested pure user experience. Menu browsing is a little bit faster on S710, drawing homescreen by pressing home button is a much faster on S710, allmost instantaneous.
And now the real test. I loaded on both device pretty large web page in ie. Page was combined of photos and text. I scroled from top to bottom and maesured time needed for scrolling. S730 was more then 2 times slower and he has 400Mhz process vs 200Mhz procesor on S710, total disaster. So based on hardware, S730 is 5 times slower then S710, this is a big shame for HTC.
I hope HTC will fix this driver issues soon, because in this state this devices is
shame for HTC company...
Click to expand...
Click to collapse
Maybe. But when it comes to load a big program, like pocket snes (super nintendo emulator) the s710 is sooo slow! When I run the same program on my s730 it plays real fast just like using a super nintendo console!
In my opinion, the new 400mhz processor makes a really BIG difference.
Hello Everyone,
I just came up with an interesting idea, following a conversation with my friend. He said: the Diamond1 is still an awesome phone, but it doesn't have enough RAM for the newer Sense and Manila ROMs. I just said: why can't you just buy a DIAM500 which has 288 MB of RAM? He said, the DIAM500 is for CDMA networks, but he uses GSM.
But the idea is still there, if the engineers could fit 288 MB of RAM into the DIAM500 why can't we just change the RAM chips in the other Diamond variants, and have the same amount of RAM as the CDMA versions? We did the same with the HTC Universal, it looks possible.
First of all I am trying to get some pictures about the System Board of these two machines, to see if they are even comparable, or (would be ideal) almost the same.
Anyone has any thoughts, or pictures, please don't hesitate to write in this thread.
Thank you,
DOMy
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.
i thought the cappy had 512 mb of ram... why do all the roms have like 341? im confused >.< either i looked at 3 faulty spec sheets for the captivate or we arent utilizing the full ram potential for the captivate. would someone explain the truth on this matter to a captivate noob like me?
i could be wrong but i believe the 341 is available to use ram, while the rest is being used by the phone to function.
nehal51086 said:
i could be wrong but i believe the 341 is available to use ram, while the rest is being used by the phone to function.
Click to expand...
Click to collapse
that would make sense, but that makes the specs misleading... i traded my HD2 for a cappy because the spec sheet said 512mb of ram and the HD2 only has 411 available to the OS when running android from nand because the rest is dedicated to winmo only (which sucks massively), and i wanted more ram lol, guess i should have looked harder into things, but regardless the captivate is "better" in very many areas, but RAM is literally my deciding factor for so many things lately (like t-mobile with the sensation or sprint with the evo 3d, i would say evo 3d because it has 256mb or so more ram)
This question has been asked and answered several times....
the phone does have 512mb of ram. Like the person above me said the phones os and graphics take up a portion of the ram. All computers and smart phones work the same way.
As a side note android handles ram very well. You don't need to manage it at all by freeing it up. free ram is wasted ram as the os will have to load it back up anyways
Sent from my GT-I9000 using XDA App
crystalhand said:
This question has been asked and answered several times....
the phone does have 512mb of ram. Like the person above me said the phones os and graphics take up a portion of the ram. All computers and smart phones work the same way.
As a side note android handles ram very well. You don't need to manage it at all by freeing it up. free ram is wasted ram as the os will have to load it back up anyways
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i know this very well, free ram can be considered wasted ram, unless you need 200mb or so free for a tegra class game, but i think android handles ram awesomely to an extent but can be improved by implementing autokiller memory optimizer in a knowledgable and appropriate way that doesnt hurt optimizations android already has in place, zipaligning, increasing the dalvik heap size, etc... can all be done, im not asking about how android handles ram or anything, and im sorry i didnt know the question had been asked several times i am brand new to the captivate today, literally, and was doing not but seeking information i didnt understand or know, thank you for the explaination though i appreciate it, and im glad to know that my new captivate will utilize the left over 171mb of ram for something unlike my HD2 that couldnt access the last 100mb because it was designated to winmo only. i had an idea that was the case and i was just clarifying to myself because i kept reading rom changelogs stating "enabled more ram now 341mb available" or something along the lines of that and thought to myself "there should be more available already" lol
I honestly think 341MB is enough.
341 MB is alot. But something is taking all that up too. On a fresh boot, half of it is used, and I have 140~170 MB. Its even worse on GB. Most ive gotten is 100 MB free.
So if the half of the 341 plus the mysterious 171 MB that is nowhere to be found, I dont get whats using the other 171 that is not part of the 341. Lol confusing
Same happens to me. Who knows, lol
Sent from my GT-I9000 using XDA Premium App
I think its the user interface graphics, like scrolling quality is good because that ram is dedicated to things
like that
Sent from cyanogen mod 7