The problem:
I just built a really simple android application today. I followed
the tutorials on Google's site. The app starts and runs great in the
emulator. I exported the unsigned apk, created a keystore, generated
my own cert, signed my .apk, verified that it was signed, and it all
looks good.
Then I uploaded the .apk to my web server, and accessed the .apk in
the web browser on my G1. It downloads the .apk perfectly, but when I
click on the application to install it it brings up a screen that says
Android System (in the background)
In the foreground an alert box comes up:
Replace Application
The application you are installing will replace another application.
All previous user data will be saved.
I've never installed my program on my phone, so it's obviously
thinking my program is something it's not. If I say "OK" it tells me
that the program I'm about to install needs access to *everything*. ..
i.e. GPS, wifi status, internet access, etc, etc. The thing is, my
application doesn't require any of those permissions. The only
permission I assigned to it in the manifest file is
android.permission.INTERNET.
Any hints? I've spent the last 3 hours digging around online trying
to solve this myself, but no luck. I know I'm a newb. Today is the
first time I've ever compiled or written java in my life ;-)
Hi, I am just reporting that I have seen the same thing happen. There
is a dictionary app at andappstore.com called WordMate. When I tried
to install it, it tried to replace the Android System (in the same way
you have described).
On Oct 25, 12:39 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com>
wrote:
> The problem:
> I just built a really simple android application today. I followed
> the tutorials on Google's site. The app starts and runs great in the
> emulator. I exported the unsigned apk, created a keystore, generated
> my own cert, signed my .apk, verified that it was signed, and it all
> looks good.
> Then I uploaded the .apk to my web server, and accessed the .apk in
> the web browser on my G1. It downloads the .apk perfectly, but when I
> click on the application to install it it brings up a screen that says
> Android System (in the background)
> In the foreground an alert box comes up:
> Replace Application
> The application you are installing will replace another application.
> All previous user data will be saved.
> I've never installed my program on my phone, so it's obviously
> thinking my program is something it's not. If I say "OK" it tells me
> that the program I'm about to install needs access to *everything*. ..
> i.e. GPS, wifi status, internet access, etc, etc. The thing is, my
> application doesn't require any of those permissions. The only
> permission I assigned to it in the manifest file is
> android.permission.INTERNET.
> Any hints? I've spent the last 3 hours digging around online trying
> to solve this myself, but no luck. I know I'm a newb. Today is the
> first time I've ever compiled or written java in my life ;-)
Ok, I solved it myself after another few hours of playing around.
Lol... This is a difficult one to understand.
If I install the app by downloading it via web browser over the EDGE
network it fails with the described behavior.
If I install the app by downloading it via web browser over Wifi it
works perfectly.
I guess maybe there's some extra nasty compression going on when
downloading over EDGE that breaks it?
Brandon Zehm
CTO, TSheets.com
On Oct 25, 8:46 am, Ed <edmundcl...@gmail.com> wrote:
> Hi, I am just reporting that I have seen the same thing happen. There
> is a dictionary app at andappstore.com called WordMate. When I tried
> to install it, it tried to replace the Android System (in the same way
> you have described).
> On Oct 25, 12:39 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com>
> wrote:
> > The problem:
> > I just built a really simple android application today. I followed
> > the tutorials on Google's site. The app starts and runs great in the
> > emulator. I exported the unsigned apk, created a keystore, generated
> > my own cert, signed my .apk, verified that it was signed, and it all
> > looks good.
> > Then I uploaded the .apk to my web server, and accessed the .apk in
> > the web browser on my G1. It downloads the .apk perfectly, but when I
> > click on the application to install it it brings up a screen that says
> > Android System (in the background)
> > In the foreground an alert box comes up:
> > Replace Application
> > The application you are installing will replace another application.
> > All previous user data will be saved.
> > I've never installed my program on my phone, so it's obviously
> > thinking my program is something it's not. If I say "OK" it tells me
> > that the program I'm about to install needs access to *everything*. ..
> > i.e. GPS, wifi status, internet access, etc, etc. The thing is, my
> > application doesn't require any of those permissions. The only
> > permission I assigned to it in the manifest file is
> > android.permission.INTERNET.
> > Any hints? I've spent the last 3 hours digging around online trying
> > to solve this myself, but no luck. I know I'm a newb. Today is the
> > first time I've ever compiled or written java in my life ;-)
I've been having the exact same problem, and your solution,
downloading my apk to my G1 over WiFi, fixed it. But this to me was
not an acceptable solution because many people are often not near WiFi
spots, and must rely on EDGE/G2/G3 networks from T-Mobile, so I
decided to play around and find out how I can download the app via
EDGE, not WiFi, and avoid this nasty compression.
I downloaded the code for Ringdroid, because this was an app I
successfully downloaded and installed via EDGE:
http://code.google.com/p/ringdroid/
It's a great app and very well documented. I set up an eclipse
environment to build Ringdroid, and had it literally along side my own
eclipse environment for building a simple helloworld app, and did
many, many comparisons of the two projects, including commenting out
about 98% of Ringdroid to bring it down to the same size as my
helloworld app - and it wasn't until I made Ringdroid very, very small
(17K down from its original 200K) that Ringdroid FAILED to download
via EDGE properly.
So, the whole time mumbling to myself that this just CAN'T work, I
just added a 200K jpeg to the res/drawable directory of my helloworld
app, compiled it to make it roughly 220K. I didn't even reference the
jpeg anywhere in the code. I put it up, downloaded it via EDGE, and
it WORKED!
Conclusions:
- There is a MINIMUM size apk that can be downloaded via T-Mobile.
- T-Mobile's data server is a mysterious black box, and this is why no
one has been able to even know what to Google for, let alone find any
documentation about this problem, or EDGE itself. And this is
probably why many people have just said use WiFi.
I think I speak for everyone when I say I would love to hear more
thoughts on this, particularly anyone who knows about EDGE or similar
networks, and if there really is a minimum size. Thanks in advance!
On Oct 25, 10:57 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com>
wrote:
> Ok, I solved it myself after another few hours of playing around.
> Lol... This is a difficult one to understand.
> If I install the app by downloading it via web browser over the EDGE
> network it fails with the described behavior.
> If I install the app by downloading it via web browser over Wifi it
> works perfectly.
> I guess maybe there's some extra nasty compression going on when
> downloading over EDGE that breaks it?
On Nov 3, 2008 1:36 PM, "UBZack" <zferv...@gmail.com> wrote:
I've been having the exact same problem, and your solution, downloading my apk to my G1 over WiFi, fixed it. But this to me was not an acceptable solution because many people are often not near WiFi spots, and must rely on EDGE/G2/G3 networks from T-Mobile, so I decided to play around and find out how I can download the app via EDGE, not WiFi, and avoid this nasty compression.
I downloaded the code for Ringdroid, because this was an app I successfully downloaded and installed via EDGE: http://code.google.com/p/ringdroid/
It's a great app and very well documented. I set up an eclipse environment to build Ringdroid, and had it literally along side my own eclipse environment for building a simple helloworld app, and did many, many comparisons of the two projects, including commenting out about 98% of Ringdroid to bring it down to the same size as my helloworld app - and it wasn't until I made Ringdroid very, very small (17K down from its original 200K) that Ringdroid FAILED to download via EDGE properly.
So, the whole time mumbling to myself that this just CAN'T work, I just added a 200K jpeg to the res/drawable directory of my helloworld app, compiled it to make it roughly 220K. I didn't even reference the jpeg anywhere in the code. I put it up, downloaded it via EDGE, and it WORKED!
Conclusions: - There is a MINIMUM size apk that can be downloaded via T-Mobile. - T-Mobile's data server is a mysterious black box, and this is why no one has been able to even know what to Google for, let alone find any documentation about this problem, or EDGE itself. And this is probably why many people have just said use WiFi.
I think I speak for everyone when I say I would love to hear more thoughts on this, particularly anyone who knows about EDGE or similar networks, and if there really is a minimum size. Thanks in advance!
On Oct 25, 10:57 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com> wrote:
> Ok, I solved it myself after another few hours of playing around. > Lol... This is a difficult one to understand.
> If I install the app by downloading it via web browser over the EDGE > network it fails with the described behavior. > If I install the app by downloading it via web browser over Wifi it > works perfectly.
> I guess maybe there's some extra nasty compression going on when > downloading over EDGE that breaks it?
> On Nov 3, 2008 1:36 PM, "UBZack" <zferv...@gmail.com> wrote:
> I've been having the exact same problem, and your solution,
> downloading my apk to my G1 over WiFi, fixed it. But this to me was
> not an acceptable solution because many people are often not near WiFi
> spots, and must rely on EDGE/G2/G3 networks from T-Mobile, so I
> decided to play around and find out how I can download the app via
> EDGE, not WiFi, and avoid this nasty compression.
> I downloaded the code for Ringdroid, because this was an app I
> successfully downloaded and installed via EDGE:http://code.google.com/p/ringdroid/
> It's a great app and very well documented. I set up an eclipse
> environment to build Ringdroid, and had it literally along side my own
> eclipse environment for building a simple helloworld app, and did
> many, many comparisons of the two projects, including commenting out
> about 98% of Ringdroid to bring it down to the same size as my
> helloworld app - and it wasn't until I made Ringdroid very, very small
> (17K down from its original 200K) that Ringdroid FAILED to download
> via EDGE properly.
> So, the whole time mumbling to myself that this just CAN'T work, I
> just added a 200K jpeg to the res/drawable directory of my helloworld
> app, compiled it to make it roughly 220K. I didn't even reference the
> jpeg anywhere in the code. I put it up, downloaded it via EDGE, and
> it WORKED!
> Conclusions:
> - There is a MINIMUM size apk that can be downloaded via T-Mobile.
> - T-Mobile's data server is a mysterious black box, and this is why no
> one has been able to even know what to Google for, let alone find any
> documentation about this problem, or EDGE itself. And this is
> probably why many people have just said use WiFi.
> I think I speak for everyone when I say I would love to hear more
> thoughts on this, particularly anyone who knows about EDGE or similar
> networks, and if there really is a minimum size. Thanks in advance!
> On Oct 25, 10:57 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com>
> wrote:
> > Ok, I solved it myself after another few hours of playing around.
> > Lol... This is a difficult one to understand.
> > If I install the app by downloading it via web browser over the EDGE
> > network it fails with the described behavior.
> > If I install the app by downloading it via web browser over Wifi it
> > works perfectly.
> > I guess maybe there's some extra nasty compression going on when
> > downloading over EDGE that breaks it?
I've noticed a few dual sim card holder for htc devices. Do you think android would host such a component? I was thinking T-Mo for data 3g and AT&T for calling on their 2g network
On Nov 3, 2008 1:52 PM, "UBZack" <zferv...@gmail.com> wrote:
Go to the Settings app, then Wireless controls, then Mobile networks, then check "Use only 2G networks" this should do the trick. -Zack
On Nov 3, 4:43 pm, "Amir Noble" <amirno...@gmail.com> wrote: > My question is how do u disable 3g t...
> On Nov 3, 2008 1:36 PM, "UBZack" <zferv...@gmail.com> wrote: > > I've been
Haven't seen anything in the API like that, that mentions multiple sd
cards, but if there is then there's probably a standard for what to
name the directory path to access each card, and this will probably be
mentioned on various forums by the time said devices are available.
Something like "/sdcard001/", "/sdcard002", etc.
On Nov 3, 6:23 pm, "Amir Noble" <amirno...@gmail.com> wrote:
> I've noticed a few dual sim card holder for htc devices. Do you think
> android would host such a component? I was thinking T-Mo for data 3g and
> AT&T for calling on their 2g network
> On Nov 3, 2008 1:52 PM, "UBZack" <zferv...@gmail.com> wrote:
> Go to the Settings app, then Wireless controls, then Mobile networks,
> then check "Use only 2G networks" this should do the trick.
> -Zack
> On Nov 3, 4:43 pm, "Amir Noble" <amirno...@gmail.com> wrote: > My question
> is how do u disable 3g t...
> > On Nov 3, 2008 1:36 PM, "UBZack" <zferv...@gmail.com> wrote: > > I've been
By the way, I can verify all this. I downloaded my 17KB APK
(NotepadV3 from the exercises) once over 3G, and once over Wifi, and
noticed that even the downloaded file size was different! This is
really strange. I doubt it's a showstopper bug, as most "real"
applications will be big enough not to be affected. But man, poor
form.
-- Eric
On Nov 3, 4:07 pm, UBZack <zferv...@gmail.com> wrote:
> I've been having the exact same problem, and your solution,
> downloading my apk to my G1 over WiFi, fixed it. But this to me was
> not an acceptable solution because many people are often not near WiFi
> spots, and must rely on EDGE/G2/G3 networks from T-Mobile, so I
> decided to play around and find out how I can download the app via
> EDGE, not WiFi, and avoid this nasty compression.
> I downloaded the code for Ringdroid, because this was an app I
> successfully downloaded and installed via EDGE:http://code.google.com/p/ringdroid/
> It's a great app and very well documented. I set up an eclipse
> environment to build Ringdroid, and had it literally along side my own
> eclipse environment for building a simple helloworld app, and did
> many, many comparisons of the two projects, including commenting out
> about 98% of Ringdroid to bring it down to the same size as my
> helloworld app - and it wasn't until I made Ringdroid very, very small
> (17K down from its original 200K) that Ringdroid FAILED to download
> via EDGE properly.
> So, the whole time mumbling to myself that this just CAN'T work, I
> just added a 200K jpeg to the res/drawable directory of my helloworld
> app, compiled it to make it roughly 220K. I didn't even reference the
> jpeg anywhere in the code. I put it up, downloaded it via EDGE, and
> it WORKED!
> Conclusions:
> - There is a MINIMUM size apk that can be downloaded via T-Mobile.
> - T-Mobile's data server is a mysterious black box, and this is why no
> one has been able to even know what to Google for, let alone find any
> documentation about this problem, or EDGE itself. And this is
> probably why many people have just said use WiFi.
> I think I speak for everyone when I say I would love to hear more
> thoughts on this, particularly anyone who knows about EDGE or similar
> networks, and if there really is a minimum size. Thanks in advance!
> On Oct 25, 10:57 am, "brandon.z...@gmail.com" <brandon.z...@gmail.com>
> wrote:
> > Ok, I solved it myself after another few hours of playing around.
> > Lol... This is a difficult one to understand.
> > If I install the app by downloading it via web browser over the EDGE
> > network it fails with the described behavior.
> > If I install the app by downloading it via web browser over Wifi it
> > works perfectly.
> > I guess maybe there's some extra nasty compression going on when
> > downloading over EDGE that breaks it?
|
