yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] glitterballs:
Man...I have tried every modem on this thing. I could never get JPK and JPM to connect to 850. JG8 seemed to do alright, but even that crashed on me repeatedly. I even tried the flash to stock, followed by Tayutama 1.01, and the update. After going through the whole thing with flashing, the update gave me soft reboots before I could even put my SIM in. What a shame, this is a beautiful ROM, and having a recovery and reboot menu in the power screen is genius.
[Captivate Android Development] raychang:
When the JPM failed to connect to 850, can you test install the stock JF6 (whole thing, one click) and see if it connect to 850 at that similar moment at that same location?
[Captivate Android Development] glitterballs:
I thought it had been established that Eclair modems would cause crashes on Froyo ROMs? So what exactly do you want to test? In any event, I'm done messing with this thing for today, and 850 is very weak where I live and very strong where I work, so if I mess around with trying to connect to 850, it will be tomorrow.
[Captivate Android Development] jslee1020:
Thanks!

OP... how was your experience testing with your new steps?

Does it find 850/1900 as it needs, or are you still experiencing problems?
[Captivate Android Development] brafrog:
Did you get WCDMA 850 band with stock modem? If you did, Make sure you follow all steps. Dont put your sim card until you can connect 850 band or start over.

Before following the op steps, i only got 1900 band on jpm modem inside my house. Now i get 850 band anywhere.
[Captivate Android Development] raychang:
A meaningful comparison is to test the Froyo ROM with JPM modem and the stock 2.1 JF6 (ROM, kernel, modem, the whole thing by one click) on the 850 Mhz WCDMA at the exact the same location in very close time instances. Then you will know why and what work or not. If the tests are done at very different time or locations, you cannot conclude logically.
[Captivate Android Development] Killemalll:
What's the method to block the apps ads just like DG did in Cog?
[Captivate Android Development] boomerod:
Done already. Results: JF6 connects to WCDMA 850 and doesn't even try to get 1900 to connect (this is mid-morning at my home in my office at my computer); JPM connects to WCDMA 1900 and does not connect to 850 at all (mid-morning at my home in my office at my computer). These tests were done were JF6 was a fresh flash from OOC; JPM was flashed on top of a fresh JF6. If you read through the various posts on this matter - in this thread and others - you'll find reports of not being able to connect to 850 on this modem at all.

Now, when I got outside on the JF6, it stayed on 850. As I took my test trips I left the debug screen going - on JF6 it stayed on 850 and I had 5 bars. On the JPM, it stayed on 1900 and I had 4 bars. Conclusion: JPM does not connect to WCDMA 850. This makes sense in that it is for a European ROM where WCDMA 850 is not used; it's used in the Americas and Australia. So, for those that connect to 850 while using the JPM modem, what explains that. To me, based on what I've read and then personally replicated, it is the flashing of a modem specifically designed for areas that use WCDMA 850. In my case, I used a full Froyo ROM that had the JG8 packaged with it. That seems to be important. This is very similar to newtr noted in his post, and what prompted me to test the theory.
[Captivate Android Development] boomerod:
No, if the modem is an I9000 Eclair modem, the side effect is poor battery life. If the modem is a Captivate modem, Eclair or Froyo, then yes, FCs and/or soft reboots are inevitable.
[Captivate Android Development] boomerod:
By the way, according to a PM exchange I had with Shep about a week ago, he is using Captivate framework for all his ROMs.
[Captivate Android Development] boomerod:
Credit goes to newter55 for figuring this out. I have suspected, since I began flashing ROMs, modems, etc., that remnants of previous flashing is left behind. There must be some engineering research that buttresses this notion; it's clearly not an illusion or voodoo.
[Captivate Android Development] boomerod:
What I found out fairly quickly is that this ROM seems to want to use 1900, no matter even if the signal is poor. It would periodically try to connect to 1900 in my home and then quickly go back to 850. I decided to select 850 only to keep it from using up my battery trying to switch to 1900, even though it did not do it that often. I figured since I get such a good signal on 850, in my home, and around town, I would just keep it on that. If I decide to take a trip that gets me out of the DFW area and where 850 is not available, I will just switch back to automatic. This is the compromise I've decided to live with until a Bell Froyo modem is released; I plan to stay on an I9000 ROM even after Froyo for Captivate is released.
[Captivate Android Development] raychang:
I thought that the AT&T has cut off the 850 bands in my home area for 4 days. I just use one click to restore to 2.1 JF6 and dial *#0011#, and it said WCDMA 850 band 5. That means I have that 850 band in my home for the past 4 days, but somehow the JPM cannot detect it from some time on. JPM did have problems in 850. It used to work on 850 bands 5 days ago.
[Captivate Android Development] newter55:
Search absolute system on the market. It does lots of other things but it also has a selection to block ads

