TouchFlo: Why only ROM but no cab? - Windows Mobile Development and Hacking General

I´ve been following with interest the porting of touchflo interface to non-Elf (Touch) devices.
There have been lots of requests for developing a cab with files n settings for such an interface. It has been suceesfully ported to custom ROMs for Artemis, wizard...., but developers say that there is no way to build just a cab.
not being a developer, i would like to know the rationale behind "cab is no possible", as i can not undestand why, if touch flow can be ccoked to a ROM, it can not be made into a cab. Surely there is an explanation.
(i ask this question because i´d rather keep the stock ROM until warranty period is over, but i want to use my device (Artemis) as much as possible without reverting to stylus)

The Problem is that the Touch.dll must be replaced with the one from HTC Touch... this is not possible.
Only before cooking the Rom you are able to replace System DLLs
..
hope this helps

So the solution would be to make an installation rotine that unloads touch dll from memory, ,overwrites it with the replacement "flo" one, and then reload touch dll.
is that a workable solution under MsMobile platform?
Sorry if i´m proposing a nonsense, as i´m no programmer at all (just "hello world" stuff)

I'm not one of the ROM cookers here but I think the system dlls that need replacing cannot be deleted because they are in ROM and therefore, the device needs to be flashed to change behaviour.

damac said:
I'm not one of the ROM cookers here but I think the system dlls that need replacing cannot be deleted because they are in ROM and therefore, the device needs to be flashed to change behaviour.
Click to expand...
Click to collapse
or just the cab being reinstalled after every hard reset?

The touch.dll is different from device to device... so u'll have to have a "touch" dll that fits your device. Another reason is that the dll can not be changed after flashing the rom, has it is protected by the OS (not even using Total Commander...).

I try to overwrite Touch.dll via some program to replace the original Touch.dll.
After replace it, Touch-screen is no respond to any touch on the screen but Hardware button still working ,then I restore my device.
In my idea, I think Touch.dll is device specific and this file take control all of touch-screen. So Touch.dll cannot be replace by conventional method.
We have to rewrite Touch-Flo program to hook on another dll, e.g. Touch-Flo.dll. (This is just my theory) But I don't know "How to do it ?".
Does anyone have idea about it ?

dferreira said:
The touch.dll is different from device to device... so u'll have to have a "touch" dll that fits your device.
Click to expand...
Click to collapse
Well, until Tytn II(Kaiser) is released, the only touch-flo enabled phone that can be bought off the shelf is HTC Touch.
So all cooked ROMs for Artemis, Wizard.....that include touchflo, must include touchflo dlls extracted from HTC Touch ROM.
Then, my understanding is that, as these touch-flo ROM do actually run on devices other than HTC Touch, the dll´s needed must be not so "device specific" but (more or less) generic for QVGA devices without graphics processor (or at least for OMAP 200 devices).
maybe its not only touch dll, but also other files which have to be replaced by files from HTC Touch.

Has any body managed to extract the touchflo files from HTC touch or TytnII??? If yes then kindly post them here. Maybe we can try to put it in other models like Hima..

c_shekhar said:
Has any body managed to extract the touchflo files from HTC touch or TytnII??? If yes then kindly post them here. Maybe we can try to put it in other models like Hima..
Click to expand...
Click to collapse
There a number of ROMs that include TouchFlo in Prophet, Artemis n Wizard xda-dev forums.
i dont know how to extract specific files from a ROM file, nor which files are flo-related files, and have to be extracted.
Surely the cookers of those ROMs can advise and even provide the Flo files.

sirgawain123 said:
There a number of ROMs that include TouchFlo in Prophet, Artemis n Wizard xda-dev forums.
i dont know how to extract specific files from a ROM file, nor which files are flo-related files, and have to be extracted.
Surely the cookers of those ROMs can advise and even provide the Flo files.
Click to expand...
Click to collapse
look in the wizard WM6 forum, there are several kitchen roms and links to OEM packs with all the touch stuf thats needed.

I agree ,
i dont understand why is not possible to make one application just to touchflo,
let´s take some examples:
http://forum.xda-developers.com/showthread.php?t=321242
this stops, but i test and works, only whid some bugs, and is not reali a touchflo
http://www.pocketcm.com/index.php
this one makes touchflo
http://forum.xda-developers.com/showthread.php?t=325223&highlight=iphone+media+player
this one is touchflo application
icontacts is a touchflo application
so...i dont understand why is not possible to make a touchflo cab
i have all this aplications in a s200 wm5!

