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.
regedit -goto
hklm/software/htc/engineermode/
and change buitinengineermode dword to 1
save
goto dial pad and enter: *#*#364#*#*
regards
Seth
I found that entry a few days ago. I tried it, but nothing happens.
What do you can see/do in engeneering mode?
Just tried it. It opened a tabbed dialog that shows all the info the phone is getting from the cellular network.
Tower number, GPRS settings and a lot of stuff I know nothing about. Nice diagnostic tool.
P.S.
funnysurf, did you dial the number correctly? For me it opened the second I entered the last *. (on Jamin, ROM 2.13.9.123)
It works... Latest Dopod ROM.
HTC Engineering Mode
I've been hunting for a way to see this info. I design cellular networks and this stuff is my second language. However, I don't see anything in any fields of GSM Test Mode. They start with "N/A" then immediately go blank. I've done the registry setting but no change. When I do the '*#'-thing, I get nada. Got any clues?
FYI- I found a program called NiceTrack that shows only some of this info, so I know it's in there somewhere, but I need to see more.
jott2me, post your ROM version. On the Dopod's 2.15 it works.
GSM Test Mode
The key word is “built in” If you have a little program GSM TestMode.exe in your windows directory, this registry tweak makes this program visible and executable. Plus don’t forget to soft reset your device in order for registry modification to take effect.
By the way, if you use this data a lot, you can make a shortcut to this utility as to any executable. No need to dial the *# a hundred times. Or just add it to your speed dial…
You guys sure respond fast! Wow! And thanks!
JWalker, here's my info:
ROM version: 1.8.10.2 WWE
ROM date: 12/10/05
Radio version: 01.09.10
Protocol version: 4.0.13.20
ExtROM version: 1.8.10.104
(I've only had this about a month so I'm leary of changing ROM versions.)
aleksandr,
I'm running Spb's Today screen (it's nice) and I've got an icon that puts me right into GSMTestMode.exe when the reg tweak is set to 1. I've reset several times still no luck seeing info. I made a contact with the '*#' stuff but when I dial it, I get, "The number you have dialed..." message.
Am I missing something?
Thanks for your help.
GSM menu
How did you reset your device, programmatic soft reset or with your stylus? Soft reset with stylus will erase registry modifications without saving them. Sorry, don't mean to use "dummy" talk, just want to make sure all proper steps are followed to eliminate all possible reasons in order to find the solution. Another reason for this issue could be in rom, but wait for J. Walker to respond. I'm in the office right now and don't have emulators here to experiment with your rom version. In the mean time make sure you’ve made all necessary registry changes in right registry entries, and soft reset using program, something like Nice start or shut down XP or SPB Pocket Plus reset function.
I've been using TRE to edit the registry then resetting it using the stylus and the hole on the right side. Every reg change I've made shows up after a reset as changed. I don't know of another way to soft reset it. Even when I've changed it back to 0 to try using JUST the GSM Test Mode.exe, it won't work. That's proof that the registry does see the changes (I think).
(... and I'm the newbie here so "dummy" talk is A-Okey doke w/ me.)
Guess, it is a good idea to change to 2.x ROM. The only thing I know that it works fine with my original S200 with Dopod's 2.15.13.27 ROM. It much morу stable and fast, so you will got the better feeling
Hi,
on Vodafone ROM 2.15.3.26 GER it does not work. I create an Link to \Windows\GSMTestMode.exe and do it that way
I tried creating the link to GSMTest but that still didn't work. I think I'm going to have to change ROMs. I'm very reluctant because I don't know where or how to get and install one. I've seen that this site is full of talk about ROM upgrades, but I haven't seen one that tells me how to do it.
The thing is that what I'm really really after is not just the GSMTest screen so it may or may not even involve a new ROM. What I really want is to learn where the info is hiding and how to display it and make some of it usable in graphical format (something like "NiceTrack" does but with all the info not just a couple fields). It's more of a programming thing. So if anyone knows where this info is stashed and how to read it, I'd go that direction. I thought that GSMTest would be a quick & easy step toward what I'm after.
any change someone could add the gsm test program. I did found the engineering key in the registry, but no program in the windows directory and entering the code on the phonedial pad didn't work as well.
i'm running tuma 1.3 wm5 rom on a qtec 9090
If you want a good guide to changing roms see this post
http://forum.xda-developers.com/viewtopic.php?t=52564&highlight=
sethxp said:
regedit -goto
hklm/software/htc/engineermode/
and change buitinengineermode dword to 1
save
goto dial pad and enter: *#*#364#*#*
regards
Seth
Click to expand...
Click to collapse
I'm sorry, but I have to ask this question. After a year or so of using these amazing little hacks I've always wondered one thing. . . How in the HELL do you folks figure out these things exist?!
I'm sorry, but I have to ask this question. After a year or so of using these amazing little hacks I've always wondered one thing. . . How in the HELL do you folks figure out these things exist?!
Click to expand...
Click to collapse
My thoughts exactly... I discovered this site 2 years ago when I had the Xda2 and I'm still amazed at the information that I can dig up here. Guess some of us have the privelege of playing with our gadgets more than others...
i had to go into the props of the file and change it from hide. i also had to use resco and searched for the file name and changed it there. from there i copied the file and choose poaste shortcut to the windows\start menu\programs
Hey i was wondering if there was a bypass so the phone doesnt interupt the data connection. Is this possible? Thanks.
sorry if this is already answered. i tried searching but couldnt find what i was looking for.
nope, only 3G handsets can do that.
It can be done with a registry hack. Try searching xda-devlopers forum for "registry wizard". Its a program someone made with a bunch of registry hacks put into a nice simple program. Just dont use the default keyboard hack. It locks your wizard up and you have to hard reset.
which tweak do you check in regitry wizard to bypass this?
I dont know. I've never done it manually. Just get the registry editor. Its all automatic and you can download it from these forums if you try. i think the thread is called "easy tweaking your wizard" or something like that.
it will still disable your GPRS during a phone call, but this tweak will reconnect afterwards.
Hi
I have put the latest Cingular AKU 3.3 on my iMate JasJam.
3G/GPRS works fine and it connects properly with most of my application:
Opera, email etc..
However, for some reasons Internet Explorer will never connect nor will it resolves URL.
What could be the issue?
All other applications using the internet connection is working !
Jean-Yves
PIE has a hardcoded proxy now, you have to remove it in the registry.
the reg change is in the hermes wiki near the end (newly updated).
is there a way to fix this without manually changing my registry settings? To date I have avoided changing my registry settings for fear of screwing something up. How "hard" is it to use one of the registry editors to change settings... is my fear justified?
Also, without changing the settings, what limitations/changes will I see in PIE that I don't see now using AKU 2.2 (or whatever the current Cingular ROM is)?
weinson said:
is there a way to fix this without manually changing my registry settings? To date I have avoided changing my registry settings for fear of screwing something up. How "hard" is it to use one of the registry editors to change settings... is my fear justified?
Click to expand...
Click to collapse
probably not. it's very easy, and the registry wiki page is quite helpful. since you just upgraded, now is a good time to try playing with the registry...worst case, you hard reset and nothing is really lost. i don't think you'll have any issues making minor changes though.
sooner or later, one of the very helpful people on this board will probably post a cab or small app that allows this registry entry to be easily changed/toggled.
weinson said:
Also, without changing the settings, what limitations/changes will I see in PIE that I don't see now using AKU 2.2 (or whatever the current Cingular ROM is)?
Click to expand...
Click to collapse
from what i understand, without the registry change PIE will not function unless you are connected via the wap.cingular APN. this may or may not even be an issue for you in the first place.
jamiefiedler said:
from what i understand, without the registry change PIE will not function unless you are connected via the wap.cingular APN. this may or may not even be an issue for you in the first place.
Click to expand...
Click to collapse
Thank you for this information,
Since I have put the HTC 2.05 Test ROM which doesn't have this issue. I also like it better as there's no AT&T logo everywhere.
JY
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......