You can make a separate workspace to test if that is a factor in the
problem you are experiencing.
On Jul 14, 11:14 pm, SChaser wrote:
> I have experienced the same problems. Deleting the workspace is not an
> option.
>
> Is there a way to reset it? I'd hate to have to back up an eclipse
> versio
Does your question 1 refer to the step in installation where you use
the AVD and SDK Manager to install build target packages? If so, you
can choose to install all of them without using up too much space on a
big machine. If you install all of the build targets you will be sure
to be compatible wit
On page 267 of Android Application Development, the AIDL-generated
code for APIDemos example is formatted for readbility and dissected,
and shows how calls within a process get short-circuited and do not
actually use IPC. Amazon doesn't allow posting links into "Look
Inside" previews of books, but
Android issue tracking is in the open, so the numbers are available to
anyone:
There have been a bit over 9000 issues reported. about 600 released
(fixed and shipped) and 600 for future release. It's hard to
characterize all combinations of issue type and status. For example,
there are 8 unreprodu
icons, and that's just not worth it to change the look of
one icon on the fly.
On Jun 6, 9:26 pm, Dianne Hackborn wrote:
> On Sun, Jun 6, 2010 at 2:30 PM, Zigurd wrote:
> > If you can't send ACTION_PACKAGE_CHANGED, how are alternative markets/
> > installers supposed to wo
hange icons.
On Jun 6, 2:40 pm, Dianne Hackborn wrote:
> On Sun, Jun 6, 2010 at 6:44 AM, Zigurd wrote:
> > I should add that you would have to get the launcher to update by
> > broadcasting an intent with the action ACTION_PACKAGE_CHANGED.
>
> You should not send this kind
I should add that you would have to get the launcher to update by
broadcasting an intent with the action ACTION_PACKAGE_CHANGED. But
that should be a general way to implement what Sense UI does by
changing app icons.
On Jun 5, 10:42 pm, Zigurd wrote:
> Try Live
> Wallpaper
Try Live Wallpapers:
http://developer.android.com/resources/articles/live-wallpapers.html
App icons are not accessible outside the launcher. At best, you might
be able to hack something by turning activity aliases on and off and
"changing" an app icon that way. That is, you might have an second a
o adb server-
strart"
Does that improve your results?
On May 31, 5:40 am, Ichi wrote:
> Well, I've tried all the solutions mentioned above, but none of them
> work for me...
> Is there any one ever tested Acer Liquid on Ubuntu 10.04?
>
> Still thanks for all you guys'
Gubatron's solution works, but necessarily because of the udev rules
file. He also has you restart the adb server as root. That, by itself
will work, but it is a workaround until you can figure out the correct
udev rules for your system.
I have a file named /etc/udev/rules.d/51-android.rules that
Yeah, I see that it specifies "debugging" as part of the goal of
setting up. And since running in the emulator is enough to validate
that the SDK is set up correctly, I see that consolidating the
instructions for running and debugging is a valid decision.
I also see that if you specify that "Setti
On the documentation page "Developing on a Device"
http://developer.android.com/guide/developing/device.html there may be
two errors in the section "Setting up a Device for Development."
First: To run (not debug) an app on a device, you do not need to set
the "debuggable" attribute in the manifest
Maybe an audible cue that they are about to navigate back out? But, as
others have said, that navigation should have no bad consequences, so
the user need not be aware of it.
While a "home" navigation in the option menu is not desirable, that
would be one way to enable your users to return to the
o out of their way today to try to make a touch-oriented UI work
> without a touch screen. That time would be better spent on improving the
> touch experience.
>
>
>
>
>
> On Wed, Apr 21, 2010 at 1:20 PM, Zigurd wrote:
> > All current Android phones have touch-sc
All current Android phones have touch-screens.
However, Android's UI is designed to be operated using the d-pad,
moving a "focus" and using a select button as well as by touch. I
think all the standard apps that are part of most Android phones can
work without touch.
If, for example, you consider
Handle the exception.
There is no guarantee that an Intent will get a match, and the
situation can change as the user adds and deletes applications.
Conceivably, matches could go away in future version of Android, or in
a port of Android with very different hardware than a phone. So even
if it wor
colin.t...@gmail.com posted the link to the documentation, above. If,
for some reason, that doesn't work on your Linux setup, you can try
this, in your tools, directory:
./adb kill-server
sudo ./adb start-server
Then start Eclipse.
--
You received this message because you are subscribed to the
When I wrote "I'm sure you are starting to see that what you thought
of doing was made intentionally difficult" I was referring the fact
that when you create an instance of LinearLayout, or any other class
in the View hierarchy, you have to specify a Context (an abstract
class) in the constructor o
I'm sure you are starting to see that what you thought of doing was
made intentionally difficult.
The reason is that, if you do it right, taking the code for an
activity and moving it to another application is easy. It's part of
Android's modularity. The data you pass using an Intent object, and
"
Can you clarify what you are trying to do? It's hard to see why you
want to do what you are asking about.
If you are trying to display the same information, from the same data
model, in two identical-looking views in two different activities, you
should create a class that extends AdapterView if y
That appears to be the problem. The confusing thing was that
singleInstance was set on a different Activity in the same app.
Thanks!!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post
I have a program where onActivityResult is being called with the
correct request code, and a null Intent parameter, before the the
Activity being launched begins. And, when that Activity calls
setResult, onActivityResult is not called.
This is probably some error indication, but for what? No exce
I came across your query while I was researching controlling input
methods. While I have not yet coded this up myself, from reading the
documentation, and from the type used to refer to the instance of
EditableInputConnection, it looks like you want the InputConnection
interface, which is document
My not-very-elegant "solution" indicates this is a permission issue.
The udev rule appears to set permissions, so it probably isn't being
run. It would be nice to verify the udev rule match, but I'm a udev
n00b and can't find what the ATTRS (formerly SYSFS) rule is supposed
to match.
--~--~---
s works.
>
> On Wed, Apr 15, 2009 at 9:56 PM, Zigurd wrote:
>
> > Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have
> > the 1.5 sdk and the new master branch of the sources.
>
> > If I change the udev rules to:
>
> > SUBSYSTEM=="usb&q
Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have
the 1.5 sdk and the new master branch of the sources.
If I change the udev rules to:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
...I'm able to mount the memory card and read and write to it. But the
command:
adb
Some information on telephony internals, PhoneApp, and communications
between PhoneApp and the RIL can be found in an upcoming book
published by O'Reilly called Android Application Development. It is
available on the O'Reilly "Roughcuts" site in draft form:
http://safari.oreilly.com/9780596156220
27 matches
Mail list logo