Marcos200 said:
i dont understand why is not possible to make one application just to touchflo,
let´s take some examples:
http://forum.xda-developers.com/showthread.php?t=321242
this stops, but i test and works, only whid some bugs, and is not reali a touchflo
http://www.pocketcm.com/index.php
this one makes touchflo
http://forum.xda-developers.com/showthread.php?t=325223&highlight=iphone+media+player
this one is touchflo application
icontacts is a touchflo application
so...i dont understand why is not possible to make a touchflo cab
i have all this aplications in a s200 wm5!
Click to expand...
Click to collapse
touchflo requires Touch.dll, and Touch.dll is not an application. Itz part of the OS which is device dependent. Unless someone writes a fully working touchflo cube, managed to remove the current touch.dll with his own dll, then it is portable from device to device.

c_shekhar said:
Has any body managed to extract the touchflo files from HTC touch or TytnII??? If yes then kindly post them here. Maybe we can try to put it in other models like Hima..
Click to expand...
Click to collapse
Hi C_shekhar
Is this can help
http://forum.xda-developers.com/showthread.php?t=321844

The_hesham said:
Hi C_shekhar
Is this can help
http://forum.xda-developers.com/showthread.php?t=321844
Click to expand...
Click to collapse
funny thread in the sense some pple is asking the same again and again.
I would summarize state of art as follows:
-Some ROMs with Touch flo have been developed by forum members for devices other than HTC Touch.
-Touch flo files are available for those who want to cook their own ROM, at least for OMAP devices.
- As today,Touch flo files can not be installed in a device over an existing ROM because installation can not overwrite certain files as they are in use by the system.
Workaround (Yet To be made)would be an installation routine that unloads files to be replaced, and loads touchflo ones. This routine should be performed after every reset, as resets reloads the files from original ROM.

Here are a bunch of cabs to give you the look of the Touch but these won't give you the finger scroll feature.
http://forum.xda-developers.com/showthread.php?t=311225
I personnally don't care for the eye candy on my wizard, but like the touch driver that lets me finger scroll. The OEM packs I've seen bundle this driver with the today plug-in, but there's just a few files specific to the touch driver that can be separated out from the today plug-in.

jorge_culv said:
Here are a bunch of cabs to give you the look of the Touch but these won't give you the finger scroll feature.
http://forum.xda-developers.com/showthread.php?t=311225
I personnally don't care for the eye candy on my wizard, but like the touch driver that lets me finger scroll. The OEM packs I've seen bundle this driver with the today plug-in, but there's just a few files specific to the touch driver that can be separated out from the today plug-in.
Click to expand...
Click to collapse
to get fingerscrolling you'll only need the touch.dll not othere file or regestry setting but somehow it doesn't seem to work for all devices. I don't know why... if it just can't work or no one figured it out yet?

The_hesham said:
Hi C_shekhar
Is this can help
http://forum.xda-developers.com/showthread.php?t=321844
Click to expand...
Click to collapse
No it does not help.....

Is there any Hermes ROM cooked with TocuhFlo?

Gullum , i need help, please.
Gullum,
thnks for the very profecional good work, in all app, roms, foruns, etc.
one question,
i dont need flash my prophet (S200 pt), but i use all the finger friendly applications that we have in xda.
i looveeee the finger scroll applications.
but i have now 1.5 years waranty, and i dont need flash.
just the scrolling feature, the touch.dll, like you say, but i dont now how i need to just install that in my wm5 rom in portuguese.
is there a solution?? a cab, or just put oem files and replace the ones that i have. i use the touchnav application, but i need more, also use the very best iContact v3, but i need finguer scroll in all applications, like the touch
Thanks in advance,

Related

Newbs: cooked rom or cab install? And go back?

