I have to travel today so I don't have that much time to write up these things in greater detail than this - apologies there. But here are two things that cropped up just yesterday that I think are issues with this new OTA.
- Going into vibrate mode. I usually do this simply by pressing the down-volume button until I get there. Well on two occasions I went to do so yesterday and found that I did eventually get into vibrate mode, but the phone didn't do its customary vibration to indicate it had gotten to that point, and when it WAS in vibrate mode I still had the silence indicator (musical note crossed out) in the notification bar. If I went in and put myself in vibrate mode from within the sound menu then it would go in properly.
- Did a reboot last night before going to bed. Set the phone in the charger base. This morning clicking on a URL in a tweet sent me to the default browser. I checked the default in the Applications menu and, sure enough, it had been set back to the default phone browser instead of to Dolphin. I've had Dolphin set to being the default browser for easily a year or more. Did not change the setting myself, and I didn't install anything new that could have done it for me.
Anybody seeing these things happen on their Bolts?
Sent from my magnificent HTC Thunderbolt using Tapatalk 2
- Going into vibrate mode. I usually do this simply by pressing the down-volume button until I get there. Well on two occasions I went to do so yesterday and found that I did eventually get into vibrate mode, but the phone didn't do its customary vibration to indicate it had gotten to that point, and when it WAS in vibrate mode I still had the silence indicator (musical note crossed out) in the notification bar. If I went in and put myself in vibrate mode from within the sound menu then it would go in properly.
- Did a reboot last night before going to bed. Set the phone in the charger base. This morning clicking on a URL in a tweet sent me to the default browser. I checked the default in the Applications menu and, sure enough, it had been set back to the default phone browser instead of to Dolphin. I've had Dolphin set to being the default browser for easily a year or more. Did not change the setting myself, and I didn't install anything new that could have done it for me.
Anybody seeing these things happen on their Bolts?
Sent from my magnificent HTC Thunderbolt using Tapatalk 2