i9000 - Canada Bell - Call Freeze - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I have an issue about my phone.
It freeze when starting a call and it really long before the real screen show up.
Everything else work and even internet on wireless (not wifi)
I have try many different Radio and ROM and all act the same.
Anyone have an idea ???

Wrong section. Needs to be in Q&A.
Sent from my I9000 running Slim ICS 3.4 with Devil 2_0.72

Sorry...
But since it was from a modified ROM phone i was thinking it was here.
Moved the thread

Try re flashing ur modem.

I'm on ICS and use the UGKG3 modem, works great for me in BC

Kg3 in bc too works great.
You say you try different roms, but have you wiped, and reformatted it. I'd do that with a fresh odin flash with repartition. What firmware are you running? Maybe you could do with a firmware upgrade.
Sent from my GT-I9000 using xda premium

Related

Flashed Tayutama Edition v1.0.0 for captive.. results

Froyo based rom, has the standard issues. Home and back reversed, volume keys reversed, radio does not work. Will not connect to data. (I am going to flash radio tomorrow, will post results) wifi works, bluetooth works, gps appears to work, speaker works, have not tried headphones yet.
URL: http://forum.xda-developers.com/showthread.php?t=808763
Have not tried the i9000 version yet. Will tomorrow as well. Flashing back to vibrant stock now, recovery flash didn't work. Had an SD card error when entering recovery mode.
EDIT: When I said radio does not work, I meant data. it's late. It did work, It would show a signal just no data, could not make a call. When doing a network scan, only found AT&T
I have flashed back to bionix, I need a working phone tomorrow. I am going to re-flash this tomorrow for further testing. I do not recommend anyone flash this. If I can get a working radio, i'll update here.
shouldnt all the captivate roms flashed on the vibrant have the same standard issues?
stefan.buddle said:
shouldnt all the captivate roms flashed on the vibrant have the same standard issues?
Click to expand...
Click to collapse
Yes.....
but I've said enough.
If people want to flash ROMs that are useless that's up to them...
seems like another pointless thread, that should be put in General, not really useful to anyone
Why dont u ask the devs 4 idea on how to work this out!! Then this would be a valid thread for development! With that said keep up your work eberyone has a right to post just in the right place.
Peace Out!
Sent from my SGH-T959 using XDA App
I would like to point out that the Captivate rom from tautama isn't a captivate rom at all, but an I9000 rom with an I9000 kernel that the source code that was online a few days ago was used to fix the issues of running an I9000 kernel on a captivate.
lol people keep doing this giving moons an idea that they should too, lol thing is most people here can't even flash a vibrant rom. Hahaha

[Q] poor voice quality on certain roms

http://forum.xda-developers.com/showpost.php?p=10882057&postcount=1751
I have tried Perception and Cognition. I have tried all combinations of kernals and modems but no matter what I do I get very bad voice problems (dropped words,static etc.) when I use my cappy as a phone. Could the problem be in the phone itself, and if not, does anybody have any suggestions.
Click to expand...
Click to collapse
I wanted to reply to this post but I couldn't because I dont have enough posts to comment in the development forum, so I appologize if this is in the wrong location.
Just wanted to say that I'm experiencing the same issue as richsale with Cognition. Friends were complaining that my voice was very staticy and unclear.
I flashed back to stock using Odin and everything sounds normal now. So it seems like this is not a hardware issue.
Has anyone faced similar issues with some roms?
Thanks
Most likely its a modem issue - see the modem thread in dev section..
Sent from my GT-I9000 using XDA App
Try using a ROM that has JK4 modem.
diablo009 said:
Try using a ROM that has JK4 modem.
Click to expand...
Click to collapse
Thanks
So I reflashed Congnition 3.04 and it's working now.. Before I was running it with GB's kernal, dont know what modem. That may have been the culprate.
I have Baseband I896UXJL1 right now
IIRC, Cognition is based on stock Captivate, while GB is a reoriented I9000 kernel. To run it, you'll need to replace the stock modem with an I9000 equivalent (JK4/JL2/JL3/KP1 all have ardent supporters), otherwise you'll run into voice problems. I believe it has to do with hardware vs. software noise cancellation on the two devices.
drm5 said:
IIRC, Cognition is based on stock Captivate, while GB is a reoriented I9000 kernel. To run it, you'll need to replace the stock modem with an I9000 equivalent (JK4/JL2/JL3/KP1 all have ardent supporters), otherwise you'll run into voice problems. I believe it has to do with hardware vs. software noise cancellation on the two devices.
Click to expand...
Click to collapse
So as long as my kernel and modem match I should be ok?
I'd like to flash a faster kernel on top of cognition. Perhaps SpeedMod or GB.

