Develop Bugs

[Q] HTC Desire freezes when switching from 3G to 2G

Hello out there,
since I wiped my phone and updated to the most recent CyanogenMod 7 build (#262), my problem regularly freezes when switching from 3G to 2G mode. The only thing to get the device running again is to remove the battery and reinsert it again. If i'm still in an area or room with only 2G coverage, the phone freezes soon after boot-up.
Help or advice would be greatly appreciated!
Thanks in advance,
toco
My phone:
HTC Desire (GSM)
PVT1 S-OFF
RADIO-5.17.05.23
CyanogenMod 7 20120225-NIGHTLY
Android ver. 2.3.7, kernel 2.6.37.6

What I'd do in this order:
1) stop using nightlies
2) change kernel
3) change radio
There was this guy whose phone froze every time he was in space with low or no 3G coverage, and I think changing kernel from snq's to some other solved it for him.
Sent from my HTC Desire using Tapatalk

Thanks for your quick response!
Ok, I appreciate your advice. If the problem keeps occurring I will switch back to the latest stable.
But, still something strange about it: I had absolutely no problem the first weeks i was using this nightly (262 was since November 2011 the latest nightly until today), the problem started to occur from one day to the other.
I am using the radio version since probably half a year or even more, without any problems.
Also, 262 was reported (cyanogenmod forums, other forums) to be very stable on the Desire, almost no people reported having problems with it. That's why i decided to update to build 262. I for my part am suspecting a software being the cause for the freezes, but i have no clue which one.. I even checked the system logs.
As for the kernel: Call me a noob, but how do i change the kernel? I know how to root devices, flash recoveries and roms, but how can i change the kernel directly?
Greetings,
toco

tocophonic said:
As for the kernel: Call me a noob, but how do i change the kernel? I know how to root devices, flash recoveries and roms, but how can i change the kernel directly?
Click to expand...
Click to collapse
Kernel is flashed the same way as roms are. Make sure you use a correct one, manU 2.1 is probably the most popular of those which will work on cyanogenmod.
Sent from my HTC Desire using Tapatalk

if that doesn't work:
Dialer/
*#*#4636*#*#
phone settings > network type: WCDMA only

Alright, one more thing: If I change the kernel to let's say Manu 2.1 - how can I switch back to the original CM7 kernel again? Just by reinstalling the CM7 ROM?
Thanks!
bortak said:
if that doesn't work:
Dialer/
*#*#4636*#*#
phone settings > network type: WCDMA only
Click to expand...
Click to collapse
Wait, if I set it to WCDMA only I can only access data services when in a 3G covered area, right? Thats not optimal either because i'm regularily visiting my parents on weekends, where only 2G coverage is available. Also in some buildings (esp. cellars) here in the city there is only 2G coverage.

tocophonic said:
Alright, one more thing: If I change the kernel to let's say Manu 2.1 - how can I switch back to the original CM7 kernel again? Just by reinstalling the CM7 ROM?
Thanks!
Wait, if I set it to WCDMA only I can only access data services when in a 3G covered area, right? Thats not optimal either because i'm regularily visiting my parents on weekends, where only 2G coverage is available. Also in some buildings (esp. cellars) here in the city there is only 2G coverage.
Click to expand...
Click to collapse
Yeah, but it can solve the issue, I get it intermittently sometimes too but after a reboot or two its usually fine.

Hi
I have similar problem, freeze mainly occuring when the radio reception is poor...
Tried almost evrything differents ROM, kernels, gparted my SD, full wipe....
For three weeks I have no freeze since i tried bending the slots cards like mentionned here :
http://forum.xda-developers.com/show...6&postcount=96

bertrand13 said:
http://forum.xda-developers.com/show...6&postcount=96
Click to expand...
Click to collapse
I'm afraid your link does not work bertrand I get a 404 there. Can u please repost the link?

