Develop Bugs

Mic, radio or Jelly Bean Issue

I have been reading through some of the threads here trying to find solution for my problem and I cant seem to figure out which of the possibilties it is. Ever since I flashed Vicious 4.1.1, I have in call troubles. Sometimes I cant hear them sometimes they cant hear me The call will be going fine then the problem just randomly starts. I tried calling myself and making a steady noise and found that after about 2 sec I started cutting out. I always have 3 if not 4 bars. I read a thread that talked about a mic issue but being that I never had this before jelly bean I have trouble believing that to be the problem. Is there a radio update that is needed going to 4.1.1? Does anyone else have this problem? Does any one have a solution for me? Attached is my phone specs

bump

if problem exists when you are stock then it sounds like you are up for a warrantee replacement.
---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------
or if you feel especially adventurous, you could try reseating the connector in this photo http://guide-images.ifixit.net/igi/D5VWDvSZo2D3VQQB.thumbnail
There are no waranttee seals. 8)

animal24 said:
if problem exists when you are stock then it sounds like you are up for a warrantee replacement.
---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------
or if you feel especially adventurous, you could try reseating the connector in this photo http://guide-images.ifixit.net/igi/D5VWDvSZo2D3VQQB.thumbnail
There are no waranttee seals. 8)
Click to expand...
Click to collapse
the problem only started after installing JB

Unresponsive and Crazy touchscreen

Received my phone yesterday, and when I was browsing it , the screen went crazy, and unresponsive. did a factory reset and the problem still persisted. Opened a return request at amazon so they can send me a new one. Don't know if anyone had the same issue or it was just me. Here is a video
https://dl.dropboxusercontent.com/u/12983778/VID_20150527_213832648.mp4

Please check if TalkBack is enabled. If this setting is enabled, the touch screen may behave differently and appear to be defective. Instead of one tap to open an item, you will need to tap once until it highlights with a green box around the selection, then double tap to open. Also when swiping it may require using two fingers instead of one. You may also be hearing voice prompts to every action made.
To disable go to Apps/Settings/Accessibility/Talkback - turn off.
Best regards,
ASUS_USA

Same problem
Hi,
I had the same issue! I getback the phone in guarantee to Taiwán. The seller says that the phone was repairde, the display was changed.... finally 2 weeks ago I reicived the Zenphone 2 (1.5moths since the deal). Now today the phone have the same issue, I try to clean the dipslay phone and suddenly the touch screen have the same issue, crazy and unresponsive screen!! I very frustaded about the ASUS Brand! tell me what's happened with your phone?
thanks
Xytrax

Try to delete user data,then factory reset and then wipe cache.If after this you're still in trouble simply use warranty:hardware problem,asus fault.

You must use 2 fingers when you type to get through the setup. I know its a pain but when you are able to get in, turn "TalkBack" off.

I bought a zenfone 2 64gb on amazon and I had the same random issues: unresponsive touch screen, unsensitive, ghost touches.
I guessed that it could be the screen protector but it was still happening after remove it.
So, I asked to amazon a replacement.
After a perfect week, I am starting to have the issues, again!
I sold my oneples one to avoid touch screen issues. I am very upset!

I'm having the same issue as you guys. I also noticed that cleaning the screen with a rag (especially the one for glasses) makes the touch screen go crazy. At first i tried to downgrade the firmware, unluckily i had the issue again. Then i upgraded the firmware from the phone and now it's all going apparently well. I'll update for any news.

Same here, wrote to customer care yesterday evening.

taldeital said:
Same here, wrote to customer care yesterday evening.
Click to expand...
Click to collapse
Please let us know if you have any answer, it is getting very annoying, thanks.

To anyone who have this issue: Try to test touch screen by SMMI's test option. Open calculator, type ",12345+" (with the comma), then "=" (equals). SMMI menu will show up. Now "single test", then "touch test".
In my case this process gives a straight line of unwanted touch inputs in the upper region of the screen ( sometimes multiple dots in a row forming a complete straight line). Do you guys have the same result?

Huge Pepo said:
To anyone who have this issue: Try to test touch screen by SMMI's test option. Open calculator, type ",12345+" (with the comma), then "=" (equals). SMMI menu will show up. Now "single test", then "touch test".
In my case this process gives a straight line of unwanted touch inputs in the upper region of the screen ( sometimes multiple dots in a row forming a complete straight line). Do you guys have the same result?
Click to expand...
Click to collapse
With the others, I have this one, also. It happens at every restart and the only workaround is turn off/on the display.

