yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rahlquist:
GalaxySsupport: @rahlquist It has the x-gold 616 baseband processor ( http://bit.ly/9045el ) which does support HSUPA. Plz contact ATT about future plans. ^L (08/09/2010 9:23:05 PM from CoTweet in reply to rahlquist)

GalaxySsupport: @rahlquist Nope, it supports HSDPA (Cat 8) w a maximum data rate of 7.2mbps. Visit http://bit.ly/9h14PN for more info on ntwk support. ^Leah (08/09/2010 6:26:25 PM from CoTweet in reply to rahlquist)

My thoughts exactly. Everyone keeps saying Rodgers has HSUPA so captivate will support it there and until someone has one with it I wont believe it. Remember AT&T has HSUPA too. Also note that second link Samsung gave me is a link to the specs for the Captivate, not The Captivate on AT&T only. That spec shows no HSUPA. I honestly feel HSUPA was something that companies that bought the captivate didnt want to pay Samsung for turning that feature on so they didnt and thats why Samsung says the phone is capable however it is not enabled.
[Captivate Android Development] rahlquist:
IANAL nor AIAM

The manufacturer says its capable but doesn't have it enabled, specs say it doesn't have it enabled, the carrier says it doesn't have it, no one has said it should have it except disgruntled users. A lawyer with any ethics at all would likely tell you the same and refuse to take the case.

I appreciated your dedication and zeal but right threatening legal action is a joke.
[Captivate Android Development] derek4484:
The captivate hardware supports HSUPA. We already know that. You can flash a different modem file to the phone and it will get HSUPA data from the towers. But then the phone calls dont have voice on one end. AT&T has either had samsung write software that disabled HSUPA or once samsung produced a ROM then the AT&T software engineers wrote crippling software. Either way, it doesnt get HSUPA. However, Rogers may want it to have HSUPA on its network, thus another modem file to try may arrise. It's a possibility that the kernel from Rogers Captivate will work perfectly on the AT&T phone since they are identical hardware.

All in all the hardware is capable, its AT&T that has crippled it so it wont compete directly with the iphone4. Once they lose their exclusivity with Apple, maybe they wont have to keep sucking steve jobs's ****, maybe they'll unlock HSUPA on it then.
[Captivate Android Development] raychang:
This makes me think that the HSUPA disabling changes are within the already released source code tree (Kernel, Platform) which are totally controlled by Samsung instead of the lower level firmware from Infenion which controls the modem chip. Can you imagine that intel is willing to released a special version of a firmware crippled CPU under a special request from a computer maker, say HP or IBM? I will say that HP or IBM have to do the crippling efforts by themselves instead of Intel If they have any similar intentions.
[Captivate Android Development] AJerman:
It's not. It's dependant on the modem.bin which isn't released as open source. It's something that the carriers can customize for their networks. I'll post more later, I'm out right now.
[Captivate Android Development] raychang:
There is a thread about the disassembly of Samsung Galaxy i9000 (or Captivate), the posts and the photos did not mention the Infenion X-gold chip as the modem chip. So, I am not very certain that what kind of modem chip is used in Captivate.

Are there any way to get the signatures from the modem.bin firmware to know that it is released from the modem chip vendor, Samsung, or the various carriers?
[Captivate Android Development] AJerman:
Expert legal, no, but that's my opinion. I just don't think anything a store rep says could be used as false advertisement, otherwise people would be suing cell phone companies, as well as every other retail establishment constantly. Most store reps don't have a clue as to what all this stuff means. They know a few things that learned in training or read on documentation, but they certainly don't know everything about a device, in fact, most of them are clueless about the details. I do know that I've looked everywhere and never seen HSUPA mentioned on any official AT&T documentation.

Now, could you try to force them to give you your money back and cancel any contract you signed, very possibly. But I doubt you'll get any further than that.

I'd love it if it would work and get them to put HSUPA into it, but I don't think one sales rep saying it's as fast as the iPhone 4 will get you anywhere. Like I said, it's not an expert legal opinion, just common sense. I definitely appreciate you thinking of any possible solution, I just wouldn't want you to waste your time trying something that almost certainly wont work.

It's possible that the Rogers version won't have HSUPA either, but I don't think it's out of the question to think it would have a different firmware. Look at the Vibrant. T-Mobile and Bell have their own firmwares just because of differences in the modem firmware. Same with the multiple different versions of the I9000 worldwide, so I don't think it's out of the question that Rogers would make their own as well. Not to mention, they very well may not want to annoy their customers like AT&T is.

I could look through it again, but I don't think there's anywhere in the modem.bin file that you're going to find a model number of the specific chip. The only way to open it up is to hex edit it, and then you're just looking at the strings in the code.

I would say for near certainty that we don't have a different chip than the other phones though. Otherwise it's very unlikely that the other modems would work at all (aside from the voice issue) on the Captivate, plus the modem.bin files are far too similar. I can specifically search for strings with the text "hsupa" in them and find references to source files with hsupa in the name in other versions of the modem.bin, but not in ours. It looks like they just didn't compile the support in.

Like I said, I'm not entirely certain, but I think the modem.bin file is actually compiled by the carrier itself, and not AT&T or the chip maker or anything. It's something that the carriers get to customize to their network. The base code may be provided to them, but I think they may put it all together and compile it. I could be wrong on that though. It'd be interesting to see if we could somehow get of the base code for the modem, but I highly doubt it. There would be no reason for it to be released publicly.
[Captivate Android Development] raychang:
I have modified a few parameters (output buffer size, etc) for the option.ko driver in Linux to enable the HSUPA for my 3G USB modem. Throughout that option.c file, there is no key word "HSUPA" in that C source code, but the fixes for enabling HSUPA by the parameter changes in the driver source code "option.c" were posted in several places. My point is that someone can change some parameters to enable/disable the HSUPA, but the C source code or the compiled object code may not mention the keyword HSUPA at all.

I don't have a hex editor in my place, but think it will be helpful if we know who compiled/released the modem.bin. If I am a vendor who selling the modem chip to Samsung, I may give them the chip with a single version of the firmware with some wrapper (or API) to enable Samsung to customize the HSUPA behavior.
[Captivate Android Development] AJerman:
I do understand that, but what I was saying is that it DOES mention hsupa several more times in the non-Captivate modems. In the form of strings related to the source files used. It seems clear to me that HSUPA support isn't compiled into the Captivate modem.bin file, meaning there isn't an easy switch or bit to change in the hex to enable it.

Here is what I mean:

Vibrant modem.bin (T959UVJFD):

Captivate modem.bin (I897UCJF6):
[Captivate Android Development] alphadog00:
It is always nice to see some common sense prevail. I am so tired of everyone jumping on the lawsuit bandwagon. There is no legal leg to stand on unless somewhere (in writing) the phone spec'd HSUPA. AND even if it did, the real remedy is to return the thing. Just like the iPhone 4 - if it doesn't perform, then return it.
[Captivate Android Development] designgears:
BUMP!!

port the phone.apk over from JP3

flash the modem.bin from JP3

enjoy HSUPA and voice :)
[Captivate Android Development] LGSilva:
Did you try this or it's just an idea? It's 2:26am, I don't have anybody awake to call right now to test this... :D
[Captivate Android Development] designgears:
just call your voicemail and see if it has sound...

