It should be noted that there is a spelling mistake in the code
version, this is how it should read:
IntentFilter mFilter = new IntentFilter
(android.intent.action.DATA_SMS_RECEIVED);
I typed it up in a browser and made the mistake.
Thanks.
On Mar 30, 11:24 am, thesquib thesq...@gmail.com wrote
Stoyan - the optimisation from the Jazelle is apparently not that good
anyway, partially because a software JVM performs all sorts of
optimisations on the fly.
On Apr 1, 8:42 am, Stoyan Damov stoyan.da...@gmail.com wrote:
Aha, maybe I wasn't clear enough. I very well understand that Android
Bugs and issues can be added and tracked at
http://code.google.com/p/android/issues/list
On Apr 1, 12:44 pm, Keith Wiley kbwi...@gmail.com wrote:
I believe there is a bug in Android's implementation of
Color.colorToHSV(). If you pass it fully desaturated color, it
assigns all three HSV
I have created a broadcast receiver statically by specifying it within
the Manifest, and I have also created the same broadcast receiver in
code and have registered it with the application context. The static
way works very well, but the dynamic way does not receive the expected
broadcast. It
I can confirm that joe.scheidegger information about data sms does
work on device. However, the port specified on the receiver does not
seem to matter.
Joe wrote:
receiver android:name=.YourBroadcastReceiver
intent-filter
action
android:name=android.intent.action.DATA_SMS_RECEIVED /
Sorry this was meant to be a reply to this thread:
http://groups.google.com/group/android-developers/browse_frm/thread/c51383cc8761ffd5?tvc=1q=sms+port
There was no reply button.
On Mar 26, 8:57 am, thesquib thesq...@gmail.com wrote:
I can confirm that joe.scheidegger information about data
Hi William,
Check out Canvas.Rotate, Canvas.Translate, Canvas.Restore, Canvas.Save
You can call Canvas.Rotate just before drawing the image and it will
be drawn on the rotated canvas.
On Mar 23, 10:25 am, William william.caine...@gmail.com wrote:
i also have the same problem when I want to
The optimisation part of proguard will likely break the conversion to
dalvik byte code. Obfuscating will be fine.
On Mar 9, 4:10 am, tovmeod tovm...@gmail.com wrote:
I searched the forum and it seems that most question in the area are
how to put it to work, my question is if it does make any
No information on this? I have been testing, and experimenting sending
messages to the G1 using a GSM modem and have made no progress.
On Feb 20, 4:31 pm, thesquib thesq...@gmail.com wrote:
What happens to messages sent to a device via a port directed SMS?
They are not *visibly* picked up
What happens to messages sent to a device via a port directed SMS?
They are not *visibly* picked up by the phone, and do not broadcast an
intent - so they seem to disappear into the ether. Is there some way
to receive a port directed SMS or are they discarded?
I believe the message is being sent
scAddress, short destinationPort, byte[]
data, PendingIntent sentIntent, PendingIntent deliveryIntent).
Specifying a port seems to do nothing, or if it does I don't see how
to extract the port number or define a specific broadcast receiver for
this port.
On Feb 16, 4:56 pm, thesquib thesq...@gmail.com
Is there already functionality similar to the push registry or
wireless messaging API in J2ME implemented in Android? Or at least
plans to do so? I have been looking at this issue for a while, because
in a corporate environment it is essential to be able to push
information out, or trigger
This thread is for reporting changes and bug fixes (or the lack of
fixes) to the new 1.1 SDK.
So far I have found:
Bug: android.graphics.Bitmap.getPixels and
android.graphics.Bitmap.getPixel still do not correctly function
(information is lost).
Feature missing: Playing sounds from input
Not officially supported, but is possible? How might we go about
using this unsupported redirection to GL canvas?
On Jan 6, 3:43 am, Mike Reed r...@google.com wrote:
Skia is a 2D engine for drawing to abitmap. However, there is
experimental support for a canvas that redirects its calls to
, 2009 at 1:19 PM, thesquib thesq...@gmail.com wrote:
This thread is for reporting changes and bug fixes (or the lack of
fixes) to the new 1.1 SDK.
So far I have found:
Bug: android.graphics.Bitmap.getPixels and
android.graphics.Bitmap.getPixel still do not correctly function
Thanks for your reply Mark. I realise that the best solution is to
collapse the hierarchy, however I am still interested to know the
cause.
On Dec 30, 9:04 am, Mark Murphy mmur...@commonsware.com wrote:
thesquib wrote:
I just wanted to add that I am interested in finding a way around
I have come across an interesting problem. If I have a class hierarchy
that is 32 deep and attempt to instantiate the 32nd one, the VM breaks
with a stack overflow. I take it this is expected - 32 seems like a
'magic' number. Debugging shows that the VM fails to load the class,
tries to throw and
17 matches
Mail list logo
