Community

_Oggy_1

Hi there,

Yesterday I had my Z5c updated to Android 6.0 and after that, today I had some freezing issues with the Radio FM application.

2 or 3 times when I tried to minimize the application (after I changed the FM station) I got a frozen gray screen. I tried to closed the app, it appeared as closed, but radio was still working (!). After about 1 minute I got the message: "FM radio isn't responding. Do you want to close it?" I tried yes, but still didn't close! So I made a restart.

Then I tried to go to: settings/apps/FM radio / Clear Data & Clear Cache

Since then, it seems to behave normally. Any ideas to avoid similar future issues??

Really appreciate your help

Thanks in advance

Bhonder

I just did a complete install via bridge for Mac, with repair soon after, of latest marshmallow and radio fm works fine.

There is just a quirk in the interaction between radio fm and trackid app but I am going to open a thread.

Bhonder

It is happening to me too.
With Bluetooth active, I started the FM radio app. The first time the phone freezeed but i have been able to stop the app with the multitasking tab.

The second time i've started the radio app, phone roboted all by itself.

the culprit is the interaction between bluetooth and FM receiver.

@Rikard: could we organize so I can send you a system dump?

_Oggy_1

Still have the same FM Radio freezing issues, after the last yesterday system update....

ro760707

I have same issue!!!!!

Bhonder

I could send a dump if Rikard gives me the go but, up to now, I got no response.

tjmkrk

It seems the workaround is to disable bluetooth and wifi. At least it hadnt hung last three times I was using FM radio app.

Bhonder

In my case disabling Bluetooth is enough but it is a lame workaround because I need bluetooth (or wifi in your case) while listening the radio.

I spent a lot of money to have all the functions offered by this device, and not only to get some of them. It's like to buy a car, discover you don't have one of the wheels, and found out that the dealer is not merely interested because he already got the money.

I already wrote to the unuseful Italian support and I disn't get a proper reply. This forum is a user forum so it officially can't be of any help. I would like to help to solve this problem but if developer are not interested, I can't.

Bah... Next phone will not be from Sony. Probably it will not be even android.

RobertoDS

Hi Bhonder

As I told you, u've got surely something broken into your phone, an HW problem for sure because SW is the same for everyone of us.

I can't replicate it too now I am sorry

I am encountering in another problem

When I am listening radio, and I try to click on Track ID on three dots on the upper right, TrackID opens but it doesn't match anything, as with the silence

Something wrong is this one

roerisigold

I found why the FM radio stops working do 20-30 minutes, the problem is the bluetooth when it is turned on the FM radio, once you turn off the bluetooth FM radio does not hang. So there is a conflict between FM radio and Bluetooth. IS IT NOT POSSIBLE !!!!!!

Bhonder

It may be a faulty production batch or one with a different supplier chip not fully aligned with firmware. I work in IT since 24 years and I have seen this happen, from time to time. I even seen an online transaction program fail during odd microseconds because the cryptographic engine.

My Z5c and roerisgold's one production date is 15w38. Maybe this common factor could be examined.

I sent two phones (during the years) to the local repairing service (which is a multibrand one) and both came back with the same issue or worse. Before ruining my only, and more pricey than previous ones, actual device I would like where the problem is. I can't get info from local service (Question.it@support.sonymobile.it) because they tell me to send it to repair with cut/paste reply. I can't get info from this forum, because is a user forum.

The problem affect more than one device: if I'd have an address to send the log to be examined, maybe a solution could be found for more than one terminal. Even by exchanging the faulty component or the entire device, if needed. But knowing it for sure, not by an trial and error method with 600€ of our own.

I could even read the log by myself if someone would give me some hints to what to look for: it is huge and I am quite sure that developers have some tool to debug it.

It would be nice for Sony to have some bugzilla home page to gather information rather than a cut&paste reply mail address.