Anyone else using Skype and seeing this?
I have a unlocked, none carrier branded Samsung Galaxy Nexus running 4.1.1. Recently when returning to the Skype app home screen from either a message chat, voice or video call my screen started looking like the attachment. There is a ghosting affect going on but it doesn't happen all the time. I also have a few issues where the program just stops working and needs to be restarted and I’m forced to reenter my password. After the restart the app does run normally for a while until I try to chat or make a call. This issue did not happen when I first got the phone running 4.0.4 but has started only a few days ago. It did not start right away when I updated my phone to the 4.1.1 about a week ago. I haven’t installed any programs since this started either, only a few updates for maps, locations services, etc.
I know that this must be an issue with this phone and android build as I do not have this problem on any of my other Android devices running various versions of Android.
No I haven't tried uninstalling and reinstalling the app yet but will if the problem persists.
Hi all,
Posting this here because it's the device in question and no one answered over at general Android Q&A and Reddit hasn't been able to help.
Long time since I posted here but I'm at the limit of what I can effectively do so I'm looking for some help here and I believe this is a problem with the OS itself and how it handles shared settings and even with the Maps application, rather than being device specific.
First, specs:
Samsung Galaxy Nexus (UK HSDPA+) running Jelly Bean 4.1.1, completely stock and unrooted.
Asus Nexus 7 (also UK, though I'm not sure this makes a difference as the N7 has no GSM radio), Jelly Bean 4.1.1, completely stock and unrooted.
All apps are the latest versions.
Background: This problem has only existed as long as I have had the Nexus 7 in addition to the Galaxy Nexus. I'm 90% sure that the issue relates to the fact that I have location reporting enabled on the GNex and NOT on the Nexus 7. I'm signed into both devices with the same Google account. Occasionally one or the other will pick up the opposite one's settings with regards to location sharing, a PITA.
The problem: Ridiculous amounts of wakelocks caused by the Play Store, Maps and the Launcher. As you can see here (BetterBatteryStats pic included). imgur . com/ a/yz83J (I can't post the hyperlink because I've not posted 10 times yet.) This only seems to cause a problem on the Galaxy Nexus. I haven't noticed wakelocks or battery drain on the Nexus 7.
This absolutely drains my battery. If I kill off Play Store and Maps and clear all cache data then the wakelocks stop for a while.
Two days ago I was forced to uninstall all updates to Maps and return it to the default version and update it again as killing the process or even rebooting the phone failed to stop the wakelocks. This didn't stop the wakelocks but out of curiosity I just told the device to completely stop updating my location on it's own. This has completely stopped the wakelocks and the resulting power drain..
The catch: I'd really rather not have to leave location updating off to resolve this. It's only been happening since I got the Nexus 7 and I'm trying to get that to NOT report my location and the GNex to report. The reason I have it turned off is that I have it on train WiFi a lot, which displays my location as wherever the connection terminates. E.g. for an entire journey from London to the north, my history for that day shows that I travelled the distance between every point on the route that my phone reported and London Euston station where the Nexus 7 was connected, in about 1 second. This led to my location history being an utter mess!
The question: Any ideas on getting this working as intended? If I can provide any more data let me know. I've already run an ADB output of my alarm manager stats and it's showing the same as the BetterBatteryStats info.
The apps will constantly try to refresh maybe because it's trying to receive data like notifications.
You can try JuiceDefender or Greenpower or apps like that in order to limit how often a certain app syncs. Some ROMs also have such a feature if i'm not wrong.
If all else fails try a factory reset and see if the problem is fixed. Did you do a full wipe before changing to jb from ics? Maybe that could cause problems.
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
JamesInsights said:
The apps will constantly try to refresh maybe because it's trying to receive data like notifications.
You can try JuiceDefender or Greenpower or apps like that in order to limit how often a certain app syncs. Some ROMs also have such a feature if i'm not wrong.
If all else fails try a factory reset and see if the problem is fixed. Did you do a full wipe before changing to jb from ics? Maybe that could cause problems.
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Click to expand...
Click to collapse
Thanks for the reply.
No I did not do a full wipe because the update to JB was delivered OTA when Google released them, these devices are completely stock. I believe the issue is that the GNex is attempting to update the location, the Google account is reading the Nexus 7 setting of not updating the location, then the response is bouncing back to the GNex, which insists it does need to update the location, etc.
As I said, I've temporarily solved this by stopping the phone updating it's location at all, however this isn't the best solution and since I've found the cause, I'm not convinced a factory reset or even reflashing the stock ROM will help. I'm pretty sure this is a deep OS issue, using the same Google account across 2 devices is great, until you want them to have different settings.
I'm probably gonna report it on code.google.com, but I very much doubt I'll get a response.
I have been experiencing sporadic login failures error messages both in my Gnex and Nexus 7, the message reads that there was a problem communicating with google servers, a couple of friends also have experienced the same. I have not identified when or what is triggering the error.
Is anyone else having this problems? any information?
regards
I've been gotten the notification a few times today. It doesn't show which specific g-app that may be causing it, however clicking the notification appears to alleviate it.
Sent from my Galaxy Nexus using xda premium
Chrome on my laptop just asked me to login again but it's the only time it's happened
Its happened to me 3 times today and it happened to my gfs one s yesterday a few times.
Sent from my Galaxy Nexus using xda premium
Yes, I also experienced couple of Google login issues since my GNex got the OTA update for 4.2 yesterday.
I've received numerous notifications on both my GNex and N7 today. If I recall, I actually saw the first one last night, on my GNex. But mine don't appear to affect functionality at all, even if i don't clear the notification.
I will add that in the previous two days, my GNex was having problems staying connected to the Google servers (gray signal bars) and that *did* kill sync, but didn't have an accompanying notification. It even killed my data connection altogether a few times, which required either an airplane mode toggle or a reboot. That hasn't happened today though.
Phew! Can't wait for 4.2.1.
I am having this issue as well.
I believe that it started yesterday. But I have been mainly noticing it today.
Anyone know the cause?
I haven't received the upgrade to 4.2 yet
Not running a Nexus (GS2 with SuperNexus ROM, though.... ), but I've been getting this as well. Saw a post from awhile back about logging in and out of Google+ to fix it, but that didn't take. Tried disconnecting and reconnecting my account, but also no bueno. Interestingly, I haven't seen this issue on my N7, today.
Got it a couple hours ago, I think I just clicked the notification and I haven't got it again. The last time this happened was the Google Now outage a month back.
Google must be making some changes to something....................
Having the issue here on my Galaxy Note (1), and but not my Nexus 10 or Sony Google Tv.
Sent from my SAMSUNG-SGH-I717 using xda premium
Appearing on both Nexus devices (toro 4.1.1) and Xoom on 4.1.2. Happened several times to me today, only once on my wife's Nexus. Maybe they're fixing the package notification in Google Now before black Friday shopping begins.
Sent from my Xoom using xda premium
Same here. I just switched from stock to CM 10 around that time so I was figuring it was residual from flashing over. I'll take that over the constant prompt for the 4.2 OTA I was stuck with though
Sent from my Galaxy Nexus using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I'm also having this problem on my Galaxy Nexus. I first noticed it Tuesday night, it happened twice yesterday and once today so far.
I've been getting it on my 4.1 Nexus for the past few days. Calendar shows a sync error on occasion.
I have been getting it as well since yesterday. I got it early today too. My girlfriend has a G2X and she got it as well. It must be something going on with Google servers again-I remember having that kind of issue a couple of months ago-it got fixed within 2-3 days.
"me too"
This has been happening to me to, seems to have started a few days ago- happens multiple times a day. Annoying as hell, BUT, doesn't seem to affect phone functionality, at least as far as I have noticed.
Stock Galaxy Nexus, stock OTA Jelly Bean 4.2. No rooting or other funniness.
For now, I'm going to give it a week and hope Google becomes aware of it and fixes this.
I saw one post in another forum that deleting the account on the phone fixes it, but I can't confirm that. I also don't want to lose all my text messages, so only going to do this as a last resort.
One time a few hours ago, all OK now.
not sure why it happened (phone not connected to usb), but i've also been noticing some disconnecting and reconnecting since yesterday, and one time play store "could not find a data connection". i'm sure its temporary.
Ive looked everywhere for a solution but cant seem to find one. My N7, currently running CM11, will randomly reboot for seemingly no reason. Sometimes i can go a day or two and nothing but just when i get comfortable, BLAM! Im not particularly worried just frustrated. I dont know what to do and I have read that its sort of common whether stock or custom(ROM). Im debating on trying to revert to stock because i cant seem to remember having this problem before CM, but i really cant be sure. Id rather not revert to stock if im just gonna have this issue but if it seems to work for others then id just go stock. Anyway I guess im saying that I need some advice here on what others experienced or think. Has reverting to stock worked for anyone else? Any other advice/insight would be greatly appreaciated!
-Thanks
The fix is coming, when Google releases Android 4.4.3, by the end of the month.. Sit tight
--=={BSnapp} ==--
My stock N7 reboots randomly from time to time. It might go a week or more then reboot twice in one day. No apparent pattern to it.
Sent from my BN Nook HD using XDA Free mobile app
I am experiencing precisely the same issue described in the OP. So I am also pretty interested in knowing if there's a fix.
@BSnapp, how can you be so sure of that upcoming fix? Is there a known issue with 4.4.2 for the N7 that was resolved for the next version? Any sources worth mentioning?
Thanks.
It's all over the Android news sites that Google is including a fix for the random reboot, plus several other fixes.. Just Google Android 4.4.3 update, and you will find the answers you seek...
--=={BSnapp} ==--
Since the Marshmallow upgrade my wife's US Cellular Tab S 10.5 has locked up several times. It never did this under Lollipop. Although it's good to be closest to the most recent release, I'm disappointed in this development. Anyone else seeing this?
This may be Chrome related. Every time it has frozen, we've been using Chrome. If we let it sit for a while, it "unfreezes."
Not only Chrome. Froze today reading thr NY Times in its app.