[TESTING] XDAndroid GBX0C 2.3.7 Build

[jigwashere]

I've been enjoying running this and haven't had many problems other than missed calls or lack of audio during calls. Since this has already been discussed, and I didn't mention it.

If you need any specific tests, let me know. I'm on stock Sprint.

Sent from my XDAndroid GBX0B using Tapatalk!

[arrrghhh]

Originally Posted by jigwashere

I've been enjoying running this and haven't had many problems other than missed calls or lack of audio during calls. Since this has already been discussed, and I didn't mention it.

If you need any specific tests, let me know. I'm on stock Sprint.

Sent from my XDAndroid GBX0B using Tapatalk!

You shouldn't be losing audio on any calls. What kernel?

Do you have logs?

Missed calls are... well, seemingly a CDMA only issue. GSM folk don't seem to have this issue... probably a RIL problem, and unfortunately I don't think it'll ever get fixed.

[jigwashere]

I'm a total newb and simply installed everything from your original post (not the updated build). I have made and received calls with no audio, but can't consistently recreate it. Sorry, I thought it was a known issue and kind of ignored it. I'll try to produce logs later today.

Most everything works for me, otherwise. With this setup and CM7.1 on my Nook Color, I can put off upgrading my device indefinitely.

Sent from my XDAndroid GBX0B using Tapatalk!

[arrrghhh]

Originally Posted by jigwashere

I'm a total newb and simply installed everything from your original post (not the updated build). I have made and received calls with no audio, but can't consistently recreate it. Sorry, I thought it was a known issue and kind of ignored it. I'll try to produce logs later today.

So the calls don't consistently fail...? Odd.

I released an update to the build, which fixed a lot of audio routing problems. Please do a full update when it's convenient... no offense, but reporting bugs on outdated stuff does nobody any good...

[jigwashere]

Originally Posted by arrrghhh

So the calls don't consistently fail...? Odd.

I released an update to the build, which fixed a lot of audio routing problems. Please do a full update when it's convenient... no offense, but reporting bugs on outdated stuff does nobody any good...

I had no more problems with audio today, go figure. Anyway, I just wiped my card and downloaded the full bundle. The only things I kept were the csv files, startup.txt (acpuclock.oc_freq_khz=700000), and the calibration file. I hope the wife and kids don't come home for a bit -- I'm playing!

[arrrghhh]

Originally Posted by jigwashere

I had no more problems with audio today, go figure. Anyway, I just wiped my card and downloaded the full bundle. The only things I kept were the csv files, startup.txt (acpuclock.oc_freq_khz=700000), and the calibration file. I hope the wife and kids don't come home for a bit -- I'm playing!

lol, that sounds great. Enjoy.

[Dinomon1]

I installed this in a new folder, and when it boots it says "Sorry, the process com.android.phone has stopped unexpectedly. Please try again" Force close and it reboot..


I still have FRX07 folder in Storage Card, but in diff area..

[arrrghhh]

Originally Posted by Dinomon1

I installed this in a new folder, and when it boots it says "Sorry, the process com.android.phone has stopped unexpectedly. Please try again" Force close and it reboot..


I still have FRX07 folder in Storage Card, but in diff area..

Force close and it reboots...? To WinMo? That makes no sense.

Is there a 'wait' option?

I've seen this, hit force close... and go about my business.

[Dinomon1]

No wait button.. only Force.. I waited 5 mins, nothing happend..

So I copied FRX07 data to this one, and it booted up.. however when I try to unroot, it said missing ADB.EXE.. So no GOOD is not working..

[arrrghhh]

Originally Posted by Dinomon1

No wait button.. only Force.. I waited 5 mins, nothing happend..

So I copied FRX07 data to this one, and it booted up.. however when I try to unroot, it said missing ADB.EXE.. So no GOOD is not working..

Uhm, adb.exe is on your machine. Has nothing to do with the build/Android.