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

HTc One M9


We all are waiting for the HTC One M9 to hit the markets worldwide which is scheduled on March,16th. Sadly, we might need to wait a little while longer because HTC missed the deadline. According to various reports, the Taiwanese manufacturer has delayed the release because of an urgent software update that the handset must receive before launch.

 

Whether or not this is true, is hard to tell, but it is a fact that the company has missed its March,16th home market shipping date. Some impatient customers, who have already payed for the flagship are reporting that the official statement they are receiving are for a delay of a couple of days to a couple of weeks.

 

VIA



Samsung Electronics is about to unveil another flagship smartphone from the S lineup called Samsung Galaxy S7. A few months ago, there were rumours around Snapdragon 820 when Qualcomm was about to reveal the complete specification of the chipset and it was said there was overheating problem. With this, Qualcomm quickly discarded these rumors and assured that the Snapdragon 820's heating is under the permissible limit..

 

But it seems that might not be the case. As per new rumors, it has been shown that Samsung is actually looking for internal heat pipe suppliers for their 2016 flagship smartphone. Heat pipes in smartphones have become a common part. We have also seen other OEMs like Sony use heat pipes in their Xperia Z5 variants, so the it shouldn't come as surprise in case Samsung also decides to take the same route.

 

It can't be said for sure if this is more of a preventive measure to save the phone from any kind of heating problem or result of using the Snapdragon 820 (as it facing heating issues). We'd like to consider that whatever issue the Snapdragon 810 had, Qualcomm has resolved that in the new 820 variant. But in order to get the complete picture we need wait till the release of the device.

 

Source

 



Multiple reports surfaced on the internet earlier about the Galaxy Note 8 refusing to turn on once the battery reaches 0% and the phone is automatically switched off and now Samsung has decided to accept some responsibility for this and admit that there is indeed an issue with the battery of certain Galaxy Note 8 devices. It is to be kept in mind that a few Galaxy S8+ users are also complaining about a similar problem and there is no reason to believe that they are wrong either. While this issue isn't as dangerous as last year's Note 7 disaster, it puts yet another blemish on Samsung's ability to supply their users with capable batteries. The good news is that so far, most reports suggest that Samsung has replaced the faulty devices.


It seems at this point that issues are mostly limited to the Qualcomm Snapdragon variants only, although that's not a fact which has been set in stone. Even though they let out a statement earlier which vaguely delivers the message that they might be considering taking responsibility for the bricked phones, clarifications regarding what exactly is the problem has not yet been provided by the OEM.


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)


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


Note 4 Lollipop

 

We already saw the Hands-on video of the Galaxy Note Edge and Galaxy Note 4 Lollipop 5.0.1 updateHowever, Samsung didn't release the update yet on any region, even the old Galaxy Note 3 got its official Lollipop update in some regions...

 

Where's the Galaxy Note 4 Lollipop Update ?

 

Well, it turns out that Samsung delayed the Galaxy Note 4 Lollipop 5.0.1 update due to compatibility issues with Samsung Gear VR. Samsung needs to make sure that the Gear VR will work well on the Note 4 Lollipop ROM, so far the Galaxy Note 4 ROM is still in the hands of Oculus VR who are tweaking the kernel to ensure its compatibility with the Samsung Gear VR.

 

Samsung Gear VR is Samsung's current take on virtual reality headset based on the popular Oculus Rift. While compatibility issues might explain the delay the question still stands why this can't be achieved in a later update. It looks like Gear VR is very important to Samsung that it delayed the full Lollipop roll-out for it.

 

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]


Description

youmobileorg
Posts: 4141





© 2015 YouMobile Inc. All rights reserved