yashsingh1/xdaforums huggingface dataset:
[General Topics] ACSteel:
Hello, this has probably been talked about before, but I wanted to let anyone interested know how this is working out. I have been doing extensive research on the purchase of a new MP3 player wanting the main features to have Bluetooth A2DP and audible.com compatible.

I realized these features are far and few between, and the players that have these two features are the size of your average WM Phone. When I finally came to this conclusion, I pulled out my old HTC Diamond and have been able to not only have these features, but by turning off the cell radio, I still have wifi, pmp, mp3, A2DP, web browser, touchscreen, etc etc all in one. Needless to say, I love my Diamond again.

I made my today screen bare with just iLauncher on it and wisbar to take away the phone features on top. Other than the hardware buttons, it looks and feels like a good solid MP3 player. Hope this may let other old phones see the light of day again. Thanks for reading.
[General Topics] phatmanxxl:
I gave my old HTC Wizard to my 19 month old daughter to watch her Dora and Yo Gabba Gabba videos on, she also likes the obscene amount of buttons that phone has. So yea, that phone is pretty much just a media player now.
[General Topics] daedric:
Then allow me to ask then for advise!

I use MediaMonkey on windows to organize my music. I like the program, it suites my needs.

The problem is on the WM phone itself. Which program do you use to listen to music? I've tried Nitrogen, and iMulator... both of them work as they're supposed to. But i could use more. iMulator need to mature, and be a little more customizable. But for a alpha stage, its quite good!

I could use a program with a good media library, probably fullscreen support, touch friendly.

Any advise ?
[Nexus One Android Development] mtw4991:
Originally Posted by stampere

you can edit the build.prop by

adb pull /system/build.prop c:\where\you\want\to\put\it\

open with wordpad and add the following lines

ro.ril.hsxpa=2

ro.ril.gprsclass=12

ro.ril.hep=1

ro.ril.enable.dtm=1

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

save the file

adb remount

adb push c:\where\you\want\to\put\it\build.prop /system/

reboot so that the settings take effect

________________________________________________________________

Stampere suggested this over in Paul's thread with no replys. The hxspa and gprsclass are not included in the Froyo build.prop anywhere I can see. They were included in CM 5.0.6.

Has anyone added these to Froyo and do they help or are they unnecessary and will conflict with the new Froyo 4.0.6 radio build?
[Nexus One Android Development] Imperial.mack:
I added the first two and it helped a lil....wondering the same thing tho....
[Nexus One Android Development] damentz:
Are you sure all those options are still relevant? My froyo image has none of these and performs well. I can get higher throughput by adding

ro.ril.hsxpa=2
ro.ril.gprsclass=12

But the rest are largely undocumented and should remain at default unless someone can prove what they do.

The biggest issue is the radio. With Froyo, my 3g disconnection issues are GONE, so now we can focus on latency and throughput.
[Nexus One Android Development] mtw4991:
This is my point exactly. While I'm still getting some Edge flipping on Froyo radio in weak signal areas like work building, if the throughput is higher then why not add it? I don't think it can hurt anything:eek:

The rest are "relatively" undocumented as Cyanogen said he didn't know what they did, therefore he wasn't going to mess with them. My 2 thoughts were:

(1) If throughput were increased, would power consumption decrease as data would be transmitted and completed faster...or

(2) Would adding additional code lines conflict with the current image somehow as they were obviously left out on purpose?
[Nexus One Android Development] prscott1:
Since this has been confirmed as a test build, perhaps some of these other properties will show up in the official build?

I too have better connection with the froyo radio - but weak throughput. I'll research and try some of these and report back if I find anything positive.
[Nexus One Android Development] mtw4991:
I added the hsxpa and gprsclass entries to my build.prop and will test also when I get out of work into a 3g environment, lol. I had modded this in CM 5.0.6 and played with hsxpa settings of 1 and 2. 1, I believe is WCDMA preferred and 2 is universal or something like that...
[Nexus One Android Development] themetatron:
my only question would be are these changes necessary, or does the device already have the settings hard coded. as in, did the carriers add these lines to some devices to level the field between the power users and the casual user.

need at least class 14 hsdpa to access tmo hspa+ 21.1 mbps

http://en.wikipedia.org/wiki/High-Speed_Downlink_Packet_Access

