yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] tee aiy emm:
I wonder if anyone else has notice this,

Testing the data speed with the SpeedTest.net app for example seems to be jerky. That is, it doesn't download smoothly and it'll go really fast then get stuck, then resume over and over.

I also experienced a dropped call early which leads me to believe that this mod makes the connection inconsistent albeit faster.

I've done multiple tests over the past day and this behavior seems legitimate, so unless you see a significant speed improvement (2 or 3 times faster than normal), you should stay with your correct/original band.

I'll continue to do testing for now.
[G1 Android Development] Stimpoff:
NO, I found that reflash-reboot thing before "mod".

Mod worked just fine for me on Friday (I am not currently in 3G area), result was same as with official TMO EU ROM

I will test the mod setting again on low traffic indoor cell tommorow just to be 100% sure.

I did tens of speed measurement in that area and uplink speed wasn't never over 380kbit after mod it was over 1Mbit all the time. I been focused to uplink only, I will check downlink as well tommorow.
[G1 Android Development] PaoloWeckl:
my results testing several times here in italy:

without hack:

479

193

569

303

197

303

133

303

114

224

124

with hack:

231

499

526

292

144

294

422

215

656

785

603

426

300

378

268

uplink is stable at 145ca.

do u think i had have an improvement?
[G1 Android Development] Archont:
I have tried it twice and crosschecked with two different speed checkers I found in the market, but my CM is faster with the original file compared to the modded one.

I cannot remember the exact numbers, but it is around midnight so I have to get some sleep right now and will deliver numbers tomorrow.
[G1 Android Development] jchico1021:
So I have a g1 and was originally on dwang and then went on WG8 CM rom to try this out... here are my results...

dwang 1.13 avg UNTOUCHED

2085 kbps. 997kbps

WG8 CM avg BEFORE

2010kbps. 365kbps

WG8 CM avg AFTER

2105 kbps. 996kbps

Did I do something wrong? Or is there something special with Dwangs rom? I wanted to check WG's rom cause of that similar update. Just posting my results

Oh...also would like yto mention that my wifes mt3g with dwang 1.13 had remarkbly slower results., on avg 1300~kbps. 50

​

0~kbps
[G1 Android Development] :
I believe WG8 already includes this mod ("* Uses GPRS Class 12 (regular US EDGE/GPRS is class 10) plus faster HSPA (props to Stimpoff)").
[G1 Android Development] uansari1:
Jesus... how are you guys getting such speeds? When I'm outdoors and have full bars I can barely manage 900ish kbps down!
[G1 Android Development] Geniusdog254:
First off T-Mobile sucks :P lol. But I'm on AT&T with an unlocked Rogers Dream so I get 3G. It all depends on tower load, distance to the cell site, and atmospheric factors. I'm in a relatively light load area on AT&T (who is known for fast, albeit unreliable, networks) and I can average about 1500Kbps down & 250-300Kbps up. I don't have HSUPA in my area so it stays below ~380Kbps up. I have seen it hit 2500Kbps down in my area several times.
[G1 Android Development] jchico1021:
Hehe... in NY. Tested indoors in my apt.

And I know wg8 had a mod but yet this mod increased the upload speed. My real question is why did I get nearly 1000kbps speeds with dwang w/o that mod??
[G1 Android Development] Wisefire:
This was a major improvement for me,

Before:

U-D

72-96

After:

U-D

1040-375

Appreciate your help. Thanks!
[G1 Android Development] JonnyFlash:
In downtown Seattle, in an office building on the 5th floor.

3 Bars, 3G, UMTS Tower.

Cyan 4.2.7.1

Ran 10 Tests On each, and did an average. Used speedtest.net. Took Note of PING/Latency speed as well.

Base:

PING/Latency: 174.9 (High/Low=274ms/127ms)

D/L: 1151.3 (High/Low=1429Kbps/576Kbps)

U/L: 349.8 (High/Low=374Kbps/276Kbps)

