Quote:
Originally Posted by tdcrone
- I had an odd bug: I wasn't doing anything significant - clicked the 'phone' phyiscal button, I think - and Android got stuck for a minute or so, and then went to the colored X screen. Booted up from the X as usual, found Sprint and signal, but no data. The oddity is that the phone itself did not reset and did not go into WM, Android just jumped to X for no clear reason (watchdog?) and then got into this Android-with-no-data.
|
When it drops back to the boot animation and then comes back (it's happened to me a number of times) it means that the kernel hasn't panicked, the low level stuff is ok... but Android crashed and restarted. Sometimes it'll go from there into a boot loop... sometimes it'll come back up and run fine.
Since Android restarted, but the modem didn't reinitialize, it probably had trouble figuring out how to bring up a network connection. It's possible going into and out of airplane mode (or manually dropping 3G and then bringing it up again, though I think you need a 3rd party widget to do that) would resolve it, but I'm not sure.
Quote:
Originally Posted by 88fingerslukee
I'm having issues with getting GPS signal locks. I see the satellites right away so I know it's working but it takes somewhere between 5 and ∞ te tell me where I am. That said, I don't think the Location feature has ever worked running Android before, not even the IP location feature.
Is aGPS enabled for Bell Mobility in Android? Is there some .conf file that I can simply add the servers to (wishful thinking)?
|
Some folks have mentioned turning on GPS and trying to get a lock in WinMo before booting into Android. Something about having the ephemeris updated helping to get locks quicker.
I still haven't played with it, so I have no idea. I gather that if people are getting locks in under 15-20 minutes, aGPS in general must be functioning. It would seem that if it works at all, it should work on Bell.