2.1 droid eris problem - Droid Eris Android Development

i have updated to the new software 2.1 everything works fine except i can only talk on speaker phone have anyone ran in to this problem

I have the exact same problem and am also waiting on a fix. Out of curiosity is your phone running on verizon or did you flash it to some other carrier like PagePlus?

Have you tried to reinstall 2.1?

I did, but to no avail.

i called verizon we did a hard reset and after that tech support told me to call *228 and worked updated all is good

sms440 said:
I have the exact same problem and am also waiting on a fix. Out of curiosity is your phone running on verizon or did you flash it to some other carrier like PagePlus?
Click to expand...
Click to collapse
Just FYI. No flashing required for PagePlus with the Eris. It works "out-of-the-box" on their service.

I'm on Pageplus, and after i flashed to 2.1,randomly the voice was not going out or coming in except on speaker phone, i tried reprogramming using *228, but it was still randomly happening, so i tried reinstalling the ROM, and now the phone works only on speaker.
i tried twice, same issues...some one please help
I'm unable to downgrade too, i have a feeling that i might have shot myself in the foot here.

Anybody having this issue all you have to do is go into your phone settings then go to the call menu and set TTY mode to OFF. I hope this helps

I did a hard reset or restored to factory settings after upgrading to 2.1. it is working now.

Same problem again, it worked for a day after the hard reset, it is not working again. i set the TTY off, still no luck..i cant do hard resets everyday.

kirack said:
Same problem again, it worked for a day after the hard reset, it is not working again. i set the TTY off, still no luck..i cant do hard resets everyday.
Click to expand...
Click to collapse
have u talked to tech support at verizon i had the same issue i did a system recovery and *228 and it worked fine

Related

Upgrade to 2.26.60 reset every 15-30 minutes. Any solution?

After upgrading to 2.26.60, the phone resets every 15-30 minutes.
Unlocked using GSM.
Didn't install any other apps.
Didn't root.
Any solution/suggestion?
My only guess would be to try a factory reset which might solve your problems
My phone went into something close to a death loop where it would reboot toward the end of the startup phase. It seemed like it was caused by some combination of wifi and GPS because the reboot would happen shortly after the GPS system fired up. The solution for me was to delete the Tasker app data through Settings - Applications and that seemed to correct the problem. Hope this helps.
Hmmm, I am having the same problem after the 2.26.60 update.
I also use it on GSM/UMTS mode with a SIM card. The phone works perfectly well, but every three calls placed or received it will either badly distort the sound, or reboot itself. I have an original, non-rooted phone.
Factory resetting it did not help either.
Anyone know of a way of rolling back this update? It definitely did not happen before.
Thanks!
hk9090 said:
Hmmm, I am having the same problem after the 2.26.60 update.
I also use it on GSM/UMTS mode with a SIM card. The phone works perfectly well, but every three calls placed or received it will either badly distort the sound, or reboot itself. I have an original, non-rooted phone.
Factory resetting it did not help either.
Anyone know of a way of rolling back this update? It definitely did not happen before.
Thanks!
Click to expand...
Click to collapse
You can go back simply by flashing the 2.26.20 SBF. You'll find a link for it somewhere on the forums.
Droid flashed back to 2.26.2. Working perfectly now.
Apparently there is a bug with the latest update and using sim gsm networks. It is a shame though not being able to update the software; especially with a brand new, original, unrooted, unmodified phone.
Sent from my DROID PRO using XDA App
http://forum.xda-developers.com/showthread.php?t=923552

[Q] Error sending/receiving MMS "National access coverage not available."

