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.
[do it via TASKER]reject and automaticall redial function
Re: reject and automaticall redial function
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 ...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.
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
Re: reject and automaticall redial function
I agree, this feature is great for the poster for sure, but would be best done via the Tasker application, it is very easy and im sure the tasker forum users will show you how.
Tasker Context: phone call (filter contact= "" (blank for every contact number) )
Task Actions: Hangup call (maybe save number for redailing); then wait (3 seconds); then redial last number;
done.
Tasker Context: phone call (filter contact= "" (blank for every contact number) )
Task Actions: Hangup call (maybe save number for redailing); then wait (3 seconds); then redial last number;
done.
Re: reject and automaticall redial function
this sounds great and is exact what i meansonhy wrote:I agree, this feature is great for the poster for sure, but would be best done via the Tasker application, it is very easy and im sure the tasker forum users will show you how.
Tasker Context: phone call (filter contact= "" (blank for every contact number) )
Task Actions: Hangup call (maybe save number for redailing); then wait (3 seconds); then redial last number;
done.
and save DWC to be not getting an overkill
Re: reject and automaticall redial function
@markum: do you really like to see it in DWC in future - or is it ok, to use an extra application which only concentrate on special call filtering ?
(i'm sure, DWC will need a lot of time to use this better as apps, which are concentrating on development only doing call filtering)
because then i would change the subject to "[Disagree]Call Filter - reject and automaticall redial function" or will move it to questions.
please let me know.
cu camel
(i'm sure, DWC will need a lot of time to use this better as apps, which are concentrating on development only doing call filtering)
because then i would change the subject to "[Disagree]Call Filter - reject and automaticall redial function" or will move it to questions.
please let me know.
cu camel
Re: reject and automaticall redial function
I just had a look at tasker. I am not sure if the task can be acomplished using this app. I have not found a way to choose the number of the last incoming call to automatically make a call to. I also get the impression that tasker although it is very specialised may not be able to make selections according to network, country code. May be an implementation in DWC would not automatically reject calls, but automatically on reject do the redial if certain conditions (being in the home country network and the contact being in a certain addressbook group, having the country code of the country).camel wrote:@markum: do you really like to see it in DWC in future - or is it ok, to use an extra application which only concentrate on special call filtering ?
(i'm sure, DWC will need a lot of time to use this better as apps, which are concentrating on development only doing call filtering)
because then i would change the subject to "[Disagree]Call Filter - reject and automaticall redial function" or will move it to questions.
please let me know.
Markum