Whether you’re a frequent or periodic social media user, you may want to pin your ears back as we have some pretty important news for you. Recently a malicious link has been doing the rounds on Facebook and Twitter, which, when clicked, overloads the default browser on your smartphone, causing it to slow down and generate a lot of heat in the process. It goes without saying that if the bug is not dealt with promptly, your handset will continue to get hotter until it overheats and has no option other than to power down.
Users of the Google Play Music app may have noticed that music cached or stored for offline playback was disappearing from their devices whenever they rebooted their smartphones. Despite some initial attempts to pin this on some DRM-based scheme, Google now appears to have acknowledged this is a bug for users who store their music on microSD cards. Read more
When LG rolled out the Lollipop update for their then flagship smartphone, the LG G3, they staked a claim as being one of the first to get Lollipop out to their devices. We all know manufacturers will roll out an update to a small market to make claims like this. Nevertheless, it is usually a decent sign of a commitment to providing the latest version of Android for a given device even if users have to wait a bit longer for kinks to be worked out and carriers to give their blessing. At the time, as a relatively new owner of an LG G3, I was looking forward to seeing what would happen with my device. Fast forward half a year later and Verizon finally pushed out the Lollipop update. That was the beginning of the transition for my “dream” phone to a nightmare and now signs point to Verizon not doing anything to fix the problems they have wrought. Read more
Verizon has begun rolling out a firmware update for all its carrier-branded models of the Galaxy S6 Edge located in the United States. The upgrade doesn’t bring much in terms of added functionality. Well, in fact, it doesn’t bring anything at all. It merely transports a fix for the extremely irritating auto-rotation bug that many early adopters have been experiencing for a while now.
The release of Lollipop 5.0 is a rather touchy subject for many members of the Android community. Whilst it’s the biggest visual and technical overhaul since Ice Cream Sandwich, it carries a handful of extremely irritating bugs that render some smartphones unusable.
It has generally been viewed as a positive development that the Nexus 6 is available on all major U.S. carriers and a simple swap of a SIM card is all that is needed for users to switch networks if they are in a position to do so. That doesn’t come without some risk though and Sprint customers seem to be suffering the ill effects at the moment as several Nexus 6 owners are having trouble receiving calls. Read more
Lollipop is the latest and greatest version of Android from Google, but like all new software, there are a few bugs. The newest release has already had a few issues (that were promptly fixed) but now it looks like some Nexus devices are being bogged down with a memory leak on Android 5.0.1.
The issue causes the Android system to use up to over 1 GB of RAM instead of the typical 500 MB, so you’ll see tons of apps being force closed and home screen redraws. It’s not a devastating glitch, but it’s enough to be pretty annoying, especially if you like to use tons of apps at once. Read more
Now that Android 5.0 Lollipop is out and public, the bugs will pop up. The newest one deals with an issue between the new flashlight toggle in the quick settings, and the camera. Apparently, if you turn on the flashlight in quick settings and leave it on until it times out, you will not be able to use either the flashlight, or the camera until you reboot. This bug has been spotted on the Nexus 5, but it’s unclear whether it’ll pop up on other devices as well.
This will surely be fixed in the next OTA update, but until then, it’s worth noting to remember to turn off the flashlight when you’re done using it.
Source: Android Police
A new glitch has been identified in the Android Wear platform that results in apps closing unexpectedly. The problem is primarily connected to the accelerometer. Apparently Android Wear attempts to access the accelerometer to update the pedometer step count. In the course of doing this, the system tries to create a new card to display this new step count data. If another application that is also collecting accelerometer data is open in full screen mode, creation of the new step count card will cause a crash of the application.
A temporary workaround for the problem involves ensuring applications do not open in full screen mode. Instead, developers need to configure their apps to create a persistent notification in the context stream and give that notification an action to go full screen.
An update to Android Wear to stop this particular problem, and perhaps others that may involve sensors being accessed by more than one application at a time, will likely be developed and pushed out soon.
According to Google, a recent Gmail bug which affected the iOS app, the offline version of Gmail, and mobile browsers may have resulted in users accidentally spam-marking or even deleting the wrong emails.
The bug was in effect between the 15th and 22nd of January, and Google says that users should check their spam and trash folders for emails that they may have accidentally put there.