edit...forgot that is not free. You can go here as well

just understand that no solution is 100%
[Captivate Android Development] Scottbg1:
Open one of Cog's zipped roms on your pc. Navigate to system/etc/ and locate the 'hosts' file. Copy that (overwrite) to the etc folder on your cappy using rootexplorer, or the like, and your in business.
[Captivate Android Development] Killemalll:
Replacing the hosts.txt file worked great! Thanks!
[Captivate Android Development] raychang:
I followed the steps in this thread, the JPM modem has been recovered and can connect to WCDMA 850 in my home again now with strong signal. I also tested in Automatic mode which selects all bands, the JPM modem prefer WCDMA 850 (the WCDMA 1900 is weak in my home).
[Captivate Android Development] momulah:
Same here afraid to flash any other roms at the moment since things are working as perfect as I want at the moment. Thanks alot to everyone involved.

Only thing is after I installed and flashed everything to get it working I noticed I have no voodoo folder in my sd. Is there a way to enable it without messing up everything else that is working so well(Edge,3G,H)?

(Just noticed I am on 1.02 full version I guess this isnt the right kernel huh.)
[Captivate Android Development] mcx6:
boomerod, do I understand you correctly, that we will have to manually select WCDMA 850 even using your recommended way of flashing, to use the WCDMA 850 band. I am in an area just the opposite of yours, mine is 1900 but when I travel I do get into some 850 bands. Will I have to manually select the 850 bands to use them while traveling or will it do it automatically. I have read alot on this but not clear on this switching automatically or not. Thank you for all your research on this issue.
[Captivate Android Development] boomerod:
That's what I noticed in my home too. But I also noticed it would occasionally try to connect to 1900 (signal bars would go down to none or one; I'd check debug/basic and it would be on 1900). From what I've read, the WCDMA 850 penetrates walls better than 1900. I need to make sure of this though as I've read some other material that has caused me to wonder (regarding GSM 850 vs. GSM 1900). I any case, what I've found is that throughout the areas that I routinely travel, and in my home, the WCDMA 850 band is strong. So, I just manually put mine on that band and will switch to automatic only when I need to.

Just use the patch to get to 1.0.3: http://www.mediafire.com/?tuh9pb702gbx3d4

No, I don't think you will have to set to manual; I just chose to because 850 is strong in all the places I routinely go.

Not sure what AT&T is doing, but the WCDMA 850 is the band they are making more available, to replace/augment the 1900 band. But this is AT&T we're talking about and, well, you never know what tricks they are up to.
[Captivate Android Development] Stephenv1971:
In my area I switched back to auto, just ran speed test 2221 down and 2014 up.

1900 band 2, 2 bars where I am right now. How this is set is really going to depend on the area I think. By the way, thanks for putting this information up, I don't think it will ever be as popular as cognition or CM6 when it is released, but for me it is providing functionality I wasn't getting anywhere else.
[Captivate Android Development] nsaia:
GPS Tanked

I've been running a few of the Cog ROMs with a lot of sucess with GPS. I decided to try this ROM because of the HSUPA which worked really well. However, after I installed this ROM my GPS has really become inaccurate. Is anyone else having this problem?
[Captivate Android Development] rickyt63:
Does 2.5mm output work with this ROM?

Hi,

I have 1 issue with COG ROM's:

- Music plays thru 3.5mm jack to (Aux) car speakers.

- 3rd party GPS plays thru 3.5mm jack to (Aux) car speakers.

