[BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes

[tomc585]

Originally Posted by arrrghhh

FRX05 doesn't have spare parts out of the box, but the app is available from the Market.

Thought it was me when i couldnt find it.

[slimbrown29]

Been using FRX05 without any problems for a week solid. No major issues at all. Only slight annoyances:

- Even with OC, the phone tends to be sluggish at times.
- 3.5 mm jack. I use my phone as media device for about 2-3 hrs a day. So wish I could use my earphones.

However, since this Android port is still the developing stage, I can live with the phone as is. All in all, I am a happy camper.
Thank you to all the developers who make the TP2 keep on going and going and going.

P.S. Looking forward to the stable realease of FRX05 Nand Boot.

[ndno]

Originally Posted by arrrghhh

Yea... I guess I should add this to the FAQ as well. Which I assume you read? .

At any rate, the power button operates... like a power button.

So does end, unless you remap it. In spare parts, you can set the "End Key Behavior" to go to home instead of be power.

FRX05 doesn't have spare parts out of the box, but the app is available from the Market.

It's in the FRX05 bundle you posted

FRX05\AndroidApps\Other\SpareParts.apk

Development.apk is there also if it's not already part of system.ext2

[arrrghhh]

Originally Posted by ndno

It's in the FRX05 bundle you posted

FRX05\AndroidApps\Other\SpareParts.apk

Development.apk is there also if it's not already part of system.ext2

O yea, I forget about all those hidden APK's .

[fishingmedic]

Originally Posted by slimbrown29

Been using FRX05 without any problems for a week solid. No major issues at all. Only slight annoyances:

- Even with OC, the phone tends to be sluggish at times.
- 3.5 mm jack. I use my phone as media device for about 2-3 hrs a day. So wish I could use my earphones.

However, since this Android port is still the developing stage, I can live with the phone as is. All in all, I am a happy camper.
Thank you to all the developers who make the TP2 keep on going and going and going.

P.S. Looking forward to the stable realease of FRX05 Nand Boot.

If you're using kernel 1253 or newer you can use the usb dongle for headphones. And you can buy the usb adaptor on ebay for 2-3 bucks.

[oisact]

Every time I boot up FRX05 or FRX04, and even if I do a proper shutdown immediately, there are always two 32k corrupt files found on the SD card. The really odd part is it is the exact same two files each time. One is text followed by binary, the other is all binary. Even stranger, when I was running FRX04, it was the same file, just the FRX04 version. Here are excerpts:

FRX04:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRX04
ro.build.display.id=FRX04
ro.build.version.incremental=eng.bryan.20110121.213411
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Fri Jan 21 21:35:50 EST 2011
ro.build.date.utc=1295663750
ro.build.type=eng
ro.build.user=bryan
ro.build.host=carbunkl
ro.build.tags=release-keys
ro.product.model=MSM
ro.product.brand=generic
ro.product.name=full_msm
ro.product.device=msm
ro.product.board=msm
ro.product.cpu.abi=armeabi

FRX05:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRX05
ro.build.display.id=FRX05
ro.build.version.incremental=eng.bryan.20110301.185226
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.2
ro.build.date=Tue Mar  1 18:53:33 EST 2011
ro.build.date.utc=1299023613
ro.build.type=userdebug
ro.build.user=bryan
ro.build.host=carbunkl
ro.build.tags=release-keys
ro.product.model=MSM
ro.product.brand=generic
ro.product.name=full_msm
ro.product.device=msm
ro.product.board=msm
ro.product.cpu.abi=armeabi

I've done a couple reinstalls, and of course a full upgrade from FRX04 to FRX05, and there's simply no possible way those same files are residing on the exact same sectors of the SD card, so I really don't think it is the SD card itself. Is this happening to anyone else?

[arrrghhh]

Originally Posted by oisact

Every time I boot up FRX05 or FRX04, and even if I do a proper shutdown immediately, there are always two 32k corrupt files found on the SD card. The really odd part is it is the exact same two files each time. One is text followed by binary, the other is all binary. Even stranger, when I was running FRX04, it was the same file, just the FRX04 version. Here are excerpts:

I've done a couple reinstalls, and of course a full upgrade from FRX04 to FRX05, and there's simply no possible way those same files are residing on the exact same sectors of the SD card, so I really don't think it is the SD card itself. Is this happening to anyone else?

Are you talking about the FSCK*.REC files that are generated at the root of the SD?

They're annoying, but you can just delete them with a command in the froyo.user.conf file.

The reason for the FSCK files is we are not shutting down the system properly - something about running on SD prevents us from being able to shut down the system properly. I'm not too clear on the details, I think it has something to do with not being able to power down the SD & umount the FS safely...?

[oisact]

Okay, I took a different SD card, formatted it FAT32, installed virgin FRX05, placed it in a totally different TP2 (so 100% different hardware, card and device), booted into Android. Once it was up I did a normal power off and let Android shut down and turn the device off. Pulled the SD card, popped it in my laptop, and it found two corrupt 32k files, the exact same files as my other device and SD card.

Something is going on that Android is corrupting the FAT32 file system in a consistent way. I can't imagine it is supposed to work this way?

Can someone else pop their SD into a windows machine and do an error check on the card and see if it finds errors? It will dump the files into FOUND.000 (FOUND.001, etc number increments each time you run error check and it finds corrupt files) on the SD card, and inside you should see two 32k files FILE0000.CHK and FILE0001.CHK.

[arrrghhh]

Originally Posted by oisact

Okay, I took a different SD card, formatted it FAT32, installed virgin FRX05, placed it in a totally different TP2 (so 100% different hardware, card and device), booted into Android. Once it was up I did a normal power off and let Android shut down and turn the device off. Pulled the SD card, popped it in my laptop, and it found two corrupt 32k files, the exact same files as my other device and SD card.

Something is going on that Android is corrupting the FAT32 file system in a consistent way. I can't imagine it is supposed to work this way?

Can someone else pop their SD into a windows machine and do an error check on the card and see if it finds errors? It will dump the files into FOUND.000 (FOUND.001, etc number increments each time you run error check and it finds corrupt files) on the SD card, and inside you should see two 32k files FILE0000.CHK and FILE0001.CHK.

Oh I see what you're saying... Yea I don't ever scan the card with Windows after running Android on it. Just seems like a bad idea .

Seriously tho, what does it matter? We already know that Android doesn't get shutdown correctly, and Linux spits out FSCK records from not being shut down correctly. Not surprised Windows also spits out errors.

[oisact]

The problem is the FAT32 filesystem is corrupted every time Android runs, even if it is a clean shutdown. And since it always happens with the exact same two files it is something that is happening explicitly, not randomly.

A few days ago I had a reset, and afterward FRX05 was totally unstable and would reset every 20-30 minutes. After 6 or 7 resets I popped the card into my laptop, had it fix the errors, and then stability was back to normal - went all day and the next with no resets. So whatever this filesystem corruption is it does have an impact on the resets.

For it to be corrupting the filesystem every single run there is a fundamental IO problem.