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.
Hi
I'm new here but I was wondering if anyone knew how I could get rid of the O2 customizations. I've unlocked it with the unlocking tool but I cannot get a Rom for I-mate to clear the O2 rubbish as I am not allowed to join clubimate without a valid imei number.
I've checked xda-developers ftp site for the correct rom but i cannot find one anywhere.
Please help me
Sloane
You don't need a new ROM, and with the UK mini S, it's probably best to leave the supplied one alone as, amongst other things, the hardware keyboard layout is different and you'd need to re-patch the keys and symbols back onto the right keys from the i-mate defaults.
I let the full O2 install happen to see what it would install (aside from the 'Active' rubbish) before I did a hard reset to clear it all out. During the reset, when it says 'installing customisations in 5 secs' (or whatever the exact msg is), do a soft reset with the stylus in the hole in the side, and voila, native Wizard, but with correct keyboard mapping... Don't worry, your SIM unlocking will survive the hard reset.
Then, get Total Commander because there are some cab files in the extended ROM that you might want like the MMS editor, additional ring tones etc...
I've got a Qtek 9100 and a mini S (now on Vodafone) and the overall build quality of the mini S is much higher.
Hope that helps?
Dox
Right, I've done exactly as you said. I now have no O2 stuff there. I've got total commander on my phone but I dont know what to look for to get gprs and mms settings back.
Can you help please
Sloane
sloane said:
Right, I've done exactly as you said. I now have no O2 stuff there. I've got total commander on my phone but I dont know what to look for to get gprs and mms settings back.
Can you help please
Sloane
Click to expand...
Click to collapse
Sure, the choice of what to add is entirely up to you, but here's what I added...
during the customising bit that you stopped when you soft reset, the contents of the Extended ROM are installed. Autorun.exe reads Config.txt and all the cab files listed there are installed. We want some of them.
Point Total Commander to '\Extended_Rom\ and you'll see them all. I looked at the extended ROM on my 9100 and tried to find the equivalent O2 cab files. Even though I had already configured MMS connection and server details, the MMS inbox didn't show up until I installed the cab file with MMS1 in the name. I also ran the RingTone one, SmartDialing and, I think, Signed_Version.sa (because my Qtek phone had a similar file, even though I'm not sure what's in it).
I've got a Voda SIM in, so I set up the two GPRS access points for web and wap( only used for MMS). Raphael over at BeyondTheTech.com has the MMS settings available as cab files to d/l and install, to save typing them in by hand. They must also be in the Extended ROM cab files, but I didn't need the O2 ones, and couldn't tell from the names, which cab they were in. The k-jam comes with all the carriers' settings in conveniently named files, and that's what Raphael has listed.
If I had had more time, I might have installed them all, one by one to see what each contained, but I was going out and wanted to take the mini S with me.
Hopefully, that will get you a good way there, but if you are stuck with any other bits, yell and I or somebody else will help I'm sure...
Good luck,
Dox
Try these files for phone settings
http://www.buymobilephones.net/sp3_setup.ihtml
V
To get rid of the O2 interface I just removed it from the Startup directory in Windows, there are two files, both with O2 icons and then did a soft reset. Although I imagine there's still some O2 trickery lurking around on my device, I didn't have to add any new settings or anything that required me to switch my brain from inactive to mildly inactive.
Eradificator said:
To get rid of the O2 interface I just removed it from the Startup directory in Windows, there are two files, both with O2 icons and then did a soft reset. Although I imagine there's still some O2 trickery lurking around on my device, I didn't have to add any new settings or anything that required me to switch my brain from inactive to mildly inactive.
Click to expand...
Click to collapse
Hi, im thinking of just removing those two files from start up as i dont want to do anything too extreme to get rid of 02 rubbish and the method of hard resetting sounds a little tricky, not sure i'd be confident doing it as i only just got the phone.
Have you noticed any error messages since doing this? Does the 02 rubbish not just appear again next time you do a soft reset?
Just let it do what its doing and then choose basic install. Then remove the 02 active in startup to stop the annoying message.
My wizard is running fine like that with all the mms settings etc.
Ok, i haven't hard reset but i have removed the 02 active thing in start up and its no longer appearing on the desktop now. Phone seems a bit more responsive.
tom99 said:
Ok, i haven't hard reset but i have removed the 02 active thing in start up and its no longer appearing on the desktop now. Phone seems a bit more responsive.
Click to expand...
Click to collapse
If your happy with how its performing then dont change. However if you hard reset and opted for a basic you should see even more of a speed increase. But like I say if it aint broke it dont need fixin
hi there
I have orange M5000 with
exRom unlocked etc
my phone app is playing up
firstly smartdialer does not seem to exist and the option
in menu does not start any dialogue
video call is not there either tho the options still exist
(this I can live with but I used intellidialer all the time on my M2000
and I believe this is the same prog)
help would be appreciated
cheers
simonastro
gah
trust me to forget the weirdest thing
on phone app menu
select options and I get the settings page
this cannot be killed tho - I have to reset the device
moreover cannot alter the settings - stuck on ring fantasy.wma
( Have got dialer and video back by selection of orange
ex ROM cabs - had to guess but all is ok )
oddness
I understand, that you did not install all cab files which were supplied by orange in extended rom. Maybe you missed installing a required cab file?
Just my quick thoughts.
Good luck.
Try installing the ENABLE-VT-RTPLUGIN-0727-2-SIGNED.CAB or similar file... should do the trick
:wink:
I did install that cab prior to my last post and
video calling and smartdial are back
however the
stuck on phone options issue is unresolved
cheers
before i go ahead and buy the orange m3100 version of the tytn, can anyone tell me how easy it is to remove all the installed orange rubbish from it? and will it void the warranty if i do so? or it it best just to live with it?
never had a windows based phone before
cheers!
If you mean the orange branded home screen rubbish that they seem to love putting on most of their phones then this is quite easy, just go into the today screen settings, items, and untick the orange option, this will see you back to a normal pda.
cool! didn't realise it was that easy!
thanks!
I haven't had direct experience with an Orange device but I do know that it is not quite that simple with an o2 device. If you change homescreen, all it does it change the theme rather than get rid of the o2 UI (which takes up about half the screen whic useless links and icons!).
However the solution to this is not too complicated either. All you need to do is do a hard reset and then do a soft reset before the extended ROM installs. This will definitely leave you with a non-branded device, although you might have to reinstall one or two useful apps that get installed with the extended ROM (eg. when I did it I had to reinstall the smart dialler).
Hope this helps and apologies to Nightshot if I am wrong about Orange devices. As I said I haven't had to do this on an Orange device.
To really get shot of it you can soft reset your device after the initial setup but before the customisation setups run. This will stop the Orange customisation running and leave you with a vanilla WM5 device.
Then you can install the cab files in extended rom without installing the orange customization CABs.
You can find instructions on how to access your extended rom on the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
If you do it, please post your extended rom here (we still don't have the orange ExtROM contents!):
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtendedRoms
nice one.
thanks to all for the info.
pof: i don't actually have one yet - just wanted to make sure i wasn't making a mistake getting an orange branded device that i couldn't de-customise.
thanks!
i've just done it
got a m3100 today and removing the orange stuff is one of my 1st jobs. I removed the xda 2i o2 stuff by registering as a corporation but saw no kind of option on the m3100. I deselected orange from the today options and set it to windows default. I dont know if still having the orange stuff on device will cause slow down. doesn't appear too.
I did this to allow me to sync with my Mac but I now don't have my MMS settings and video calling.
How do you get around this?
JustinFe said:
I did this to allow me to sync with my Mac but I now don't have my MMS settings and video calling.
How do you get around this?
Click to expand...
Click to collapse
You did what? Not installing the customized CABS (e.g. the Ext ROM)?
If so, you need to get a copy of the Ext ROM for your orange, and find the file that is responsible for the MMS and Video calling. You can either search in this forum (not sure if there is), or just guess by their names.
I hard reset then prior to the orange customisation/ cabs loading did a soft reset - the 'phone works fine apart from mms and video messaging. I've tried running the MMS cab from Extended ROM, then soft resetting - loading onto device but this doesn't bring MMS back.
Any ideas?
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......