32 replies to this topic

[astroswede]

 jaimefortega, on 10 July 2012 - 12:01 AM, said:

Hey, i believe that the automatic mode (GSM/WCDMA), in the GSM/UMTS Network Preferences menu, is causing some trouble, i selected only WCDMA, and it seems to be working fine now. Give it a try!

If this fixes the problem, i'll try using GSM/WCDA (WCDMA preferred), just to see if i can use 2G when i want

I tried WCDMA preferred but I eventually lost connection anyway. But I had done several other things at the same time so maybe I should try again. WCDMA only seems not like an option. If you leave 3G coverage you would still want to be able to call.

 tomhanman, on 09 July 2012 - 08:25 AM, said:

Hello, can't help, but I thought I'd mention that I've always experienced this with CM7.1 on my DEFY... was hoping that it would be fixed - as its the only thing that needed fixing - at least getting a 3G conection on my phone seems more important to me than the colour of the overscroll background!

Like you state, it seems to happen in almost any situation - either after a few days, or straight away after a restart, but a restart can fix it too!

Do you think we should look at what apps we have in common to find possible 3rd party causes? I expect if this was just the way it is with the Defy then there would be more shouting.

I have today joined 7.2, yet to see if it has changed anything (apart from the rather lurid pale blue everywhere).

Tom.

I could also be that we that have this problem have a hardware problem that motorola covered up with software and that this is missing from CM.

[jaimefortega]

 astroswede, on 10 July 2012 - 08:48 AM, said:

I tried WCDMA preferred but I eventually lost connection anyway. But I had done several other things at the same time so maybe I should try again. WCDMA only seems not like an option. If you leave 3G coverage you would still want to be able to call.



I could also be that we that have this problem have a hardware problem that motorola covered up with software and that this is missing from CM.

If the connection comes back without the need of a reboot, i believe that it's fine, why? because i always use a 3G connection over an Huawei USB Modem, and i always get disconnected. These kind of things depends most of where you live and your service provider. I don't believe that this is a hardware problem, but a Signal strenght. But at least, with my phone, i don't need to restart it, and the battery doesn't drain too fast.

This could be a problem with some energy saving tool too.

Edited by jaimefortega, 10 July 2012 - 07:39 PM.

[jaimefortega]

well, i guess that i'll wait a few days more, or just try the latest CM9 nightly, because this problem is in CM9 too.
------------
no, i just got to restart my cellphone

Edited by jaimefortega, 10 July 2012 - 07:47 PM.

[jaimefortega]

If i use the Energy Management widget to enable/disable the Data Connection, when I definitly can't get a 3G connection,  and if i try to disable the Data Connection then i get the following error:

"network mode state unknown. please change it manually"

I believe that this is a good start for filling a bug report, but i don't know how to do it because i'm new to this, i don't know what kind of log files are needed, and i don't have so much time these days.

Edited by jaimefortega, 10 July 2012 - 10:50 PM.

[jaimefortega]

Guys, now i'm REALLY sure about what the problem is... the error happens when trying to change from a WCDMA to GSM, or from a GSM to an WCDMA network. Why am i sure of this? well, I've made changes in the GSM/UMTS Network Preferences menu, i wanted to know if there is another way to configure this, well, i discovered that there is a hidden menu, YES, calling to *#*#4636#*#* will show it, if you can't connect to your 3G network then call to *#*#4636#*#*, go to "Information about this phone" and  it will say an error saying:

"activation reject GGSN"

and there was an inconsistency between the network preference that i selected, and the one that was showing this Hidden Menu, so I selected only WCDMA which caused an error that never let me change the network, so i set only WCDMA in the typical menu (not hidden), then restart the phone and called *#*#4636#*#*, and it was an inconsistence again, so i selected WCDMA only, and there was no problem at all, so i tapped in the button that deactivates the connection to the network (yes, inside the menu) and activated again. So, to be sure that there will be no inconsistency, I've restarted my phone, and there was no inconsistency, but after a while, the change that i've made in the hidden menu was back to GSM auto (PRL), it ALWAYS back to that option, I can't set a Prefered Network. I'll see if I can figure out how to keep a prefered network, thus we can workaround this, otherwise, we'll have to report this error and wait for a fix

Edited by jaimefortega, 11 July 2012 - 03:08 AM.

[jaimefortega]

It looks like that there is no way to workaround this, i just noticed that the Prefered Network make changes by itself. It never stays constant, I got disconnected, and instead of saying "GSM auto (PRL)" as a prefered network, it says "GSM only", and every time this happens you can't get connected, no matter what you do, if you set GSM only on both menus this will change, even if you force to use 2G only

Edited by jaimefortega, 11 July 2012 - 05:56 PM.

[tomhanman]

Jaimefortega, thats some seriously good work!! How the hell did you find the crazy hidden menu?!

I have done the same on my phone, although it is working on wifi at the moment. I don't know exactly where in the list of info you see your error, or if thats all you see? I have a list of stuff including ping host Google, signal strength, gsm service etc etc, then I get to:

GSM disconnects:

