Related
Hey guys, I'm having an issue where my Atrix keeps disconnecting the data connection every few seconds whenever I start using data (browsing, youtube, google music, etc).
When the issue first started I was running ATT 4.5.91 with 01.77.15 Baseband. So far I tried factory reset, reflashing baseband, CM7 Ba2Tf, and right now I'm running on ATT 4.5.133 rooted and deodexed, with 01.77.36P ATT Baseband. I did the update to 4.5.133 and the current radio via CWM after wiping cache, dalvik and data. The problem still occurs.
If I keep my phone idle, it stays connected (blue bars, blue H+ icon and arrows beneath it).
A few seconds after I start browsing the web or using other data intensive tasks it keeps disconnecting the data connection at frequent intervals, every few seconds. It doesn't drop any signal bars, but the H+ and bars turn grey (lost connection to google servers) and doesn't show the Up/Down arrows below H+, meaning it disconnected the data connection. After a few seconds it connects back and everything turns blue again.
It's really annoying and I'm out of ideas. I have tried reflashing everything, another rom, another radion, also tried setting the apns by hand, all to no avail. Some insight would be very much appreciated, thanks in advance.
Sounds like an app problem. The new market did this in it's earlier versions. Would have to reboot or go into and out of airplane mode to reconnect data. What apps are you using when it happens?
In my case, CPU Tuner was causing this behavior.
I think I've set it up incorrectly or something and as soon as I uninstalled it the problem went away, but will try it again soon.
Sent from my Atrix using Tapatalk
Thanks for the help, guys.
In order to test for an offending app, I cleared /data (factory reset on CWM), cache/dalvik cache and installed the latest CM7 weekly. I did not flash gapps and did not restore/installany third party apps.
The issue still appeared while browsing the web. Then I restored my current rom (att 4.5.133) and left the phone sit for a couple hours. After a while I did a few tests and everything was normal again. Then I went to bed after testing the phone for about one hour and when I woke up the issue was back. Could it be that my carrier has anything to do with it? I'm trying to get a hold of another carrier's SIM with data enable to test it out.
I had this exact issue. I was running CM7 Ba2Tf for several weeks, no problems. Then all of a sudden, my connection to google would drop for no reason at all.
The H+ & signal bars would turn white, indicating that I still had a data connection to AT&T, but no connection to google. Every time I used one of the gapps, the connection to google would drop. This was especially apparent when I was using google talk.
I cleared caches, data, re-flashed, wiped, etc..., and the problem persisted. There was absolutely no way around the problem. I'm baffled that after completing clearing & re-flashing everything, the problem persisted.
I could not find a workaround. I am now running a fruitcake variant, and do not have this problem. I really miss CM7, and am curious to hear if anyone has found a legitimate solution.
It looks like this is not a new bug either. Check out Cyanogen mod issue 3557.
I know that this thread doesn't have much action, but for what it's worth, I don't have this problem on Jokers ICS Roms.
It appears that when this problem manifests itself, it's somewhat rom specific.
Sent from my MB860 using XDA App
Sounds strange, but I had the exact same problem after I installed Chess for Buddies. I removed the app and everything went back to normal. I do miss playing chess though
sp0tted said:
I know that this thread doesn't have much action, but for what it's worth, I don't have this problem on Jokers ICS Roms.
It appears that when this problem manifests itself, it's somewhat rom specific.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I have it on Turl's ICS.
That's crazy! Did you have it the instant you flashed the ROM, or were you able to run for a few days?
What were you running beforehand?
Sent from my MB860 using XDA App
I think those having this problem should try removing APNs they are not using, thus only leave the one you are using.
I was having this issue on any application that would load up the GPS, as soon as I deleted all other APNs and just left the one I needed I never had the problem. I think part of the issue is when GPS connected it would quickly knock me out from data but on reconnect it would try the standard ATT APN versus the mvno I am using.
Probably won't help for everyone but that was my solution and it has worked on various ROMs I have tried (Blur, CM7, CM9).
That's a solid observation mastermind.
I would to add that the evening before I started seeing the issue, I enabled tethering on my cm7 the (ba2tf). Pretty much the next day I started seeing the issue.
Perhaps something got screwed up in the APN settings when I tethered. Up until then I hadn't seen the issue.
Sent from my MB860 using XDA App
I don't really have a clue why these things started happening, but they have, and they're very annoying.. So basically from one night to the next morning, I noticed my phone started doing some..out of the ordinary..things. These are what I've noticed so far:
* Vibrates (twice I think?) upon answer a call, which I think it only used to be once.
* Vibrates every time you take your face away from the sensor and the screen comes back on
* Plays a completely different song for my ringtone, even though I've verified the settings 1000 times.
I've booted into recovery, wiped everything, and did advanced restore to restore each thing, one at a time, to find out where the problem was...it was in data.
Has my lack of checking app permissions finally caught up to me, and now some dev who thinks he's cool is screwing with my phone, or could it be something different?
Any help? I don't wanna completely wipe this thing, but I might end up having to :[
Do you have an active profile?
Profile can override your notification settings.
Sent from my HTC Panache / Darkside CM7.2 using xda premium.
I had the same thing happening, I had the do a full wipe and restore
It was the profile, haha. Thanks a ton for the help. I was messing with profiles earlier, but I didn't realize I'd actually changed it from the default.
if you recently just flashed the rom and havent done major changes.
The simplest way to figure your problem is to do a full data wipe, cache!
and re-flash and then you can see whether if it'll vibrate again!!
My wifi Xoom, using EOS 155, hasnt been able to connect to google's servers in several days. everything else works fine.... browsing, the amazon app store app, irc, etc. But the wifi icon won't turn blue, and when I try to goto the Andriod market it says it can't connect. gmail seems fine... just sent an email to another account and got the reply....
If i go into settings and look under accounts, everything that I have setup to sync says its doing it.... I just can't access the market and the wifi icon is grey.
This happens no matter where I'm at... my house, my friends and family, work, etc. So I know it can't be the network I'm connect to. I haven't made any changes to any settings in a while.... so unless something changed without me doing it....
I've power cycled it numerous times... both rebooting and turning it off completely and then back on again.
Anyone have any ideas what might be the problem???
Thanks
Wifi problem in previous EOS version?
RacerX780 said:
My wifi Xoom, using EOS 155, hasnt been able to connect to google's servers in several days. everything else works fine.... browsing, the amazon app store app, irc, etc. But the wifi icon won't turn blue, and when I try to goto the Andriod market it says it can't connect. gmail seems fine... just sent an email to another account and got the reply....
If i go into settings and look under accounts, everything that I have setup to sync says its doing it.... I just can't access the market and the wifi icon is grey.
This happens no matter where I'm at... my house, my friends and family, work, etc. So I know it can't be the network I'm connect to. I haven't made any changes to any settings in a while.... so unless something changed without me doing it....
I've power cycled it numerous times... both rebooting and turning it off completely and then back on again.
Anyone have any ideas what might be the problem???
Thanks
Click to expand...
Click to collapse
Strange problem... been using EOS for months now and have not had a similar connection issue. Only problem I had connecting to Google site and Application store occurred when I move to Google 2-way authentication and had to setup the security properly.
Did you have this same problem using an earlier version of EOS? When upgrading to EOS 155 did you do a wipe or clean your dalvik and cache? I would try a full system wipe and reflash the ROM. Sometimes it is easier to redo it from scratch then track down a particular issue.
I've never had any issues with any version of EOS, and I've been using them since night 1. And I had 155 installed since it was released... and this issue just happened a week or two ago. So nothing should have changed on my xoom.... unless it was done by some application or something. (And I'm the only user of the device)
I've tried stopping and clearing the cache on the google play app.... which I found the suggestion on another site... but that didn't do anything.
I had this happen before, but it normally just required a rebooting of the tablet, and it would then connect again.
I wish there was something like on windows with the event viewer.... cause I have no idea what the problem is. The error message when I try to connect to the storeis RH-01.
I'm going to install EOS4... but I wanted to wait a day or three until they have a chance to find/correct any early bugs.
I've also been getting error messages about google+... which I never had before. I'll just be doing anything.... browsing, using tweetcaster, playing music, etc and a error msg about google+ pops up.
Could not figure out what the issue was.... I just installed EOS nightly 160.. and everything is back to normal. I don't know if it was a Xoom issue or EOS issue... esp. considering everything was working fine on the nightly I was on for weeks... then all the sudden it stopped.
Reinstalling all my apps...
Simple solution: reflash gapps package.
Lol it's really that simple, I had the same issues as well, but on CM roms.
RacerX780 said:
Could not figure out what the issue was.... I just installed EOS nightly 160.. and everything is back to normal. I don't know if it was a Xoom issue or EOS issue... esp. considering everything was working fine on the nightly I was on for weeks... then all the sudden it stopped.
Reinstalling all my apps...
Click to expand...
Click to collapse
I've had a similar issue.. but resolved it with simply removing/deleting the remembered networks and re connecting them. This could be an artifact of my network setup with both the router and a wireless extender being visible from my location.. and once in a while it seems to confuse the connected systems.
Of course if I learned to leave my working systems alone.. they might not 'break' so often. but it is just too much fun to play:silly:
Chaosgod27 said:
Simple solution: reflash gapps package.
Lol it's really that simple, I had the same issues as well, but on CM roms.
Click to expand...
Click to collapse
Oh well... I should have just tried reflashing everything... but I figured I would move on to 4.2 soon anyway... which I like (4.2) but it's a bit laggy on my xoom compared to 155.
You have to make sure you flash the correct gapps version with the ROMs. 4.2 nightlies require the packages named as follows: gapps-jb-201301##-EOS-XOOM-ONLY.zip be flashed together at the same time. EOS ROM 155 gets flashed with gapps-jb-20120802-eos-signed.zip.
Sent from my Xoom
Bought this phone about 2 weeks ago. Was playing with the settings when i noticed in accessibility there was an option for the camera light to flash when you get a message. Cool right? **** no!
At first everything seemed great, then while sitting in the gf's truck waiting for god knows what, i noticed that the light was on in my pocket, the phone was mad hot, and it killed the battery power by 30%.
Ok, simple solution right? Turn off the option... Later in the day realized the flash was back on on notifications, turned it off again. Long story short, unfroze all the bloat (non rogers bloat anyways) and killed the process (cant remember the name atm) and problem solved. The accessibility option did not re-enable.
Until today... Weeks later, randomly, the phone is flashing away on notifications once again. Turn off the option, reboot, and the option is selected again.
This phone has been problem free, no power issue or fc's. Actually its a great device, but is this stupidity really just me?
Sent from my Nexus 7 using Tapatalk 2
Yeah, had a feeling this was just me...
Sent from my SGH-I337M using Tapatalk 2
Have you tried wiping cache (and dalvik if you have cwm/twrp) in recovery after resetting light notification setting?
xBeerdroiDx said:
Have you tried wiping cache (and dalvik if you have cwm/twrp) in recovery after resetting light notification setting?
Click to expand...
Click to collapse
Stupidly enough no... Considering this being the first device I've left stock the thought hadn't even crossed my mind. (cache wipe, yes ive done, didnt think of dalvic though).
Thanks, will give it a shot.
Sent from my Nexus 7 using Tapatalk 2
Edit: Seems this is a more widespread problem, looks like the consensus is that is has to do with Daylight Savings Time change & the wireless charging Orb. Some others with similar problem:
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
https://code.google.com/p/android/i...=ID Type Status Owner Summary Stars&id=61868
----------------------------------------------------------------------------------------------------------------
(Original Post)
Hey guys. I have a 16GB Nexus 4 that is rooted (SuperSU 1.65), running CWM (6.0.3.6), stock radio, stock kernel, stock 4.3.
I installed the pre-released hangouts v2 that was extracted from the AOSP 4.4. It immediately started causing random apps to crash so I uninstalled it and reinstalled the original version of hangouts. Ever since then though, every morning when I take my phone off the charger (orb) whenever I try to open any google apps (gmail, settings, camera, etc) it will force close that app. Once I reboot the phone everything seems to be working fine until the next morning.
I have tried clearing the cache & dalvik but to no avail.
My last nandroid is from a few months ago so Id really like to have to reload that only as a last resort. Any suggestions?
Thanks.
burnski said:
Hey guys. I have a 16GB Nexus 4 that is rooted (SuperSU 1.65), running CWM (6.0.3.6), stock radio, stock kernel, stock 4.3.
I installed the pre-released hangouts v2 that was extracted from the AOSP 4.4. It immediately started causing random apps to crash so I uninstalled it and reinstalled the original version of hangouts. Ever since then though, every morning when I take my phone off the charger (orb) whenever I try to open any google apps (gmail, settings, camera, etc) it will force close that app. Once I reboot the phone everything seems to be working fine until the next morning.
I have tried clearing the cache & dalvik but to no avail.
My last nandroid is from a few months ago so Id really like to have to reload that only as a last resort. Any suggestions?
Thanks.
Click to expand...
Click to collapse
Try clearing the data of Google Services Framework. If that doesn't work, reflash your Gapps package.
thanks, I will give that a shot.
Mine started doing this but not rooted and didn't install any pre-release apks. The clock even crashes while on the charger when it tries to sound the morning alarm.
A reboot clears it for the day but its back every morning. I reset the phone but no change.
crashes every morning
I think it has something to do with the time change???
crashes every morning.
stock rooted
whole bunch of other people too over at reddit
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
Anyone with any fix for instant Karma?
seems to be fixed. thanks.
burnski said:
seems to be fixed. thanks.
Click to expand...
Click to collapse
which fix worked for you?
burnski said:
seems to be fixed. thanks.
Click to expand...
Click to collapse
I got the same problem, i click on clear cache of Google Service Framework but nothing happens!
Can you reproduce your steps?
whelp, i was wrong. When I woke up this morning, checked my email and it crashed. So I tried to go into settings to clear the framework and the settings crashed too. So I rebooted and its fine again. Any other ideas?
Same problem
I was the one that started that thread on Reddit. I've done a factory reset from the settings menu, cleared the cache data and factory reset via fastboot menu and the issue is still occurring. Phone is completely bone stock, no root or anything.
For me it started Saturday 11/2. I have been using the charging orb just as everyone else. I tried using my wall charger last night and I didn't have an issue. Not sure why out of the blue this could be the cause. I will be trying my orb again tonight to see if it reoccurs.
Mine did not crash this morning, after clearing the google service framework yesterday.... now it might crash tomorrow.
here is my thought into the process... Are we all using the google alarm clock? and after the time change?
4.4 can't get here fast enough
Bobvark said:
Mine did not crash this morning, after clearing the google service framework yesterday.... now it might crash tomorrow.
here is my thought into the process... Are we all using the google alarm clock? and after the time change?
4.4 can't get here fast enough
Click to expand...
Click to collapse
The first time it happens to me i was using the timely app as alarm clock. And it occurred the same day i got the time change. After that i uninstall timely and start using de default clock app.
The same day i got the time change the chrome app was not working either, i had to change my time zone to fix it.
I dont use my phone as an alarm clock, I dont use daydream or anything like that.
Do we all use the orb to charge though? Is that something we all seem to have in common?
Bobvark said:
I think it has something to do with the time change???
crashes every morning.
stock rooted
whole bunch of other people too over at reddit
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
Anyone with any fix for instant Karma?
Click to expand...
Click to collapse
Wow, just went through the reddit thread. seems to be a much bigger issue that originally though.
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
I also found a link to a google group through the reddit thread, so I posted in that to complete the triangle. LOL. Hopefully someone comes up with a solution.
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
Should also mention on here that my wifes charges her Nexus 4 wirelessly with an LG WCP-300. I charge with the Nexus orb. She does not have the problems.
burnski said:
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
I also found a link to a google group through the reddit thread, so I posted in that to complete the triangle. LOL. Hopefully someone comes up with a solution.
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
Click to expand...
Click to collapse
It's not the orb charger. I've been getting the same issue, but I use the N4 cable charger. Timely alarm clock still goes off, but there's a FC message when I go to my phone. Reset fixes it for the day. UK based, CM10.2 M1 + latest goo.im gapps. Also, I have a weird issue where the screen keeps turning back on when I lock it. Just keeps the lock screen permanently on when I'm charging in the morning.
burnski said:
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
Click to expand...
Click to collapse
I dont think the problem is related to the orb or wireless charger. Two people just post about the problem and they are using wired charging.
Everybody had to change the time before the problem start (summer time, DTS, whatever)? i'm suspicious that android is not handling this changes.
Anybody knows if android has a log with the errors? Maybe we can found some tip.
has anyone had the problem and NOT charged overnight?
Its possible that this occus overnight because the DST change usually occurs at 2am so if the glitch happens at 2am most of us dont see it until we get up.
Im going to disable the automatic network time & automatic time zone settings tonight - see what happens tomorrow morning.
burnski said:
Im going to disable the automatic network time & automatic time zone settings tonight - see what happens tomorrow morning.
Click to expand...
Click to collapse
I like this idea, but for me, the issue started the morning before the daylight savings rollback.
I used my wired charger last night and didn't have the issue this AM, but will be trying my orb again tonight.