Hello,
Lately I have been unable to send or receive text messages that contain pictures or videos. The error message is always the same "National access coverage not available."
I called Verizon, on Thursday of last week (1-13), and the technician was unable to figure out the problem. He escalated it to the next level and said that someone would be contacting me in a day or 2. Well it's now Wednesday (1-19) of the following week and so far, nothing!
Has anyone else run into this problem? If so, what's the fix? Any help would be appreciated, especially since Verizon has been no help at all!
I'm using a Moto Droid2 ver, 2.3.2 Rooted and OC'd @ 2.25Ghz
Thanks,
Scott
Dial *228 and update your PRL.
silverfang77 said:
Dial *228 and update your PRL.
Click to expand...
Click to collapse
Thanks for the reply.
Unfortunately, it didn't work. I updated it waited the 15 minutes. When it didn't work I rebooted the phone figuring maybe it needed to be refreshed or something, (long time windows tech, reboot fixes everything!) but still nothing. Just that same message.
I get the exact same error when sending or receiving MMS 50 percent of the time with the first initial try... *228 does not fix this.. verizon cannot fix it either...
OK, got tired of waiting for Verizon to call back. On the phone with 2nd tier support now for about the last hour, so far nothing.
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
OK, got finished with the Verizon tech, who was very helpful, but we still could not resolve the issue.
She removed and reloaded my data from the server, switched me to another IP address and did a few other behind the scenes things but nothing worked. She suggested doing the factory reset, but I'm ready to give up troubleshooting this issue yet. If all else fails, then I guess I will have no other option.
Since sending MM text's in not a huge part of what I use my phone for, I may just wait for the next release of the software and hope that fixes it.
In the mean time I'll just keep playing with settings and searching Google and the message boards in the hope that someone can come up with a fix that doesn't involve having to wipe it.
rtfield said:
Mine started doing that on mms after using juice defender app and I had to do a factory reset to fix it.
Click to expand...
Click to collapse
I used to use that app, but removed it long before this started happening. I wonder if it left behind some orphan files that are somehow in there wreaking havoc?
Since the problem still existed even running the phone in safe mode, I would think that would not be the case, but anythings possible.
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
1250x said:
my phone does the same thing with same message... if i try again to download message it will usually come through, but if it happens on outgoing message it will never go through
Click to expand...
Click to collapse
That's the thing. Since so many people are having the same or similar issue, I just find it hard to believe it's not something on Verizon's side or with their software. This many people screwing up their phone's in the exact same way all around the same time just seem a little suspect to me.
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
rtfield said:
Mine happened 6 months ago. Just reset it and see what happens. All your apps with reinstall by themselves.
Click to expand...
Click to collapse
Yeah, I guess I'm going to have to try something. I want to make a nandroid backup first just to be safe and then I'll give it a shot.
Thanks.
This is great!
So, I just finished the factory reset (which DID fix the problem) and was starting to configure all my custom settings when the Verizon tech I spoke with called me back. She said that she had just spoken to Motorola and they said it was a known problem with their phones! They are not sure what it is yet, but they are working on it. In the mean time, the only thing they can suggest is to reset the phone as a work around!
I asked the Verizon tech if there was any kind of documentation about this that she could send me, but of course there isn't. And there's also nothing on the Motorola site about the error either, at least nothing I could find.
While it doesn't make the situation go away, it does make me feel better knowing what the root of the problem is, sort of. Only problem is, there is no guarantee that it won't happen again.
i turn airplane mode on then off... works for me
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
S.Meezy said:
i turn airplane mode on then off... works for me
Click to expand...
Click to collapse
Yes, I had heard that worked for some people, and I did try that but it still didn't work. Even so, that would only be a work around and not really fixing the issue.
V.A.T.Juice said:
Im having the same problem. I even reflashed to stock motorola, still does it. I noticed if i hold down on failed pics or tap download a few times it works. The problem seems to be triggering the data on and off from the send button.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Interesting, since I did the factory rest I haven't had a problem. If it happens again, I'll be sure to check that.

Device keeps entering "Emergency Callback Mode" for no reason