zatarra77 said:
With the others, I have this one, also. It happens at every restart and the only workaround is turn off/on the display.
Click to expand...
Click to collapse
Same as me.. But I think this is lcd controller firmware or driver problem on kernel . because yesterday I'm install custom rom on my zenfone (Cm12.1) then surprise ... this problem continue... I had change custom kernel but no chance ... if you have this problem open Asus glove mode this is temporarily solution for now. Asus will contuniue work on this problem. Now I waiting Asus response for this .. :

Huge Pepo said:
I'm having the same issue as you guys. I also noticed that cleaning the screen with a rag (especially the one for glasses) makes the touch screen go crazy. At first i tried to downgrade the firmware, unluckily i had the issue again. Then i upgraded the firmware from the phone and now it's all going apparently well. I'll update for any news.
Click to expand...
Click to collapse
It's a software related problem.. Because we're a lot of ppl suffering this problem. But, don't know why, ASUS is ignoring us.

I have sent my phone for repair. They say that they will replace the whole display.

Hi guys. I have almost identical issue and this seems like a hardware fault. I sold the Zenfone 2 to a friend and after 2 months she complains about the unresponsive touchscreen only at the top of the display..... I have the phone with me now, trying to fix it.. Did a factory reset, firmware upgrade, no results. Definitely a hardware issue and it is seems that lots of people are affected. So dissapointed by Asus......

If it's a hardware issue why is it so many people experiencing this now together all in the same time? Not earlier not later? My guess will be software problem. But I'm not sure

Any of you guys have a microsd card installed?
Sent from my ASUS_Z00AD using Tapatalk

ImjuzCY said:
If it's a hardware issue why is it so many people experiencing this now together all in the same time? Not earlier not later? My guess will be software problem. But I'm not sure
Click to expand...
Click to collapse
im 100% sure it is a software problem..
To me.. and to every1 i know who's facing the issue.. the problems started with the September Update..
Im guessing it is the touchscreen firmware version.. Hope ASUS check it..l

gREENNNNN said:
im 100% sure it is a software problem..
To me.. and to every1 i know who's facing the issue.. the problems started with the September Update..
Im guessing it is the touchscreen firmware version.. Hope ASUS check it..l
Click to expand...
Click to collapse
I'm going back to .59 to try. I don't think asus is aware about this. Need to post it to zentalk to get more attention from Asus. @ASUS_Khang
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 11:12 AM ---------- Previous post was at 10:58 AM ----------
This is what I have. Video in the link. Previously only appear when phone is hot especially when charging.
These days it comes out randomly. Hot or not. Even in recovery.
https://drive.google.com/file/d/0BzA8N76_PxvsSkdjbEhFT0p0bFk/view?usp=sharing
---------- Post added at 11:36 AM ---------- Previous post was at 11:12 AM ----------
I've downgraded to .59 and the problem still persist. Maybe the touchscreen firmware isn't downgradable or it's hardware issue

ImjuzCY said:
I'm going back to .59 to try. I don't think asus is aware about this. Need to post it to zentalk to get more attention from Asus. @ASUS_Khang
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 11:12 AM ---------- Previous post was at 10:58 AM ----------
This is what I have. Video in the link. Previously only appear when phone is hot especially when charging.
These days it comes out randomly. Hot or not. Even in recovery.
https://drive.google.com/file/d/0BzA8N76_PxvsSkdjbEhFT0p0bFk/view?usp=sharing
---------- Post added at 11:36 AM ---------- Previous post was at 11:12 AM ----------
I've downgraded to .59 and the problem still persist. Maybe the touchscreen firmware isn't downgradable or it's hardware issue
Click to expand...
Click to collapse
Hey everyone, thank you so much for sharing with me. I'll forward this to our service team. Sorry been away..it's Thanksgiving week here in the US...so I'll get to this on Monday!

TWRP Touchscreen problem

Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?

Brainium said:
Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?
Click to expand...
Click to collapse
both panels should be supported by twrp...at least when they came originally from htc.
seems the sharp panel you got its another revison/running an incompatible driver.

j to the 4n said:
both panels should be supported by twrp...at least when they came originally from htc.
seems the sharp panel you got its another revison/running an incompatible driver.
Click to expand...
Click to collapse
That may be true, but why would it work in the ROM, but not in the recovery? Would it be possible to take the driver out of the ROM and put it into TWRP?

same here, works in ROM, not working in twrp

Did this ever get figured out. I have the same issue!

was rooting a friends phone, everything went well...got to twrp. no touch. turns out he has sharp panel as well... is this a twrp issue or just a driver issue that we are SOL with?

I have the same issue too!

