I would like to both find the following 2 fixes and cook them into my rom, but i cannot yet find the fixes - perhaps someone could be so kind as to help.
1. I do not want to see the 'could not connect' message - yes I have disabled both the connected and disconnected option but cannot find a way to remove that message. Really annoying when using TomTom.
2. When I tap the little keyboard at the bottom, to bring up the on screen keyboard, half the tme I accidentally get the input option menu I never use this and only want the standard keyboard - can I disable the option menu?
I have more questions, but am working through them as I think they are solvable by me with more time research.
Many thanks.
EDIT - See post 22 for likley solution to problem 1
crazyC said:
1. I do not want to see the 'could not connect' message - yes I have disabled both the connected and disconnected option but cannot find a way to remove that message. Really annoying when using TomTom.
2. When I tap the little keyboard at the bottom, to bring up the on screen keyboard, half the tme I accidentally get the input option menu I never use this and only want the standard keyboard - can I disable the option menu?
Click to expand...
Click to collapse
1. I don't know.
2. [HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ezsip]
"EnableSipMenu"=dword:00000000
Softreset...that's it.
Thanks, but I have tried that and it did not work. (I have gone back and checked that the reg edit was still there after the soft reset, and it was.)
TomTom breaking Manila
I still cannot answer my two initial questions, but have come across a strange issue.
I have tried to cook TomTom into my ROM to save time on the install. I have done this is the past with old style kitchens on previous phones no problem.
I have used the cab to ext converter in OsKitchen and made a package. If I inlcude the package in my ROM however, Manila will not start. Itr just syas tap here to start HTC Sense, and then flickers a bit but for love nor money I cannot make it start.
By a process of elimination I am sure it is the TomTom package causing this.
Running the cab via cab does not cause this issue.
Would anyone know what the problem might be?
Cheers
Don't use the cab converter to make the EXT. My guess is that the cab has a setup.dll, and the converter is missing something important. Here is how you want to make the package:
Install the cab; get all of the files created and put them in your package. Obviously, there will be files in \program files, but there may be some dumped into \windows, \my documents, the device root or \application data or \startup. There may be a new directory in \windows. Find those files and put them in the package as well; organize them however you want. Personally, I'd relocated the .exe and dll's and anything else I could into \windows, but I've never used tom-tom and don't know how it's organized or how it works.
Next, get all of the registry keys (after you register the program). I'm guessing that it's HKCU\software\tomtom or hklm\software\tomtom or something similar. There may also be other keys installed elsewhere (like clsid keys). Find those. If there's a setup.dll, you can open it with a text editor and probably see where they are. Some may appear in the _setup.xml. The best way to do this is to track changes with sk tracker, or do it the hard way and compare the registry before and after install with windiff (comparing full registry exports).
Once you have all the files and the reg keys, build the package. Clearly, the package builder is failing you, so I'd punt on it. Don't cook in the setup.dll, though (or anyting with a similar name, like tom-tomsetup.dll; sometimes there's more than one). Also, sometimes more complicated cabs will have zip files that install further during installation-open these up, look at them to make sure you have all the contents, then remove from the package.
Just a little add to Farmer Ted's excelent instruction.
I use wince cab manager to extract a cab, this will give you the registry plus the file locations.
This will give you something to compaire and helps you easier search what you are looking for.
The file locations you can create yourself in initflashfiles.dat or app.dat
To export a registry on device I use registry workshop.
With registry workshop you can export registry from your device straight to your pc.
If you are planning to realocate all the files to windows you need to edit the shortcuts to so they direct to windows and not program files for example.
The shortcuts you can open with a tekst editor.
Thanks guys - much appreciated.
The problem is that TomTom runs fine, its just that it screws up Manila. I will try and pull the cab to pieces as advised to make sure it is converting properly and also to see if I can spot anything that might impact Manila in the registry etc.
I dont suppose you have any thoughts on teh original two questions?
Not realy, but if the cab runs fine but your package isnt then there must be something wrong in the package isn't?
crazyC said:
I dont suppose you have any thoughts on teh original two questions?
Click to expand...
Click to collapse
There is actually not much in the cab.
Using Wince cab Manager I can see no setup.dll
There are also no reg entries - nor can I find anything in the reg on the device that does anything other than list the install directory.
Looking at th files it installs, there are a couple of bluetooth files that can cause an error - odly it seems to not affect me when it is a cab but it must overwrite the windows ones when it is cooked in. The only thing I can think of is that it also has a phone.dll that presumably overwrites the one in the sys.
I will try cooking without this in my next build and see.
Unfortunately I am out of time as have recooked/flashed almost ten times trying to tie down this issue and then getting back to a stable base.
I have also 'broken' Arkswitch which was working on earlier builds. Don't think its related though.
crazyC said:
Thanks guys - much appreciated.
The problem is that TomTom runs fine, its just that it screws up Manila. I will try and pull the cab to pieces as advised to make sure it is converting properly and also to see if I can spot anything that might impact Manila in the registry etc.
I dont suppose you have any thoughts on teh original two questions?
Click to expand...
Click to collapse
It's weird that it screws up manila; I don't use manila (or T-T, obviously), so can't help you there. I'm just guessing that you're missing a registry key that you need to get the package to work. Is there a tom-tom demo (not warez)? If you post a link, I'll take a look at the cab to see if I can make an ext from it, or figure out what's going on. Some cabs are just a *****, and you're better of doing a cab install. You should see the Redfly cab, it's sick, lol. It's one that has a zip file that does a secondary install. I hate it. I also hate Redfly, but that's another story.
I read somewhere that with some sip buttons, if you press the left half, it launches the keyboard, and if you press the right half, it launches the menu. I've never experienced it myself, and don't know which builds it affects or why it happens. Is this what's going on? I'm just guessing, since you say it eff's up half the time. I have no idea how to disable the connection message, but I wouldn't mind knowing how, either. It's annoying as crap.
What's your device memory left over?
I'm just thinking, maybe you could exclude TomTom from the taskmanager exclusive list.
Sorry one more idea, you are cooking for Rhodium right?
HD2 and Rhodium have a simulair bluetooth stack.
I remember on first HD2 roms there were some problems with TomTom and bluetooth on HD2.
Just a taught.
crazyC said:
There is actually not much in the cab.
Using Wince cab Manager I can see no setup.dll
There are also no reg entries - nor can I find anything in the reg on the device that does anything other than list the install directory.
Looking at th files it installs, there are a couple of bluetooth files that can cause an error - odly it seems to not affect me when it is a cab but it must overwrite the windows ones when it is cooked in. The only thing I can think of is that it also has a phone.dll that presumably overwrites the one in the sys.
I will try cooking without this in my next build and see.
Unfortunately I am out of time as have recooked/flashed almost ten times trying to tie down this issue and then getting back to a stable base.
I have also 'broken' Arkswitch which was working on earlier builds. Don't think its related though.
Click to expand...
Click to collapse
Thanks both for your continued help.
Yes I am cooking for the Rhodium and am using the Rhodium Manila plus Cookie 1.6.1 so as to keep memory use in check. Ok I have added in the 1.8 HTC messaging but it doesn't cause a problem. Memory is about 40% free on first boot - am also using 23568 as the SYS base. I also use Ameba.
I think my Arkswitch issue is due to something else cooked in, but being honest I dont really use Arkswitch much and so am going to drop it next time I cook I think.
Farmer Ted - There is no issue with TomTom as regards Warez as far as I know - the program is fine - it is the maps that must be purchased and talking about getting round that is where the problems arise. The program itself is OK.
I might get one last chance to cook and flash tonight to check out my theory about the Phone.dll. If not I will post back and throw myself on your mercy, although as you say, it might be better to just live with the fact it will be a cab install. due to the way the files interact and the fact that the tomtom package works, I do think something is being overwritten in the cooking process and all I can see is that file.
The reason I have persisted with TomTom is that I have made an old style OEM package in the past from the cab with no problems (long lost kitchen).
With regards to the Bluetooth issues - I have sorted those now AFAIK.
RESULT! re TomTom - will post back after putting my little girl to bed.
OK - to summarise.
I ran TomTom through the cab importer within OsKitchen and it produced a package.
Although the cab had installed and run with no errors, cooking it in created 2 errors.
Firstly, there was a bluetooth message about bttray or something not being a valid application.
This is caused by two BT files in windows being overwritten by the TomTom ones. Simply renaming the two fiels to include the word OLD in the name sorted that. I will just remove them next time as I do not think they are necessary if the windows files are there.
The second issue was that Manila would not start. I believe this is due to a similar issue to the above, in that phone.dll was being overwritten. I renamed the file to PhoneOLD.dll and cooked in the package and now Manila starts.....
Still looking for answers to my first two questions though
(and yes its cos I keep hittingt he side of the button with my fat fingers that the keyboard selector comes up)
I'm not sure what's up with the keyboard, although I use Resco, so maybe you don't get then menu popup when you hit the wrong half. Have you tried killing SIPGT_app.exe? Maybe it won't pop up with that killed. If that's the case, then remove the bootlauncher key in your ezinput package. Killing it may not help, though.
I could not find that exe file to kill. The keyboard behavious is I believe as it is intended to work - just not how I want it. But are you saying Resco Keyboard fixes this?
However my final reflash last night seems to have gone a bit nuts. I am now getting all sorts of problems with apps not being able to run because they are unsigned etc or bits missing.
We are talking about stuff cooked in that has previously worked flawlessly.
Had some issues with my PC last night as well. I think I need to go back a step when I get home tonight and maybe rebuild the kitchen.
Time and kitchens have moved on a little, but as things are going well, I am back to my original 2 questions that continue to perplex me:
1. Is there a way of stopping the 'cannot connect' bubble from coming up, or even to make it automatically close after say a few seconds.
2. Is there a way of stopping the keyboard selector menu from popping up when the side of the keyboard icon is hit. I just want the qwerty option and do not want the menu to come up ever.
I have been able to make no headway at all with (1), - found mention of one cab somewhere but the link had expired - and have tried various things for (2) but with no success yet.
Anyone?
Cheers
PS- to follow up my previous posts yes the fixes I mentioned for Tom Tom work fine - it was the 3 files causing the issues.
In my old Kaiser roms i used the below reg key to disable connect notification,sorry i really dont remember if it disable also"cannot connect".
Code:
[HKEY_CURRENT_USER\ControlPanel\Notifications\{8ddf46e7-56ed-4750-9e58-afc6ce486d03}]
"Options"=dword:00000000
Disable Sip Menù is the same reg key that another guy posted here:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\ezsip]
"EnableSipMenu"=dword:00000000
I tried it on my HD2 before posting here and setting it to 0 it leave the menù where you can select keypad,compact qwerty,full qwerty and language,it is still present a little menù with the option and my guess is that this isnt removable.
crazyC said:
Time and kitchens have moved on a little, but as things are going well, I am back to my original 2 questions that continue to perplex me:
1. Is there a way of stopping the 'cannot connect' bubble from coming up, or even to make it automatically close after say a few seconds.
2. Is there a way of stopping the keyboard selector menu from popping up when the side of the keyboard icon is hit. I just want the qwerty option and do not want the menu to come up ever.
I have been able to make no headway at all with (1), - found mention of one cab somewhere but the link had expired - and have tried various things for (2) but with no success yet.
Anyone?
Cheers
PS- to follow up my previous posts yes the fixes I mentioned for Tom Tom work fine - it was the 3 files causing the issues.
Click to expand...
Click to collapse
Cheers for that - I am concluding that the SIP issue I wil live with, and I already have that reg key set to zero for the connections issue, to no avail. I am experimenting with some other keys, but its really shooting in that dark, and as I cannot readily reporduce the notification, it will be a few days before I can even see any change.
Oh well. I will update if I get anywhere.
Ooooohhh, following some more digging, I MAY have an answer re the cannot connect bubble. I saw someone elses solution and that has actually led me to what could be far simpler.
I will try and cab it up later tonight for other to try. It is just a reg entry
EDIT - maybe I spoke too soon.
I am testing this by alternating between 3G and 2G on the comm manager - normally this will pull up the message. (Could someone confirm this as a valid test method).
I thought I had it solved, then the message appeared, but have done it another ten times with no hint of the message.
Some more testing to do......
Related
Has anyone come up with a fix so that the GPRS is back to being always on as it was in the original 1.03 ROM? I have read some posts on this on other sites, but I have not found anything here. I assume that I have everything set properly, but the GPRS has to be started every time now.
In general I do not feel that the 1.06 ROM upgrade did much of anything to enhance my device, and quite frankly I wish I was back to 1.03, however, I have heard that a new ROM upgrade will soon be released and I bet that one or I hope that one will provide some real value and fix things.
I've posted this in another thread, here's the quote:
Here's a solution I've done to my XDA II with T-Mobile GPRS problem. I don't know who came up with this solution, but thanks to my friend who suggested this at PDAMobiz.com.
1. After a hardreset and completing the initial screen alignment, interrupt the auto-installation process by softreset your XDA II (you have 3 seconds before the files in Extended_ROM will automatically install).
2. Make your Extended_ROM viewable, whether by using the Extended ROM Viewer from http://www.ppcw.net or Extended ROM Switcher (sorry I forgot the link).
3. Now, install each cab files, except TMD_AP_NL.sa.CAB. In fact, I also disregarded, Caller ID, and some other TMD stuff.
As a result, the GPRS is now always-on as it should be.
Cheers,
Thank you for responding to this post. I had to wait quite awhile.
Your #3. states to install the cab files and disregard the TMD files. Did you delete these files or just not open them? What are these TMD Files for?
I assume that I cannot, at this point and without a hard reset, just delete the TMD Files that are viewable in my Extended Rom. Is this a correct assumption or could I accomplish the same goal by just deleting those files?
Thank You
gratefuled said:
Thank you for responding to this post. I had to wait quite awhile.
Your #3. states to install the cab files and disregard the TMD files. Did you delete these files or just not open them? What are these TMD Files for?
I assume that I cannot, at this point and without a hard reset, just delete the TMD Files that are viewable in my Extended Rom. Is this a correct assumption or could I accomplish the same goal by just deleting those files?
Thank You
Click to expand...
Click to collapse
Yes you need to delete does file from Extended_ROM and hard reset it.
Or hard reset, quickly soft reset after you finish the screen calibration, run the extended_rom viewer and manually open/run each of the cab files except the mention cab. ( basically follow exactly what jopard said ).
I read also somewhere in this forum that someone did a differrence search on the registry between GPRS always on and GPRS off when idle. With this method you can change the setting without hard reset.
Hi, the mentioned cab installs the following registry key (among others):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConnMgr\Planner\Settings]
"CacheTime"=dword:0000003c
"SuspendResume"=hex(7):\
69,6e,74,65,72,6e,65,74,00,00,00,00
I guess it must be the SuspendResume setting. Can you post your setting without applying the cab file?
softworkz said:
Hi, the mentioned cab installs the following registry key (among others):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConnMgr\Planner\Settings]
"CacheTime"=dword:0000003c
"SuspendResume"=hex(7):\
69,6e,74,65,72,6e,65,74,00,00,00,00
I guess it must be the SuspendResume setting. Can you post your setting without applying the cab file?
Click to expand...
Click to collapse
This is my setting running my own cook 1.60.06 skiping that file:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConnMgr\Planner\Settings]
"SuspendResume"=hex(7):7E,00,47,00,50,00,52,00,53,00,21,00,00,00,00,00,00,00,00,00
"CacheTime"=dword:00000258
And yes my GPRS is always on.
Hm, I'll try that, but I had another problem:
When I was always GPRS-connected my GSM-connection was always lost
after 12-24h. The device showed that it is connected but I could not dial out and I could not be called.
Now since I am not "always on" anymore I do not have this problem anymore.
Did you experience something similar?
softworkz said:
Hm, I'll try that, but I had another problem:
When I was always GPRS-connected my GSM-connection was always lost
after 12-24h. The device showed that it is connected but I could not dial out and I could not be called.
Now since I am not "always on" anymore I do not have this problem anymore.
Did you experience something similar?
Click to expand...
Click to collapse
Mine work fine I can call, received phone/sms while npop and aim is running in the background.
is there
Is there a way to do this without hardrestting? It just took me two hours to load all the program into XDA. Can I just hack the reg?
thanks
my rom
My rom does not even have this cab in the ext file. Can I hack it in the reg?
I have XDA II 1.50WWE ROM
thanks
softworkz said:
Hm, I'll try that, but I had another problem:
When I was always GPRS-connected my GSM-connection was always lost
after 12-24h. The device showed that it is connected but I could not dial out and I could not be called.
Now since I am not "always on" anymore I do not have this problem anymore.
Did you experience something similar?
Click to expand...
Click to collapse
I think you will find that many carriers have a "timeout" after several hours of non use.
Dave
SuspendResume
What does this look like in the registry:
This is my setting running my own cook 1.60.06 skiping that file:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ConnMgr\Planner\Settings]
"SuspendResume"=hex(7):7E,00,47,00,50,00,52,00,53,00,21,00,00,00,00,00,00,00,00,00
I have PHM Registry Editor, and entering the entire string does not look like a meaningful option.
Is it a REG_DWORD with a base of HEX ?
Regards
Michael
I use resco registry editor you can just import in that registry.
I found another post regarding this issue:
http://forum.xda-developers.com/viewtopic.php?p=26866
I'm afraid I do not understand how this thread has evolved.
I understand the posts that speak to the hard reset and softreset within 3 seconds to keep the device ROM applications from loading. From there to install fix for viewing extended ROM files and then load everything except TMD, and perhaps some of the T-Mobile apps you do not want. Although the response says a specific TMD file and some other TMD-no specifics, all or some?
The balance of the thread seems to speak to radio settings.
Is it being said that you can change some settings on the radio stack and get the GPRS always on? If so how do you do this in reasonably simple terms?
Ed
Nonintrusive Keep-Alive
The intrusive solutions are enticing to me but they are for "developers". From a user's point of view, I am always worried about doing something and then not being able to restore it to the original state (or having to spend a lot of time to get back) should something go wrong. My bandage solution (unique to my use situation) is to open an ssh or a telnet window and run a shell script which loops to print the current timestamp and then sleeps for 5 seconds. A T-Mobile tier 2 tech guy told me that the disconnection was by design for the benefit of network service providers so that they can save on connection resources.
By the same token, I like the Keep-Alive application solution - I think it is worth my $2.45 (See thread http://forum.xda-developers.com/viewtopic.php?t=5220). I wonder if the to-come T-Mobile Windows PPC 2003 comes with some sort of control that is equivalent to the Keep-Alive application - in a matter of a month or two, supposedly.
Here is a wait animation package for WM6 with 10 cursors and an install mortscript. Same animations used by Juryduty for his WM2003 cursors. I have 25 of these I've done, this package only contains 10 because they're kinda big.
EnJoy!
Nice! Thanks!
Will this work on WM5? is there a possibility to let this work or a same programm for WM5? please tell me..
Thank you! very nice!
didnt work well on my mogul. wouldn't uninstall, had to hard reset.
for WM5 try here:
http://forum.xda-developers.com/showthread.php?t=317476
this script will probably work for them, but you'd have to edit it if the resource name is different , and rename them 'filename.wait' then zip them to wait.zip.
the resource name for WM6 is 'shellres.96.dll' you'd have to find out about WM5 and make the corresponding changes in the script 'waitskins.mscr'.
As far as having to hard reset, did you mean soft reset? This sometimes happens to me randomly after installing a cab and can happen with any cab. I don't think it has anything to do with the cab, but more to do with the state of your device when you install it.
At any rate all this cab does is copy some files to 'programs\waitskins' (or 'storage card\programs\waitskins')and 2 shortcuts to windows\start menu\programs.
The script uses Mortscript4.01b12. It unzips the skins, copies the selected one, deletes the unzipped files, and tells you to do a soft reset. Thats it. Hardly anything to worry about.
it didnt work well with my very top bar in my today screen. after i installed the cab my clock, speaker icon, and signal icon were messed up. i couldnt change the icon back to the origanal wm6 after i changed it to one of the 10 you provided. after that i uninstalled and it wouldnt go back to the wm6 icon. i finally HARD reset my phone and had a fresh backup from earlier that day. no biggie, i may have installed wrong. i would like to get this to work, i may try again. thanx tho, Jody
The icons problem happens when the file hasn't been signed. I've signed all these and they work on my COOKED WM6 device. maybe your device doesn't like the certificate I used. I really don't know for sure.
When this happens you should be able to run the waitskins program, select CANCEL and this will delete any skins on your system, then a soft reset will get you back to the default thats built into your rom. then an uninstall.
Sorry about your hard reset...but since you just barely did it you might want to test this again and find out if the problem is with ALL of the skins, and weather or not the above tip saves you from another hard reset.
thanks for the feedback and if you test this any further please let me know what you find out.
Joeman
work for me (wizard wm6), but I can't change back to the original one , the cancel just change the cursor to the latest one.
It will be good if you attached more skin here.included the original one.
thank
thanks nice one
I would like to complain because I am an a$$. But I cannot, these are a great choice of icons. Anyone with WM6 aught to give it a try.
Great work!
Finally I tried these awhile back but would not work!! They are awesome! Thank you!
I found the original cursor here.
http://forum.xda-developers.com/showpost.php?p=1451996&postcount=37
& try to change name to "original.wait" then add to zip. after running it's work ,but have error at the top bar icon as oakwestplayer comment.
any comment
nice cursors, thanks
bit off topic, but that m & m dance looks more like "Cool Spot" to me
anyone remember the old megadrive/genesis game.
http://en.wikipedia.org/wiki/Cool_Spot
ong9:
Looks like the file needs to be signed.
Look for a tool in this forum called "multiple file signer' and use it to try to sign the file.
http://forum.xda-developers.com/showthread.php?t=306982&highlight=multiple+file+signer
If the file signing failed then try to find the 'file Unsigner', and unsign it then sign it again.
http://forum.xda-developers.com/showthread.php?t=329160
This has worked for me.
The multiple file signer lets you choose from 3 different certificates, if one doesn't work try the other two.
If this doesn't work for you then I don't know what to tell you.
Good luck!
Joe
BTW Funy yes that IS cool spot, (LOL) I didn't even notice the .GIF name but in the package I've called him COOL SPOT! Guess that's why I've seen that animation with the color changed (green blue etc.). I don't even think it looks like the M&Ms (must be the sunglasses), that's probably why I didn't make the connection. Good eye!
This is not a program, but just registry settings to use the built-in biotouch.exe to call Manila Control in order to toggle between M2D and Today.
Notes:
must install Manila Control to \Windows\ before the attached .cab
the cube no longer works after installing this, but the corresponding processes (i.e. QuickDial.exe, MediaHubMini.exe and APLauncher.exe.exe) may still in your memory unless you replace the .exe by dummy programs or kill the processes.
must backup the original [HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\Biotouch] before installing the attached cube, otherwise won't be able to restore the cube.
toggling M2D/Today using softkeys as shown in the demo video is NOT set by the attached .cab
Demo video:
http://hk.youtube.com/watch?v=3fGNWYI2fkA
download:
for Nike, Polaris and Vogue, pls refer to attachments of this post.
for Elf, pls see the one provided by dark.angel at post #13
Good idea, I'll try on HD when I'll have it, I hope monday.
Thank you
great idea. Although I've still yet to find a use for a second today screen. lol
is there going to be a version of this for the vogue? it seems neat but im not ballsy enough to install something not meant for my device quite yet.
lazyboy0172 said:
is there going to be a version of this for the vogue? it seems neat but im not ballsy enough to install something not meant for my device quite yet.
Click to expand...
Click to collapse
Vogue uses different registry settings. please try the newly added cap in post #1. pls be prepared for bug-fixing time because i can't test it on my own. for safe, pls do a backup, especially the [HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\Biotouch] registry key, before installing.
good luck.
davideuck said:
Good idea, I'll try on HD when I'll have it, I hope monday.
Thank you
Click to expand...
Click to collapse
surely none of the 3 uploaded version would fit the vga devices.
if you want a try, i guess the Polaris version can be a good start. pls be prepare for the pull-up screen being in 1/4 size.
pls do let me know the testing result and see whether i can find a way to fix it. if it doesn't work at all, pls kindly let me know the following registry key values on your device:
[HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\Biotouch]
"App1"
"Cube1"
"Path11"
thanks for your interest.
thx!! its very fine!
to pp18 with a simple question..
PP18!!
please let me know before i make some serious mistake with my HTC touch 3G jade..Is it working on it as well?Or your program is connected only to the above mentioned phones?I needed exactly the program tweeks u wrote.It should be fantastic,but I have this conserne..
Please let me know if I can tweek my 3G jade without fear..?!
by the way,thank you for the nice app you wrote..HELIOS
Great find,. thanks for sharing,,.
pp18 said:
This is not a program, but just registry settings to use the built-in biotouch.exe to call Manila Control in order to toggle between M2D and Today.
Notes:
must install Manila Control to \Windows\ before the attached .cab
the cube no longer works after installing this, but the corresponding processes (i.e. QuickDial.exe, MediaHubMini.exe and APLauncher.exe.exe) may still in your memory unless you replace the .exe by dummy programs or kill the processes.
must backup the original [HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\Biotouch] before installing the attached cube, otherwise won't be able to restore the cube.
toggling M2D/Today using softkeys as shown in the demo video is NOT set by the attached .cab
Demo video:
http://hk.youtube.com/watch?v=3fGNWYI2fkA
Click to expand...
Click to collapse
Is it possible to use this on HTC Touch (Elf)?
And also I would like to change running program from ManilaControl to any other, for example CommManager.
I've installed reg settings from the Vogue cab (is it right?), and copied original Biotouch.exe and dummy APLauncher.exe, MediaHubMini.exe and QuickDial.exe to the windows dir, created shortcut for biotouch.exe in the windows/startup folder and Soft-reseted my device.
Now when I make touch gesture the screen appears into black and nothing happens.
Is it possible using registry settings to bind touch gesture to run any exe (for example, commmanager.exe)?
Thank you for answers!
heliosismagic said:
PP18!!
please let me know before i make some serious mistake with my HTC touch 3G jade..Is it working on it as well?Or your program is connected only to the above mentioned phones?I needed exactly the program tweeks u wrote.It should be fantastic,but I have this conserne..
Please let me know if I can tweek my 3G jade without fear..?!
by the way,thank you for the nice app you wrote..HELIOS
Click to expand...
Click to collapse
sorry i really can't answer your question because i haven't played around with a Jade before and I don't have any friends who have bought one. the main prob is, i don't know the version no. of biotouch shipped with Jade.
if you really want a try,
do a full backup (so that you can hard reset + restore in worst case)
backup/export the [HKEY_LOCAL_MACHINE\Software\HTC\Biotouch] registry subtree
try the Polaris version
good luck
dark.angel said:
Is it possible to use this on HTC Touch (Elf)?
And also I would like to change running program from ManilaControl to any other, for example CommManager.
I've installed reg settings from the Vogue cab (is it right?), and copied original Biotouch.exe and dummy APLauncher.exe, MediaHubMini.exe and QuickDial.exe to the windows dir, created shortcut for biotouch.exe in the windows/startup folder and Soft-reseted my device.
Click to expand...
Click to collapse
Elf's built-in biotouch version is different from Vogue's. pls find the Vogue's version, which should appear in those threads about installing 4-sided cube on Elf
Now when I make touch gesture the screen appears into black and nothing happens.
Is it possible using registry settings to bind touch gesture to run any exe (for example, commmanager.exe)?
Thank you for answers!
Click to expand...
Click to collapse
basically yes. the trick is in the "App1" reg key. if the app being called has a visible window and you want to use the swipe-down gesture to hide it (like the original cube), the first part of the key value must be the right class name. otherwise, like the case for Manila Control, simply use a non-exist class name.
I've duplicated my commanager.exe and mui files and renamed them to biotouch.exe and biotouch.exe.mui, so now after the touch gesture commanager is running. It works!
Here is the test cab file, i haven't tested it on a clean device, but it seems to be work. If it doesn't working, post here please.
added a link to the Elf's version by dark.angel to post #1
snoopy
Hey, Love the snoopy. Is there anyway to take it off however? I't just doesnt go well with my today screen?
KH2GR said:
Hey, Love the snoopy. Is there anyway to take it off however? I't just doesnt go well with my today screen?
Click to expand...
Click to collapse
though not totally take if off, but editing the registry keys as below can minimize its appearance:
[HKEY_LOCAL_MACHINE\Software\HTC\Biotouch\Biotouch]
"TotalBMP"=dword:00000001
"Cube1"=hex:07,01,01,01,01,01,01,01,0A,C8,C9,CA,CB ,01,01,01,01,01,01
"UpFPS"=dword:0000FFFF
if you want to further cut down the size of the snoopy image that may appear for a short time, you can also change the below key:
(for Nike and Polaris) "Path1"="mc01.brn"
(for Vogue) "Path1"="\Windows\mc01.brn"
Is it possible to call manilla from any program with this gesture fix?
I mean the way I call and close cube by just scrolling tumb up or down.
TRY AT OWN RISK!!!! I CAN NOT BE HELD RESPONSIBLE FOR ANY PROBLEMS, LOSS OF DATA, ETC!
*EDIT*
For now I just created a Mortscript file doing all these operations. Place it in a folder with the files from the zip in the first post (the following):
1de372cc_manila
3fee37f0_manila
24DBB12A_manila
57a92846_manila
64c98668_manila
247c62d4_manila
345f892c_manila
486d3b1a_manila
0828aea6_manila
3633be96_manila
People_Pages.xml
I commented out some stuff, please check the file for comments. Some registry settings I don't change myself, you can enable them by removing the brackets (#) in front of the corresponding lines.
Use at own risk of course (Mortscript is needed for this...)
*EDIT*
ORIGINAL POST:
Well, because I hated the 2.5 messaging and didn't like the fix of disabling it and going back to windows classic messaging (not being able to tap the sms in the message tab and all) I decided to just give the following a try:
http://forum.xda-developers.com/showthread.php?p=5202063#post5202063
For information, using the Topix 0.2 rom at the moment!
What I did was the following:
0. Download the archive file
http://manilavga.googlecode.com/svn...nse_amarullzNoMessagingClient_2.0.0-BETA2.zip
1. Disable sense (Disable it in the today settings)
2. Make a backup of all the files you are going to replace, just in case These are the files in the archive above.
3. Rename/delete the ManilaFull.xml in the windows dir (mentioned in that thread as well).
4. Copy the manilla and xml files from the .zip to the windows folder (in the zip there are a few manila files in subfolders, these are language files it seems and I just put them all in the windows dir, so not in the subfolder).
The PeoplesPages.xml I also copied to the ManillaXML folder in the windows folder.
4b. Extra step! Copy the file found in this post: http://forum.xda-developers.com/showpost.php?p=5203019&postcount=1308
Into the windows folder as well, overwriting the other manila file. This fixes a double-tap not opening the message bug...
5. Enable sense again
6. Restart
7. Add rotation to it using BSB Tweaks
(8). I had the HTC messaging disabler cab installed and uninstalled it afterwards...
I think this was all...
Apart from some expected (it was made for VGA afterall) graphical issues (mainly in landscape mode) it actually seems to work fine!
The messages are divided over different pages now, no lag when loading, etc...
Just tried it now so I might find more issues soon but thought I'd mention it at least in case brave souls want to give it a try
Again, try at own risk!!! Haven't been able to test it extensively!
Any chance of some screenshots? The graphical VGA issues are holding me back from trying it...
Sure
Uploaded a portrait and landscape pic, just when the keyboard is displayed there is some overlap on the top. Nothing really bad though... Hope this helps, I'll see if there's something else I can make a screenshot of. But now, first dinner
Seems to work OK for me too Using Balaji 1.1 rom on Blackstone (HD), WM 6.5.x and Leo 2.01 based. Haven't tried landscape (I don't use it) but portrait seems to work fine. Only slight irritation is keyboard doesn't pop up on reply until you tap the text entry area. Much quicker than the laggy 2.5 messaging client
BTW I used the files from 0409 folder only, which I believe is English language. Well I'm English, and it worked anyway...
millski said:
Seems to work OK for me too Using Balaji 1.1 rom on Blackstone (HD), WM 6.5.x and Leo 2.01 based. Haven't tried landscape (I don't use it) but portrait seems to work fine. Only slight irritation is keyboard doesn't pop up on reply until you tap the text entry area. Much quicker than the laggy 2.5 messaging client
Click to expand...
Click to collapse
Good to hear!
Don't know if the keyboard thing was different with the original software? But still, atleast a fast messaging app
Just tried this on my TP2.
Works GREAT thanks!!!
is there an eaiser way to do it? lol
It works for me! Thanks dagrim1.
Not perfectly, though. Clicking on the send message link in the contact card will restart Sense, and the same will happen if I choose the messaging tab inside the contact card.
Using the 1.61 Turkish ROM (will switch to EnergyROM soon).
It should be possible to do it through a cab file. Anyone up for it?
working for me on the topaz.
The overlap bug is more acceptable than the lagging message, thank you
Hmmm, some possible bugs?
1. Capitalize letter when starting a new sentence doesn't work? Maybe it's the rom though, heh...
2. When sending a message I don't see the contact but just the phone nr as the recipient. Clicking the msg DOES open the contacts tab (and goes to msg tab) but then the msg isn't listed there...
Still trying to find out an easier way to do all this as well.
One more bug: clicking on "menu" doesn't show anything.
NSider said:
One more bug: clicking on "menu" doesn't show anything.
Click to expand...
Click to collapse
Hmmm, does with me... You mean after opening a msg? In the msg-tab from the people/contacts tab so to say?
Doesn't seem to work for me. Though I use Leo's Dutch version and the Dutch country code isn't included in the files. Anybody knowing a solution?
Or you need to do anything with the app.reg and _skip?
Hmmm, does with me... You mean after opening a msg? In the msg-tab from the people/contacts tab so to say?
Click to expand...
Click to collapse
Yes. I see a flicker on the screen, but nothing pops up.
Anyone up for making a CAB?
I can't seem to change things in my windows folder, even though SENSE is off.
For anyone curious, this will not fix the SMS sending message problem.
Michiel0211 said:
Anyone up for making a CAB?
I can't seem to change things in my windows folder, even though SENSE is off.
Click to expand...
Click to collapse
by change do you mean copy files? as i get a message saying i dont have permission when using activesync and i get
cannot copy '345f892c_manila': access is denied
agent.m said:
by change do you mean copy files? as i get a message saying i dont have permission when using activesync and i get
cannot copy '345f892c_manila': access is denied
Click to expand...
Click to collapse
Exactly the same thing.
Acces denied. How do we circumvent this?
much faster sms but now seem to have the message sending bug on 1.61
any fix`/
For all who have problems to copy files into windows folder.
Grtz,
Degake
EDIT:
I added separate cab files with tweaks founded in the original downloadpackage.
There are 2 folders: 1 for GSM and 1 for CDMA devices.
tweaks contained are: - max. sms shown upgraded
- different font sizes (going from 0 to 8)
Hello guys,
I have a strange problem.
I mod Jackos Rhodium ROMs (under his permission and valuable help) translating them to Polish, but I still continue to have one issue after my modifications.
Apparently my problem occurs only on WM6.5.x ROMs (currently on 21690, but before that Jackos used 28236 and the problem was there as well).
And the problem is that after some time since last SR the dialer just stops appearing after I press the "Send" button (or clicking the "Phone" link in Start Menu). After I make a SR, everything is fine for some time (sometimes 1h, sometimes 2-3 days) and out of a sudden I have to call someone and I press the Send key to bring up the dialer and... nothing happens. Sometimes only a SIP icon appears in the middle of the bottom homescreen softkeybar.
My modification is quite simple. I dump Jackos' ROMs using PRB mini kitchen which I got from Jackos (to flat dump form), exchange all the language files (mui, htm, txt) with Polish equivalents and recook the ROM adding 2 cabs to the config.txt which are used only to change some reg entries. Then I recook the ROM using the kitchen.
I reviewed all the mui files and all the reg changes and everything seems to be fine. Well, the ROM eventually works fine except for the dialer/phone canvas/SIP problem.
If you don't know what the problem is perhaps some of you can give me some advice where should I look?
I search the xda and other forums for few days and haven't bumped on any working solution...
Sorry for bumping, but I'm getting to nowhere...
I downloaded Jackos's full custom kitchen and spent 5 nights to adjust it for making 0415 ROM. I had to change many of the .mui files and hundreds of .reg, .rgu, provxml files. I decided to build all the polish packages from scratch to avoid any errors. And finally I built the ROM and besides problems with start menu structure it generally works fine. The memory management seems to be as good as original Jackos WWE ROMs (I didn't change anything in the base rom, only separated 0409 files from the packages and added 0415 packages).
But guess what! My dialer problem is baaaack...
After a SR the Sendkey works fine, but after a few phone calls it just doesn't bring the dialer/phone canvas to the front. The button itself is ok, because longpress works fine. And when I press the sendkey the light also goes on.
And the phone canvas is OK as well, because when I slide-open the keyboard and put any letter from the HQWERTY, the dialer appears immediately.
Furthermore I can now return to portrait closing the keyboard and do all the things I usually do with the dialer (put names, numbers, etc.)
Pleeeease help a poor cooking begginer because I have run out of ideas...
Stop crying and start debugging?
Use one of the tools to see the dependents of PhoneCanVas. I also suggest that you exclude all of your registry tweaks.
I'm crying 'cause I slept 2-3 hours per day since Sunday because if this @#$#%[email protected]%$
Just noticed one more thing. When the problem with the dialer happens it affect also Sense message notifications. I just received a text message and there is no "green dot" on the Sense slider nor on the notification bar. Only an SMS symbol on the taskbar.
After SR it's all good... for now...
Debugging... What tools you mean? I never played with no tools that can check the dependancy between packages...
Use the DependencyInspector by ultrashot. It's really easy to use.
Either I'm too stupid to use it or it shows nothing for PhoneCanvasEnhancement. I moved language folders in this package to the OEM way as I read this tool is for OSBuilder only, but still no effect...
Skrobel said:
Either I'm too stupid to use it or it shows nothing for PhoneCanvasEnhancement. I moved language folders in this package to the OEM way as I read this tool is for OSBuilder only, but still no effect...
Click to expand...
Click to collapse
It's designed to work with OEM packages and you're inspecting a EXT package. Try harder.
Well, the folder structure is like in the OEM package. What else should it need? a dsm? I could install OSBuilder and force it to build a dsm file for the package, but if the libraries have any dependances they should be detected by the DependencyInspector just like by the OSBuilder when building .dsm, shouldn't they?
Skrobel said:
Well, the folder structure is like in the OEM package. What else should it need? a dsm? I could install OSBuilder and force it to build a dsm file for the package, but if the libraries have any dependances they should be detected by the DependencyInspector just like by the OSBuilder when building .dsm, shouldn't they?
Click to expand...
Click to collapse
Choose what you want to inspect. You can do better than that.
Well I'm afraid I don't get you... again...
I'm trying to inspect a package. As far as I tested on other packages (in the OEM folder) the app tests all the dlls and muis it can find. And testing a kitchen doesn't make any sense with this structure and only EXT packages, does it?
Does the attached picture help you by any chance?
Heh... I should've known you never give straight answers, but you make people think. Let me dig some more...
Well... not much findings anyway.
I have changed 3 .mui files (commctrl.dll.0415.mui, shellres.dll.0415.mui, phcanhtc.dll.0415.mui). They seemed OK by the resources, but all of them have some code inside as well. Perhaps this will help.
Havent found anything in the registry. But I'm just groping as I don't know where to pay attention. The error occures usually during normal use, I couldn't find any rule when it actually happens to be able to reproduce it later on.
Either way I now use another test ROM. We'll see...
Good luck, mate.
Ehhh... still nothing. I haven't found any solution among the dependancies...
I even had a case when my dialer wouldn't have showed up right after flash (with no customisation).
But there's one additional matter. It's only the Send Key which could not trigger the phone canvas to show. When I clicked the PHONE shortcut from left softkey it showed up without problems. But the long press worked.
I started to search around for an information of the hard keys driver. But no breakthrough as well. I run out of ideas here...
Additionally I have another Rhodium (I've bought Jackos' one) and the problem is there also. So now I'm sure it's "my" PLK ROM problem, not a broken MoBo or anything else.