With Mod:

PING/Latency: 158.7 (High/Low=252ms/132ms)

D/L: 1220.9 (High/Low=1525Kbps/563Kbps)

U/L: 348.8 (High/Low=371Kbps/263/Kbps)

Download seemed slightly faster, though pretty insignificant. For UMTS, I'm pretty sure it's inconclusive right now. I'm going to try again at the pub in about an hour, where at the counter, I can only get about 1 bar and can only get Edge - not to mention very slow at that. Regardless, so far it's been educational.

edit: not able to get good enough reception at the pub to test.
[G1 Android Development] Nayyak:
tested it twice (with Speedtest.net App) before the change and results were:

1. 563 Down, 190 Up

2. 556 Down, 55 Up

After the modification, the results were:

1. 1802 Down, 254 Up.

2. 2116 Down, 282 Up.
[G1 Android Development] ivanmmj:
It's really dependent on the tower you're currently being fed from and how T1 lines are attached to it. Some people won't see an increase because there is nothing to increase to. I saw an increase from a consistent 200k to about 1.2-1.8m.
[G1 Android Development] JonnyFlash:
{off topic, my apologies} Very true. I work on large phone systems, and the biggest complaints I get from customers are recordings of "All Circuits Are Busy" or Fast Busy/Reorder Tones, when they're trying to run call centers with a single PRI T-1 (24 voice channels) or a single group of IP Trunks (32 voice channels) concurrently with an overloaded IP network (voice is given the priority in the scheme of things, but you can't stop the signal). Most towers have at least a DS3/T-3 which provides about 28 T-1's at 1.544 Mbps each (you do the math). A single DS3 can provide a ton of connections. Most towers are being converted to HiCap Fiber for the data, so we should see more speed coming soon.
[G1 Android Development] acidwashg1:
just tried this, reporting results. test from location where I get a solid 2-3 bars of 3g. near los angeles. cyanogen 4.2.6.

before mod:

588kbps down, 187kbps up

just changed "ro.ril.hsxpa=2":

590kbps down, 210kbps up

changed both "ro.ril.hsxpa=2" & "ro.ril.gprsclass=12":

493kbps down, 184kbps up

basically, nothing happened for me. oh well, it was worth a shot.
[G1 Android Development] Shane2:
Didn't test this beforehand with speedtests, but I was usually lucky to get 30-40 KB/s on my downloads, after applying this patch I am able to get 80-110 which is really impressive (T-Mobile UK)
[G1 Android Development] jbdubbs:
No effect, 900 Down, 350 Up before and after.

T-Mobile US

CM 4.2.6

G1
[G1 Android Development] Morrolan:
Rebooted multiple times. throughout the day.

725.4 down/156.6 up (right now)

Still say the myth is busted.
[G1 Android Development] Stimpoff:
Tested 2 phones simultaneously(!), same place.

Empty 3G cell, capable HSDPA 14,4Mbit / HSUPA.

Operator has QOS (shaper) for 3Mbit/1Mbit

Phone without mod (cyanogen 4.2.7.1)

1812/360

1770/367

1696/362

Phone with mod (cyanogen 4.2.7.1) + mod

2688/1026

2642/1014

2775/1004

EDGE

no difference
[G1 Android Development] H@OBouget:
So I tried this (using the scripts) and actually got worse speeds.

I went from 788d 154u to 489d 147u

Then I looked at it again and saw that the scrips replace the build.trout.prop,

but as even the first post mentions, Tmo in the US uses the Build.prop file for these settings.

So I tried to use terminal to get a copy of the build.prop file...I'm not good with the language so I got errors.

Did those of you who got the speed boost on Tmo use the build.trout.prop file or the straight build.prop?
[G1 Android Development] olearyp:
So to clear up a point of confusion, any build.*.prop or build.prop file does the same thing, as long as the build is set up to read it. The trout/sapphire prop files are used to hold platform-specific props when multiple platforms are supported; only the one corresponding to your device gets read due to a boot-time check built into the ROM's init scripts. All of these end up in the same prop database, accessible via the getprop command in terminal.

