Related
I posted this in NilsP's Business GingerSense thread, but don't think it's a ROM issue, more of a Google Talk issue. Running the 2.0 version of that ROM.
The issue is where Google Talk shows all your contacts as Offline after a period of say five to ten minutes, maybe shorter than that. I'll be messaging someone, and after a few minutes when they haven't responded, I'll wake my phone and open GT. All the contacts are Offline. A simple sign out/sign in fixes that, and the usual contacts show Online or Away.I've noticed this all week, so I'm thinking it's a GT issue, but I've never had it happen before.
Don't want to have to sign out/in every time I want to use it. Cleared GT cache, fix permissions, multiple wipes of data/system/cache/boot/dalvik/user data before each ROM install, and haven't had this before now.
Thoughts?
EDIT: After playing, it happens when switching from 3G to WiFi and vice versa, so maybe it is a ROM thing...?
i'm having the same issue. noticed after my gingerbread OTA update from verizon.
Droid 2.
It seems to happen a few minutes after logging on.
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
carapauzinho said:
I also have that issue with Gtalk. After some time all contacts appear to be offline, but only when I'm on data connection and not on wifi.
There is still no solution for this?
Cheers!
Click to expand...
Click to collapse
Me too. Anyone was able to do something?
Well I've since moved on, and haven't noticed it on other ROMs. Right now I just tested toggling Wifi on and off, and the contacts would appear offline, then come online once 3g or wifi connected.
I'm thinking in my case, it was that version of the ROM I was running at the time.
Sent from my ADR6300 using xda premium
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
dragon droid said:
Just a thought, check any task killers / managers and make sure talk is unchecked. I had the same problem a long time ago and ATK was the culprit. Haven't had the issue since and I have used almost every Rom possible at one point or another
Sent from my Incredible Stock+v2.6 Ginger Tiny
Click to expand...
Click to collapse
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
RMarkwald said:
True. Right after I rooted over a year ago, I had an issue with the alarm clock not going off intermittantly, and coincidentally I was using ATK at the time. After reading that ATK could be the issue, uninstalling it fixed the issue. Since then, I don't actively kill tasks, but I do have System Panel installed just in case.
I'm running Stock+ v2.6, and since moving on from v2.0 of NilsP's ROM where I had the initial issue, I haven't noticed/had the problem.
Click to expand...
Click to collapse
Hi,
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Thank you both for your input.
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
RMarkwald said:
If you're on a stock ROM (you're both rooted right?), back up your ROM and flash another just to see if it happens in something different.
Click to expand...
Click to collapse
Yes, we are.
The thing is that it seems to me that it happened only after XXVJR (meaning it happened to me in XXJVS and XXJVT, and now we're already at XWJVU, all these being Samsungs "leaks"), and I have a friend with XXJVS that works just fine.
I even tried flashing a stock ROM, to see if it happens again. Testing that one now.
Thanks for your advice.
Same problem here.
Although I have not tried it with stock non rooted phone...
I'm having the same problem on a stock rooted Motorola Photon. Very annoying to have to sign out and back in to see who's online. Hopefully someone comes to the rescue with a solution.
Hi,
The only thing I could find is that the problem is, indeed, NOT in the custom ROM's. It's google's problem.
The only way I could get by was with an alternative IM. And, for me, the better is Trillian (taking battery, performance, etc. in consideration.)
I updated my software which included an updated gtalk with video..so far so good.
crs77 said:
I updated my software which included an updated gtalk with video..so far so good.
Click to expand...
Click to collapse
Mine got better with one of those. But it ended up all the same.
DarkSorcerer said:
Me and the other user are I9000 users. No task killers. We're trying to figure out if its a stock / custom ROM issue (since we're both using the same ROM), or some app forcing GTalk to sign out, or even a network problem (we both use the same mobile operator).
Click to expand...
Click to collapse
I am having this issue too. I have had it since the beginning, when I had the preinstalled stock rom, I had it with all the other stock roms I flashed, I had it with all the versions of Talk I tried (those which supported video calls), I had it with all the other customs roms I tried (Simplicity, CyanogenMod, MIUI). I never used any task killer. For these reasons I am strongly convinced this is a Google Talk related bug.
Some more details about the problem:
after a few minutes after having logged in, contacts are shown offline on Android while they appear online on the desktop client;
despite their offline status I still receive messages from them and as soon as I answer only that contact appears online while the others keep being shown offline;
signing out and back in fixes the problem temporarily, but it happens again after a few minutes.
What surprises me is how come very few people seem noticing it or being annoyed by it? How come a huge bug like this has been out for so long and Google hasn't fixed it yet? All the posts I have seen reporting this problem on Google Talk Help Forum have been ignored.
Exact same problem with my I9100, Gtalk with video. Very annoying.
I have the SGS i777 (Samsung Galaxy S2 on AT&T), and just recently (since late February) started experiencing the same issue. When on WiFi, it doesn't appear to be an issue, only when not on WiFi, particularly if I have just recently turned off WiFi.
Other "friends" show me as "Away", so I am connected.
This is bone stock 2.3.6 Samsung official ROM (never rooted UCKK6).
I tried crawling a bit through the logs (aLogCat output), filtering for "[Tt]alk", but I can't make enough heads or tails about where the failure might be (not being an actual developer), other than lots of messages get created. I'll see if I can't figure something more useful out about it.
A hard reset with no apps installed has the same problem. Though I've noticed that the problem appears to get "worse" as the phone "ages" - namely, hard reset fixes the problem, but it slowly (over days) gets worse and worse.
Update: I have not noticed this issue at all since getting the official Samsung/AT&T ICS build (IML74K.CLE5).
Google Talk failing for toooo loooong
Hi there,
I'm a cyanogen 7.1 (stable) android user, and I just want to join myself to every other person who's affected by this issue.
I'll leave here some links to other places discussion exactly the same issue:
code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=gtalk%20offline&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=24242
You may check this thread: groups.google.com/a/googleproductforums.com/forum/#!topic/chat/6m0YqHoiIDg
Until now, I wasn't also able to find any clue to what the cause may be.
Starting to suspect that's something on Google's side, not android/rom itself.
Maybe something to do with our google accounts' settings?
Are there any news about this issue? I'm having the same problem.
Issue 1: Multitouch issue
- As far as I'm aware of, there is no fix yet and a lot of people are experiencing the issue. What happens is whilst in landscape mode, sometimes, if one finger is placed at the bottom left of the screen, and another is placed on the bottom right, it'll fail to recognize the second touch (bottom right). This doesn't always occur, but does happen at times.
Simple fix: Lock the screen, then unlock it
Issue 2: Wifi consistently dropping
While downloading files, or sometimes even watching youtube videos, the wifi icon will disappear for a split second, then come back and an error will appear along the lines of " File could not be downloaded due to an error" or in the case of the market, it'll just stop downloading and give an error.
Fix: Sadly, the only fix that I have found so far for this issue is to get a new router. See my post here I used a Linksys WRT300N
EDIT: Another potential fix is to change some settings with the router but I'm not sure exactly what settings are needed to be changed.
EDIT2: I've created an issue about the wifi issue over here and according to [email protected]:
Im assuming you are downloading huge files using WiFi... there is a notorious bug still unresolved on DHCP leasing time. If your route is settled to infinite (0 or ffffffff) a local timeout of few minutes is applied, thus the download broke and resume time by time because dhcp renewal. To fix this try to adjust your route settings indicating a discrete leasing time (i.e. 24 hours or 2 days) and thi should fix this specific issue (also noticeble when watching youtube videos, that may freeze after few minutes).
Hope this helps.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Hey everyone,
I have had my Galaxy Nexus from Bell for a few days now, and it is a beast Everything runs smoothly, no lag (even with live wallpaper) and helps me accomplish everything I need from a mobile device ( a hell of a lot better than the milestone - international version of the Droid)
However, there are some prominent issues throughout the device.
1.) The wifi constantly times out, it will stop working at random times even if im 1-2 ft away from the router. Also, when I was downloading SD files for a game (asphalt 6 - 524mb file i think), i had to restart the download at least 10-15 times to finally get it to download. Is this a hardware issue? Can this be fixed through a software update
2.) The multitouch doesn't work at random times. For me, whether its plugged into the charger or not, at random times, when you touch the left side of the device in landscape mode, the device will not recognize touch inputs on the right side. HOWEVER, if you lock the screen, then unlock it, it works flawlessly. I am determined this is a software bug (may not be though) and if it isn't could someone please tell me? Thanks. And a lot of people also have this issue : http://forum.xda-developers.com/showthread.php?t=1385587
Also shown here:
www.youtube.com/watch?v=YdRSRROffO4
I have two question for you awesome people at XDA.
1.) Could someone please either post an issue to Google regarding these two issues or direct me to a website where I can post them?
2.) Could any of these be a hardware issue? Do you think I should return it and get another one?
Thanks so much guys,
Mosh
Would also like to know if the second problem is software related or not :/
EDIT: noticed now that my screen gets really hot at the top. Really hot! Does your get warm aswell?
Don't know. The easy fix is to swap it.
Sent from my Galaxy Nexus using xda premium
Both my touchscreen and WiFi have been working flawlessly.
I did have some initial hiccups with the WiFi until I power cycled my router.
Sent from my Galaxy Nexus using xda premium
Make sure 'Avoid poor connections" is ticked off in the advanced WiFi settings.
sgs064 said:
Make sure 'Avoid poor connections" is ticked off in the advanced WiFi settings.
Click to expand...
Click to collapse
I've been having WiFi trouble with the Nexus too - the phone generally seems to get poorer signal in comparison to my other devices. I've unticked this box, but it still keeps avoiding connecting (and when I go to WiFi settings, actually says it's avoiding connecting to my network because the connection is poor). It's frustrating, to say the least.
Rather than immediately assume that you should swap the phone, or thinking it's hardware, or (?).
What build do you have? There are at least 3 builds available for the SGN.
http://forum.xda-developers.com/showthread.php?t=1376856
Sounds like another on the way...
sephtin said:
Rather than immediately assume that you should swap the phone, or thinking it's hardware, or (?).
What build do you have? There are at least 3 builds available for the SGN.
http://forum.xda-developers.com/showthread.php?t=1376856
Sounds like another on the way...
Click to expand...
Click to collapse
Seriously people need to stop making such a big deal of these separate builds.
WiFi could be an issue with the router. I had a problem where connecting Nexus to the router would cause both mine and other users internet in the network fail. Once I disconnected, internet returned. It worked on first few loads, then not anymore. Strange thing is that it fixed itself few weeks later.
(Same happened once with another router and when I was using HTC Desire, Android seems to be a wacky WiFi partner)
@rbiter said:
Don't know. The easy fix is to swap it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not this. If its software you end up with another phone with the same problem.
You may find other radios help with wifi, check the dev section for details if you have a rooted device. Otherwise youll probably need to wait for one of them to drop via an official ota.
As others have said, uncheck the weak wifi option
In terms of the multitouch issue, just tested my device and can't see any issues at all. Could be software related as the screen itself can support 10inputs - be interesting for users on non standard roms to check and see if they do have a problem as this may lend some weight towards the software related argument.
mohitrocks said:
Hey everyone,
I have had my Galaxy Nexus from Bell for a few days now, and it is a beast Everything runs smoothly, no lag (even with live wallpaper) and helps me accomplish everything I need from a mobile device ( a hell of a lot better than the milestone - international version of the Droid)
However, there are some prominent issues throughout the device.
1.) The wifi constantly times out, it will stop working at random times even if im 1-2 ft away from the router. Also, when I was downloading SD files for a game (asphalt 6 - 524mb file i think), i had to restart the download at least 10-15 times to finally get it to download. Is this a hardware issue? Can this be fixed through a software update
2.) The multitouch doesn't work at random times. For me, whether its plugged into the charger or not, at random times, when you touch the left side of the device in landscape mode, the device will not recognize touch inputs on the right side. HOWEVER, if you lock the screen, then unlock it, it works flawlessly. I am determined this is a software bug (may not be though) and if it isn't could someone please tell me? Thanks. And a lot of people also have this issue : http://forum.xda-developers.com/showthread.php?t=1385587
Also shown here:
www.youtube.com/watch?v=YdRSRROffO4
I have two question for you awesome people at XDA.
1.) Could someone please either post an issue to Google regarding these two issues or direct me to a website where I can post them?
2.) Could any of these be a hardware issue? Do you think I should return it and get another one?
Thanks so much guys,
Mosh
Click to expand...
Click to collapse
I get #2 in shadow gun if it goes into sleep mode while i'm playing. Its clearly a software issue as restarting the game it goes away.
Point 1 happens to me too. I've tried multiple ROM's. I'm getting a bit worried that it's hardware. It's dropping every few mins when I need it... then it comes back rather quick.
You have any news or has anyone else experienced it?
I'm not seeing a ton of people talk about this wifi problem, so I'm guessing it's not a widespread issue. I'm assuming it's not hardware either, but I'm curious about it. Whenever I turn on wifi on the Nexus and it tries to connect to my router, it disables all other connections, and the Nexus reports that it's not in range of the router. I'm interested in what routers people are using that are experiencing this issue.
I have a D-Link DI-624, a free router provided by Verizon with FIOS signup. I'm using a custom password, not the one that came with the device. I have a 13 digit alphanumeric password (sorry, I can't remember the exact security setting for it).
Edit: Actually been doing some research on this, and it's appearing it may be a frequency / channel issue, that the phone is broadcasting at a frequency similar to your router. Looking into exact fixes at the moment.
I have no problem with wifi and multi touch.
But I noticed that two fingers cannot be very closely touched it will mingle together. For example if you hold shift button on keyboard it could act like normal shift (turn lowercase to upper or vice versa) but its very difficult to use shift + a
Also lots of games exiting on me, first I thought was multi touch acting up so I could accidentally hit home or back button. But then I think its just matter or compatibility of those games with ICS.
Sent from my Galaxy Nexus using XDA App
do you know if the latest update solved the touch problem?
Same issues here. On the samung version (dont remember the codename) i had this issue so i rooted and changed it so that google updates my phone. But this didn't help either. Still losing wifi when i am downloading. Like now i was going to download 9mm and after 2 seconds the wifi disconnect until i quit 9mm and then it pops up straight away. Can it be a hardware issue?
PS: before i change my phone brand to google, i could see the "avoid poor wifi connection" but now when i go to advanced tab it's gone :S
Ok everytime i try to test wifi in speedtest it says network communication issues after 2 sec of testing. Any info please? Do i have a faulty unit? going crazy over here
For what it's worth, I haven't had either of these problems on my Galaxy Nexus, and it's been on a lot of WiFi networks.
I've gotten speeds in excess of 20mbit/20mbit via the speedtest.net app multiple times on the campus wifi, as well as my parents', and my dorm connections. I've downloaded the Asphalt files twice without any interruptions either time, and I've never experienced any problems.
As for multitouch - no problems with that either. To type in all caps you can hold down the caps button on the keyboard and type - it's never given me any issues. I don't think I've been in a situation where I've felt multitouch hasn't performed right.
horadee said:
Point 1 happens to me too. I've tried multiple ROM's. I'm getting a bit worried that it's hardware. It's dropping every few mins when I need it... then it comes back rather quick.
You have any news or has anyone else experienced it?
Click to expand...
Click to collapse
Multiple ROMs doesn't mean much, they all share official driver binaries and radios that are available.
Sent from my Galaxy Nexus using Tapatalk
Manacit said:
For what it's worth, I haven't had either of these problems on my Galaxy Nexus, and it's been on a lot of WiFi networks.
I've gotten speeds in excess of 20mbit/20mbit via the speedtest.net app multiple times on the campus wifi, as well as my parents', and my dorm connections. I've downloaded the Asphalt files twice without any interruptions either time, and I've never experienced any problems.
As for multitouch - no problems with that either. To type in all caps you can hold down the caps button on the keyboard and type - it's never given me any issues. I don't think I've been in a situation where I've felt multitouch hasn't performed right.
Click to expand...
Click to collapse
Then i probably got a faulty unit. Will give it 2 more days and if it's still the same i'll return it.
Hey There,
I've just installed this fine ROM today, and it seems great,
but for some reason, the wifi reception is BAD now.
It works fine if I seat near my router, but if I move 3 meters away
it looses the connection ... and says the reception is POOR.
Any1 else has this problem?
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Thanks for the quick replay
I flashed the "[08-09] [ROM] CyanogenMod 10 - Endeavor Unleashed" rom.
I don't think this is the same cm10 everyone's using.
and I don't really understand, doesn't the Kernal comes with the rom?
Can I change it without changing a rom ?
alexx_za said:
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
I notice the same problem a few days ago (I think is since I have install CM10). I have switched on OrDrost since 2 days, I tried the Faux kernel and finally I just revert to full stock rom and my wifi signal haven't change :/
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Thesalan said:
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Click to expand...
Click to collapse
But on the stock rom WIFI was ok.
Update: Ok I did the "Squeeze" test. Wifi is great whn I squeeze
So it is a hardware problem?? How it only started after I put CM10?
Have you reinstalled the stock rom since you have the problem?
I don't know if CM10 is the cause, or it's a coincidence..
there's an UNOFFICIAL release at the moment which may fix some issues, though I've not noticed anything and I've had every release since A10 installed, so it could be a hardware issue.
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Thesalan said:
Have you reinstalled the stock rom since you have the problem?
Click to expand...
Click to collapse
Not yet, I really hate the stock rom.
tgcp, Where can I get this rom?
(Although it really seems like an hardware problem,
I heard the latest stock update helps a little so there
might be a software solution)
Rodbouy said:
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But if you use Cm10 without that little earphone cable, the wifi won't work good?
BTW, what does htc support ask to fix the problem? Do they care you rooted and unlocked the device?
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
but it is noticeable!
I can't move more then 2 meters from my router or it disconnects.
Does your wifi issue not that bad? (without the cable's help)
With out my fix the signal is a joke. 1 bar when 3 feet away. Wasnt usable.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Problem is I can't get back to stock! from what I understand the Stock RUU for my phone wasn't released ...
Do you think HTC will be "understanding" and fix the wifi issue even with a custom rom?
(they'll know anyway that I opened bootloader)
Try flash the Rom with the stock kernel, that will surely solve the WiFi problem.
Sent from my HTC Desire C using xda premium
Did you not do a backup before installing custom rom. Im positive that even if you relock the bootloader they can see that if they went in to recovery. But unlikely. So if you flash stock rom and re lock bootloader, remove root you should be fine
Sent from my HTC One X using xda app-developers app
Hi, try using tbaldens CM10. It can be found under HTC ONE X ORIGINAL ANDROID DEVELOPMENT. I found this to be the best CM10
I have been chasing this problem ever since installing CM10 on my Evo 4g LTE. I was getting 4 times the wifi distance on the stock rom. I go about 30 ft. outside the office and wifi drops. Also, what is the most annoying... I stream over our LAN, and when the screen is off, it turns wifi off after a few minutes. (and yes, the check box is checked to keep wifi alive). I've also tried all of the wifi fix apps and none work. If I leave the screen on and stream........ it is good anywhere from 1/2 hour to an hour, then it will just stop. This kills my battery of course. The problem 1st occured when I first bought my OEM 4g lte, but there was an option in the advanced menu "best wifi performance", after checking that, it worked great, then I switched to CM10 and I now have the wifi issue, and there is no option for "best wifi performance". I've tried a couple other jellybean roms and they have the issue as well. This is driving me nuts. I hope someone finds a solution. I don't think the average person would find this as a problem, but when I stream over the net and move all about the shop, it is unacceptable.
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
rectorfury said:
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
Click to expand...
Click to collapse
I've tried changing my Region Code, but for some reason it keeps defaulting back to Europe... Any ideas? I've tried changing it numerous times, same result.
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?
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