Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
alphax_0 said:
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
Click to expand...
Click to collapse
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
droidstyle said:
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
Click to expand...
Click to collapse
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
I see. It's just sometimes my 3g/wifi will be colored and still won't be receiving signal every so often even when I disable the other data method. Oh well
sendan said:
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
Click to expand...
Click to collapse
same here...but quite a few report the same issue as op. I seen a post where chopper said to only leave one on or the other. just passing the info along.
Hmmm, it may have to do with the radio. I've seen a few people mention that the handoff is better with the eh03 radio; coincidentally that's what I've been using since I came back to MTD.
Sent from my SCH-I500 using xda premium
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.
Back when I was using Nonsensikal Froyo 5.1 I was able to do a Bluetooth PAN connection with the Wireless Tether app and everything was peachy. However, starting with the builds based on CM6.1, I get a kernel panic when I connect, and my phone reboots. The phone pairs fine, and I can transfer files to / from the computer without a problem. The panic happens while my computer says it's acquiring an IP address.
This has happened to me on Nonsensikal 10, Nonsensikal 16.1, GSB 2.5, and is still happening on GSB 3.1.
There is a bug for this exact issue, but it claims to have been fixed a year ago. I haven't had any luck convincing them to reopen it. http://code.google.com/p/cyanogenmod/issues/detail?id=573.
I'd REALLY like to get this sorted out, because bluetooth is definitely the best tethering method for the Eris. Since I'm out in the boonies and it's using a lot of wattage to communicate with the tower, both the USB (charging) and the Wifi tethering methods cause the phone to overheat and drop from 3G to 1X. Bummer.
Does anyone know how I can fix this?
jacksenechal said:
Back when I was using Nonsensikal Froyo 5.1 I was able to do a Bluetooth PAN connection with the Wireless Tether app and everything was peachy. However, starting with the builds based on CM6.1, I get a kernel panic when I connect, and my phone reboots. The phone pairs fine, and I can transfer files to / from the computer without a problem. The panic happens while my computer says it's acquiring an IP address.
This has happened to me on Nonsensikal 10, Nonsensikal 16.1, GSB 2.5, and is still happening on GSB 3.1.
There is a bug for this exact issue, but it claims to have been fixed a year ago. I haven't had any luck convincing them to reopen it. http://code.google.com/p/cyanogenmod/issues/detail?id=573.
I'd REALLY like to get this sorted out, because bluetooth is definitely the best tethering method for the Eris. Since I'm out in the boonies and it's using a lot of wattage to communicate with the tower, both the USB (charging) and the Wifi tethering methods cause the phone to overheat and drop from 3G to 1X. Bummer.
Does anyone know how I can fix this?
Click to expand...
Click to collapse
Perhaps it's a kernel issue with Conap's CFS kernel rather than something with Cyanogen? Nonsensikal was using Conap's CFS v4, based on my quick read of the dev history of the ROM.
I'm not sure that CFS V4 would work on GSB, but I suppose you could try flashing it and see if it changes anything? Or try flashing on a newer Nonsensikal and see what happens?
It looks like it's no longer on grdlock's site, but, if I did it right, here is a link to it: https://www.sugarsync.com/pf/D71034_157223_626779 (let me know if that doesn't work.)
My Eris on Cynogen 7.0.3 has the same issue, I tried to enable the PAN bluetooth and get a hang every time.
Good call!
doogald said:
Perhaps it's a kernel issue with Conap's CFS kernel rather than something with Cyanogen? Nonsensikal was using Conap's CFS v4, based on my quick read of the dev history of the ROM.
I'm not sure that CFS V4 would work on GSB, but I suppose you could try flashing it and see if it changes anything? Or try flashing on a newer Nonsensikal and see what happens?
It looks like it's no longer on grdlock's site, but, if I did it right, here is a link to it: https://www.sugarsync.com/pf/D71034_157223_626779 (let me know if that doesn't work.)
Click to expand...
Click to collapse
Wow... so I flashed that over GSB 3.1 and it seems to work so far. I'm posting this over the bluetooth PAN connection right now. I'll post back here in a few days with an update whether everything else still works. For now... looking good! Thanks!
Okay, this is potentially a really stupid question...but here goes.
I'd installed CM7.1 on my Fascinate as soon as I got it (was running a Vibrant with CM7) and immediately started seeing the weird issues like:
-data connection disappearing
-"double ring"...ringer ringing away during a call, requiring an end and re-dial to have a clean conversation
-call volume being ear-piercingly loud
As a result, I've started ROM hopping. However, the ROMs I've tried all seem to have the same issues.
Not trying to flame anyone, or bag on any of the ROM authors/maintainers, but are all the Fascinate ROMs out there a copy/modification of the CM ROM? Or are these issues I'm seeing (as others are too) a common failing of anything other than the stock ROM that came on the phone?
im running cm7.1 and have none of those issues.
What modem do you have? The ringing you are experiencing is called the phantom ring. I thought it was a known issue in all mtd roms, but I haven't used one in awhile. I remember having the call volume the same way. You have to press vol down once.
Sent from my SCH-I500 using XDA App
droidstyle said:
im running cm7.1 and have none of those issues.
Click to expand...
Click to collapse
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
uzumaki82 said:
What modem do you have?
Click to expand...
Click to collapse
I flashed Evil Fascinate over the weekend and I'm running DL09.
However, this doesn't answer the deeper question as to if the issues I saw in CM7.1 are pervasive in the other ROMs for this phone, as I've already experienced them in Evil, and it's been three days in use.
I'm not sure if I should simply accept the issues and find a ROM that I like, or if there's a different ROM out there that doesn't have the CM7.1 issues.
I am having the issues with the volume but, pressing volume up or down works to clear that up. I have also gotten complaints of the other end having an echo. This is on all calls with multiple carriers from other people. Anyone having this issue as well and know how it can be resolved? It doesn't echo on my end. Just the person I am talking too. Also I am running modem Baseband EDO5. I was running EBO1 and still have the same issues with each. I have tried MIUI as well and still the same. I flashed to stock fascinate as if you were to get it from Verizon and all of that seemed to go away. When I flashed back to CM 7.1 all of these issues arose again.
thedoman said:
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
my wifi never drops...sometimes I have to toggle it off/on after a reboot but thats it.
I have had that problem on all my android devices that I have had. Sometimes hardware just freezes up and you have to do a reboot. They are basically little computers anyway but, if you are constantly having to reboot to get something to work. It is more than likely a problem with the mod.
Hey everyone, I'm new to the site and fairly new to Android. Got a thunderbolt when it came out and rooted out a few months back. Currently running CM7 and have tried many bamf roms as well. Anyways, my question is about the wifi sleep setting. It's my understanding that wifi sleep being set to "never" means that when connected the wifi will stay on whether the phone is awake or not. That is not happening with my phone and it hasn't happened since I've had the phone that I can remember. Is this typical or an I missing something?
Sent from my rooted thunderbolt using Tapatalk
Must be a bug somewhere in CM. I'm using bamf forever 1.09 and my wifi never disables on sleep. Maybe a kernel issue also.
Sent from my ADR6400L using Tapatalk
bpyazel said:
Must be a bug somewhere in CM. I'm using bamf forever 1.09 and my wifi never disables on sleep. Maybe a kernel issue also.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks for the response!
I have tried multiple ROMs (including multiple BAMF ROMs) and I've had the same issue with all of them I believe. I think it was even happening while on stock actually. I wasn't paying much attention at to it at that point in time because I was new to Android and mesmerized by everything else I wasn't looking at that at all but I don't remember a time when I would wake my phone and it still be connected to Wifi.
Is there some sort of testing I can do to see what the issue is? I really like CM7 because my battery life is outstanding with it but I am open to flashing another ROM to see if that's the issue.
Anyone have any other ideas of what it might be/actions to try to determine the issue?
I flashed a new ROM yesterday (Infected Eternity) and it appears as though the wifi is maintaining connected while at rest. I'll keep an eye on it and update if anything changes. Looks like it must be something within CM7. Thanks for the heads up bpyazel!
On a side note, the new ROM seems to be pretty nice as well. Battery life has been acceptable (better than most of the other ROMs I've run, with the exception of CM7) and it also has a DarkHorse theme available which I am a fan of. I'll be sticking with this for a bit to see how much I like it.