bortak said:
Yeah, but it can solve the issue, I get it intermittently sometimes too but after a reboot or two its usually fine.
Click to expand...
Click to collapse
I would have written you a PM but as I'm not yet allowed to (too few xda posts) I have to put the question here: What happens on May 7th (your signature)? Because i'm looking for an adequate successor to my Desire (~3,7" display) as well.

tocophonic said:
I'm afraid your link does not work bertrand I get a 404 there. Can u please repost the link?
Click to expand...
Click to collapse
Sorry about late answer, I bought a Samsung SG2 so i forgot to check here
The right link is
http://forum.xda-developers.com/showpost.php?p=22302386&postcount=96
I have done that one month ago and no a SINGLE freeze
I had about 5 a week before
It was mostly difficult on a train trip.
I am a heavy user of those very fast french train and i suffered of freeze about 3 times per trip (3 hours running 300 kmh)
Since the "bending" of sim an sd card = SOLVED !!

Thanks, that seemed to help! Even if i don't get the logic behind that.. but i don't have to, i just want a working phone
Thanks again mate!

There seems to be a lot of people complaining about desire freeze
I thins this should be tried by those since it fixes freeze for me and for you too !!!
Happy this helps you

I am using an other rom, but had the same issues. Problems gone with new kernel.
Droidzones kernel did it 4 me, but i am on a sense 3.5 rom.
Try with uv and other governors too. But i think its a kerne related problem.
Sent from my rooted Transformer TF101

3G to 2G freeze - solved
Hi,
I had the same issue: on 3G to 2G network change the phone froze. When moved out of 3G coverage, sometimes during/after the call (probably due to 3G-to-2G handover during the call), seconds after forcing the phone to 'GSM only'. I tried different ROMs, different radios, no success. Finally the guilty component was found: microSD card.
I changed from class 10 to class 4 and suddenly the issue disappeared.
The logic behind this is hard to grasp, but I tried two different ROMs now on a slower card and no freezing for couple of days now.

Problems with WIFI, GPS and radio after 2.17 update

A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse

Basic question. Still, have you backed up and tried Factory restore?

recently my phone doesn't read the SIM after a few hours of use. Says there's no SIM.
Sent from my HTC One X using Tapatalk 2

agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi

wilku said:
agree with the first comment. Can't confirm yet WIFI performance but GPS is now really bad. It was working great on 4.0.3 same as WiFi
Click to expand...
Click to collapse
I do not agree. I'm also using 2.17 and everything with GPS and wifi is OK.

Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2

omaboy said:
Have you installed the correct bootfiles also the Kernel for this rom?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I used only files from the instalation guide. No other modifications

CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)

krivas said:
A few problems with 2.17 / 4.0.4
After i installed the update 2.17 i notice that my wifi is even worse. I have i good connection with my Dynalink D635 router. So i don't think it is a hardware problem. But wifi works just sometimes. It was the same with 1.29, but al lot beter Now i loses his connection and than it come back, but mostly there is no data-stream at all.
Also the GPS is not working fine anymore. Lost connection a the time. It was working fine with 1.29 .....
The radio (connection with G/3G/H) is also worse. And sometimes he lose my sim-card and even goes into flight-mode??
HTC, i dont know what you are doing over there, but i have to say that this product is absolutly not what i suspected. I waited for the 2.17 to give the product a second chance, but it is even worse
Click to expand...
Click to collapse
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2

Hunt3r.j2 said:
I have a good question: Did you drop the phone recently or otherwise do anything to push the phone case down? It sounds like you crushed all the antenna contacts or your case just isn't seated right.
SIM losing contact would suggest that the SIM pins aren't fitted snugly against the SIM. You can either put tape on the sim to get to to fit more snugly or send it in for warranty repair.
Sent from my Inspire 4G using Tapatalk 2
Click to expand...
Click to collapse
I did not drop the phone, or did something strange with it. The only thing i want from a device that costs € 500,00 is that everything is does work.

I've have experienced a drop in mobile network signal after the 2.17 update. Haven't tested GPS but WiFi seems alright. I have not dropped the phone nor done anything unusual to it, just updated. Before, I had 5 bars/full signal all the time, and when I checked battery stats the network signal indicator throughout the day was green. Now, after the update the indicator is yellow and I have around 1-3 bars if signal.
Also, I'm in Denmark so I got the 1.29.xxx.12 update which was supposed to optimize signal strength. So right now I hope they are working on a similar fix.
Sent from my HTC One X using xda app-developers app

smidgeox said:
CUSTOM ROMMERS
Just ensure you have installed the rom correctly, aswell as flashing the right boot.img for 2.17.401.2, then although it seems like a pointless task, please do well to include the command 'fastboot erase cache' before AND after the flash of the boot.img, just to be sure we don't have any kernel bits left behind. You could also go the extra mile and clear the dalvik cache in your custom recovery...
STOCK ROMMERS
You should ensure that your update was successful (check this in settings > about > software information) If the software version is 2.17.XXX.X
Then the update was successful, just double check your radio/baseband is what its supposed to be which is 2.1204.135.20 (i think)
Click to expand...
Click to collapse
The Custom ROMMERS part worked for me.
I had the same Problem. Just checked after a half hour and it still works.
Just try this method

Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.

