Database Users

O2 User Interface

Hi,
I have a sim-free XDA II which as it happens is on 02. How can I get rid of that User Interface though - I really hate it, and want to remove it?
Can anybody help please?
Thanks
Rich

goto ad remove programs and remove anything o2 related, then soft reset. Change the dialer skin then all your left with is the boot screens and the o2 logo on the case

I'd recommend chaning the dialer skin back to the default before uninstalling o2 active; there are some images stored in dlls that are difficult to find, but can be changed via the phone skinning applet in o2 active.

The correct order (IMHO that is), is as follows...
1 - Firstly, while you still have the Active interface, use the menu item on the navigation bar, I think it might be listed as 'view' to go in and change the dialler skin to the default one.
2 - Then soft reset.
3 - Next up, now go into File Explorer on either the phone, or via ActiveSync, and go to the Windows/Startup folder, and delete the shortcut for "Active"
4 - Reboot again, to get the phone to load without Active running.
5 - Go into Settings > System > Remove Programs, and remove the Active app, the V2R stff, and O2 Xmail if you never use it. You will get warnings that some files or folders still remain - no problem, this gets resolved later...
6 - Another soft reset.
7 - Now, go into File Explorer again, to the Windows Folder itself, and delete the folder for the V2R stuff.
8 - Change your Today theme to something better looking, do a re-boot, and voila...
If I have missed anything that I think of, I will come back and editt this post, but that's it for now...
EDIT - even if you change the dialler skin back to default before removing the O2 stuff, you will find a strange quirk with the talk/end button, whereby even with the default skin, after ending a call, the old flat red O2 style button will display.
This can be resolved by downloading the XDA Phone Skin Chooser application available from DesignLab (do a google), and then setting the skin to use (even though you might already be using it) to the Default Skin, and then resetting the device. This is the only way I have encountered, other than hard fiddling with hard to find .dll's, to get ALL the buttons to use the default skin, and thus have a proper 'pressed in' appearance when touched.

XDA Phone Skin Chooser will work on my xda2 ?

Nice one Shadamehr. Getting rid of all that speeds the system noticeably
Thanks

XDA Phone Skin Chooser will work on my xda2 ?
Click to expand...
Click to collapse
yes

davidand1 said:
Nice one Shadamehr. Getting rid of all that speeds the system noticeably
Thanks
Click to expand...
Click to collapse
Better than just uninstalling it?
Will removing it in this way stop all o2 related programs reinstalling after a hard reset?

Not sure. I've never tried to uninstall everything.

z0mbi3 said:
davidand1 said:
Nice one Shadamehr. Getting rid of all that speeds the system noticeably
Thanks
Click to expand...
Click to collapse
Better than just uninstalling it?
Will removing it in this way stop all o2 related programs reinstalling after a hard reset?
Click to expand...
Click to collapse
No, not by a long shot.
As the installation files etc, are stored in 'hidden' extended rom, and all a Hard Reset does is clear your phone, and then set about running and installing any files in the extended rom.
To remove it so that it is not installed after hard reset, is kind of achievable, but only if you know what you are doing.
You would have to use the Extended Rom Unlock tool on this site, to unhide and unlock your extended ROM, then you would have to remove any of the CAB install files from this folder for the O2 stuff you don't want (and its up to you to know what's what).
And then you would need to edit the config.txt file that 'calls' all of these installation routines, so that it no longer references any that you have deleted.
Then you could lock and hide the extended rom.
Thus, on a hard reset then, only the stuff you have left gets installed.

Slow, slow, sloooow

Hello,
I believe many of you are (or have been) having similar problems - I wonder if there's a solution for this?
The problem I have is that when the device comes back from sleep (that is, when I open it after not using it for a while) the screen lights up immediately, but the device is extremely unresponsive. Trying to click the Start menu (or anything else on the screen for that matter) will appear to do nothing at first - then when the device finally comes to its senses (10-30 seconds later) my clicks are "played back" at lightning speed. From then on the device is usable, but this delay is infuriating.
I have ROM 1.13.53 WWE (from Sep-23) with radio 1.03.01. My notifications database is small (15 entries) and I'm not running a lot of apps (I have PocketPlus installed).
Is anyone else having this problem? Is there a solution?
TIA

Are you using any Themes? Try switching back to the standard wm5 theme. My m5000 gets very glacier-like as soon as I try any other theme.

Try this.

Thanks for the replies!
I'm using the default theme. As for this Uni-Turbo thing, what does it do? Just so I know before I install it?