Brainium said:
Hi, I had cracked my screen and got a replacement from ebay. It went in just fine, and works well. The problem is that in TWRP, no touch events are recognized. It works fine in Viper10, but in recovery and the MultiROM menu, it doesn't. I'm thinking it may be a driver issue, as the previous panel was a Tianma, and this one is a Sharp.
Any suggestions as to what may be the problem and how to fix it?
Click to expand...
Click to collapse
Have you worked it out yet? Thanks.

mybnr34 said:
Have you worked it out yet? Thanks.
Click to expand...
Click to collapse
I had the same issue. Cracked my screen, had it replaced in an unauthorized service center. Came back, no TRWP touch response. Funny enough, even an update with a RUU did not work and would fail every time.
Sent to HTC for repair, they changed the screen for another one. Still didn't work. Sent the phone back again, they supposedly reset the phone to factory settings and "connected connector (A102)". That's at least what the service protocol says. Screen works perfectly after that.
Another side effect, when the TWRP was not working was, also double-tap to wake in android and camera launch shortcuts also didn't work.

mybnr34 said:
Have you worked it out yet? Thanks.
Click to expand...
Click to collapse
No. I ended up just getting a new phone through Verizon.

guys anyone found a solution for this?
i change my htc 10 screen too for a one that i bought in alliexpress and no luck with twrp
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
madzur said:
I had the same issue. Cracked my screen, had it replaced in an unauthorized service center. Came back, no TRWP touch response. Funny enough, even an update with a RUU did not work and would fail every time.
Sent to HTC for repair, they changed the screen for another one. Still didn't work. Sent the phone back again, they supposedly reset the phone to factory settings and "connected connector (A102)". That's at least what the service protocol says. Screen works perfectly after that.
Another side effect, when the TWRP was not working was, also double-tap to wake in android and camera launch shortcuts also didn't work.
Click to expand...
Click to collapse
hi, what means this?
---------- Post added at 03:26 AM ---------- Previous post was at 03:25 AM ----------
mybnr34 said:
I have the same issue too!
Click to expand...
Click to collapse
you also broke your display and replace it?

dentedilupo said:
guys anyone found a solution for this?
i change my htc 10 screen too for a one that i bought in alliexpress and no luck with twrp
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
hi, what means this?
---------- Post added at 03:26 AM ---------- Previous post was at 03:25 AM ----------
you also broke your display and replace it?
Click to expand...
Click to collapse
Hi. This is something that was listed on the service protocol. I have no more details about this. That's why I wrote it here, hoping maybe someone has an idea.

Double tap not always working

Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.

angka8 said:
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
Click to expand...
Click to collapse
I found it wasn't great in the dark, I assume it uses the light sensor to determine if in pocket etc
Sent from my Google Pixel XL using XDA Labs

I have noticed the same thing. It isn't 100% consistent.

FWIW: Mine seems to be very consistent if I triple tap. Perhaps the first tap wakes it up if it's in a deep sleep?

Hopefully fixed in the December update.

JAYNO20 said:
Hopefully fixed in the December update.
Click to expand...
Click to collapse
No change for me.

cam30era said:
No change for me.
Click to expand...
Click to collapse
Has been working consistently for me so far. Will post back if that changes.
---------- Post added at 03:07 PM ---------- Previous post was at 02:26 PM ----------
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.

JAYNO20 said:
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
Click to expand...
Click to collapse
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.

cam30era said:
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
Click to expand...
Click to collapse
Makes no sense. I'm glad we are seeing the same issues though, at least it's consistent there

I'm having the same exact issues. Tap not working consistently and sometimes the lift doesn't work either. Hmm.

It's worth noting I had the same issues with the Elemental kernel before this ddtw option was available. The ddtw option was just as inconsistent for me.

Neither working at all for me.
Update: Seems to be working fine now.

if you have a screen protector that might cause the issue
if it still doesnt work without screen protector reflash the factory image

The update seems to fix the issue.
Update: the issue still there. But much less frequent

The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?

I have noticed that is works better if the screen is locked. So if your phone doesn't lock for 5 or so minutes, it may not work until after that time. Try to set your phone to "Power button instantly locks" and then try it. Mine was not working at all, but when I locked the device sooner, it started to work consistantly. Might not help you, but fixed it for me.

Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
GCbard said:
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
Click to expand...
Click to collapse
It's an option with the newer OTA.

clockcycle said:
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
It's an option with the newer OTA.
Click to expand...
Click to collapse
Where is this option located? I'm on the November update. Is this with the December update?

GCbard said:
Where is this option located? I'm on the November update. Is this with the December update?
Click to expand...
Click to collapse
December OTA. Same location as other Moves/ gestures.

FWIW: what I've noticed is that if my phone is sitting on something, DTTW works 100% of the time. If I have it in my hand, it's very sporadic.

Android Messages outgoing message sounds not Working

Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you