Darkyy's Q&A

Darky Q&A
It seems that a pinned Q&A for Darky is missing here.
I have been using Darky 8.1 and just recently decided to give 9.3 a try. One of the things I have liked about Darky is that that the version of 2.2.1 on it supports bluetooth voice dial. I have a BlueAnt S4 in my car, and although it does not voice dial 100% perfectly, it's still worth using. (the rest of the 2.2.1 roms I have tried that do not support bluetooth handsfree)
Okay, here is my question: on Darky 8.1, going to Settings - Display - Wallpaper -Lock screen wallpaper - Gallery ... would result in->
Sorry!
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
[Force close]
I seem to remember the initial update to 9.0 (or 9.1) listed that this was fixed. I just got 9.3 running last night, and this still results in a force close. Does Darky have a forum to post this kind of thing, where the developers might see it?
swype
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Bump
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Bump
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Same problem here, also on Darky 9.3 extreme cappy. I've tried reflashing the captivate swype file, restoring a previous back up, and installing the newest beta. No dice on all 3 accounts.
This doesn't seem to be a problem with just Darky though, and poking around the site it doesn't look like it is exclusive to the Captivate either.
Darky's 9.3 phone not receiving calls
Once again I would have posted in Darky thread in android development if I could..
Ever since I have installed Darky's my phone has had problems receiving calls and will often say "simcard removed from phone please reboot". Today I got a new simcard because I thought that may be the problem but I tested and it still doesn't work. My friend rung me and as the call comes through my phone loses service and the call gets cut instantly and slightly later it'll pop up saying simcard removed please reboot phone. Is anyone else having this problem? Maybe it's time to go to Cyanogen Mod..
Did you ever restore data with Titanium Backup after you installed Darky's?
Yup I restored everything that was on my old rom Cognition
That's your problem. I used to have the same problem. Your phone settings is different between the two ROMs. You should typically ONLY restore app data. Not the system data.
Try going into back into TiBu, then find 'Phone' and click on 'Wipe data'. Hopefully that'll make your calls work again. If not, you might need to reflash Darky's.
System data backups really don't work well between different ROMs (and even different versions of the same ROM).
P.S. Nice to meet another NZer btw.
Oh I see, yeah that makes sense, I asked a friend if I should restore everything I backed up and he wasn't sure so I just restored them all anyway. Now I'm not sure if I should reflash Darky's or move to Cyanogen Mod.
I would try the 'Wipe data' thing first before I try any flashing though!
Upgrade from 9.2 to 9.3 help
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
Click to expand...
Click to collapse
You can flash a Modem in Recovery just like you Flash a ROM or Kernel. If you happen to Flash a wrong Modem it won't cause any problems other than you won't get Cell Service. I am presently using the New znkp1 modem and it doing Great on my Cappy with 9.3 Darky and SuckerPunch/Voodoo Kernel.
moymike said:
Okay, Swype just expired.
"Your trial period has ended. Please upgrade your copy of Swype."
I am on Darky 9.3 extreme captivate edition. Any fix?
Click to expand...
Click to collapse
Hope u got to downloading the latest fix with Swype
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Just kinda worried cause I have read so much about people bricking their phones when putting the wrong kernal/modem combo together. I noticed on the Darky app it has options already there, so do I have to downlad the kernal seperately, or did it come with the app, or does the app download it from somewhere?
I am afraid that if I flash the modem first, then reboot it won't match the kernal and I will get stuck.
Thanks!
Click to expand...
Click to collapse
Yeah.. Use No Kernel/No Modem in DarkyRom Configurator app and do as RonH54 said!
Lockscreen Wallpaper
moymike said:
It seems that a pinned Q&A for Darky is missing here.
I have been using Darky 8.1 and just recently decided to give 9.3 a try. One of the things I have liked about Darky is that that the version of 2.2.1 on it supports bluetooth voice dial. I have a BlueAnt S4 in my car, and although it does not voice dial 100% perfectly, it's still worth using. (the rest of the 2.2.1 roms I have tried that do not support bluetooth handsfree)
Okay, here is my question: on Darky 8.1, going to Settings - Display - Wallpaper -Lock screen wallpaper - Gallery ... would result in->
Sorry!
The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
[Force close]
I seem to remember the initial update to 9.0 (or 9.1) listed that this was fixed. I just got 9.3 running last night, and this still results in a force close. Does Darky have a forum to post this kind of thing, where the developers might see it?
Click to expand...
Click to collapse
Just letting you know that in the Darky Rom Configurator App, if u enable LockScreen Wallpaper, it would use Samsung Gallery which has a battery draining bug. Hence it is an option in the Darky app before flashing.
If you really want to use it, enable it and then flash. Or I'll just work on disabling that menu option.
DriftinOutlaw said:
In the dev thread, it says you should flash a captivate kernal and modem before installing 9.3. I was wondering if anyone could point me in the direction of a guide to flashing modems/kernals.
Click to expand...
Click to collapse
Don't know if I'm too late on this but...the modem/kernel combo included has been working good for me; no need to change it. Like rickysa2000 said, don't select a modem/kernel using Darky's Configurator when you flash 9.3.
My only SMALL issue has been when going into APPS and sometimes they won't scroll for maybe two/three seconds.
But it's still my favorite ROM so far (though it's only my fourth). Especially impressed with the dev's attitude and willingness to help!!!
[ROM] Darkyy's 10.0 Gingerbread!
I was just in the i9000 forum and Darkyy said he will have a flashable rom on friday!!! I hope we can get this ported for the Cappy.
Edit: looks like beta 3 is already available for the i9000. Got so excited I impulse posted...
Sent from my SAMSUNG-SGH-I897 using XDA App
She is a he. That pic is his girlfriend. But thanks for the info.
Sent from my SGH-I897
Ha ha oops edited
Sent from my SAMSUNG-SGH-I897 using XDA App
i do not think the port will be coming anytime soon. Without source you can not have a captivate kernel. You can flash i9000 but no back button, and screen rotation, head phone jack, etc
MIUI
mcord11758 said:
i do not think the port will be coming anytime soon. Without source you can not have a captivate kernel. You can flash i9000 but no back button, and screen rotation, head phone jack, etc
MIUI
Click to expand...
Click to collapse
If its on i9000 it will be on captivate within a day lol

