wnapod

Recently, I had to do a hard reset when the X30 locked up. I suspected the recent installation of ICBar,although I had also reinstalled the Resco Audio Recorder after a long time of not using it. At any rate something caused it and now after getting it going again,especially when I've been using Tomtom Navigation vers 5.21 the bluetooth (and wifi if I was using it) lights keep blinking after turning the power button off. The screens dark but the lights keep flashing.Batteries end up running out much faster too,even when I don't see these lights flashing. Before all i had to do was hit the power button and everything went off. Is there a setting somewhere that could control this. Thanks

nonentity

I found it was very easy to get confused between bluetooth / wireless but some advice I found here really helped.

Basically I set button one - far left hand side of X30 - as WirelessPower in Start, Settings, Power. Now when I press this button both Wireless and Bluetooth come on but if I don't need Bluetooth I just switch it off using Bluetooth Manager on the system tray. When I want to switch Wireless off I just press button one again.

I appreciate that this doesn't answer why they don't turn off when you power down but it's maybe worth a try anyway.

non

wnapod

Thanks, but its a new problem that just started after some year of not happening. It's bizarre for the bluetooth to stay on when I power the thing down. Of course if the bluetooth light is showing its not powered down. The other day both the bluetooth light and wifi were glowing after I hit the power button. Still would like to find out whats going on.
Later, with the X30 seemingly off, I woke up to find the low battery light flashing. So apparently it is staying on?
Actuslly I think I may have stumbled onto the answer. It might have been an audio player's (Mort Player) setting of turning off the display after some seconds. That was just the behavior I noticed when the screen looked totally off but I found I could still hotsync. I took the program off and so far it seems normal. In its defense I did have that program on before the hard reset and didn't have that problem,so not sure what caused it to start.