Hi !
i am new to nike and still stoked, such a nice device
Now i read that Manila3D is almost good to go - And i´ve read that Qualcomm is 3D capable, too.
What about some working (ati?) 3D drivers ?
Just would like to get information for my know-how.
Thanks !
This drivers must be ported first. Just installing doesn't have any results
meisterlampe2000 said:
Hi !
i am new to nike and still stoked, such a nice device
Now i read that Manila3D is almost good to go - And i´ve read that Qualcomm is 3D capable, too.
What about some working (ati?) 3D drivers ?
Just would like to get information for my know-how.
Thanks !
Click to expand...
Click to collapse
Ask Jerpeala he's in nike upgrading forum and he's really knowlegable on nike roms and kitchens
hy
i have tested the 3.55 kaiser ddi drivers with the new 3d drivers that work for kaiser
but on niki i dont get hardware acceleration
till now there are 3 usable drivers(software)
1.from latest opal rom (works but is not fast)
2.from latest opal rom (works and is faster than any htc driver)
3.from latest niki rom 2.12 (the worst)
i can not get 3d working even if i flashed kaiser radio rom and i have used kaiser drivers
there is something else needed (maibe in SPL or IPL)
BR
Okay thank you !
If there is anything that has to be tested...I am the one...
ATM i donßt een have a clue about that, so i´ll have to read a lot till then...
These drivers must be ported for niki (I didn't mean porting to rom)
Kaiser and Niki similiar, but not same. We need someone, who can disassemble and improve .dll's
Polaris already got working drivers
jerpelea said:
hy
i have tested the 3.55 kaiser ddi drivers with the new 3d drivers that work for kaiser
but on niki i dont get hardware acceleration
till now there are 3 usable drivers(software)
1.from latest opal rom (works but is not fast)
2.from latest opal rom (works and is faster than any htc driver)
3.from latest niki rom 2.12 (the worst)
i can not get 3d working even if i flashed kaiser radio rom and i have used kaiser drivers
there is something else needed (maibe in SPL or IPL)
BR
Click to expand...
Click to collapse
My shot is the kernel... this driver don´t work in NIKI´s kernel.
In order to work with the hardware, the driver needs to operate with the kernel. On a computer the SO kernel uses the HAL(hardware abstraction layer) so that one kernel can work with hundreds of hardware configurations. On the PCC/WinCE platform, the kernel is specific, so in the absence of HAL any driver will be specific to that configuratio too. So we need a modded driver wich can work on NIKI´s kernel...
The I/SPL will not add much on this...
We almost have a working SW driver haven´t we ?
So maybe TF3D will be just fine, when it´s done...
Sorry but i am not a software guy
Hy All
i have an working os for nike with kaiser original video drivers
if anyone wants to try it please ask
BR
jerpelea said:
Hy All
i have an working os for nike with kaiser original video drivers
if anyone wants to try it please ask
BR
Click to expand...
Click to collapse
Could you upload it for us?
Thanks!
HOUSTON WE HAVE HARDWARE D3D
UPLOADING ROM NOW
http://rapidshare.com/files/152360877/RUU.rar.html
install this
http://rapidshare.com/files/152361404/HTC-CA-Kaiser-Drivers.cab.html
and
RUN
DLL CHECKER
D3D demo
Best regards
POWER BUG/do not press power button (to restart needs soft reset)
jerpelea said:
HOUTON WE HAVE HARDWARE D3D
UPLOADING ROM NOW
http://rapidshare.com/files/152360877/RUU.rar.html
install this
http://rapidshare.com/files/152361404/HTC-CA-Kaiser-Drivers.cab.html
and
RUN
DLL CHECKER
D3D demo
Best regards
Click to expand...
Click to collapse
Thanks mate!
I will try it later tonight...
jerpelea
please keep my informed which driver package you used (Kaiser or Polaris? modified or original?) and wether you need special ROM for this (ie, you ported kaiser ddi or smth manually?)
This so that info can be put up on the HTC-CA site
(Kaiser, Polaris, now Nike.. we getting places )
Alex Minards said:
Thanks mate!
I will try it later tonight...
Click to expand...
Click to collapse
Alex, any feedback on installing the cab file. I'm keen to try it out, but currently busy testing a rom for one of the cookers. (don't want to skew my results )
Whoa, so what is this useful for? Just 3d? I want bloody 2d fixed first! It's horrible! =P
And what's that bug? Could you explain it a little more? Also, can that cab be installed with any rom or only that one you provided?
xangma said:
Whoa, so what is this useful for? Just 3d? I want bloody 2d fixed first! It's horrible! =P
And what's that bug? Could you explain it a little more? Also, can that cab be installed with any rom or only that one you provided?
Click to expand...
Click to collapse
you can use the cab only with the test rom
is the original kaiser cab
the power bug is solved
BR
Chainfire said:
jerpelea
please keep my informed which driver package you used (Kaiser or Polaris? modified or original?) and wether you need special ROM for this (ie, you ported kaiser ddi or smth manually?)
This so that info can be put up on the HTC-CA site
(Kaiser, Polaris, now Nike.. we getting places )
Click to expand...
Click to collapse
i have used kaiser ddi drivers and original kaiser htcclassaction.org drivers
you need this special rom to use it
BR
i will release soon an new rom with all the bugfixes done incluing 3D drivers and test tools
ans if is enoug space i have an surprise (quake 3 GL demo)
i have tested it last night and is
BR
Good to know. You ported the Kaiser DDI to Nike, interesting.
How did you solve the power issue, though?
What about the 2d scrolling etc?
Related
I was wondering is this possible.
The hardware spec. is pretty much the same, except the TouchFLO.
I think ... the Touchscreen is differnet and the main Problem. I have see, the first ported touch cube starts via hardware key! not like on a elf.
Touchflow available on Wizard???
I am not too sure if the H/W if so diff... I think someone has been succesful in porting touch flow to the Wizard.
Check out the following link..
http://forum.xda-developers.com/showthread.php?t=313656
Actually, I didn't hope for the TouchFLO to work.
Just that this may be the first official WM6 ROM for HTC Device.
It may be a good and stable base ROM for further development.
Would it help if I uploaded the rom of the german o2 version of the htc touch. My brother got one yesterday. From the first look is the touchscreen pretty much the same as that of the prophet. Same memory size and processor type, too. Just more MHz.
Greets
Markus
not working
I've tryed to flash a rom with all the OEM parts from the ELF the only new app I got working was the new camera wich by the way is realy cool. but none of the other apps worked. they did load but where not displayed. like the commanager showed no images but I could turn on bluetooth by pressing the screen where the image was supose to be.
to get it to work some dll files must be modified
what would be handy is to get the battery driver from this rom and try it, as this is still giving problems on the current WM6 roms.....
Jesterz said:
what would be handy is to get the battery driver from this rom and try it, as this is still giving problems on the current WM6 roms.....
Click to expand...
Click to collapse
now that would be intresting yes. I will try that
http://forum.xda-developers.com/showthread.php?t=416474
Seems to have speeded up the scrolling on my phone and made it more responsive when i touch the screen.
I may be imagining it though.
Someone else try and let me know what you think?
I've cooked my ROM using it : my Niki seems to be a little more responsive than with the HTC one, but I haven't benchmarked it, so I don't know if it's my mind or the driver
In fact, since it can't be worst than original D3D driver, I think I'll keep it for a while...
I have try it...
and seems that it doesn't work
I use official rom ported to WM6.1
What do you mean by "it doesn't work" ?
My device has a ROM cooked thanks to jerpelea's kitchen, and when I mod the registry in order to use the Omnia driver, everything look OK for me...
CAb installed succesfully on my HTC TOuch ( ELF) with self cooked rom wm6.1 !
I perform benchmark actually !
Note : This driver is for the graphical ? or for the processor ?
Thanks !
It's a D3Ddriver, but a software driver...
I cooked it, not used the cab... Maybe the problem come from it ?
I heard that drivers need to be cooked, cant be just installed.
Does it work better? Or there isnt much diference? How about in 3d games?
Hi,
It´s possible to install this drivers in an original rom?
Thanks in advance.
Huiguita
I think we need to wait the NEw htc wm6.1 rom, and update our drivers
These driver will not work on niki because Omnia based on Intel Xscale CPU without video accelerator.
CPU in omnia can understand MMX instructions, this is the main reason it works very fast in video decoding (About 1.5times faster than HTC Diamond)
P.S. Doesn't work means thats there is no any differences after installing
I cooked a rom. Basically, it's a PTG OEM Rom, but with drivers from Dopod s600. Used same method that xangma. However, I'm testing the rom now, but the system seems to be the same, no improves. Maybe I'm wrong, but there's no software benchmarks can I do to display driver?
Other question, there's any way to improve system performance? I've installed advanced configuration, but file cache was already enabled.
By using original Touch Dual driver, you device will be freeze up every time you touch the touchscreen (Thanks HTC!)
Dopod S600 driver doesn't have this problem
Tiago Machado - try to clean up you rom
Tim4 said:
By using original Touch Dual driver, you device will be freeze up every time you touch the touchscreen (Thanks HTC!)
Dopod S600 driver doesn't have this problem
Tiago Machado - try to clean up you rom
Click to expand...
Click to collapse
I've flashed the Rom minutes ago so I've only Resco explorer and Adv. Config. installed. I'm confused because, when I use Mary, Tom, and Shark Rom's, they come with a lot of programs and are faster than mine now, so I always thought that the speed was conected with the video driver.
So... how can I put my rom working like yours?
May be you just made something wrong with cooking?
When i have cook my self rom (20753 build), it was isn't faster, isn't slower than other rom
Tim4 said:
May be you just made something wrong with cooking?
When i have cook my self rom (20753 build), it was isn't faster, isn't slower than other rom
Click to expand...
Click to collapse
No... The only thing I've done was replace all touch.dll folder. I wanted to have two roms exactly the same but with differente video drivers so I can compare... But I will do some tests now. I've downloaded this software and it's running right now.
http://www.freewarepocketpc.net/ppc-download-vsbenchmark-2007-v1-20.html
Dont you know a better software?
I just finished the benchmarks... well... the results are almost the same So many hours cooking and then I even dont know want gonne wrong... anyone have the results with and withouth most recent video driver so we can compare?
Nothing wrong, just there is no any video driver that will work on niki
Tim4 said:
Nothing wrong, just there is no any video driver that will work on niki
Click to expand...
Click to collapse
So, why are some roms faster than the others?
So, why are some roms faster than the others?
Various builds, cleaning, etc.
I use original rom ported to wm6.1
I don't think Mary rom, or Tom's rom work much faster that my one (I have tested it, benchmarking prof it).
Can you cook rom, that contains build from kaiser, radio from kaiser, and .dll from kaiser (DDI.DLL, DISPTOOLS.DLL and another that can be compatible with niki)?
May be it will allow to use D3d driver from kaiser
Tim4 said:
So, why are some roms faster than the others?
Various builds, cleaning, etc.
I use original rom ported to wm6.1
I don't think Mary rom, or Tom's rom work much faster that my one (I have tested it, benchmarking prof it).
Can you cook rom, that contains build from kaiser, radio from kaiser, and .dll from kaiser (DDI.DLL, DISPTOOLS.DLL and another that can be compatible with niki)?
May be it will allow to use D3d driver from kaiser
Click to expand...
Click to collapse
I dont think that will work Even if I believe it works, I really cant do it. Really a noob Cant you help me faster my rom?
i forgot one thing... there is several programs from original touchflo
They made by HTC (calls HTC_program, htc_settings, they launch from large start menu) they change original programs and settings window to another one (They look absolutely same, but they isn't same). In result it works more faster.
For example - touchscrolling in program's applet. Without this programm, scrolling so laggy (Thanks HTC!), but by using it, scrolling works without any freezes/stops/lags
hi,
i recently flashed my new niki that came right from support with the new htc shipped rom, and also the lite v2.1. but i can't seem to get the hardware drivers to work... no idea why... in lite v2.1 with 3d drivers i get extreme lags all the time and the D3D benchs, whatever u wanna call it just show errors and close. on shipped htc rom i've installed the cab found on htcclassaction.org. the dll check says "dll check finished" but it won't work anyway. none of the benchs work. im using hard spl 1.15 mfg ( might this be the problem? ) and using the radio that came with lite v2.1/shipped rom (dunno lol ) i get no audio there, but ill fix that later... so what to do now?
ok so now ive tried a few radios/spls... still no better... dll check is ok but none
of the other tools work. also performance doesn't seem to be better anywhere
Hey I had this problem and then i realised that you need to install the polaris version of the drivers not the kaiser version. The htcclassaction website is wrong. see here - http://forum.xda-developers.com/showthread.php?t=435153
that worked fine thanks... btw: touchflo3d (not the manila 2d one ) runs fine! its nearly as fast as manila 2d!
Hi all,
I've taken to trying to get some Neon ROM action happening again. I've downloaded the latest Nike ROM kitchen as a base and have managed to get the ROM to install and mostly function on the Neon hardware. The outstanding problems I can't figure out are as follows:
1) The hardware keyboard does not function correctly (it acts like the 16-key model, where "QW" is the internet key, "AS" is start menu) and has no backlight. I have tried installing the latest EZInput files to no avail.
2) The Nike camera application functions but the Neon camera button does not work (have to use the d-pad button to take photoes) and no auto-focus.
3) No working FM Radio application (I have tried the FM Radio QVGA Diamond Style CAB from here to no avail - though I haven't tried the CAB from the original extrom yet).
Other than that, the phone is highly responsive and calls, tones, ringer and vibration are fully functional.
Would appreciate not being accused of lack of searching because I have spent plenty of time researching these issues. The main complication is that the forum does not let you search for 2-letter terms (such as FM, 16, 20 etc). I think I've done a reasonable job getting this far!
Please help!
maximus007 said:
Hi all,
I've taken to trying to get some Neon ROM action happening again. I've downloaded the latest Nike ROM kitchen as a base and have managed to get the ROM to install and mostly function on the Neon hardware. The outstanding problems I can't figure out are as follows:
1) The hardware keyboard does not function correctly
2) Neon camera button does not work
3) No working FM Radio application
Click to expand...
Click to collapse
Given that Nike is the basic starting point, and the Neon is not quite a Nike, have you tried extracting the relevent package from an official Neon ROM and using those in your OEM?
maximus007 said:
Hi all,
I've taken to trying to get some Neon ROM action happening again. I've downloaded the latest Nike ROM kitchen as a base and have managed to get the ROM to install and mostly function on the Neon hardware. The outstanding problems I can't figure out are as follows:
1) The hardware keyboard does not function correctly (it acts like the 16-key model, where "QW" is the internet key, "AS" is start menu) and has no backlight. I have tried installing the latest EZInput files to no avail.
2) The Nike camera application functions but the Neon camera button does not work (have to use the d-pad button to take photoes) and no auto-focus.
3) No working FM Radio application (I have tried the FM Radio QVGA Diamond Style CAB from here to no avail - though I haven't tried the CAB from the original extrom yet).
Other than that, the phone is highly responsive and calls, tones, ringer and vibration are fully functional.
Would appreciate not being accused of lack of searching because I have spent plenty of time researching these issues. The main complication is that the forum does not let you search for 2-letter terms (such as FM, 16, 20 etc). I think I've done a reasonable job getting this far!
Please help!
Click to expand...
Click to collapse
please send an original neon rom and i will make the changes for you
there are some incompatibilities
BR
jerpelea said:
please send an original neon rom and i will make the changes for you
there are some incompatibilities
BR
Click to expand...
Click to collapse
Thanks jerpelea,
seth2006 put an original copy of the Telstra Neon ROM here, which is the same as what came on my device initially. If you hate rapidshare I can upload a copy elsewhere.
Once you have figured out the incompatibilities could you post them here so us Neon users can finally stop begging for help? Or better yet, explain briefly how you knew which files to extract?
Thanks,
Max.
This is awesome news : ) Sig me up as a tester
hy
it will take me several days
BR
Thanks jerpelea from all us Neon tragics!
I just popped my sim back in my Neon 300. Would love to start testing for days when I'm bored with my G1.
do you have a kitchen or you use nike kitchen?
hardspl works for you ?
br
jerpelea said:
do you have a kitchen or you use nike kitchen?
hardspl works for you ?
br
Click to expand...
Click to collapse
I was a goof and loaded a rom before I had a backup of my US Neon300.
This is how I did my hardspl
http://forum.xda-developers.com/showthread.php?t=377260
Would one rom work for each neon (200,300,400) or would different versions need to be made?
Here it is - the first test version of the new Neon ROM!
Can I get a copy of the kitchen you used? I'd like to start looking into cooking myself. I think I have enough info to get started. I just never had the right info to put together a working kitchen.
TheDudeOfLife said:
Can I get a copy of the kitchen you used? I'd like to start looking into cooking myself. I think I have enough info to get started. I just never had the right info to put together a working kitchen.
Click to expand...
Click to collapse
I will release the kitchen in full once all the issues are sorted out
maximus007 said:
I will release the kitchen in full once all the issues are sorted out
Click to expand...
Click to collapse
Awesome, perfect, wonderful.
maximus007 said:
I will release the kitchen in full once all the issues are sorted out
Click to expand...
Click to collapse
I, for one, am extreamly excited about getting the kitchen. I have always wanted to learn how to cool, so this will be great!
Whatever happened to this kitchen?
I have factory neon 300
I am extracting parts 0 through 3 as we speak. I can post those for you if you like and it will help speed this project along.
Val
I have hung back waiting for this moment, Neon 300? sign me up