I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app

dzdimov said:
I can also confirm taht after the 2.17xxx update wifi is droping a lot. Didn't had that problem on 1.29. Also there are other issues but it will probably be best if I open a new thread or someone else does that, just for the sake that htc will read it and make our phones better
Sent from my A501 using xda app-developers app
Click to expand...
Click to collapse
To me, your issues sound like radio related issued, although I could be wrong. You both on custom roms? With custom recoveries? I suggest if 1.29 worked better signal wise that you flash that radio in your custom recovery. That might improve your signal. Its basically different for everyone which radios work the best so basically it's trial and error.
Lemme know how you get on :thumbup:
Nightscope said:
Dear all,
I was using the Lee-droid rom. I switched to insert coin rom 9.xx and even tried the android revolution rom. In both I had the same problem. Using wifi I have almost no data although the signal is strong. It just keeps trying to synchronize like for hours. But for some reason whatsapp conncection works and no problems there, but when it comes to loading the play store it takes ages (5 min. plus). I already searched the internet for solutions but haven't found one. When I use my providers internet, it also just keeps trying to synch (and for some reason never seems to complete??) internet is also really slow and it used to be faster on mobile as wel as wifi. Is anyone else experiencing this?
I am really desperate to get this working, I hope someone can point me in the right direction.
Edit: Confirmed that wifi does drop out sometimes and cant seems to get a signal although im standing right next to the router. But when I have wifi, I have a great connection, but almost no data, only whatsapp seems to work.
Click to expand...
Click to collapse
Sent from my now amazing HTC One X thanks to TeamVenoms ViperX rom

I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now

duckysempai said:
I'm not sure if it's the same problem but i've been having a strange issue for a while. I believe is started when I began using jellybean roms (Not 100% sure). My phone will work for a day or two with no issues and then I just suddenly lose my gsm/3g connection. Numerous restarts later and if still doesn't work. Can't use it as a phone at all. If I reflash or change the rom, my connection works again for a few days and then then same thing happens. I'm having to reinstall roms every few days to have a working phone. I did have the pogo battery cover on for most of that time. Last time it happened, I removed the cover and I suddenly had a connection. I've left it off since, hoping it was just that but sadly not. Happened again to me just now
Click to expand...
Click to collapse
Hi, have you flashed any different radios? What's your current software version and does your Wifi drop as well? Or is it just mobile data?

After the 2.17 OTA update, the signal is always medium...but now there r no call drops or loss in signal

sandipbarik said:
I got my 2.17 OTA update last night, immedietly after the update my wifi signal was dropping, which was pretty stable 3 bars before that.
Today morning im getting dropped gsm signal...sometimes its showing no signal...eve a manual signal search gets me no network, omly airplane mode on/off gets the signal back.
I m not unlocked and not rooted...just plain factory stock.
should i unlock it and flash the radio from the 1.29 rom ??
Click to expand...
Click to collapse
That's up to you, but many users have experienced that some radios work better for different people. 2.17 works ok for me, maybe you should try.
Sent from my HTC One X

I think i have the same problem, when data On, GPS On he sometimes turn of after i turn in and when put the pin and he try to connect to the carrier turn of again. This only happens now when i flash faux kernel and before with alex-v kernel..

[Q] Push notifications delayed on WIFI

I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio

No problem with Gmail push notification on Stock 2.17.401.2.
Yesterday I still was on ARHD 9.7.2, also there I never noticed any delay.
Edit: this complies to various wifi networks (@home, @office, @parents etc.)

