Hi guys. I'm having a real hard time with my phone right now and I hope someone can help me.
First of all, my Note is still on ICS running the last stable build of CM9 (CM 9.1.0 to be exact) without any other kernel or radio modifications. I just performed a clean install of this the other day also. The problem I'm having is that the phone will literally be sitting next to me connected to my home wi-fi and it will fail to receive texts and phone calls. What I mean by that is, my girlfriend will be trying to text me but nothing will come through on my phone for up to an hour. Then at some random time, all the so-called pending SMS will finally display on my phone all with the same time-stamp. Similarly, if someone tries to call me, I will have no notification of this until way after the fact when the voicemail symbol appears (that's IF a message was left).
Now, to me, this seams to be happening at completely random times and I have not been able to pinpoint what's causing it. Before, I used to think it happened after a prolonged time of having the phone on silent and non-use. But just last night the problem happened again when this was not a factor.
A few other notes:
Only seems to happen at home where I am connected to wi-fi. And frankly, I don't travel enough to test my phone anywhere else. While at home my signal strength on AT&T fluctuated between 0-1 bar up to 3 bars. Kinda strange, I know.
Before switching to the CM 9.1.0 rom, I was using CM9-Kang h0tsauce "9" 20120817 *reborn* for quite some time. I experienced the problem with that rom as well but it didn't seem to happen as much.
Rebooting the phone seems to help. When I do this, it seems to push everything through and allows me to be able to receive new messages instantly. Obviously, though, this is not a good work-around since I have no idea when the problem will show up.
So.... anyone know what's going on here? Hardware/software/network problem? I've done some searching but couldn't really find this issue discussed anywhere else. Any help is greatly appreciated.
kevindena said:
Hi guys. I'm having a real hard time with my phone right now and I hope someone can help me.
First of all, my Note is still on ICS running the last stable build of CM9 (CM 9.1.0 to be exact) without any other kernel or radio modifications. I just performed a clean install of this the other day also. The problem I'm having is that the phone will literally be sitting next to me connected to my home wi-fi and it will fail to receive texts and phone calls. What I mean by that is, my girlfriend will be trying to text me but nothing will come through on my phone for up to an hour. Then at some random time, all the so-called pending SMS will finally display on my phone all with the same time-stamp. Similarly, if someone tries to call me, I will have no notification of this until way after the fact when the voicemail symbol appears (that's IF a message was left).
Now, to me, this seams to be happening at completely random times and I have not been able to pinpoint what's causing it. Before, I used to think it happened after a prolonged time of having the phone on silent and non-use. But just last night the problem happened again when this was not a factor.
A few other notes:
Only seems to happen at home where I am connected to wi-fi. And frankly, I don't travel enough to test my phone anywhere else. While at home my signal strength on AT&T fluctuated between 0-1 bar up to 3 bars. Kinda strange, I know.
Before switching to the CM 9.1.0 rom, I was using CM9-Kang h0tsauce "9" 20120817 *reborn* for quite some time. I experienced the problem with that rom as well but it didn't seem to happen as much.
Rebooting the phone seems to help. When I do this, it seems to push everything through and allows me to be able to receive new messages instantly. Obviously, though, this is not a good work-around since I have no idea when the problem will show up.
So.... anyone know what's going on here? Hardware/software/network problem? I've done some searching but couldn't really find this issue discussed anywhere else. Any help is greatly appreciated.
Click to expand...
Click to collapse
I have been having the same problems as you on a Blackstar X and Flapjaxxx's ICS build 12. I talked to AT&T a couple of times and they reconnected me to the network which has helped a little, but I still get missed texts and calls, but not as often. I have no idea how to fix the issue. Hopefully, somebody out there does.
Sounds like to me that you have a very bad signal. In case you didn't know, texts go through the phone signal and not wifi. The wifi connection is just a coincidence since you never leave home and are always connected to wifi. Going somewhere with a better signal would help clarify this.
There are apps on Google Play that restore your network when it goes down. Possibly they may help you.
Agoattamer said:
Sounds like to me that you have a very bad signal. In case you didn't know, texts go through the phone signal and not wifi. The wifi connection is just a coincidence since you never leave home and are always connected to wifi. Going somewhere with a better signal would help clarify this.
There are apps on Google Play that restore your network when it goes down. Possibly they may help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will try one of these apps that restores the network. Fingers crossed!
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
gregsarg said:
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
Click to expand...
Click to collapse
Thank you, thank you, thank you!! I will test this as well.
gregsarg said:
Also ..
AOSP ICS builds are known to fail phone operation...
Not always, and not on every device.
I pulled CM9 yesterday for this very reason...
And it appears you are having the issue as Well...
Revert to a non AOSP build to test..
Mine is working fine now on UCLF6 ICS .......g
Click to expand...
Click to collapse
I started having this issue with my One X. Git a replacement and had the same issue. Now on my note I have the same issue. It's only at home though and I'm on wifi. Started on BlackStar X now I'm on FJ AOSPxxx JB. Seems to happen more. Think I might go back to BlackStar. Didn't happen as much
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Also ..if going back to blackstar ...
The older version is UCLF6 ...And the newer version comes from the N7005 device base .....
Not that it makes much difference, but the older version will likely give you the same results as FJ's UCLF6 builds.....
You may want to try the newer version first ...g
Edit: the older builds allow the use of FJ's 3.0.2 kernels....the newer base will not.
Related
I have been discouraged from the Froyo ROMs for a while due to the problem with calls being dropped but then suddenly they aren't dropped. I really like the Froyo ROMs though so I decided to try it again and the first day I experienced it yet again on CELB 3.6. It only happened a couple of times then 3.7 was released and I flashed that and it happened again on the first call LOL. I then started looking through things in the settings and under the mobile data setting I turned on National Data Roaming, since then I have been on several calls ranging from 20 minutes to an hour and have yet to experience this problem since turning data roaming on, some of these calls were in areas that I know for certain I had the dropped and reconnected calls happen before. Maybe some others may want to try this out and see if it helps you as well. Hope this helps some people that have experienced this as well.
Has anyone else tried this yet? And if so, has it made any difference for you as well?
happens to me all the time. kaos froyo, tazz froyo, celb froyo, nonsensikal froyo. Only at my house tho. i have 3 bars there. not sure whats going on there but i have learned to live with it. Wont be long till we are on 2.3 anyway. deal with it for a month. by the new year kaos should have a completley functional 2.3 rom. maybe without camera, but still fully functional.
I've been messing around with the national data roaming for about a week now. When I have national data roaming enabled it doesn't happen, if I turn it of it does. Try enabling it and see if it makes a difference for you too. It's located under settings>wireless & networks>mobile networks
will enable it and see if it happens tonight.
Same here, after enabling it I have had no stopped call issues. Its been about a week, so far so good
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Scott586 said:
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Click to expand...
Click to collapse
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
CondemnedSoul said:
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
Click to expand...
Click to collapse
I also have this problem happen on non-Verizon based ROMs such as RCMix.
The call says it's dropped, but the person on the other end can hear everything that's going on.
Then the phone rings you back, but in reality, they were hearing everything going on around you in the meantime.
I almost lost my girlfriend because of it. Immediately flashed away from said ROM. Had the same problem with Froyo ROMs.
May switch to a CM ROM now, if this is a serious fix. Thanks very much for this.
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
bftb0 said:
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
Click to expand...
Click to collapse
Sorry ut didn't work for you.... so far now im at 3 weeks without it happening to me
I have still had this temporary dropped call problem occur just as frequently on CELBFroyo 3.6 with this "fix". And most of the time I'm in my apartment on the phone for hours when it happens, and it sometimes happens more than once during these extended phone calls.
Just as has been described before: the phone looks and acts like the call was dropped, I can hear nothing but the other person can hear everything, and then after several seconds everything is back to normal.
Oh well. Thanks for the suggestion, though.
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
farmdoc said:
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
Click to expand...
Click to collapse
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
CondemnedSoul said:
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
Click to expand...
Click to collapse
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
bftb0 said:
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
Click to expand...
Click to collapse
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
farmdoc said:
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
Click to expand...
Click to collapse
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
roirraW "edor" ehT said:
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
Click to expand...
Click to collapse
Thanks! BTW what is AFAIK?
farmdoc said:
Thanks! BTW what is AFAIK?
Click to expand...
Click to collapse
You're welcome! AFAIK = As Far As I Know
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
Hello gentlemen!
First of all, I want to thank neobuddy and everyone that he worked with on the ICS Passion ROM. I find it excellent and have been using it for the past week or so.
I do have a slight issue, though, and as I am not yet familiar with mobile development, I am not sure if the problem stems from my hardware or the software. I bought this Vibrant used, though in excellent condition. As soon as it arrived, I rooted it and installed ICS Passion on it. Therefore, I never actually used the stock software, and that is why I am unsure if this issue stems from the ROM or from the phone itself.
Anyway, my problem is that sometimes during a call, my voice will cut in and out very frequently. This occurs with various people and in various places, so it doesn't have anything to do with signal strength. I can hear the other person just fine. It also seems to only occur when I receive a call. Once I hang up and call the person back, they seem to be able to hear me just fine.
I suspect that this has something to do with one of the following:
1) Sound filtering and normalization. The way that the software handles the data that it receives from the microphone. If it was the microphone itself, I would expect this issue to be much more consistent.
2) Which network the phone uses during phone calls. I've gathered that H is for data transfer and 3G is for phone calls (for the most part). Is it possible that ICS Passion somehow fails to switch to the proper network when a call is received? This seems unlikely as I searched through the ICS Passion thread in the dev forum, but couldn't find an issue similar to mine.
Any insight would be appreciated, although I suppose if no one can help out I can just flash the stock and see if the problem persists. If it does, then I can only assume it's the phone.
Thanks!
try v 10 or v 10.6
Mute and then unmute your call. We've had this problem since cm7
Sent from my SGH-T959 using XDA App
bfranklin1986 said:
Mute and then unmute your call. We've had this problem since cm7
Click to expand...
Click to collapse
Sweet, good to know, thanks. Do you know of a more permanent solution?
LDKnight said:
try v 10 or v 10.6
Click to expand...
Click to collapse
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
ProfessorKazuki said:
Sweet, good to know, thanks. Do you know of a more permanent solution?
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Click to expand...
Click to collapse
Been on v10 for a week and have not had the reboot problem. I've heard 10.6 has some problems but yeah the mute/unmute bug isn't that bad you get used to it
Sent from my SGH-T959 using XDA App
kenrb said:
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
Click to expand...
Click to collapse
That's what it seems like. I have not had a single "you sound like you're underwater" issue for outgoing calls.
Thanks for the responses, everyone. I'm glad to find out that the problem isn't with the phone because I can't afford to replace it for a while. I guess I'll just wait a bit and hope that these slight issues get resolved in a more stable iteration.
UPDATE: Thank you guys so much for the help! My phone is running well so far! The GPS works well enough for navigation, and I should hopefully be able to limp through until my full upgrade. I can't tell you guys how thankful I am that you all took the time to help me answer my questions and get my phone going again!
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Personally I'd Odin back to stock JFD and either do a reflash or pick a new ROM (bionix comes to mind).
Could do a fresh install of the apps you want on your phone. Your battery could be going bad and may need to be replaced, and if your sim card is getting old, you may need to stop by T-Mobile and have them replace it.
Not sure if that could be the trouble with your notifications or voicemail, but they are all quick things to try that should be cheap and quite possibly very effective.
The_MamaBee said:
what would you do? I have a Vibrant, and have done quite a lot of troubleshooting with it. Tmo's tech support said it's a hardware issue and that they've done all they can.
I've tried just about all the Froyo ROMs on it, and things seem to work well for a while, then it gets odd. I regularly clear my call logs, messages, and browser cache. I use wifi whenever I'm at home, and whenever I'm in the minivan I have my phone plugged in.
I am currently running Axura - Moped/FishmanMod v1. This has seemed to work the longest.
Lately, though, I've been missing phone calls...as in, no notification, no log, nada. I rebooted last week and suddenly had a voicemail icon...I had 7 new voicemails. One from my son's teacher. I never knew she even called. I've since reinstalled Tmo Visual Voicemail and at least now I think I'm getting my voicemails. Missing phone calls can't happen though. We don't have a landline, and we have a child with health issues. I have to be available.
Other issues:
*My battery died about halfway through the day yesterday, even though it had charged fully overnight.
*This thing is slowing down. As in, taking a photo with my phone isn't really viable. By the time it finally snaps the picture, my kiddo has grown an inch.
*Lag! I'm using Swiftkey X and it often hangs on a key for several seconds before finally typing it. It's very slow to open apps, etc as well.
Does anyone have any more advice for me? I'd love to run an ICS or JB ROM, but having the ability to call 911 is not negotiable for me. Woodrube and some others have given me some great advice, which has helped, but I'm still having some issues.
I could pare down the apps and use it just as a phone, but what would be the point of having an Android...and data? I need the calendar, email, task list, etc. to keep track of everyone.
I'd love to try to figure out how to make this phone last longer. I could upgrade now, but our checkbook doesn't like the idea.
Click to expand...
Click to collapse
Well, although it isn't too helpful to say...I honestly believe that if you simply must be available because you have a child with health issues, you definitely should not be tinkering with your device. True, my phone runs better, faster, stronger, and longer (ha daft punk) than it did running stock, but I have certainly had the occasional issue such as data issues, force closes, battery drains, SODs, etc, etc...it's simply a fundamental part of the life of modifying your phone. It's not to say that you won't have issues if you kept it stock, but you really shouldn't be messing with your phone if you don't have a land line and you NEED to be available for something so important.
Now, onward!
I will look into similar occurrences of your problems and report back..(sorry in class atm, then off to a meeting). Until then, Gl!
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
blizzardproof said:
you could try and use a cyanogenmod based Rom. They are one of the best roms out there except you can't as of right now call 911 (some phones can and some cant ) also gps is semi-broken.
Click to expand...
Click to collapse
Thanks for the advice, but not an option. I have to have 911 capability, and we're pretty active geocachers, so my GPS gets used a ton. I've been so tempted by CM Roms, and my husband is rocking one on his One S, but going without 911 isn't an option.
After this last round of my phone's slowness, we did ODIN back to stock, then did the ((*^&^%$*&^) updating it to Froyo. (Yay!) We were hoping that taking it back to stock would help our issues, but it actually seemed slower. (And oh, the agony of using TouchWiz!) I very, very carefully added back ONLY the apps I used on a daily basis, watching carefully to see if there were any issues. It was crazy slow.
We then went to this last ROM and I added back apps even more slowly. I noticed that I had issues after I put the Zedge app back on, so it's gone. I also noticed that it acted funky after I put Google Goggles on, so it's gone as well.
I am not, by the way, storing any music on my device. I stream it through Google Music.
I do have another battery for it. I'll put Battery Calibration on and swap batteries to see if that helps. Good idea.
Also, my SIM is pretty old. I hadn't thought about seeing if I could get a new one! I know it solved some issue LONG ago with my BlackBerry. I'll see if I can do that at our TMo store today. Appreciate that suggestion.
I've been just about the give up on this phone altogether and just going with the One S like The Hubs, but forking over the money for it (not to mention that it would be $200 for me and $49.99 for a new contract!) is just not in the budget now. Might be getting close to something we just can't avoid though.
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when restoring apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Try flashing back to stock 2.1 with repartition checked. Then flash one of Fishman/Moped 2.2 ROMS ( he has odin files if you prefer that method). I think you may still have some "ghosts" left behind from the last ROM or two you had on your phone. A fresh odin to stock with repartition checked should get rid of any "ghosts". Also when resorting apps make sure you restore app only, not app+data. Remember, after installing a ROM allow your phone to sit for a good 10 minutes then reboot before you use the phone.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
That could definitely be it. I used to just restore all my apps+data with My Backup Root. I'll see if I can convince The Hubs to help me work on the phone this weekend. I'll let you know how it goes. Thanks!
Okay, we did the repartition flash, then put it on FishmanMod Blue 2.2 Frankenstein Slim. Seems to be running a little better, but now my GPS won't lock at all. I've rebooted, tried Samsung GPS Restore (never locks) and GPS Test. Test sees 4-5 satellites but doesn't ever lock on. I've tried Nav as well and it is not able to lock on.
I've checked our forums and I see a lot of fixes, but no recent fixes and most of them are for 2.1. I've tried dialing the *#*# numbers, but they don't do anything.
I sure could use some suggestions. I'd like to be able to use my GPS. I know it's generally an issue with Vibrants, but mine has never failed to lock on before. Might be slow, might take it until the end of the block, but it always locks. Until now...
Thanks in advance!
Go to the Dev section and look for a thread called GPS Fixes by Solisfiend. It'll be buried way back and I'm mobile so I can't link it. It has directions and app to fix Froyo GPS.
I have 2 posts in there, 1 is clarification of some things and the other is a download app you can use. Should work well for you.
Thank you, Woodrube. I'll do just that.
ETA: Found the link.
http://forum.xda-developers.com/showthread.php?t=1393991&highlight=gps+fixes
Sent from my SGH-T959 using xda app-developers app
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.