Sign up for the FREETell Membership and receive benefits that include the digital edition of Tell Magazine sent straight to your inbox, product giveaways, coupons and much more!
It looks like the new update to the Motorola Cliq this week has users seeing more problems than before. The new update, 1.3.18, has a number of users going to the T-Mobile forums to complain of various issues that their phones are now having.
Problems users seem to be experiencing include the inability to log into MOTOBLUR, Bluetooth connectivity issues, SMS lagging and crashing, problems with the virtual keyboard, dimmed displays and reseting the clock to Linux “0″ (7 p.m. December 31, 1969). A moderator on the T-Mobile forums has stated that the issues are being passed along to those who can fix them. In the mean time, the mod advises against master resetting your phone if your OTA didn’t download or caused problems.
Hopefully the issues can be fix relatively soon, having a bricked, or near bricked phone can not be fun. The issue seems like it would lie with Motorola, though like the Danger problems, it’ll likely come back to T-Mobile. It is sad to see the carrier see so many issues that really can’t be fixed without relying on other companies. At least this time there’s an option to not experience the issues, at least assuming you didn’t download the update yet.
[UPDATE] Motorola seems to have a few ways of fixing the issues users have found with the recent OTA update. Users encountering force closings for SMS, should be able to fix the problem by clearing out their inboxes. Also, users will be able to fix the update overall by sideloading the update, it seems. The information for that can be found here.
It looks like the new update to the Motorola Cliq this week has users seeing more problems than before. The new update, 1.3.18, has a number of users going to the T-Mobile forums to complain of various issues that their phones are now having.
Problems users seem to be experiencing include the inability to log into MOTOBLUR, Bluetooth connectivity issues, SMS lagging and crashing, problems with the virtual keyboard, dimmed displays and reseting the clock to Linux “0″ (7 p.m. December 31, 1969). A moderator on the T-Mobile forums has stated that the issues are being passed along to those who can fix them. In the mean time, the mod advises against master resetting your phone if your OTA didn’t download or caused problems.
Hopefully the issues can be fix relatively soon, having a bricked, or near bricked phone can not be fun. The issue seems like it would lie with Motorola, though like the Danger problems, it’ll likely come back to T-Mobile. It is sad to see the carrier see so many issues that really can’t be fixed without relying on other companies. At least this time there’s an option to not experience the issues, at least assuming you didn’t download the update yet.
[UPDATE]
Motorola seems to have a few ways of fixing the issues users have found with the recent OTA update. Users encountering force closings for SMS, should be able to fix the problem by clearing out their inboxes. Also, users will be able to fix the update overall by sideloading the update, it seems. The information for that can be found here.
Read [Boy Genius Report]
Related Posts