http://en.wikipedia.org/wiki/High-Speed_Uplink_Packet_Access
[Nexus One Android Development] Daddyroot:
[URL=http://www.speedtest.net][/URL]Just Google hsdpa, hsupa, hsxpa

You need to choose the appropriate category for your local network.

I forget which is which but the category number is representative of the download/upload speeds you are capable of while on edge, 3g, beyond 3g, hsdpa.

For me, T-Mobile in Madison, Alabama,

GPRS= category 32

Hsdpa= category 14 (this doubled my speed on mobile speedtest.com!)

Hsupa= category 7

Hsxpa= category 2

I always add these to my build.prop and yes its because when I first saw them in one of Paul's desire roms, I googled each of them and tested and I can definitely tell the difference.

Good luck

Want free 2gb dropbox?

Use this link. https://www.dropbox.com/referrals/NTczOTM2MTY5
[Nexus One Android Development] Imperial.mack:
definitely got faster UL and DL speeds with the text I bolded :D
[Nexus One Android Development] rjhay22:
Interesting... not sure itll be a good idea or even make a difference but Ill give this a try and report back my findings... If I may add though, an easier way to edit would be through root explorer app from market.
[Nexus One Android Development] rallos98:
I added those 2 lines and 3G signal seems to be better when indoors. Especially in my room where the coverage is bad.
[Nexus One Android Development] rjhay22:
Update based on speedtest.net:

NOTE: Tested each tweak 5x and took note of it, phone stayed on the same exact place the whole time.

3g

- No significant change in speed between stock FroYo build.prop/ril=1/ril=2.

Edge

- Gprs =12 gave me slower DL and UL speed.

- Gprs = category 32 showed slight increase in DL speed but noticeably slower UL speed.

I'm sticking with the stock FroYo build.prop, it works perfectly fine.
[Nexus One Android Development] mtw4991:
Testing update: Weird results

Ok, did some testing. Changing hsxpa from 2=>1 did help it stay on 3G and reduced the switching from 3g to Edge a little. I had hsupa=6 and was getting download speeds of around .04-.09 mbps with upload speeds of 1.72 mbps on multiple runs?????? really weird, almost like it kill the dl and supercharged the ul.

The link below shows that the T-mobile N1 is hardware configured for

gprsclass=10

hsupa=6

hsdpa=6/7

hsxpa=1 or 2

http://my.opera.com/fordcom2002/blog/2010/01/13/google-nexus-one

These are the only settings I played with and didn't do every combination as there are a bunch. Seems it didn't make a big difference no matter what I set them to. Also, there is the possibility that these settings are conflicting with built in Froyo settings somewhere else, although it would take someone much more knowledgeable than this rookie to find them, lol.
[Nexus One Android Development] agentkalaw:
did you just do this today?

it might be a TMobile glitch or speedtest app. I'm on a non froyo radio and was checking my speeds today and I was getting a 0.00 DL with a 1.4 UL

WTH?

but i know its DL'ing fine because i have no problem with the browser or youtube
[Nexus One Android Development] serialtoon:
Its possible that it could be a glitch. Check out my DL speeds. One is from an LA server and another from a Chicago server. Im located in LA.
[Nexus One Android Development] mtw4991:
Damn, I hope not as I spent some time changing/rebooting/changing/rebooting etc. :(
[Nexus One Android Development] stampere:
ro.ril.hsxpa=0 is UMTS

ro.ril.hsxpa=1 is HSDPA only

ro.ril.hsxpa=2 is HSDPA,HSUPA this is also network dependent. if your network isn't configured for this then your better off with option 2
[Nexus One Android Development] stampere:
they don't conflict with the radio. the additional settings help with keeping the speeds consistent for streaming while tethered to the phone.
[Nexus One Android Development] stampere:
froyo build prop
[Nexus One Android Development] mtw4991:
Thanks man, I'll do some more testing tomorrow. Don't need tethering with wifi hotspot now:D
[Nexus One Android Development] mtw4991:
Do they need to be in the order you have listed in your build.prop? I had them arranged differently which might have been an issue...such as hsxpa, then gprs, then hsdpa, then hsupa...then the rest of the standard build.prop.
[Nexus One Android Development] RogerPodacter:
perhaps this is related, but i am not using froyo. i just installed cyanogen 5.0.7 and now i am capped at 384Kbps upload speed. it seems my HSUPA is no longer working. when i flash back to my stock ROM, i immediately get upload speeds of 1.4Mbps.

does anyone know if and why this happens with latest cyanogen? how cna i fix it? i read this thread, but i am noob so have no idea exactly how to edit this file. thanks.
[Nexus One Android Development] Daddyroot:
There is no set category for everyone. It all depends on your local network connection.

the higher the category number, the faster possible speeds, with exception of hsxpa which is described accurately a few posts back.

For example, where I'm at there are edge, gprs, 3g, and hsdpa T-Mobile networks. Madison/Huntsville was one of the first cities to get the 3g and the hsdpa recently released is awesome.

The best suggestion I have is to first Google the different categories and once you understand what we are talking about. Then try one number higher until you get one that wont let you connect. Then go back to last category number that you could still connect to whatever network you are testing and use it.

These categories just give a Max threshold capability for your network.

You will never achieve the highest possible speed for the Max capability of your network. But you simply want to correctly identify and not set the threshold too low.

That said, recognize this is for those of us wanting that extra KB/sec just because we want to push the limits just to do it.

This isn't a miracle speed boost.

In fact, if you don't understand yet by this point of the thread, do your self a favor and just leave the settings as is.

For each place I frequent Each day, I know which network I am connecting to, where to stand to get a hspa connection, and where the strength of signal is best.

Lol

Want a free 2gb dropbox to sync PC with android?

Follow this link:
[Nexus One Android Development] RogerPodacter:
That just doesn't make any sense. The stock ROM has the correct setting, and when you flash cyanogen it changes to the incorrect setting. The phone will always connect to the highest connection available at that particular location. But cyanogen artificially limits this, requiring you to do this trick to get it back. It's quite crazy if you ask me.
[Nexus One Android Development] rjhay22:
I am not sure what makes you think Cyan's ROM has the incorrect setting, but 5.0.7.1 ROM has a default gprs=10 and hsxpa=1 setting which to my knowledg is Tmobile's default setting and stock ROM.
[Nexus One Android Development] Daddyroot:
The stock rom doesn't necessarily have the correct settings because the "correct" settings are different depending on you location.

But Like I said,

if you don't understand.

do some research.

It is comprehendable if you learn all about hspa/etc

Good luck!
[Nexus One Android Development] RogerPodacter:
Because cyanogen's ROM disables hsupa. I finally rooted and flashed after using stock ROM for 3 months and cyanogen disables upload and caps it at 384kbps. I'm on ATT and when I flash back to stock my upload immediately jumps to 1. 5mbps. I finally edited this build.prop and now my speed jumped right back up to 1. 5. If you pull the cyanogen build. Prop file its clearly set to 1 which is just insane to me.

There is no reason to artificially limit the connection. The nexus one is a 7. 2 hsdpa and 2. 0 hsupa phone, and that's what the stock ROM ships with. If a hsupa phone travels to a lower hsdpa area, it will just drop down on its own. It doesn't have to be forced to hsdpa like cyanogen is doing. Makes no sense.
[Nexus One Android Development] RogerPodacter:
I'm well versed on all the hsdpa technologies. The nexus is a 7.2mbps phone. If you leave a 7. 2 area the phone jumps down to whatever is available on It's own. It doesn't matter what part of the world the phone is located. This should always be set to the stock setting of maximum.

I know exactly what happened. People noticed this setting was different on other phones like the hero so this "myth" carried over to the cyanogen and nexus. But its totally wrong.
[Nexus One Android Development] simms22:
I get wonderful 3G speeds with cm, always did. Maybe its because im using tmobile. Cm always had tmobile settings. Since you are on att, these settings wont work. Tmobile 3g and att 3g are using differing frequencies. It only makes sense that the settings should be different.
[Nexus One Android Development] RogerPodacter:
I must not be explaining correctly. I get fine download speeds, 2.0mbps easily. But the upload speed is capped at 384kbps with the latest cyanogen. As soon as I flash my stock ROM back my upload immediately goes back up to 1.5mbps.

http://www.speedtest.net/android/4336552.png

I finally did the edit build prop from this thread on the cyanogen ROM and it fixed my upload back us to 1.5mbps. I just don't know why this would ever be set to anything other than hsupa (hsxpa=2) because the phone will drop itself down to 3.6 mbps hsdpa if its not in an hsupa (7.2mbps) area.

Here are all my speed tests with cyanogen:

http://www.speedtest.net/android/4314740.png

http://www.speedtest.net/android/4307857.png

http://www.speedtest.net/android/4314948.png

And after I correct the build prop:

http://www.speedtest.net/android/4342614.png
[Nexus One Android Development] stampere:
order doesn't matter on how you have them arranged.
[Nexus One Android Development] bahathir:
There are many ro.ril parameters which I found from /system/lib/libhtc_ril.so

Enjoy :)

$ strings libhtc_ril.so | grep 'ro\.ril'
ro.ril.a53.%s
ro.ril.ecc.%s
ro.ril.def.agps.mode.%s
ro.ril.def.agps.feature.%s
ro.ril.def.agps.mode
ro.ril.def.agps.feature
ro.ril.oem.ecclist
ro.ril.oem.nosim.ecclist
ro.ril.enable.dtm
ro.ril.gprsclass
ro.ril.hsdpa.category
ro.ril.hsupa.category
ro.ril.hsxpa
ro.ril.enable.nitz
ro.ril.enable.network_identify
ro.ril.qos.maxpdps
ro.ril.qos.traffic.class
ro.ril.qos.max.ul
ro.ril.qos.max.dl
ro.ril.qos.guarantee.ul
ro.ril.qos.guarantee.dl
ro.ril.qos.delivery.order
ro.ril.qos.max.sdu
ro.ril.qos.delivery.err.sdu
ro.ril.qos.transfer.delay
ro.ril.qos.traffic.priority
ro.ril.always.laccid
ro.ril.fast.dormancy.rule
ro.ril.fd.scron.timeout
ro.ril.fd.scroff.timeout
ro.ril.fast.dormancy.plmn
ro.ril.enable.3g.prefix
ro.ril.3g.long.name
ro.ril.htcmaskw1.bitmask
ro.ril.htcmaskw1
ro.ril.enable.homezone
ro.ril.enable.vt
ro.ril.enable.regucid
ro.ril.enable.hsdpaind
ro.ril.enable.a52
ro.ril.enable.a53
ro.ril.enable.dcm.feature
ro.ril.enhance.htcdis
ro.ril.enable.tim.feature
ro.ril.enable.korea.stk
ro.ril.enable.hsupaind
ro.ril.enable.gea3
ro.ril.enable.managed.roaming
ro.ril.enable.enhance.search
ro.ril.disable.mcc.filter
ro.ril.search.first.pnn
ro.ril.enable.ncell.ind
ro.ril.enable.enhance.nws
ro.ril.radio.svn
ro.ril.wp.feature
ro.ril.emc.mode
ro.ril.ucsq.mode
[Nexus One Android Development] rallos98:
Upload smashes into space.
[Nexus One Android Development] d1mitrov:
ok so what are the best settings for 5.0.8 and froyo on t-mobile's network?
[Nexus One Android Development] manfly9884:
Here you go:http://www.google.com/support/forum/p/android/thread?tid=70bc0539d1352511&hl=en
[Nexus One Android Development] d1mitrov:
ok well this site says that ro.ril.hsxpa should be 1. however on 5.0.6 where i get best speeds such as 3mbps and above it is set to 2. thats weird.
[Nexus One Android Development] RogerPodacter:
I'm the only one it seems screaming at the top of my lungs that changing hsxpa=1is a horrible thing to do.
[Nexus One Android Development] jettrue:
Why is it "horrible"? Such a strong word. ;)

