Share your experience!
Hi.
Since last software update (about a month ago) my Xperia M flashlight doesn't work at all, not in cameramode, not with flashlight apps and neither with xperia diagnostics
Now i'm in vacancy and i decided to resolve the problem.
First of all i tried the Pc companion's firmware repair function, but didn't work.
After it i performed a factory reset with data wipe and another firmware repair without results.
It seems that the problem with the flashlight started just after the update but it's not software correlated.
Anyone have suggestions about possible solutions before i send it to the repair service?
ps: SORRY FOR MY BAD ENGLISH, i'm italian!
Solved! Go to Solution.
Hi!
I'm happy to say that the problem is solved!
It were not an hardware issue, but a really strange NeoReader bug.
After last update i restored the system (my choice) and after that moment i've never used NeoReader app.
Two days ago, i saw a qr code and, after a quick search in the menu, i found the qr-style icon of NeoReader.
Opened the app, i noticed a banned flashlight logo, i touch it and... MAGIC! Flashlight turned on again after months!
So, if there's anyone else with flashlight problems, try to open this app and discover how stupid is this bug.
NB: as i wrote last week, I performed several factory reset, but the problem weren't solved. It's clearly a bug!
This could be a hardware issue, you should contact your local Sony Xperia Care center
Hi!
I'm happy to say that the problem is solved!
It were not an hardware issue, but a really strange NeoReader bug.
After last update i restored the system (my choice) and after that moment i've never used NeoReader app.
Two days ago, i saw a qr code and, after a quick search in the menu, i found the qr-style icon of NeoReader.
Opened the app, i noticed a banned flashlight logo, i touch it and... MAGIC! Flashlight turned on again after months!
So, if there's anyone else with flashlight problems, try to open this app and discover how stupid is this bug.
NB: as i wrote last week, I performed several factory reset, but the problem weren't solved. It's clearly a bug!