On Jun 4, 11:32 am, TreKing <[email protected]> wrote:
> Android Market coming pre-installed on most devices, Amazon's
> app having to be manually installed, and sideloading disabled
> on AT&T devices are also major factors.
Just FYI, if by "sideloading" (a term I haven't heard before),
you mean loading from outside of the Android Market, there is a
fix for that bug (I know...but as far as I'M concerned, it's a
bug, as is the unwanted screen lock that keeps popping back in
despite the no-lock widget, and the utterly useless Global
Unplug, which I end up destroying every time my phone reboots).
Sorry...back to the topic now....
I'm using this work-around to test the app I'm working on, since
my PC isn't up to the task of running the virtual device.
First Settings-->Applications-->Development-->USB Debugging must
be checked.
Second, use adb to install the app: from the command line, run
it as:
(23:13) $ ./adb install appname.apk
(I don't actually run it this way...I have a Zsh alias set up, so for
me,
that would be: "adbinstall appname.apk" which, for a bit of added
security (habit) uses its full path, and adds a -r to replace the
existing
copy.)
For those who already know this, sorry about the redundant post,
but I got the impression that this may not be as widely-known as
I thought.
Obviously, if you load and run a 3rd-party app that manages to
get some authority on the system and trashes it, you're on your
own....
Later,
--jim
--
73 DE N5IAL (/4) | DMR: So fsck was originally called
[email protected] | something else.
< Running FreeBSD 7.0 > | Q: What was it called?
ICBM / Hurricane: | DMR: Well, the second letter was different.
30.44406N 86.59909W | -- Dennis M. Ritchie, Usenix, June 1998.
--
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