I'm on tmobile and get these speeds now in St. Louis (heart of the city, not the burbs)

I added these lines:

# GPRS class

ro.ril.hep=1

ro.ril.hsxpa=1

ro.ril.enable.dtm=1

ro.ril.gprsclass=10

ro.ril.hsdpa.category=8

ro.ril.enable.a53=1

ro.ril.htcmaskw1.bitmask = 4294967295

ro.ril.htcmaskw1 = 14449

ro.ril.hsupa.category = 5
[Nexus One Android Development] xguntherc:
I never did this when I went to FRF50 Modaco's first, rooted version of Froyo. I'm still running that and have slightly slower speeds than before.

anyone confirm this helps for T-mo US, i'll be doing it on FRF83
[Nexus One Android Development] Christopher3712:
Keep in mind I live in an area where T-Mobile has upgraded their networks. I changed a few things myself and have yet to complete full testing, but i did notice something incredible. I did some research on the classes used in the ro.ril settings and decided to max mine out, regardless of what the N1's hardware capabilities are. I'm currently at work, where I usually see D/L speeds of about 500kbps and uploads of 100 kbps. I work in an area 15 west of DFW Airport where T-Mobile hasn't upgraded their towers. When I'm by DFW Airport, I usually see D/L speeds of 4000 kbps and U/L speeds of 800kbps. So I made some changes to see what would happen:

