Related
Hi all... I need your help... I have a Blue Angel and I want to buy a universal. But I read that Universal is very slow in compare with fx. blue angel... Is it tru? How can it be true...! because BA`a processor is 400 mhz..! Please tell me a little abouet universal... What is hot and not... thanx...
BA is 400mhz powering a 320x240 display.
Uni is 520mhz powering 640x480 display.
BA running WM2003se runs from RAM.
Uni running WM5 runs from NAND.
The Uni is slower, but it's a far better device If your BA is running WM5, then it's already slower than the BA running WM2003se, but the display is what makes the Universal great
AlanJC said:
BA is 400mhz powering a 320x240 display.
Uni is 520mhz powering 640x480 display.
BA running WM2003se runs from RAM.
Uni running WM5 runs from NAND.
The Uni is slower, but it's a far better device If your BA is running WM5, then it's already slower than the BA running WM2003se, but the display is what makes the Universal great
Click to expand...
Click to collapse
Thank you for your answer... But my BA with wm5 is very faster then BA with WM2003... And I think speed is VERY important, if you would like enjoy your machine... and yes the display is what makes the universal great : )
by the way... you said Uni running WM5 runs from NAND. What is nand?thanks again...
For an explenation of NAND memory look here: http://en.wikipedia.org/wiki/Flash_memory#NAND_memories
It's true the universal was very slow at first but with the new rom's comming out it actually performs quite up to speed imho.
I agree it's faster than the AKU2 and earlier days, but it's still slow compared to a BA running from RAM, especially when you run things like TomTom or anything else that renders the whole screen in high res.
thanks for link for NAND... Is it so a minus that uni run from nand. Can I also change the Q... What is the plus and minus with the universal... I have now a BA. I know uni has a great display but is there anything else that can be a reason to buy and use an universal in stead of BA?
I Used to have a BA, the universal beats it in every way except size.
Midget_1990 said:
I Used to have a BA, the universal beats it in every way except size.
Click to expand...
Click to collapse
so you say the speed is not annoying...
I don't know how many of you are running the HTC phone skins, but that certainly is a major slow down. If you use the OS default phone skin it speeds things up significantly.
The processor can also be kicked up to full speed (not exactly overclocking, since it's a standard clock speed), and things will fly along, although I've never found the need to do so.
It's fast enough. It's not going to beat Blue Gene or anything, but it works and is a nice device. Particularly at VGA.
V
vijay555 said:
I don't know how many of you are running the HTC phone skins, but that certainly is a major slow down. If you use the OS default phone skin it speeds things up significantly.
The processor can also be kicked up to full speed (not exactly overclocking, since it's a standard clock speed), and things will fly along, although I've never found the need to do so.
It's fast enough. It's not going to beat Blue Gene or anything, but it works and is a nice device. Particularly at VGA.
V
Click to expand...
Click to collapse
Can you tell me how to put the default OS Skin without losing the video call button?
And also how to speed up the processor without overclocking it?
Thanks
I don't use video calling but you can access video calling externally, don't have to use the video call button. However, frankly I've not investigated this much, so in you case it may be worth sticking with the phone skin.
Since it also disables dialing prediction I think, stick it out if you need that stuff.
But do try it with the OS skin just to see how much difference it makes!
Speed up the processor - the standard overclockers do this I imagine.
I wrote a clock speed changer that will notch up the speed: I don't consider this overclocking, since the pxa27x specifies it can be clocked to 624mhz, just normally isn't. This app was unreleased since it's only for my research, and not required since other apps do the same better.
V
VJ: can you recommend an application for the uni to clock it up to 624?
I think Pocket Hack Master is the standard recommendation:
http://forum.xda-developers.com/showthread.php?t=246214
V
vijay555 said:
I don't use video calling but you can access video calling externally, don't have to use the video call button. However, frankly I've not investigated this much, so in you case it may be worth sticking with the phone skin.
Since it also disables dialing prediction I think, stick it out if you need that stuff.
But do try it with the OS skin just to see how much difference it makes!
Speed up the processor - the standard overclockers do this I imagine.
I wrote a clock speed changer that will notch up the speed: I don't consider this overclocking, since the pxa27x specifies it can be clocked to 624mhz, just normally isn't. This app was unreleased since it's only for my research, and not required since other apps do the same better.
V
Click to expand...
Click to collapse
Thanks for the info.
I try'd the OS phone skin and didn't noticed much diference. So I switched back to my previous one from Helmi-c rom.
One bigger problem that I have with this skin is that i'm using the VGA hack version of Helmi_c rom (the latest version) and sometimes when I switch from the phone skin to the today screen, the phone hangs and only the bottom bar works, so I have to rebbot the phone to comeback to normal. I'm using the vga phone hack too.
I don't recommend using it, but have you tried VJBigPhone?
V
vijay555 said:
I don't recommend using it, but have you tried VJBigPhone?
V
Click to expand...
Click to collapse
That is what i'm using, but why don't you recomend it?
Is there any alternative to make the dialpad big for VGA hack?
I thought there were some hacked versions of the Eten skins or similar for VGA... not sure tho. I don't use my own apps..
V
Anybody found anything useful on how to speed up this slow bugger? ive tried cleaner ROMS, wm 6.1, changing the pp, and doing the usual reg hacks for changing the glyph, font, and file system cache as high as they will go but...its still so slow all the time!
for a dual-core, brand new device...i was really expecting more.
anything anyone?
thanks.
You say it's slow but in what sense though..
Also, if you expect it to be PC fast then we all know it's not going to happen. Also, fast could be referring to personal preference (I think), cuz my device is fast in terms of menu responded in timely manner, connection is good enough. For most part, I don't have to wait 8 seconds for something to show up after I clicked it. But some programs I have require a little time to load like sprint tv it takes about 3 seconds.
Also, checkout HTC Performance, some say it worked on Touch some say it doesnt due to dual core in touch.
Good luck.
vboyz103 said:
You say it's slow but in what sense though..
Click to expand...
Click to collapse
i mean that when i click "settings" in the start menu, i have to wait a good 3-4 seconds before it comes up, and another 3 seconds before it will respond. on a clean stock rom, 6.1, or dcd's 0.2.0 rom. messaging is (slightly?) slow to open...
not sure what other specific things there are. the device just seems to be overall sluggish.
thanks for the tip on the htc performance, i will give that a shot and see.
i just wish wizcode could put out their v5 build that supports the 7500 chipset! looks like the wait for a faster device and longer battery is still about a month off sadly...
HTC Performance won't work on the qualcomm processor in your device. I haven't seen any word yet on an overclocker for the qualcomm chips.
I find the vogue quite fast, but not as fast as my 624mhz dell axim x50v with wm6
thats stinkin fast.
My Mogul was faster then the damn Touch guys, come on... half as much RAM, otherwise, same hardware. Explain THAT. If HTC would just get off their collective asses and release the video drivers...
I agree, my XV6700 (WM6, Helmi) was quite a bit faster at some things.
I hate the lag I'm seeing on some of the buttons (end call for one even with hack to speed it up) and others.
trehouse said:
I agree, my XV6700 (WM6, Helmi) was quite a bit faster at some things.
I hate the lag I'm seeing on some of the buttons (end call for one even with hack to speed it up) and others.
Click to expand...
Click to collapse
pretty sure that my dads axim x30, with ppc 2003 or whatever, has a screen that is A HUNDRED times more responsive/sensitive (pretty retarded of HTC to make an all touch device for the masses that isnt have as responsive as a device released 4-5 years ago) and the device just runs so much faster.
everything is instant on the x30. you barely even have to touch the screen, adn BAM. you are already there. whereas on the vogue you would still be in the process of getting the screen to recognize that you had touched it, then wait for it to respond and get moving.
true, that device has a 624mhz processor, but it only has half the ram. this device is 5 years newer with an os 5 years newer, yet still FAR slower.
it makes me so mad how unresponsive the screen on this device is compared to the x30.
I know the HTC Performance app supposedly doesn't work on our touch....but with mine overclocked to 524Mhz, it seems like everything just opens much faster. (I can especially tell with Opera and the Messaging app).
Red49er said:
I know the HTC Performance app supposedly doesn't work on our touch....but with mine overclocked to 524Mhz, it seems like everything just opens much faster. (I can especially tell with Opera and the Messaging app).
Click to expand...
Click to collapse
hmm, strange. i didnt notice any difference when i tried it.
have you tried shutting off the "overclocking", waiting 10 seconds, then shutting down, then waiting 10 seconds, then poking the reset hole and trying the app's mentioned again? is there a definite speed increase if you try doing that?
ludester said:
I find the vogue quite fast, but not as fast as my 624mhz dell axim x50v with wm6
thats stinkin fast.
Click to expand...
Click to collapse
I have the X50V on the lastest wm6 rom and the vogue runs circles around it. The only way the x50v is fast is with one small application open. The only speed advantage I see is in games and videos because of built-in video acceleration.
Nate
Vogue is plenty fast for me.
Regardless of the mythical talk of overclocking your HTC device being a bad thing (if done reasonably) Has no drastic effect on your device! For the past 2 years I have been using a small yet simple app called performance. With the app, you can overclock your device up to 624mhz (for those with lesser performance) or underclock your higher powered device to save battery life!
All you have to do is unzip the file save it the memory card, then copy it to your device root menu (NOT WINDOWS ROOT), run the app, enable the software, and there you go, simple and easy!
I'm not going to take any credit for this app, because it isn't mine! There is no mention of anyone who created this app. But, if you are out there, let me know!
If any one has any other questions, drop me a line!
dude, for what CPU is it made...
Has no drastic effect on your device!
Click to expand...
Click to collapse
well, oc should have drastic effect..
--
ehhh.. doesn't work on pxa270 cpu. it looks just as uni oc-er, if i remember right.
it is not working at all(cpu clock is NOT changing, as i supposed.
---
also, it is hard to imagine 620 mhz omap, lol.
I'm talking in the negative sense! It doesn't hurt the phone! As I mentioned, I have been using it for 2years now and I have not had any issues!
This app is good for ARM and OMAP processors!
nothin said:
dude, for what CPU is it made...
well, oc should have drastic effect..
--
ehhh.. doesn't work on pxa270 cpu. it looks just as uni oc-er, if i remember right.
it is not working at all(cpu clock is NOT changing, as i supposed.
---
also, it is hard to imagine 620 mhz omap, lol.
Click to expand...
Click to collapse
Ok, I apologize, the oc'er is best utilized with HTC devices. I did my further research and found out! Sorry for the misleading info! However, I am pretty sure there are other oc'ers out there that will SAFELY oc your device! As, I mentioned, I have been doing for the 2 years!
For those who are uncertain check out this thread. Yes, I started it, but the feed back speaks for itself!
http://forum.ppcgeeks.com/showthread.php?p=699069#post699069
Im new to the HTC scene, and have recently just purchased a Touch Pro...
Will this over clockin app work with this model HTC?
Cheers
i've used battery status to determinate if there is an effective increase of performance in my polaris ; the clock speed is still 400mhz
edit:
doesn't work with htc cruise. tested with sbp benckmark
I have tested this app, on a Touch Vogue, PPC6700 and a Touch Diamond, and noticed a difference with all three, one more than the other and vise-versa! Its small enough to take no room on your device and its an .exe file, so, nothing is created on your devices root or anywhere else!
does this work for newer devices like dhd?
pashkustva said:
does this work for newer devices like dhd?
Click to expand...
Click to collapse
Dude, this thread is almost a year old.
Try:
Oc/uv beater-dhd forums, not supported anymore but still works.
Systune-market
Nofrills-market
Possibly voltage control-market
If you use CM OC ability it's built into settings.
SetCPU-market
bclark said:
Dude, this thread is almost a year old.
Try:
Oc/uv beater-dhd forums, not supported anymore but still works.
Systune-market
Nofrills-market
Possibly voltage control-market
If you use CM OC ability it's built into settings.
SetCPU-market
Click to expand...
Click to collapse
+1 on the oc/uv beater. Really nice
Sent from my Mikrunny'd Vivo_w
Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]
Thus far I think we've only overclocked the main CPU, haven't touched the GPU. Looks promising tho.
ohhhhhhhh my god its really ?? i cant belief !! its co0o0o0o0o0o0ol
Jandyman said:
Hi im running xdandroid on my rhod210 and i am very happy with it, one of the few annoying downsides to it is the ****ty fps of 17.5 which is quite choppy for most 3d games.
But iv heard that gpu overclock for rhodium is definatly possible with the right line added to startup.txt.
look at this thread:http://forum.xda-developers.com/showthread.php?t=697673
it says about overclocking the vogue with a line in startup.txt, with it the vogue achieved 36.5fps!!! which is brilliant, and the vogue is inferior to the tp2 harware wise.
So we know its possible and will give us great improvement, so all we need is someone with the know how to tell us how? it was sais that we would "need to talk to your kernel devs to add this functionality" so hopefully this will be a great update.
any comments, anyone willing to help? anyone working on the xdandroid project willing to implement this? it would be much appreciated.
tank you, please reply :]
Click to expand...
Click to collapse
this would be awesome, would definitely raise its quadrant score
I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.
I'm not sure what is Vogue and what screen resolution it has, but I supppose as it's old phone with Qvga. Qvga means 1/4 of the pushing pixels that we have on screen. So if Rhodium had qvga screen we would have 4 times beter frame rate. 69 FPS. I wouldn't call 17,5 fps of WVGA 3D ****ty in phone that was presented almost 2 years ago with different operating system. And we should remember that it's Android, which isn't (for now) fully working.
Click to expand...
Click to collapse
your right the htc vogue has a qvga screen, but it also has less processing power so this should somewhat balence things out. But i still think gpu overclocking would greatly improve the rhodiums performance and if i remember right neoseekers version of android recorded 24.1 fps, and that is without gpu overclock. so improvement is more than possible.
ohhhhhh god 24.1 fbs its brilliant beside 17.5 to the htc rhodium its co0o0o0o0ol
I tried the startup option they were talking about in the thread referenced... if the value is too low then maybe that is the issue, or it just doesn't work. Either way got 17.6fps on neocore before and AFTER changing the startup.txt and rebooting. Unless a dev wants to chime in I don't think that is the only step to overclocking.
Well those startup options are in the kernel. So we'd have to get the kernel enabled before we can ever dream of having the startup option work
Basically any option that's set in cmdline is being passed to the kernel - so if our kernel isn't enabled for that feature/option, it'll just get ignored.
arrgghh beat me to it
i dont kno how hard or easy it is to change the kernal to allow this but hopefully the devs will hear and implement this feature. Or if someone could contact them suggesting it would be great.
its actually simple to over-clock, but does anyone know what values to overclock to before burning up the phone?
If you guys want this done, id look for an existing winmo solution to do this on windows. Once we know what values to use on the clock regs, we can easily port it over on android.
a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.
Jandyman said:
a quick google search of 'overclocking gpu on htc touch pro 2' has lead me to nothing :/ im presuming this is because there is no need to overclock the gpu when running windows mobile because there are very few decent windows mobile games (as far as i kno) and havnt found any using 3d, specially not free.
But if we find the detailed specs of the touch pro 2, and then search for the safe frequesncy to overclock that power of gpu too wouldnt it be the same? thats probly our best bet unless someone can find evidence of overclocking gpu on a tp2 running windows mobile.
Click to expand...
Click to collapse
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
There are also other clocks involved with the display. mddi, mdp are other clocks that can also change. Vogue for example has the ability to over clock mddi.
But yea.. a winmo app would be very helpful.
[ACL] said:
Nahh.. don't work that way. Its not like 1 clock you can change to any frequency. All the clocks are derived from the plls and you would need to do some math to determine what pll to use and what to devide it by.
Click to expand...
Click to collapse
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.
Hamsteriel said:
For those who are still unawares at this point, PLLs are crystals on the mainboard that resonate at different frequencies. Thus you would need to tear open the phone and figure out which PLLs are linked to the GPU and which are just ancillary, and then be able to put it back together. Whomever wants to take this upon themselves, I wish them luck.
Click to expand...
Click to collapse
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Yay, I can haz FPS?
[ACL] said:
Not entirely tru. We know which pll the gpu uses and what its currently dived by. We had this discussion today on the irc board. There is some work being done to help improve the speed.
Click to expand...
Click to collapse
Just curious if this work on GPU overclocking ever got anywhere or was determined to be possible in the future?
it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay
randomblame said:
it's possible - but more than likely it would cause severe problems with battery life and stability. Considering the dismal state of our battery life already I doubt the work is worth it for an extra 4fps in angry birds.
Thread necromancy is bad mkay
Click to expand...
Click to collapse
If you're up to date on kernels, especially if you're on Wistilt's test branch, battery life is great. When sleeping, battery life is measured in days now. Anyway, just because the compromises involved don't interest you doesn't mean they wouldn't work for someone else.
Alternatively to overclocking the GPU, I wonder what sort of UI smoothness/framerates would be possible if the display driver were recoded to pixel double to our screen from 400x240 (same resolution as a Samsung Intercept).
I played around with the lcd density but that didn't seem to be able to create the same effect, as program's like Neocore still knew that my display was actually 800x480 and displayed as such.
Hello!
I-m trying to apply several live wallpapers. Some crash, its acceptable.
Others, plain buggy. Example: Galatic Core.
I select it in the Livewallpapers selector, it does not error, and shows a black screen. i press settings, get the message "buy the app", and then it shows!
If i then select it, i get a black screen... and then the original wallpaper again.
Anyone got more luck than i ?
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
thoughtlesskyle said:
They were never meant to run on our phones so they will be iffy at best for performance
Also if your using cm6 that's a known issue across the board with them
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Could you guys please stop doing that ?
"" XPTO was not meant to run on our phone ""
What is it there... that our phones have... or have not... that make a given app not run ? Sure... we can agree on "it wasn't designed for 320x240. Ok, i agree too.
But either than that ?? Yeah, our CPU is the slower MSM on the field, at least compared to Diamonds/Raphaels and upwards... but hey!! We have 1/4 of the pixels to take care of. That sould give us some room...
Now, don't get me wrong. It was not designed to run Android. But that doesn't mean it was not meant to. Take for example a simple little phone, sold here on Portugal as Optimus Boston. It has a MSM cpu... it came with 1.6 running at 600mhz... but the latest update to Eclair 2.1... underclocked it to 480. My kaiser usually runs at 550. (official rom, its possible to have custom roms running at the original 600.) and it still is a great phone... look at the simple specs :
http://www.gsmarena.com/gigabyte_gsmart_g1305_boston-3201.php
Now, someone explain... why can't our Kaiser/Vogue/Polaris run Android like that leatle freak underclocked to 480 runs. Please.
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
thoughtlesskyle said:
The fact that we have absolutely no RAM doesn't play into it ever since sheer clock speed always determines speed, to be honest I haven't even seen them run well on my hero and I have it OC'd to 691
But hey if you want to argue about it there are links to the source around go in and fix the problem, most of the devs for this project have more important things to focus on at the moment
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Do not feel ofended. It was not my intention.
My point is that if we had accepted the slowness of our devices, we would never had attempted to port Android.
As for the RAM, agree.. it is a bottleneck...
Now, has for speed... i've seen them run well... on other devices of course.
I did many tests on my Kais130 Fresh Froyo, about livewallpapers
I agree with Daedric on the ability of our device.
I managed to run the "Grass" Wallpaper properly. Others, like Mario, Galactic Core, ... Sometimes with bugs and/or too many resources used.
It seems to me that LiveWallpapers work less well in the latest Froyo
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
aceoyame said:
Well were not the slowest android phone anymore. But that doesnt mean much, we still have a lot of instability. The ram limitation can be overcome with comp cache (virtual memory) but that brings only more instability and adds overhead that we don't need. Also the performance just isnt there yet. Our phones beat only one phone and thats because that phone doesnt have froyo on it. Otherwise it would beat ours out. Also that was with my kaiser overclocked to 572 mhz with a gpu overclock as well. Any other phone msm 7200 phone at those speeds kick our kaisers ass. I think the resource intense ones are just not meant to work well at all for us. My background works at least lol, I use a background that shows the core of a 486 cpu.
Click to expand...
Click to collapse
Should we assume... that at the same speed, diferent MSM devices offer diferent performance ? Or, are we simply doing still things wrong, i don't know, perhaps a poor schedule, buggy drivers which introduce lag, perhaps the graphic one.
We must remember, they kick our kaiser hard, but they have much more pixels, how can that be ?