Unresponsive idle issue and call microphone issue - Asus ZenFone Max Pro M1 Questions & Answers

1. My 4gb ZB601KL sometimes doesn't respond to the unlock button for a while.
2. Sometimes when I make a call, the recipient cannot hear my voice while I can hear theirs. I'm using Jio4G VoLTE.
Version: 327, stock rom, without root/bootloader locked.

spyro197 said:
1. My 4gb ZB601KL sometimes doesn't respond to the unlock button for a while.
2. Sometimes when I make a call, the recipient cannot hear my voice while I can hear theirs. I'm using Jio4G VoLTE.
Version: 327, stock rom, without root/bootloader locked.
Click to expand...
Click to collapse
Yeah it happens sometimes with me too, your 2nd issue.
I am on stock v326 on 6gb version.
I tried holding where the mic can get sound exposure but what worked was kind of silly.
Just blow mildly into the mouthpiece and suck out mildly. The issue gets resolved.
Whenever i find it happening for the earpiece and mouthpiece, I do this and surprisingly it works.
Intially i thought i was covering the mic with my finger or due to the case that we out on.
For your first issue can you elaborate more? Unlock button as in the FP or the physical button that we hardly use ?

For the first issue
Both unlock button and do sensor don't respond sometimes, and neither does DT2W, does no one else have this issue?

spyro197 said:
Both unlock button and do sensor don't respond sometimes, and neither does DT2W, does no one else have this issue?
Click to expand...
Click to collapse
Try to wipe partition cache from recovery menu.

Related

Screen Lock issue with HD2

