I did the upgrade, and everything went well except one thing:
The icons on the top left of the screen (volume, battery indicator, 1/2 of the signal strength indicator) are "cut off." Its like they're covered by something. Any ideas on how to get this back?
You must have done something after the update!
What you have to do is remove the following key in the register:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shell\
There should be a key called: "TBOpt", delete this and soft-reset your device!
Ran a registry wizard
I ran a registry wizard to activate "G" network access which may have done it. I wonder why this wasn't part of the T-Mobile ROM upgrade.
For some strange reason, HTC left more things out of their ROM's that can't be explained
The thing that went wrong in your case was the following:
You have to uncheck "Taskbar Date/Time". This option doesn't work in any AKU2.0 ROM
Related
Everything was going along so great.
I used lokiwiz to unlock my cingular 8125. I did both option a (unlock) and option c CID unlock.
Worked great.
I then flashed the latest summiter rom (one with 217...AD2P_fixed)
Again, went flawlessly. Everything was working and I was a happy camper.
Installed a few mods including:
- smartskey
- nullkeyboard
- tcpmp
- flash capable from Macromedia
I checked each app after installing and everything was working great.
Later that day, I added RegistryWizard and its associated OpenNETCF file and made just a few setting changes:
- 802.11G on
- default to nullkeyboard
- changed a setting for improving performance from 4K something to 8K something.
I clicked on okay and it asked for a restart and I said OK.
It never woke up. I tried a hard reset, tried removing the battery. All I occassionally get is a white screen and then back to blank screen.
I tried to reflash but since I can't connect via Activesync, I can't reflash.
Can someone help! I've only had this phone for 2 days!
Take it back to Cingular and tell them the phone just up and quit, and can they just give you a replacement phone.
whew. problem fixed.
I searched and searched and finally found the solution.
I guess there is this thing called bootloader mode (rainbow colored screen).
This allows a connection via usb even though Activesync doesn't sense the pda.
To get in this mode for the Cingular 8125, I took the battery out to shut it down. Then put the battery back in and while holding the camera button, pressed the power button.
This turned on the 8125 in bootloader mode. I could then plug in the usb cable and reflash with no problem.
Had the same problem. Hard reset actually worked for me in terms of resetting the phone in order to reflash.
The problem you're having is related to NullKB and Registry Wizard. As soon as I set NullKB as the default through Registry Wizard, phone died on reboot. Happened three times, and at that point, you know, shame on me.
Reflashed, set everything back up, did not set NullKB as default, and no problems (except a random reboot in the middle of phone calls).
jonty12 said:
Had the same problem. Hard reset actually worked for me in terms of resetting the phone in order to reflash.
The problem you're having is related to NullKB and Registry Wizard. As soon as I set NullKB as the default through Registry Wizard, phone died on reboot. Happened three times, and at that point, you know, shame on me.
Reflashed, set everything back up, did not set NullKB as default, and no problems (except a random reboot in the middle of phone calls).
Click to expand...
Click to collapse
I sort of suspected that. I only changed a few registry wizard settings. I basically reinstalled everything and only changed the 802.11g setting for now. Working great again. I thought the problem might be with null keyboard or the fact that registry wizard gave me a warning about being for an older version of windows mobile. Had me worried for a while. Did lots of searches and had no idea to search for bootloader.
For others searching... white screen, frozen, locked up, can't install rom, lost activesync, can't restart.
I know, I know before the torrent of replies happens - "Why didn't you Search", "You should have searched before posting" et etc ...... I did search and the results didn't help
I have two Kaisers with identical software builds (slightly different contents but the base OS is identical). On both of these I have (had..) the backlight issue where if the backlight was off when the device was locked (either via the 'Device Lock' Today item or via Battery Status 'DeviceLock on Wakeup'). To enable the backlight it must be unlocked and in bright sunlight this is very difficult.
Now for some reason this behaviour has changed on one of the Kaisers - the 30-second dimming still happens when locked or unlocked, now however tapping the screen turns the backlight on. This is exactly the behaviour I want I assumed there would be a registry difference between the two however I can't find one. All the values in the keys
Code:
HKCU\ControlPanel\BackLight\
HKCU\ControlPanel\BackLight\LockLevel\
HKLM\ControlPanel\BackLight\
are identical. I was hoping to copy the changed registry values and include them in my next ROM re-build but I can't see any differences.
Does anyone know what other registry keys I should look at?
Cheers
Andy
Install this cab and power the phone off and power it back on.
Hey presto brightscreen when you want to unlock the phone!
dwarf said:
Install this cab and power the phone off and power it back on.
Hey presto brightscreen when you want to unlock the phone!
Click to expand...
Click to collapse
Thanks for that but that is the behaviour I have at the moment without a startup application. There is obviously something in the registry that is making this work as I want it on my Kaiser. I just want to know what it is?
Andy
I think I have fixed it....
After rechecking the registry settings I found a difference and I don't know how I missed this previously. I have made the change on the Kaiser that wasn't working as I wanted it and now it's working exactly as I would like:
Code:
[HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel]
"LockLevel"=dword:ffffffff
No more guessing when trying to unlock it in sunlight....
If anyone is interested?
Cheers
Andy
TQ very much.
It is working like you said.
No need to use 3rd party app. Just a simple registry tweaking.
Regards,
morisa
dim backlight on device-lock
I recently flashed to a WM6.1 ROM (ATT 3.57.502.2) and I have noticed that now when you enable the device-lock it does NOT dim the screen. I actually preferred it that way as it helped me realize when I had a successful tap to enable the lock. Not to mention battery-life issues when putting phone in a tight pocket, immediately afterwards.
Can somebody enlighten me on how to make it behave as it used to? I tried to edit some of the registry entries mentioned in this thread, and others, but none seem to apply to the device-lock. Again, I'd like to have the screen dim on device-lock as it did with my old ROM.
Thanks in advance everyone.
,jR
ADB100 said:
After rechecking the registry settings I found a difference and I don't know how I missed this previously. I have made the change on the Kaiser that wasn't working as I wanted it and now it's working exactly as I would like:
Code:
[HKEY_CURRENT_USER\ControlPanel\BackLight\LockLevel]
"LockLevel"=dword:ffffffff
No more guessing when trying to unlock it in sunlight....
If anyone is interested?
Cheers
Andy
Click to expand...
Click to collapse
Thanks, that works... BUT
on my Kaiser only until the next soft reset, then dword is back to 00000000. Anyone else see the same? Solution?
Loewe538 said:
Thanks, that works... BUT
on my Kaiser only until the next soft reset, then dword is back to 00000000. Anyone else see the same? Solution?
Click to expand...
Click to collapse
For me also same problem, OS is WM6.1
Loewe538 said:
Solution?
Click to expand...
Click to collapse
Found out that the cab from post #2 partially solves it. You still have no backlight the first time after a reset, but at least you don't have to go into the registry every time after resetting.
Too bad it sets the level to x0A instead of x0FFFFFFFF.
Key to try for backlight woes
I've had this problem since flashing from 6.0 to 6.1 AND selecting an unlock password at initial startup. Sometimes it would reset backlight time to 10 sec. after soft reset and it was even resetting it without a soft reset for a while. Changing the "Locklevel" key helps as previously posted, but sometimes it would get reset to "0" from my setting of "7" intermittently and then the problems returned. a soft reset always reset this key to "0". I found another key below which I changed from "1" to "0". everything has been totally normal for a week of heavy use. I have not yet reset, but at least it behaves normally even when I use the Today screen Device Lock.
The key is HKLM-Control Panel-Backlight-DimBKLinUnlockScreen
The only remaining issue is sometimes when I power on from suspend the screen comes on and then goes off immediately. Hitting the button again keeps it on.
Good Luck!
I was fooling around with a couple of programs and now I have lost half of my phone signal strength icon (only the left half is showing) and there is nothing showing to the right of it, which should be the speaker icon. If I tap where they should be the programs come up ok. So it seems like something is just hiding that portion of the tray.
The 2 programs I was using were ArielBattery and VjToggle. I tried deleting both but this did not bring back the missing icons so I reinstalled them.
Any suggestions?
Regards,
Fred
I'm going to ask a stupid question here.. Did you restart the phone?
Yup, tried that.
I have been having trouble with my kitchens and some strange behavior I have never seen before. So here goes and sometimes we get narrow sighted when looking for problems.
Some Basic information first:
Ervius Visual Kitchen
WM 6.5 Native kernel
WM 6.5 builds 21869 & 23071
Storage card reformated and blank.
Tried both with and without extendir
Tried both with and without modifed XIP
RunCC set to reset
Manila 2.5
All LEO packages except Dshow, Phone Canvas, SensorSDK.dll, Power, etc.
Not using OOBE setup package.
Now My problem as best as I can describe.
The best way I can describe is a startup problem. Device boots fine and goes through RunCC ok and resets. On second start when the background appears and the titlebar is shown the phone signal icon is showing no signal. The conection setup will the show up and the progress bar goes through and the say done. Sometimes it will not even go in to the connection setup. When you press done the screen does not update but you can see the title bar and the phone still shows no signal. Manila will not start it seems without a radio signal.
Now some of the weird part. Sometimes if I press around on the volume buttons and more so on the title bar and task manager it will sometime refresh and the signal pops up at 100 % signal. It is like the signal was there all along but not updated. As soon as the signal is there Manila starts to load up. One loaded all is ok.
On soft reset it is usually ok with a occasional same problem as above.
On hard reset the same problem as above is quite frequent.
Any help or ideas welcome.
I think it RunCC...
Try a different build of RunCC.
Try to use another connection setup package including ConnectionSetupDB, also check the runcc.lua, maybe you have something over there which may cause the problem during runcc.
Guys, I have a weird issue with my X1. Im using the Energy Rom (6.5), installed a few things (including the SE Icon to replace the Windows one on the start menu), did a soft reset and everything was going ok.
After fiddling about with the phone some more, on the next soft reset i found that the Battery Icon on the taskbar would not update, see the attached screenshot, says the phone is being charged but the phone isnt even plugged to anything. Seems like it only shows the battery status of when i turn on the phone, then stays that way until windows starts again.
Any help would be appreciated,
Thanks
XtriFe said:
Guys, I have a weird issue with my X1. Im using the Energy Rom (6.5), installed a few things (including the SE Icon to replace the Windows one on the start menu), did a soft reset and everything was going ok.
After fiddling about with the phone some more, on the next soft reset i found that the Battery Icon on the taskbar would not update, see the attached screenshot, says the phone is being charged but the phone isnt even plugged to anything. Seems like it only shows the battery status of when i turn on the phone, then stays that way until windows starts again.
Any help would be appreciated,
Thanks
Click to expand...
Click to collapse
What did you install?
That usually happens to me when I install a taskbar that's missing a key .dll file. I think there's a bugfix for it in the apps/themes section, but generally when I run across this problem, I just uninstall the taskbar and install a different one with a working battery meter
harveydent said:
What did you install?
That usually happens to me when I install a taskbar that's missing a key .dll file. I think there's a bugfix for it in the apps/themes section, but generally when I run across this problem, I just uninstall the taskbar and install a different one with a working battery meter
Click to expand...
Click to collapse
Harvey is right...It's a known issue, having troubles if we install a custom Taskbar over another Icon set. Same applies when installing a custom Volume control over a custom Taskbar....
So just uninstall the Custom Taskbar...
Many thanks Harvey Dent and Xperiencer, I will do as suggested.