it will speed u your processor, after istall u will find the changing botton on Start/Settings/System/Power/Processor it works but using more power.

Im using this, it works Great ... i think its free, but

It essentially places a control panel file in \Windows which 'replaces' the power control panel item. The replacement is from another device, which has a Turbo Mode. So this gives you the ability to activate the turbo mode on your Universal. I've tried it - its safe to use and removing it returns things back to normal.
Try it and see if anything improves. I can guarantee though, that you'll see far more improvement by hard resetting (use Sprite Backup's free beta to backup emails, contacts, messages, etc).

martona said:
The problem I have is that when the device comes back from sleep (that is, when I open it after not using it for a while) the screen lights up immediately, but the device is extremely unresponsive. Trying to click the Start menu (or anything else on the screen for that matter) will appear to do nothing at first - then when the device finally comes to its senses (10-30 seconds later) my clicks are "played back" at lightning speed. From then on the device is usable, but this delay is infuriating.
I have ROM 1.13.53 WWE (from Sep-23) with radio 1.03.01. My notifications database is small (15 entries) and I'm not running a lot of apps (I have PocketPlus installed).
Is anyone else having this problem? Is there a solution?
TIA
Click to expand...
Click to collapse
If you have some Today plugins installed on your device it might slow down the response after turning it on.
For example:
I've got the Resco Explorer installed with it's Today plugin, and my device comes back with the plugin displayed in 15 seconds after opening it.
But when I turn off displaying Resco Today plugin it comes back immediately, after opening... (0,5 secs)
HoPe

My Uni works very well, but then I use it for next to nothing, but I keep memory clean with VJOkButt and stay away from memory resident stuff.
Although not exactly for this question, installing the extended rom dialler had a dramatic impact on speed on mine. If you don't need the pretty buttons, I highly recommend the stock MS Dialler.
V

Start button slowdown on first use
On the issue where the start button doesn't seem to do anything for a while after a suspend or soft reset:
The reason is that an application is listed in the Start Menu which resides on the SD card. What happens is that the Start menu tries to load the icon of the application from the SD card, which first has to wake up, causing the slowdown.
Same thing happens when you're browsing through the Programs folders (Start -> Programs), and there is a pause while loading the application shortcuts.
It's quite annoying, and I think it may be related to one or other registry hack.

Use SmallMenu!
V

vijay555 said:
Although not exactly for this question, installing the extended rom dialler had a dramatic impact on speed on mine. If you don't need the pretty buttons, I highly recommend the stock MS Dialler.
Click to expand...
Click to collapse
is there any way to uninstall the extended rom dialer? it's neither listed in the list of installed programs (in SKTools) nor in \Windows\AppMgr :/
thanks, fuf.

Start button slowdown on first use
On the issue where the start button doesn't seem to do anything for a while after a suspend or soft reset:
The reason is that an application is listed in the Start Menu which resides on the SD card. What happens is that the Start menu tries to load the icon of the application from the SD card, which first has to wake up, causing the slowdown.
Same thing happens when you're browsing through the Programs folders (Start -> Programs), and there is a pause while loading the application shortcuts.
It's quite annoying, and I think it may be related to one or other registry hack.

BeyondTheTech has an interesting article somewhere on Skype with this issue.
I just use SmallMenu, the normal StartMenu is useless to me.
Uninstalling the extended rom - i don't think so. You can probably manually delete the files it installs, but it'd be incredibly tedious and perhaps inaccurate/unstable. Best is to hard reset and setup again, but that's also tedious.
V

Re: Start button slowdown on first use
snorbaard said:
On the issue where the start button doesn't seem to do anything for a while after a suspend or soft reset:
The reason is that an application is listed in the Start Menu which resides on the SD card. What happens is that the Start menu tries to load the icon of the application from the SD card, which first has to wake up, causing the slowdown.
Same thing happens when you're browsing through the Programs folders (Start -> Programs), and there is a pause while loading the application shortcuts.
It's quite annoying, and I think it may be related to one or other registry hack.
Click to expand...
Click to collapse
So how come then I have the same thing when browsing anything for the first time after the soft reset even when I have NOTHING installed on the SD card? :wink:

