account arrowhead-down arrowhead-up mobile-menu search sm-bold-x x-skinny-rounded x-skinny arrowhead-right social-facebook social-googleplus social-instagram social-linkedin social-pinterest social-qzone social-renren social-tencent social-twitter social-vkontakt social-weibo social-youku social-youtube

Please help us improve our website

Take our customer survey to evaluate your visit.

It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.

cancel
Showing results for 
Search instead for 
Did you mean: 
Tips & Tricks

Curious about what is happening at IFA?
Read more and discuss the press conference here.

Update 48.1.A.2.73 has issues.

One time poster
Message 1 of 20
5,896 Views
Message 1 of 20

Update 48.1.A.2.73 has issues.

My Xperia xa1 ultra just updated to 48.1.A.2.73 as of Nov 16 2018 and is having serious issues. The top 1/4 of the screen has touch desease, the phone will go through spastic fits of rolling screens, picking apps at random then closing them down, won't respond to powering down, won't powerdow after getting to choose it...........!!!!!!!!

Since the last update my Bluetooth has stopped sending meta data in streaming music, then stopped streaming music. WiFi got slower on download, the phone is slower, the battery cant go as long on a charge.........

19 REPLIES 19
Learner
Message 2 of 20
5,857 Views
Message 2 of 20

Re: Update 48.1.A.2.73 has issues.

Try factory reset and solved your problems

Learner
Message 3 of 20
5,834 Views
Message 3 of 20

Re: Update 48.1.A.2.73 has issues.

Is there any one else having same problem 

One time poster
Message 4 of 20
5,686 Views
Message 4 of 20

Re: Update 48.1.A.2.73 has issues.

Im so sorry for you problem, i have a Xperia XA1 Ultra too,. But the message update Just pops up today,. So you dont recomend the updating,.?

The update Is to change to Android Pie? Thank you!! 

Learner
Message 5 of 20
5,249 Views
Message 5 of 20

Re: Update 48.1.A.2.73 has issues.

After update got problem charging very very slow and half day battery become 4x% only , before have 7x-80% ……


@BonesDig1 wrote:

My Xperia xa1 ultra just updated to 48.1.A.2.73 as of Nov 16 2018 and is having serious issues. The top 1/4 of the screen has touch desease, the phone will go through spastic fits of rolling screens, picking apps at random then closing them down, won't respond to powering down, won't powerdow after getting to choose it...........!!!!!!!!

Since the last update my Bluetooth has stopped sending meta data in streaming music, then stopped streaming music. WiFi got slower on download, the phone is slower, the battery cant go as long on a charge.........


 

Visitor
Message 6 of 20
5,086 Views
Message 6 of 20

Re: Update 48.1.A.2.73 has issues.

Does the factory reset clear all my info? 

Rookie
Message 7 of 20
4,562 Views
Message 7 of 20

Re: Update 48.1.A.2.73 has issues.

Yup, this update just ruined the phone.  Slow charging, 50%battery to 0% in 2 seconds of use. 

It's almost like what Apple has done make software to slow or ruin the device so people will spend money to upgrade. 

Shame on Sony! 

Rookie
Message 8 of 20
4,545 Views
Message 8 of 20

Re: Update 48.1.A.2.73 has issues.

Update is flawed, but after installing Xperia companion on Pc then to repair software seemed to fix all issues..

Its a pain because the phone gets wiped. 

 

Perform a backup first to save contacts and files. 

In google play go to history and you will find all your previously installed apps.  Makes it easy to reinstall. 

The version on companion says 48.1.a.2.73-r2b. 

Rookie
Message 9 of 20
4,511 Views
Message 9 of 20

Re: Update 48.1.A.2.73 has issues.

Update... Seems the software update ruined the memory of the battery percentage.  Symptoms of overcharging now damaged the battery and now will not hold a charge.

The software repair in pc companion did not fix the problem.

One time poster
Message 10 of 20
3,086 Views
Message 10 of 20

Re: Update 48.1.A.2.73 has issues.

I have exact problems decribed. Assumed it was a hardware problem but maybe not afyer what you said.