This matters in the case of some ROMs, such as enomther's, which don't even have a build.prop, opting instead to put everything in the platform-specific file.
[G1 Android Development] Stimpoff:
I added video of testing in my office into first post...
[G1 Android Development] xenio2000:
I am using the fantastic ultra fast TheOfficial from Enom, I changed the build.trout.prop and build.sapphire.prop but I did not get any improve in speed.

Is my changes ok for the Enom rom or I have to modify something else?.

Thanks.

Xenio
[G1 Android Development] dipeshb:
My Results:

UK T-Mobile with a Black G1:

Kbits/s

Before Mod:

Down (Max)	267.0

UP (Max)	150.1

After Mod:

Down (Max)	353.3

Up (Max)	148.2

Only one test done before and after with 3 bars on 3G, looks promising

UPDATE EDIT: Also Changed my locale to UK, to: ro.product.locale.region=UK

Then got these results:

First Time:

Down (Max)	456.5

Up (Max)	167.3

Second Time

Down (Max)	382.1

Up (Max)	127.4

Again only 2 tests done with 3 bars on 3G, I can not be sure changing the region locale made any difference at all, but cant see it making things worse!
[G1 Android Development] Stimpoff:
it seems that for some users is needed to do two reboots after each change of prop file to apply setting
[G1 Android Development] acidwashg1:
even with this information in tow, I edited build.prop, build.trout.prop, and build.sapphire.prop to all include the changes.