ro.ril.hsxpa=2

ro.ril.gprsclass=32 (Click and scroll down to the Multislot Class Chart)

ro.ril.hep=1

ro.ril.enable.dtm=1

ro.ril.hsdpa.category=14 (Click and scroll down to the HSDPA User Equipment (UE) categories Chart

ro.ril.enable.a53=1

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

ro.ril.htcmaskw1.bitmask=4294967295

ro.ril.htcmaskw1=14449

ro.ril.hsupa.category=7 (Click and scroll down to the Versions Chart)

What I initially saw after the change, were D/L speeds of 900kbps on average and U/L speeds in the range of 375 kbps. This is virtually double what I had before the change. However, on one particular test, I saw a D/L speed of 496 (not impressive at ALL), but an upload speed that hovered around 3000 kbps before settling at 3068 kbps. I'm curious to see how my phone responds in areas where I know the network has been upgraded. 4pm cannot get here soon enough.
[Nexus One Android Development] mtw4991:
Keep us posted with your results....good test pre/post network upgrade!
[Nexus One Android Development] Gr8gorilla:
I can't see any difference with or without. I am in atlanta in areas where the signal is good I get up to 4 mbs download. That is with or without the settings. I really don't think these settings matter at all.
[Nexus One Android Development] mtw4991:
I tend to agree with you Gr8gorilla, I have strong signal and routinely get 3-5mbps dl but only around .60-.70 upload speeds. I'm just looking for a way to increase upload speed to around 1.2-1.4, then all will be right in the heavens.
[Nexus One Android Development] xguntherc:
Yup, I've not done any of these changes but I updated to FRF83 and my speeds have steadily improved to high tmo speeds in Vegas. I'm not even on the strip where they are supposed to be even faster..

3.5 down and 1.3 up. Middle of day and at night both tested for network load.
[Nexus One Android Development] RogerPodacter:
well i'm only talking about this edit, ro.ril.hsxpa=1. setting that to 1 immediately limits my upload speed to 384Kbps. when i change it right back to 2, my upload speeds immediately go back up to 1.5Mbps.

i dont like this edit because it is limiting your phone down to only 3.6Mbps down and 384kbps up. according to this:

ro.ril.hsxpa=0 - UMTS r99

ro.ril.hsxpa=1 - HSDPA

ro.ril.hsxpa=2 - HSDPA/HSUPA

the phone ships with HSUPA/HSDPA hardware up to 7.2Mbps. but it seems when you set hsxpa=1 you are artificially reducing your 3g connection to plain old HSDPA 3.6Mbps (with 384kbps upload). so i just dont understand it.

in my area our 3g network is wide open, no congestion, so i regularly hit the limits around 3Mbps download and 1.5Mbps upload. so its a good testing ground to easily see what this setting does. it caps my upload for sure and i cannot break 0.37Mbps no matter what i do. set hsxpa=2 and upload jumps right up to 1.5Mbps.

unless i am totally missing something. has anyone with hsxpa=1 ever had a faster upload speed than 384kbps?
[Nexus One Android Development] Christopher3712:
Okay, so I've gotten a chance to run more tests and haven't seen any improvement. It appears i'm getting the same D/L and U/L speeds at home that I originally got w/o the extended build.prop edits. I was hoping that by maxing the parameters, I would allow the processor to try to reach its packet transfer maximum. However, it doesn't appear to work as such. If anything, i saw decreased d/l speed by DFW Airport (down to just below 3000 kbps). I also saw some spotty 3G coverage on my commute home. Not sure if it had anything to do with my build.prop modification or the heavy storm cover that was starting to blanket the area. I can ony assume the 3068 u/l speed was a fluke as I was unable to achieve that speed again. The closest I got was 618DL/2596UL and that was after MANY tests averaging U/L speeds at 500mbps. I'm going to switch it back to the parameters that are established by the snapdragon chipset. I can't wait to get a 1.5 GHz phone... those allow for true 21.1 Mbps (theoretically). :D