Related
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Atra said:
I'm having this problem and have seen several others with same. When trying to use VC, get the "..have encountered a problem, try restarting" error. I fixed this problem with registry corrections before but the required Keys are not setup when installing under WM5 or lower. Just having this problem with WM6 (reloaded 1.7.1). Any ideas?
Click to expand...
Click to collapse
What else do you have loaded on your phone(s) that have this issue. I use VC on all WM6 and WM5 roms that I've run (and ones I've cooked, like the Crossbow Reloaded ones you mentioned) and have never had this error and I've never tweaked around registry settings. I just install the cab and it works...
Are you installing VC 1.6 US?
With all the WM6 roms i've used (not as many as some but i'm new here) I haven't had an issue with VC 1.6 US either.
don't think it's a definite answer, but i did have this problem in the past when i installed voice command on my memory card rather than on phone memory. sometimes during loadup after a soft reset i would get that error...think it's because it takes longer to load from the card and voice command is setup to run right away (always in the background)...
if it's installed on the phone memory...dunno...sorry
I run VC 1.6 US and have never had a problem with it. I always install it in main memory.
I give..
Going back to WM5 Molski. To answer some of the post..
It's VC 1.6
No other software loaded..Fresh flash.
Installed to device, not storage *only option offered for install location*.
Get a message during device install: (...recommend installing to main memory. Do you still want to install to "."...) I answer Yes because it just aborts install to say No.
Thanks for the replies guys..
<--[Totally Screwed]
OK, now I have no sound from the speakers and Mic not working. While in Phone mode, the speaker button stays in the On position and won't turn off. Got the old Voice Command registry settings in place but it seems the new problem is the culprit. Going to start a new thread with new problem unless someone has any ideas..
Closing out
Back up and functioning on Molski 3.3 Crossbow. From what I can tell, during the WM 6 load, the speaker phone option became stuck in the On position but the speakers and Mic were not functioning. Voice Command seemed to know there was a problem and gave the "..restart VC.." message. After re-flashing Molski (a few times, still no joy), I flashed with the wired earbud/Mic connected. After flash and phone restart, I removed the headset while in phone mode. Speaker button reset to normal, phone speakers/mic started working again. Reloaded Voice Command and all worked.
aaahh the joys of PDAdome.. Where else can you get the thrill of accomplishment by getting back to the same friggin place
Thanks again for the replies all..
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Give Molski a try..
Avatar28 said:
I have actually had this error a LOT with various ROMS, all were based on the Faria real thing base I believe. I'm not sure if that's relevant or not. At first it would just pop up randomly. Sometimes I could restart it and it would be fine, others it would never restart until I soft reset. The errors tended to get more and more frequent until it finally stopped working completely. Even on a reset it would come up right away. I hard reset that particular rom and it was fine for awhile but the issue returned and much more quickly. I never really installed any software onto the phone that ran in the background so I'm really at a loss as to what causes it. The last couple of ROMs I used didn't have VC and I never bothered to reinstall it because it kept having errors anyways. I am about to reflash yet again so I guess I'll put it in if it's not already there and see how it goes.
Click to expand...
Click to collapse
I didn't have any problems with his roms (..and went back to it with no probs). Only started having problems after I tried the Faria WM6. If the Molski works for you let me know. We'll give Faria a nudge.. Good Luck!
VC issues I've run across
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
At one point I had a strange issue with the bluetooth microphone.... VC would work fine (I'd ask "what time is it" and it would tell me the time) but when I was in a call, no one could here me.... I ended up enabling and then disabling auto gain control... wallah, mic works again.... weirdness.... (don't think this was rom related)
Anyway... the roms that I've had this problem with was XDA Mobile 6 (release 1... relase 2 is kicking a$$) and I think NBD 7.1... never had a problem with a ny Pandora cooked roms.....
Anyway... my $.02... (I'll probably get change)
kudo's to the rom wizards that be...
never had a problem. Installed in a few different roms. works fine
installed to main memory.
wolverine9827 said:
I've tried pretty much every WM6 rom out there.... and cooked some of my own using the Pandora Kitchen.... and it seems that VC 1.6 decides to ignore my bluetooth activation button on some roms... all incoming calls and texts and reminders get announced as expected and the handsfree works great, but I can't push the headset button and get VC to wakeup.... Tried disabling VC and then re-enabling it, repairing the bluetooth, removing and then readding VC... nothing would fix it.... reflash with a different rom and presto! VC works!
Click to expand...
Click to collapse
Voice Command Bluetooth Fix
View attachment 43147
I can't take credit for this and I can't give credit but Thank you...!
I've used this and has worked when VC w/n initiate via earpiece.
There's several threads on the specifics of this cab.
I have the app on my phone and i still recive the text messages from sprint but the program isnt detecting them
I haven't attempt to get the Sprint Visual Voicemail working on AOSP 1.6, but I will attempt to get it working, once quiet releases the update to AOSP 1.6 later this week.
Good Luck. I have been working on getting it working on 2.1 and ASOP 2.0...yeah...about that. Lots of variables in play
Cheers,
Matt
gu1dry said:
I haven't attempt to get the Sprint Visual Voicemail working on AOSP 1.6, but I will attempt to get it working, once quiet releases the update to AOSP 1.6 later this week.
Click to expand...
Click to collapse
Ok thanks!!! i have the app on my phone already i guess it just needs some programing internally..
Anyone making progress on this?
I'm loving running 1.6, even though it's AOSP. Everything is great except I really like VisualVM.
I can't even find the apk to try...advice?
Is_907 said:
Anyone making progress on this?
I'm loving running 1.6, even though it's AOSP. Everything is great except I really like VisualVM.
I can't even find the apk to try...advice?
Click to expand...
Click to collapse
The apk is sprint_core.apk or something along those lines.
i wanna be able to send messages without problems or thephone not working without being on speaker THEN the visual spirint voicemail D:
Is_907 said:
Anyone making progress on this?
I'm loving running 1.6, even though it's AOSP. Everything is great except I really like VisualVM.
I can't even find the apk to try...advice?
Click to expand...
Click to collapse
Since I have my voicemail re-assigned to Google Voice, no more worries of Sprint's version. Give it a shot, the app is awesome!
magicalan said:
i wanna be able to send messages without problems or thephone not working without being on speaker THEN the visual spirint voicemail D:
Click to expand...
Click to collapse
Everything but the speaker in the phone app works for me. I just did a backup, wipe (from recovery), and flashed.
daveydave said:
Since I have my voicemail re-assigned to Google Voice, no more worries of Sprint's version. Give it a shot, the app is awesome!
Click to expand...
Click to collapse
Got specifics on setting up GV's VisualVM going properly? All I would want from GV is the VisualVM. No need for any of the other stuff (calls etc.)
I'll play with it a bit now
I have changed over my voicemail to Google Voice and that seems to be the way to go for all platforms. I have even stopped giving out my regular phone number and instead opt to point people to the gv.
i am curios to know this too. I believed that the message sprint sends to triger visual voicemail was a MMS. Now that MMS has been resolved for this ROM, is visual voicemail working? Anyone tried it?
All you have to do to get the your VM to go to your GVoice acct is log into your GVoice acct on the computer, go to Settings & there will be an option, with instructions, on how to activate/setup it up.
Awesome. Apparently it was working for a good 30mins before I realized it haha.
I like this! I left myself a VM and got an email notification of it (on my phone) before I even opened the Voice app on the phone to make it check for VMs more often heh.
I'd use GV for VM over the Sprint one any day and on any ROM.
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Additionally here is a video on the Voice Actions for Android, NOTE: This is different from the Bluetooth Voice Dialer as it has additional features
http://www.youtube.com/watch?v=tPPcTN5sdX4
and
http://www.youtube.com/watch?v=8Ml34vtrGwc
Wow, this is fantastic. I was following the info posted in that AR 3.2 thread, so I'm happy to see something posted.
I'll give this a try tonight.
legend221 said:
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Click to expand...
Click to collapse
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
BillTheCat said:
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
Click to expand...
Click to collapse
Thats exactly what this does, install and you'll see this for yourself mate.
Sent from my fast / stable HTC Inspire 4G
I am running AR 5.1.3. Voice dial works fine from the phone but when I try to initiate it from my bluetooth headset I get a Force Close of processcom.android.voicedialer. I uninstalled voice dialer with TB and then installed the bluetooth voice dialer from this thread via CWM and I still get the force close when initiating from my bluetooth.
Any ideas on how I can fix this other than flashing a new rom?
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Wow this is cool to have. Im not having much accuracy though. Ive got a 2 year old Jawbone Prime so my bets are that its the problem. Looks cool but hasnt played nice since day one. Anyhow this does work if you got a decent headset
Did you ever figure this out?
toadleyb said:
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Click to expand...
Click to collapse
svarzaru said:
Did you ever figure this out?
Click to expand...
Click to collapse
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
xperi said:
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
Click to expand...
Click to collapse
Download Cyberon Voice from the market. It does cost a couple of bucks but it makes all problem go away on every rom you need BT with. At least for me it did!
Confirmed working with Virtuous Unity 1.24.0 Sense 3.0 based on Pyramid with Vlingo
Man just what I was looking for will give it a try.....Thanks
Sent from my Inspire 4g using XDA Premium App
missing voice dialer
I tried to flash it, and it didn't do anything. I'm using Virtuous Unity v1.27.0. I even tried to extract the app from the zip (which currently doesn't exist on my phone) and install that way, but it says "application not installed". Nothing happens at all when i hit the button on my bluetooth. With the stock rom, before installing VU, it would pull up the voice dialer. But i can't even install it now. Can anyone help me out? Thanks!
EDIT: Got it to install, but now it force closes when I try to use it, with or without a bluetooth headset.
awesome!!!!!
I'm running AHD 6.1 but it lacks the ability to let bluetooth headset to do voice command. but after i flashed this it worked out fine!!
and btw im using vlingo to do voice dialing, its an awesome app!!
legend221 said:
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Click to expand...
Click to collapse
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
crypted said:
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
Click to expand...
Click to collapse
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
homeslice976 said:
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
Click to expand...
Click to collapse
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
crypted said:
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
Click to expand...
Click to collapse
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
homeslice976 said:
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
Click to expand...
Click to collapse
Right. That was my assumption and my plan once I got home tonight to do that assuming no-one confirmed it for me. Will flash after while and edit post with results.
I flashed this to arhd 6.1.1. It don't work. App did not appear to be installed. I tried installing the apk and it would just say application not installed.
So it appears to be a no go.
Sent from my HTC Inspire 4G using XDA App
My fellow Canadians...
I have noticed a number of issues with the latest official firmware for the Rogers captivate. I think it would be a good idea to put them all in one place and try to start figuring out what common issues exist and perhaps we can address them all at once. Please state the issue, when it seems to happen, and what if any modifications you have made to your software setup. Maybe someone will notice a pattern or trend and we can get them resolved.
Thanks!
Reserved +10 char
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
clemmie said:
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
Click to expand...
Click to collapse
Did you try a factory reset after you updated?
Voice for Swype
The voice command for Swype doesn't work.......
1. Speed dial no longer works. Says 'USSD code running' then closes and gives message 'unknown application'
2. GPS has stopped working completely.
As far as the launcher crashes, I don't use touchwiz. I do use Launcher Pro. It does seem to crash every so often. I've replaced all my widgets because I've read somewhere that this might help.
No random shutdowns here.
I talked to a samsung technical support rep and his captivate's swype voice input didn't work either.
iam_immigrant said:
1. Speed dial no longer works. Says 'USSD code running' then closes and gives message 'unknown application'
2. GPS has stopped working completely.
Click to expand...
Click to collapse
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Nick0703 said:
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Click to expand...
Click to collapse
I also don't have any issues with the GPS or Speed Dial. My only mod was rooting with the FUGU kernel.
erbsmokah said:
Did you try a factory reset after you updated?
Click to expand...
Click to collapse
I hadn't thought of that; I wonder if I'll lose my root? Come to think of it, I wonder if that's causing the launcher crashes...
Nick0703 said:
GPS works perfectly on mine captivate 2.3.3 and I get better reception and locking time. But GPS will stop working if you flashed a custom Kernel on it! I know that because I tried it and GPS wasn't working when I had a custom Kernel, had to flash back the stock kernel.
Edit: I just tried Speed dial and it's working perfectly, I think there is something wrong on your phone.
Click to expand...
Click to collapse
Got the phone from Rogers with 2.1 then upgraded to 2.2 then to 2.3.3 (all done through Kies. GPS was ok but spotty on 2.1 and much better with Froyo but hoped Gingerbread would bring more improvement.
I've tested it since Rogers released 2.3.3 and on a few occasions I've even gone to the roof of my building on a clear day and waited for 45mins!! and nothing! Not lock then lose it but NOTHING! Speed dial I can live without but I actually use the GPS quite a bit.
Since upgrading I've done a factory reset 4 times and even sent it in for repair, which came back saying "upgraded SW and factory reset" which fixed nothing.
I've just rooted (just root nothing else) and I've tried to do use the gps code but I can't even get into that!!
What can I do at this point?
iam_immigrant said:
Got the phone from Rogers with 2.1 then upgraded to 2.2 then to 2.3.3 (all done through Kies. GPS was ok but spotty on 2.1 and much better with Froyo but hoped Gingerbread would bring more improvement.
I've tested it since Rogers released 2.3.3 and on a few occasions I've even gone to the roof of my building on a clear day and waited for 45mins!! and nothing! Not lock then lose it but NOTHING! Speed dial I can live without but I actually use the GPS quite a bit.
Since upgrading I've done a factory reset 4 times and even sent it in for repair, which came back saying "upgraded SW and factory reset" which fixed nothing.
I've just rooted (just root nothing else) and I've tried to do use the gps code but I can't even get into that!!
What can I do at this point?
Click to expand...
Click to collapse
Yeah, with the 2.3.3 you can't access the gps setting by entering the code, because everything you enter the code *#*#3214789650#*#*, you'll get a message saying "Service mode has crashes blablaba...". The only that I found to bypass that was to go to market and install the app "Anycut" then launch it, select New Shortcut, Activity then choose Angry gps.
I'll look up what's the problem that causing you not to get a good gps signal.
Sent from my SGH-I896 using XDA App
Nick0703 said:
Yeah, with the 2.3.3 you can't access the gps setting by entering the code, because everything you enter the code *#*#3214789650#*#*, you'll get a message saying "Service mode has crashes blablaba...". The only that I found to bypass that was to go to market and install the app "Anycut" then launch it, select New Shortcut, Activity then choose Angry gps.
I'll look up what's the problem that causing you not to get a good gps signal.
Sent from my SGH-I896 using XDA App
Click to expand...
Click to collapse
Man I was going nuts trying that gps code. Googled and searched this forum and everything pointed to that code. Was ready to toss my phone off the roof!
Was reading these forums for the past couple weeks learning how to root/flash (just rooted today actually) to get gps working.
I'm guessing I might have to try flashing it again with the stock rom from this thread http://forum.xda-developers.com/showthread.php?t=979133 but gotta do some more reading before attempting it.
iam_immigrant said:
Man I was going nuts trying that gps code. Googled and searched this forum and everything pointed to that code. Was ready to toss my phone off the roof!
Was reading these forums for the past couple weeks learning how to root/flash (just rooted today actually) to get gps working.
I'm guessing I might have to try flashing it again with the stock rom from this thread http://forum.xda-developers.com/showthread.php?t=979133 but gotta do some more reading before attempting it.
Click to expand...
Click to collapse
I use an app called GPS Status from the market. There, in the menu under 'tools', you can 'manage A-GPS state and wipe the location info the GPS has back to scratch. Then download the assistance data from the internet. This worked well for me and I do it from time to time to keep things current.
Sent from my SGH-I896 using XDA App
clemmie said:
One major issue I have noticed is when updating apps through the 3.1.5 market. It seems to only happen when I am updating an app, not when I am installing a new app:
Sorry!
The application TwLauncher(process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again.
At which point I have to force close it.
Also, I have experienced random shut downs, I will click the power/screen lock button to unlock the phone, and it seems the phone has shut itself off. If you hold down the power button it boots normally.
Anyone else experiencing these issues?
Click to expand...
Click to collapse
How long have you had the phone? The random shut downs is not a ROM issue. I am pretty sure it is a hardware problem. It was acknowledged by Samsung. There is even a list of effected builds. I am sure you could find the build numbers with a little search. I had this problem when I first got the phone last December but had Rogers replace it. If it is the same problem, I think you will notice that the sleep of death only occurs when the battery is like above 85% or somthing like that. It has been a while so I can't exactly remember.
I can't seem to get the firmware actually downloaded. I'm going through kies and it recognizes my phone, and recognizes that I need to upgrade, starts downloading the upgrade and at 12% it disconnects. I have two screen shots here that show what I am talking about.
Any ideas?
clemmie said:
I use an app called GPS Status from the market. There, in the menu under 'tools', you can 'manage A-GPS state and wipe the location info the GPS has back to scratch. Then download the assistance data from the internet. This worked well for me and I do it from time to time to keep things current.
Sent from my SGH-I896 using XDA App
Click to expand...
Click to collapse
Tried this the entire day and still nothing. I know it's kinda cloudy out today but still nothing.
i found 2.3.3 very slow, and poorly built. no voice button in swype PEEVED me off.i was originally making my custom canadian rom off Kh2 (rogers 2.3.3) but i dropped that project and released a canadianized/rogersized KJ3 (2.3.5).
one of the best roms in the dev section. and will be updated by the end of the week with the theming all included. the pic in my sig is a link to the rom if you havent seen EFFIN EH!
Unable to update my Captivate
My captivate is still 2.2 and while connecting to Kies it says this version of the device cannot be updated.
Current version shows PDA: JL1/phone: JL1/CSC: JL1 (xxx).
I had rooted via Super one click and I can see Superuser installed. I havent used it for any purpose.
I removed my external SD card and did factory reset. No luck.
nambisan said:
My captivate is still 2.2 and while connecting to Kies it says this version of the device cannot be updated.
Current version shows PDA: JL1/phone: JL1/CSC: JL1 (xxx).
I had rooted via Super one click and I can see Superuser installed. I havent used it for any purpose.
I removed my external SD card and did factory reset. No luck.
Click to expand...
Click to collapse
flash to stock 2.3.3 using the link in my signature. YOU NEED BOOTLOADERS coming from 2.2
Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
clcrawl said:
Hello, I did some searching and couldn't seem to find anyone else with this issue so I figured I would post. I just installed the latest CM10 Nightly (20120825). Everything went fine phone booted up seemed to be working great (was super responsive). Then I made a call, the call will go through however the "Phone" app basically locks up. And I can't talk, and I can't hear the other end of the call. Oddly enough if I pickup the call on my other phone and hangup the app displays this but still no voices can be heard. Anyone else had this odd behavior? I did do a full factory reset / wiped cache before installing.
Thanks in advance.
Click to expand...
Click to collapse
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Thank you very much, I am going to give this a try shortly.
scarroll825 said:
This is a known issue with the 08/25 build. Try using 08/23, a lot of people have been having success with it.
Click to expand...
Click to collapse
The 8/26 nightly fixes this issue and was just posted to get.cm.