[Q] CM7 and Modems

So ive been rooting htc phones for a while, and my friend wanted me to root his captivate for him which was completed, and now the phone is running cm7 nightly 4/21, platypus kernel 4/27, but my friend keeps telling me he loses signal and cant make calls and or send text msgs. Im thinking its the modem, can anyone helps out a samsung noob(me lol) and let me know which modem i should use, and how to install it? i tried flashing through cwm recovery 3 but it doesnt like the scripts. thanks in advanced
Scroll towards bottom fire compatible modems
http://sourceforge.net/projects/teamhacksung/files/captivate/
Make sure your friend has a imei still on the phone. Hope you did the efs backup step
Sent from my SGH-I897 using XDA Premium App
How often does it happen to him? My buddy has a cappy running cm7 nightly no problem. I had some issues at first so I cleared system/cache/data and reflashed initial, then updated and it works fine. I lose service at times but I did before root anyways.
Sent from my robot vaccuum smartphone!
awesome thanks guys, i just flashed jl2 modem from the teamhacksung site, hopefully my friend will see better results. he said it was happening quite a bit. i also installed cm7 according to the instructions to a t
edit:i just flashed JL2 but when i look at baseband in about phone it says JK4 (confused)
Yes it is a mistake they have jk4 in the jl2 pack
You can flag any modem now just replace the modern bin in the flag package
Use the package because it is cwm 3 compatible
Sent from my SGH-I897 using XDA Premium App
awesome, thanks alot
he may have one of the captivates with a rare hardware defect that makes him incapable of using i9000 modems (jk3, jk4, jl2, kc1, etc). I have a similar captivate and am forced to use the KB1 captivate modem (check my signature), which unfortunately has no voice processing. it makes calls sound horrendous, but it maintains a constant signal. so depending on how he wants to use his phone, it may work for him (assuming he doesn't place many phone calls, just texts). if not, for now, CM7 may be unusable for him and you may have to fall back to a KB1-based ROM that uses a Captivate kernel/modem.
I suggest Torch + OverStock kernel + KB1 modem.
There's absolutely no way around it?
Sent from my ADR6300 using XDA Premium App
Please use the ROM-specific sticky at the top of the forum. That's why they're here.
DirtySimpleClean said:
There's absolutely no way around it?
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
nope. if he has a captivate suffering from this issue, his choices are to use KB1 and have ****ty voice quality or use a captivate modem/kernel combination on froyo. until audience chip is ported, there will be no alternatives.
Thread closed, since this can be discussed in the sticky.

[BUG] S5830IXXLK3 & Custom Kernels

Hi there! I was excited to get S5830IXXLK3_S5830IBTULK1_BTU firmware from samfirmware.com and flash it and use the latest custom kernel from Rafael.Baugis with it.
When I flashed 201212101860-E3-boot.img it completely killed my service. I enter the settings and it reports out of service. I says there is signal strength but I cant connect to the network or anything. I am on 3 (three) [H3G]
I tried 2 other custom kernels also: odin-kernel.tar from hell_lock (http://forum.xda-developers.com/showthread.php?t=20221470 and: PDAnitKernelNoSplash.tar from axyllum (http://forum.xda-developers.com/showthread.php?t=2026654)
Neither worked and did the same as Rafael's kernel. I thought a lot about it and tried flashing different basebands etc to see if that changed anything but to no avail I was stumped once again.
I went to a s5839i F/W from samfirmware.com S5839IBULE2_S5839IVOPLE1_VOP and the kernel works fine with that so in conclusion its the latest XXLK3 F/W that stops it working? Did Samsung 'fix' XXLK3 to not work with custom kernels? guess I go back to the old F/W and such :crying:
How can I solve this and get the kernel to work with XXLK3? I tried Alucard1989pl Deodex version of XXLK3 and same problem no service.
EDIT: Tried GT-S5830i Czech Republic 2012 November Android 2.3.6 S5830IXXLK2 S5830IXEZKL1 So far it works so its not the latest but its fine with the customs =D shame about XXLK3 though
I have a s5839i that came with stock BULE2 firmware
It now has XXLK3 (XXLK1 baseband) and it works fine with rafaelbaugis
Samsung will never "fix custom kernels", they directly allow people to modify their kernel by posting the sourcecode on their site
What country and carrier do you have?
Does the stock XXLK3 kernel give you service?
Interesting
ZakooZ said:
I have a s5839i that came with stock BULE2 firmware
It now has XXLK3 (XXLK1 baseband) and it works fine with rafaelbaugis
Samsung will never "fix custom kernels", they directly allow people to modify their kernel by posting the sourcecode on their site
What country and carrier do you have?
Click to expand...
Click to collapse
I am in the UK and my Carrier is H3G it is also the s5839i PAYG from three.co.uk it orginally had PDA: S5839iXXLD4 CSC: S5839iH3GLC2 MODEM/Phone: S5839iNELD1 but I lost that as I could not/or know how to back up from the phone as its my first Android device and indeed first smartphone too.
Maybe there is a particular bug with my firmware? though, neither XXLK3 nor the deodexed one worked, then again maybe its the CSC?
ZakooZ said:
Does the stock XXLK3 kernel give you service?
Click to expand...
Click to collapse
Yes. I would not have even bothered flashing the custom if it did not
I went to S5830i firmware to get CWM recovery using the David Jacket method but that was the only time it worked as the latest CWM kernels from Raf don't work on my device they jus stick on first screen. The e3 ones are ok though. Kinda buged me as I bought the CWM recovery pro app when I had it enbedded and working not I cant use :crying:
I'm sure there is a bug with this firmware, also see this thread. dNik17, the reason you can't get service even though you have signal is because for some reason, Android refuses to read our device's IMEI number on XXLK3. When your service was dropping out, if you had looked at your IMEI number in phone settings I can pretty much guarantee you it would have been blank at that time.
I have experienced this problem with the stock XXLK3 kernel as well as Rafael's and Hell Lock's. It does seem to be somewhat kernel dependent (and also possibly ROM dependent), for instance if you flash between stock and custom kernels it often fixes or recreates the problem. If you go into testing mode and turn off the radio and then turn it back on that sometimes fixes it also.
However, I think I may even have experienced it with stock ROM, stock kernel. I tried lots of different variations of ROMs and kernels in an attempt to nail down what exactly is going on but the issue seems to be quite unpredictable at times and difficult to repeatedly reproduce. I do know that XXLK3 has an updated stock kernel so I don't know if that has anything to do with it.
XXLK2 was fine and had no such problem.
@makeyourself thanks for the info! I am currently reverted to XXLK2 with latest Rafael.Baugis, I gave up hope of it working properly xD. I did have a back up of the partition with the IMEI info in but I did not try restoring it. I backed it up using galaxy toolboox.
I see your cooking a rom!!! good luck with that, I have tried using the kitchen a few times and but I cant seem to get the rom imported properly from the stock rom from samfirmware. I wish you more luck than I had!
dNik17 said:
@makeyourself thanks for the info! I am currently reverted to XXLK2 with latest Rafael.Baugis, I gave up hope of it working properly xD. I did have a back up of the partition with the IMEI info in but I did not try restoring it. I backed it up using galaxy toolboox.
I see your cooking a rom!!! good luck with that, I have tried using the kitchen a few times and but I cant seem to get the rom imported properly from the stock rom from samfirmware. I wish you more luck than I had!
Click to expand...
Click to collapse
Thank you mate, appreciate it :good:. Yeah I did use dsixda's kitchen just to kick things off and deodex the ROM. I use Debian, a Linux distro day-day anyway and I think that helps when it comes to extracting firmwares in tar format etc.
Yeah, the XXLK3 issue is a bit of an odd one, I don't think the efs partition is being corrupted or wiped as the IMEI number comes straight back if you switch kernels / ROMs / firmwares or occasionally just by effectively rebooting the phone. For whatever reason the ROM or the firmware is just refusing to read the efs information that is still sitting there intact. I'm sure someone will work out exactly what's going on soon anyway!
you flashed the "PHONE"(MODEM) in Odin? i think was the Modem.md5 , it comes from other country, i had that problem, just flash the Modem.md5 of my country (colombia)(MODEM_S5830M_WHLE2.tar)
carlos9545 said:
you flashed the "PHONE"(MODEM) in Odin? i think was the Modem.md5 , it comes from other country, i had that problem, just flash the Modem.md5 of my country (colombia)(MODEM_S5830M_WHLE2.tar)
Click to expand...
Click to collapse
No I don't think it can be that because I'm from the UK and downloaded the UK XXLK3 firmware. But also XXLK2 has the same modem and works fine.
Sent from my GT-S5830i using xda app-developers app
dagnabbit
makeyourself said:
No I don't think it can be that because I'm from the UK and downloaded the UK XXLK3 firmware. But also XXLK2 has the same modem and works fine.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I tried many different modems as I thought that was the logical issue but none worked with the custom kernels and XXLK3. The only time I had XXLK3 working was on the stock kernel. I am guessing that there is some difference in XXLK3 kernel that is not addressed in the custom kernels yet.
I would concur that its a problem reading the IMEI.
XXLK2 (Czech) is working nice for me atm with XXLK1 modem.
I think its wise to stick with the XXLK2 firmware at the moment.
There is definitely something weird with the S5830i, when I flashed the deodexed lk3 from this site it simply refused to boot until I flashed the Rafael img and kernel. It does have perfectly fine service though.
Sent from my GT-S5830i using xda app-developers app
Viprdxd said:
I think its wise to stick with the XXLK2 firmware at the moment.
Click to expand...
Click to collapse
I agree its working nice for me at the moment. I am using the deodexed version from Alucard1989pl :highfive:
I've learned to stay away from custom kernels because each of them are unidimensional - developers use a source code from Samsung that's always incomplete and behind the release, and each dev. works for his device, that might be a S5830c (Rafael), a Chinese S5830i (hell_lock) or the more common among users here Indian S5830i. Guess what? each variant is different, something might work on one (phone book contacts, headphones, signal strenght, 3g) but not on others. That's why I don't approve the use of "universal" next to "kernel" - sure it boots all of them, but do everything works?
I would prefer kernel developers join the android kernel kitchen project, and find ways to add their mods there, so that every user could mod their own kernel.
When it comes to custom roms, you should never flash a full wiping package (repartition) that was not meant for your phone. Always Splitfus the new rom, and replace csc, phone and bootloader with your original ones.

Categories

Resources