[Droid Eris Android Development] endoki:
For those that have Metro as their carrier:

I was doing some testing to see if the LOST DATA had something to do with redirecting the connection using a proxy and ip tables, as ASR seems not to be needed any longer. I don't know if you guys have noticed but, it appears that Metro changed something on their network and is now not using a proxy. This led me to think that maybe by installing the MetroFix that included autostart.sh Script to set ip tables and use a proxy, that was somehow causing of the LOST DATA issues.

I decided to test various ROMs that I know in the past, needed the MetroFix (ip tables and proxy) to work, and see

:

1- If DATA was present before installing any MetroFix, right after first boot.

2- If DATA contined to work/changed/worsened after installing a MetroFix that excluded the autostart.sh Script part for proxy/ip tables, and ASR.

3- If DATA continued to work after ONLY including the "Production/MMS" values in the telephony.db file and APNs by modifying the SQL Script that took care of this.

4- If DATA issues changed/worsened after flashing Token's MetroFix which sets up proxy/iptables -- includes the autostart.sh Script, the complete telephony.db and APNs values/tables, and ASR as it is currently being used.

5- I also tested if the Mms.apk needed to be replaced for MMS to work, and some other stuff / APN settings in my effort to collect data for the One-Flash-Fix I am working on putting together.

6- If the LOST DATA issue was GB specific.

I tested Android 2.1, 2.2 and 2.3 ROMs; here is a list of ROMs I used:

xtrSENSE 4.6.5

xtrROM 5.0

Froyo:

CELB Froyo 4.3

FroShedYo V11

VANILLA FroShedYo

KaosFroyo V39

Tazz Froyo GB v26

Vanilla Tazz v28

GB:

Tazz Blackened Ginger 2

Ginger Tazz 10

Ginger Tazz 11

GSB 1.8

GSB 1.9

Results:

1- DATA was PRESENT on all ROMs without installing any MetroFix at all.

2- DATA was PRESENT/UNCHANGED after installing a MetroFix that excluded the autostart.sh Script for proxy/ip tables, and ASR.

3- DATA was PRESENT/UNCHANGED after only including the "Production/MMS" values/tables in the telephony.db and APNs by modifying the SQL Script that generated/populated those values/tables.

4- DATA seemed to worsen (drop more) on some ROMs and not on others after flashing the current MetroFix which sets up proxy/ip tables -- autostart.sh Script, complete telephony.db and APNs values/tables, and ASR.

5- Mms.apk had to be replaced on all Froyo and GB ROMs except on: FroShedYo V11 and VANILLA FroShedYo...

Extracting the Mms.apk included on these two ROMs and using it on other ROMs showed that: this Mms.apk works / can be used on other ROMs.

6- The LOST DATA issue seemed to only affect GB ROMs; with only the usual minor/short LOST DATA moments that resolved on its own, across all other ROMs... maybe the DEVs currently workgin on GB ROMs can help us fix this on their end. ;)

Conclusion:

It appears that Metro has made some changes to its network and no longer uses a proxy for WEB. Thus, the need for any of the MetroFix's parts that addressed these settings are not needed (u2nl, autostart.sh, internet telephony.db/APNs and ASR). Now, only the MMS specific settings and the Mms.apk are needed to take care of the MMS part, as WEB/DATA seems to be completely working; and using a proxy/ip tables seemed to affect DATA on some ROMs.

The LOST DATA issue appears to be more GB specific, with varying results from one GB ROMs to another.

I am sharing with you the DATA I collected in my effort to have a better understanding of the actual/current Metro issues that some of us have been experiencing, and my attempt to contribute. I hope this info can be of help and please, feel free to add... ;)

I am working on putting together a new/modified One-Flash-Fix that will include only the current necessary settings and the Mms.apk.