- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So excited to finally receive the Nokia Amber update plus GDR2 for WIndows Phone 8 this week. Of the new features, we're supposed to have the ability to configure the phone to filter (block) calls from "unknown" or "private" (blocked) numbers. Allegedly we should also be able to add phone number to the block/filter list. Sadly none of this works. Anyone know if this is more VZW heavy handedness or if the feature simply doesn't work on any phone on any network?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems like its a Verizon thing. I have been asking on alot of forums about this, and am pretty ticked off that it doesnt work. With no apps on the windows phone that I can find to do this like on my old android device this was the best feature of the update for me. Rumors are its VZW "heavy handedness" as you put it as I guess they have a fee based service to block calls. Not sure if this is true but so far it seems to be affecting only VZW customers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have confirmed that SMS filtering DOES work. Call filtering (on the VZW network) does not. Swap the SIM card with that of another network and both automagically work! Call Verizon support and complain about this. They have a call filtering service they want to charge you for... of course they don't want this cooked into the phone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They don't charge you for blocking calls.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
demmo86rt wrote:
They don't charge you for blocking calls.
They don't charge you to MAKE a blocked call, that is true, but if you want to block calls from a specific number, that is a different story and they will gladly charge for that service.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can block up to five numbers free for 90 days via your on-line MyVerizon account. You can re-block them every 90 days as needed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tikibar1 wrote:
You can block up to five numbers free for 90 days via your on-line MyVerizon account. You can re-block them every 90 days as needed.
Which of course misses the point of this thread altogether. The firmware and OS of the phone support permanent blocking without needing to remember to call every 90 days. The Verizon Website is lacking on specifics but I do know there is a fee related to requestinting a permanent block. That of course would be no longer necessary if the phone capabilities were fully supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, the Free Block of up to 5 numbers doesn't allow you to block Private or Anonymous callers. Was very happy to see this feature added and very bummed to see it doesn't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In a nutshell I siad it was shameful for Verizon to disable the ams/call block feature. The reason: money.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any word if this is going to be fixed? Or is it in fact VZW working another cash grab?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had a conference call with VZW support and Nokia last week. NEITHER is taking blame but this is clearly a network (read Verizon) issue since it works on every other carrier. I was told this would be resolved in a future update.