Hey,
I wanted to know if anyone knows how to convert the Kaiser cabs to a more appropriate CDMA version. I have no experience in them, so I have no idea where even to begin. I am hoping someone here knows how, and would be kind enough to change them. A few guys on another website are tweaking the original Touch Dialer, which worked well on gsm phones, but had tons of bugs with CDMA (including enabling data, memory leaks, and disabling ## codes). If anyone can do anything, I would really appreciate it.
Thanks!
The following from the Kaiser is OK to use, I'm running them and can vouce:
Audio Manager
BT Quicklink
Comm Manager
Home Plug-In
You can also run the new X-Button v1.5.1 Build 30229 and I'm running the Beta CDMA HTC Touch dialer from PDAphoneHome too: http://pdaphonehome.com/forums/638252-post57.html
Note that the Voice Recorder and the Network Wizard do NOT apply and do NOT work on our phones.
ViPaDawG said:
Hey,
I wanted to know if anyone knows how to convert the Kaiser cabs to a more appropriate CDMA version. I have no experience in them, so I have no idea where even to begin. I am hoping someone here knows how, and would be kind enough to change them. A few guys on another website are tweaking the original Touch Dialer, which worked well on gsm phones, but had tons of bugs with CDMA (including enabling data, memory leaks, and disabling ## codes). If anyone can do anything, I would really appreciate it.
Thanks!
Click to expand...
Click to collapse
You can dl the cab for the Kaiser Home plugin and it just works. Same goes for Comm Manager and the rest that he mentioned. So in short, you don't have to convert them at all.
The thing to be careful with is with things like the older version of the dialer/network wizard/etc where we KNOW that they don't work. But once the devs update them (like the dialer has been) you should be ok without need for conversions.
yeah, i've been using the 5 tab home from the kaiser, and the touch comm manager, but that's about it. i heard that even the comm manager has some stuff that conflicts with CDMA, which is why i was wondering. I'm also using the beta touch dialer from paul_hammons, and that works great, and i absolutely love it, but I was just wondering about the other stuff, and when/if it will be converted.
Well you can use the audio today plugin and the audio app too AFAIK
Related
A few questions hopefully some of you vets can answer:
First, I have the Alltel version of the HTC Touch. When I click on Device Info the model number is: VOGU100.
So am I in the correct forum?
Questions:
1. Just downloaded Audio Manager, how do I make it my default player instead of Windows Media Player. When I use the cube, I want it to default to Audio Manager
2. How do you send attachments in Text. When I click, the "Insert" is grayed out.
3. I see that there is a GPS Icon. Is this thing GPS capable? Do I just contact Alltel for the service?
Thanks!
yes ur in the right place.
1. not quite sure how to do that. i use the manilla 2d, and in the music tab it uses audio manager by default.
2. most of the time u will have to send attachments in email. or u can use the search in the forum. its been talked about in a few places. its a smms cab file.
3. for gps, i upgraded to winmo 6.1, and it is included there. hope that helped enough.
im pretty new myself, and hate when ppl dont reply. jus figuring things out 1 step at a time.
I'll have to check out that manilla 2d. I updated my Rom to the 6.1 version this morning.
So I'm making progress. Thanks again.
vogue
the vogue or xv6900 is the htc touch. you can modify the cube using this tool from ppcgeeks. It works on the verizon touch also.
http://forum.ppcgeeks.com/showthread.php?t=12746
manila 2d is what i call a theme. i am not sure if that is the correct term for it. there are a bunch of these out there that you can try some for free some trial then pay. sbmobile shell is a nice one. pointui is another, touchcommander is another (one i am currently playing with), manila 2d is another, iphonz is another. do a google search and you will find the cabs for these. the manila 2d i used was difficult to remove so i did a hard reset to remove it. sb, pointui, iphonz were easy to remove. iphonz takes alot of work to set up.
also you can get skins and set up these themes to operate differently. i like robodads sbmobile shell theme that i think came from this site. it is really nice. have fun.
Can you tell me what I'm doing wrong with trying to play youtube vids?
I downloaded TCPMP and a Flash file, but I keep getting this error:
crash.txt
error
I just can't seem to find a fix. Do I have a old version of TCPMP? TCPMP will not open at all, it gives the crash.txt.
Thanks,
Eric
Hi I uploaded a working cab for Name Display for Rogers and Fido subscribers.
I used the rilphone.dll from the new Rogers roms released. The corresponding radio is 1.14.25.55.
It should work for most custom and stock roms. The only problem I found was it doesn't show in the dialer for the new touchflo 3D roms but does show the name in the call log.
For people who don't know, Name Display is a feature in Canada that allows the name of the person to show on your screen even if they are not listed in your phonebook. Please keep in mind you have to subscribed to this feature.
I've never made a cab or anything like this before. I did it with alot of searching on xda and google. Luckily most of the work was already done by the guys over at the raphael and diamond forums. So thanks alot to them.
So try out the cab!
Make sure you install SDCERTS first!!!!!
Hi sundeep,
I installed your CAB file on my Generic X1i R3AA010 ROM. Name Display does work now, however with S2U2 enabled, I don't see the name of the caller. I'm sure this is a limitation with S2U2. I will try to send A_C a message to see if he can figure out how to enable it in S2U2, but if anyone else has any ideas, please let us know.
I also noticed that you incorporated the TrustTimeZoneField fix for the incoming SMS wrong time issue.
Thanks for packaging this up!
It might be an issue with how the visual aspects of s2u2 are aligned. For the new touchflo dialer, it doesn't show either but when you replace the dialer .png file with one from the vga dialer, it works perfectly.
Hey sundeep01,
could you link to the dialer .png file from the vga dialer?
Thanks
Sorry, i dont have that file anymore. It's not worth it anyway, it doesn't fit the screen fully and since its the only thing changed in the dialer it throws off everything else and the slider doesn't work.
Thx for the cab, I installed it and it works! However, I have the same problem with the new dialer not showing the name. It does show up in the call log so I know it works.
Anyone found a solution yet?
Ok this is really annoying! Evertyhing works except the incoming call, it just doesn't display the name! There must be a solution out there somewhere...
Hey folks, I've been using Name Display on my XPERIA for a while now. Christian has even cooked it into one of his ROMS!
Before that I used the Rogers Name Display cab from the Diamond. It's located somewhere on this forum and it works great. I do not seem to have the issue that you guys are having with the dialer (using the default dialer)
Thank you for this man! It works excellent!
thanks,
hope it will work
try.. it...
I have a pair of bluetooth headphones by Sony (DR-BT21G) with media controls (AVRCP). This has always worked perfectly with the HTC Audio Manager throughout many ROMS (the default and Dutty's) but I upgraded to WM6.5 this weekend and it no longer works. Now, any time I try to use the controls, Windows Media Player fires up and takes over. Is there any way to change this or to manually set this back to the HTC Audio Manager? Listening to music is probably what I do most with my HD so this is probably reason enough for me to go back to a different ROM if I can't figure this out.
I've searched like crazy and it seems to happen to the WM6.5 Energy ROMs too, so it must be a general WM6.5/Manilla problem. So far, I've tried looking through all the settings in HD Tweak and Advanced Config, as well as changing the 0 and 1 keys in HKLM\Software\Microsoft\Shell\Rai\:WMPLAYER to point to AudioManager_Eng.exe, but none of that worked.
Does anyone have any other ideas?
Edit: Slowly, it seems to be becoming clearer that the Bluetooth Driver might be (part of) the solution. Any assistance in getting different versions of the BTHCI.DLL file or more insight would be great! If you have a Manila 2.5 ROM with working bluetooth control, please take a minute to share your driver with us!
I have exactly the same problem and I've posted about it here: http://forum.xda-developers.com/showthread.php?t=566157&highlight=AVRCP
elammertsma said:
I have a pair of bluetooth headphones by Sony (DR-BT21G) with media controls. This has always worked perfectly with the HTC Audio Manager throughout many ROMS (the default and Dutty's) but I upgraded to WM6.5 this weekend and it no longer works. Now, any time I try to use the controls, Windows Media Player fires up and takes over. Is there any way to change this or to manually set this back to the HTC Audio Manager? Listening to music is probably what I do most with my HD so this is probably reason enough for me to go back to a different ROM if I can't figure this out.
I've searched like crazy and it seems to happen to the WM6.5 Energy ROMs too, so it must be a general WM6.5/Manilla problem. So far, I've tried looking through all the settings in HD Tweak and Advanced Config, as well as changing the 0 and 1 keys in HKLM\Software\Microsoft\Shell\Rai\:WMPLAYER to point to AudioManager_Eng.exe, but none of that worked.
Does anyone have any other ideas?
Click to expand...
Click to collapse
Same here with Dutty R5.
A fix would be great.
I worked pretty hard at trying to find a solution but to no avail. I found that there's a key in the registry that refers to a bluetooth plugin for WMP, but deleting it had no effect and I don't think there's a simple way to get rid of the actual plugin. Doing so also still doesn't guarantee that AudioManager will take over. Maybe if someone takes the time to try swapping out files between (for example) Dutty's WM6.1 v4.3 and Dutty's WM6.5 Leo R5, it might work. Particularly, swapping out AudioManager_Eng.exe and all WMP files and registry settings might work. Just an idea! I'd do it myself, but considering crazy work hours, my need for a working phone and problems I've been having with 6.5 it will be a while before I can do more on this.
I was also using Dutty's Leo R5 but due to major stability issues which seemed to be primarily related to importing contacts and texts (through either PIM or "My Phone"). I'll miss the twitter tab and all the neat features of the new manila and WM6.5 improvements but for now Dutty's v4.3 Final is just so much faster, more reliable and doesn't have the bluetooth problem.
Unless some smart guy figures this one out, I think we can best just hope for it to be resolved in a future rom with a fix in the new Manila.
The question for me is: Is this problem on all 6.5 ROMs??? I thought I had tried a 6.5 ROM before without this issue... but I might be wrong...
Am I right in assuming you returned to Dutty's 6.1 ROM? Because then I would flash a 6.5 ROM and we could test replacing files: You upload them here and I try replacing them on my Blackstone!
Update: I just flashed PhamQuang's V67 (a 6.5 ROM with Manila 2.1) - and guess what: My BT-headset controls the TF3D music player!
So maybe this is not a 6.1 vs. 6.5 problem, but rather a Manila 2.1 vs. 2.5 problem? Or it just depends on what ROM you are using and if the cook has done his magic correctly?
Great news! I'm glad you have it working and it narrows the problem down a bit.
So it seems that for now, bluetooth music lovers should steer clear of M2.5. I'd think it's a Manila 2.5 problem considering it works on all Manila 2.1 versions I've tried so far and on PhamQuang's V67 ROM with WM6.5 that you're using. I still wonder if swapping files between Manila 2.1 and 2.5 would be possible, but after using WM6.1 and Manila 2.1 for a day I'm hooked on the speed and won't be going back to Manila 2.5 until some major speed improvements have been made. (Or am I mistaken and is WM6.5 the laggy culprit?)
Considering you have your headset working with PhamQuang's V67 and it runs WM6.5, I'd like to wander off topic a bit and ask how you like that one? Has it been fast and stable so far? I've been pretty happy and faithful to Dutty's work but if there's something better out there (with working bluetooth to HTC's AM) I'm definitely game! I especially miss the smoother kinetic scrolling of WM6.5 and the wonderful Twitter tab in Manila 2.5. I guess I'll just have to be patient for that last one considering it seems you can't have everything.
Fix. thx to Gooru from xda-developers.info
Awesome! Thanks NewFolk! I'm glad there's a solution and hopefully it will help anyone who's searching for it. I can't test whether it works on Dutty's Leo R5 at the moment but I'll take your word for it
At least this is one less reason to avoid WM6.5 + M2.5!
elammertsma said:
Considering you have your headset working with PhamQuang's V67 and it runs WM6.5, I'd like to wander off topic a bit and ask how you like that one? Has it been fast and stable so far? I've been pretty happy and faithful to Dutty's work but if there's something better out there (with working bluetooth to HTC's AM) I'm definitely game! I especially miss the smoother kinetic scrolling of WM6.5 and the wonderful Twitter tab in Manila 2.5. I guess I'll just have to be patient for that last one considering it seems you can't have everything.
Click to expand...
Click to collapse
PhamQuang's ROMs aren't the fastest ones out there, which is why I'll switch to a different 6.5 ROM or back to Topix (the best 6.1 ROM I've tried) as soon as I get my LCD replacement (I managed to break my LCD screen while attempting to exchange the touchscreen... )
NewFolk said:
Fix. thx to Gooru from xda-developers.info
Click to expand...
Click to collapse
Awesome! Thank you! Hopefully this fix enables every WM+Manila combination!
elammertsma said:
Awesome! Thanks NewFolk! I'm glad there's a solution and hopefully it will help anyone who's searching for it. I can't test whether it works on Dutty's Leo R5 at the moment but I'll take your word for it
At least this is one less reason to avoid WM6.5 + M2.5!
Click to expand...
Click to collapse
If you get around to trying a 6.5+2.5 ROM, please post some feedback!
NewFolk said:
Fix. thx to Gooru from xda-developers.info
Click to expand...
Click to collapse
Didn't work for me on Miri's V10, still launching WMP. Still looking for a solution.
Wow, sorry to hear about your screen, MAMeingast. I wouldn't dare attempt that with my dear HD, although I do wish it had a capacitive screen. I haven't touched my stylus in months.
If I can get Sashimi to do decent backups and automated installs, I might be able to experiment with ROMs more freely, but for now XML provisioning and other settings restorations don't seem to work well and reflashing and configuring still takes a few hours each time. I might try a full backup of my current setup this weekend and test a few Manila 2.5 ROMs. Maybe I can pinpoint what the differences are between the working and non-working BT configurations are and make a cab to fix it. Unfortunately, I'm not aware of a method to monitor file or registry key access so I can't see what's active during BT headset pairing. In other words, getting that together will have to be a pretty labor intensive process.
The cab file simply contains a version of the BTHCI.dll driver file. I haven't been able to find Gooru's original post (using Google translate considering the site's all Russian), so I don't know which ROM(s) the cab file is meant for, where the file comes from or which build of WM it is included in. A quick search turned up this post by Da_G from way back in May, noting that the 216xx WM6.5 build comes with a BTHCI.dll version that isn't bound to WMP. How the binding is done isn't clear to me, but it's possible that the currently running media player (usually AudioManager_Eng.exe) would accept the input without extra configuration. If people can grab that version (see below) and post results here (or any other versions for that matter... it can't hurt to try more!), we could see if it fixes the problem. It's starting to look like that file is indeed the culprit, so good news there!
Thinking out loud: If it turns out to be more than just the driver, I might try replacing the dll on Dutty's Leo R5 first, followed by others until I find a Manila 2.5 that the cab file fixes. If that works, I can dump the file system and registry before the fix, and the file system and registry of other uncabbed ROMs to see if a general fix can be made and hopefully pass that along to Dutty and the other cooks to add to future releases. If anyone is running a Manila 2.5, please try installing the cab and posting your results. It would be additionally helpful to let us know which version (or date and size) your original BTHCI.dll is.
mauriceheath said:
Didn't work for me on Miri's V10, still launching WMP. Still looking for a solution.
Click to expand...
Click to collapse
I'm sorry to hear that. Naturally, I hoped someone had come up with a general fix, but we'll keep looking. I changed the topic title back from [Solved] considering it didn't work for you. If you find out more, let us know! Maybe you can help with the dll questions, considering you're running a 2.5 ROM.
Edit: Found a download of the proposed older working BTHCI.dll! Try the cab from this post and let us know if it works for you: http://forum.xda-developers.com/showpost.php?p=3807872&postcount=114
It should be uninstallable, but I still recommend backing up your original. You can never be too careful, right?
neither #8, nor #12 can fix my problem, ROM udk Leo R3. still looking for solution...
elammertsma said:
Wow, sorry to hear about your screen, MAMeingast. I wouldn't dare attempt that with my dear HD, although I do wish it had a capacitive screen. I haven't touched my stylus in months.
If I can get Sashimi to do decent backups and automated installs, I might be able to experiment with ROMs more freely, but for now XML provisioning and other settings restorations don't seem to work well and reflashing and configuring still takes a few hours each time. I might try a full backup of my current setup this weekend and test a few Manila 2.5 ROMs. Maybe I can pinpoint what the differences are between the working and non-working BT configurations are and make a cab to fix it. Unfortunately, I'm not aware of a method to monitor file or registry key access so I can't see what's active during BT headset pairing. In other words, getting that together will have to be a pretty labor intensive process.
The cab file simply contains a version of the BTHCI.dll driver file. I haven't been able to find Gooru's original post (using Google translate considering the site's all Russian), so I don't know which ROM(s) the cab file is meant for, where the file comes from or which build of WM it is included in. A quick search turned up this post by Da_G from way back in May, noting that the 216xx WM6.5 build comes with a BTHCI.dll version that isn't bound to WMP. How the binding is done isn't clear to me, but it's possible that the currently running media player (usually AudioManager_Eng.exe) would accept the input without extra configuration. If people can grab that version (see below) and post results here (or any other versions for that matter... it can't hurt to try more!), we could see if it fixes the problem. It's starting to look like that file is indeed the culprit, so good news there!
Thinking out loud: If it turns out to be more than just the driver, I might try replacing the dll on Dutty's Leo R5 first, followed by others until I find a Manila 2.5 that the cab file fixes. If that works, I can dump the file system and registry before the fix, and the file system and registry of other uncabbed ROMs to see if a general fix can be made and hopefully pass that along to Dutty and the other cooks to add to future releases. If anyone is running a Manila 2.5, please try installing the cab and posting your results. It would be additionally helpful to let us know which version (or date and size) your original BTHCI.dll is.
I'm sorry to hear that. Naturally, I hoped someone had come up with a general fix, but we'll keep looking. I changed the topic title back from [Solved] considering it didn't work for you. If you find out more, let us know! Maybe you can help with the dll questions, considering you're running a 2.5 ROM.
Edit: Found a download of the proposed older working BTHCI.dll! Try the cab from this post and let us know if it works for you: http://forum.xda-developers.com/showpost.php?p=3807872&postcount=114
It should be uninstallable, but I still recommend backing up your original. You can never be too careful, right?
Click to expand...
Click to collapse
Hi elammertsma,
I've already tried the T-Back 6.5 BT Driver.cab, still launches WMP so I'm guessing there's more to this than just the version of BTHCI.dll. The BTHCI.dll included in Miri's V10 ROM is dated 01/10/09 16:31 (although that may be the date I installed the ROM, not sure) and is 63K in size. Hope this helps.
seems the bthci.dll is a rom file, and prevent copy? I try to copy the file from a rom which headset could interface with manila audiomanager, but fail - say the file in not allow to copy...
i-PDA2006 said:
seems the bthci.dll is a rom file, and prevent copy? I try to copy the file from a rom which headset could interface with manila audiomanager, but fail - say the file in not allow to copy...
Click to expand...
Click to collapse
You'll need to use another file manager like Total Commander or Resco File Explorer to copy the BTHCI.dll file
mauriceheath said:
You'll need to use another file manager like Total Commander or Resco File Explorer to copy the BTHCI.dll file
Click to expand...
Click to collapse
I'm using the Resco, but still same problem. Properties of the bthci.dll is checked for hide/ready/sys/rom. It can not be seen both in WM file explorer and Resco, but in Resco search for the name you can find it. I try to copy via Resco, it said copy fail...
mauriceheath said:
Hi elammertsma,
I've already tried the T-Back 6.5 BT Driver.cab, still launches WMP so I'm guessing there's more to this than just the version of BTHCI.dll. The BTHCI.dll included in Miri's V10 ROM is dated 01/10/09 16:31 (although that may be the date I installed the ROM, not sure) and is 63K in size. Hope this helps.
Click to expand...
Click to collapse
For mine:
1. BTfix.cab, still activate WMP, and seems no change at all.
- I try WMP, my headset is still interface with it, works well.
- Manila audio - sound was transferred to headset but interface no.
- CorePlayer - sound was transferred to headset but interface no.
2. T-Back 6.5 BT Driver.cab, not activate the WMP any more, and others unchanged.
- I try WMP, need manually open WMP first, and my headset is still interface with it, works well.
- Manila audio - sound was transferred to headset but interface no.
- CorePlayer - sound was transferred to headset but interface no.
being a bluetoth headphones ower to i ued the htc audio player too. im using nrgz photon rom 11.10.09 manilla 2.1. the default launched audio player from headphones is media player. tried this fix it dont fix it. yes i know its for m.2.5 i was just hoping it would work.
guess i will have to make playlists there instead. i remember there being issues with Wmp it wouldnt recognise all my content. like eminem album i got from play.com. all my own cd rips are good though lol. i will post a fix if i find one. i got a cab. the for s2p which is called tback but all that does is the opposite and unlocks the htc audiomanager and reverts to WMP or s2p. ive looked at nitrogen but unable to find anyway to make headphones work.
My Observations on this
Now my observations on this is that it was not happening on NRG Leo release 14092009 (think it may have been the last Genisis version). We know that NRG's rom platform on 23016 is rock solid as he has stated that many times so I'm suspecting it must be something in the lastest M2.5 version 1919xxx or another package addition as it seems to be effecting all the current Roms running this version of the Leo Manilla. I'm really suspecting that it is something in the way M2.5 HTC audio player is interfacing with WMP but that is just my humble non technical opinion
Can't find if BT stack has been updated in all of this. Bit of a bugger as I have the same issue in the my current version 23092009 release and it is also in the 11102009 release. Hope NRG can take a look at this as I use my BT headset constantly or my bit helps in some small way in finding a solution. In the meantime I'm falling way back to 14092009 NRG Leo version.
About a month ago I upgraded from my old trusty and excellent HTC HD to the new HD2.
After a few tweaks, haks and fixes and some downloads, I was extremely happy of my HD , in fact the only real improvement in the HD2 to me seems to be the much faster CPU (which of course is not a little thing)
However there are a couple of major gripes (or just lack of aternative options) on the HD2 that I find particularly unnerving, prominent among which is the excruciatingly bad Kboard.
It's even worse than the one I've got on my HTC Hero which has a far smaller screen.
On the HD I had installed "FingrKboard" which I found simply excellent; is'nt there something similar that would work on the HD2?
Or maybe do you think that the same .cab file that worked on the HD's wm 6.1 will also work on the HD2 wm 6.5?
Second major problem with the HD2 is that I still have'nt been able to find a (good and possibly free) registry editor for it.
I have read about some very interested tweaks for the HD2 in the threads of the forum, but they all require the use of a registry editor, which one would you suggest?
And again: would I be able to install and use one of those I had on the wm 6.1 of my old HD(1) ?
And last (and probably least too): would "Gyrator" ,be installable and working on the HD2 as it did on the HD1?
No eh?
And do you know of another app that would make the screen turn from portrait to landscape with all apps?
Even if you could point to the solution to just one of my conflicts with the HD2 , you would have accomplished your Xmas good deed by making very happy a poor afflicted geek.
This is the way you might earn your place in heaven, you know ?
PlexusXXX said:
About a month ago I upgraded from my old trusty and excellent HTC HD to the new HD2.
After a few tweaks, haks and fixes and some downloads, I was extremely happy of my HD , in fact the only real improvement in the HD2 to me seems to be the much faster CPU (which of course is not a little thing)
However there are a couple of major gripes (or just lack of aternative options) on the HD2 that I find particularly unnerving, prominent among which is the excruciatingly bad Kboard.
It's even worse than the one I've got on my HTC Hero which has a far smaller screen.
On the HD I had installed "FingrKboard" which I found simply excellent; is'nt there something similar that would work on the HD2?
Or maybe do you think that the same .cab file that worked on the HD's wm 6.1 will also work on the HD2 wm 6.5?
Second major problem with the HD2 is that I still have'nt been able to find a (good and possibly free) registry editor for it.
I have read about some very interested tweaks for the HD2 in the threads of the forum, but they all require the use of a registry editor, which one would you suggest?
And again: would I be able to install and use one of those I had on the wm 6.1 of my old HD(1) ?
And last (and probably least too): would "Gyrator" ,be installable and working on the HD2 as it did on the HD1?
No eh?
And do you know of another app that would make the screen turn from portrait to landscape with all apps?
Even if you could point to the solution to just one of my conflicts with the HD2 , you would have accomplished your Xmas good deed by making very happy a poor afflicted geek.
This is the way you might earn your place in heaven, you know ?
Click to expand...
Click to collapse
FingerKeyboard worked on WM6.5 on the HD1 and works on the HD2. I found it to be superior to the standard HTC keyboard.
There is also a cab file that reduces the sensitivity of the screen on the HD2. This is supposed to make typing a bit easier although I have not personally tried it.
For registry editing, I use PHM RegEdit. It's a free program.
I use Resco Explorer and once you've downloaded that (for free), download the registry editor add-in (both cabs on the Resco site)
sunking101 said:
I use Resco Explorer and once you've downloaded that (for free), download the registry editor add-in (both cabs on the Resco site)
Click to expand...
Click to collapse
Resco Explorer will eventuall need a key to fully register the program. I do however second Resco if you can buy it.
kareeem said:
Resco Explorer will eventuall need a key to fully register the program. I do however second Resco if you can buy it.
Click to expand...
Click to collapse
The registry editor stays unlocked though. I actually never use the Explorer part but you're right, that gets locked after a few days so you need to purchase it (if you want to).
Try Swype as a keyboard. I found it on this site and haven't looked back! It has an amazing input method and is not as over-sensitive as the native HTC keyboard. Check it out....
http://www.swypeinc.com/
Plexus,
This thread will also help you...http://forum.xda-developers.com/showthread.php?t=583638
WB
I second PHM RegEdit.
Simple, easy to use and free.
Thanx fellas.
I had both PHM regedit and fingerkeyboard because I had downloaded and installed them on my old HD(1) and Samsung Omnia i900 ( of which I got rid long ago) , now I have installed them on the HD2 and they work great.
I wonder which other win 6.1 apps will work on the big screen and win 6.5 of the HD2.
Dutty (one of my heroes) for exemple had to modify Cyberon voice dialer to get it to work on the HD2 because as it was the standard version would'nt play together with the HD2., so not all HD apps would be usable on the HD2.
I wonder how Gyrator would behave in the new environment.
Oh, and thanks very much for the link too, very interesting and useful.
I hope I'll be soon able of being of some help too.
BSB tweaks for screen rotation mate
http://forum.xda-developers.com/showthread.php?t=589305
Thanx Carlos, I have already installed the awesome BB Tweaks and now I have also cheked the "show standard windows setting" box, but I still can't find the menu you uploaded with the screen turning option.
Where is it hidden?
Is there any particular option I should enable?
I have enabled nearly all of them anyway but hat option still eludes me.
gargon01 said:
Try Swype as a keyboard. I found it on this site and haven't looked back! It has an amazing input method and is not as over-sensitive as the native HTC keyboard. Check it out....
http://www.swypeinc.com/
Click to expand...
Click to collapse
where can I get this from as the link doesn't give any option to get it ?
PlexusXXX said:
Thanx Carlos, I have already installed the awesome BB Tweaks and now I have also cheked the "show standard windows setting" box, but I still can't find the menu you uploaded with the screen turning option.
Where is it hidden?
Is there any particular option I should enable?
I have enabled nearly all of them anyway but hat option still eludes me.
Click to expand...
Click to collapse
Run BsB Tweaks and open the menu - Rotation is in there.
Hi there..
Dont mean to flame or anything like that.
But the title of the thread suggests that you arnt happy with the device.
So we start reading your post.
But its all just software features you lack or want to change.
And that does not really imply the hardware exclusive to the HD2.
@ Johncmolineaux
Thank you mate, I looked for it for 2 days, maybe I should wear my glasses more often.
@ Enonoid
I'm sorry if from my title you or anybody else got the impression that I was'nt happy with the HD2: I bloody love it man!
I just wished to find a few apps, progs and tweaks to which I got used with my old HD1 (which I loved too).
I also have an HTC Hero and a Nokia N97 ,which after Nokia changed camera lens, camera cover, GPS chip & software, installed ROM 2.0, optimized memory, and gave me for free one year subscription to the latest OVI maps for Europe, has become a great phone too; but the HD2 is my fav hands down, even though as an OS per se I like Andrid more than WM 6.5 (mainly because of the marketplace and the awsome free apps available).
One must be a brainwashed Apple fanboy not to like like the HD2.
Gyrator works fine on the HD2
gargon01 said:
Try Swype as a keyboard. I found it on this site and haven't looked back! It has an amazing input method and is not as over-sensitive as the native HTC keyboard. Check it out....
http://www.swypeinc.com/
Click to expand...
Click to collapse
marra2 said:
where can I get this from as the link doesn't give any option to get it ?
Click to expand...
Click to collapse
+1. No download link. Is it actually available for use on another phone but the Omnia II?
found it its here and its brilliant http://www.4shared.com/file/168683514/da3fc332/Swype.html
gargon01 said:
Try Swype as a keyboard. I found it on this site and haven't looked back! It has an amazing input method and is not as over-sensitive as the native HTC keyboard. Check it out....
http://www.swypeinc.com/
Click to expand...
Click to collapse
Swype is the next generation keyboard, amazing. I am running it on the HTC Touch HD, although it will run much better on a capacitive screen, more sensetive the screen the better it will work.
Yes, Swipe rocks,but after BB tweaks adjusted the screen sensitivity of the standard kwerty, and the FingerKboard, they have become absolutely excellent too.
The only problem is that I can't put any of those in ladscape position.
I have tried to reinstall Gyrator but it does not seem to work on the HD2 it seems made for devices with styluses and resistive screens.
Did anyone find a way to type messages, notes, etc. in landscape?
Hi all
I want to port a dialer from the Photon to the Nike or the EzInput from the Rhodium
I was wondering if I can ask from the guru's who port dialers, Sense, etc from 480x800 to 480x640, etc what actually needs to be edited?
I have IDA and Restorator as well as a hex editor. I would like to learn how to go about this and want some help.
I know pcarvalho at one stage was porting the EzInput 2.1 before the MEGA was released - so I know that it is possible, just want to know how.
The main reason for the EzInput is that the Nike has a hardware keypad that doesn't seem to work with any Ezinput other than v1.5 and then there is a 16key version and a 20key version, so the builds are different - just want a more recent one that is QVGA and works with the hardware input also
Reason for the dialer is to correct a few errors in the MEGA dialer (already corrected the incoming call Position - but Call History is an issue) and I believe that V5 Phone Canvas solves this problem - I would also like to look at a more recent 3G dialer, but the only that I can do for that is look at porting one from a different resolution, as there are no recent QVGA ones. Why the Leo never had 3G video dialing is a mystery to me
Is it possible to add Video dialing to a 2G dialer Canvas?
Anyway, I hope someone can assist me to do this, or at the very least point me in the right direction.
Thanks
DT
that is very hard and i dont know how to make it... look at this OEM pkgs i get from LEO to QVGA maybe you can have an idea makin a diference hex edition
+ Que PPC said:
that is very hard and i dont know how to make it... look at this OEM pkgs i get from LEO to QVGA maybe you can have an idea makin a diference hex edition
Click to expand...
Click to collapse
Thanks + Que PPC - I have already ported the power/backlight from the Leo - editing the XMLs is good if the package has them.
I also understand what I am asking is not straight forward; otherwise anyone could be doing it. There are however, those in the XDA community that have the knowhow - I don't mind if the help comes via PM or email so that the inevitable thousand questions and comments aren't there - it is though, something I would like to be able to do, if not just for myself, but to also help the XDA community.
The people with QVGA devices would love to get updated components - the MEGA helped that immensely, but they are still crying out for a decent 3G dialler – I would be able to halve my ROM releases if nothing else with that. I for one want to be able to use a newer Ezinput – one that I can get working with the Nike’s hardware keypad. If that means pain stakingly editing every file in a package, then so be it.
Maybe it is as easy as editing a few XML files with the newer packages – I don’t know, if someone wants to help then I welcome the assistance. We all start somewhere and I wouldn't be able to even cook a ROM if 14months ago people in this community didn't lend their helping hand.
Thanks again, appreciate the input.
DT