Develop Bugs

[Q] Whatsapp drops connection on Wifi.

So yeah, I have been noticing that my Desire running on the latest MildWild software (and Cyanogenmod 7.2) for that matter has been trouble keeping it's connection constant on Whatsapp.
Basically, it stops 'reporting' when it comes to 'last seen'. Sometimes I have to turn off Wifi (It is mostly on Wifi, can't recall it being the same story on 3G but I think so too) to fix the connection. Other times it just reconnects after a minute.
This happens when the screen is turned off and back on.
It's getting a kind of annoying and I have no idea where to look. I've checked my modem and router and both are fine.
Anyone else with this problem? Any ideas how I can fix this? Also, Wifi Sleep Policy has been set to 'Never'.

the same galaxy s3
Ravons said:
So yeah, I have been noticing that my Desire running on the latest MildWild software (and Cyanogenmod 7.2) for that matter has been trouble keeping it's connection constant on Whatsapp.
Basically, it stops 'reporting' when it comes to 'last seen'. Sometimes I have to turn off Wifi (It is mostly on Wifi, can't recall it being the same story on 3G but I think so too) to fix the connection. Other times it just reconnects after a minute.
This happens when the screen is turned off and back on.
It's getting a kind of annoying and I have no idea where to look. I've checked my modem and router and both are fine.
Anyone else with this problem? Any ideas how I can fix this? Also, Wifi Sleep Policy has been set to 'Never'.
Click to expand...
Click to collapse
Any help please,
Rooted s3, I restore the device but still the same,when my wifi is on and start whatsapp it drop and phone data starts for few seconds the drops,so I have to start wifi again,
I falsh custom rom ,once twice,then I wipe out all my data factory reset, re install whatsapp the problem comes again.when I uninstall whatsapp the wifi stay stable!!!

WiFi connectivity issues on all Jelly Bean ROMs (grey signal bars)

Ever since I put Jelly Bean on my VZW Galaxy Nexus, if I connect to WiFi and let the screen go to sleep, after a while (ranges from a couple minutes to an hour or so) my WiFi icon will turn grey. It stays this way after I wake up the screen and I won't have Internet connectivity.
I only experience this issue on my home WiFi network. It does not happen on mobile data or my workplace WiFi (which is using WPA2 security like my home network). This issue also has occurred on every Jelly Bean ROM I've tried (stock rooted JB, a couple early CM10 hybrids, Bugless Beast, AOKP build 1 and now CM10 nightlies).
I wanted to test some bare-bones scenarios so I did a clean install of the 8/22/12 CM10 nightly build last night (wipe data / factory reset, format system, wipe dalvik cache, flash CM10, flash gapps, boot). On first boot I connected to WiFi but did not sign in to my Google account or set anything else up. I hooked it up to my computer and ran an adb logcat all night, but the icon stayed blue when I checked this morning.
Since I had no issues in this scenario, I then added my Google account and updated the Gmail app when prompted. Other than that, no change, still haven't even launched an app. Ran another adb logcat and within 10 minutes I started noticing connectivity issues in my logcat so I turned on the screen to check, and sure enough, my WiFi icon was grey.
Attached is the log from the bare bones CM10 after I signed into my Google account and let the screen fall asleep with a blue WiFi icon.
If anyone has any troubleshooting ideas from here, I'd really appreciate the help!
EDIT: Ran a new logcat showing the actual connection process, although this time after noticing the connection issues in the log and turning my screen on, the icon only stayed grey for a few seconds and then turned blue. This is adb-log-2.txt attached.

I assume you already messed with the WiFi sleep settings, right? Also, I read another post explaining that the bars turn from blue to gray when you are not connected to any google services. Not sure if that's true or not.
Anyway, I see the same behavior on my phone at times and although it never bothered me, now I want to know what cause it as well...

Same problem on CM10.
Hi guys,
I have this problem too, in Cyanogen Mod 10. Galaxy Tab 10.1 WiFi here.
After deep sleep (5+ minutes) WiFi locks it self off, i cant turn it back on because its grey d out.
Reboot so far, seems the only solution, a bit annoying have to reboot every time it goes to sleep, but oh well, this rom is still amazing.
Any solutions yet? I wonder trying a diferent Kernel, eve that most users posted it as useless as it keeps locking itself off. :
Cheers!

I'm also unsure of this issue but sometimes it does happen. Turn on airplane mode and then turn it off a few minutes later or reboot.
Sometimes turning off wifi will fix the issue.
To make sure just go into advanced and turn off avoid low signal thing in wifi if you haven't already.
Also unfortunately some routers are picky on our WiFi drivers as with other phones. It is also ROM related too.
I had a droid incredible and on sense 3.5 it always lost WiFi and signal every 50 minutes to an hour.
Sent from my Galaxy Nexus using Tapatalk 2

funkymonk145 said:
Ever since I put Jelly Bean on my VZW Galaxy Nexus, if I connect to WiFi and let the screen go to sleep, after a while (ranges from a couple minutes to an hour or so) my WiFi icon will turn grey. It stays this way after I wake up the screen and I won't have Internet connectivity.
I only experience this issue on my home WiFi network. It does not happen on mobile data or my workplace WiFi (which is using WPA2 security like my home network). This issue also has occurred on every Jelly Bean ROM I've tried (stock rooted JB, a couple early CM10 hybrids, Bugless Beast, AOKP build 1 and now CM10 nightlies).
I wanted to test some bare-bones scenarios so I did a clean install of the 8/22/12 CM10 nightly build last night (wipe data / factory reset, format system, wipe dalvik cache, flash CM10, flash gapps, boot). On first boot I connected to WiFi but did not sign in to my Google account or set anything else up. I hooked it up to my computer and ran an adb logcat all night, but the icon stayed blue when I checked this morning.
Since I had no issues in this scenario, I then added my Google account and updated the Gmail app when prompted. Other than that, no change, still haven't even launched an app. Ran another adb logcat and within 10 minutes I started noticing connectivity issues in my logcat so I turned on the screen to check, and sure enough, my WiFi icon was grey.
Attached is the log from the bare bones CM10 after I signed into my Google account and let the screen fall asleep with a blue WiFi icon.
If anyone has any troubleshooting ideas from here, I'd really appreciate the help!
EDIT: Ran a new logcat showing the actual connection process, although this time after noticing the connection issues in the log and turning my screen on, the icon only stayed grey for a few seconds and then turned blue. This is adb-log-2.txt attached.
Click to expand...
Click to collapse
It could be your network, what's your network setup like?
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Signal loss

Greetings.
I have a problem regarding my gnex's signal loss.
I've been using PA3+ and today I installed the RootBox-JB rom. Both have been installed from scratch (full wipe).
Baseband is I9250XXLJ1.
The problem itself is very odd: as soon as I make a call, the signal bar drops to a minimum (1 or 0 bars) and stays there. When I end the call, the signal keeps changing from 1 to 4 bars ==> there is a lot of signal fluctuations that I get with my gnex.
I noticed that when my WLAN is turned on, the mobile signal is (more or less) being stable. Data "on" or "of" doesn't make any changes.
The problem is that my call quality is miserable - call breaking, talking like the other person is in a "tunnel", and so on.
Until recently everything worked fine (was using PA2.99) and I wasn't experiencing any similar signal-loss problems. Today I returned to stock OTA 4.2.2. and stayed there for hour or two, and didn't notice the problem there.
FTR, bootloader version is PRIMELC03.
Is there anything that I'm missing here?

PS I intslled GetRIL and frome there the RIL is matched with the baseband.
Any help?

I've actually got a similar issue... Since going 4.2.2 on AOKP the radio has been extremely unstable with WiFi on.. It drops like 3 times in 60 seconds and just is in a loop. With WiFi off its a bit more stable but still drops at least once in two mins. If I have a ping app constantly going the radio seems to stay on.
I've wiped tried cm and pa with same radio issues. I've flashed new radios and old radio. Matching RILs non matched RIL. Different kernels and still have crazy GSM radio and off.
I didn't go back to stock though. Once I get my Nexus 4 I'll reset and flash latest stock ota since you said that worked for you. Update thread if you have a break through.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] problem with cm12

Hello all
I installed cm12 nightly and I'm stuck with a setup screen where I have to choose language and WiFi, I select them and then I have a 2nd select WiFi screen
How can I solve this ?
Thanks

I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.

Well I can't skip through it because it gets stuck at the 2nd network detection, probably provider selection but I never get there.
It's the Cm account app, why they need an app for that is beyond me but if it is not solved soon I'll move along to another rom....
In the meantime i'm still looking for a fix
Thanks
apuntigam said:
I'm glad someone started a thread like this for issues with CM12 nightlies. Hopefully it gets used and noticed.
I also had your problem, I just skipped through it until I got to the next part of the setup process.
But overall, CM12 nightly was disappointing compared to the NamelessROM I'm using. Mobile data would be on for only a few seconds then it would disconnect for ages, only occasionally coming back for a few seconds. Makes it unusable for me, and I'd still classify it as an experimental build rather than a nightly because of that. This issue was fixed ages ago in the unofficial 5.0.x ROMs, so I can't understand why CM hasn't fixed it.
Click to expand...
Click to collapse

note 2 n7100 strange Problem

Till yesterday i was on cm13. Everything war working pretty fine.
But suddenly my cell getting restarted again and again as soon as i launch game(clash of clans).
But afterwards i came to know that its not only for that game its happening everywhere.
Its happening like, first suddenly network bar becomes empty and a no service message come in notification.
After 5 to 10 sec network comes again, but it goes again ( at this stage,Either the cell become hang or most of the time it reboots)
all this thing is happening randomly no matter on which app.
after doing some experiment i get to know that...
- Its only happening when mobile data turned on and some incoming and outgoing is going on ( on ideal state its fine, no reboots ) ..
- Its working fine on wifi no random shutdown...no network loss (mobile data was on)
-its also working fine while on charging (Mobile data was on and wifi was off)
i thought it maybe cause of cm13 so i reverted back to 12.1 through nandorid backup.. but all the same story happening...
i think its because efs or modem issue or may be of battery.

CM 13 be BETA and not stable [email protected]
I am also back to 12.1 i have issues with wifi