Closed fat-tire closed 13 years ago
I was able to get the browser working by setting a location by using the "Clock" app in cm7 and by disabling "Data enabled" under wireless networks. Open clock, click the unable to update weather text and it will bring up a button to set location. Set a zip code, once set click the weather once to bring up the local forecast for the zip code you entered. Go into menu/settings/wireless and network settings/mobile networks and uncheck "Data Enabled".
My build from 02/01/2011 does not have this problem. I have not set the location and I have yet to have the browser crash. The Google home page, which uses location information, simply says the location is unavailable.
Keep these reports coming. I like WORKSFORME bug fixes :)
fyi, disabling networklocation in build.prop does not fix.
Bad news. A completely fresh installation WORKED the first boot, then went into the sleep of death, and when it woke up, touching the browser got this KP:
The relevant part of /proc/last_kmsg:
I did not understand shad0wf0x's instruction above to set a location via the Clock, but I did disable Data enabled under wireless and the kp disappeared.
I then deliberately SOD it, rebooted, checked that "Data enabled" was STILL off and tried again. This time I put airplane mode on. The airplane icon appeared, and phone data was greyed out. It STILL LET ME USE WIFI
And no crash on browser. I think that data may have been the issue. If we can permanently force airplane mode, maybe this solves this. Still should investigate, play around, and have others confirm.
Update: Airplane mode is permanently on now for MOBILE only. Settings won't let you turn it off. This is good in the sense that phone now tells you mobile is down, etc. But it is not good in the sense that it solves the kp issue.
This was identified by scotty2 as a race condition in the cache flush. He attempted a patch which was not successful-- however it was close enough to the changes observed in .32 that a backport was attempted. This eliminated the problem.
Another bug bites the dust. Thanks scotty2!
Hate to add another issue, but it's here so we may as well acknowlege/eliminate it.
This kp/reboot started within the last week. Previously browser worked fine without even a FC. Theory: this is related to browser hitting the GPS or otherwise using the location service, leading to a kp (somehow).
If it's useful, I or someone else can post a /proc/last_kmsg.