Page 1 of 2 12 LastLast
Results 1 to 25 of 26
Like Tree1Likes
  1. jrdatrackstar1223's Avatar
    Member

    Posts
    654 Posts
    Global Posts
    966 Global Posts
       #1  
    I was wondering if there were any bugs that were annoying enough to make people roll back from Mango to NoDo, particularly those using the HTC Arrive? There are just a small few that make the experience a little worse for me on the Arrive, and although the new features are great, these bugs (like laggier IE Explorer or Speech-To-Text that usually has problems translating my speech) almost make the update worthless without new apps.
  2. thed's Avatar
    Member

    Posts
    993 Posts
    #2  
    I've considered rolling back to NoDo because of a bug that's popped up a few times on my phone. Sometimes when I want to respond to an email I'll tap the respond button and when I select reply/forward/reply all the dialog goes away and nothing else happens. So if I want to reply I have to copy the text and paste it into a new email.

    Restarting the phone doesn't fix the bug, but it always goes away on its own after a day or 2 so I haven't had to roll back. But man is it annoying. I haven't seen anyone else complain about this. Hopefully it's fixed in the real update (I'm running 7712).
  3. jrdatrackstar1223's Avatar
    Member

    Posts
    654 Posts
    Global Posts
    966 Global Posts
       #3  
    yea i'm runnin build 7720, and the biggest bugs for me is the virtual keyboard is worse IE 9 seems much laggier and stuff....

    Also, TellMe for speech recognition hardly works for texting...
  4. dirtbikr's Avatar
    Member

    Posts
    17 Posts
    #4  
    I haven't had any problems with the speech recognition, it usually surprises me actually.

    IE is definitely faster for me than on NoDo, at least browsing is. I don't know about start up time, but I never wait around for it.

    The only real "bug" that I have is when I go into a text to reply, about 50% of the time the keyboard starts in lowercase, so if I start typing it won't auto capitalize the first word of the first sentence. The rest of the way through the text it works fine. I have found that if I notice the keyboard is in lower case before I start typing, I can press the delete button and the characters all jump up to caps like they should be. This also happens sometimes when I pull the keyboard out and start typing. Mildly annoying, but the only bug I have honestly found in Mango compared to NoDo.
  5. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #5  
    Strange. I'm not experiencing these issue.

    The only thing I'm worried about is if there's going to be some problem when I try to revert back to Nodo when the carrier version of Mango is out.
  6. ninjaap's Avatar
    Member

    Posts
    2,454 Posts
    Global Posts
    2,466 Global Posts
    #6  
    Quote Originally Posted by Reflexx View Post
    Strange. I'm not experiencing these issue.

    The only thing I'm worried about is if there's going to be some problem when I try to revert back to Nodo when the carrier version of Mango is out.
    You don't have to revert back to NoDo. I asked @zunesupport and @winphonesupport via Twitter and they both replied that all phones will get updated even ones running Mango Beta (I specifically asked about 7720 RTM).
  7. jrdatrackstar1223's Avatar
    Member

    Posts
    654 Posts
    Global Posts
    966 Global Posts
       #7  
    Quote Originally Posted by dirtbikr View Post
    I haven't had any problems with the speech recognition, it usually surprises me actually.

    IE is definitely faster for me than on NoDo, at least browsing is. I don't know about start up time, but I never wait around for it.

    The only real "bug" that I have is when I go into a text to reply, about 50% of the time the keyboard starts in lowercase, so if I start typing it won't auto capitalize the first word of the first sentence. The rest of the way through the text it works fine. I have found that if I notice the keyboard is in lower case before I start typing, I can press the delete button and the characters all jump up to caps like they should be. This also happens sometimes when I pull the keyboard out and start typing. Mildly annoying, but the only bug I have honestly found in Mango compared to NoDo.
    For the IE bug, it isn't that pages load slower; it's when you rotate the screen and stuff. In NoDo, the animation would be so smooth that it isn't funny. In Mango, it kinda of just stutters when it does it. I've tried reflashing a couple of times to see if that's the problem, but I dont' think that's it.

    Also, TellMe works BUT it doesn't work like if there is a HINT of noise other than your voice surrounding you. I thought Microsoft was promoting this great noise cancellation feature, but apparently they didn't put it in Windows Phone (for the record, I push "Go" when I'm done speaking) because half the time it does something TOTALLY OPPOSITE of what I said (I'm American and have no accent). When it's quiet, it works. When there is a hint of wind or anything it doesn't work (for me at least). Then there are times it works SPOT ON and, other times (usually), when it's just off when it comes to speech-to-text.
  8. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #8  
    Quote Originally Posted by jrdatrackstar View Post
    For the IE bug, it isn't that pages load slower; it's when you rotate the screen and stuff. In NoDo, the animation would be so smooth that it isn't funny. In Mango, it kinda of just stutters when it does it. I've tried reflashing a couple of times to see if that's the problem, but I dont' think that's it.

    Also, TellMe works BUT it doesn't work like if there is a HINT of noise other than your voice surrounding you. I thought Microsoft was promoting this great noise cancellation feature, but apparently they didn't put it in Windows Phone (for the record, I push "Go" when I'm done speaking) because half the time it does something TOTALLY OPPOSITE of what I said (I'm American and have no accent). When it's quiet, it works. When there is a hint of wind or anything it doesn't work (for me at least). Then there are times it works SPOT ON and, other times (usually), when it's just off when it comes to speech-to-text.
    Keep using it!

    I hope everyone keeps using TellMe. The more that people use it, the better that it will get.

    Especially use it for things like Bing Search. Because it will actually compare what you said to what search option you choose. Or if you make a correction in the text field, that data will be sent to MS so that they could improve TellMe accuracy.
  9. ethylove's Avatar
    Member

    Posts
    38 Posts
    Global Posts
    126 Global Posts
    #9  
    I went back to NoDo just to make sure i could prior to the carrier release and immediately went back to mango. i havent had any problems with is, including speech to text.
  10. Luisraul924's Avatar
    Member

    Posts
    785 Posts
    Global Posts
    791 Global Posts
    #10  
    Quote Originally Posted by ninjaap View Post
    You don't have to revert back to NoDo. I asked @zunesupport and @winphonesupport via Twitter and they both replied that all phones will get updated even ones running Mango Beta (I specifically asked about 7720 RTM).
    That's awesome! If true then it saves me a helluva lot of trouble lol :D
    Quote Originally Posted by ethylove View Post
    I went back to NoDo just to make sure i could prior to the carrier release and immediately went back to mango. i havent had any problems with is, including speech to text.
    ethylove, you should read ninjaap's post...
  11. jrdatrackstar1223's Avatar
    Member

    Posts
    654 Posts
    Global Posts
    966 Global Posts
       #11  
    So is TellMe supposed to get more accurate over time? I'm considering just leaving Mango on there, although the IE choppiness really gets to me because I feel like I'm using Android again. It's still pretty smooth, but not as smooth as it was on NoDo.

    I just finished using TellMe for a trip to the store and it worked flawlessly for a while. Then, it just stopped working well and started reading back things back weren't close to what I said. For example: I would say "Find Meijer" and it would return "Finding Porn". I'm like wtf!? This was with noise in the background (wind from the window down). However, there were other times when keeping the window down with wind wouldn't mess up the results at all.

    As far as Microsoft implementing changes and to keep using TellMe for Microsoft to improve it......we won't see those improvements until Tango or Windows Phone 8....guarantee it =(

    I just wish Windows Phone would speed up a bit in the things that need improved...
  12. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #12  
    TellMe will improve as it gathers data. Well, as long as you allowed it to transmit data. Which you pretty much have to in order for it to work.

    What happens is that your audio is transmitted to a server that analyses that and returns a response to your phone. With Bing search, it will also transmit corrections you make to the text. So those corrections are sent to the database.

    As more and more and more users use it, the audio patterns will get more and more accurate.

    And since it's not actually your phone analyzing the data, you don't have to wait for an OS upgrade to benefit from the voice recognition improvements. It's the servers that keep getting better.
  13. bear_lx's Avatar
    Member

    Posts
    811 Posts
    Global Posts
    1,319 Global Posts
    #13  
    i rolled back, but i heard that you would need to be on nodo to get official release of mango.. still not inclined to believe otherwise... if it voids warranty. from past experience on android phones, you couldnt get updates if you messed with the os at all... we shall see
    WP Central - Super Member
    Xbox Live GamerTag - Bear lx
  14. ninjaap's Avatar
    Member

    Posts
    2,454 Posts
    Global Posts
    2,466 Global Posts
    #14  
    Quote Originally Posted by DizzyMaker View Post
    i rolled back, but i heard that you would need to be on nodo to get official release of mango.. still not inclined to believe otherwise... if it voids warranty. from past experience on android phones, you couldnt get updates if you messed with the os at all... we shall see
    Your concerns are certainly understandable and I'm sure many feel the same. I pretty much asked the people who are ultimately responsible for releasing and supporting the update. And I pretty much told them I am running 7720 RTM, but no threats or corporate mumbo jumbo speach about voiding my warranty like one usually expect.

    Here is my conversation with them: Updating to Official Mango from 7720 RTM | Windows Phone Forums

    I'm not trying to convince anyone. Just wanted to put it out there. Sorry for hijacking the thread OP...
  15. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #15  
    Quote Originally Posted by ninjaap View Post
    Your concerns are certainly understandable and I'm sure many feel the same. I pretty much asked the people who are ultimately responsible for releasing and supporting the update. And I pretty much told them I am running 7720 RTM, but no threats or corporate mumbo jumbo speach about voiding my warranty like one usually expect.

    Here is my conversation with them: Updating to Official Mango from 7720 RTM | Windows Phone Forums

    I'm not trying to convince anyone. Just wanted to put it out there. Sorry for hijacking the thread OP...
    It does make sense though.

    I'm currently running Mango RTM 7.10.7720.68

    So I assume that once AT&T gets through with it, they'll only be adding stuff. Not removing stuff. To keep it compatible with future MS RTM updates.

    That would mean a version number above the RTM one. So I would guess that it would just add in the stuff you're currently missing.

    Oh.. and I hope you don't mind. I sent a follow request to your Twitter. So when you get something from @WinningGuy, that's me.
  16. ninjaap's Avatar
    Member

    Posts
    2,454 Posts
    Global Posts
    2,466 Global Posts
    #16  
    Quote Originally Posted by Reflexx View Post
    It does make sense though.

    I'm currently running Mango RTM 7.10.7720.68

    So I assume that once AT&T gets through with it, they'll only be adding stuff. Not removing stuff. To keep it compatible with future MS RTM updates.

    That would mean a version number above the RTM one. So I would guess that it would just add in the stuff you're currently missing.

    Oh.. and I hope you don't mind. I sent a follow request to your Twitter. So when you get something from @WinningGuy, that's me.
    Plus the devs who are on the same version need a way to update to Mango. I doubt MS expects them to revert back to NoDo.

    You follow me? I follow you too ;)
  17. jrdatrackstar1223's Avatar
    Member

    Posts
    654 Posts
    Global Posts
    966 Global Posts
       #17  
    Quote Originally Posted by Reflexx View Post
    TellMe will improve as it gathers data. Well, as long as you allowed it to transmit data. Which you pretty much have to in order for it to work.

    What happens is that your audio is transmitted to a server that analyses that and returns a response to your phone. With Bing search, it will also transmit corrections you make to the text. So those corrections are sent to the database.

    As more and more and more users use it, the audio patterns will get more and more accurate.

    And since it's not actually your phone analyzing the data, you don't have to wait for an OS upgrade to benefit from the voice recognition improvements. It's the servers that keep getting better.
    But how long do you think it will take before we see the improvements? And as far as the corrections, the only time I am able to make corrections is when I use speech-to-text for texting. Are you saying that when I say, for example, "Pizza Hut" and it returns and searches for "Putt" that if I correct "Putt" to "Pizza Hut" in the search bar when the search results come back that Microsoft will be able to see that? If this is not true, when do you make these corrections?
  18. jalb's Avatar
    Member

    Posts
    751 Posts
    Global Posts
    814 Global Posts
    #18  
    How can you tell what version of Mango you have on?
  19. TheWeeBear's Avatar
    Retired Moderator

    Posts
    5,293 Posts
    Global Posts
    5,295 Global Posts
    #19  
    Quote Originally Posted by jalb View Post
    How can you tell what version of Mango you have on?
    Just go to Settings / About / More, jalb. :) (OS Version)

    Mine is 7.10.7720.68 (RTM)

    .........HANDSET: Nokia Lumia 920
    .........COUNTRY: Scotland UK
    .........NETWORK: 3 UK
  20. theefman's Avatar
    Member

    Posts
    2,347 Posts
    Global Posts
    2,348 Global Posts
    #20  
    Quote Originally Posted by ninjaap View Post
    Plus the devs who are on the same version need a way to update to Mango. I doubt MS expects them to revert back to NoDo.

    You follow me? I follow you too ;)
    Actually MS already stated to devs that they WOULD be required to revert back to Nodo to update to the official Mango release. All part of the multiple backup messages displayed when accepting the beta invite. I think we've all forgotten that the beta was supposed to be for devs to build Mango apps with, and not as an updatable beta.

    Plus I've had conversations with Zune support to reset the device count on my Zune account due to the repeated exchanges I went through with my DVP and they couldnt understand my problem. Frankly I'm not convinced they know what they are talking about. You could end up being alright and be able to go from RTM to carrier final but its 50-50, I think.
  21. jalb's Avatar
    Member

    Posts
    751 Posts
    Global Posts
    814 Global Posts
    #21  
    Quote Originally Posted by TheWeeBear View Post
    Just go to Settings / About / More, jalb. :) (OS Version)

    Mine is 7.10.7720.68 (RTM)
    Thank you! Mine is 7.10.7712.60

    Do you suppose I would need to update to the 20.68 (RTM) in order to avoid having to roll back to nodo when the actual Mango update comes out?
  22. ninjaap's Avatar
    Member

    Posts
    2,454 Posts
    Global Posts
    2,466 Global Posts
    #22  
    Quote Originally Posted by theefman View Post
    Actually MS already stated to devs that they WOULD be required to revert back to Nodo to update to the official Mango release. All part of the multiple backup messages displayed when accepting the beta invite. I think we've all forgotten that the beta was supposed to be for devs to build Mango apps with, and not as an updatable beta.

    Plus I've had conversations with Zune support to reset the device count on my Zune account due to the repeated exchanges I went through with my DVP and they couldnt understand my problem. Frankly I'm not convinced they know what they are talking about. You could end up being alright and be able to go from RTM to carrier final but its 50-50, I think.
    But doesn't RTM mean return to manufacturer, meaning it is no longer in Beta? From what I understand if you're not carrier locked, this is pretty much the version you're going to receive, plus the drivers and whatever the manufacturer needs to add. So it doesn't really make sense to go back to NoDo if you already have the final copy. Of course, I'm no engineer so I could be totally wrong.
  23. theefman's Avatar
    Member

    Posts
    2,347 Posts
    Global Posts
    2,348 Global Posts
    #23  
    Quote Originally Posted by ninjaap View Post
    But doesn't RTM mean return to manufacturer, meaning it is no longer in Beta? From what I understand if you're not carrier locked, this is pretty much the version you're going to receive, plus the drivers and whatever the manufacturer needs to add. So it doesn't really make sense to go back to NoDo if you already have the final copy. Of course, I'm no engineer so I could be totally wrong.
    Could well be. But with the Chevron WP7 thing MS claimed those devices were out of sync with the normal update process, and no OEM is expecting to build an update for devices running RTM. So same thing could happen here. Or not. Guess as long as someone is ok with going back to Nodo if it doesnt upgrade to final its not a real problem.
    ninjaap likes this.
  24. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #24  
    Quote Originally Posted by jrdatrackstar View Post
    But how long do you think it will take before we see the improvements? And as far as the corrections, the only time I am able to make corrections is when I use speech-to-text for texting. Are you saying that when I say, for example, "Pizza Hut" and it returns and searches for "Putt" that if I correct "Putt" to "Pizza Hut" in the search bar when the search results come back that Microsoft will be able to see that? If this is not true, when do you make these corrections?
    Yes. If you have the option where you share your data to MS on, then it will do that.

    I work at a company that uses speech recognition. So the topic about Microsoft's methods has come up.
  25. Reflexx's Avatar
    Member

    Posts
    3,942 Posts
    #25  
    Quote Originally Posted by theefman View Post
    Could well be. But with the Chevron WP7 thing MS claimed those devices were out of sync with the normal update process, and no OEM is expecting to build an update for devices running RTM. So same thing could happen here. Or not. Guess as long as someone is ok with going back to Nodo if it doesnt upgrade to final its not a real problem.
    I believe with the Walsh update (I think that's the one you're referring to), it was taken from a full carrier release. So the version number was actually higher than the MS Release To Manufacturer update.

    There was extra stuff on there already. Extra stuff that would interfere with the extra stuff your carrier was trying to put on your phone.
Page 1 of 2 12 LastLast

Posting Permissions

B