Hi all.
I've bought an herald (P4350 in Italy) for my wife. I've registered the product to htc club and i've installed windows mobile 6 in italian.
Now i've read some thread as:
Newbs guide to Herald modification *updated* 10/18/07: http://forum.xda-developers.com/showthread.php?t=327046
and:
All you need on your Wing: http://forum.xda-developers.com/showthread.php?t=326655
If i've understood well, the first option means overwrite the OS i've just installed with another one with (impressive) features (as touchflo, cube interface, kayser like apps) preinstalled.
The second means collect some apps and install it (maybe it's possible htc home, even touchflo but certainly not cube's interface).
Well, due to limitation of the second way (cube's interface for example), i'd like to try the modified rom (cooked?), but i've some questions:
1) First of all, is it true that i can have all the functionality of the "Touch-IT,WWE v1.1" or similar cooked rom only by flashing the rom or i can found ALL the functionality by installing some apps?
2a) If 1) is false where can i found ALL the apps for doing the same things as well as in a cooked rom?
2b) If 1) is true, can i flash with Touch-IT rom my italian device with italian WM6 installed?
2bI) If 2b) is true, after trying Touch-IT rom can i reinstall my WM6 italian rom by double-clicking on the file downloaded from htc club? If not is a way to rollback to the original rom?
2bII) If 2b) is false (but also if it's true because i prefer the OS in my language ), PLEASE Itje make a Touch-IT,IT where the second IT meas ITALY
1. While you can have the apps, touch-it is built on a newer, more streamlined version of windows mobile 6.
2a. see 2b
2b. You can flash the WWE. I believe there was some effort to get a native language port, ask itje about that.
2bI. Yes. I believe the HTC club one is an RUU, a "Rom Update Utility". If you mess up in the flashing, you can use it restore from bootloader also
2bII. Again, ask itje.
wow that was confusing. Outlines are like hell on a apple.
fzzyrn thanks a lot for answers.
1. So u think that i can have also cube interface by installing an apps? Wich one?
2b. how can i contact itje for a native language port?
Again, thanks a lot for helping me.
i believe there are like flash-based emulations of the cube. Look in the main software development forum.
To contact Itje, private message him. Click on his name and then it should be obvious to extent

Building and Editing Polaris ROM's

Hi All
I see now we are getting quite a few custom ROM's from the likes of bepe, panosha and other.
Great Work Guys.
But i would also like to be able to build or a least edit a ROM to exactly meet my requirement. Like adding or removing certain CAB files and making reg edits.
Have been reading a lot of other threads on the site put none seem to deal directly with the Polaris.
So i was hoping some of you great cooks (grovel grovel grovel) would wight a description on how to take a nbh file and extract and edit the different nb parts and then rebuild back to a nbh file ready for flashing.
Thanks
polaris kitchen
sorry......wrong answer
I'd love that too! I want to mod an existing ROM and make it specific to my needs.
Will anyone be so kind and post a short guide how to do this? And make the topic sticky!
First, you can start with Kaiser's Kitchen...and at last, use Dark Simpson tool (htc room tool) to make nbh file (config add Polaris device in tool config)
Cheers,
ouioui
Good place to start is here http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
Yep , good one, but everything is based on Kaiser.
I don't have a Polaris Radio, neither does the HTC Rom Tool allow to cook Polaris Rom's.
Any other ideas ? Or could someone help ?
Thanks a lot in advance
The Kaiser kitchen works fine and all you need to do with the Dark Simpson ROM tool is change the Model ID from KAIS***** to POLA*****
As always read the threads before you start cooking and make sure you have Hard SPL!!
Thanks
I've been reading all night ;-)
In the HTC Rom tool there is no Polar***** , strange, although I thought I downloaded the newest ini. I've read in another thread that I could use the Kaiser one as it was basically the same device, is that so ?
Other question though:
Talking about Hard-SPL- I've Hard-SPL'd mine , but do I need to include that one in the rom as well ? Like while using the HTC Rom Tool , in the SPL section ???
Second question, where can I find the radio.....nb ?
Thanks for your help, I appreciate that.
As I said set the ROM tool to Kaiser then change the Model ID to POLA***** and use as normal to create the nbh image.
As for Hard SPL... once you´ve flashed it that´s that, no need to flash it every time you change ROMs or radio...
id love to see the guide for polaris aswell.
and oem packages as well.
i did everything as it was sowen in kaiser guide, but i got an error on building system. have no idea why..
was saying that something is missing or path is icorrect smth like that
post here exact errr.U got.
here is htcrt.ini for polaris (only Polaris Option is active) simply rewrite htcrt.ini in folder with htcrt.EXE
It's not necessary to include Radio ROM when building? Right?
nope, its up 2 U what 2 include (SPL/Radio/OS/Splash)
phsnake said:
post here exact errr.U got.
here is htcrt.ini for polaris (only Polaris Option is active) simply rewrite htcrt.ini in folder with htcrt.EXE
Click to expand...
Click to collapse
Thanks for the guidance. The tutorial is great but fails to mention specifics if you are not cooking a Kaiser Rom. For example, does the baserom have to come from a shipped Rom? I was using the 3.02 Kaiser Rom as my baserom. Can you do that when cooking a Polaris rom? How do I get the RUU_signed.nbh out of any other Rom. I thought about using the WM6.1 19716 Rom but couldn't extract anything. (Probably stupid questions but cant find answers in the wiki). BTW, I was getting same errors about half-way through compiling process. If I try again today, I will record the errors and post. Again, thx for help.
sgreenwood99M me i have 19716 WM6.1 for cooking. U can Use some part of any ROM but U have to be sure exactly what. In general U can Use OEMpackages freely, but be aware with drivers, baseapps....(i have perfect CZECH 19199 WM6.1 but w/o working SMS)
Hi,
i've read through the Kaiser kitchen guide and it all seems to make sense however i'm not sure how much is relavent to the Polaris, for example the ingredients section talks about expanding the radio file and the rom files to folders, from the Kaiser files on rapidshare etc.
Do us Polaris users do these points too? or are there specific Polaris Radio and ROM files we use?
I have my base ROM file called RUU_signed.nbh and i've also managed to use pdocread to get the RAW files too, but just not sure where to go now?
All i want to do is remove a few cabs and add a few cabs and EXEs to my rom.
can anyone post comments on exactly which parts of the Kaiser kitchen guide need to be changed to use on a Polaris?
thanks.
dont need raw's. simply put *.NBH(polaris) to BaseRom folder. Run begin.cmd(or bat?) Choose option 1.
click......... then start cook.cmd(or bat)
Do we replace the KaiserCustomRUU and the BuildOS files with ones specific to Polaris? Thanks.
yes, take udK CustomRUU & replace kaiser one, u dont need to replace anything else(except htcrt.ini ||KAIS**** replace with POLA***). And of course Polaris' *nbh
Whenever I put a Polaris nbh in the BaseRom folder, the process gives me an error that it cannot find RUU_signed.nbh.

WM6.1 Manila2d Blueangel ROM

Requesting all those great Rom cookers out here to create a Rom with Manila2d in it. No, not on ExtROM but inside the ROM itself. That would be faster better and faster I think.
ebautista said:
Requesting all those great Rom cookers out here to create a Rom with Manila2d in it. No, not on ExtROM but inside the ROM itself. That would be faster better and faster I think.
Click to expand...
Click to collapse
Integrated Manila 2D into cooked ROM is surely a better solution, however most people prefer a clean ROM. Beside due to limitation of the flash size (32MB i think), it would requires to remove lots of even basic application come with the ROM.
not possible due to limited 32 mb storage. even the mms is not included in any ba wm6 rom so can u think for Manila.
ebautista said:
Requesting all those great Rom cookers out here to create a Rom with Manila2d in it. No, not on ExtROM but inside the ROM itself. That would be faster better and faster I think.
Click to expand...
Click to collapse
krishan2207 said:
not possible due to limited 32 mb storage. even the mms is not included in any ba wm6 rom so can u think for Manila.
Click to expand...
Click to collapse
exactly...
M2D cooked in
I'v tryed to fit "M2D" in a cooked ROM you can get the main files in there' But not enough of the image files, I also did some test builds "without" the calc, media player,dialer,and commManager skins, And Flashed them from "ExtROM" as Themes It Seamed to Work fine But you would still Be adding A large number of files Via ExtROM so not much to be gained (can't say It was any different speed wise)
My origonal Idear was Adding skins to your device like this may, make rom's more fun and the user could change Skins From *.cab files (Themes)
So If you fancy a try and some people are intrested in making some Skins then I'll cook My New V3 and working version of M2D into a "ROM" With all Skins Removed and Post it with One Full Set of Skins in CAB files and folders of files for you to edit and i'll even pack some of your Themes into CABs and we'll see what Comes of it
I would like at least 5 people to be intrested in assisting with skins as I don't Have enough time to do it all
So If you would like to have a GO then you need to say SO or i'll not bother that's my offer regards
swampy395
I think it is a great idea, manila2 in a cab with no skin, and the default skin in a separate .cab so we can replace and tinker with it at leisure
I am in to give a hand!
Ok people think about it just for a minute, Manila 2D has a size of 12 mb, with a rom of 32 mb even if it is compressed we have to cut a lot of things from main rom to make this possible, and the the stupid questions will come, why this or that not work. Thats why i am working on a proper kitchen so the people can choose whatever packages they want in rom and make it themself. So if the rom does not boot or has audio video formats problems or software compatiblity problems this will be the builder configuration fault not mine or any other rom cooker.
Also you can use my last kitchen but you need to add options.xml in OEM and SYS folder to choose the packages
swampy395 said:
My original Idea was Adding skins to your device like this may, make rom's more fun and the user could change Skins From *.cab files (Themes)
Click to expand...
Click to collapse
Well this is good as idea(i mean the complete customization from cabs and saving space from the skins in the rom area) but you have to make manila not to load on startup because without skin it will just crash and you will have to reset, and there will be infinite loop ...
xplode said:
Also you can use my last kitchen but you need to add options.xml in OEM and SYS folder to choose the packages
Click to expand...
Click to collapse
I would love to give this a try, but I don't know enough about the interdependencies of the root packages to build a reliable options.XML file. Could you post a list of the diff packages that are part of the ROM with a notation of which are required, which are nice to have and which can be left out? If you do, then I will try to build an Options.xml file and post it for testing with your kitchen.
I have modded manila2d so the default skin is no more and instead one more of my liking. The resulting cab is 100KB smaller...
It boots fine
Will be posting today
gloomyboy said:
I have modded manila2d so the default skin is no more and instead one more of my liking. The resulting cab is 100KB smaller...
It boots fine
Will be posting today
Click to expand...
Click to collapse
you cooked it in rom or what ?
No, I haven´t gone yet for cooking, I just tinkered with the .cab files in the ExtROM folder.
See my separate thread for details
Themes
Hi guys
NO fighting
As my previous post I did some tests and I could get enought of the M2D files in the ROM for IT to boot! and from "rom boot" to "ExtROM Finnish" it doe's not try to load M2D, first load of M2D is after the reset that Terminates ExtROM loading BUT I had to remove 'Calculator,Dialer,WM_Player skins,ring tones and some shortcut, The rom I tested for about 4 days and was as stable as any rom!, And here's a BIG "BUT" Keeping track of all the bits that are needed is a some TASK! in short it will work but it's hard work
swampy395 said:
Hi guys
NO fighting
Click to expand...
Click to collapse
Fighting???? We are all friends in here.
swampy395 said:
As my previous post I did some tests and I could get enought of the M2D files in the ROM for IT to boot! and from "rom boot" to "ExtROM Finnish" it doe's not try to load M2D, first load of M2D is after the reset that Terminates ExtROM loading BUT I had to remove 'Calculator,Dialer,WM_Player skins,ring tones and some shortcut, The rom I tested for about 4 days and was as stable as any rom!, And here's a BIG "BUT" Keeping track of all the bits that are needed is a some TASK! in short it will work but it's hard work
Click to expand...
Click to collapse
I can live without all of the things that you removed as I use alternates for all of them which are loaded into storage anyway and just waste the ROM space.
BUT, as you say, I don't have enough knowledge to know which parts can and can't be dumped from the core ROM. That's why I asked Xplode to make a list. If you can make some kind of list, I'm willing to try and build a suitable options file to be used with his kitchen.
Another thing. I may be slow, but I can't figure out what parts of M2D are in the ROM and what parts are being installed via CAB. I opened the M2D cab and I see that the executables are still in there. If they are in the CAB, what are you loading in the ROM?
motisu said:
Fighting???? We are all friends in here.
I can live without all of the things that you removed as I use alternates for all of them which are loaded into storage anyway and just waste the ROM space.
BUT, as you say, I don't have enough knowledge to know which parts can and can't be dumped from the core ROM. That's why I asked Xplode to make a list. If you can make some kind of list, I'm willing to try and build a suitable options file to be used with his kitchen.
Another thing. I may be slow, but I can't figure out what parts of M2D are in the ROM and what parts are being installed via CAB. I opened the M2D cab and I see that the executables are still in there. If they are in the CAB, what are you loading in the ROM?
Click to expand...
Click to collapse
Hello again
I didn't publish that ROM, It was a test 'only' My M2D roms have most of the today plugins removed from rom as you don't need them, you can only have M2D plugin running!! If you remove WMP you loose so many formats 3gp etc. There are many things you can install from cab But cannot leave out thay have to go back in, The end finnished rom plus cabs is just the same size so y bother
P.S. If your useing a swampy rom then you can flash new skins from a cab
Swampy, if you cook my modded M2D you will have some 100Kb more to play with in the first place...
Now, if you zip up your ´Removed´ folder after cooking a barebones rom with M2D in rom we can help you build .cabs that would go in ExtROM an hence we would have a much more modular design
Taskmanager is a good candidate to go on a .cab, some people like one some like another. It pains me to see two installed
Swampy, but there is an alternative to Windows media player,
Mplayer, a 4megs cab. Supports many formats, it is lean and a standard in Linux (available for Windows Mobile)
Download MPlayer for Windows Mobile
You could remove everything to do with windows media player and put them on a .cab, then give users a choice; windows media.cab or mplayer.cab
swampy395 said:
Hello again
I didn't publish that ROM, It was a test 'only' My M2D roms have most of the today plugins removed from rom as you don't need them, you can only have M2D plugin running!! If you remove WMP you loose so many formats 3gp etc. There are many things you can install from cab But cannot leave out thay have to go back in, The end finnished rom plus cabs is just the same size so y bother
P.S. If your useing a swampy rom then you can flash new skins from a cab
Click to expand...
Click to collapse
Sorry, but I'm still not following you. In the first post of your 20275 thread and in your sig, you have a M2D version. If this isn't the M2d in ROM version, then what is it? If all that you did was leave out the today plugins, what did you use the extra ROM space for? Also, I never use WMP as almost any other player is far better IMHO (Coreplayer, S2P, Tcpmp,Mortplayer, Etc.) If I don't use it, will I still need its support for diff file types?
Swampy´s M2D roms don´t contain M2D in the rom itself but will install it in rom from the storage card whenever you do a hard reset.
So it is basically loading the extra stuff from a custom ExtROM folder in the storage card
Of course I agree it would be better to have M2D in rom proper and say windows media player in a .cab in the ExtROM folder so it can be easily removed if you don´t want it (I certainly don´t want it)
gloomyboy said:
Now, if you zip up your ´Removed´ folder after cooking a barebones rom with M2D in rom we can help you build .cabs that would go in ExtROM an hence we would have a much more modular design
Taskmanager is a good candidate to go on a .cab, some people like one some like another. It pains me to see two installed
Click to expand...
Click to collapse
I agree with gloomyboy. Since there are SO MANY differnt app/utilities that more or less do the same thing, it stands to reason that everybody will have their own preferences. If someone could build a kitchen that really allows you to pick and choose what goes into the ROM, everybody could custom tailor their ROM for what they really use. Unfortunately, AFAIK, all of the kitchens available today only allow periferal change and not major systems changes. I don't know why, maybe it is just my lack of understanding of the core requirements of a ROM and it can't be done any other way. But I can allways wish....
gloomyboy said:
Swampy´s M2D roms don´t contain M2D in the rom itself but will install it in rom from the storage card whenever you do a hard reset.
So it is basically loading the extra stuff from a custom ExtROM folder in the storage card
Of course I agree it would be better to have M2D in rom proper and say windows media player in a .cab in the ExtROM folder so it can be easily removed if you don´t want it (I certainly don´t want it)
Click to expand...
Click to collapse
OK, now I get it. I do that myself with my own home grown EXTROM based more or less on Xplode's new release of M2D with all sorts of shortcuts and config files being copied from my SD card into memory. I am constantly changing my cfg.txt file to include newer versions and getting rid of apps and utilities that I find that I don't use. I think that the ROM should contain all the permanent stuff that will fit and I can't function without.

pictures tab (official sense2.5) - G-SENSOR ROTATION?

hello folks, i'd like to ask if it is possible to get the g-sensor rotation with the HD2 animation on the official sense 2.5 rhodium rom, and also when sliding the keyboard?
I'm asking because i think there's a chance htc could have left the necessary manila files required for this is the windows directory, and if not, maybe this can also be done by adding some files we could grab on a HD2 dump...
so please guys, tell me what do you think is possible for that
THANKS IN ADVANCE EVERYONE
It is possible.
Most chefs will mention it if it's included, I think NRG has it? Not too sure!
Just try a few chefs out, or ask the chefs directly on the relevant thread.
Not sure if I understand you question but there is a program called Gyrator. It changes the rotation as you move the screen.

Blackstone updated 6.5 OEMDrivers?

I have searched and asked whether there are any updated OEMDrivers for the native Blackstone 6.5 Kernel? It appears some of the Topaz 6.5 OEMDrivers are compatible with the Blackstone 6.5 native kernel and there are ROMs out there that have these drivers integrated? In the dump of the latest official Topaz 6.5 ROM lots of the .dll files from OEMDrivers are modules that get dumped as single files in the final Blackstone 6.1 ROM. I think due to the memory differences between 6.1 and 6.5 this is beneficial for Blackstone WM 6.5x ROMs with the native 6.5 Kernel?
I don't have the luxury of going through each of the files/modules and cooking ROMs as I only have a single Blackstone and its my only phone. But it does appear this has already been done by some of the Blackstone chefs? If someone could let me know what modules/files I can transport from the Topaz to the Blackstone I'd be grateful - maybe an upload of a converted/updated Blackstone OEMDrivers kitchen folder?
Many thanks
Andy
The Mikenificent ROM contains some updated Topaz Drivers apparently? The chef isn't responding to PM's and any other requests I have made have gone unanswered so does anyone have a dump of this ROM or the OEMDrivers folder?
The link to the Mikenificent ROM has also gone...
Andy
Hi Andy,
I've tried my self, but it's not an easy task.
I'd suggest to identify the target drivers you want to improve from the original Blackstone 1.59 ROM, and then create cabs with the Topaz drivers and install them on top for a quick try. You may need to recmod some of them.
I have tried a few of them, but some are not compatible (E.G.: smarttouch)
An alternative is to ask someone of the users on the mikenificent thread for a copy of the 13.3 Rom, flash it and get a copy of the drivers he is using and compare with the original blackstone drivers.
ypsmav said:
I'd suggest to identify the target drivers you want to improve from the original Blackstone 1.59 ROM, and then create cabs with the Topaz drivers and install them on top for a quick try. You may need to recmod some of them.
I have tried a few of them, but some are not compatible (E.G.: smarttouch)
Click to expand...
Click to collapse
That's probably the best approach. With 6.5 kernels, you can convert all of the oem drivers to modules (in my experience), and there will definitely be more modules among the drivers in 6.5 roms compared to 6.1 roms. If you want to test out some from a topaz rom, dump the rom and then recmod the ones you're interested in. I would just copy them into \windows with total commander or resco explorer, and over-write the rom module. Soft reset, and see how it works. You can do several at a time. For the hell of it once, I converted all of my oem driver dll's to files and then over-wrote the rom modules with the files to see how the device behaved. It worked ok (more virtual memory is used, though), and all of the files did load into ram properly.
I think this is what you are looking for.
> Blackstone-WM6.5-OEMXIPKernel.zip
Laurentius26 said:
I think this is what you are looking for.
> Blackstone-WM6.5-OEMXIPKernel.zip
Click to expand...
Click to collapse
Hi, thanks for the link but I already have that and thats what I am using in my Blackstone 6.5 ROMs. Its the OEMDrivers folder I want to update/replace with Topaz drivers that:
1. Work perfectly on the Blackstone
2. Are newer and written for WM 6.5
3. Offer better performance than the latest Blackstone 6.1 drivers
I have already re-moduled most of the 6.1 drivers however I can't see any performance increase with doing this - I think it is more memory efficient to have modules but since the drivers are essentially the same they perform the same
I have already asked in the Mikenificent thread as well as PM'ing Mikenf(?) and haven't heard anything so far...
Thanks, Andy
Half the fun of cooking is experimenting with the ingredients and settings. I suggest you just get the drivers and find out for yourself.
Topaz Drivers for testing on Blackstone
Hi,
I did a comparison of all drivers Blackstone 1.59 vs Topaz 2.53.
Attached you will find them, split by function (some of them unknown).
I'll be start doing some test myself using some in my next roms and advise
If you test and work, pls also advise.
Any new news here?
WBR
Siemens Lover

Categories

Resources