RC-29: access to 3G data network going down after onResume()?

by JP » Tue, 04 Nov 2008 12:17:43 GMT


Sponsored Links
 Anybody willing to check out a problem I found on the G1 I have?

When testing the app I am working on, I am mainly using WLAN in order
to have relatively constant up-/download characteristics (speed/
latency). No need to weight T-mobile's network down either. One
concern is the coming back to live after receiving an onResume(). I've
tested this on WLAN and it checks out fine.
Then on to test on T-Mobile's 3G network. This test coincided with an
OTA update to RC-29 this morning. I am seeing strange things now. Of
particular concern is the following: Access to the 3G data network
completely breaks down (without the network going down (;->)). This
happens with any app that accesses the Internet, including Maps or the
browser. Here's what happens on my G1: Put the phone to sleep. Let it
sit for maybe 15 or 30 minutes, then bring it back to life (e.g. push
Menu button twice) and without delay start requesting data by moving
the map around. This seems to fall into a window where the phone is
not quite ready to access the data network. It's perfectly fine to
require a couple of seconds to reconnect to the network, but once it
has, everything should be back to normal. Not on my phone. When I
perform the above test, the phone/Android completely loses access to
the data network. I can reproduce this all time, assuming the phone
has been sleeping long enough. The only remedy is to restart the
phone.  TIA.


--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Problems with shared library JAR

I'm trying to use an external library packaged in one JAR file
(openRDF Sesame 2.2.4 [1]). As suggested in this group, I first added
the JAR to a new folder in my project, then added it to the Java build
path via the project properties in Eclipse. Now I could already use
the classes from the library in my source code without getting any
errors. I also added the line <uses-library
android:name="org.openrdf" /> to the manifest file inside
<application>.

The problem is that as soon as I try to run the app, I get an
installation error (INSTALL_FAILED_MISSING_SHARED_LIBRARY)  on the
console and I'm told (via logcat) that my package "requires
unavailable shared library org.openrdf".

Where's my mistake?

Thanks,
Max

[1] 
http://ovh.dl.sourceforge.net/sourceforge/sesame/openrdf-sesame-2.2.4-onejar.jar
--~--~---------~--~----~------------~-------~--~----~

2. Bluetooth application...how does one get started?

Mark,
Thanks for your quick reply.
As far as you know, is there anything one can do in C/C++?
(And still have a standard phone image?)
I have seen a few things where images were rebuilt to enable functionality.
I am not really up for that...but I do need someway to move a file received
by the android to an embedded device that has neither wifi nor eithernet.
Any ideas?

-Mike






--~--~---------~--~----~------------~-------~--~----~

3. Production Crash Logs

4. testing uses-permission

5. Android on OLPC anyone?

6. with android sdk 1.5, i got a problem.

7. How can i display memory remaining to my app?