martona said:
Hello,
I believe many of you are (or have been) having similar problems - I wonder if there's a solution for this?
The problem I have is that when the device comes back from sleep (that is, when I open it after not using it for a while) the screen lights up immediately, but the device is extremely unresponsive. Trying to click the Start menu (or anything else on the screen for that matter) will appear to do nothing at first - then when the device finally comes to its senses (10-30 seconds later) my clicks are "played back" at lightning speed. From then on the device is usable, but this delay is infuriating.
I have ROM 1.13.53 WWE (from Sep-23) with radio 1.03.01. My notifications database is small (15 entries) and I'm not running a lot of apps (I have PocketPlus installed).
Is anyone else having this problem? Is there a solution?
TIA
Click to expand...
Click to collapse
If you are using SPB Pocket Plus or any other similar software and allowing the SD card indicator on your today screen just remove it and you will realize the difference.
Also avoid to use any battery indicator on today screen as it will slow the device as well.
My last advice to you if you are using SPB Pocket plus is to un-install it and use any other similar program like Resco today plugins.... this will also speed up your device becuase the available version of SPB pocket plus is not completely compatible with WM5.
Regards,

I am using SPB PP (beta release) and its fast, but I didnt have a real problem with the earlier releases. I also use SPB diary and SPB Weather, and still no real problem, slightly sluggish but not intolerable.
My device wakes up perfectly immediately every time, and rings at the beginning of the second ring.
1. Remove SD card and battery monitors
2. Disable some of the additional SPB plug ins that you dont need like safe mode boot, PIE plug ins, battery monitor etc
3. Remove the antivirus software
4. Disable error reporting
5. Disable auto receive beams
6. Try disabling SPB altogether and see if it is still sluggish and unresponsive
7. Dont have anything on SPB or other that is immediately directed to the SD card as the SD card takes longer to recognise on wake up
8. Consider not switching the device off. I never turn it off, at all, wind down screen brightness, disable auto off, but auto off the screen only, close the clam shell switches off the screen but doesnt switch off the machine. the screen sucks the battery, not the processor.
Let me know if you have had any luck with this.
Perhaps you could also:
1. Ensure you have the latest rom from the website
2. Dont allow the extended rom to install (hard reset, and press reset when it says customising device), then use total commander to go to the extended rom and selectively install the items you need, this forum is full of information for this.

vijay555 said:
I just use SmallMenu, the normal StartMenu is useless to me.
V
Click to expand...
Click to collapse
I just tried it and I have to admit I already like smallmenu. One question please: How do I customize smallmenu?
It seems to me it is locked at the following list:
Today
Programs
Favorites
Commonly Used Programs
Settings
Suspend
SmallMenu

I reset my device before any of the crap from Ext.Rom could install. I now have a speeeeeedy device. Oh, i am using an i-mate Jasjar btw.

simon_darley said:
close the clam shell switches off the screen but doesnt switch off the machine. the screen sucks the battery, not the processor.
Click to expand...
Click to collapse
I disagree, try to power off the device every time you close the clam and power it on when you open it and you will see how much the battery life will improve. It really makes the difference, I just can't be bothered and am too lazy to do it :lol: I charge it every night anyway.

Help! Slow input type selection window!

When you need to input text, you can click on the icon at the bottom of the screen to bring up the text entry area. You can tap on the little triangle beside the icon to bring up a window to select between block recognizer, keyboard, letter recognizer, phone pad, and transcriber.
On my 8125, it is taking a long time for this window to pop up after tapping the triangle. It is taking a few seconds, when it used to take maybe 1/3 of a second. It is quite frustrating!
Why is is doing this? And what can I do to speed it up like it used to be?
This has happened before. It was when I first got the phone and was installing apps and games on it. One day I noticed this slow behavior, and I ended up doing a hard reset and slowly adding my apps and registry tweaks back on one at a time to see what would cause the problem. Well, nothing caused the problem and it stayed fast for a long time.
Then yesterday I updated to Summiter's latest ROM and started adding my apps back on. This text entry type window was working just fine through most of it, and suddenly as I'm finally finished putting everything back to where I want it, this problem is back!
Help! I don't want to do another hard reset already!

I have the same problem, I use transcriber as SIP but since it takes so long to show up when you click the triangle, I just put a shortcut to transcriber.exe in the start menu folder. So, I just use the Programs menu, it's much faster

I like to switch between letter recognizer, keyboard, and transcriber. I suppose I could put links to them in the start menu, but it would be so much nicer if I could just figure out why it's being so slow!
Any ideas?

I've read this is due to having MS Voice Command installed, although I haven't confirmed this myself.

I have the problem and never installed Voice Command, so there must be another explanation

anyone idea what the keyboard exe is called?
thanks

