.
Thanks again,
Dave Smith, PE
Double Encore, Inc.
On Sunday, April 13, 2014 12:51:07 PM UTC-6, Doug wrote:
Bear in mind that anything could be causing main thread delays. It could
be your code. It could be other threads in your app's process. It could
be other apps running on the device
Hello all -
I am working on an application that is using Choreographer and OpenGL to
render flash patterns on the display. Our GL calls are quite simple,
simply toggling the display back and forth between white and black using
glClearColor() based on the frame time and status of the pattern
for editing, or to indicate that using
ACTION_OPEN_DOCUMENT should include a branch check on FLAG_SUPPORTS_WRITE
to determine if the edit can happen in place, or if ACTION_CREATE_DOCUMENT
will need to be used anyway to create a new file for the edit changes.
Thanks again,
Dave Smith
@devunwired
,
suggesting that developers use ACTION_OPEN_DOCUMENT for in-place editing
doesn't seem like a viable approach.
Dave Smith
@devuwired
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers
(a Commons
Guy) wrote:
On Wed, Nov 7, 2012 at 10:38 AM, Dave Smith dasmi...@gmail.comjavascript:
wrote:
In my mind, the old devices that don't understand the sw qualifier
should
just ignore its existence and the two directories should just look like
large and xlarge.
If a directory has
I am trying to develop an efficient method of including resource qualifiers
to appropriately select the layouts (and other resources really) for
handsets, small tablets, and large tablets. To properly support devices on
both sides of Android 3.2, when smallest width was introduced, I had hoped
I have an application that communicates with a Service in a remote process
using the Messengerinterface. Here is the basic architecture of how things
are set up:
- The application generates several Operation objects that require
access to the service.
- Each Operation contains a
. I will take a look at this and the workaround you
proposed as well.
Thanks again!
Dave Smith
@devunwired
On Thursday, August 30, 2012 4:12:02 PM UTC-6, Dianne Hackborn wrote:
It is true that sending a messenger across processes will require holding
a GREF on it for the other process
Which is why we will all be eagerly watching the bug that Mark filed in
anticipation :)
Cheers,
Dave Smith
@devunwired
On Wednesday, August 29, 2012 3:24:50 AM UTC-6, Romain Guy (Google) wrote:
Note that using software layers comes at a performance and memory cost.
On Tue, Aug 28, 2012
will still work as expected. I will update the gist example
when I have a spare moment with some discussion, and I have starred the
issue Mark created (you should do the same).
Cheers,
Dave Smith
@devunwired
On Monday, August 27, 2012 2:29:20 AM UTC-6, Thesalan wrote:
Hi!
I started Android
It's too early to tell at this point, but the 10.8.1 update seems to have
helped quite a bit. I'm not longer needing to play USB Port roulette in
order to get the device to pick up. At least for now.
--
You received this message because you are subscribed to the Google
Groups Android
Macbook Pro, and it definitely does. Symptoms are the same regardless of
device.
On Friday, August 10, 2012 4:02:33 PM UTC-6, bob wrote:
I have the Galaxy Tab 10.1, and it doesn't give me any trouble. Are you
sure it gives you trouble?
Also, are you on Macbook Air or Pro? I'm on Pro.
This definitely does help, but only for 1-2 times; then I have to move the
port again. This is definitely faster than rebooting the devices, though,
so this will be my new go-to workaround.
It just feels like there's a bug somewhere in how it picks up connected
devices, or how it reads the
Galaxy Tab 10.1, Nexus 7, Droid 2, Droid Intercept; I'm fairly confident it's
not device/manufacturer specific. Wondering if there's a USB cache I can
clear...
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
I noticed that, as soon as I upgraded to Mac OS Mountain Lion (10.8) I have
been unable to reliably get any of my devices to connect with ADB (Galaxy
Nexus, Nexus S, HTC EVO 4G, just to name a few). It can take upwards of
10-15 cable re-plugs, re-starts of the ADB server, and toggling USB
As an addition to this, I have noticed that I can almost always get the
devices to detect if I power them down and then back up while still
connected to USB. The problem arises trying to get ADB to pick them up if
they are connected while alive.
--
You received this message because you are
Can an Activity still have read/write access to an SD card after it
has been mounted to USB storage (connecting USB and selecting Mount
from the resulting notification screen). In other words, does
mounting the SD card lock out system access until USB is disconnected.
I need to create a live
Hi all -
I'm needing to get my hands on an unlocked device for some development
work, and I noticed that the ADP1 is supposedly out of stock until
(maybe) early next month. I know someone who is wanting to get rid of
their T-Mobile G1, and I'm curious if anyone out there has had
experience
18 matches
Mail list logo
