[q] Livewallpapers - Tilt, TyTN II, MDA Vario III Android Development

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 ?

Related

HTC overclocking

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

[Q] Mid-Range? Whatever...

http://androidandme.com/2010/06/new...s-all-other-android-phones-in-gpu-benchmarks/
I found this to be interesting and a bit odd that we have all of this talk about the "Mid-Range" Cpu at 600 Mhz but no talk about the GPU. Does anyone have some information on the GPU and if they are receiving similar scores in this category?
Can we officially stop calling this a "Mid-Range" phone if this turns out to be true?
Remember the phone is only 320x480 res vs the N1, Droids, etc 480x800+. That alone will greatly improve the performance (if same GPU).
IMO a Large res display is required for a high end phone too.. though a good one its still a mid level.
Please post this is the correct section.
mesajoejoe said:
Please post this is the correct section.
Click to expand...
Click to collapse
This question is very relivant to the development of this device.
This all goes back to my mantra, lastest dont always mean the greatest. Hell, put it in this perspective...any woman would sacrifice an inch for better performance. I would much rather something do what its supposed to do and do it with blazing colors, than have something look pretty with all the bells and whistles and hiccup in comparison. Ive played with all the android phones from tmobile thus far, and the slide is by far my fav.
My reasoning behind throwing this in the development section was to hopefully find someone who could shed some more light on the GPU in this phone. I am sure that the pixel differences between this device and others are part of it but it seems as if more is going on in the background with this phone. Here are some questions this benchmark test brings up for discussion:
1.Is this GPU Open GL ES 2.0 capable?
2.Has Qualcomm opened up more possibilities with this GPU drivers compared to other phones?
3.It seems that this is an Adreno GPU, but which one? The Nexus has an Adreno also.
4.How much of this phone is hardware accelerated compared to other phones? I remember taking up the RAM from my G1's GPU to help run the main components of the phone, maybe this phone has a bit more help built in to it.
Let's all run to tmo and drop one so we can see what's inside! I for one just compaired it to the mt1.2 and it blows it away! The wife loaded up her baseball flash site and flipped at how fast it rendered the stuff. The screen res ain't got nothing to do with that. Maybe they fibbed on the cpu info so we wouldn't know. Or they got themselves one smart dev for software building.
Has anyone tried linpack tests yet?
mejorguille said:
Has anyone tried linpack tests yet?
Click to expand...
Click to collapse
Linpack is 2.6+ for the one i tested at the store.I think the CPU is honestly down-clocked from what it really is, for all we know it could go up to 800Mhz or 1GHz. When linpack ran there were some b/g apps open.
Re: Mid-Range? Whatever...
If you look at the power.xml in github for Wes Garners's developments on this phone you will see the option for 998mhz as the high end for this cpu. I'd imagine overclocking it will bring at least 1.3 to the table. No info on the GPU yet.
Sent from MTS using Tapatalk
Re: Mid-Range? Whatever...
mejorguille said:
Has anyone tried linpack tests yet?
Click to expand...
Click to collapse
Yes. Mflops came out around 2.2. It needs to be tweaked severely but id assume this is due to the bloated processes and underclocking of the CPU.
Sent from MTS using Tapatalk
i dont understand why everyone is hating on this phone, my g1 is perfect. does what i need from android. and i like it over all. i never have problems with my processor. so this phone is a huge plus to me. although id love to make the sence ui on it a lil differnt, like the normal sence
mtjnkee said:
Yes. Mflops came out around 2.2. It needs to be tweaked severely but id assume this is due to the bloated processes and underclocking of the CPU.
Click to expand...
Click to collapse
Really? That's very low in my opinion when a droid, also running a 600 Mhz get much higher, and my rooted g1 with cyan kernel 2.6.34 get 2.3-2.4 on linpack.
Wikipedia says that the mytouch slide has a MSM7227 processor compared with Snapdragons which are QSD8xxx series. Some google searches found that the 7227 is for "cheap", sub $150 smartphones. Here are the specs for the processor:
Code:
The platform -- known as the MSM7227 -- is apparently designed with higher-power,
lower-cost handsets in mind, offering HSDPA / HSUPA radios, a 600MHz CPU, 320MHz
application DSP, 400MHz modem processor, hardware-accelerated 3D graphics, Bluetooth 2.1,
and GPS support integrated in a 12mm x 12mm chipset. The MSM7227 can also supposedly handle
8 megapixel camera and 30 FPS WVGA encoding / decoding with ease, and is capable of
supporting Android.
1
2
mejorguille said:
Really? That's very low in my opinion when a droid, also running a 600 Mhz get much higher, and my rooted g1 with cyan kernel 2.6.34 get 2.3-2.4 on linpack.
Wikipedia says that the mytouch slide has a MSM7227 processor compared with Snapdragons which are QSD8xxx series. Some google searches found that the 7227 is for "cheap", sub $150 smartphones. Here are the specs for the processor:
Code:
The platform -- known as the MSM7227 -- is apparently designed with higher-power,
lower-cost handsets in mind, offering HSDPA / HSUPA radios, a 600MHz CPU, 320MHz
application DSP, 400MHz modem processor, hardware-accelerated 3D graphics, Bluetooth 2.1,
and GPS support integrated in a 12mm x 12mm chipset. The MSM7227 can also supposedly handle
8 megapixel camera and 30 FPS WVGA encoding / decoding with ease, and is capable of
supporting Android.
1
2
Click to expand...
Click to collapse
Well thats because the droid has a better processor (not speed but type) and the G1 is rooted and all the bloatware cut plus probably jit enabled plus swap/comcache. Besides that score seems rather low. I have a G1 and the MTS is way faster. I dont need a benchmark test to tell me that. Its definately as fast as my friends droid may be faster.
I know its been said before but it has the same gpu as the n1 for me that makes it all the proccessor i need
http://forum.xda-developers.com/showthread.php?p=5719829
neva dinova said:
I know its been said before but it has the same gpu as the n1 for me that makes it all the proccessor i need
http://forum.xda-developers.com/showthread.php?p=5719829
Click to expand...
Click to collapse
awesome
Z51 said:
awesome
Click to expand...
Click to collapse
either way, its better than the g1 and mt3g and even the 32a mt3g's.. when it gets rooted, this device will fly even moreso than it already does. bloatware be damned, we'll have it working wonders and fixing aids!*
aids may not actually be fixed by rooted slide
I know right. This morning I was looking at the running apps and saw the following that ran even if you cleanly booted it up:
* Visual Voicemail (don't get many VMs, so it's useless to me)
* Faves (useless)
* Swype (useless to me)
* IM (why is this even running?)
* AppPack (useless)
* My Account (useless)
Each of these apps take 20 MB or more.
marvinp said:
I know right. This morning I was looking at the running apps and saw the following that ran even if you cleanly booted it up:
* Visual Voicemail (don't get many VMs, so it's useless to me)
* Faves (useless)
* Swype (useless to me)
* IM (why is this even running?)
* AppPack (useless)
* My Account (useless)
Each of these apps take 20 MB or more.
Click to expand...
Click to collapse
with a clean rom, we're gonna have so much extra space we'll have no need for a2sd