This is supposedly caused by a bug in the OS. I use an application called 'Smartskey'. There is a setting that talks about reboot notification for a Wizard. This affects the time it takes for the input method choice popup-. See the text about it from the manual:
REMOVEDUPSDDAEMON=0 (0 or 1)
Only for HTC Wizard. The function is originally not related to SmartSkey. The HTC Wizard contains a program called sddaemon that is the voice command program for wizard. It contains a bug that it will automatically create one more
notification for each reboot. It will make the program slower and slower after a number of reboot and overflow the notification system. To set this to 1 will automatically remove the duplicated notification event. If you are a user of Wizard, it is suggested to set it to 1. The flag is harmless for other machines.
I cannot remember where I downloaded the program, but if you search this forum, you should be able to find a copy.

i dont use smartskey, so is it something else causing my slowdown? i dont understand.
is that a reg key your talking about there?

funy said:
i dont use smartskey, so is it something else causing my slowdown? i dont understand.
is that a reg key your talking about there?
Click to expand...
Click to collapse
Smartskey isn't the problem. It solves a problem with the OS. zIt appears that every time the device restarts, it makes a record in a log file somewhere. Eventually, the log is so full, it takes longer and longer to pull up the menu. I don't recall all of the details, but I found it here. You can probably search to find more information.
The setting I put in the post is a smartskey.ini setting to resolve the problem.

thanks, might give it a try then

mrschwarz said:
Smartskey isn't the problem. It solves a problem with the OS. zIt appears that every time the device restarts, it makes a record in a log file somewhere. Eventually, the log is so full, it takes longer and longer to pull up the menu. I don't recall all of the details, but I found it here. You can probably search to find more information.
The setting I put in the post is a smartskey.ini setting to resolve the problem.
Click to expand...
Click to collapse
just put that ley in but stil doesnt seem to have done anything

Problem with hacks working on US MDA...help

Hi,
New here. I have been learning a lot from everyone here, Thanks!
I seem to have a problem though.... Every Hack so far that I try to implement won't work. Here are 2 examples:
Change Reg Keys for Left Soft button. I want it to point to my Agenda Fussion Calender instead of the Windows calender. So I change the Key to point to the AF exe location, being very careful to leave "" and to type path in precisely. I save the change and soft reset the device to see if it works...NOPE....When I go back into the registry to see what happened, the registry key is changed back to point to the microsoft calender. I have even closed the reg editor and reopend to check the change before the soft reset. Before the re-set my change is still there, but not after....
I have tried both PHMRegedit and TascalRegedit.
I have a US version of the MDA with ROM version# 2.26.10.2 WWE
Next problem I wanted to stop the system tray from showing up. So I removed the shortcut for Init_Tray from the startup menu....Well the tray still shows up. Now looking in the startup menu the shortcut is no longer there, but it still launches the tray!
What Am I doing wrong here? I see people making these same hacks and they work for them.
A little background on me. I have been entrenched in computers since 1983. Doing my share of programming (though nothing since I was kid...). I have been using pocket pcs for the last 2 years. With Toshiba 740's and e800's. So I am capable of doing this stuff. But for some reason I can't get these things to work...
Any help? Sorry for being so long winded

on your registry problem.. after changing the value manually, let the phone sleep or just sit there for a few minutes before soft resetting.. There is a delay write to the registry...

Thanks ShogunMark
I need to be more patient. I did this just before I read your reply...The hack for the soft button is now working the way I want. Now to get rid of the bottom system tray.
Thanks again!!

im not sure if you can exactly get rid of the system try completely in WM5.. however i could be wrong... i think at most you can only get rid of the icons in it.. but it does prove very useful for placing shortcuts..

Touch screen delay after wake up

Don't know if its only me:
- Press END key (goes to standby)
- Press any key (wakes up)
- Quickly tap any icon --> Won't react
You need to wait about 1 second for touch screen to be enabled. No big deal but sometimes you are quick and this kind of "retards" your intention and forces you to do a 2nd tap.
Anyone?

pckshd said:
Don't know if its only me:
- Press END key (goes to standby)
- Press any key (wakes up)
- Quickly tap any icon --> Won't react
You need to wait about 1 second for touch screen to be enabled. No big deal but sometimes you are quick and this kind of "retards" your intention and forces you to do a 2nd tap.
Anyone?
Click to expand...
Click to collapse
Works fine here. At least I need a second to reach the top of the screen.

here the same but you must be really quick

Yup, annoyes the hell out of me, unlock the phone and use my other thumb to slide to unlock, nothing happens, have to try again and it works.

I am getting that, but is not a show stopper for me. have you try to use the 3rd party locking screen app?