I rebooted twice, and even a third time. Still, my results were the same...no change at all, the exact same average speeds. Whatever results those may have anywhere but the US, lucky you. But my hypothesis is that these changes have absolutely no effect in my immediate area, sadly :(
[G1 Android Development] bogdi1988:
the variation might be a difference in network traffic and that's why people might get better speeds...

i've tried this a couple weeks ago... no change.
[G1 Android Development] olearyp:
Changing both won't hurt anything, but your phone is reading only the build.trout.prop (for G1). Results of the change seem pretty mixed, so who knows.
[G1 Android Development] Swifty:
Great post!

My speeds are almost trebled after making the change according to mobilespeedtest.com!

Does feel snappier too.
[G1 Android Development] wellsie:
Major improvement

I have useable, un-filtered net access at work...Yeah!

Speedtest.net results

Before down/up (no I don't have them the wrong way round)

11/767

11/37

10/38

After

1122/378

1828/376

1300/376

Thank you
[G1 Android Development] Brutal-Force:
Went from ~300kbit to 1.7kbit

:D

Thanks for the hack.
[G1 Android Development] Binary100100:
you mean 1.7mbit right?
[G1 Android Development] HSDarkT3k:
Not bad

speedtest from Xtreme Labs, on 3G 2 bars in the same location (work inside of a building). Not much of a change... but navigation still works :) I will test this in an area where I tether a lot (ie. School, since they have the worst networks :rolleyes:) and see how it goes.

Before

Download: 503.2*:(

Upload: 142.8*

After

Download: 716.3*:)

Upload: 150.8*

*Kbit/s

Thanks!
[G1 Android Development] revwillie:
my browsing seemed snappier after trying this, but something else happened around the same time. When I try to charge my phone through USB, it indicates that charging is happening, but the battery's charge either declines or increases much more slowly than normal. I restored my trout settings to see if that fixes the problem, but I'm bringing it up in case anyone else may see the same issue.

My speedtest app connecting to Wash DC servers showed no improvement in EDGE or 3G speeds.
[G1 Android Development] ultra spikey:
I just tried this out...here are my results...seems like this myth is busted =T

Info-

- CM 4.2.5

- 3bars of signal on 3G

- speedtest.net app

(Speed is Down\Up and in kbps)

BEFORE the hack...

569\347

589\343

516\342

514\340

AFTER the hack + 2 reboots...

322\368

498\338

567\359

476\354

REBOOTED one more time just to make sure...

577\362

539\356

599\363

593\365
[G1 Android Development] Jrbourque:
So the only thing that we have to do with this is to throw these files on sdcard and run the switch script right? because i did that but not showing a difference , but my internet is slower inside my work so not sure if that is the issue or not but same speeds before and after
[G1 Android Development] s15274n:
How does one run the script, is there something in the recovery image I go to (console?) or do I flash it?

Is this something you can revert back.... or does it revert when you flash the newest cyan rom?

I would like to try this on my lunch break.
[G1 Android Development] HSDarkT3k:
You can use the terminal or adb.... follow the link for the download and terminal commands it just su and sh
[G1 Android Development] dead2hill:
hello, i did this just now, didnt take any test. but i do tether often and use the net on the phone a whole lot. and almost instantly seen a difference. the market was so much snappier. and the tethering is moving quick as ever.
[G1 Android Development] Jrbourque:
do we have to run both of those scripts to get his to work? or is the one script just to replace the old one if we want to go back?
[G1 Android Development] s15274n:
:edit:....
[G1 Android Development] Rekna:
I made these changes in salt lake city where I was getting around 450 down and 150 up. The changes to the build.trout.prop did not seem to have any effect on either the download or upload speed in SLC. I'm guessing SLC doesn't have HSUPA.
[G1 Android Development] s15274n:
Just realized I had a typo when running the script.... going to have to report back when I get outside if there is a change in my speeds.
[G1 Android Development] ShatBag1105:
Hahaha mine got dramatically worse in dallas.

884 up. 356 down. Before hack

396 up. 324 down. After hack

Sucks to be me.

(Done with the script)

Back to stock.

844 down. 373 up.
[G1 Android Development] HSDarkT3k:
This for some reason does not work for everyone... I have tried it on a Hero 1.5 Build Saw a 900Kbit/s download and about 225 Kbit/s upload but the Cyanogen 4.2.6 I saw a 200Kbit/s download difference but none on upload.
[G1 Android Development] sstang2006:
wow nice improvement. thanks
[G1 Android Development] Seeknay747:
To be clear, to apply the modification to a US T-Mobile G1, can we use the providied script to modify build.trout.prop or do we need to apply changes to build.prop and if so how?

Is there an editor on the phone we can use, or should I modify the script to change the settings for build.prop?
[G1 Android Development] Amon_RA:
There are actually a bit more settings you can play with to improve troughput. These are my current settings (give me the highest speed on my network) :

ro.ril.hep=1

ro.ril.hsxpa=2

ro.ril.enable.dtm=1

ro.ril.gprsclass=12

ro.ril.hsdpa.category=8

ro.ril.enable.a53=1

ro.ril.enable.3g.prefix=1

ro.ril.htcmaskw1.bitmask = 4294967295

ro.ril.htcmaskw1 = 14449

ro.ril.hsupa.category = 5
[G1 Android Development] nebochenezzar:
I thought I would put this out there, These speeds that you are talking about are including the latency and raw speed of the towers 'internet connection' not to mention the connection strength to your phone. So this also brings to the point that from time to time these towers have more or less load on their 'internet connection' making the differences in the increases you all are experiencing might be load time on that tower. I just got 3g here, which would mean that there are not a lot of people on my network, therefore mine will be much faster. now thats not to say that you all are not making an improvement, it just seems like playing with these settings and trying to benchmark them over large area seems silly.

Not to mention when the phones are right next to each other, it could come down to priority to the network and other factors, so we need to look at phones close together to really benchmark and find the best solution.

could the networks have different settings place to place? and that the TMO phones adjust to the network, and ours are not?
[G1 Android Development] CiDhed:
Here in the US.

Before:

D:523.4Kb(Max:523.4Kb)

U:140.6Kb(Max:141.4Kb)

After:

D:803.9Kb(Max:806.5Kb)

U:143.6Kb(Max:155.7Kb)

Full 3g bars using xtremelabs speedtest.
[G1 Android Development] ShatBag1105:
Ok so using the script before I had a big decrease in speed. I lost like half my download speed. So I had to revert back to stock. Anyway, using the app SU File Browser and Terminal I copied the buildtrout to my sdcard, applied the changes, and copied it back. Now I have no decrease in speed unlike last time I tried with the script. So thanks for the mod. Hopefully ill have a speed increase when my area allows it.
[G1 Android Development] sourcesociety:
Here's my report. Until I did the test multiple times, and reverted back to original for consistency, I was wholly skeptical.

Handset: HTC Dream

Network: T-Mobile

ROM: CyanogenMod-4.2.7.1

These are rounded averages. I also made sure to reboot before every test. Reverting back to the original build gave me identical readings to the first unchanged test. These tests were conducted in my home, and to my knowledge have never gotten above 400Kbits in or near my home.

XtremeLabs Speedtest was used, while having two bars of 3G reception.

---------------------------

Before change to build.trout.prop:

DL: 340Kbits / UL: 150Kbits

After change to build.trout,prop:

DL: 755Kbits / UL: 150Kbits

----------------------------

Although I'm happy for the faster download speed, I remain curiously skeptical of the reasons for the improvement.

-

I forgot to mention that I'm in the north western region of Phoenix, Arizona.
[G1 Android Development] Stimpoff:
to summarize this...

This mod could help in areas with at least 7,2Mbit HSDPA in downlink

Definitely improve uplink in HSUPA area - without this mod isn't possible to break 380kbit barrier

It will not help in case that you are blocked by operator's QOS (throtling, shaping)

It will not help in interfered areas.

Don't expect miracles in case your operator doesn't have sufficient technology.

From previous post is visible that somebody experiencing huge improvement, somebody slight, somebody non improvement and some few degradation.

Again this mod isn't an miracle which will improve 3G speed beyond operator's capabilities. It just enable higher coding schemes on your phone, that's all.
[G1 Android Development] Stimpoff:
I will try that on my almost empty cell tommorow ;-)

