Texting issue/ phone app relation? - Samsung Captivate Glide

I have the android.phone.com whatever b when I upgraded to ICS, and I'm gonna due a factory reset as soon as I have the time (gotta write act one of a screenplay in five days), but yesterday and the day before, my phone wigged out on some tested and received ten copies of it instead of one. This isn't happening all he time, just with specific numbers or messages. Is it related to the android.phone.com thing or do I need to go to ATT? Stock locked phone. -Ara
Sent from my Nexus 7 using xda app-developers app

It is an ICS glitch.
It is already discussed in the ICS Leak Issues Thread..
http://forum.xda-developers.com/showthread.php?t=1833518&page=8
Please search in forums before making new threads..
Btw i am not facing it anymore after running NardROM

Related

[Q] Phone Doesn't Ring When Receiving A Call

Hey Everyone! So I'm having this problem where my phone will NOT ring or show that someone is even calling. The only way I found out that someone called me is when they text me asking why I didn't answer them. Well, my simple answer (that people are starting to not believe) is that my phone didn't even show that someone was calling... This wasn't so much an issue before because they could always text me if they needed to get a hold of me. But now after to applying to many places for a job, I kinda need it to ring. I also have another issue and that is that texts will not receive either. The only way I can get them is through Google Voice. This wasn't such a big deal to me but I would like to know if that can be fixed too. I have never had this issue until after I tried CM9. Since then I have tried many other ROMs to see if i still had this issue. I did.
The other ROMs I tried are:
MIUI v4
AOKP
Clean GB
Marcusant v3
MIUI Gingerbread
CM7
Legendary
What my current setup is:
ROM: AOKP
Android version: 4.0.3
Baseband Version: S700.0.5S.EI22
Kernel Version: [email protected] #6
Build Number: IML74K
Mod Version: aokp_epicmtd_build-28
Theme: NONE
PLEASE!!! ANY HELP IS APPRECIATED!
Odin back to stock EL30. Follow the procedure in the How to restore a semi-bricked Epic thread. Test it there. If it works root and flash, do not restore data.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Odin back to stock EL30. Follow the procedure in the How to restore a semi-bricked Epic thread. Test it there. If it works root and flash, do not restore data.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I did this and (sorry for taking so long to get back to you but i wanted to make sure that it was happening often and not just once in a while) it worked for the phone ringing but the messaging, although im receiving them, they come late. sometimes VERY late like a whole day later. This is not cool and would really like to find a solution because i dont want to have to be stuck on stock :'( Oh yeah btw the ROM i flashed this time was AOKP. Thank you for the help!!
I believe late texts are a symptom of carrier network issues. It should clear up when the maintenance is finished.
Sent from my PantechP4100 using xda premium
I am having the same issue with the phone calls either coming in late or not at all. I test this by calling my number from a land line. It takes 4 - 5 rings before the phone will start ringing, if it rings at all. Most of the time, Google Voice answers for voicemail.
I remember back in the days when I had my Windows phone, there was something that we could do to have the phone poll the towers more often to make the phone ring faster. I know that this faster response to phone calls came at the expense of more battery usage. I wonder if some of the battery saving tweaks done by the ROM developers has had a negative effect on the phone calls coming in.
I have tried updating my PRL and whatever through EL30, then reflashing with out restoring any data. Still having the issue.
Thanks.
this same thing is happening to me and everyone else in my neighborhood that has sprint. Its one specific tower that's causing the issues. I know this because once I connect to a different tower the issue goes away. I contacted sprint about it and they said they would fix it when they do the network vision upgrades, which could be a ways away.
Sent from my cm_tenderloin using Tapatalk 2 Beta-5
kennyglass123 said:
I believe late texts are a symptom of carrier network issues. It should clear up when the maintenance is finished.
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
I kinda thought it was a problem with the network and so i called them and last time they sent me a airave and it didnt solve the problem. I still think its a problem with sprint overall and am planning on calling them.
I have the same exact problem. I have even had the phone replaced and it still does it. I only know when it happens because google voice logs the missed call. I have had it happen with a completely stock phone as well as rooted.
It is very frustrating because like you said, people don't believe you when you say that your phone did not ring.
They are actually going to switch my phone again. I know this is not going to fix the problem, but I will play the game!