GPU overclocking

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.

[Q] Kaiser 3D Drivers For Android - SOLVED - CAN BE CLOSED

I was wondering, the 3D performance is a lot better on the kaiser when using the video drivers (of course).
But is there any way to get the 3D driver to work in android?
Since i don't think it's possible to just install the driver on WM and then run Android because it fully shuts down WM i was wondering wether there's a way to get that nice smooth performance on Android as well.
Or is there any app that makes the kaiser a bit faster (graphics wise)?
Thanks a lot!!!
Answer:
3D Drivers are implemented (if that's the correct word (I'm from Belgium so)) in Android.
syntax1993 said:
I was wondering, the 3D performance is a lot better on the kaiser when using the video drivers (of course).
But is there any way to get the 3D driver to work in android?
Since i don't think it's possible to just install the driver on WM and then run Android because it fully shuts down WM i was wondering wether there's a way to get that nice smooth performance on Android as well.
Or is there any app that makes the kaiser a bit faster (graphics wise)?
Thanks a lot!!!
Click to expand...
Click to collapse
Aren't they allready implemented using opengl????
If your running android you already have the drivers, they are in the kernel. I think we need to make a big sticky of that somewhere, third time ive seen it asked this week.
aceoyame said:
If your running android you already have the drivers, they are in the kernel. I think we need to make a big sticky of that somewhere, third time ive seen it asked this week.
Click to expand...
Click to collapse
I second that
syntax1993 said:
Or is there any app that makes the kaiser a bit faster (graphics wise)?
Thanks a lot!!!
Click to expand...
Click to collapse
As has already been said, HW3d is implemented into the kernel which utilises the qcom chip in our kaiser's, but the hardware graphics acceleration although better then nothing is pretty crap compared to the new phones coming along so you can't expect miracles, just be glad it has any at all and android can actually use it unlike window mobile!
scooter1556 said:
As has already been said, HW3d is implemented into the kernel which utilises the qcom chip in our kaiser's, but the hardware graphics acceleration although better then nothing is pretty crap compared to the new phones coming along so you can't expect miracles, just be glad it has any at all and android can actually use it unlike window mobile!
Click to expand...
Click to collapse
I would not call 32 frames per second in NEOCORE, with your build, prertty crap.
Well, can not be compared to new phones, but you must admit that this is more than enough to run 3D games(we can play RagingTunder2!).
Millence said:
I would not call 32 frames per second in NEOCORE, with your build, prertty crap.
Well, can not be compared to new phones, but you must admit that this is more than enough to run 3D games(we can play RagingTunder2!).
Click to expand...
Click to collapse
No, it is quite impressive for an old timer, but obviously it can't keep up with the new hardware on the market and therefore the applications/games that are targeted at these devices. It's also a shame it isn't man enough for new video codecs although installing arcMedia which uses FFMpeg as it's backend improves things a little and gives support for more formats.
Thank you for answering, i had no idea it was integrated into the kernel.
I've heard that the kaiser had a quite good video chip but that's probably compared to the other phones at that time .
Well my phone is running Quake2 at about 10FPS (a bit higher (about 15-20) when looking into corners etc.) and i was hoping for a bit higher rate but it seems it isn't very easy to gain that on android.
Thanks a lot again for this quick answer, i haven't found any post on the forum wich answered my question so...
Syntax1993
Haven't looked well enough then it seems.
I'm sorry.
awhile back I looked at the performance of our integrated 3d and it is about on par with a rage 128 from what I remember... which is pretty bad lol not to mention that on android we have to run through java and we have a pretty weak fpu. I mean in linpack with my barebones rls 3 and overclocked to 572 mhz I get 3.8 mflop/s which is pretty bad lol. That was with JIT working properly even.
aceoyame said:
awhile back I looked at the performance of our integrated 3d and it is about on par with a rage 128 from what I remember... which is pretty bad lol not to mention that on android we have to run through java and we have a pretty weak fpu. I mean in linpack with my barebones rls 3 and overclocked to 572 mhz I get 3.8 mflop/s which is pretty bad lol. That was with JIT working properly even.
Click to expand...
Click to collapse
Have u had any problems clocking that high? I'm a bit scared to clock higher than 450Mhz because i don't want to brick my phone tbh.
Would be cool to clock that high.
*Afraid to clock that high LOL*
syntax1993 said:
Have u had any problems clocking that high? I'm a bit scared to clock higher than 450Mhz because i don't want to brick my phone tbh.
Would be cool to clock that high.
*Afraid to clock that high LOL*
Click to expand...
Click to collapse
And there's the batt consumption issue... even if it can be reached ull need a really really long lasting extended batt, I got a Seidio Inocell 1600mAh, in a donut with .25 kernel and oced to 470, my batt last me like 10-12 hours if I use moderate wifi, bt or gps and keeping my data to 2g only.... If I try to keep my wifi or gps turned on all time and use 3g probably it wouldnt last more than 4-6 hours.
albertorodast2007 said:
And there's the batt consumption issue... even if it can be reached ull need a really really long lasting extended batt, I got a Seidio Inocell 1600mAh, in a donut with .25 kernel and oced to 470, my batt last me like 10-12 hours if I use moderate wifi, bt or gps and keeping my data to 2g only.... If I try to keep my wifi or gps turned on all time and use 3g probably it wouldnt last more than 4-6 hours.
Click to expand...
Click to collapse
Well since the data here costs a lot of money (i don't know what it's like where you live) i rarely use it.
GPS is off and wifi is only on when at home or for a short period of time.
BT is also rarely used and off when not used.
I'm using a 2880Mah battery so the clocking won't be that much of a problem and i can recharge it every night so.
Aren't there high costs for 2G and 3G? it's waay to expensive to have it turned on all day.
Would i get any problems when clocking to around 500Mhz or smthng like that?
syntax1993 said:
Well since the data here costs a lot of money (i don't know what it's like where you live) i rarely use it.
GPS is off and wifi is only on when at home or for a short period of time.
BT is also rarely used and off when not used.
I'm using a 2880Mah battery so the clocking won't be that much of a problem and i can recharge it every night so.
Aren't there high costs for 2G and 3G? it's waay to expensive to have it turned on all day.
Would i get any problems when clocking to around 500Mhz or smthng like that?
Click to expand...
Click to collapse
If ur using a data plan its relatively cheaper... i've oced my lil htc tilt to 520mhz, specialy when trying heavy apps and never had an issue (well never had issues more than the normal ones LOL ) you'll feel it gets a bit "warm" in the backside (maybe due to the higher batt consumption) and speed increase isnt that much beyond a certain point but maybe ull be luckier than me! (this is something common in evert oc! my cousin and i both have an evga gtx 275 i can get ir run almost 100 mhz higher than stock and if my cousin even tries to touch the values his pc hangs up!!) Taking abuot that... The only thing i've never tried was to oc the gpu (i've seen that option in atools) dunno if its doable in our kaisers and if there's a real increase/decrease in performance... if you give it a try maybe you could publish ur results...
albertorodast2007 said:
If ur using a data plan its relatively cheaper... i've oced my lil htc tilt to 520mhz, specialy when trying heavy apps and never had an issue (well never had issues more than the normal ones LOL ) you'll feel it gets a bit "warm" in the backside (maybe due to the higher batt consumption) and speed increase isnt that much beyond a certain point but maybe ull be luckier than me! (this is something common in evert oc! my cousin and i both have an evga gtx 275 i can get ir run almost 100 mhz higher than stock and if my cousin even tries to touch the values his pc hangs up!!) Taking abuot that... The only thing i've never tried was to oc the gpu (i've seen that option in atools) dunno if its doable in our kaisers and if there's a real increase/decrease in performance... if you give it a try maybe you could publish ur results...
Click to expand...
Click to collapse
I'll try clocking CPU to about 500Mhz or a bit more
Going to use it tomorrow because it's about 9pm ATM.
GPU would be nice if it was possible to overclock it.
I'll post it tomorrow, could be that i can't see any result compared to a lower frequency.
Thx for ur help btw!
I've noticed a small diffrence when trying quake2 atm.
The diffrence isn't very great but i will try clocking it a bit higher tomorrow
Yooooo
As i've said before many times there is no risk in overclocking past 528 because we are not touching the voltage going to the cpu when we are overclocking it, just the crystal that controls the frequency it is running at. There is a slight heat increase and loss of battery consequentially because of that extra heat but that is it. I am speaking from experience overclocking a 2.4 ghz celeron E2200 to 4.25 ghz on air cooling with no disatrous results and used it as such every day. Basically I overclocked it with a pinmod for voltage and FSB increases and then I overclocked it further with the motherboard and supplied even more voltage. For the heatsink I used an OEM socket 775 heatsink and had no problems at all, it typically ran about 48 Celsius. If an overclock that high and potentially harmful won't kill the cpu then certainly one of a much smaller % is not going to harm a little kaiser.
FYI I took the voltage on that Celeron to 1.7 volts to get it that high. Stock is 1.1 if I recall
aceoyame said:
As i've said before many times there is no risk in overclocking past 528 because we are not touching the voltage going to the cpu when we are overclocking it, just the crystal that controls the frequency it is running at. There is a slight heat increase and loss of battery consequentially because of that extra heat but that is it. I am speaking from experience overclocking a 2.4 ghz celeron E2200 to 4.25 ghz on air cooling with no disatrous results and used it as such every day. Basically I overclocked it with a pinmod for voltage and FSB increases and then I overclocked it further with the motherboard and supplied even more voltage. For the heatsink I used an OEM socket 775 heatsink and had no problems at all, it typically ran about 48 Celsius. If an overclock that high and potentially harmful won't kill the cpu then certainly one of a much smaller % is not going to harm a little kaiser.
FYI I took the voltage on that Celeron to 1.7 volts to get it that high. Stock is 1.1 if I recall
Click to expand...
Click to collapse
Awsome I could only reach 2.9 gigs on a intel q9400 on an asrock g31m-s (its a really crappy n cheap mobo!) The q9400 runs stock @ 2.66 maybe u can help me with that too lol!! Kiddin...
Sent from my HTC Kaiser using XDA App
albertorodast2007 said:
Awsome I could only reach 2.9 gigs on a intel q9400 on an asrock g31m-s (its a really crappy n cheap mobo!) The q9400 runs stock @ 2.66 maybe u can help me with that too lol!! Kiddin...
Sent from my HTC Kaiser using XDA App
Click to expand...
Click to collapse
See BSEL pin mod for socket 775 as it isnt a gigabyte board that should send your OC soaring through the roof since it doesnt use CPUID for configuring its clock speed on boot.
Millence said:
I would not call 32 frames per second in NEOCORE, with your build, prertty crap.
Well, can not be compared to new phones, but you must admit that this is more than enough to run 3D games(we can play RagingTunder2!).
Click to expand...
Click to collapse
Just tried Raging Thunder 2. Wow - I had no idea games like this could run well on our old machines - except without an accelerometer I can't see how to steer and accelerate at the same time .
Are there any other nice looking action/racing gaems out there that give decent frame rates?