anyway where you get this parameters especialy htcmaskw1 ?

dtm will not improve speed it enable data transfer during call on 2G but am not sure if this feature is implemented in some network, in my not

ro.ril.enable.3g.prefix=1: adds the 3G prefix to the operator name.
[G1 Android Development] H@OBouget:
Ok so I redid this hack

First I edited the build.trout.prop to include Amon Ra's additions.

Then I manually entered the script text.

Note: there was no error in the scripts. I hand copied cause I could.

However I question the switch scripts need to rename copy a file, remove said file, and then copy a file in place of the removed file. Why not just rename copy and then copy the replacement in.

The replace script just copies it back.

On initial reboot I got 458d 146u

Said screw it and did a rapid reboot, reboot, reboot

After 3 reboots tests showed 878d 152u, 560d 147u, 890d 152u.

My old numbers were 788d 154u stock.

So there was some sort of improvement.

Looking at the script I realized that I had a typo error when I hand entered it. I forgot the /system after /mtdblock3

Didn't seem to stop it from working, but..

Ran the script again to correct it. (Not to worry about the org trout file I have a master copy saved.)

Even if I don't get high speeds, what I have noticed is that the initial 400 Kbit's used to take the first 20-30 % (about 5-6 sec) of the test to reach. Now its the first 1-3% (1-2 sec) then it kinda drags its way up from there.

1 reboot after script, 3g 3 bars, location desk mount.

1st test 618.5d 156.6u

2nd test 743.9d 166.2u

3rd test 778.0d 169.1

Average 713.4d 163.97u

Rebooted it 3 times as fast as it would go...I was impatient :D

4th reboot after script, 3g 3 bars, location desk mount

1st test 567.1d 154.3u