I have an HTC Hero that keeps entering "Emergency Callback Mode" for what seems to be no reason at all. It mostly happens as soon as I answer an incoming call but also randomly in between.
This mode kills all data conenctions and prevents outgoing calls for 5:00. But, even if I say cancel, or wait the 5 minutes, it still stays on and I have to reset the device. It usually resolves itself after 45 mins or so. It happens once or twice a day.
I have researched the issue on google and I have found very little information about this problem. On some phones, this mode is enabled immediately after calling 911 to allow rescuers to call you back and locate you via GPS. I have never called 911 on this device.
I am currently running Cyanogen 7.1 RC2 ROM but I had the same issue on many different ROMS I tried so its not related to that.
on baseband 2.42.01.04.27. Maybe I should try downgrading it? How can I do that safely?
I really don't want to try reverting back to a stock ROM...
EDIT:
I think I posted this in the wrong forum, mod please move, sorry.
Hmmmm........so a complete doesn't solve the issue? And when you say ''sense'', does that mean with sense, it doesn't happen, but with the other Roms it does?
Try updating your radio to the latest .29
Yea its Me Again With the
Modified Hero
I just upgraded to the lastest baseband and it's still doing it.
I also figured out I can trigger the problem immediately by going to mobile network settings and changing my roaming preferences.
I should probably not that I recently repaired this phone and used QPST service programming tool to copy settings over from a touch pro 2 to the Hero. Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Just did a PRL update. No luck...
Did a succesful over-the-air profile and PRL update. Same problem...
ki1022 said:
Could there maybe have been a wrong setting from the TP2 that is affecting the CDMA on this phone??
Click to expand...
Click to collapse
Sounds like it. Is there no way to put everything back to default manufactured settings?
oohaylima said:
Sounds like it. Is there no way to put everything back to default manufactured settings?
Click to expand...
Click to collapse
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
ki1022 said:
I am considering using a stock RUU to completely wipe the phone to factory settings, but am trying to exhaust all my other options first so I won't have to re-root it and set everything up again... I'm almost at that point though.
Click to expand...
Click to collapse
!!!!!!!!!!!
FIXED IT SUCKAS.
Did a ##786# which reset all the CDMA settings, then re-did my NAM and data profile settings and it works. Go figure. Doing the ##786# on this phone also retained nearly everything including meid, baseband, recovery, and ROM. All it did was fix the problem. Awesome.
I still have no idea what was causing this to begin with, it was driving me crazy. Hopefully this thread will be helpful to someone else who has the issue.
On a side note, how dumb is this emergency mode?? So you call 911, then you can't call anyone else after that?? What if you need to call your wife and kids to say you love them one more time?! Haha.
Awesome!!!!!! Glad it's fixed. Now I'll just star this just in case it happens to me.

Nexus S total network loss.

