Hi, is possible?someone has done?Bye
Try these
OmapClockPlus v0.0.4 - OmapClock Helper
OmapClock v2.0
Sethide said:
OmapClockPlus v0.0.4 - OmapClock Helper
OmapClock v2.0
Click to expand...
Click to collapse
There are to Omap processors,I don`t think it works in P3600/P3600i our device is samsung processors
http://forum.xda-developers.com/showthread.php?t=391957&highlight=overclock
http://forum.xda-developers.com/showthread.php?t=350635&highlight=overclock
http://forum.xda-developers.com/showthread.php?t=324781&highlight=overclock
Uhm, i have to add my experience with the Wizard....i used to overclock the OMAP processor, and after a while i got serious instabilities of the lcd screen and spontaneous reboots even going back to nominal speed. In short, my Wizard went out of use. I know that the samsung processor is less good at it - therefore i decided not to try it...my individual experience, for what is worth...
Related
Did this work with my TyTN II?
I have installed it but I only see X icon which makes soft reset.
And if this not work... what sw do the same... dynamic clocking?
Pasi
Hi PeeHoo,
Nope, the overclocking would not work as it is processor specific, not written for Kaiser. It has been mentioned in other threads..
And... any other possibilities to do this?
why would you want to overclock it? It is already pretty fast...
well, I'd like to have a similar tool, too. Not to overclock, but setting the CPUs freqency to less than 400 MHz if not used.
I did that with my wizard using batterystatus (130-240MHz) and saved lots of energy
Nothing out there that is compatable with our CPU that I know of.
I have seen cooked ROMs with Battery Status installed, but no OMAP or equivalent, is there anything out there that works, I needs more speed
then go with android i recomment myns doughnut builds
great news that seems awesome
http://www.htcclassaction.org/driverprogress.php#update_20080717_1 (MOD EDIT: LINK CORRECTED)
""Now we have all that out of the way, here is the actual CAB file(http://www.htcclassaction.org/download/HTC-CA-Kaiser-Drivers.cab ) . Just install it on your device. Here is a RAR file (http://www.htcclassaction.org/download/Lights.rar) containing a sample D3D application - indeed the same as shown in the video - you can use to see if the drivers worked! Unrar it on your PC, copy the EXE files to your device, and run it on your device. It will show a few popups telling you if hardware is used or not.""
""These drivers require a Kaiser (TyTN II) and a ROM based on the official HTC WM 6.1 update!. Exactly which ROMs are compatible is not yet known. We have tested this on multiple Kaisers, but all of them were running Dutty's Diamond V1 ROM. It is extremely unlikely that these files will work out-of-the-box on any other MSM7x00 based device (at this time).""
i'm just flashing and check this out
They work on Garmin 1.2. Bigggg difference running the Lights program
Just thought i'd add the rest of the info:
"OK folks, here it is! A few hours later than projected, but still: OpenGL ES and D3D drivers (non-fullscreen) for the kaiser!"
"Before continuing, we would like to stress yet again, because there seems to be a little confusion here and there: these drivers are not finished, this is a work-in-progress. This is not a fix-all solution!. Currently the only things that are supported are hardware-accelerated D3D and OpenGL ES. These drivers are merely a release you can 'play' with, and prove it can be done. How many real-world applications will work with it remains to be seen, and we expect the users in the community will gather a list of these rather quickly."
"To elaborate further, these drivers do not accelerate video playback. These drivers do not accelerate normal Windows operation. Some of you have asked if we have abandoned accelerated 2D. We have not, it may still come. The simple fact is, that in this particular case, it was easier to work with the 3D drivers first"
yes but is a big big start
now we can keep hopping for better days with our kaisers
FINALLY!
I hope we get 2D acceleration as well. 3d is great, but 2D is better for me since I'm using office apps on my kaiser the majority of the time.
Ahh so it wasn't HTC who released these drivers like I originally thought. My original F**k you to HTC still stands.
Props to the person(s) who spent many hours getting this working.
Nice to see some actual progress, honestly I had pretty much given up hope. HTC isn't putting these out though, so don't thank their sorry asses.
Link in post 1 didnt work for me, the one below should lead to the page on the classaction site
http://www.htcclassaction.org/driverprogress.php#update_20080717_1
rcm_rx7 said:
Nice to see some actual progress, honestly I had pretty much given up hope. HTC isn't putting these out though, so don't thank their sorry asses.
Click to expand...
Click to collapse
Agreed !!! HTC had nothing to do with this driver project, it was all done by an indiviudual wiz , thanks should go there,HTC's behavior in this driver drama has been little but nothing more then talk with empty words. But indeed I got some hope again
sheptard said:
I hope we get 2D acceleration as well. 3d is great, but 2D is better for me since I'm using office apps on my kaiser the majority of the time.
I hope HTC continues with the development of these drivers and doesn't just say 'well, you complained about 3d accel long enough, here's something resembling a driver' and leave it at that.
If someone from HTC is reading this, Thank you very much for finally getting these out the door, and please don't stop I think 2D accel would be a great christmas present
Click to expand...
Click to collapse
As said in previous post HTC let us down totaly on the driver issue, vague promises, but no delivery, then againm why make the Kaiser better if that may have negative sale impact on the new Daimond..
I can tell HTC one thing: the Kaiser was my last HTC, not because of the Kaiser, I still love it; but due to their attitude in this driver struggle.. They shown they have no regards whatsoever to the customer after they bought their product,
Well.... for me... as long as i got a better camera in my device.... i am happy... as it is the only thing i am unhappy with my device..
----------------
Now playing: Hitomi Harada - Eternal Feather
via FoxyTunes
can someone upload the cab so we that are on our kaisers can download!
austinsnyc said:
can someone upload the cab so we that are on our kaisers can download!
Click to expand...
Click to collapse
There you go
Link to the cab file
we need a sticky thread that people post what there results are with the beta drivers with different ROM's right now i tried on my rom that is in my sig (april 29 dutty's), and i had no go, i dont know if before directdraw worked in video tests, but i benchmarked a video and it worked very slow though 39% vs 80-95% in raw and other setttings
also for those who can benchmark it would be nice to see which ROM gives the most performace and bug free?
also i would like to know if its possible to do reg hack/import of the paths that diamond based roms have, to those that were pre diamond based or even pre full 6.1 roms?
im not 100% sure but remember that those new roms didnt have drivers but did have paths/links to what could be drivers, with a simple cab older ROM's could work with the driver as well?
I'm sorry to interupt but this driver is not finished & doesnt make any change to kaiser graphic performance. i think there was an old thread similar with this that has been closed long time ago. dont get mad. i already say sorry
hang.tuah said:
I'm sorry to interupt but this driver is not finished & doesnt make any change to kaiser graphic performance. i think there was an old thread similar with this that has been closed long time ago. dont get mad. i already say sorry
Click to expand...
Click to collapse
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
skatdawg said:
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
Click to expand...
Click to collapse
OIC. thanks skat. so the conclusion we still have to wait or just buy Raphael
skatdawg said:
That's not entirely true, it doesn't make any changes to the kaiser's 2D graphic performance, but that is because it's 3D graphics drivers. The video demonstrates that there is 3G acceleration being enabled by these drivers, though it still won't fix what ails the kaiser...but it's a step in the right direction.
Click to expand...
Click to collapse
I agree, When I first tested the light.exe bench, It was laagy and hardware was not detected, now it rocks
Glbenchmark is still not working but I think there is hope for 3D games and may be touchflo 3D
confirmed
1. run lights.exe with no drivers
- driver provider: Microsoft
- hardware rasterization: false
- hardware T&L: false
- using system memory
- around 1 fps
2. installed drivers, soft reste
3. run lights.exe again
- driver provider: n/a
- hardware rasterization: true
- hardware T&L: true
- using video memory
- around 15 fps
one bug - could be driver could be lights.exe could be rom (L26_KDV9): leaving lights.exe runing until the screen turns off freezes your device. I didn't test w/o the driver.
dani31 said:
1. run lights.exe with no drivers
- driver provider: Microsoft
- hardware rasterization: false
- hardware T&L: false
- using system memory
- around 1 fps
2. installed drivers, soft reste
3. run lights.exe again
- driver provider: n/a
- hardware rasterization: true
- hardware T&L: true
- using video memory
- around 15 fps
one bug - could be driver could be lights.exe could be rom (L26_KDV9): leaving lights.exe runing until the screen turns off freezes your device. I didn't test w/o the driver.
Click to expand...
Click to collapse
u r right. just tried it. wonderful app by Omikr0n. but is there any benefit for other apps if we using this driver? just curious whether this driver better cooked in or just as seperate cab.
Hallo, I finally dismissed my chicken outfit and flashed htc's wm6 rom onto my wm5 (the thrill !!).
With all today plugins off except for BatteryStatus (the latest beta), and the phone turned on, after a soft reset I get a paltry-ish 15M of program memory, changing magically to about 19M after a while (why ? dunno). Of course that then leaks slowly but surely and I'm sure we wouldn't want it any other way.
Is this the memory I'm supposed to get ?
Also, as a further term of assessment & comparison: the device is OC'ed to 260 via BatteryStatus, and I tried ThrottleLauncher on it (http://www.throttlelauncher.com/portal/index.php/pruebas/34-public-releases/76-092beta#tutorial). In spite of the OC, it seemed slow and clumsy.
Is it because
a) the herald's cpu is slow and there's no BS that can help it
b) throttlelauncher is aimed at faster devices or is still in development
c) stock wm6 is for some reason slower than say a custom rom under which throttlelauncher might work like a breeze
?
Thanks
stock wm6 is sooooooooooooo slow. if u want a clean stable rom, try open touch 5.2 org. that's what i use and u can manually disable the htc home plugin under settings>today and put everything back on to look like stock rom, but itll still be much faster than stock, and if u run bs, itll be smooth and quick
all of the above. period
I have in the past few days read maybe a hundred billion posts, and I am by now almost subliminally convinced that cooked roms are faster than stock, BUT
what is it exactly that makes the stock rom go slow ?
I mean, speaking of computers, short of replacing drivers for this or that feature, the pesky 200mhz cpu stays the same. On a desktop I may gain performance-wise if I turn off services, but I get no cookie for just deleting stuff from /Windows.
And how does the program memory really influence speed ?
(From the presumption that it looks more like "amount of stuff you can run at once" rather than "the more you have the smoother you go", at least to the untrained - mine - eye.)
the build of the custom roms is newer (therefore, better?) and there are less background processes running, which takes up the cpu. This is where the "more memory equals more performance" mantra comes from.
you can overclock, of course, and the stock rom usually comes with this HUGE pagepool thats just plain downright unneeded.
Download here:
SJ SamsungOmnia_Driver_D3D.zip
Instructions: Install SJ SamsungOmnia_Driver_D3D.cab and reboot!
I've extracted the driver from latest Samsung Omnia rom and tested it on my kaiser rom (HyperDragon III Full Version - 4 August) with dynamix 3d benchmark and some D3D test application from HTCClassAction.org (D3DMDemo.exe, Lights.exe, Text3D.exe) and it runs good and pretty fast! Have fun
Here's some D3D sample Application: SJ D3D Mobile Sample.zip
whats the differences with the drivers from HTCClassAction.org ?
Any 2D improvments ?
Who is the author?
thanks
sakajati said:
Download here:
SJ SamsungOmnia_Driver_D3D.zip
Instructions: Install SJ SamsungOmnia_Driver_D3D.cab and reboot!
I have tested the driver on my kaiser rom (HyperDragon III Full Version - 4 August) with dynamix 3d benchmark and some D3D test application from HTCClassAction.org (D3DMDemo.exe, Lights.exe, Text3D.exe) and it runs good and pretty fast! Have fun
Click to expand...
Click to collapse
Link doesnt work.
Im getting an invalid link for that file...
Looks like there's an error on xda server or my internet connection maybe.
It works now.
edit: mirror removed. (not needed anymore)
What exactly does this software do,i'm baffled.Can somebody please explain?
Got TCPMP 0.81 up to 204% with directdraw with my test video. Was 170-180% before... Seems there are some improvements
HTC CA apps seem also faster, but less smooth than before ?
Anyway thanks SJ for sharing this good finding
Interesting...I wonder if my phone will run it:
Does it work on WinMo 6.0?
(Running AT&T Stock rom without bloatware)
Is it un-installable (just in case)?
i tried the drivers and they work fine. even the 3d text test app from htcca is working ok now with the text displaying correctly. perhaps the 2d drivers from the omnia work, too?
will this work on older roms?
neva dinova said:
will this work on older roms?
Click to expand...
Click to collapse
I guess you could try it and see what happens?
On L26 V10, these make some difference. I first had to install the HTCCA drivers to get any of the tests and GL-mark to run.
Compared to the HTCCA drivers, here's what I noticed from brief testing:
- Text 3D was clear and readable, unlike with just HTCCA drivers
- With Lights.exe, HW T&L and rasterisation were false instead of true, seemed to run smoothly, don't know how to get FPS to compare
- D3DMdemo.exe seemed to run much faster with this than HTCCA
- GL-Mark tests seemed the same, no better or worse (but did not work at all before installing HTCCA drivers, then these on top)
Can't compare TCMP, as it does not seem to work on L26 V10 at the moment. No apparent increase in snappiness of 2D environment etc as far as I could tell (PointUI us always snappy apart from when changing screen orientation).
Lets see what others notice... keep up the good work with the drivers folks!
If it reports that there's no HW TnL etc. then it's perhaps just an optimized software path.
Can't wait to hear what Chainfire and his crew has to say about this though.
Can the "author" gibve us some more info on what files are included, etc.
More reports (proper before/after tests in Coreplayer and TCPMP using directdraw would be interesting) needed!
Benchmarking on the fly...
VSBenchmark 2007 on a fully loaded Romeos v.4.21 with running apps (Blackberry Connect, PUI Home etc etc). Just look at the "graphics" values.
Install: the Samsung driver overwritten HTCCA driver.
1St Column -> HTCCA Driver
2Nd Column -> Samsung Drivers
Vsbenchmark 2007 Score: -- 1561 -- 1542 --
CPU score: -- 1739 -- 1752 --
File system score: -- 1907 -- 1861 --
Jpeg score : -- 2421 -- 2429 --
Game score: -- 1472 -- 1499 --
Write 1 MB file (KB/sec): -- 515 ms -- 595 ms --
Read 1 MB file (MB/sec): -- 81 ms -- 91 ms --
Write 8 KB x 128 files (KB/sec): -- 1440 ms -- 1486 ms --
Read 8 KB x 128 files (MB/sec): -- 246 ms -- 347 ms --
Fill Rate Buffer To Screen (Fps): -- 310 fps -- 326 fps --
Fill Rate Buffer only (Fps): -- 2381 fps -- 2375 fps --
There seems to be an improvement in graphics benchmarks. Nothing special, just another step towards our true Kaiser.
undac said:
If it reports that there's no HW TnL etc. then it's perhaps just an optimized software path.
Can't wait to hear what Chainfire and his crew has to say about this though.
Can the "author" gibve us some more info on what files are included, etc.
More reports (proper before/after tests in Coreplayer and TCPMP using directdraw would be interesting) needed!
Click to expand...
Click to collapse
That's right, this is only software optimization (Intel XScale Optimized D3DM Driver).
It only installs one file to your device: D3DMXSc50PB.dll and only import functions from 2 modules: COREDLL.DLL, DDRAW.DLL. So I guess it should work on most roms/device.
Just try it guys, you can uninstall it to go back to previous driver.
sakajati said:
That's right, this is only software optimization (Intel XScale Optimized D3DM Driver).
It only installs one file to your device: D3DMXSc50PB.dll and only import functions from 2 modules: COREDLL.DLL, DDRAW.DLL. So I guess it should work on most roms/device.
Just try it guys, you can uninstall it to go back to previous driver.
Click to expand...
Click to collapse
So it is un-installable? ...and uninstalling will roll back to original drivers?
(Just like to check to make sure I can revert if it negatively affects the phone.)
Also, can anyone confirm this works on WinMo 6.0?
It works fine on WM 6.0. Orange rom.
I can confirm - installs on wm 6.0, but... I dunno if it works. Don't have any apps to test it (I forgot where those test apps are ) but fpsece seems to work as ****ty as usual.
thanks for all Sakajati anyway
bro
If this driver is just software optimizations, it is very strange that it would score so close on every benchmark to the hardware HTC ones. Maybe it is reporting software rendering to handset but using the HW someway (note, I don't really know what I'm talking about).
Also, if this driver was ported so quickly. Wouldn't it be just as easy to port the 2D driver(s)?
Hopefully if this driver is HW rendering, it won't piss off the programmer working on the drivers. We still need 2D support!