It was just an idea...
[Captivate Android Development] mostyle:
Don't tease me.. lol

Actually, unless someone has tried this I will give it a go.
[Captivate Android Development] wpb2:
Patiently waiting an update on if this works.

Can someone post the phone.apk, and Modem.bin from JP3? I will try it I guess. What do I have to lose.
[Captivate Android Development] anilkuj:
hI design

i flashed the modem but when i try to install the phone.apk it says not installed

i got the phone.apk from the Galaxy S stock apps.

also even though the phone.apk dint install now my phone app keeps FC'ing if i try to make any calls

ps: my upload speed went up from 270's to 1.2 Mbps and my download speed went up from 1.8 MBps to 3.2 Mbps , the HSUPA definitely does affect the download speeds , i tested from the exact same spot at my office desk.

Update:

Just installed phone.apk using this

cat /sdcard/Phone.apk > /system/app/Phone.apk

and restarted the phone , but i seem to have the same voice issue , just tried calling my voicemail dint hear any voice.
[Captivate Android Development] alphadog00:
The files are on Samsung Firmwares. See other threads for links.
[Captivate Android Development] shaolin95:
Man, I sometimes feel like flashing this just to get the faster speeds then flashing back to the normal ones for regular usage.

Since I cannot call while at work I mostly use the phone for watching online videos so that is about 8 hours of using this for the faster speeds then flash back before going home...sounds crazy?

