View Single Post
  #256 (permalink)  
Old 01-22-2010, 03:08 AM
makkonen's Avatar
makkonen
TouchPro Android Guy
Offline
Threadstarter
 
Join Date: May 2007
Posts: 585
Reputation: 3280
makkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIPmakkonen is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Linux/Android on CDMA Touch Pro (RAPH800) - PRE-ALPHA (not yet usable)

Quote:
Originally Posted by pierocksmysocks View Post
So I deleted my data.img, let it create a new one, and kept having issues with it crashing every time it tried to sync my google account over evdo. So... trial and error, I turned on wifi and used that to sync. Worked like a charm. Tried to download last.fm app while using evdo, and it kept crashing. Turned wifi on again and the app was able to download without an issues. I figured what the heck and ran the app while connected to wifi and I'm able to play music without the handset crashing. Unfortunately, if I use just evdo for this, it crashes.
OK. If you're getting such consistent crashes, maybe you're a good person to track this down. First of all, make sure you're using the latest version of the kernel (RAPH800-kernel-modules-2010-01-17-1263772660.zip) -- there was definitely a bug in the second-to-last one that was causing crashes on CDMA data access.

Grab the debug.zip file from the 3rd post on the front page, and extract it to your sd card.

Then, after a crash, when windows boots up, go into /Storage Card/debug/ and launch haret.exe, then immediately quit. A file should appear in your debug folder called dmesg.txt. Either open that file and look at it, trying to figure out where the kernel panic happened, or just attach it to a post here and I'll do so. The file's a bit messy, so you have to be a bit of a detective. Take note of the timestamps. If you have booted into android multiple times without fully shutting down the phone, it could write a new log over an old one, and wherever the new one ends, you'll start seeing the old data.

Anyway, more data is good. Might help us figure out where the problems are. Not that we'll be able to do anything with that data once we have it, but it's something.
Reply With Quote