i use s2u2. same problem here. no unlocking in the first one or two seconds after wakeup... does the processor maybe take some time to speed up...?

I don't think its the processor because its actually fast. Must be some internal software delay, maybe the touch screen driver 'wake up'...

Similar problem existed in the HD, i have it, and i tried out a fix posted by one of the forum members, as follows:
1.Make a file named - "welcome.not" and place this in the root of your storage card.
2. Hard Reset your device.
3. You will not be asked the screen calibaration thing, and this will solve your problem.
(How to create "welcome.not" = open notepad on your computed, and safe the blank notepad file with double quotes as : "welcome.not"
This will make the extension of the file as .not
Hope this helps!

Insane Devil said:
2. Hard Reset your device.
Click to expand...
Click to collapse
Did you mean reset? or clearing the storage

CLEAN STORAGE. (A hard reset, my friend!)

Before making a hard reset i would wait for maybe other fixes or something as i cant imagine that HDs and HD2s problems are the same... Also i didnt figure out this bug on my old HD, even without "welcome.not"...
You can even start the screen alignment whenever you want. So what happens if you do an alignment after applying your fix? Problem back again?
Last thing: I would not recommend a hard reset with your SD-Card in the device as it ruined all my data on it. At least backup all you stuff from the card somewhere on the PC and try this fix with an empty storage card.
EDIT: I completely forgot: there is no screen alignment taking place after a hard reset on the HD2

Insane Devil said:
CLEAN STORAGE. (A hard reset, my friend!)
Click to expand...
Click to collapse
Well that's weird because I read here http://forum.xda-developers.com/showpost.php?p=2139034&postcount=5 that it only needs a reboot and people confirmed it work that's why I was confused.

Insane Devil said:
Similar problem existed in the HD, i have it, and i tried out a fix posted by one of the forum members, as follows:
1.Make a file named - "welcome.not" and place this in the root of your storage card.
2. Hard Reset your device.
3. You will not be asked the screen calibaration thing, and this will solve your problem.
(How to create "welcome.not" = open notepad on your computed, and safe the blank notepad file with double quotes as : "welcome.not"
This will make the extension of the file as .not
Hope this helps!
Click to expand...
Click to collapse
I posted an updated fix here http://forum.xda-developers.com/showthread.php?t=587931. If you don't want to hardreset, go into the registry and find HKLM\Hardware\DeviceMap\KEYBD and look for the entry "First Calibration." If it's there and the dword is 1 then change it to 0 and manually softreset. That achieves the same thing as bypassing screen alignment. Manually aligning the screen creates this entry, which is why if you use welcome.not and then later realign your screen, the problem comes back. To solve that you have to change the reg key again. I don't have an HD2 so I cannot confirm if the reg is there or if this would work on it, but it may be worth a try.
S3

dont have my hd2 here at the mom (repair) but would be excited about testers and answers. Just cant figure out how screen alignment and wakeup-delay go together...but the thread mentionend in post above makes me hope

on a german leo the key does not exist

jayjoe said:
on a german leo the key does not exist
Click to expand...
Click to collapse
Neither in WWE Rom.
But there is a PassCalibration already with value 1.

Mines has the same problem, not very often but the problem is there. After wake up the tap just does not move or register my touch and because hd2 has such a large screen, they should have put the slide to the middle or at the bottom and not all the way to the top to slide unlock the phone.

@Skywatch:
For getting the slider on the bottom, search for Dusk lock screen in the HD Apps forum, and install that and u will get it on the bottom, it looks lovely! and I have 100% belief that it will work on the HD, as its the same OS and Screen resolution.
@All:
Regarding the Welcome.not, i read in the HD forum regarding the tweak, and it clearly said to HARD REST, or Re Flash your device and only then it will work. not with a soft reset.
This is to skip the Screen Calibration which happens after a Hard Reset and that has to be skipped.
if you have done this, and later you re align your screen, then the tweak will fall off its place. Another HardReset or ReFlash will be required.
No problems doing it with a mSD full of data as i have been flashing that way since past 4 years, without any problem. But, up to u!

pckshd said:
Neither in WWE Rom.
But there is a PassCalibration already with value 1.
Click to expand...
Click to collapse
pckshd, what are the other key entries besides PassCalibration?

It is actually at HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH\
Other values are AlignScreenNeeded=0, CalibrationData=287,479 57,96 57,864 518,864 518,96 and some more...
These values are from a fresh hardreset, never calibrated, and actually HD2 does not prompt for alignment. So I don't think the issue is related to calibration.
Delay still there