How hard would it be to go back and forth?
[Captivate Android Development] TheTodFather:
Gears, i tried this to had the same problems... :( what did you do exactly, I'm sure I did it differently then you.
[Captivate Android Development] sl8125:
Man i really want this fix. Barely getting 1 mb dowload .250 upload.
[Captivate Android Development] ace518:
Get rom manager and play with nandroid backups.
[Captivate Android Development] TheTodFather:
Hey I see DesignGears is back with us...

<BUMP>
[Captivate Android Development] TheTodFather:
Gears,

How did you get data to work with voice? I cant seem to replicate what you did. Did it actually work?
[Captivate Android Development] TheTodFather:
Is there a registry setting to raise Maxium Transmition Units (MTU) settings? I already knew that the phone was only spittin out 1280 while I was tethering PDANET. (would of done through mobileAP but need to reflash when i get home).

I'm sure this would definitely help with downloading.

However, I do realize that th e RWIN values are going to be low because LinuxOS works differently then lets say windows XP. The RWIN values move dynamically when needed. Im pretty sure that how Vista and Win7 work.

I would like to manually edit the MTU and perhaps a few other settings like multiple acks or what not.

Why the hell is it stuck at 1280? That just sounds retarded I cant imagine if we made it larger we would encounter pack-losses. SO lets bump that up ...just need to know how.
[Captivate Android Development] mostyle:
Guys.. DG never said 'I have it working'.. :)
[Captivate Android Development] TheTodFather:
Back to the drawing board
[Captivate Android Development] eddiet29:
What are the differences between the Vibrant and the Captivate that one can't use the radio ROM (pardon me if I don't use the technical word) of the Vibrant to enable HSUPA on the Captivate? If this has already been suggested please pardon my ignorance.

If one doesn't know what I'm referring to here is the link (apparently I can't post outside links) from Engadget discussing that the unlocked Vibrant has 1+ MB upload speed.

Cheers
[Captivate Android Development] TheTodFather:
apparently the radio.bin or modem.bin is developed for each carrier for obvious reasons. So it is not included in the source files that are released publicly. There have been

ATT fouled up the .bin and disabled it since we have no source code then it makes the task that much harder to trouble shoot and fix.

If you where following this thread you would know that we are counting on the rodger's modem.bin or radio.bin(forgot) because fortunately Rodger's firmware would potential work once dropped in and replaced with ATTs pile of douchery.

HOpe that helps

***edit Mobile AP is nice its doubling my speeds when tethering. I have 4.09 down and .32 up. On the phone I have 1.9 down and .32 up...both have pings in the low 300ms

8-28-2010 looks like we dont need the rodgers dump to get hsupa.
[Captivate Android Development] centex99:
Where is a rogers dump? ? Hasn't the phone been out for a while now?
[Captivate Android Development] TheTodFather:
nope not the captivate still hasn't been announced yet. (twiddles thumbs)
[Captivate Android Development] strictlyphat:
You know what's crazy. I flashed an i9000 modem.bin and the t mobile vibrant kernel and I get hsupa with voice working. All this on top of stock jf6 rom. But volume buttons are reversed. And home and back buttons are reversed. Why can't we get hsupa. It just poses me off
[Captivate Android Development] wpb2:
Can you post links to the 2 files? I would like to try it on JH2.
[Captivate Android Development] evertec:
Is HSUPA mainly to help with upload speeds? Cause I'm getting 3megabit down, 350kpbs up out of the box, which is pretty much the max download speeds for 3g that I'm aware of.
[Captivate Android Development] ranova:
yes its greatly increases the upload speeds, which subsequently helps ping times.
[Captivate Android Development] raychang:
Does anyone know whether or not the rest of the kernel source codes are (beside modem.bin) compilable? I checked the source code tree, they have the .config file in the linux kernel directory. If the kernel code is compilable, we can somehow discover the real differences related to HSUPA between Captivate and the Vibrant besides the position of the UI buttons and try to compile the HSUPA enabled Captivate kernel which works well with the modem.bin from i9000.
[Captivate Android Development] Unhelpful:
Modem.bin isn't part of the kernel and is therefore not part of the kernel source release...
[Captivate Android Development] raychang:
Are the rest of the source codes (beside the modem.bin) compilable? Have any teams be able to compile the released source codes?The .config file in the linux kernel directory in Vibrant and Captivate might have provided the clues for the differences in the HSUPA settings.
[Captivate Android Development] Unhelpful:
Perhaps you have not seen the custom kernel thread? ;)
[Captivate Android Development] raychang:
I don't know how these custom kernels are ptroduced (by compiling from the released source codes?) Some thread indicated that some drivers (non-open source) are not there and thus the whole thing is not compilable. If it is compilable, then with the post from strictlyphat which indicated that the Vibrant's kernel worked well with the i9000's modem.bin in the Samsung Captivate with only a few reverse positions on the UI buttons. Then someone can definitely compile the Vibrant kernel to reverse the buttons's positions (by modify the .config file or other config files) then use the newly compiled Vibrant kernel to work in Captivate phone.
[Captivate Android Development] dewt:
You know you can change the key mappings right? /system/usr/keylayout has the files which map the softkeys to functions.
[Captivate Android Development] anilkuj:
i did this too on top of my JH2 , i dont have a very good signal at home so i cant really say if i have HSUPA because of the DL/UL speeds

