Norton Mobile Utilities Public Beta

[klingoncowboy4]

Hi

I love this app but have a few suggestions.

I am on Rogers Wireless and they have a service called My5 (I know other carriers are offering similar services) where you have unlimited calling and txting to any 5 Canadian Numbers of your choice (I am actually getting MY10 so its 10 numbers).  Currently after every call the app is alerting me that I have almost used all my minutes.  The problem is that 80% of the minute I used are for MY5 contacts and as such will not be counted on my bill.  I suggest that maybe we can have an ignore list where you can add numbers to ignore.

Similary I would like to be able to program a schedualed ignore time for evenings and weekends.

I also have unlimited txting so having the ability to turn off all txting alerts would be nice.  For now I just set the "unlimited incomming" on and then set my monthly total so large that it will never trigger an alert.

[Andmike]

Hi klingoncowboy4.

Welcome to the community, and I'm delighted that you like Norton Mobile Utilities (NMU).

Thanks for the feedback.

The request for excluded numbers has been made before so Norton may introduce it in a future version but I am also aware that there are such a large number of different options out there that Norton would probably find it difficult to justify being able to handle all options.  I'm sure they will take your request into account but you will just have to wait and see what develops.  Stay tuned to this forum and I would expect you to be one of the first to hear of any changes.

The same remarks go for the evening and weekend options.

As for the unlimited texts; if you go to Usage Settings and select "Total Monthly SMS", then clear the display (so that it shows no figures, not even a zero), then hit OK.  I think you will then have got what you want.  It should record the number of messages but will not set any alert.  In effect you will have set, no alert level.  You can also leave it as you have if you prefer.

Sorry I only have one solution to offer at the moment but I hope it helps.

Let us know if you have any other thoughts or problems with NMU.

Good luck.

[erik_carlstrom]

I'd follow Mike's steps to set the number to "unlimited" for text messages.  

As to items like "My 5" etc.  Unfortunately for us to do a perfect job of handling special free calls like a special list of numbers, all mobile numbers, mobile numbers of the same carrier, etc would require a partnership with your carrier.  Right now, since the product is still in Beta that's just not possible.  As to an exclusion list, I'll bring the idea back up again and we'll when we can get to this.  

[Andmike]

Erik you advised klingoncowboy4 to 

"follow Mike's steps to set the number to "unlimited" for text messages."

I have just been looking at this again and what I am sure used to work no longer seems to.  I am sure that on older versions of NMU if I set say the data limit to blank then the display showed a number but that incremented up with use and no alarm was raised.  Now I can enter blank in any of the usage limits but if I back out and return a numerical figure is entered as if I had entered it.  Now I cannot test if these limits are fixed or if they will in fact also increment up should my usage approach them as they are higher than I expect to use on my device at the moment, but what appeared to be a useful feature appears to have gone.

The facility I thought we had but now seem to have lost is - to be able not to set a limit on some usage items and just have NMU track the usage.  Now I can probably achieve that by setting a ridiculously high limit but then the visual displays will appear blank or virtually so.  Previously the bar showed progression against a marked scale and the scale changed when usage increased, this was nice but appears to have gone. 

Am I making myself clear and does anyone else recognise the issue?

[Andmike]

I have just tried out an older version of NMU (1.0.2.77) and found that the data limits seemed to reset to numerical limits on that as well.  So either I was wrong in my understanding of what was happening with earlier versions (quite possible) or the change seems to have been made prior to 1.0.2.77.  :-(

[erik_carlstrom]

This looks like something that might have been introduce in build 77.  I'll let the team know.