Thread: Offical Bugs List with Sprint Touch Pro 2 - WinMob. 6.5 Update
View Single Post
  #180 (permalink)  
Old 03-21-2010, 01:30 AM
austin420's Avatar
austin420
lt cmdr of a garbage scow
Offline
Location: kansas city mo
  
Join Date: Dec 2008
Posts: 2,450
Reputation: 4305
austin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributionsaustin420 should be added to the payroll for their contributions
Mentioned: 30 Post(s)
Tagged: 0 Thread(s)
Re: Offical Bugs List with Sprint Touch Pro 2 - WinMob. 6.5 Update
Quote:
Originally Posted by popularbelief420 View Post
1. blue satin WAR theme WILL not only break your dial pad while on a call but it WILL Destroy the entire screen. if you need screen shots let me know so i can painstakingly reproduce it. it WAS NOT pretty.
2. i dunno if dis qualifies 4 a bug but i seriously had to link ALL my contacts pics to their facebook profile. (ex: choose favorite> edit contact> choose pic> choose facebook profile) took MAD long. i was dropping ill types of mighty updates and NEVER ever ever had to do this mundane task.
3. end calls hard key doesnt end calls.
4. you have to refresh the opera browser a few times to get it browse a link. very annoying
5. not feeling the RAM or the general speed (could be the bloatware)
Quote:
Originally Posted by black88mx6 View Post
On my first Sprint 6.5 flash w/out a hard reset my power button and end call key stopped working. I was thinking I was having a hardware problem. As soon as I did the hard reset, they both started working again.
also, i did a hard reset. i think it makes a world of difference.
Reply With Quote