is there another way to check if i have HSUPA is enabled
[Captivate Android Development] raychang:
If you can go to a local AT&T store, the signal there should be very strong. If the upload speed >= 384 K, then I think the HSUPA has been turned on.

Could someone please upload the Vibrant kernel for us to download? The one for Vibrant at the samfirmware.webs.com are in private zone and need username and password which I have no ideas how to get them (I did registered in that new site, but the Vibrant's firmware need a different username/password to get the access).
[Captivate Android Development] anilkuj:
here you go ,

http://koush.tandtgaming.com//test/kernel-vibrant-stock.tar.md5

btw i tried to change the keymapping swapped back and home and vol up and down and rebooted the phone , no luck.

finally i can see HSUPA enabled with 3 bars i got 2.6 mbps / 1.1 mbps dl/ul speed.

just need to fix these damn keys.
[Captivate Android Development] robstunner:
Lmk how to install this an I'll try it out.i have high speed in my location and an iphone 4 to compare with.I'm getting 1270 upload with the iphone, then 150 with the captivate.really irked me when it took 20 minutes to send a 2mb picture via email over 3g.
[Captivate Android Development] anilkuj:
like strictlyphat suggested ,

i just flashed JP3 modem.bin and Stock vibrant kernel one after the other using ODIn on my Captivate which was on JH2 .

have linked the vibrant kernel in one of the threads above

and let me see if i can link the JP3 modem here

here you go,

http://uploading.com/files/5f938cb6/I9000XXJP3.tar/
[Captivate Android Development] anilkuj:
Wooow all button issues are fixed now including volume and home and back buttons

Only issue is autorotate thats very small compared to the speed gain.

Thanks to dewt for this tip! !

Just had to edit 2 files under the/ system/usr/keylayout/

S3c-keypad.kl for volume up down and

Melfas-touchkey.kl for back and home just swapped the entries using root explorer
[Captivate Android Development] robstunner:
i found in the stock rom, HSUPA_0 under:

data/data/com.android.vending.cache

and

data/mount/data/com.android.vending/

Now, i have no idea what im doing, but i wonder if just changing that to a 1 would fix the issue?
[Captivate Android Development] ranova:
Sounds like you're on to something? Voice works and upload speeds are fast?
[Captivate Android Development] Clienterror:
You're allstar lol That worked perfect.
[Captivate Android Development] Clienterror:
Yea, I did it and voice works perfect. I swapped the key numbers on the files he said and everything is just like stock except I'm getting 1.4mbs upload speed and the screen auto rotate is goofy. Other than that it's perfect.
[Captivate Android Development] madjsp:
what do you mean by "goofy?"
[Captivate Android Development] Clienterror:
It wants to put the phone in landscape holding it normal and vise versa. You go into settings -> sounds and display-> uncheck "orientation" or whatever and it's fine.
[Captivate Android Development] Clienterror:
Also for the heck of it I tried to use the vibrant OC kernel and it wouldn't load past the vibrant boot screen. So stick with the stock Vibrant kernel.
[Captivate Android Development] Zilch25:
Wait why are we using a JP3 modem.bin? Isn't that from a Froyo firmware?
[Captivate Android Development] Unhelpful:
Maybe we should be trying to figure out where the magic is in the Vibrant kernel? They're not very different, my Captivate kernel is built from the Samsung Vibrant source release. The real differences appear to be in the initramfs...
[Captivate Android Development] Clienterror:
Got me. It also seems my GPS isn't working, Played with settings and such to no avail. But then again who am I kidding it never really was "working" right?
[Captivate Android Development] Zilch25:
This is exactly what I think too. It seems using the Vibrant kernel is what allows these HSUPA enabled modem.bins to fly- which means there's something in the Captivate kernel limiting it

Talk about a sweet selling point for your next OC kernel eh? :D
[Captivate Android Development] raychang:
Unhelpful,

Are you saying that the released source codes are compilable by you?
[Captivate Android Development] Zilch25:
He's been compiling OC kernels since a couple weeks after the source was released :D Just a matter of figuring out which things need to be snatched from the Vibrant source to enable HSUPA on a stock Captivate kernel from the sound of it
[Captivate Android Development] Unhelpful:
Again, I am already using the Vibrant source. The only difference in the source is that the captivate source is missing some things, mostly audio drivers.
[Captivate Android Development] designgears:
can someone post up the init.rc while you have the vibrant kernel flashed?

adb pull init.rc

--edit, nvm, I got it
[Captivate Android Development] Clienterror:
If you guys get this working you better have a donation link in your signature ;-) I also got a couple random reboots while running this setup. One at a random time, another while backing up my apps. After it recovered from doing my apps, I tried to backup again and it was fine. Running a Setcpu stress test now....so far so good at 12 minutes.
[Captivate Android Development] clrana9017:
So, what is the definite procedure and files to do this? I just tried flashing the modem firmware of the Bell Vibrant for fun and, no surprise, HSUPA was working but there was no audio for voice calls. I would really love HSUPA enabled as this would make my hobby of uploading videos and pictures easier!
[Captivate Android Development] Clienterror:
I did a fresh install of JH3 before doing this thinking that the "GPS fix" stuff from SRE might have made it freak out and not work. It's a no go, with the JP3 modem and the vibrant kernel GPS doesn't want to work =(
[Captivate Android Development] Clienterror:
You want to have any version of the stock cappy firmware running. Then flash the modem file from post #225 then it will reboot. Then flash the Kernel file from post number #223 and it's enabled. Then just change the keys from I forget what post, it's on the same page. Then basically you loose GPS (at least it is for me, I was running JH3 before I flashed all this) and you need to turn auto orientation off and you're GTG.
[Captivate Android Development] Clienterror:
Figured I'd toss this up.
[Captivate Android Development] anilkuj:
I haven't had any issues until now

Dint try the gps yet
[Captivate Android Development] iamamp3pimp:
I wonder how long it will take them to catch on.
[Captivate Android Development] shaolin95:
I have been waiting for this and Froyo to be able to call my phone, at least for me, perfect!

Following this very closely and considering giving it a shot already
[Captivate Android Development] anilkuj:
That makes it worth it

3.2 mbps/ 1.3 mbps
[Captivate Android Development] tikidroid:
@Clienterror

Try re-calibrating your orientation and see if that fix the landscape issue.

The steps are in this post: http://xdaforums.com/showpost.php?p=7846452&postcount=651

You should be able to run sensorcalibutil_yamaha directly on your phone from a terminal app. Its in the /system/bin/ directory.

Let us know if it works.
[Captivate Android Development] TheTodFather:
Sweet jeeesus...can a brother get a witness! Good work,this proves that everyone can lead us to the promised land. Sweeet
[Captivate Android Development] Clienterror:
Gave it a shot and it's a no go, It "calabrated succesfully"......wrong, was worth a shot though, thanks for the info.
[Captivate Android Development] Unhelpful:
I think this can be fairly simple... if changing only the modem.bin and the kernel gets us working hsupa, try a Vibrant-configured kernel with a Captivate initramfs, and vice versa, and we'll know then which has the important change.
[Captivate Android Development] Clienterror:
If you make that up, I'd flash it. I'm kinda like zilch, nuke my phone repeatedly for the good of the community :-)
[Captivate Android Development] Zilch25:
It's a race to see who can discover the first legitimate brick! Go go go!
[Captivate Android Development] madjsp:
Can we just turn off auto rotation for the time being?