So my girlfriend's Nexus S has been losing the entire voice and data network and going into no service mode, no biggie at first, just cycle airplane mode, then it went on to rebooting because you would select airplane mode from the power off menu but it would not check the box in the wireless settings menu.
After the reboot the box would show checked and airplane mode could be disabled and the service would resume. The the phone started getting stuck in airplane mode and not even rebooting it would bring it out the first few times, then it got to the point of resetting the phone, a wipe cache/data reset didn't fixed it. So off to T-Mobile for a new sim card. Rebooted the network immediately. And as of last night its back in full force and now not even a new sim will resurrect the network.
Have tried wiping, reflashing stock 2.3.3, new sim again, multiple resets, had to get an toggle widget to get it out of airplane mode and still a dead network, all this time the network in the *#*#4636#*#* menu showing unknown and is not able to be changed and reverts back to unknown immediately, OEM specifics settings button is greyed out and you are not able to disable the radio either.
While I'm going to call Samsung on Monday and I guess send the phone off, I worry about mine because it too does it but only once a month or so, but I do constantly have issues resurrecting the phone from airplane mode at times because the box will not be checked in the wireless settings menu but I can see the airplane instead of network bars, problem persists with reboots sometimes.
I also would like to add that even when the box is not checked in the wireless settings menu for airplane mode, if you click it it just hangs forever and will try to select but never will and stays grey like its turning everything off, but if the scren goes off its like you never tried.
Has anyone else seen this? I have seen a lot of people with data network issues or having to reboot to get voice network back but nothing as bad as I'm experiencing.
Both our phones are and have been completely stock and unmodified.
Thankfully we still have her Vibrant and in case I need to send mine in my Nexus One.
Sent from my Xoom using XDA App
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
cdaly985 said:
Have you tried restoring from another persons' pre-made nandroid backup?
This over-writes the radio firmware, you should give it a go!
I also found that I had problems on 2.3.3, however reverting to 2.3.2 gave me no problems!
Just contact me if you need any help restoring from a nandroid backup or finding the 2.3.2 backup files
Click to expand...
Click to collapse
Is that true? I am just on the verge of calling samsung. My phone won't connect to or display any available networks, and is pretty much now dumbed down to a small tablet. I've tried everything except another persons nandroid backup. I've been told to stay away from flashing another persons... but I'm really desperate.
If you could provide me with a backup, that would be awesome.
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Gawthorne said:
I'm having identical problem.
It was working fine yesterday, look back to it and now it's got no mobile network, nothing. Just the no bars and cross symbol. I've tried wiping dalvik cache, reflashing the radio, wiping data/factory reset, reflashing the rom, restoring with a backup (Backup of when I first rooted the phone) and still no signal. Nothing has worked..
Anyone got ideas on how to fix this issue?
Click to expand...
Click to collapse
Can you search for and view available networks?
This sounds like the CM7 powerwidget problem (3g/2g) I used it and I loss all network, phone process will crash every second, however if your phones are stock I can't think in anything causing it.
For CM7 you'll have to reflash and delete userdata or edit the sql database for the providers and change a value to 0, but you need root.
When I went to *#*4636.... my preferred service was "unknown" too, but now it is OK.
Try to dail:
*#*#4636#*#*
and find your network information.
ketchup539 said:
Can you search for and view available networks?
Click to expand...
Click to collapse
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Gawthorne said:
Nope. Sits their 'searching' but nothing shows up.
In, *#*#4636#*#*, it gives little to no information. Just says nothing for current network and for GSM disconnects it has,
Sate: DvInactiveState
disconnected with last try
at 9:59AM
fail because No Error
And that time never changes, stays at 9:59AM.
As my above post suggested, I've tried doing a factory reset and reflashing. I don't think I use CM.. I flashed with Oxygen 2.1.6 (using it's kernel) but I restored to Oxygen rom and trinity kernel after it didn't work.
Click to expand...
Click to collapse
That is the EXACT same problem I have. I too was using Oxygen 2.1.6 and lost all connectivity. I've just locked my bootloader and flashed back to stock ready to send for repairs. That rom must be doing something >.>
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Gawthorne said:
Oh no
I didn't want to send it back D:
Anyone got some suggestions that I haven't tried?
Click to expand...
Click to collapse
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
ketchup539 said:
I've been trying *everything* for last past few days. Nothing is working. That shouldn't stop you from trying though. Just stay well away from ODIN and those i9023 files, I've seen bad things.
Click to expand...
Click to collapse
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Gawthorne said:
Cheers, going to a mates place soon to see if he has anything up his sleeves to try and fix this annoying issue..
If we somehow fix it, I'll be sure to post how we did here.
Click to expand...
Click to collapse
Ok, it'd be great if you worked something out. I'm so glad i'm not the only person with this issue!
Anyone had any breakthroughs? *hopeful*
I wouldn't call it a breakthrough but I got somewhere!
Ended up putting a extremely thin piece of wire into the external antenna port at the back of the phone. Wasn't too keen on doing this, but my phone now has reception isn't stuck at the dreaded -113dbm.
The reception isn't good, but it's enough to send texts and have calls.
Although the area needs quite good reception for me to receive anything, and it's extremely sensitive. To get 3 bars in a place where I usually get full bars, I have to be outside. While inside it's reduced to none or 1 bar, which is enough to send/receive texts and a sort of lagging phone call (did a few tests). As mentioned before extremely sensitive. The phone seems to like it better when it's up-right. In the middle of the CBD at Brisbane I get full reception and 3G, which is fine but in the places where you usually get 2 bars, you get no signal at all, unless you're outside.
So this is hardly a fix. I will most likely be sending it to Samsung to get it actually fixed. Either that or get it fixed the same day and pay probably close to $100 so I don't have to wait 2 months waiting for Samsung to twiddle their thumbs.
Thats awesome! But I'm going to post mine off to Samsung USA tomorrow, which will take forever considering international shipping. Where could you get it fixed same-day? I'm going to try this wire thing
So it can't be a software issue, but maybe the rom overloaded the antenna and fried it or something? I'm glad we've got that far.
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
RcrdBrt said:
I've seen that nexus s has a problem like the iphone, the antenna gate. Try take the phone with the left hand looking to no touch the rear of the softkeys
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
Its more serious than that my friend! Thanks anyway
I got a quote from a place in Brissy called "FixMyMobile" and they said if they can fix it, it will cost $99. Although I'll get quotes from different places (if I find them) and see what they charge however I don't think I will be able to get cheaper, most likely around the same price..
So I may do that to not wait the ridiculous time it will take to get it back from Samsung.. Not sure on places in NZ though.
Yeah it seems like a hardware issue definitely. I eventually reverted the phone back to stock everything and it still happened, so that there shouts hardware issue.

[Q] unfortunately, the process com.sec.ims.android has stopped

Hey guys, my wife has a stock Note 3 and every so often this prompt will pop up "unfortunately, the process com.sec.ims.android has stopped" If I hit ok, it will go away for about half a second and then pop up again. I can restart the phone sometimes or have to pull the battery and it won't happen again for about a week, but this is a problem that I need to resolve and I know someone in here has the know-how. I've looked all over the place on the internet, and on this forum but no one else has experienced the same thing, I'm puzzled. Please help, thank you.
gacn87 said:
Hey guys, my wife has a stock Note 3 and every so often this prompt will pop up "unfortunately, the process com.sec.ims.android has stopped" If I hit ok, it will go away for about half a second and then pop up again. I can restart the phone sometimes or have to pull the battery and it won't happen again for about a week, but this is a problem that I need to resolve and I know someone in here has the know-how. I've looked all over the place on the internet, and on this forum but no one else has experienced the same thing, I'm puzzled. Please help, thank you.
Click to expand...
Click to collapse
Go into settings>General>app manager>All> find contacts and open it then clear cache. If that doesnt help. Clear cache and data. Fixed it for me.
Galaxy Note 3
gacn87 said:
Hey guys, my wife has a stock Note 3 and every so often this prompt will pop up "unfortunately, the process com.sec.ims.android has stopped" If I hit ok, it will go away for about half a second and then pop up again. I can restart the phone sometimes or have to pull the battery and it won't happen again for about a week, but this is a problem that I need to resolve and I know someone in here has the know-how. I've looked all over the place on the internet, and on this forum but no one else has experienced the same thing, I'm puzzled. Please help, thank you.
Click to expand...
Click to collapse
hey there , wondering if you got your problem resolved , I have the same problem my phone start with that error today & even if I reset it , when I try to make a phone call come back up so I do manufacturer reset & still the same damn problem can anyone help me?
scooby2604 said:
hey there , wondering if you got your problem resolved , I have the same problem my phone start with that error today & even if I reset it , when I try to make a phone call come back up so I do manufacturer reset & still the same damn problem can anyone help me?
Click to expand...
Click to collapse
Same thing started happening to me on Friday 11/21/2014 morning.
I've tried:
Clearing cache and data in contacts.
Restarting the phone.
Reset the phone to factory default.
Wipe cache.
In some situations it will work for a call or two and then the same error message again.
Thank You
Hey, I keep having the same problem, but when I turn off my 4gLTE and just set it to just 4G not LTE the phone works fine, I can receive and make calls fine them when I turn on LTE I cant make or receive calls and my phone gives me the. unfortunately, the process com.sec.ims.android has stopped. Please try to see if this works for you, if it does it has to be the network.
this happens to my phone from time to time, but in my case, I only dismiss rhe pop up, and everything runs fine, I am also puzzled about this too
Same problem here, november 23 2014
I've done everything possaible....no answers??????? metro pcs...phone was a T-Mobile switched...Note 3
---------- Post added at 02:26 AM ---------- Previous post was at 02:15 AM ----------
sm0ke0ne said:
Hey, I keep having the same problem, but when I turn off my 4gLTE and just set it to just 4G not LTE the phone works fine, I can receive and make calls fine them when I turn on LTE I cant make or receive calls and my phone gives me the. unfortunately, the process com.sec.ims.android has stopped. Please try to see if this works for you, if it does it has to be the network.
Click to expand...
Click to collapse
ok this did work for me...but data will not work when im in this mode...network it is...im pretty upset2 days of dealing with this b.s....to metro pcs I go tomorrow...thanks for the help I will keep you updated
I have a t-mobile note3 switched to metro
I'm having the same problem . I tried what everyone was suggesting and nothing worked for me. I also tried Google and nothing. I Went To 2 Metro But Then Say It Was My phone. It seemed like they were not even trying to help me since the phone is tmobile. Everything works ok just the calls part. Some one help! It's frustrating
Has anyone been able to identity and or fix the issue? I'm also having the same problem phone works fine as far as everything I just cannot make or receive phone calls sometimes I never know when. I have it unlocked to use it with MetroPCS and it was working fine it just started one day. I have tried a brand new Sim card, factory reset, even disconnecting it and reactivate the phone...no luck. On WiFi calling it works perfectly so makes me think it's not the phone but make me wonder if it was the network why only us out of the millions of people...if anyone has any updated regarding this issue please get back with us. Thanks...
This worked for me!)))))
gunn714 said:
Has anyone been able to identity and or fix the issue? I'm also having the same problem phone works fine as far as everything I just cannot make or receive phone calls sometimes I never know when. I have it unlocked to use it with MetroPCS and it was working fine it just started one day. I have tried a brand new Sim card, factory reset, even disconnecting it and reactivate the phone...no luck. On WiFi calling it works perfectly so makes me think it's not the phone but make me wonder if it was the network why only us out of the millions of people...if anyone has any updated regarding this issue please get back with us. Thanks...
Click to expand...
Click to collapse
Go to settings...then calls...press that VOLTE then just turn it off. I've been weeks with my phone and finally this worked for me. I went through the same thing everyone else did..it sacked but now my phone working great hope it works out for u
lala4 said:
Go to settings...then calls...press that VOLTE then just turn it off. I've been weeks with my phone and finally this worked for me. I went through the same thing everyone else did..it sacked but now my phone working great hope it works out for u
Click to expand...
Click to collapse
@lala4 ...thanks i did just like u said and so far it has been working great for me no issues anymore..u are a lifesaver
Dizy801 said:
Go into settings>General>app manager>All> find contacts and open it then clear cache. If that doesnt help. Clear cache and data. Fixed it for me.
Click to expand...
Click to collapse
yea i am curently experiencing the same problem
I tried the same thing and it works as long as i dont restart the phoen. Then it starts all over again. Very frustrating. Does anyone know if what this process does or if you can disable or uninstall this? Maybe thathat would work, as long as it is not something you really need ofcourse. Thanks.
You can try the same thing using titanium back up. that helps sometimes. Just open Titanium backup. locate ur contacts and phone apk. click them and then click clear data. i havnt tried this method but its worth a try. maybe the next time i experience it i will try this as well.
Dizy801 said:
You can try the same thing using titanium back up. that helps sometimes. Just open Titanium backup. locate ur contacts and phone apk. click them and then click clear data. i havnt tried this method but its worth a try. maybe the next time i experience it i will try this as well.
Click to expand...
Click to collapse
I tried doing that already and same message appears when i restart phone. I was thinking of freezing the com.sec. Ims.android and all ims related using titanium, but wanted to see if anyone knows what these processes are used for.
Question??
lala4 said:
Go to settings...then calls...press that VOLTE then just turn it off. I've been weeks with my phone and finally this worked for me. I went through the same thing everyone else did..it sacked but now my phone working great hope it works out for u
Click to expand...
Click to collapse
What is "VOLTE"????
I had the same problem and i went to the app manager>all and there I found the process that always crashes (com.sec.ims.service) and I forced to stop, and it's seems to have solved the problem by now

Categories

Resources