markum wrote:I normally reject all incoming callers I know and redial them immediately since I have a flatrate. It would be a useful function if this could be kind of automated.
Ideas:
a) have an additional icon on the lock screen for those I want to reject and call back
b) have an additional mark to addressbook entries which would depending on the active profile or time of day automatically redial entries after I have rejected them. May be this could be realised through an addressbook group.
thanks for the idea, not sure, how much DWC users will have a REAL FLATRATE, and how much users will need such kind of functionality ...
anyhow the idea itself is ok
and:
a) the reject and call back is a android based system application which can't be modified (or don'T know how), and is on several devices different + on almost every android version
b) in call filter, you can set to reject contacts (but then they will be rejected all the times). A automatical redialing of rejected contact ... don't how this should work.
the only thing, what i can think, that can be working is: a call filter application, which reject contacts, and then recall this contact.
maybe this can be done via an application: "Tasker" or perhaps there is such "extended call filter" application anywhere.
but to make DWC like an huge call filter application - not sure, if this will be a good idea, because then the DWc will consume a lot of MEM, because all call filters must be hold in memory and the application will lost focus con contacts & phone.
---------
and if implementing: there a lot of questions for handling:
if a contact will always rejected:
1.) should the contact be rejected all the time ? 24hoursx7days ? amnd automatically call them 5seconds later ?
2.) What happen if my phone is not on my side ?
3.) How can be sure, that the phone is in my hand ?
4.) What happen if contact is not avialible (wrong number, out of service, routed to mailbox, busy, ....) ?
5.) What happen if contact is not avialible (wrong number, out of service, routed to mailbox, busy, ....) ?
and there are much more questions ... so - not sure if this is so easy to implement, that it is useful for any DWC user ...
But i will think about and discuss such kind of idea. Thanks for your interesttng idea
cu camel