- However incoming/outgoing calls cannot be heard thru 2.5mm jack to (Aux) car speakers :(.

Does Tayumata's ROM has this issue? I'd like to know before install Tayumata's.

Any info is greatly appreciated.

Thanks
[Captivate Android Development] Pirateghost:
i want to know where this 2.5mm jack is located.....all i can find is a 3.5

:P
[Captivate Android Development] rickyt63:
Hehe, it's newB typo! :)
[Captivate Android Development] Stephenv1971:
I just researched this a bit, the missing fall, dandelion, and polar clock are in the livewallpaper.apk file. I believe we are missing the proper library's and haven't got a clue how to troubleshoot further.
[Captivate Android Development] mcx6:
I installed this following the new procedures, everything went well except now 9 out of 10 Market Downloads fail. I searched this thread and did not see anybody having this problem. I have cleared the cache on downloader and market and did not help.
[Captivate Android Development] Killemalll:
The market is down for everybody. Try later today
[Captivate Android Development] mcx6:
Thanks for your reply, nice to know market is down, not just my setup.
[Captivate Android Development] boomerod:
If that's where it is, see attached from Cog Beta 8. Pulled from /system/app.
[Captivate Android Development] crazililazn:
man... its kind of retarded that this modem can't switch from wcdma 1900 and wcdma 850 correctly depending on the location... but at home, when i select 850 only, i DEFINITELY get better reception. and wherever i get 1900, i also get 850, so its not much of a loss :]

just thankful that there is finally a fix for ppl with terrible reception :]
[Captivate Android Development] timur525:
Please...

Need help,

i was planning to flash to Cog 9.1.2 so i created a folder in voodoo named disable-lagfix. I let it reboot and it moved data back to rfs and started normally. everything worked untill i started charging it. Then the screen wouldnt light up or anything. It still has Tayutama 1.0.3 installed but it doesnt do anything. Paperweight not ftw. Any suggestions?

TIA
[Captivate Android Development] Stephenv1971:
yeah I tried that, needed the odex file too, but it just doesn't show them right. It has to be a library of some sort.
[Captivate Android Development] ranjo65:
So, this is all very very new to me, but I want to help in any way that I can, even if it's through my ignorance. With that in mind I'll share my experiences over the past couple days.

This first part took place yesterday in my apt. and at work, both in the same urban area about 4 miles apart. It was my original installation of Tay's v1.0.3 (Odin to JF6, CWM to v1.0.3)