BFSilva said:
Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you
Click to expand...
Click to collapse
I am having the same issue! This update has been a headache so far haha

It's been like this ever since I jumped on the first beta. Surprised it's still broken....well.....not really.

Aerro47 said:
I am having the same issue! This update has been a headache so far haha
Click to expand...
Click to collapse
AndrasLOHF said:
It's been like this ever since I jumped on the first beta. Surprised it's still broken....well.....not really.
Click to expand...
Click to collapse
Thank You very much for your answers!
Are you on Android 9.0 final release?
Have you guys tried to factory reset?
Thanks

Yeah, it hasn't worked for a while. I've been using P since beta 2 and I factory reset every single beta update including the now released final Pie.
Don't bother factory reseting, it won't fix it.

Mr Patchy Patch said:
Yeah, it hasn't worked for a while. I've been using P since beta 2 and I factory reset every single beta update including the now released final Pie.
Don't bother factory reseting, it won't fix it.
Click to expand...
Click to collapse
Thanks man! I was getting worried it might be some kind of bug during the update process, and I was on the verge of factory reseting the phone!
:good:
Have you noticed any battery improvements since the update?
Since Oreo 8.1.0 that I've noticed that the battery doesn't last as long. In my case I've noticed a 25 to 30% decrease in battery life!

BFSilva said:
Since I updated to Android 9.0 Pie on my Pixel 2 XL, the Android Messages outgoing message sound is not working.
Is this happening to anyone else?
Does anyone know a fix for this?
Thank you
Click to expand...
Click to collapse
Really mines works...I can't get it to turn off

plokm said:
Really mines works...I can't get it to turn off
Click to expand...
Click to collapse
Screw you.....joking lol
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
BFSilva said:
Thanks man! I was getting worried it might be some kind of bug during the update process, and I was on the verge of factory reseting the phone!
:good:
Have you noticed any battery improvements since the update?
Since Oreo 8.1.0 that I've noticed that the battery doesn't last as long. In my case I've noticed a 25 to 30% decrease in battery life!
Click to expand...
Click to collapse
I haven't noticed battery improvements for any phone that ever claimed better battery. I always have to top up every phone I've had after work. I'm a heavy user tho, but no phone has ever given me "amazing" battery. This phone is no different. I've had A LOT of different phones too.

I'm experiencing the same issue. Also experiencing double notification sounds for some incoming messages. Mostly annoying but would like to see a fix.
Messages version: 3.4.048, last updated 8/7/18

I've been running the beta from the start without this problem on my Pixel XL. Just updated my wife's Pixel XL and she reported the problem to me. It wasn't until I enabled and disabled this feature that I had this problem. Now I can't turn it off. It seemed to start after installing the Digital Wellbeing Beta. Wouldn't that be ironic.

I got an update for Messages last night and now I'm finally seeing suggested replies in the notification shade. Also...now the notification sound when sending is working but it's not using the 'swoosh' type sound and instead is using the sound I have picked when receiving messages.

Yeah I just got the pie update on my phone (Pixel 2 XL) and I can't seem turn off outgoing notifications. I went to settings and clicked that setting off. It still will not turn off. I never even knew my phone had this function until this update but it is driving me crazy.

Just switched to Pie on my Pixel 2 XL two days ago and got the messages update as well.
I have the same issue as a few others have mentioned, I now have an outgoing sound when previously I did not and there is no way to turn it off. The switch in Messages to turn it on/off does nothing and it is the same sound as the 'received' message notification.

Well I got it to stop but can't get it to turn back on. I went into settings -> apps -> messages (app) -> storage and cleared both the storage and cache. Now it no longer sends out going message sounds. The problem is I can't turn it on or off. Lucky for me I just want it off.

Silly question: does clearing cache and storage delete all of your messages? This happened immediately after I upgraded my Pixel 2 XL to Pie....like everyone else.

Sadly it was only a temp fix. Today the outgoing sound came back.

jwjames83 said:
Silly question: does clearing cache and storage delete all of your messages? This happened immediately after I upgraded my Pixel 2 XL to Pie....like everyone else.
Click to expand...
Click to collapse
No it doesn't. They will all reload. Done this numerous times.

i can not get mine to turn off

This is getting old!
This is getting really really old!
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
I wonder if a replacement SMS app would have the same issue?
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
I just installed a 3rd party messaging app. No outgoing notification issue or double notifications on incoming messages.

UserDave said:
This is getting really really old!
---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------
I wonder if a replacement SMS app would have the same issue?
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
I just installed a 3rd party messaging app. No outgoing notification issue or double notifications on incoming messages.
Click to expand...
Click to collapse
Textra works great. With outgoing sound :good: