YouMobile on Facebook YouMobile on Google+ Follow YouMobile on Twitter
Tags - fix


Even though it was a disaster when a few of the Samsung Galaxy Note 7 smartphones started to catch fire all over the world, many have applauded the Korean electronics giant on their decision to recall all the 2.5 million smartphones that they had shipped. However, as is often the case in such scenarios, some of the customers have decided to disregard the warnings issued by flight authorities, tech-experts and the manufacturer themselves. While it is questionable what would prompt such negligence, in spite of the free refund/replacement scheme employed by Samsung, many customers are of the opinion that the incidents are far too low and in between to be concerned about it.


Nevertheless, Samsung has decided to limit the maximum charging point to 60% of the Note 7's full battery capacity in an OTA update that will be released shortly in South Korea. This news was confirmed when the Seoul Shinmun (a popular South Korean newspaper) published the message from Samsung on its front page. This is a temporary fix until all the customers turn in their smartphones for free replacements, which should begin by the end of the month. According to Yonhap News Agency, the same update could also make its way to all other nations as well, but we will have to wait and see. In the meanwhile, we advise you to stop using the Galaxy Note 7 and get it replaced/refunded as soon as possible. Although some have pointed out that the chances of your Note 7 exploding are similar to that of winning the lottery, this is one lottery that you may not want to win!


Saikat Kar (tech-enthusiast)



One of the basic functions of any phone by its very essence is to enable the user to take and make calls, but unfortunately, some of the Galaxy S9 and S9+ units do not seem up to be up to the job. Apparently, a lot of users are complaining about their units dropping calls or the phone muting the call automatically. This issue has been confirmed beyond doubt and Samsung is working on a fix as you read this. It should be noted that this is an old problem now and Samsung has already sent out a patch or two to fix the problem, but so far, they have proven to be ineffective or marginally effective in improving the situation.


Personally, I can vouch for the fact that my old Galaxy S8 also experiences a strange calling related issue. At times, I can see a full signal bar but all call and SMS facilities simply go out of order. I had missed an entire hour's worth of calls last week, without even realizing that it was happening. It was only when I restarted the phone that the messages and calls started to come in again. I guess Samsung needs to improve on the basic phone functionalities of their flagship devices soon.


Saikat Kar (tech-enthusiast)





When it comes to security of the Nexus devices. Google is practically living a nightmare. The most recent bug in that Google needs to fix is consumer-facing and exploitable without any geeky tricks. It seems the Nexus devices are vulnerable to an exploit that lets users bypass factory reset protection.


For the uninitiated - factory reset protection has been kept in place to help you to keep your device password protected in case someone tries to reset the factory settings. It is supposed to render the phone practically unusable without the password, but a work around has emerged that does the job by pressing series of buttons. Check out the video given below to see the exploit:


Google pushed a security patch that covered the fix for this issue, but RootJunky - the first person to report the bug - has come up with yet another video that shows vulnerability of the device in spite of the patch released in January.


Although it has become more difficult to exploit the loophole, it is still achievable.This essentially sends out a message that the development and quality testing are done thoroughly. Google might take more time to provide fix for this bug, as they would like to get it right in the next release.



 



If you own a device that got updated to Android 6.0, you might have noticed something strange about the system clock on your phone. Many complaints have been filed in the Google Code site about the clock running slow after updating to the Android 6.0. This can make the alarms and event reminders set from your calendar absolutely useless.


We're not discussing about a 30 second difference, or even five minutes. As per Nexus users posting on the Issue Tracker (Issue # 189789), the time mismatch can go up to 30 minutes. Some have managed to fix the issue by turning on Airplane mode and then reverting to normal mode again. But this solution won't apply to all the devices.


Rebooting the smartphone is a fix that has resolved the issue for many, but others have reported that switching to a 3G network setting from 4G will get the phone's clock synced with the network.


Updating to Android 6.0.1, will fix the system clock and you won't be late for work anymore or miss appointments. So the modus operandi is to keep trying one of the workarounds until Android 6.0.1 is pushed to your device.


Source


JB

 

There have been recent concerns over the security issues in the rather outdated WebView mode in Android Jelly Bean (v4.1 - v4.2 - v4.3). Due to its outdated nature, it is facing security issues, which would otherwise be a non-issue on newer versions of Android.

 

Google has responded to these concerns by basically saying they won't be updating the WebView in Jelly Bean. But while that may not be what people have been expecting, Google does have a reasonable explanation for it.

 

jelly bean

 

Starting KitKat onwards, the WebView component, that is the browser that you see within apps that open links in their own built-in browser instead of sending you to your default browser, runs on the newer Chromium engine, which is the same as in the Google Chrome browser. However, Jelly Bean and older versions of Android use WebKit engine, which is pretty vast and being updated by hundreds of developers since it's open source. So, it is not easy or secure to update a part of that engine for Google.

 

Secondly, even if Google does release an update, it is entirely in the hands of the OEMs to deliver the update. For phones that are still running Jelly Bean when there have been two major updates of Android since, it's unlikely that OEMs are going to release any updates for them, meaning the security update may never reach the users.

 

Source


Google Search 4.2


Google Search App for Android has been update to version 4.2.16.87075793, bringing several new features and improvements, including a much need Android Wear bug fixes... many users reported that the previous version (4.1) had many issues with Android Wear devices.

 

Google Search

 

The updated App now offers a new "Now cards" settings option that allows you to manage your card history, delete card preferences, manage notifications for card updates and show/hide cards. You can access this option by pulling out the slide-out navigation menu and heading to settings.

 

Search

 

In addition, the search giant has also tweaked the settings for lock screen "OK Google" access there's now a "Personal results" setting which you can enable/disable to control the access to your personal information while using the lock screen "OK Google" feature. You can Download the Google Search v4.2 App for devices running Android (4.1+).

 

search

 

Google Search 4.2 [APK]

 

Google Search 4.2 [Play]

 



As per @Ricciolo1, a well-known leakster, Sony is aiming to upgrade its Xperia Z5 series to Android 6.90 Marshmallow in January and for older models the same update is planned shortly after the Z5.


Marshmallow comes with a bunch of improvements, optimizations and features that'd be very useful to any smartphone. Battery life improvements and performance boosts are the most noticeable changes to the software. But this is a rumour; nothing is fixed and there is no solid timeline. So take this with a pinch of salt.


Sony has been really good with getting the older devices updated. The Xperia Z (not the Z1) was upgraded all the way to Lollipop 5.1.1, although it had an older Snapdragon S4 Pro processor. Just like many flagships devices that were launched last year (apart from the One A9), the Sony Xperia Z5 is one of the many still operating on Lollipop.


It would be quite interesting to see what Sony has planned for their version of Marshmallow. We know that Sony has been working on a near-stock Android build for sometime and by using the Marshmallow's Doze feature in conjunction with their own proprietary battery saving software, the battery life in many devices can be enhanced.


Source


Android 5.1

 

You may remember the memory leak bug that was reported on Android 5.0.1 Lollipop when it was released. Unfortunately, the same Bug still exists in the Google's latest version Android 5.1 Lollipop and it affects the system performance in the long-run. Google promised a final fix for this issue.

 

Issue No. 159738, "Memory leak still present on Android 5.1" was reported at the AOSP issue tracker. Last Friday, Google closed the bug and said that it has internally fixed the issue and plans to include it in the upcoming release version, Which most likely would be Android 5.1.1 Lollipop.

 

Android 5.1.1 lollipop bug


The complaints are beginning to read the same. Apps, especially Google+, restart on their own. Some active apps disappear in the middle of using them, and free RAM drops in hours to about 750MB-800MB from 1.1GB-1.3GB. Most of the people who sent in a complaint appear to be using the Nexus 5, although other Nexus devices have been cited. Some complaints said that opening apps would increase the amount of RAM in use, but closing apps would not reduce that figure.

 

Android version 5.1.1 shouldn't take long until we see it rolling-out to Nexus devices and tablets as an OTA package or a Factory Image.

 

Source [AOSP]


Lollipop-51-youmobile

 