With Service Mode set to Automatic, and WCDMA 850 added, my phone would connect to 1900 Band 2 only (we all know that 850 is missing from JPM modem). At home I was getting 4 bars (rscp- -81/88) while at work I was getting 0-1 bar. Voice and data still worked, however. (I checked to see if I was still connected to 1900 Band 2, and I was but, unfortunately, I don't remember what rscp was.)

So, this morning I check this thread and see boomerods new instructions, which I follow...which lead to my phone connecting through WCDMA 850 Band 5, while set to Automatic (rscp= -61/77) Cool! My dl speeds jumped from the 1700 I got on 1900 Band 2, to 2600 on 850 Band 5. Upload speeds stayed about the same, mid 1300's. So far, so good.

But after flashing I had to take a little road trip which took me into a part of the state where there is no WCDMA signal, just GSM. What happened was that while Service Mode was set to Automatic, instead of making the transition to GSM, my phone simply lost service entirely and stayed that way until I went back into Service Mode and chose GSM. Once I did that, service was restored, the "E" icon appeared, and voice/data were back in action. Everything was good on the return trip until I got back to WCDMA-land. I went into Service Mode once again and set to Automatic but my phone stayed on GSM. So, I set it to WCDMA only and promptly lost service. After that nothing worked. Not GSM, not WCDMA, nothing. I had to reflash when I got home and I'm back on WCDMA 850 Band 5 with rscp roughly what it was this morning.

All in all I'm left wondering if this is what I'll have to go through anytime I venture outside of WCDMA coverage? Anyway, this has been my experience so far.
[Captivate Android Development] boomerod:
Thanks for sharing. That is valuable information, particularly at this point in our journey with I9000 Froyo on Cappy. Obviously, this not good news. Would you mind recalling what all you did to try to get service before deciding to re-flash?

Sent from my SGH-I897, disguised as a GT-I9000.
[Captivate Android Development] ranjo65:
Once I lost service the second time I went back into Service Mode and chose WCDMA only, no dice. I even tried choosing 1900 only as well as 850 only, no dice. When I tried GSM only, however, I didn't try to lock a single freq. I rebooted twice thinking that that might help but it didn't. The one thing that occurred to me that I did not try was a factory reset. I'm not sure if that's as detailed as you were wanting?
[Captivate Android Development] boomerod:
It is, thanks. Even if a reset would have worked it would still not be a good thing. No one wants to have to do that.

I'm going to stay with this ROM through next weekend (11/6) when I'm planning to take a roadtrip that will lead me in to GSM only territory and see what happens. But I think it's pretty clear: we need a Bell modem to make an I9000 ROM viable long-term on a Cappy.

Sent from my SGH-I897, disguised as a GT-I9000.
[Captivate Android Development] Rhiannon224:
I am having great battery life with this ROM and kernel. I see my phone toggle between "G" (2g), 3g, and "H" (hsupa) daily. I checked what modes are enabled using the SGS tools app from the market and it appears that I am usually on 1900 with a good signal. It seems to have installed with all band enabled by default. I always flash back to stock jf6 before flashing a new ROM. I have flashed other modems and kernels previously, maybe this kernal installed over another and settings from a previous modem and/or kernel remained. I didn't change any settings, I did try to enable the 850 band.and lost signal, so I reflashed back to stock and then reflashed Tayutama's ROM v 1.0.1 full and then both patches and today I watched my phone toggle between all three bands. I only lost signal briefly in an area of my job that has never had any signal with any AT&T phone but this is normal, it's been that way for years it is a dead zone. I can get slow data speed but no voice calls in this one spot ever. I am not sure what kind of signal I would get it I drove through and remote areas. I do live in an area with a lot of towers so I am guessing that helps. I love the speed.of this ROM and it is so smooth. I previously used all of the SRE and Cognition releases up until 5.5. I tried Cog beta 9 and flashed this back a few hours later. I love this setup because of speed and smoothness. I love Designgears work but this ROM has spoiled me now.
[Captivate Android Development] kangi26:
I am wondering do you know how to find out which areas are 1900 and which are 850? I'm really interested in keeping this ROM. I do very little travelling, but I do need my phone when I do go.

Edit: I found AT&T World Coverage Maps. Covering 3G 850/1900, GSM 850, and GSM 1900, http://www.mobileworldlive.com/coverage.asp
[Captivate Android Development] J-T:
Well I finally gave into the urge to flash over to Cog 9.1.1 and it was pretty good but it was short lived. I just couldnt resist coming back to this rom.I really like this rom I just hope we can get a really dependable modem for everyone's situation. Right now it works for me the area I'm in, I'm just scared if I do some traveling i'm going to be left without service. I have seen my phone go to edge service a couple of times but never long enough to test anyting... Has anyone gotten dependable edge service out of this modem at all?

______________________

Samsung Captivate:

Tayutama's JPM 1.0.3 I9000 Froyo

Xcaliburinhand Re-Oriented JPM-I9000 Kernel v2.1.1 WIth Voodoo & Color Fix
[Captivate Android Development] kangi26:
I was starting to have some issues with 1.0.2. I was having a few things going on; I was getting really bad reception no signal to -99db, where normally I get 'ok' signal. Then today I noticed the lock screen just popped up, went away, and then came back again. I also started seeing the Home Button flashing, like it was being pressed a lot. So I thought I'd give 1.0.3 a try. I flashed back to JF6. Did the complete install with no issues. Signal looks a bit better around -88db right now. I'll check battery life, signal, GPS and my Home Button issue tomorrow.

This is a great ROM and I hope the modem issue works out soon

P.S. GPS on 1.0.2 was looking better than I've seen in some other ROMS, not great, but better
[Captivate Android Development] Killemalll:
I'm back to this ROM after trying Cog 9.1.2 as well. It's just too solid. I may compromise for some time by flashing the JI6 modem over and giving up HSUPA.
[Captivate Android Development] hsnmz:
as per the documentation on Voodoo lagfix the folder or file should be named "disable lagfix".

Here is an extract from the documentation.

To archive the revert to RFS operation, you need to complete 2 operations :

■Create a file or folder named “disable lagfix” in a a directory named “Voodoo” in your internal SD card.

■Reboot

Done !

If you need to disable it without having access to your screen (ex: screen broken, you need to send it back to a repair center) here is what you need to do:

adb shell ">/sdcard/Voodoo/disable-lagfix"

I will also suggest that you revert to the original stock firmware before sending it back.

source: http://project-voodoo.org/documentation
[Captivate Android Development] arffer:
disable-lagfix

This is incorrect. It has always been 'disable-lagfix'. I looked at the documentation page you cited, and saw where it said 'disable lagfix', but that has to be a typo. Look a bit further down in your quote from that page where they show an example:
[Captivate Android Development] hsnmz:
^^ thanks for ponting that out, yes I also noticed that but considering that I have no idea about adb commands, I thought that "-" was to add a space between two words in the file/folder name.
[Captivate Android Development] arffer:
Not to in any way doubt what you have experienced, I just want to share that it can behave properly. I live in a single tower single service area, only 850GSM is available. Three miles away in the next town is 850 WCDMA and 1900 WCDMA.

As I drive between the two town, usually 2-3 times per day, my JPM modem promptly switches on its own to the strongest signal, and back again as I drive back home. I have COMBI set to all on but WCDMA 900, and AUTOMATIC.
[Captivate Android Development] ranjo65:
Encouraging news, I think! It could be that my experience yesterday was an isolated one, or that I had inadvertantly borked something in Service Mode and just didn't catch it. I don't go outside of WCDMA coverage very often so while I'm concerned, I'm not concerned enough to give up this ROM, there's just too much to love about it.
[Captivate Android Development] stndra:
no service

need help,

i just flash over to this rom use guide from first post, but i get no service.

already reboot several times and still no service.

when check the baseband version it said unknown.

thxx
[Captivate Android Development] ranjo65:
Yeah, a successful flash would show Baseband Version I9000XXJPM. Are you able to get back into Download Mode? If so, just Odin back to JF6 and start over. Also, did you flash with the SIM card in or out? If you flashed with it in, take it out this time just to be on the safe side.
[Captivate Android Development] stndra:
now i'm start over again, my flash before without sim card.
[Captivate Android Development] chrisryn:
Have you tried the disable lagfix with out the -? It works with just a space. At least for me it does on the re-orient kernel.
[Captivate Android Development] chrisryn:
Has any one tried the bluez bluetooth stack that DG was using for a bit with the reorient kernel. I know that there was thought to be bluetooth issues with HUSPA but I'm not using a modem that enables that and my blue ant is nothing but static. Was just curious if that would work. If I could find it and know how to install it I would test. But my searches haven't found anything.
[Captivate Android Development] keredini:
Just wanted to say that this is the best ROM I have used so far...I have had a few minor issues, but nothing that was a dealbreaker and have not experienced any unwanted reboots and only one or two FCs. I have only had a couple issues, namely:

* For about 4 hours or so my phone switched to Edge instead of 3G/HSUPA when i was at home. I'm using the JPM modem.

* At one point I was talking on the phone and was getting ready to end the conversation when another person called me. I say goodbye to the first person i was talking to, swiped to answer the incoming coming call, and then the popup came to end or hold the first call (as we hadn't been disconnected yet). I selected end, and then was taken back to the screen to swipe to answer the phone. I swiped, and again was presented the screen to swipe to answer the phone. I was stuck in an endless loop, even if i chose to ignore the call. This went on for about 45 seconds, i was never connected to the other caller. Eventually i had to pull the battery to reboot, as the power button wasn't working. Very strange, but that only happened that one time.
[Captivate Android Development] glitterballs:
A question for those of you using JPM modem - For those of you who get it to connect to 850, are you able to connect to both 850 and 1900 when traveling? I tried a few different modems over a couple days and never got one working that I was as satisfied with as I was with JI6. I thought boomerod wrote something about leaving 850 only on his phone, but if I have to manually switch from 850 to 1900, I'd rather just do without HSUPA.

Secondly, anyone have any thoughts as to whether or not I could flash atinm's Froyo kernel over Tayutama's ROM and then use the JI6 modem?
[Captivate Android Development] wmwilker:
I'm on 1900 here at work and on 850 at home.

I followed the exact instructions boomerod has in the op except I leave all bands checked.