-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Problem with dropped data connection after CM6 root (GBD)
- Thread starter i2004tor
- Start date
vikingisson
Android Expert
^ 3.22.26.17
^ 3.22.26.17
3.22.26.17 seems to be a source of problems for many. (In particular I think its related to areas w/multiple towers.) I know you swear by it vikingsson, but its utter crap. and has been since rogers forced it onto my fiancee's dream.
vikingisson
Android Expert
what can I say, CM6 (actually a variant) ran without any problems with that radio and I'll never sign the waiver. But now I want to use the newest radio and have gone back to 2.1, works even better (faster network) with no drops or cutoffs.
Out of curiosity, where abouts are you located? Rumor's I've heard are that the issue is known to exist by Rogers in their post-E911 HTC Dream's(the kicker here is that it can interfere with making 911 calls), and only occurs in areas with multiple towers. Basically a tower will try to hand your phone off to another, and the phone doesn't catch the request to change over, and keeps sending data to the old tower, which is no longer listening.
I'm also running a varient of the rogers 2.1 for the last few weeks, no problems w/the new radio, but my fiancee's dream(CM6, 3.22.26.17) still gets buggered up around 5-10 times a day.
vikingisson
Android Expert
@thor, I'm in Mississauga On. I have a tower on either side of my home and sit in the weak zone of both so depending on which side of the house I go it will swap between the two which is a good thing because neither are very strong and I'd surely drop off if handover didn't work. Doing speed tests I can tell that one is HSPA and the other is plain ole 3G. I even did a tethering test last night and was impressed with the speed from the laptop, I could forget that I was on tether. The newest radio seems like an improvement to me.
I'm running a Magic, not a Dream. If this problem is causing issues with 911 then that's really ironic.
I'm running a Magic, not a Dream. If this problem is causing issues with 911 then that's really ironic.
cezegg
Newbie
^ 3.22.26.17
no, 3.22.20.17... haha
i went from 3.22.26.17 to 3.22.20.17, and now i'm back at 3.22.26.17... waiting for my data to come back, i don't know how to get a network refresh. haha
vikingisson
Android Expert
just call them and say you lost data and need a network refresh. but for sure you want 3.22.26.17 if you hope to keep your data. so, no, 3.22.26.17
I've run that radio on both my Magic and her Dream, as soon as that radio touches either phone they drop their connections. Switch to the pre-E911 radio and no problems (other than rogers disconnecting me).
I've used both all three radios for tethering, and they all work out about the same in speed tests(w/in 250kbps).
Did you have any problems on 3.22.20.17?
just call them and say you lost data and need a network refresh. but for sure you want 3.22.26.17 if you hope to keep your data. so, no, 3.22.26.17
How do you do this? I've called twice now, both times I asked for a network refresh and both times they rambled on about how they couldn't and that they're waiting for a specialist to look at it. I repeatedly asked them and they refused
cezegg
Newbie
nothing substantial... my sms messages weren't sending, but i think that's a problem with the cm rom i have on (cm6 stable)... it only sends sms messages when my wifi is off. haha.
odd...
vikingisson
Android Expert
How do you do this? I've called twice now, both times I asked for a network refresh and both times they rambled on about how they couldn't and that they're waiting for a specialist to look at it. I repeatedly asked them and they refused
I don't know other than I called, told them my problem, and quickly told them what has to be done (refresh). Once while waiting too long in the queue I jumped over to the iPhone support and got it done there. Of course the iPhone support guy said I was in the wrong place but he could do the reset as easily as anyone. I had to do it several times.
Since paying attention to my radio version I haven't lost data.
I finally decided to bite the bullet and try this because of all the dropouts I was having with the dream radio and I am not willing to sign the waiver. So I tried it and as you said it was a piece of cake using Radioswitcher. I too found the stock 2.1 to be very snappy and I do like it so far. I will test the 6.35 radio over the next days and report my findings. Thanks for advising about RadioSwitcher. As well, I will miss some of the neat features of CM6.
I have been running the rooted 2.1 for a week now with no data dropouts at all and both the rom and the radio feel much snappier. Previously the dream radio would cause dropouts during calls. I guess I will stay with this until perhaps CM comes up with a rom that uses the 6.35 radio. I also like the fact that there is an HTC Flash program that runs flash and that I can view wmv, whereas this was not possible with CM even under 2.2. So far so good.
I've had similar experience with 3.22.26.17 radio on CM6. Data drops randomly during the day. Switched to 3.22.20.17. Better reliability, performance, speeds, etc. The only problem is because it's pre 911 fix radio, I lost my data after couple of days. Went to Rogers website to sign the waiver. Entered everything correctly into the form (triple-checked), clicked sumbit and it told me that my IMEI number is invalid. Called Rogers to inform them about problem with broken waiver form. CSR said that he escalated that issue and someone will call me during next 24-48 hours after it's resolved and did network refresh(restored my data). Obviously nobody called me back and I lost my data again. So I called Rogers again and this time they told me that escalation process isn't complete and usually takes from 5 to 7 business days and all they can right now is do another network refresh for me.
So at this time I can't really sign that stupid waiver even if I want to. Rogers is completely useless in my case. All I want them to provide me with reliable data service I pay money for. So I said: "Screw this" and flashed new radio and rooted 2.1 Rogers ROM from xda-developers. But there is no excuse for Rogers for not letting me to use fully functional 2.2 ROM on my Magic because they are so cheap to pay HTC for releasing 2.2 update and being so ignorant to it's customers. I would think twice now before renewing my contract with them in near future.
So at this time I can't really sign that stupid waiver even if I want to. Rogers is completely useless in my case. All I want them to provide me with reliable data service I pay money for. So I said: "Screw this" and flashed new radio and rooted 2.1 Rogers ROM from xda-developers. But there is no excuse for Rogers for not letting me to use fully functional 2.2 ROM on my Magic because they are so cheap to pay HTC for releasing 2.2 update and being so ignorant to it's customers. I would think twice now before renewing my contract with them in near future.
Was using the rooted Rogers 2.1 variant mentionned earlier in this thread and was getting nothing but problems. Sense was restarting on me frequently, and at 6 AM this morning the phone rebooted. Got the nice HTC startup sound and an elbow in the ribs from my wife...
So first order of buisness, time to switch BACK to CM6. I used the radio switcher app also mentionned earlier here, and noticed that the radio version this comes with is the 3.22.20.17, which is the pre-E911 radio and subject to data disconnection from Rogers. Also tried the Rogers waiver which did not work for me either. Tells me the IMEI number is bad but that's what the sticker and info screen report!
Found and loaded the 3.22.26.17 radio and that worked, but I know there are issues with this one also. Namely the regular data drops requiring an airplane mode toggle to re-connect to the network. This was the reason for switching back to the stock 2.1 to begin with!
So in searching around I also found a 3.22.23.18 radio that I flashed and it's working fine so far. Haven't been running it long enough to tell if I'll get the intermittent data loss or flat out disconnected by Rogers yet though...
Kind of thinking that Rogers is looking for the 3.22.20.17 radio specifically for the disconnect, so gambling that this will get me out of the woods. Does anyone else have experience with this radio?
I'll post back in a few if things stay stable, as of right now though voice and data are working just fine as long as I have signal. Kind of weak here, but that's normal...
So first order of buisness, time to switch BACK to CM6. I used the radio switcher app also mentionned earlier here, and noticed that the radio version this comes with is the 3.22.20.17, which is the pre-E911 radio and subject to data disconnection from Rogers. Also tried the Rogers waiver which did not work for me either. Tells me the IMEI number is bad but that's what the sticker and info screen report!
Found and loaded the 3.22.26.17 radio and that worked, but I know there are issues with this one also. Namely the regular data drops requiring an airplane mode toggle to re-connect to the network. This was the reason for switching back to the stock 2.1 to begin with!
So in searching around I also found a 3.22.23.18 radio that I flashed and it's working fine so far. Haven't been running it long enough to tell if I'll get the intermittent data loss or flat out disconnected by Rogers yet though...
Kind of thinking that Rogers is looking for the 3.22.20.17 radio specifically for the disconnect, so gambling that this will get me out of the woods. Does anyone else have experience with this radio?
I'll post back in a few if things stay stable, as of right now though voice and data are working just fine as long as I have signal. Kind of weak here, but that's normal...
I just loaded this radio(3.22.23.18) on to my HTC Dream w/CM6. I had been using 3.22.20.17, as I had the random network disconnection problems described in this thread while using 3.22.26.17 radio. So far so good, CM6.0.0 booted w/no complaints after changing the radio via flashboot.
Because Ive been using the 3.22.20.17 radio the phones data keeps getting cut by rogers. I tried to sign their stupid waiver, but it kept coming back with the invalid serial number error. Called their tech support to have them fix their list of serial numbers, told them which phone number it was and which imei number it was(I have a Dream and a Magic on the account), had them open a tech ticket. I was told that I would be contacted some time in the next TWO WEEKS! In the last week and a half I've had my 3G cut by them twice, had to wait on hold 30+ minutes each time to get them to do a refresh(which they were happy to do as I had an open tech ticket). The dimwit on the second call in hung up on me, but did the refresh. typical of rogers.
Last night I finally was "contacted" by rogers: A text was sent to my MAGIC (remember, its the Dream I want to sign the waiver for), saying that an correction had be made and I could sign the waiver. Went to sign the waiver for my Dream... and surprise surprise, still wouldn't work. I'm assuming they screwed up and corrected their list to include my Magic, not my Dream. *sigh*
Hi
I just wanted to post that my Magic continues to run flawlessly on the rooted 2.1 now for about 2 weeks. I have not experienced the problems that spyke555 has, I guess different phones must react differently. Also, I have indeed noticed that battery life appears much improved with the new radio.
I will report periodically. Finally though I still would wish CM to come out with a 6.35 radio option.
I'm sure it probably has something to do with the apps I run. In particular there is one app called Ambient Light Sensor which technically should NOT work with Sense IU ROMs but just happens to work on the rooted Rogers 2.1... Maybe not as well as I thought... ;-)
This app's great for pumping up the backlight when outside automatically, and droping it down when inside / at night to save battery. One of the main reasons I jumped to CM in the first place. Was kind of hoping HTC skipped Sense UI on this build, wishful thinking I guess...
Oh and there is a ROM that ports CM to the 6.35 radio, camera is a bit flakey though:
[Rom][32A][6.35] CM-6.1.0 - FroyoRider v2.0 - Cam OK w/ToyCam (19-Sept-2010) - xda-developers
Data is still on... Did have to do two airplane mode toggles yesterday, but may have been signal issues and me being impatient though.
Can you disable senseUI? Are you happy with Ambient Light Sensor. Seems to be a useful app. Thanks.
Really like ALS, yes...
As for Sense UI I was able to install ADW.Launcher instead and switch the default home screen to that no problem and it did help with the stability.
The Sense UI lock screen can also be removed but then there must be settings somewhere that are messed up. The sliders end up at the top and bottom of the screen, slide up and down, and the text is all in the wrong places.
Even if you get that done there is the clock app that's integrated into the Sense UI lock screen. Your alarm will go off, but it expects the lock screen to be there to turn off... So it's a yank the battery affair to turn the alarm off, talk about a rude awakening!!! That is of course unless you also replace the clock app with the vanilla one. Not quite as simple but I was able to find a script to do that, but required root access...
I think that's where my issue came in. The second time I tried this I only replaced sense ui with ADW.Launcher and left the rest as is. Then at 6AM the phone rebooted on it's own. Had an alarm set for that day and time but it was disabled. So something went wrong...
So is it possible, absolutely! You'll need to do some fidling to get it stable though. An in the end, Sense UI is still there, just not front and center...
As for Sense UI I was able to install ADW.Launcher instead and switch the default home screen to that no problem and it did help with the stability.
The Sense UI lock screen can also be removed but then there must be settings somewhere that are messed up. The sliders end up at the top and bottom of the screen, slide up and down, and the text is all in the wrong places.
Even if you get that done there is the clock app that's integrated into the Sense UI lock screen. Your alarm will go off, but it expects the lock screen to be there to turn off... So it's a yank the battery affair to turn the alarm off, talk about a rude awakening!!! That is of course unless you also replace the clock app with the vanilla one. Not quite as simple but I was able to find a script to do that, but required root access...
I think that's where my issue came in. The second time I tried this I only replaced sense ui with ADW.Launcher and left the rest as is. Then at 6AM the phone rebooted on it's own. Had an alarm set for that day and time but it was disabled. So something went wrong...
So is it possible, absolutely! You'll need to do some fidling to get it stable though. An in the end, Sense UI is still there, just not front and center...
Here's the page with the scripts I mentionned:
Fix: Working Vanilla Lockscreen + Alarm for 2.1
Note that although these are supposed to also fix the lock screen issues they in fact don't. They do however get rid of the HTC clock and install the default Android one for you...
Fix: Working Vanilla Lockscreen + Alarm for 2.1
Note that although these are supposed to also fix the lock screen issues they in fact don't. They do however get rid of the HTC clock and install the default Android one for you...