After i hang up on a call (when the phone is in sleep mode and the screen is locked) the screen unlocks. this is quite contrary to what is mentioned in the phone manual chapter 1 page 45. this becomes an issue since i use a bluetooth headset and the phone remains in its sleeve/case and after every call, a whole bunch of applications will launch since the case is in contact with the screen. have i overlooked some settings or are there other owners who have faced this issue?
ideas and suggestions welcomed
did you check it out if any of the hardware buttons being pressed against the case hence wakening up the phone.?
i had it to only closed al my apps in taskm and it stoped flickering
My HD2 is also behaving in the same way even in controlled test conditions - the phone unlocks when a call comes in (I'm presented with slide to accept or reject call) The phone unlocks during the call, but fails to lock again on disconnect (either by pressing "end call" or hang up via bluetooth).
Can anyone verify this? Is it interacting with something I installed?
I believe I found a (complicated) workaround.
What I want: leave HD2 inside pocket, answer calls with bluetooth headset, hang up and phone will go back to lock.
Problem: After I hang up using bluetooth or press the big red "End Call" button or the other party hangs up, the phone stays unlocked! It stays powered on and all kinds of buttons gets clicked.
Practically all lock sw uses their own lock screen (which I don't want to install). CSDevCtrl does not trigger by phone. TouchLockPro uses its own transparent lock screen but can respond to phone events. Using the !SUSPEND for TAPI\Ended under settings does not seem to work when the screen dims about 50 secs into the call.
Solution: Use TouchLockPro together with LockAndOff. Get TAPI\Ended to run LockAndOff will turn phone off, whether by bluetooth, big red "End Call" button, or the other party hangs up.
BTW: I think there is some confusion on whether the phone locks when you
1. press the big red "End Call" button, or
2. the hard "End call" button
in the forums.
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
linivan said:
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
Click to expand...
Click to collapse
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
johncmolyneux said:
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
Click to expand...
Click to collapse
My proximity sensor does not work, when I am getting a call my screen turn off and when I am taking the phone out from my face it turn on only when I am out side at the sun!! the screen stay off when I am inside room. I tested it with flsh light and it is working also.
I have a T-Mobile US version of the HD2. I am having the same problem when using the bluetooth system in my car. After answering or making a call the phone stay unlocked. And then starts making random calls while I am driving!!!!
There has got to be an easy fix for this!!!
Buy pocketshield, problem solved.
i have this unlock problem with 1.48 rom and i solve it by pressing start button and lock. after that everything works fine unless i change theme in settings. then just repeat first step.
Solved
Same trouble with me until I use the following software. I tried it and it's almost perfect. unzip it and just copy to your HD2, run CallerLoc.exe and click Yes, you'll find:when you hang up, or he/she hang up a call, or a call is established, the screen will turn off.
Why say 'almost perfect', the software is in chinese, but the filename is in english. and it's a call location software but with the function we need.
To stop or before you delete the software, run Callerloc.exe and click Yes again.
Hope this will help you. Sorry I don't find a English version of this software. I esure and I'm using this software perfectlly with my Leo.
theciscokid said:
Buy pocketshield, problem solved.
Click to expand...
Click to collapse
Same for me
Greetings.
I understand this is quite an old thread I'm digging up but I need a little help as well and I didn't want to start a new topic just for that.
I've this silly problem, appeared right out of the blue:
You all know the standard manila behavior, when the phone is idle, the screen first dims and after some more time, depending on your preferences, the screen locks. It also locks if you press the power off button. This all was happening to me till this morning.
I added an event in the calendar (the only change I made today) and after that, my phone dims and then goes in sleep mode after the designated period of time, but DOESN'T lock!!! It doesn't even lock when I press the power off button. I can still lock it by pressing Start and then lock or by press and hold the power button and choose the lock phone option. So one would say that it's still operational, so why bother about it, but I kinda liked the standard function and I have to freaking idea why it changed!!!
I'd be most appreciative if you could offer some help with that.
Oh, I forgot to mention. Soft reset didn't solve the problem. Erasing the calendar event didn't either.
My phone runs the factory ROM (1.66.482.1 ELL), I haven't changed anything other than user settings (yeah, I'm a noob... )
Thanks in advance!
Nasos
Pocketshield could be the end of your problems. You can try it for 10 days and see how it goes...
But why do I need to buy third party software in order to revert my phone to it's original operation?
No, this is not the answer I am looking for. I was wondering if you know of any kind of settings that might have changed by accident and caused this undesired behavior.
Thanks.
The best to return to normal operation would be a hard reset. Or you can spend a while trying.
You can try
HKLM\Software\Microsoft\Shell\Lockscreen\Enable=1
HKLM\Software\Microsoft\Shell\Lockscreen\Active=1
Thank you very much. I opted for the hard reset option... I hope it stays ok this time!
My HD2 also had some strange unlocking and unwanted calling.
I noticed it appeared when using the android style lockscreen.
When I changed back to the original one, problem solved
i had this too. the andriod lockscreen seems to be a bit buggy last time i used it, i accidentially called 7 random numbers

Multiple problems after official froyo update

i successfully updated to froyo from kies. before this i had the stock rom and did not install any custom one
after updating my proximity sensor works when the phone is held vertical in an upright position
but after making a call, if i keep it on the table and close the sensor, the screen doesn't turn off. it should turn off and was working fine in 2.1 for me
can you guys confirm if the sensor turns off even when laid flat on the table?
also, the volume up/down button does not silence the ringtone when i get a call
please reply so that i can confirm whether the problem is with my phone or with the new release.
Not sure about the sensor problem but as far as your second problem is concerned hold the vol down button for a few seconds to mute the ringtone
Sent from my GT-I5800 using XDA App
Proximity Sensor is problematic
Yes The Sensor does'nt seem to be responding towards the end of the call. Just use the home key to light up the screen.
The display screen timeout settings does not automatically turn off even after specified time.this happens very often and need to enable screen timeout settings again and again.
Sent from my GT-I5801 using XDA App
Yes , I am experiencing problem with Swype , it is not responding to aby gesture. I am able to type using swype as regular keypad but not as "swype". I resetted my phone 3-4 times but i wasn't lucky.
So i am using keypad only. Its official DDJP2 FROYO version thpugh its flashed using odin as i was experiencing problem with KIES.
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
satyamsit said:
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
Click to expand...
Click to collapse
May be you have checked "screen lock sounds" option in /settings/sound unchek and see if the problem persists...
deadwood01 said:
May be you have checked "screen lock sounds" option in /settings/sound unchek and see if the problem persists...
Click to expand...
Click to collapse
Thanks a lot for ur reply but the option is unchkd from beginning ... ..
satyamsit said:
I am experiencing some strange behavior in media and notification sound. while i play some song and want to lock my screen from power button, some glitchy sound is coming, same happening when some messages coming. is anybody experiencing the same. plz try it with headphone attached while playing a song and just lock the screen from power button menu...
Click to expand...
Click to collapse
Yes....This is happening
This is the worst release by Samsung , as per me....Even on call if you are using headphone, you will hear clicking sound (argh)
Yes the proximity sensor isn't working fine. Screen does not turn on after a call. So I need to press home screen every time.
And long pressing menu button in call log does not enable search bar which happened perfectly in 2.1
maverickgenius said:
also, the volume up/down button does not silence the ringtone when i get a call
please reply so that i can confirm whether the problem is with my phone or with the new release.
Click to expand...
Click to collapse
For those who r facing the problem silencing the ringtines from vol up down, press power on off button, it shud work.
satyamsit said:
For those who r facing the problem silencing the ringtines from vol up down, press power on off button, it shud work.
Click to expand...
Click to collapse
we do know about pressing the power on/off key but that also switches off the sceen. but volume up/down only silences the ringtone but doesn't switch off screen.
araandroid said:
Yes , I am experiencing problem with Swype , it is not responding to aby gesture. I am able to type using swype as regular keypad but not as "swype". I resetted my phone 3-4 times but i wasn't lucky.
So i am using keypad only. Its official DDJP2 FROYO version thpugh its flashed using odin as i was experiencing problem with KIES.
Click to expand...
Click to collapse
swype doesn't work because languages are not installed. root, delete swype, install swype from official site.
jaskiratsingh said:
Yes....This is happening
This is the worst release by Samsung , as per me....Even on call if you are using headphone, you will hear clicking sound (argh)
Click to expand...
Click to collapse
and during a call, if you press volume up/down button to increase/decrease the volume, the voice breaks for a second and you hear a clicking noise.
these problems are seriously irritating me. thinking of going back to 2.1 or some custom ROM is samsung does not release an update fixing these problems.
Few more problems that I had observed....
1. If you open contacts and press back button you won't be going any where
2. Previously I used to connect my phone using bluetooth to my PC (Ubuntu) but now even after turning on my Bluetooth along with visiblity phone is not visible. Once I was lucky and recognized my phone as "V5" though the device name is different.
3. If you try to add pics to the contacts from your gallery the time taken is very long which was not the case with Eclair 2.1
4. Previously with Launcher Pro plus on Eclair I never had to "Force close" any application, but after upgrading to Froyo the first call itself raised a warning for force close. Even after sometime in my other call I couldn't End my call as the screen was not responsive.
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
techie.raj said:
Few more problems that I had observed....
1. If you open contacts and press back button you won't be going any where
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
Click to expand...
Click to collapse
I was experiencing the same problem on the first day, but after that i rooted my phone and installed busybox. from last 2 days did not find that contacts back key problem anymore.. i dont know its a temporary fix and what has fixed it anyway...
but really .. somehow this release is not at all convincing. so sad.
techie.raj said:
After a struggle for One day on latest Firmware I feel that its not that worth to wait this much amount of time for official firmware.
Click to expand...
Click to collapse
i too feel the same way mate..
can anybody tell me if I5801ZHJPF better that DDJP2?
I have another different problem my battery life is not going above 10 hrs while on 2.1 i used to get 18hrs. Am i missing some setting or what.I am gonna install something else if this **** firmware does not improve in the next update
i think this update was hastily released.
many bugs in it.
if you see the in-built task manager, the "uninstall" button is not even properly designed.
even accelerometer has some problems
the worst bug ever is the camera bug
theres this geo-tagging option..
until you get a fix on ur location camera will force close..
and it cant be disabled at all..
the only way to get around it is to use 3g or disable network mode in 2g..
19.nvv.11 said:
the worst bug ever is the camera bug
theres this geo-tagging option..
until you get a fix on ur location camera will force close..
and it cant be disabled at all..
the only way to get around it is to use 3g or disable network mode in 2g..
Click to expand...
Click to collapse
i saw somewhere that this can be solved by disabling "use wireless network" option in settings->location and security.
not sure though. try it.
maverickgenius said:
i think this update was hastily released.
many bugs in it.
if you see the in-built task manager, the "uninstall" button is not even properly designed.
even accelerometer has some problems
Click to expand...
Click to collapse
+ add one more bug to the list,
the microphone is also not working properly with different applications like Talking Tom or Talking Parrot, previously they used work on 2.1 without any problem or distrubance.
Did anybody also had the same problem?
One good thing with the Froyo update is previously my phone is used to restart unconditionally with the stock firmware (randomly sometimes during call or when Ideal). But till now no such weird behaviour in the current release.

[Q] Home button wont work During Call.

I have searched and then made this thread. There were some people with home button issue but None of those were related to my problem.
PHONE MODEL - GT-I9505 ( International version)
I have had my S4 for a couple of months now and I am addicted to flashing. I flash a test lot of new roms.
MY PROBLEM
When i make or I get a call, Once i pick the call and put my phone to the ear and after the proximity sensor turns off the screen i cannot use my home button or powerbutton to wake the screen during call. For example if i want to cut the call During a call. I simply cannot do it. Sometimes the home button will respond, Some times it wont
For the home button to work The other party has to cut the all only when my phone detects that the call has been disconnected it wakes up. Looks like the home button stops functioning ?
I dont know what is happening.
I thought it was the rom issue, But it isnt. I tried two different roms. Did the same behaviour.
Any advice or anything to help me will be appreciated. Is my hardware damaged?
My phone is never dropped and is very new like .
ROMS I TRIED
Wanam Lite.
Cynogenmod 10.1
same problem. any solutions?
I am having the same issue with my home button. Won't press during calls. Did you ever find a solution? Thanks!
rdhalla said:
I have searched and then made this thread. There were some people with home button issue but None of those were related to my problem.
PHONE MODEL - GT-I9505 ( International version)
I have had my S4 for a couple of months now and I am addicted to flashing. I flash a test lot of new roms.
MY PROBLEM
When i make or I get a call, Once i pick the call and put my phone to the ear and after the proximity sensor turns off the screen i cannot use my home button or powerbutton to wake the screen during call. For example if i want to cut the call During a call. I simply cannot do it. Sometimes the home button will respond, Some times it wont
For the home button to work The other party has to cut the all only when my phone detects that the call has been disconnected it wakes up. Looks like the home button stops functioning ?
I dont know what is happening.
I thought it was the rom issue, But it isnt. I tried two different roms. Did the same behaviour.
Any advice or anything to help me will be appreciated. Is my hardware damaged?
My phone is never dropped and is very new like .
ROMS I TRIED
Wanam Lite.
Cynogenmod 10.1
Click to expand...
Click to collapse
jasonbosch said:
I am having the same issue with my home button. Won't press during calls. Did you ever find a solution? Thanks!
Click to expand...
Click to collapse
Go to Apps - Settings - My device - Call - Untick Turn off screen during calls :highfive:

Cannot unlocked ZUK Z1 after ending call with screen off

Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Hi there, i am facing the same issue since two days now
First i am unable to come up with the physical home button issue and now there is this new issue. The phone does not respond after a call and the screen remains off and does not respond to any touch (double tap) or even the power button and home button pressed. I had to take the mobile into the recovery mode via home buttons power button and volume rockers. Is there any possibility of this getting fixed. I think i made a huge mistake purchasing this phone.. Slowly getting into problems one by one.. First the physical home button issue then this screen off issue. Checking for updates daily but seems like ZUK officials and Cyanogen are sleeping! Highly disappointed!!!!
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
ingtrans said:
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
Click to expand...
Click to collapse
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Sydarij said:
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Click to expand...
Click to collapse
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
ingtrans said:
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
Click to expand...
Click to collapse
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Sydarij said:
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Click to expand...
Click to collapse
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
ingtrans said:
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
Click to expand...
Click to collapse
Yes, the accidental wake up is set yet the issue cannot be resolved. Any other way you can resolve this and prevent the issue from reproducing? In my opinion, ZUK and Cyanogen officials are asleep after launching their new flagship. Dont see any updates coming from them since last 2 months. highly disappointed with this!
Sydarij said:
Any other way you can resolve this and prevent the issue from reproducing?
Click to expand...
Click to collapse
No idea. The solution I found seems to work well for me, at least I have not had any issues since I applied it.
Please turn on adaptive brightness. Issue will be resolved
ingtrans said:
Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Click to expand...
Click to collapse
Hi! I'm facing the same issue for the last 3 days. I felt everytime there is any moisture of sweat on the ear piece the phone hangs and doesn't get unlocked.
Will try shutting the double tap options. Hope it works! This is the first time I've brought anything in the launch sale without reading reviews. Hope I don't regret this.
sir when call come rintone accor but calling display doesn,t show
when i press phone icon in menu then it shows
phone is lenovo zuk z1
screen freezes during/after call !!
did you solve this problem?
i too have posted the same problem here ..
any sugesstions?
i am facing a black screen while calling and receiving calls on my zuk z1 .. any solution? and where do i find the proximity setting in my settings?

Proximity sensor problem

On all the noughat roms i've used i'm having an issue with the proximity sensor.
The problem is, whenever I call someone or pick up a call the screen goes black.
I changes the settings so that pressing the power button cuts the call, but i can't put the call on speaker cause i can never see the caller screen, because of this problem.
Please help.
Thanks.
Also i'd like to mention that I've tried the method in which you push a reconciled apk through ADB. This method used to work, but that stopped working.
Facing the same issue

Categories

Resources