Zendio said:
I've seen a few similar threads to the one I'm about to make. I've tried different suggestions which I will post here. Yet, none of them seems to work and I'm curious to see if anyone of you has a fix for my problem. My phone is an unbranded international HOX using the 9.7.2 ARHD rom by Mike1986. Here we go:
Problem
While being on WIFI my push notifications aren't coming through in time. There's a delay from anywhere between a few minutes up to as much as 40+ minutes. The phone doesn't have this issue being on the mobile data network. I'm also not 100% sure if the delay is still there when I'm on an different router. Even when I turn on the screen again, the messages seem to come in randomly.
Settings
WIFI best performance enabled
Static IP by router
WIFI sleep policy: Wifi always on
Tried suggestions
Wakelock: One thread described using an app called REGPON keep-alive, which installs a wakelock onto the phone to keep the data connection alive. This app did not do the trick. It only drained my battery and the messages still didn't come through.
Wifi performance: Set the phone to maximum wifi performance. This seemed to work for a while but ended up not working proper either
Kernel: Try a different kernel was one suggestion. I've switched from Stock to Faux123 010 kernel. This didn't change anything about the WIFI problem.
Static IP + Portforwarding + Disabling router Firewall: I've tried both port forwarding on port 5228 and even the range 5224-5228. I've also tried setting up triggered ranges. Maybe I'm doing something wrong on this part though. The router firewall is disabled and it should no longer block anonymous WAN packages.
Disable SmartSync: With the Suite Tools that are included in Mike1986's rom I've disabled Smartsync. No results as far as the wifi problem goes.
Probing app: I've tried an app that supposedly probes my router at least every minute in order to keep the connection alive.
Switching between b/g/n network: Didn't make a difference. The signal quality of the router is also good.
The only thing that did work for extended periods of time was using this remote control app that allows me to type through my PC keyboard, where the text ended up on the phone. I've also got an app installed to test push notifications. It's capable of making a log. Maybe that'll give you guys more information.
Right now I'm not sure if it's an issue with the HOX or if my router somehow stops the traffic. I don't recall having this problem on my HTC Desire. Does anyone have anymore tips?
Thanks,
Zendio
Click to expand...
Click to collapse
I am so sorry to hear you are affected by this problem, but also happy someone else is experiencing the exact same thing as I am !!!
I have tried different solutions to no avail.
Would love to hear something on this topic !!

Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.

Zendio said:
Also I should note, I don't have any kind of task killer installed.
In general use WIFI feels really fluid and responsive. I really have no idea what could cause these problems.
Click to expand...
Click to collapse
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3

modd1uk said:
Did we get any update on this, I have the issues on 3 phones..desire HD, sensation and a brand new Galaxy S3
Click to expand...
Click to collapse
I hope so. My One S is experiencing the same thing. I've tried everything above. No luck. Some stuff is fairly critical that I get it as soon as it comes in. I might try getting ahold of a Nexus 4 and do some testing with its wifi, just to make sure it isn't a general Android problem.

What router do you have? My issue was any android device in the house. Turned out it was my router, I put a custom firmware on it and all my trouble have gone away. My friend has the WiFi issue on a virgin media superhub.
Sent from my HTC Sensation Z710e using Tapatalk

I have an Asus RT-N66U. Funny you should suggest that. I'd planned to throw Tomato on it tonight and see how that works out. I did some tests at my folks' and their router had the same results. It's some cheap Netgear thing. Not sure of the model at the mo. I'll post back with results. If not tonight, tomorrow some time.

No go
Well that was unsuccessful. Actually it slowed things down. With the default firmware I get notifications from the instant I press power to wake up my phone. With Tomato there was a second or so before I got them.
Time to try DD-WRT tonight to see if that does the same thing.

I have an rt-n56u so the older version of yours and I'm running the Asus wrt that is being made, its fixed all my problems and is awesome tbh.
Sent from my HTC Sensation Z710e using Tapatalk

Set Beacon mode power safe (BMPS) to 0 in WiFi ???.ini config file should resolve this problem.
Such ???.ini config file usually placed under /system/etc/wifi or /system/etc/firmware/wlan/prima/

Defy+ Plus phone and data hang

Hi all, I posted in the CM10 support thread, but this issue doesn't seem to be well known so I'm raising it in its own thread.
I'm not having much luck with my newly-purchased Defy+. The factory firmware suffered random reboots, which is pretty well documented. I installed the latest CM10-20121018-NIGHTLY-mb526.zip, and the random reboots have stopped. However I now get occasional dropouts of phone and 3G service.
Usually, I find out when either I try to use data and even though the 3G icon suggests a connection, no data is transferred. Then the phone app hangs when I try to make a call. If people call me, they *do* get a ringtone, but my phone doesn't make any sound or visual feedback that there's a call coming in. Aircraft mode doesn't rescue the situation, I have to reboot the phone to get it to work.
Hope someone can help - I came from a rock-solid CM7 / HTC Desire HD setup, and this is doing my head in. Am happy to provide any more debug information as required.
NB I see from http://forum.xda-developers.com/showpost.php?p=31440310&postcount=321 that there is a known 3G data dropout bug on these phones, but that's not what I see - I can't make phone calls either. Plus my ROM has that fix in.
I have installed Connection Checker which will hopefully give me details of if there's any pattern to the problematic behaviour. Look forward to any feedback, thanks in advance.

