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.
2016-10-09 07:12 PM
I updated my device and the problem still there, with the same 883 mb. I´m really upset with this. I had to uninstall almost all apps, so that the device can run, but with a very slow performance. I´ll never buy again Sony devices.
2016-10-09 08:58 PM
I still wait an official Sony announcement about this issue. Is that a hardware problem? Did one of the 1 Gb memmory block dead?
2016-10-10 10:13 AM
Hello AraujodeSouza, All
I noticed a number of problems are still remaining after the update.
In particular try removing your SD Card if you have one.. when i inserted my 64Gb sd card, Android reported only 883Mb RAM (AGAIN!!!). I reformated it (on the phone) and now i have the SD Card in and Android sees the 2GB RAM available on the M4.
The update (26.3.B.1.33) isn't solving all issues yet. I'm still having crashes and blue screens.
I hope this helps,
2016-10-10 04:58 PM
Looks like i spoke too soon.. i was re-installing and updating the apps when my M4 blue screened..
It hasn't been up since.. it goes to blue screen righ after the white sony startup screen.
Getting ready for another Xperia Companion Repair!
2016-10-11 06:23 PM
Hi dirik, after performing steps the cell works, but even restarts very often.
what is this about?
How can i fix it ?
2016-10-12 11:08 AM
I'm sorry to hear that you all are experiencing this. It has been forwarded to the developers and they are still investigating the cause behind the missing RAM memory.
I apologize for the time this is taking.
2016-10-12 03:45 PM
Hello and thank you Didrik,
Please do let the developers know that the missing RAM issues isn't systematic with the latest firmware (26.3.B.1.33)
Sometimes it show 883MB sometimes the whole 2GB.
What is really annoying is the frequent blue screens (again not replicable.. not happening when doing something specific).
Thank you for your support,
2016-10-16 08:04 AM
2016-10-17 12:08 AM
Your description of the problem seems very accurate.. something is making a component run very hot (at the top of the phone).
It could still be a software issue, some code not running correctly and making the processor very busy and therefore hot until it crashes.
The problem has been logged for some time now.. but still no solution :/