[Q] Highest stable overclock on Touch Pro 2?

Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Depends on the device. Most seem to max out at 748,800khz, one guy claimed he hit 820mhz or smth outrageous.
Honestly the best way to establish what your device can handle is to push the OC in WinMo until it's not stable any longer. That should be a good indicator of how far you can push Android.
Honestly I found OCing Android to be way more trouble than it's worth - the phone seemed to lag even more, and it definitely made the device less stable. I'm not a big fan of overclocking my computer either, so I am a little biased.
Cool. Thanks arrrghh. I reprogrammed a USSC TP2 to use with PagePlus for my daughter and put Android on it for her. Just wanted to try and push it to its limits I guess and see what it would do. What class/size/brand card do you suggest I use? Right now it is using a Sandisk class 6 8 gig card, but I've heard some have gotten better performance from class 2 cards.
I'd start at around 600mhz and keep pushing it up 20mhz at a time. The clock driver only takes it in steps of 19.2mhz, but is smart enough to divide it correctly via mod. At 640 or so the bottom started to get noticeably warm, and I've set it at 660 right now.
Each device is different, some take overclocks easily than others.
-- Starfox
Thanks for the help guys, I'll keep tinkering with it.
I've a RHOD100 and have acpuclock.oc_freq_khz=692000 on FRX07 and all is well and does not seem to even get any way warm underneath.
Mind you, while I've set this, is there any way to check within Android as to what speed my TP2 thinks it's actually running at (in case it is ignoring the setting in the setup file) ?
However, it is possible that the speed may work differently with differing builds of the various components but maybe someone more knowledgable on here could confirm whether or not this is the case.
C
Hi,
i use the tool "CPU Master Free" to see the actually clock speed (i hope it shows the right values).
At this time its oc at 633,6 Mhz an no problems.
sebastian
Perfect - it says I'm running at 691.2Mhz
C
reocej said:
Anyone care to tell me what the highest stable overclock they have achieved on the Rhodium/Touch Pro 2 with Android?
Click to expand...
Click to collapse
Got my Tilt2 (most recent kernel + rootfs) maxed out at 768.000MHz, and I noticed smoother scrolling and window animations.
But for me, I noticed that the phone actually freezes at times.. even when the phone wasn't overclocked. I believe that's just bugs in the kernel, though, soo not much to do about that from my experience, OC performance relies heavily on the device and kernel version (if that wasn't obvious lol).
EDIT: Ehh, I've read that anywhere from 600-640MHz is the most stable. Currently I'm at 595.2MHz and am noticing an improvement in stability over 768MHz.. Hope this helps.

Categories

Resources