Spam detection software, running on the system "azul3.aguilardelgado.com", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Great! So there is a open end... At least we can try to 
implement
   it and include into the main release next version. That's one solution. [...]
   

Content analysis details:   (7.8 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 1.0 EXTRA_MPART_TYPE       Header has extraneous Content-type:...type= entry
 3.1 FH_HOST_EQ_DYNAMICIP   Host is dynamicip
 1.5 HTML_IMAGE_ONLY_28     BODY: HTML: images with 2400-2800 bytes of words
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.5 RCVD_IN_PBL            RBL: Received via a relay in Spamhaus PBL
                            [83.39.64.181 listed in zen.spamhaus.org]
 1.6 RCVD_IN_SORBS_DUL      RBL: SORBS: sent directly from dynamic IP address
                            [83.39.64.181 listed in dnsbl.sorbs.net]
 0.1 RDNS_DYNAMIC           Delivered to trusted network by host with
                            dynamic-looking rDNS
 0.0 DYN_RDNS_AND_INLINE_IMAGE Contains image, and was sent by dynamic
                            rDNS

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

--- Begin Message ---
Great! 

So there is a open end... At least we can try to implement it and
include into the main release next version.

That's one solution. 

I will try to take a look also to the ndk toolkit. Maybe is there other
solutions.

Thank you!








____________________________________




  Gonzalo Aguilar Delgado
  Consultor CRM - Ingeniero en
Informática

        M. +34 607814276







On mié, 2009-07-01 at 14:46 -0400, Mark Murphy wrote:

> Gonzalo Aguilar Delgado wrote:
> > I'm sorry I didn't explained myself...
> > 
> > What I wanted to say is that It must be another way to hang an outgoing
> > call. Other than the hang button in the phone.
> > Because others are doing it.
> 
> The only example you have cited is a firm (Huwaei) that presumably made
> changes in the firmware to accomplish their ends.
> 
> > So the question still remains. What is the way to hang an outgoing call?
> 
> Via the SDK, you cannot hang up an outgoing call.
> 
> > And I don't find any reason to not allow this.
> 
> It may not be a question of "allow", but a question of engineering time
> to implement the capability in the SDK. Believe it or not, Google does
> not have 999 engineers working on building Android. Hence, you are
> welcome to make a patch that implements this feature and submit it to
> http://source.android.com. Or, hire somebody to make a patch. Or, raise
> funds to hire somebody to make a patch.
> 
> At minimum, I would think it needs a permission, so the user can decide
> whether or not a specific application can forcibly hang up the phone.
> But, hey, that's just me...
> 
> > So... I think this is the group to ask about how to manage this.
> 
> For making changes to the Android open source code, you will be better
> served with a list that pertains to the Android open source code:
> 
> http://source.android.com/discuss
> 

<<attachment: yo-48x48-bw.jpg>>


--- End Message ---

Reply via email to