2nd test 780.2d 171.2u

3rd test 794.7d 148.4u (Jeez! it started at 500!)

Average 714d 157.97u

I noticed a climbing pattern to the testing so I did a series of 10 tests back to back and only cared about the basic results...

671 147 started in the 200's

786 149 started in the 200's

761 164 started in the 400's

600 150 started in the high 400's

816 156 started in the high 300's then jumped to 500

829 148 started in the high 500's then jumped to high 600

787 150 started in the 500's

836 148 started in the high 500's

791 150 started in the high 200's and jumped to 400

835 153 started in the mid 400's

Averages 771d 151.5u starting point about 423 Kbit in the first second.

My old numbers again were 788d 154u stock- based on one test.

The biggest difference I noticed was the first 5% of the test.

Stock would always start in the 200 area and build up.

The hack seemed to start in the 400 area.

Better than stock...:confused:

It seems faster in the browser, but .... I'll keep it for now.

For everyone's enjoyment I added the build.trout.prop and the scripts I used to this post. This build.trout.prop includes the changes by Amon Ra.

I take no credit, other than combining the work of 3 other people.

Stimpoff - for the thread/idea

cloverdale - for the org scripts

Amon Ra - for the update to the prop
[G1 Android Development] Amon_RA:
The mask parameters were taken from the European Hero, and the other settings are from the European Sapphire.

I know that the dtm and prefix parameters will not improve speeds but they are a nice to have ;-)
[G1 Android Development] mgorman:
3 bars in 3G w/o modded script (speeds in () are with modded prop)

latency to sever 268ms

Test 1:

Down 368 (632)

Up 388 (377)

Test 2:

Down 604 (561)

Up 287 (380)

Test 3:

Down 594 (449)

Up 330 (376)

@ 2bars 3g

Down 598

Up 268

So I have a decrease in down speed and an increase in up speed
[G1 Android Development] Blueoval24:
Successfully updated but didn't take any before tests to compare. Did want to mention one thing though. After recently flashing H's 1.33.2005 spl, I had been having issues with sending mms texts. Sometimes I kinda got it to work by swapping wifi on and off but it barely worked. What would happen is that it would say a text did not go through so id resend. After testing it was random if it went through or not. Long story short, I ran this script and in the last 24 hours I have not had ONE problem with sending texts. I think its safe to say this fixed it bc before almost every text I sent responed as unable to send. Thank you for this!
[G1 Android Development] sino8r:
I was snooping around build.sapphire.prop and it mentions network parameters also. Would those be worth changing or does the trout.prop one the only one that matters.
[G1 Android Development] sino8r:
Opps... double post
[G1 Android Development] ccflo:
Just awesome

Wow...., just doubled my download speed.... thx a lot!!!!!
[G1 Android Development] Rapax:
Thanks!

Until now, I was stuck at the 384kb speeds of old UMTS. I was actually going to pay the local orange store a visit next week, because I suspected they were barring me from HSDPA.

With this mod, I now have >1Mbit download speeds.

Running the latest CM on a rooted US G1 on Orange Switzerland network.
[G1 Android Development] tutech:
If you only have/use this modification on a Dream then the build.trout.prop is the only one that your phone reads from. If you have/use a Magic then the build.sapphire.prop is the only one that your phone reads from.
[G1 Android Development] bhilgeman:
I found this article relevant and exciting!

http://www.pcmag.com/article2/0,2817,2353300,00.asp
[G1 Android Development] Seeknay747:
I just wanted to add to this thread that my download speed was the same but my upload speed doubled.

I have a T-Mobile G1 in New York and used the provided script from the other thread. (The exact speeds I wrote down and dont have on my atm.)

Thanks for the up in upload speed!
[G1 Android Development] localh0rst:
I had to reboot twice ...

3g, 3 bars, Germany O2, speedtest.net:

1311/404

after:

1929/983

(both 3 times tested)

very nice, thank you!