Hello!
I recently switched to the m4 from my trusty LG OG, an it is perfect except for one thing... it doesn't ring.
I have tried all Sony-solutions, including PC software repair, etc... but no joy. My wife also has an M4 and has the same problem.
It is worked-around by using a 3rd party lockscreen (I use Hi-Locker), which is awesome.. but not ideal due to security problems, most notably Android Pay.
My question?
Can I replace the lockscreen at the ROM level? Can I replace the basic function with maybe a lockscreen from the Z5?
Unless someone knows how to fix this
I have never compiled my own rom, but I have a reasonable level of tech-savvy. I can flash ROMS and do work in Linux.
I have rooted and unlocked my bootloader, and I am using Stock Sony ROM
I have the latest firmware
Kernel 3.10.49
build 26.1.A.2.99
I have NOT tried using an old firmware- or an alternate ROM. I probably will, but my wife doesn't love the idea for her. Thus, I would like to work out a precision fix.
My thoughts?
Idea 1. find where the stock lockscreen/security module lives.. and try and replace with something from a different phone.
Possible?
Thank you for reading.. I know some other people have these problems, as I read them in threads here.. but I didn't find much in the way of fixing.
just for reference- THIS is the problem.
just for reference- THIS is the problem.
Mustang243 said:
My phone doesn't ring when it 's locked. If phone is unlocked ringtone rings and vibrates. When it's locked no sound or vibrate. Whatsapp messages vibrate but they have no notification sound. I have checked all the settings, volume is up. Last resort is factory reset but i'm not there yet. I don't wanna lose all my settings.
E: Okay I used Sony PC Companion and used the Fix phone/tablet -thing and it downloaded the firmware and installed it so I think it reset my phone. Still my phone doesn't ring if its locked. If I press the power button when someone is calling to me, I can see the lockscreen notification on the screen but it doesn't ring or vibrate. FFS. Any ideas guys?
E2: I guess I find a solutions. Or a temporary solution. I noticed that if I disabled the screen lock, my phone would ring and vibrate normally. So I decided to try and download "Next" lockscreen app. Guess what. When I use it, my phone works perfectly. I don't know why it stopped ringing because there wasn't any new updates from Sony but it's clearly problem in Sony's software.
Click to expand...
Click to collapse
Mustang243 said:
I still have the "silent phone" issue with this update. I have to use third party lock screen app. If I use Sony's lock pattern or pin code and use my gf's phone to call my phone: screen doesn't wake, no ringtone can be heard and no vibration. When I press power-button I can see that someone's trying to call me. Anyone else experiencing this problem? I hope you understand what I tried to say, the issue is kinda hard to explain.
Click to expand...
Click to collapse
Yeah this is a huge problem and we're not the only ones suffering from it. Now I use CM Locker because Next drained my battery. I also noticed that my phone works fine if I boot on safe-mode. Still haven't figured it out which app causes the problem. Gotta wait for the 6.0 update and hope that fixes things.
Same issue with out-of-the box...
Well, have M4 'out of the box' - meaning - no custom software installed, no customized ROM, no custom lock-screen... and well - to make the ring work back I have to restart phone every few days (as soon as realize that it's not working) - oh Sony, what should I say ....
Related
Hey guys, I'm having this issue with my stock Razr Maxx, where the ringtone volume turns down (close to silent) and I don't even know it unless I receive a call and there isn't any noise around (or else I totally miss the call).
I understand this is probably a well known bug, but I would just like to know if there's anything triggering it, so I know how to avoid this. I'm using a bluetooth headset every day, at work, but I haven't figured out a pattern yet, or even if the bluetooth headset is causing this.
Help? Please?
teomor said:
Hey guys, I'm having this issue with my stock Razr Maxx, where the ringtone volume turns down (close to silent) and I don't even know it unless I receive a call and there isn't any noise around (or else I totally miss the call).
I understand this is probably a well known bug, but I would just like to know if there's anything triggering it, so I know how to avoid this. I'm using a bluetooth headset every day, at work, but I haven't figured out a pattern yet, or even if the bluetooth headset is causing this.
Help? Please?
Click to expand...
Click to collapse
Looks like your bluetooth headset may be changing the volume without your consent.
Try to plug it off at least for a day and see if the problem happens
It looks like it wasn't the bluetooth headset.
During the weekend I haven't used it and this morning the volume was all the way down...
I have disabled the 'increasing volume' setting from my alarm and see if that helps, as I realized I always snooze or stop the alarm while it's still barely audible.
=P
I'm used to have three different alarms. I don't like snooze...i prefer to sleep more ten minutes and have a different alarm. Since i'm sleepy when i look the alarm i tend to cancel it instead of snooze also
Some time ago i had a similar problem with my XT910. After taking it to a authorized local service my volume up key wasn't working anymore ; they fixed it somehow.
Why don't you try to install an custom rom or reflash your actual rom ? It would tell us if your problem is hardware or software (if the problem persists with another rom surely its a hardware thing - i don't think kernel is related to this).
I will be flashing the official JB when it comes out, hopefully soon. I've got the "MERetail.en.06" software version now and I understand this is the Middle East version, which will not get the JB OTA update, so I will have to flash another ROM anyway. I'm willing to wait for it to come out first.
Hello Guys
I bought my Z5c in November 2015. Until Thursday it had been working fine. We all know about battery drain and all that but actually the phone was working. I personally like the phone a lot.
On Monday July 31st, I updated to Nougat 7.1.1. Everything was OK. On Thursday Morning the back / home / recent buttons were not working.
I already tried:
- Safe mode (the problem is still there)
- Factory reset
- Software repair (Xperia Companion)
- Flashed the phone and changed CDA to another region. I could not downgrade
I don't think this is a hardware issue because the buttons work in the lockscreen and in landscape mode. It just doesn't work in portrait mode.
This made the phone unusable. My phone company gave me a Sony Xperia XA for $47 for now.
The Z5c was purchased unlocked.
I really need your help please
Thanks
What can I do in this case? I don't think there's a Sony repair center in my country
hi... I have exact same problem..! plz help...
Plz help someone
.....
I am running lineage 14.1 and still there is problem. It works OK in recovery
Hi
I've got the same issue with my wife's Z5C. The navigation buttons are totally unresponsive! Phone is not rooted, so I have no idea if they work in recovery or not. But the buttons DO work if I put phone into landscape mode with Sony logo to the right, but not with the logo to the left?!?
I'm stumped here, so please provide some feedback please...
Meanwhile I'll reset phone with PC Companion and maybe later I'll downgrade a few builds...
//Johan
UPDATE:
Downgraded to .160 (Generic AU) but no luck. I think this phone is toast, but the weird thing is that according to built-in diagnostics, the surfaces where the back/home/recents button are located are all functioning properly. Any thoughts?
The easy solution is to install an alternative from play store and see if it works or if you are still covered by the warranty just send it to Sony...
The 'get your hands dirty' option...
Has anyone tried flashing their phone using the flashtool http://www.flashtool.net/ ?
It Sounds to me like you are facing a software bug that would disappear if you perform a clean installation of android...
What exactly happened? Provide us with more info....
unfortunately, i act in assumption, this is a hardware issue like seen often on the z3c. The digitizer is broken at these positions. it happens often at the home/back buttons and at the pull down menu.
You can verify this by activating the glove modus (hope this is the right translation of the german Handschuhmodus) which indicates, where exactly you are hitting the touchscreen.
- fix is to replace the touchscreen.
- workarounds are to activate display rotation (and then rotate so that the buttons are appearing at the upper (right) side of the display
- activate the glove modus - i can actually still hit the buttons at their corners
-use the "Back Button" app to generate additional menu buttons.
- move the buttons with Google ADP tools
(i'm actually not allowed to post links, google for it in the official z3c Sony support forum)
Did you ever resolve this? I've come across the same problem (running stock Android 7.1.1).
Went through all reset procedures, safe mode, screen tests etc.
Seeing the same result as you - this area of the screen works fine when locked, but when unlocked it's unresponsive.
I've done a full factory reset on it, just to determine if that'll fix it - no luck.
I would love to know more about why this is thought to be a hardware issue, when the hardware concerned works fine to unlock the phone.
My next step will be flashing a custom ROM, see if that fixes it. Any other hints / tips / clues / suggestions more than welcome!
eduardo4188 said:
Hello Guys
I bought my Z5c in November 2015. Until Thursday it had been working fine. We all know about battery drain and all that but actually the phone was working. I personally like the phone a lot.
On Monday July 31st, I updated to Nougat 7.1.1. Everything was OK. On Thursday Morning the back / home / recent buttons were not working.
I already tried:
- Safe mode (the problem is still there)
- Factory reset
- Software repair (Xperia Companion)
- Flashed the phone and changed CDA to another region. I could not downgrade
I don't think this is a hardware issue because the buttons work in the lockscreen and in landscape mode. It just doesn't work in portrait mode.
This made the phone unusable. My phone company gave me a Sony Xperia XA for $47 for now.
The Z5c was purchased unlocked.
I really need your help please
Thanks
What can I do in this case? I don't think there's a Sony repair center in my country
Click to expand...
Click to collapse
Hi guys,
Kind of new to pocophone but I'm experiencing something really strange that I haven't on any other phone I've had before. Here's the background..
I bought the phone as a gift for my mum and she absolutely loves it but she's told me the phone will randomly make a call itself. I didn't believe it until I saw it happen. She can be on the phone (having made or received a call legitimately) and the call will automatically be put on hold waiting for her to answer a call from another person. The issue is, that person hasn't called her so when she calls back, the person is confused. This can also happen when she isn't on the phone
I checked her call waiting options (turned off and on, neither makes a difference) and reset the phone to factory settings but still getting the same issue. We haven't set up Google assistant or anything similar so the calls wouldn't have been made my a voice command either.
It's really strange and I've looked on the Internet but can't find anything reported on it. The phone is running miui 10 and she is on virgin mobile. The phone is less than 2 weeks old.
Any help is much appreciated.
Vik
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
melodystyle2003 said:
Haven't faced something similar. If I were in your shoes, I would 1. Factory reset everything, 2. flashed latest global stable miui ROM and 3. checked again if the same problem persists.
Click to expand...
Click to collapse
Thanks @melodystyle2003. I've tried a factory reset on the phone. When the phone does a factory reset, would that not install the latest stable miui ROM? It installed miui 10 and when I checked for updates on the phone, it informed me that there were no more updates available
I think the problem is, proximity sensor. This used to happen to older family member.
About phone->MIUI version, which version does it use?
green. said:
I think the problem is, proximity sensor. This used to happen to older family member.
Click to expand...
Click to collapse
Thanks @green. Did you ever find a solution to that proximity sensor issue?
melodystyle2003 said:
About phone->MIUI version, which version does it use?
Click to expand...
Click to collapse
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
vikz.t said:
@melodystyle2003 here's the version information I see when I go to about phone : Miui Global 10.1. Stable. 10.1.3.0. ( PEJMIFI)
Click to expand...
Click to collapse
This is the latest stable version.
Install the google dialer, and force stop the default one. Also, try switching your network connection, like if it's on 3G, shift it to 2G or vice versa, for some time.
And if proximity sensor is the cause (as mentioned by another fellow member), you can check the sensor wake up time through BBS or similar app. Proximity sensor does appear in the sesnor column of BBS app. And going through the wakelock's data, you might also be able to detect any other possible cause.
Have you tried switching off the 'redial automatically' option in the dialer options? That seems to be your problem.
vikz.t said:
Thanks @green. Did you ever find a solution to that proximity sensor issue?
Click to expand...
Click to collapse
It's not the hardware fault. Old people tends to keep the phone slight upwards while speaking, the proximity sensor wakes the screen and by accidentally registers the touch. This usually happens and the accidentally put the call on hold, accepts the second call or the add new call. You can try using the phone for a day.
Old thread, but just wanted to add that we have the same issue with a Pocophone we use at work. When you put away the phone after a call, then at random times it calls the last person you talked to before the current call. Does it about 1 out of 40 calls and is 100% a phone firmware issue, not some old lady holding her phone wrong.
Hi,
I have looked on internet regarding the issues on motorola razr ( 2019 ) with peek display but i couldn't find anything helpfull. The thing is that the peek display when the phone is closed is working sometimes and I can see that the screen is on when I closed the phone and try to turn on external display. I have tried to clear the cache of the display app but it didn't helped much to be honest. The phone is brand new from official website so there is not option to have a faulty phone as like I said the screen (display app ) sometimes works sometimes doesn't. I have even tried to uninstall the app update and reinstall it but still doesn't work as it should. I do not want to factory reset the phone becasue my e-sim will be removed from phone and I will have to call my carrier to send me the code again.
Whoever has a phone could you please let me know if you experienced the issue as me ? If yes and you have fixed that please tell me how as this is let's say annoying for foldable phone when extra display just not working and I fell like to stick with my old phone
I have latest Android 10 update on the phone as well.
Thanks
Snip3r
My peek display is working fine. There don't seem to be many ppl with this phone so not a very active forum.
pjcons said:
My peek display is working fine. There don't seem to be many ppl with this phone so not a very active forum.
Click to expand...
Click to collapse
You lucky cuz for me it's working sometimes and it's annoying to check notification or whatever I have to open the phone and unlock it.. Like i said i tried reinstall app install update ect but it didn't helped much. I could restart it but I will loose by esim from phone and it will take time again to get the new one.
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Glaux said:
Anyone else experiencing this? Less than 10 seconds after I fingerprint unlock, sometimes the screen will go black while I'm reading a message or whatever. Other times it seems to be triggered by a touch action, like pressing on an icon or clearing a notification.
I found no setting that explains it. Screen timeout is set to 1 minute. I don't have any third party lockscreen or display related apps. It's been happening for as long as I can remember with this phone, and I thought the January update might fix it but it persisted through. Faulty proximity sensor maybe? I'm starting to contemplate warranty servicing.
Click to expand...
Click to collapse
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
bobby janow said:
I think it's A12. On the P5 you could look at the device and it would stay on when doing something. The feature, although there is a setting on/off, does not work any longer. I never had it on the P6 shipped with A12 but on the P5 my wife has the same problems since updating. So perhaps a proximity update will fix it but if all else is working the replacement will almost guaranteed be worse.
Click to expand...
Click to collapse
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
vandyman said:
Are you using a custom kernel or have had a custom kernel installed in the past?
If so, you will need to try a factory reset and complete full stock image.
Click to expand...
Click to collapse
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Glaux said:
I saw that setting but I don't see how it's relevant. Even without that setting, the display should not turn off on its own before 1 minute of inactivity.
No. I didn't do any modding beyond bootloader unlock and root with Magisk. I flashed the January factory image a few days ago and rerooted, but as I said the problem started long before that.
Click to expand...
Click to collapse
I didn't realize you were rooted, I usually don't read signatures. Have you unrooted and tested? Other than that I'm not rooted so perhaps someone can help you out. Maybe change the title of the thread so rooted folks will jump in with suggestions. Good luck.
Looks like the issue might have come from the launcher I use, Smart Launcher. Specifically a setting called "Smart Screen Off" that's not working as intended. I turned that off and so far I can't reproduce the issue.