We already reported before about the Memory Leak bug in the Android 5.1 Lollipop and that Google promised to fix once and for all in the Android 5.1.1 Lollipop. Today, Android SDK Manager added Android 5.1.1 build, which confirms that Google is getting ready to release the update.

 

Android Developers and users are eagerly awaited the 5.1.1 release to fix this bug. Google has acknowledged that the leak existed, but also posted that the necessary repairs had been made. Google did not have everything ready to go for Android 5.1, which is why the Android 5.1.1 update is so important to many Android users. We might also see the addition of a VPN (Virtual Private Network) which would allow users to tap into a Wi-Fi network to communicate over a Google owned VPN.

 

5.1.1 sdk

 

It's only a matter of days until we see some Nexus Factory images for the 5.1.1 build available for download. Over-the-air updates to 5.1.1 will also come as early as next month. Stay tuned!

 

VIA


Galaxy S5 Android 5.0.2 Lollipop update

 

Samsung already started rolling-out the official Android 5.0 Lollipop update to the Galaxy S5 users back in February making it the first Galaxy device to get the Lollipop update. Since the update was released, it faced many delays caused by various bugs being reported by the users who got it first, still there is some users complaining about the update stability on their Galaxy S5 devices.


SamsungUK admits that there are issues with the Galaxy S5 update, via its official Twitter account, and confirmed that Samsung's Engineers are sending-out micro updates that contains a fix for these bugs. It's not yet clear if the micro update is Android Build 5.0.1 or even 5.0.2 or just a hot fix update that will keep the same 5.0 build on the device after installing.

 

 

 

 

The Galaxy S5 users should and wait see the upcoming software update for their devices, it may solve all their problems once and for all. Stay tuned!

 

VIA [Twitter]



These improvements had been rolling out in South Korea for a while now but finally it's here in the US. AT&T has started to roll out a single huge update of 480MB to the Galaxy S8 and Galaxy S8+. It will address the color calibration settings on the two devices so that the users can set the RGB calibration to their liking and get rid of any unwanted hues. Also included is an improvement to the Bixby hardware button which has something to do with the timing of short-pressing the button. Other improvements include fix for the infamous DQA pop-up error and fix for a 5G access point Wi-Fi compatibility issue.


Firmware version G950USQU1AQDE and G955USQU1AQDE are making their way onto the Galaxy S8 and Galaxy S8+ respectively. The only difference in-between the two being the size (the S8 may have a smaller file size). It's good to see the update make its way into the US, but what we would have also liked to see is some of the Bixby functionalities which are currently available for South Korean users, make their way onto other regions as well.


Saikat Kar (tech-enthusiast)


Head over to our firmware section to find all the latest available updates for your Samsung smartphones and tablets.



The Galaxy S8 has been an iconic smartphone for Samsung due to multiple reasons and those reasons are not only limited to the design language. The S8 marked Samsung's first foray into flagship territory after the infamous Note 7 disaster and a lot rested on its success. It did turn out to be a success as reports are coming in now to indicate that the S8 might be selling five times faster than the S7! Then there's of course the design language with its huge yet surprisingly manageable 18.5:9 bezel-less display and removal of the Home button to make it possible. However, it has not been all good either.


The Galaxy S8 has been plagued with criticisms for its smallish battery size and weirdly placed fingerprint scanner to begin with and then it was followed up by a series of problems like the red tint issue, the restarting problems and a whole bunch of other small yet disruptive bugs in the software. Even the famed iris scanner turned out to be quite easy to fool and Bixby was half-baked (to say the least) at release.


The good news is that Samsung has eventually taken care of most of those problems and will continue to take care of them with software updates as and if more pop up. The latest of those updates solved an issue with the S8/S8 Plus where the smartphones restarted themselves while playing audio via Bluetooth. While it can be argued that the S8 seems rushed and you would not be wrong to think so given the circumstances, it is also true that any more delay would have surely hurt the sales and it would have been very hard for Samsung to stay on schedule for the upcoming Galaxy Note 8.


Saikat Kar (tech-enthusiast)


Head over to our firmware section to find all the latest available updates for your Samsung smartphones and tablets.


Description

youmobileorg
Posts: 4141





© 2015 YouMobile Inc. All rights reserved