topperdoggle said:
Hi all, I posted in the CM10 support thread, but this issue doesn't seem to be well known so I'm raising it in its own thread.
Click to expand...
Click to collapse
I'll let this go, but be aware that usually double posting will result in any subsequent threads being closed.

Change baseband. I had the same problem. It's solved changing the baseband.
Mine was Europe\central Europe\3.4.x or 3.4.2-145 changing to 2.21 no problem at all.
Sent from my MB526 using xda app-developers app

cyrusct82 said:
Change baseband. I had the same problem. It's solved changing the baseband.
Mine was Europe\central Europe\3.4.x or 3.4.2-145 changing to 2.21 no problem at all.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the response, it's interesting and heartening. I can't find a factory SBF so I can't take it back to the shop.
FWIW, I find the baseband screen confusing. My service provider is Golan Telecom. They have a UMTS 2100MHz network, and rely on roaming with another local provider - Cellcom for GSM 900/1800 and UMTS 850/2100.
I think I understand the frequencies but not what the 2.21 etc means.
As I type this, the phone has been on 2.21 for 20 minutes, and is now exhibiting the problem again.
I am now trying Asia / China 0.26/1.10 which has frequencies 850/2100 MHz. If for no other reason than Israel isn't listed in the list. However, that didn't work for long, if at all. I'm absolutely hating this.
Can you or anyone add to this by suggesting how I might choose the right baseband out of the options given?

Try one by one according to your location.
Sent from my MB526 using xda app-developers app

cyrusct82 said:
Try one by one according to your location.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Well, my location (Israel) isn't in the list. I've tried many settings, with varying results, but not one has been able to avoid this problem where the phone (app as in the actual telephone) just hangs and I lose voice and data. I can keep going, but I don't understand why one would magically work. I think 900/2100 should work with my SP, and I don't understand the differences between the myriad of options that still result in the same frequencies. Have I missed something?
Is there anything else worth trying? I have heard that sometimes it can be a SIM problem, but my SIM isn't even a year old.

I think I have a fix, due to great work by coas (see http://forum.xda-developers.com/showpost.php?p=31025913&postcount=34).
My carrier (Golan Telecom) has a national roaming agreement with Cellcom. It seems that flashing the Cellcom radio for the Defy Plus has fixed the issue. It's been up for four hours now, which is four times as long as before.
I guess the issue is that flashing the SBF to root the Defy Plus, messed up the radio in some way, but I don't really understand the whole radio issue, and what is different in radios from different carriers' firmware. I thought GSM was GSM and UMTS was UMTS. Anyway it seems to be working so I'm not complaining.
Just wanted to put this here for the benefit of anyone else who might be having the same issue.

Sadly, it was a short-lived "fix". Still unreliable, just not quite as bad. I'm going to try the Orange (Partner) radio .sbf which coas tells me is updated, and if not, then return it to factory firmware and take it back to the shop.

topperdoggle said:
Sadly, it was a short-lived "fix". Still unreliable, just not quite as bad. I'm going to try the Orange (Partner) radio .sbf which coas tells me is updated, and if not, then return it to factory firmware and take it back to the shop.
Click to expand...
Click to collapse
If you are willing to stick with a Custom ROM, you can try a different setting on the CPU Settings.
Not a long time ago, I had similar problems and solved it enabling "load all modules" and "conservative" settings in the custom recovery.
Good Luck and let me know if it worked for you.

Hi, thanks for the answer. I didn't update the thread, but I can confirm that I took it back to the shop. The guy knew about the problem and replaced the handset, and now it's fine. So it's a hardware issue - he said it happens on around 1 in 5 Defy Pluses.

Hi, I had the very same problem with my defy+, it suffered that issue on CM9 and CM10. I could not resolve it and had to go back to stock, it works fine now.
It seems the problem is more frequent with national roaming in use.
After the replacement, is everything working fine even with CM10?

Android 4.3 WiFi Issue

Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!

I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app

Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.

geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?

http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2

What I really wanto to know if this issue is posted in the official google bugs tracker

Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4

stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.

I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app

Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.

FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app

FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4

I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.

I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..

memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.

stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?

stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4

memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?

stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844