And it says:' DATA, State: DcInactiveState disconnected with last try at 12:59 AM fail because No Error'

I love that, gotto love logic 'fail because no error' WHAT!? Anyhow, I was fast asleep at 1 in the morning, so was not interacting with the phone at all, and the wifi was active all day and night, so I can see no reason for anything to have 'happened' at 12:59 AM.

As I live in the country, the network coverage is poor, (it even indicates 'no neighbouring cells) so I now use WIFI all the time at home/work, so I can't really help with showing up the problem all the time.

Speaking of which, do any of you have Wifi-N problems with the DEFY? I have had to disable N on my router as as soon as the Defy connected in N, it crashed the entire network! This is a problem I have read a bit about in the past - wondering if it could be linked... doesn't affect all routers etc, so difficult to trace. There doesn't seem to be any fix for it - except disabling the wifi-N... which is not a fix.

I would say you have done a lot of work for an amateur, and that this deserves to be looked at by someone with superhuman understanding of these pesky addictive little bricks to be. But as you, I have no idea how that could happen... moderator?

[jaimefortega]

I just googled for it, every cellphone have something hidden.

It looks like that my router doesn't support 802.11 n, so i can't really help you with it.


Anyway, i've done something about 2 days ago, and since then, my 3g is stable, and i can change between 2G and 3G without a problem. So this is what i've done:

- I did a hard reset to my DEFY (yes, the one that comes with the motorola device, data/cache and cache wipe), but (¡¡¡WARNING!!!) after doing this you'll NEED to use RSD Lite to flash the Android 2.2.2 Stock Firmware (i've restored the original software that comes with DEFY and is specific for my service provider), and yes, you'll NEED it, or your battery will not be recognized by your phone (soft brick) and it'll be drained until it's over, and if that happens, you'll need to charge the battery using another way just to flash your phone. This happened to me and gave me a real pain in my ... but it gets fixed by flashing the original firmware. I don't know if this can get fixed by using a recovery image (that contains your stock software), i mean the one that one can make before installing a custom rom, maybe you can try this before using a firmware. But, make sure that your stock software contains Android 2.2.2. (WARNING: Using RSD Lite with the wrong firmware may BRICK your phone)

- After using RSD Lite, I've rooted my phone and installed the bootloader.

- I've wiped data/cache and cache in custom recovery mode.

- Install cm7.2 and gapps in the custom recovery mode.

- After this, i've selected the right baseband for my region and then configured the APN.

Done

I don't know if CM7.2 requires 2.2.2 stock to works fine, because maybe requires some kind of specific things that comes with the stock software. I'm saying this because i've rooted an Optimus One, that came with 2.2.1 and after installing the custom rom, there was no way to make a call, because the baseband configuration was unknown, and the only chance to get it working, was updating the stock software to the latest version, 2.3.3, and THEN install the custom rom. So, that should do it.

Edited by jaimefortega, 13 July 2012 - 08:26 PM.

[tomhanman]

OK, congratulations!

So basically you're saying a totally clean install on a defy that has been returned to the as new straight out of the box condition has solved the problems. Hmm, ok. Quite a lot of work, and risk, but if it works... Let us know if it is proving reliable, then maybe when I have a quiet weekend I'll have a go. Thanks,
Tom.

[jaimefortega]

It looks like that it doesn't work, but at least it last like 3 days, not hours like before, and the battery doesn't drain too fast like before. I just noticed that i'm not using the proper APN configuration, so i just deleted the old configuration and created a new configuration using tweakker.
If you're not sure what baseband you need to use, this may help you a bit.

http://en.wikipedia....le_Network_Code

I refuse to believe that this is a hardware problem , more news about this in five days more i guess.

[jaimefortega]

I've found something interesting, I have another rooted phone, with CM7.2 (LG P500) with a SIM card from another service provider, and 3G works great, i never turned it off for a month. So, i changed the SIM cards, and guess what... after two hours i got the same problem, or after a day, it's very random... So this should be a problem of the SIM card, or of the service provider...
one question for all of you...

Have you changed your Service Provider and kept the old phone?
because that's my case. My previus provider was Movistar, and now i'm in Virgin Mobile. I guess that this kind of devices doesn't work well when you change your service provider

Edited by jaimefortega, 01 August 2012 - 03:42 AM.

[jaimefortega]

I called to the service provider support, about 6 days ago, and they told me that my device was defective, then i told them that the problem happens even after changing the device, so they told me that the problem was another, and that i wasn't the only one who was experiencing this behaviour. And now there have been more than 4 days without a problem, even when the signal strength is very low or when i lost it because of travelling. This is a service provider problem, and not with your device

Edited by jaimefortega, 06 August 2012 - 09:05 PM.

[pr0zac]

Just to chime in... I've tried SEVERAL custom roms on my Defy.
I'm currently in São Paulo, Brazil and selecting the correct Baseband won't make it better.
For some reason, Cyanogenmod 7, 9 and 10 have the mentioned issue, while others don't.
The stock rom and the MIUI based ones are just much more stable.

The rest is perfect and I love it.

Edited by pr0zac, 10 October 2012 - 01:38 PM.