Can't update my phone in any way

Hey guys, I'm new here, so this thread is probably on here somewhere, but oh well. I can't update my S3 OTA or through Kies. I know there is an update, as my friend got it fine on his yesterday (it's the one with the brightness slider in notification center). On OTA, it says communication failed every single time, then says up to date. I have tried clearing data and all that as well. And in Kies, it also says I have the latest firmware, even though I know I don't. Any ideas? I really don't want this happening when Jelly Bean comes out. Oh yeah, I'm not rooted or anything by the way, I'm still on stock for now.
I have the same exact issue. I think it has something to do with ATT and the phone not being set up right in their system. Did you by chance have an iPhone before your S3 and use the same Sim card?
Mine wouldn't find the ota on the phone. I searched around here and found a thread someone had started that has instructions on how to download the flashable zip and install it via CWM. Worked like a champ. If you are rooted this is the way you'll want to go
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yes I did come from an iPhone. And I am planning to root soon so I might have to try that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Vanillamarble said:
Hey do you mind giving me instructions on how to do that? And is there a safe way to root my phone on a Mac? And last of all, can I still get updates such as Jelly Bean on a rooted GS3 without losing root without messing anything up? Sorry I'm coming from iPhones and jailbreaking so I'm not familiar with all this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
I had the same problem with not being able to get the OTA update on my S3. Turns out it was a bad sim. As soon as I got a new sim from AT&T everything worked fine. Wish I would have done that first cause I spent hours on the phone with AT&T and Samsung trying to fix the problem. Good luck. Hope that works for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Same issue here. Just spent a couple hours this Saturday at an AT&T store - end result is that they are swapping it out under the manufacture 1 year warranty.
Sim replacement did not fix it for me.
Tech support over the the stores land line says that the option to push OTA to phone is greyed out and not selectable with my account.
They are sending me a new phone so we'll see.
G-Man. said:
I've always recommended returning whatever device you have back to 100% stock (as it was out of the box) before taking any official updates. I've heard ppl say they can take them just fine while still rooted - but they lose root. Sometimes you can simply re-root, sometimes you have to wait for a new exploit to be discovered before you can root again. In light of this, I always wait a week (sometimes less) after a new OTA (Over The Air) update is released, just to be sure I can regain root immediately. Welcome to the wonderful world of Android OS!!!
[edit] to answer your post about not being able to take the last OTA update. Have you tried a factory reset? Through Android Recovery? You will lose personal settings and contacts if you dont back them up. But, it may solve your update issue. Another thing I know, that a lot of ppl do is - as soon as you buy a new device, such as the awesome Galaxy S III, is to immediately do the factory reset. (Who knows how many employees have goofed around with the new toys they just got in stock)
Click to expand...
Click to collapse
Read through the thread guys - there are other answers given besides just swapping the sim card...
Ok I'm going to try a factory reset. Wish me luck guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just did a factory reset, and it didn't help at all. Now I've got to get everything back on my phone. Coming from iPhone, I will say that Apple has a heck of a lot better backup system. I do 0refer my GS3 though. Ok so any suggestions now?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
you've tried to update over cell network AND WiFi... correct? same error each time?
I'm not sure what else to suggest except trying a new sim card like someone else suggested... beyond that, a replacement device. Sorry man, wish I could be more useful...
[edit] The only other thing I can think to try would be to completely remove all your current USB Drivers for Samsung from your PC and reboot the PC, then re-install the USB Drivers, and try Kies again. If it still doesn't work, try a different PC.
Well I'm going to try a different computer, and if that doesn't work, I'm going to an AT&T store. Thanks for all the help guys.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Possible JB Bug: View Type: Alphabetical list

So I've been fighting with Touchwiz force closing quite often since the JB update. I flashed the full official ROM from Telus, as well as 2 other Telus based ROMS, all suffered from the same problem. The only thread I found pertaining to a similar issue is HERE.
Issue:
Touchwiz force-closing (stopping), when creating folders, or moving icons on the homescreen (like to delete them or move them to another homescreen).
In a nutshell, myself and 2 friends all have GS3s. 2 of us were having the issue, myself (rooted) and my friend (unrooted, completely stock), where as another friend (rooted) was not having the issue.
After much hair pulling and testing (3 different ROMS, using different computers and cables to flash, having my device flashed by my friend who was not having the issue), I came to the conclusion that Touchwiz was force closing ONLY when the App Drawer was in "Alpahbetical List" view type. When it was in a "grid" view type, there were no issues.
I was wondering if anyone else could do some testing and let me know if I'm on the right track with this.
I ask that you change your App menu to "Alphabetical List", and use it normally for a few hours or days, and let me know if you see any instances of Touchwiz force closing. If I see enough response, I'll start looking into how to place a bug report on this.
Thanks.
Did you wipe/factory reset? You should not be having issues like that if you did.I don't see any of that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Did you wipe/factory reset? You should not be having issues like that if you did.I don't see any of that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I wiped, factory reset, cleared caches, etc several times, as well as trying 3 different ROMS like I said.
The only way I could fix it was to clear data from Touchwiz Home. But the issue would still come back after a few hours.
So you are on JB, and are using "Alphabetical list" without issues??
Did you back up system and maybe restored the data wipe titanium by accident? If you have a clean install with nothing restored yet does it do this? If not install back all your apps one by one widget by widget to see what is causing this. Could be an app compatible issue. I tried to replicate your issue and could not at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Did you back up system and maybe restored the data wipe titanium by accident? If you have a clean install with nothing restored yet does it do this? If not install back all your apps one by one widget by widget to see what is causing this. Could be an app compatible issue. I tried to replicate your issue and could not at all.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Essentially a clean install, nothing installed or restored with titanium, and the issue was there. I think the only apps I had installed were Chrome browser, Go SMS (or Handcent, I tried them both because I thought maybe one of them was causing the issue), and Facebook. Other than that, I was on a stock rom (rooted).
I was just able to re-create the issue by doing the following:
1) Switch app list view type to "Alphabetical list".
2) Go to task manager, do a "Clear memory"
3) Go to homescreen, grab an icon, as if to remove it from home screen, and let it go.
Touchwiz force closes (Unfortunately, TouchWiz Home has stopped). As soon as I set it back to "Alpahbetical grid", everything works as it should.
Note: I do have a folder in the shortcut area on the homescreen (bottom, next to the Apps button), not sure if this makes a difference, but it usually starts when a folder is created...
I was able to recreate this problem on 2 Telus devices, and 1 stock Rogers device, all running JB.
Followed that and I still unable to recreate this. I also have a folder on mine in dock for email with Gmail and email in it. I am at&t though. Even though I am not sure if it matters.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crystalstylez said:
Followed that and I still unable to recreate this. I am at&t though. Even though I am not sure if it matters.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm, interesting. I was thinking of perhaps trying an AT&T based ROM (all I've tried were Telus based, and was able to recreate the bug on a friends Rogers device as well...). Maybe it's Canadian devices only? I did notice that it doesn't seem to be a very widespread issue. Although there was a thread about it, there were very few responses...
I'll see about flashing an AT&T ROM, but for the moment, its working properly in grid view, so I'm good with that.
Thanks for the input though!
I'm not able to reproduce this issue on my SGH-I747M (Rogers) running stock (not rooted) Android 4.1.1.
If you factory reset/wipe data on the stock ROM, configure the phone without installing any third-party apps from the Play Store (heck, don't even bother signing in with a Google account initially for this one), then set the app drawer to alphabetical list and attempt to reproduce the issue as per your earlier steps does it still occur? Just curious.
kmcckenn said:
I'm not able to reproduce this issue on my SGH-I747M (Rogers) running stock (not rooted) Android 4.1.1.
If you factory reset/wipe data on the stock ROM, configure the phone without installing any third-party apps from the Play Store (heck, don't even bother signing in with a Google account initially for this one), then set the app drawer to alphabetical list and attempt to reproduce the issue as per your earlier steps does it still occur? Just curious.
Click to expand...
Click to collapse
Thanks for trying it out.
I was actually able to reproduce it on my friends stock Rogers 4.1.1 OS.
I was able to reproduce it with a minimal install of third-party apps (mentioned in another post, I think I had Chrome, Go SMS and Facebook installed...).
Perhaps I'll give it a try if I flash a new ROM anytime soon. Right now, my device is working well, and I only figured out it was the List option causing me the problem after installing a bunch of apps and customizing. Don't feel like resetting right now just to try to reproduce it, lol.
Tested on Rogers Stock 4.1.1 root injected, no issues at all here.
Sent from my SGH-I747M using xda premium
jb 4.1
i tried to get this to happen on my gs3 but so far i have no complaints .i was running aokp for last 6 months or so and yesterday decided to go back to stock att jb 4.1 and must say i forgot how smooth tw is. i love aokp and tho i never really had any issues running tasks rom and now that he released 4.2 is fantastic!! but im likeing this new update from att its just nice to have everthing working perfect with awseome battery life charged my phone last night to full then unpluged and went to sleep . pleased to say that phone this morning 6 hrs later is still at 100 %..what i did to install was first i wiped phone completely formated everthing and then used odin to flash root66 rom insatlled booted up intsalled cmw and then just fixed parmisions. today is second day so far not one issue at all to report .. gunna hang with this for a bit let the bugs get fixed in 4.2
Also not able to reproduce this on blackjelly v1.02 (based on 4.1.1 ota).
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Please help. Frozen clock and can't send text messages

My sprint gnex is rooted and I am running JBSourcery4.5. About a week ago I noticed that the clock across the top of the screen stopped and not being able to send or receive text messages when this happens. Hard and soft resets help but only for a short period of time. I thought that it might be the rom so I switched to PARANOIDANDROID 3.0 and had the same problem. I've searched all around for a solution and I saw something about turning off my wifi and that's seems to correct the problem but I'd much rather us wifi if it's available. Please help
Are those two roms using the same kernel? Also, did you wipe caches? Maybe try a superwipe..
Thank you so much! I changed my kernel and it's been working great ever since!!!!
Sent from my Galaxy Nexus using xda app-developers app

[Q] Cyanogenmod Texting Issues

I recently upgraded to Cyanogenmod from the vanilla android of my Sprint S3. I've had no issues with it since I've gotten it running until suddenly today it refuses to send text messages. It receives them just fine but for some reason refuses to send? I found another thread on this but it just confused me more and seemed to be talking about non CDMA phone (an Italian Evo 3d) and it doesn't make sense for my issue... yet it seems to be the same.(Reference)
Synopsis:
1. I could send and receive fine for an entire week til today.
2. I can still receive texts but cannot send them.
3. Sometimes it will send a single text through? That could just be a fluke.
4. Turning it off and back on didn't help.
Thanks!
Update: The error code associated with it is Error 34. No clue what that means, Googling has shown poor results.
Wrong forum, this is for the AT&T upcoming Galaxy S4
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
Wrong forum, this is for the AT&T upcoming Galaxy S4
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, realized that. My bad. No clue how to delete.
crowbahr said:
Yeah, realized that. My bad. No clue how to delete.
Click to expand...
Click to collapse
Maybe PM a moderator to get it moved.
crowbahr said:
I recently upgraded to Cyanogenmod from the vanilla android of my Sprint S3. I've had no issues with it since I've gotten it running until suddenly today it refuses to send text messages. It receives them just fine but for some reason refuses to send? I found another thread on this but it just confused me more and seemed to be talking about non CDMA phone (an Italian Evo 3d) and it doesn't make sense for my issue... yet it seems to be the same.(Reference)
Synopsis:
1. I could send and receive fine for an entire week til today.
2. I can still receive texts but cannot send them.
3. Sometimes it will send a single text through? That could just be a fluke.
4. Turning it off and back on didn't help.
Thanks!
Click to expand...
Click to collapse
Try fixing permissions in your recovery
Q: Did you dirty flash over?
Sent from my SPH-L710 using xda premium

Categories

Resources