[Q] Bad voice quality when conversing with landline on custom ROMs? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi everyone,
My girlfriend currently owns an Samsung Galaxy S i9000T (Telstra-brand, so it has an 850MHz antenna) that's running the XXJW4 firmware with the DVJV4 modem from Telstra's 2.3.3 KIES update.
Due to Touchwiz being fairly clunky (as in overall, not the launcher), my girlfriend had been interested in custom ROMs. However, whenever I install one for her (be it CM7, AOKP or similar) she seems to have trouble with voice quality (both on hers and the other's end) when talking to someone using an older landline phone. Usually they can't hear her for a few seconds, then there's a lot of lag on the line. Sometimes they just can't hear her entirely.
With AOKP I tried to flash the DVJV4 modem via Odin, which quite obviously didn't work. The modem hasn't been CWM zipped either, so no luck there. I'm unsure if it didn't work because it's a custom ROM, or if it's because it's a Gingerbread modem.
With CM7, I used the latest 850MHz enabled modem for the i9000. This seemed to work fine for data, as well as talking to other mobile phones, but not when it came to older landline phones (yet again).
DVJV4 seems to only work well with official Samsung firmwares. Why is this? Is it impossible for her to run a custom ROM (especially CM7, which was very snappy) with the DVJV4 modem?

If you already have CWM, you can flash any modem you like. Search on forums for suggestions for your country, even operator

Related

[Q] Flashed new rom/kernel, now call quality is bad

I'm trying to get to the bottom of this problem: it started ever since I flashed Cognition 3.02 and Firebird 2 kernel last week. That was my first endeavor into custom roms. This week I'm on Cog 3.04 and Speedmod kernel. I'm in the US on ATT in a big city with good signal strength.
It's the strangest thing: I can hear calls perfectly fine, but the other people that I'm talking to complain of static and background noise, and basically can hardly hear a word I'm saying.
Anyone know what in particular causes this type of situation? I really don't want to go back to stock rom, but I may have too because, well, I do need my phone to... you know, make phone calls.
What modem are you using? You are using an i9000 base kernel you want to make sure you are using an i9000 modem. I would suggest jk4
http://forum.xda-developers.com/showthread.php?t=835272
Look in the modem thread under development. I am using the UGJL2 Modem. Having great success with it.
Sent from my SGH-I897 using XDA App
I'm using the UXJL1 modem. Is this somehow bad/incompatible?
At this point, I'm not looking for any frills or speed, I just need something that's going to be rock-solid dependable. People complain about call quality all the time when I talk to them. It's weird, because everything sounds perfectly fine on my end.
Also, sorry for the dumb question, but I didn't see in the modem thread on how you actually install a new modem? Do I just flash it like a rom/kernel, etc.? Can I use Clockwork for this?
Flash through clockwork. Dl to phone move to sd. In clockwork select install zip from sd, find modem, select.
Jk4 is used by most i9000 roms. I would start there.
Jl1 is a rogers captivate kernel best performance with i9000 kernel will be a i9000 modem
If you are using the firebird kernel you can use a captivate modem for best call quality at the cost of losing hsupa.

[Q] SpeedMod, but without a modem flash

Hello folks;
A quick question...
I have the latest SpeedMod, and in a lot of threads in the forum people recommend flashing an i-9000 modem with the kernel, with the concern of compatibility issues where you would have the i-9000 kernel with an 896/897 modem.
I haven't had any problems with the stock Rogers Froyo modem(uxlj1) and SpeedMod. Should I flash a new modem anyway? What will the benefit be? Am I just not noticing real problems that are there, or is there something to the Rogers Froyo Modem that works with SpeedMod without the need to flash a compatible modem?
Also, what could go wrong if I do? Seems some people have trouble with data and bluetooth after flashing a new modem.
If you have working bluetooth I believe there would be no need to flash another modem
Thanks for that.
Whenever I flashed Speedmod without changing over to an I9000 modem with it, I had horrible voice call issues where it would sound like I had my vocal cords removed and talked through one of those voice boxes.

Can Bell Vibrant JK4 Modem be made to work on Rogers Stock Froyo?

I'm rooted on Rogers Stock Froyo with the latest SpeedMod revision and the stock Rogers Froyo modem. I am having no issues at all with this setup.
However, I tried pairing the phone with my car's bluetooth, and it(predictibly) turns out I don't have bluetooth. I have done some research, figured that a lot of Rogers users are using the JK4 modem, but that it has it's own set of issues(GPS, etc). Most (perhaps all) of these users have custom ROMs installed; I don't, but I gave it a shot.
Upon an attempted installation, I got this message:
E:copy_data_default_apk:Can't mount DBDATA:
Installation Aborted
So, I understand that there are some custom ROMs that iron out some of the GPS and Bluetooth issue, but is there an i-9000 modem that will work with the Stock Rogers Froyo release? I'm not really ready to sacrifice the stability for speed, and FWIW I am fine without bluetooth if everything else is stable and working fine.
However, I'm still curious if anyone else is running SpeedMod on Rogers Froyo and has found a modem that gives bluetooth functionality without flashing a custom ROM?

[Q] Bell i9000m and Ginger bootloaders - safe?

Hey,
I skimmed through the forums and saw various posts about people asking what ROMS were safe for the i9000m but haven't seen anything about sbl.bin
As most of you probably know, the i9000m was plagued with sd card corruptions pre JL2. Then, that miracle FW introduced a new sbl.bin that solved some stuff and the sd card corruption went WAY down. Now, with the arrival of Gingerbread and new bootloaders, i was wondering if it was safe to use these new bootloaders on our i9000m devices and still benefit from that miracle cure that the JL2 bootloaders provided. Its pretty much the only concern i have thats stopping me from going to Gingerbread.
Thanks
BottleB said:
Hey,
I skimmed through the forums and saw various posts about people asking what ROMS were safe for the i9000m but haven't seen anything about sbl.bin
As most of you probably know, the i9000m was plagued with sd card corruptions pre JL2. Then, that miracle FW introduced a new sbl.bin that solved some stuff and the sd card corruption went WAY down. Now, with the arrival of Gingerbread and new bootloaders, i was wondering if it was safe to use these new bootloaders on our i9000m devices and still benefit from that miracle cure that the JL2 bootloaders provided. Its pretty much the only concern i have thats stopping me from going to Gingerbread.
Thanks
Click to expand...
Click to collapse
I'd also second this question but add on to it the following:
boot.bin
sbl.bin
Both safe?
In addition:
Can we go back to eclair/froyo if we want, in order to reflash official from kies in Canada?
Can we use our own CSC?
Does this support the 850 band, or do I need to flash the KC1 modem?
Will the phone die?
We thank you all for your time
1. yes
2. no
3. yes if you use the method here: http://forum.xda-developers.com/showpost.php?p=12156313&postcount=438 or just keep using JL2 or KC1 modem
4. mine hasn't yet, been on gingerbread for about a week or so now
moved to gingerbread and can't see why you would want to go back to an earlier firmware.
custom rom and especially a custom kernel transform the phone completely: much faster, much better functionality and better battery life
you can still connect to kies, but why? odin and cwm provide a much better means to upgrade and change firmware and open source development is much better than anything Bell will ship
things to realize: (1) the sgs is incredibly resilient and robust, most "bricks" are not bricks at all but recoverable with download mode and reflash (2) there's lots of expertise to see you through every situation and every rom chef and kernel developer has its loyal fan base, so try for yourself and find the combination that works best for you
do we need to update the bootloader if we come from KC1 and we want to upgrade to JVH?
not to use kc1 modem with JVK rom no: but if you are coming from 2.2 froyo rom to 2.3.3 gingerbread JVK rom, you need bootloaders to move from the 2.2 rom to the 2.3 rom
the sequence is:
1.change rom from 2.2 to 2.3 stock JVK with GB bootloaders (see http://forum.xda-developers.com/showthread.php?t=1047924)
2. change stock JVK rom to custom JVK rom (deodexed, zipaligned and rooted) using cwm sd card zip method
3. if desired, flash compatible performance JVK kernel (using odin or cwm) note: many roms include kernel, check features list -- this step is only to replace the included kernel that got you rooted or to swap it out for one that has different performance features (speed, battery life etc)
4. activate 850 mode in JVK modem or reinstall KC1 modem (flash in odin or use cwm sd card zip).
5. go into cwm recovery, perform backup and then add custom modded theme if desired -- do the backup of the full functioning system before doing theme changes, that way if anything goes wrong you are starting from the completed install and don't have to repeat everything!
5. load titanium backup and restore apps: use market to update and then set up your launcher
6. do another backup!
Seems more complicated than it is. Along the way if anything hangs step 1 is always pull the battery and reboot. If that doesn't do the trick, step 2 is pull the battery and use the 3 button control to go into recovery mode, reflash and reboot, and if that doesn't work, use the 3 button control to go into download mode and reflash the part that hung, and if that fails, go into download, connect to odin and start at the beginning!
shamelessly stolen from all the good guides that dot the xda landscape and a surfeit of trial and error!
Here is what I did. At first I was on KC1 (updated trough kies). Later I flashed a 2.2.1 JS8 based ROM, without modem or boot loader (so these two were still KC1)
I wanted to try gingerbread. So I flashed the gingerbread starter through heimdall (boot loader and kernel)
I booted in recovery and installed my custom JVH ROM (took the rooted deodexed JVH ROM, removed a few stuff, edited gps.conf for north-america and replaced Swype with a fr-CA enabled-one), upgrading the kernel (to default JVH) but not the modem.
So my modem is still KC1 (850 MHz working out of the box) and JVH works fine.
zorxd said:
Here is what I did. At first I was on KC1 (updated trough kies). Later I flashed a 2.2.1 JS8 based ROM, without modem or boot loader (so these two were still KC1)
I wanted to try gingerbread. So I flashed the gingerbread starter through heimdall (boot loader and kernel)
I booted in recovery and installed my custom JVH ROM (took the rooted deodexed JVH ROM, removed a few stuff, edited gps.conf for north-america and replaced Swype with a fr-CA enabled-one), upgrading the kernel (to default JVH) but not the modem.
So my modem is still KC1 (850 MHz working out of the box) and JVH works fine.
Click to expand...
Click to collapse
You can use this procedure (as stated before) and use the latest modem with 850hz support
http://forum.xda-developers.com/showpost.php?p=12156313&postcount=438
I got JVH running with a full flash and 850hz
What exactly does the 850 band give us? I've never switched anything on or off in regards to bands/modem and my phone has always given me a signal and a data connection. What exactly do you get when you enable the 850 band? Also how do you know if it is enabled or not?
Some places in Canada have poor or no 1900 MHz coverage. In this case you will want 850 MHz.
I noticed my phone used 850 MHz mostly indoor and in rural areas. To check you need to go in service mode (I don't remember the code by heart but it starts with #*#*)
@t1mman
Thanks I know but I think it's easier to say on KC1 as I have no problems with this modem.
no problems
been on jvb for a week with zero problems, this phone was previously sent in for repair prior to 2.2 jl2 release... so things seem to be good... i flashed ugkc1 modem for 850 band

[Q] Downgrading Android Versions -- Verification

I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by @BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
dawgdoc said:
I have a SGS Captivate I have been using as a sports tracking device and as a music player for the past year. I now have a few questions before changing ROMs on it.
History >> Two years ago I soft bricked it while on CM9. Not being able to resurrect it at the time I purchased an SGS3 and set the Captivate aside for a while. I resurrected it using a KK4 Heimdall One-Click and immediately flashed it to CM10.1. Having been on CM10.1 for a number of months I upgraded the device to CM10.2. After doing so I noticed the bootloader was listed as unknown and the baseband was KG3. I have checked this in terminal emulator and using a "Samsung Info" app from the PlayStore. I've verified the KG3 modem is for the i9000. I checked in the updater-script of the CM10.2 I downloaded and installed and observed it being coded for captivate and for i897. So, I am not fearful that I downloaded the incorrect ROM.
I have known of the above discrepencies for months and have not been terribly concerned. I do not know if they could have something to do with the fact that I have not had a sim card in the phone since before I resurrected it. Even though I do not currently plan to use it as a phone I intend to have it in a condition to do so if needed. That, and I was interested in flashing a ROM I have seen recommended several times by BWolf56, Gamerzrom Legend 4.0. The questions I have stem from the fact that I will be going from a ROM based on Android 4.3 to one based on 4.2.2.
To correct the bootloader and modem I intend to flash, again the KK4 stock ROM (Gingerbread). This will be with the Heimdall One-Click from the forums, Odin is not an option - I run Linux. Once installed I will verify bootloader and modem. Based on the Gamerzrom blog I will then install CM10.1 before installing their ROM. (This could be avoided if I were not going back to stock.) At each step I will wipe and format as indicated, I will probably wipe and format to excess.
[Q1] Is this the best approach to get to having the 4.2.2 based Gamerzrom installed from where I am?
[Q2] Should I not do this at all, the donwgrade, even to stock, could seriously damage my phone?
[Q1] Is there anyone who thinks I could safely shortcut the above by simply flashing the KK4 bootloader and modem?
(If I can still find a download on the forums.) This would eliminate going back to stock GB and then to CM10.1.
[Q2] Is there no reason to worry about the bootloader and modem? The discrepency is simply an artifact based on there being no sim card in the phone and I would be best off advancing directly to flashing Gamerzrom from CM10.2.1.
Click to expand...
Click to collapse
1: don't need to flash cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flashing stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
BWolf56 said:
1: don't need to flag cm first but you do have to flash the ROM twice to repartition it then flash the gapps.
2: flagging stock should recover/fix your unknown bootloader issue but unless your imei is unknown, you shouldn't have any problem using as a phone if needed.
I do suggest flashing KK4 before going to GamerzROM to avoid any issues.
Click to expand...
Click to collapse
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
dawgdoc said:
The imei is still present at least according to "Samsung Info" and using getprop in terminal emulator.
Okay, flash stock KK4 rom, no need to flash CM10.1, but flash Gamerzrom 4.0 twice.
I was getting CM10.1 from Gamerzrom 3.0 installation instructions for those coming from GB. I was thinking going back to KK4 would reset the partition scheme to GB. I guess the double flash of GLE4.0 takes care of the repartitioning back to JB layout.
Thank you.
Click to expand...
Click to collapse
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
BWolf56 said:
That's exactly it, whether you flash cm or gamerz twice, it will do the same thing and repartition. Just don't forget the gapps after.
Click to expand...
Click to collapse
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
dawgdoc said:
Thanks, I wouldn't dare forget GAPPS.
In fact, I have already downloaded both GAPPS and the ROM -- that was about 6 hours ago. I probably will not flash until Monday. :{​
You know, I am a bit surprised at how regularly posts are made to the Captivate forum. More often than I would have expected.
Click to expand...
Click to collapse
While it's an old device, it's really great and some of us keep supporting it
Mixed Results with increased understanding
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
dawgdoc said:
Well I went through the process I outlined above, or tried to do so.
I downloaded a One-Click stock rom, android 2.3.5, from this thread. It is actually the same leaked stock rom I used two years ago. I flashed it twice per instructions to get the bootloader, doing so to correct my unknown bootloader issue. After this was installed I used a "Samsung Info" app to verify bootloader and modem. The modem was KK4, yet the bootloader was still unknown. I repeated the process twice more with the same results.
Rather than download a different stock GB rom I proceeded with the remainder of my plan. I flashed Gamerzrom Legend Edition 4.0 from here on the recommendation of @BWolf56. I wiped, formatted, and then flashed twice as he recommended. The ROM didn't boot, but not to worry I repeated the process. Still no boot. I next went ahead and flashed CM 10.1.3 and booted into it. The bootloader was still unknown and the modem was now listed as KG3, an i9000 modem, again. My guess is CM did this since this how it was listed before I went back to stock. I now went back to Gamerzrom and successfully flashed it. (Still showing bootloader unknown and modem as KG3.)
I am setting up the phone this evening. So far in addition to installing ROMs and adjusting settings I have verified wifi works. Later tonight I will be testing the GPS and bluetooth. With the "wrong" modem my results could be decremated, but I don't expect them to be. When I was previously on CM 10.1.3 and 10.2.1 and on the KG3 modem all worked. Bluetooth, wifi, and GPS worked that is, I didn't try calls because I wasn't using it as a phone and didn't have an appropriate sized sim to borrow.
If I need this device as a phone I will first try it as is with bootloader unknown and modem as KG3. If that doesn't work I will flash an i897 modem, probably the KK1 modem, and see how that works. If that doesn't do the trick I will try an earlier GB stock One-Click rom, either KK1 or KJ3.
Click to expand...
Click to collapse
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
BWolf56 said:
Modem doesn't affect BT so it should be fine. It's odd that Gamerz didn't boot but glad it turned out fine. Also, having a different modem won't change anything about the bootloaders but that being said, I highly doubt it would stop you from using it as a phone.
You're seeing I9000 modems cause the ROMs were often built off the international version of the Captivate. Both I897 and I9000 work well on the device and you can flash whichever one gives you the best results in terms of networking (which you don't seem to be using anyway).
Click to expand...
Click to collapse
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
dawgdoc said:
True, the kernel controls BT and wifi. I'm not sure why I was mentioning BT w/ modem.
I think I didn't organize my thoughts too well in that last paragraph. Closer to what I meant was that if needed as a phone I would try it as is >> unknown bootloader and KG3 modem. If I had any troubles with it working I would try a different modem. This is where I was erroneously thinking that the i9000 modem may turn be a problem. If that didn't fix it then I would go with another stock ROM to give another go at fixing the bootloader issue. I actually think/hope it would work as it currently is. The phone has repeatedly booted, so at least the sbl (?) secondary boot loader partition is intact.
BTW, the GPS seems to be working well, even though I have a 10/08 build device. Bluetooth, on the other hand, is not pairing with my Linux laptop nor a cheap bluetooth speaker. The same held true when I was on CM 10.2.1 with the cappy. Both, the laptop and speaker, pair with my SGS3.
Could the reason the Gamerzrom didn't flash straight off is that I was coming from a stock TouchWiz 2.3.5 rom instead of from any JB rom? Thank you for helping.
Click to expand...
Click to collapse
BT not working can be cause it wasn't updated in so long or kernel issue. Or could simply be that it doesn't work with your specific devices.
I flashed mine off stock KK4 (same one you flashed), tried to boot without flashing it twice, which of course didn't work but then went back in recovery, re-flashed and it booted just fine.

Categories

Resources