Related
Phone details are in my signature. I reset the phone right out of the box as I always do when new phones or after doing a software upgrade.
I've noticed that marketplace isn't notifying me of app updates available.
When I buy something, it keeps says I have to buy over and over again and never lets me download the app even though I get the email confirmation from MS.
The on-screen keyboard, at the password screen or even when I go to start a text, there is a full 1 second delay or more in the first letter/number I push, always. Is this a defect in the touch screen or software?
My old WP7 had none of these issues.
Anyone else?
92GTA said:
Phone details are in my signature. I reset the phone right out of the box as I always do when new phones or after doing a software upgrade.
I've noticed that marketplace isn't notifying me of app updates available.
When I buy something, it keeps says I have to buy over and over again and never lets me download the app even though I get the email confirmation from MS.
The on-screen keyboard, at the password screen or even when I go to start a text, there is a full 1 second delay or more in the first letter/number I push, always. Is this a defect in the touch screen or software?
My old WP7 had none of these issues.
Anyone else?
Click to expand...
Click to collapse
Take it back and get another one. At a store they should swap it right there and then. It could be software related like every phone at launch has issues or a serious hardware problem
92GTA said:
Phone details are in my signature. I reset the phone right out of the box as I always do when new phones or after doing a software upgrade.
I've noticed that marketplace isn't notifying me of app updates available.
When I buy something, it keeps says I have to buy over and over again and never lets me download the app even though I get the email confirmation from MS.
The on-screen keyboard, at the password screen or even when I go to start a text, there is a full 1 second delay or more in the first letter/number I push, always. Is this a defect in the touch screen or software?
My old WP7 had none of these issues.
Anyone else?
Click to expand...
Click to collapse
Have you synced your device with the desktop Zune client yet? It might be worth a go before you finally swap it.
drupad2drupad said:
Have you synced your device with the desktop Zune client yet? It might be worth a go before you finally swap it.
Click to expand...
Click to collapse
Yes so I could sync all my pics, video, etc.
I already have the device setup exactly how I want it, I'd hate to return it when there is no backup/restore option in Zune. Dang it.
If its a software issue we can rule out Factory Reset... and that Im aware of there hasn't been an RUU leak for 8112 for the titan2 so flashing it is impossible.
Was the issue present from the get go? Like the moment It was turned on before setting up anything?
Tachi91 said:
If its a software issue we can rule out Factory Reset... and that Im aware of there hasn't been an RUU leak for 8112 for the titan2 so flashing it is impossible.
Was the issue present from the get go? Like the moment It was turned on before setting up anything?
Click to expand...
Click to collapse
After turning on my phone out of the box, I went straight and did a hard reset. So I noticed everything after that. Marketplace not notifying of app updates and the touchscreen keyboard issue yes. I only tried buying that app after reinstalling all the other apps I had bought for my previous WP so I can't say about that issue.
I think I will just hang onto the handset until the Tango update is released and hope that resolves the issues.
UPDATE: Looks like marketplace is now notifying me of app updates correctly now and the app purchase I made has no gone through. I guess something was maybe going on with MS's side of things. I'll just deal with the keyboard/dial pad delay thing and hope Tango fixes it, it's only delayed on the first character I enter when I start typing anyway.
92GTA said:
UPDATE:I'll just deal with the keyboard/dial pad delay thing and hope Tango fixes it, it's only delayed on the first character I enter when I start typing anyway.
Click to expand...
Click to collapse
A temporary fix is just to turn off the "key press" sound. Once sound is off, there is no delay. Same issues with the Focus S and my Titan 2.
xs2k said:
A temporary fix is just to turn off the "key press" sound. Once sound is off, there is no delay. Same issues with the Focus S and my Titan 2.
Click to expand...
Click to collapse
Thank you, that worked! I wonder why some windows phone have this issue and some don't? Perhaps the quality & latency of the nand flash? I have noticed this phone is a little slower than my Arrive was.
I had the exact same keyboard / touch screen delay issue. Turning off the keybaord sound definitely seems to have fixed the issue. Thanks.
I had a Lumia 900 and trades it for the HTC Titan II because of the camera issues with the Lumia. The HTC is better in my opinion but the tap delay issue was a real pain and I did not experience it with the Lumia.
I'll give it a shot, too as I have the delay. I also swapped out my Lumia for a Titan 2 and very much prefer it.
I have exactly same issue on my titan II.
I used focus before titan II. But focus hadn't this issue.
I think it can be fixed but now I feel inconvenience a lot.
92GTA said:
Phone details are in my signature. I reset the phone right out of the box as I always do when new phones or after doing a software upgrade.
I've noticed that marketplace isn't notifying me of app updates available.
When I buy something, it keeps says I have to buy over and over again and never lets me download the app even though I get the email confirmation from MS.
The on-screen keyboard, at the password screen or even when I go to start a text, there is a full 1 second delay or more in the first letter/number I push, always. Is this a defect in the touch screen or software?
My old WP7 had none of these issues.
Anyone else?
Click to expand...
Click to collapse
Re-flash the ROM with stock ROM. HTC they have serious problems in doing their initial setup. I had problems with my 2 HTC devices, and flashing helped me.
jazeelkk said:
Re-flash the ROM with stock ROM. HTC they have serious problems in doing their initial setup. I had problems with my 2 HTC devices, and flashing helped me.
Click to expand...
Click to collapse
Do you have the stock ROM for the Titan II?
Anybody please help with htc stoke rom for titan 2, thanks
Stock ROM is much appreciated ! Anyone with some information ?
i too had the keyboard issue, but have mostly gotten used to it, but it would be nice to have it fixed while keeping the keyboard sound.
another issue im having is more hardware related- when i press lightly, on the edges of the screen, there is a "glow" around the area i press like on a pc when you touch the screen. i can also feel the screen around the edges bending slightly, like the screen is loose. anybody else have this?
i have never had this on anything else with a touchscreen- ive had 2 iphones, a samsung gs2 skyrocket, and an asus transformer prime
mbucks911 said:
i too had the keyboard issue, but have mostly gotten used to it, but it would be nice to have it fixed while keeping the keyboard sound.
another issue im having is more hardware related- when i press lightly, on the edges of the screen, there is a "glow" around the area i press like on a pc when you touch the screen. i can also feel the screen around the edges bending slightly, like the screen is loose. anybody else have this?
i have never had this on anything else with a touchscreen- ive had 2 iphones, a samsung gs2 skyrocket, and an asus transformer prime
Click to expand...
Click to collapse
That is probably because of the unibody design they've opted for. This issue is much similar to what annoyingly cheap hardware feeling I get when I press hard on "Windows" softkey. You can feel the spring and at times it makes that cracking sound too. But from what I've read around, as time passes on with these unibody designs, the back case get lose and so does the front chasis. Probably that "glow" you are referring to is due to lose screen chasis?
drupad2drupad said:
That is probably because of the unibody design they've opted for. This issue is much similar to what annoyingly cheap hardware feeling I get when I press hard on "Windows" softkey. You can feel the spring and at times it makes that cracking sound too. But from what I've read around, as time passes on with these unibody designs, the back case get lose and so does the front chasis. Probably that "glow" you are referring to is due to lose screen chasis?
Click to expand...
Click to collapse
no one else has this? because the phone is brand new and did this out of the box
I'm actually having this problem as well new right out of the box. But also its not only the keyboard sound but sound in games as well. When I play games its really glitchy as the game will pause for a split second when there is a long enough gap in sound.
I bought the phone new in box unopend off craigslist for my girlfriend so im not sure if I can get this warrantied. Additionally I tried flashing the stock rom like people have been suggesting but with no luck the issue is still present.
Its a shame that such a nice phone could have such a frustrating problem right out of the box. My first gen wp the HTC Arrive never had this issue. Yet I really haven't seen much online or a fix expect whatever has been said on this thread.
Can my girlfriend just simply activate the phone and take it to at&t and get it replaced without proof that she bought it at the store?
NIKOKAPS said:
I'm actually having this problem as well new right out of the box. But also its not only the keyboard sound but sound in games as well. When I play games its really glitchy as the game will pause for a split second when there is a long enough gap in sound.
I bought the phone new in box unopend off craigslist for my girlfriend so im not sure if I can get this warrantied. Additionally I tried flashing the stock rom like people have been suggesting but with no luck the issue is still present.
Its a shame that such a nice phone could have such a frustrating problem right out of the box. My first gen wp the HTC Arrive never had this issue. Yet I really haven't seen much online or a fix expect whatever has been said on this thread.
Can my girlfriend just simply activate the phone and take it to at&t and get it replaced without proof that she bought it at the store?
Click to expand...
Click to collapse
I found that if you turn off key press sounds and disable the sound enhance, the phone works much much better.
hi,
i have this issue, everytime i make a call, once i press the call button, screen goes black, and i need to press the main button in the back to get it back, but sometimes it stay black and i can t hangup wich is a pain.
do you also have this? any idea how to adjust or remove that?
thxx for your time
I also have this priblem， Don't know how to fix it
Sent from my LG-H961N using Tapatalk
glad to know i am not the only one!
even it s no fun to have this bug...
Do you have a full screen protector? A case that covers or youre covering the light sensor next to the speaker?
yes i do, you think that can be the cause?
clockcycle said:
Do you have a full screen protector? A case that covers or youre covering the light sensor next to the speaker?
Click to expand...
Click to collapse
actually it s not a full screen protection, it s the film that was on the screen when i bought it.
light sensor works fine
I got mine fixed by calibrating the motion sensor in display settings.
Sent from my LG-H961N using Tapatalk
Just did it but when i make a call, once i press the dial button, screen turns off
Sounds like your proximity sensor is covered up or not working. Do you have a screen protector or anything on the phone which might interfere with it? If so maybe remove it and retry. Also I'm sure you could find an app that would check it.
nocomp said:
hi,
i have this issue, everytime i make a call, once i press the call button, screen goes black, and i need to press the main button in the back to get it back, but sometimes it stay black and i can t hangup wich is a pain.
do you also have this? any idea how to adjust or remove that?
thxx for your time
Click to expand...
Click to collapse
The Software is buggy and LG is not doing anything about it . I tweeted to them so many times and i thought HTC was bad.. they were amazing .. my first and last LG device .. however i am just confirming its not always proximity sensor issue .. Its the buggy software implementation.
i quite agree with you.... any idea when we get 6.0 ?
Would it be software? If we all have the same phone with the same software then we would all have the same problem, but we don't?
It's a software bug... Rebooting the phone fixed the problem， but then it starts acting the same way after few calls.
Sent from my LG-H961N using Tapatalk
You could try( if you haven't already), wiping your sensors. They sometimes get dirty & don't work properly.
I have same issue and have no protectors or covers or nothing just the stock phone. I think it's got to be some stupid software issue and it is very irritating. Went from one ridiculous phone into another headache...
warriorvibhu said:
The Software is buggy and LG is not doing anything about it . I tweeted to them so many times and i thought HTC was bad.. they were amazing .. my first and last LG device .. however i am just confirming its not always proximity sensor issue .. Its the buggy software implementation.
Click to expand...
Click to collapse
Drama much? The phone has been out for barely more than a month... and not every phone is having this issue.
Process: Collect as many bug reports as possible, recreate and fix issues, release a patch.
LG is not going to release a patch just for your particular problem because you tweeted really hard.
carbon12 said:
Drama much? The phone has been out for barely more than a month... and not every phone is having this issue.
Process: Collect as many bug reports as possible, recreate and fix issues, release a patch.
LG is not going to release a patch just for your particular problem because you tweeted really hard.
Click to expand...
Click to collapse
Retarded much ? I did not tweet to them about this problem, many people did. I tweeted then wrt their update roadmap and yes the phone should not be out in the first place if it has such obvious bugs you are clearly not aware how responsible companies work. I rest my case. If you are happy then enjoy.
warriorvibhu said:
Retarded much ? I did not tweet to them about this problem, many people did. I tweeted then wrt their update roadmap and yes the phone should not be out in the first place if it has such obvious bugs you are clearly not aware how responsible companies work. I rest my case. If you are happy then enjoy.
Click to expand...
Click to collapse
My phone doesn't exhibit this behavior. I just get tired of all the worst phone ever, LG how could you?? posts in this group. It's ridiculous. Get over yourself.
carbon12 said:
My phone doesn't exhibit this behavior. I just get tired of all the worst phone ever, LG how could you?? posts in this group. It's ridiculous. Get over yourself.
Click to expand...
Click to collapse
Well people value their money and thats why when they feel they have inferior product the will complain. Like micro scratches on the screen, bleed on second screen, back peeling off .. and if you dont have this issue does not mean these issues dont matter and it also means serious quality control issues at LG. You for one needs to get over yourself and respect other people's problems, i have none of the above problems except the software bugs, i still feel compassionate towards fellow community members who might have recieved inferior quality devices. I clearly understand your personality type, "I dont care if the whole world goes to hell if i dont have a problem i am good." You should try to be less selfish and i am sure i am not the first one in your life to call you selfish. Think about why those people think you are selfish.
nocomp said:
hi,
i have this issue, everytime i make a call, once i press the call button, screen goes black, and i need to press the main button in the back to get it back, but sometimes it stay black and i can t hangup wich is a pain.
do you also have this? any idea how to adjust or remove that?
thxx for your time
Click to expand...
Click to collapse
Firstly, Take a chill pill all
All u need to do is adjust the timeout time [emoji6]
Search within settings for "timeout"
Or go to Display settings
sent with Hugz from my new fully stock, non-rooted VZW LG V10 VS990 which an old faithful still working Rezound helped me to afford to get
way back Google has acknowledged this issue and hoping it will be fixed in Android 7.0 update, but still there. This issue seems to be related to the noise-cancelling mic found on the back of the device.
I know some people posted some workaround such as covering up the mic fixes the issue, or persist.audio.fluence.voicecall=true, and changing it to false in build.prop (if rooted, which I am not).
I know there are tons of post related this (searching Google gives many of them), I was just wondering if anyone seen any improvement after 7.0 update or pretty much the same or any other workaround that worked for you..
share your thoughts and findings would be great..
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Smallsmx3 said:
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Click to expand...
Click to collapse
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
jazzespresso said:
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
Click to expand...
Click to collapse
Did you get it from Google?
Smallsmx3 said:
Did you get it from Google?
Click to expand...
Click to collapse
No. I got it from BestBuy couple months ago...checked with Google, and re-turn period is over for this phone, and BestBuy has 90 days return, which is also over...
and I know noise cancelling mic. is there for a good reason, but it is better people can hear me when I speak is more important, so I am planing to put a small tape on mic back of the phone and give a try and see if any improvement...
other than, I really love my Nexus 6P, but this small annoying issue really really bothers me..
If it's a hardware issue why does it work fine when your in speaker phone? At least mine does.....
Sent from my Nexus 6P using XDA-Developers mobile app
Mine also works fine in speaker mode, using the handset speaker everyone always complains about the quality
Sent from my Nexus 6P using Tapatalk
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
mrsean said:
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
MedicStuder said:
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Click to expand...
Click to collapse
You just quoted someone that said he fixed his in safe mode and then you said it's for sure a hardware issue......?. It could be a hardware or software issue depending on you situation. I believe mine is software because it works great in speaker phone.
Sent from my Nexus 6P using XDA-Developers mobile app
skw5115 said:
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hello there!
Same problem here, opposite side is always telling me, that I sound like from garbage/drain or some pipe and also opposite side has echo of it's voice, so practically they hear only themselves with echoes and me very bad or not at all...
I'm using my 6P with Spigen Rugged Armor, and I also tried to make calls without it, and it looked like it's better, so I tried another cover case - Nilkin Perfect Fit, same problems as Rugged Armor and now for the third time, I'm trying Spigen Thin Fit and don't be surprised, it's all the same. So again I tried to use phone without cover and problems appeared same as with cover, so there is no straight connection between cover and these problems in my opinion!
I was preparing to make a ROOT and disable back microphone, but I've read some posts about it and decided to try RMA first, I will come back, how it will end up.
I have the same problem, but only when using the internal mic. Other end says I sound muffled, and I'm only 10" away from the mic. I have to be about an inch or so away and NOT on speaker for them to understand me. I can hear them clear as can be. I have the Unicorn Beetle case, and the noise canceling mic isn't covered, or dirty. I'll try a reboot into safe mode, call, and reboot again. Of course, it could also be just certain people are having a hard time hearing me. I'll see what I can come up with.
Originally Posted by mrsean
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
This worked for me. Thx!
For those who sufferef from muffled voice/bad microphone, try loose the screw at the bottom back of your 6p, you have to open the cover first by using guitar pick/cutter>loose the screw (centre)>put the cover back> completed. No complaint from the other end at all.
Stock 6p, dp4
Solution- Safemode restart...
Thanks guys..I just tried the Safemode restart and it worked perfectly. Then restart in normal mode and the interference could be heard again..so it's one of the apps..not the handset. Thanks again, saved a lot of hassle by avoiding the RMA nightmare.
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
EvoX2008 said:
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
Click to expand...
Click to collapse
Turn the "speaker" line back to true.
Geezerooo said:
Turn the "speaker" line back to true.
Click to expand...
Click to collapse
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
EvoX2008 said:
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
Click to expand...
Click to collapse
Did you reflash the correct vendor?
https://www.asus.com/zentalk/forum.php?mod=viewthread&tid=120244&extra=page=1&mobile=2
It should take some time to update, still talking to asus though on the bootloader for the 5.7, still awaiting that answer. However yay finally.
Darkdragontc said:
It should take some time to update, still talking to asus though on the bootloader for the 5.7, still awaiting that answer. However yay finally.
Click to expand...
Click to collapse
Only real difference I've found so far is the always on backlight and the allways on screen, though if you have a case that turns screen on/off it kills that function...
Haven't made any calls so can't comment on that.
The update is around 200mb... It's not Android 7...
ultramag69 said:
Only real difference I've found so far is the always on backlight and the allways on screen, though if you have a case that turns screen on/off it kills that function...
Haven't made any calls so can't comment on that.
The update is around 200mb... It's not Android 7...
Click to expand...
Click to collapse
It would have been nice if there was also an always off for the backlight. I guess they skipped my request I can't imagine someone would want the backlight keys on all the time. To each their own I guess. They said there were camera improvements, but I haven't tested that out yet.
pacattack81 said:
It would have been nice if there was also an always off for the backlight. I guess they skipped my request I can't imagine someone would want the backlight keys on all the time. To each their own I guess. They said there were camera improvements, but I haven't tested that out yet.
Click to expand...
Click to collapse
The Always On back light for the keys for me is quite useful when operating the phone in the dark. It it the same as a computer keyboard with back light. I'm glad they added this feature, otherwise it's as good as not having any back light at all for the keys.
I also see a definite improvement in the audio quality. Earlier while playing tracks with silence, there was a slight hissing sound (using audiophile headphones) and I had reported this to Asus. I checked this now with a few tracks and it seems like this is fixed. I hear absolutely no hissing and the audio is crisp and clear even at high volumes. !
rynaus said:
The Always On back light for the keys for me is quite useful when operating the phone in the dark. It it the same as a computer keyboard with back light. I'm glad they added this feature, otherwise it's as good as not having any back light at all for the keys.
Click to expand...
Click to collapse
That's interesting. At night is when the backlight annoys me. I'd prefer they don't ligh up. Glad they made someone happy though. I'll still wait and hope for an always off feature.
pacattack81 said:
That's interesting. At night is when the backlight annoys me. I'd prefer they don't ligh up. Glad they made someone happy though. I'll still wait and hope for an always off feature.
Click to expand...
Click to collapse
Definitely put in your requests through email and at the zentalk forum. Could be coincidence, but I almost feel like the 'always on backlit' was done at a specific person's request (seen here) because it was early on and they were so vocal on the forum for this issue. Also the forum's audience isn't that big - so more of a chance to be heard.
The Simple said:
Definitely put in your requests through email and at the zentalk forum. Could be coincidence, but I almost feel like the 'always on backlit' was done at a specific person's request (seen here) because it was early on and they were so vocal on the forum for this issue. Also the forum's audience isn't that big - so more of a chance to be heard.
Click to expand...
Click to collapse
Thanks for the idea. I signed in, but unfortunately it won't let me post to that board. I wonder why?
Hello everyone, I just got this tablet today and I'm having an issue with it. I was trying to play a music game and I noticed that when I touched both extremes of the screen the multitouch would release my fingers for some reason. I've recorded a video of it using a multitouch application just to make sure I wasn't going crazy, here it is:
Link to the Youtube video
Do you think it's defective? If anyone has this M5 10 tablet could you test it for me and see if you also have the same multitouch issue? Since I just got it today, should I return it? Or is it something that can be fixed?
Thank you.
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
RubyRP62 said:
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
Click to expand...
Click to collapse
This stuff happens Thanks for testing it out! This one is going back
I have the same problem bro! You can find my post here: https://forum.xda-developers.com/showthread.php?t=3777471
I have already open a ticket on the support
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
andrgin said:
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
Click to expand...
Click to collapse
Hi Andrgin, which is your problem? In my case I have the problem only if I touch the screen with two fingers. In this case seems that the tablet, after 2 sec, can't recognize anymore the touch. I'm waiting the response of the support for the ticket that I opened, hopping that they can tell me that is only a software problem and not an hardware issue, let's see...Anyway I have your idea too, I bought this tablet to play music game and is really useless with this problem.
When I touch the screen with 2 fingers at the same time and do not move them for about 1 second the tablets looses the touch of both fingers. It does not happen if I dont put both fingers down at the same time (more than about 500ms), move the fingers around while they touch the screen. Also it does not happen with 3 or more fingers.
To me it seems like the system treats the as a gesture.
I made a video about it:
youtu.be/PXXakOw_1Hk
I also thinks that the system treats this as some kind of a weird gesture. I don't think it is related to the hardware. I'll ask the Huawei support soonish because it really is annoying with cytus 2 for example or even pdfs when you want to pan soon and have 2 fingers on it and then your touch input gets removed.
This is with the 10 pro
Could it be, I hope that you are right but is really strange that only some devices have this problem, if it is a software problem, all the devices with this software need to have the issue.
I think all have this problem. So far everybody that said he does not have this bug had tested it the wrong way. You have to place both fingers at the same time and do not move them. If you move them while touching the screen it still works.
And no I dont think it is hardware related.
I also experienced this (talked about it in another thread), but it must be more complicated than that.
It's not something that systematically happens whenever i put two fingers down a the same time. It works just fine most of the time, but occasionally notes will drop, always in the same spots, in the same songs. "Pointer location" shows the touch is still being registered, if that's anything to be trusted.
I'll take the occasion to ask again since there seem to be other people who play music games in this thread: beside the touchscreen issues, has anyone noticed a slight delay on the audio feedback? I'm talking about a 100-150 ms delay from the moment i touch the screen to the moment the corresponding sound effect plays. The touch itself is registered correctly, but the audio lags behind for some reason.
Either way, i sent back the 10.8", gonna have the 8.4" here by tomorrow i hope, will update on how this one behaves.
It does not matter where you place your fingers only that it happens at the same time (less than about 500ms) and you dont move them for about 1 second.
About audio I dont know. Most time I had sound off.
It may be a general Android Oreo bug, although the article speaks about Android 8.1, not 8.0:
https://www.xda-developers.com/android-8-1-oreo-multi-touch-bug-fixed-june-update/
Maybe Huawei used parts of Android 8.1 for the M5.
A fix from Google is planned for the June security update.
Just tested the 8.4", after installing the new update. Interestingly enough, it didn't seem to drop any inputs.
The sound delay, however, is exactly the same, and it baffles me no one else seems to notice it.
On top of that, i think i got a defective unit, as the charging speed starts off at 3300-3400 mAh, then drops to 500-600, never to rise again. So much for quickcharge.
Battery also seems to run considerably hotter for no apparent reason: 37 degrees Celsius while charging at that pitiful speed, no other apps running.
For reference, the 10.8" never exceeded 32 degrees, and that's while charging at max speed, with apps running at the same time.
Overall, this tablet has been nothing but a huge disappointment, i'll just refund it and wait for something else to come out at this point.
Edit: it charges normally when the screen is turned off. When the screen is on, the charger seems to provide enough current to offset whatever i'm consuming, plus those 500-600 extra mAh, so no matter what i'm doing that speed doesn't change. The 10.8" was charging normally, full speed minus whatever power i was drawing, so i'm still pretty sure something's not right.
@chris_g I really hope it could be the problem but wait two more months it's really frustrating! For now I haven't received yet one answer from the support...
Not really good news from Italian support, them tell me that no reports was received about our problem, so them suggested me to try to reset the device to the default to see if is a software problem. Did you guys found something else? I'm really thinking to request the replace of the device.
Just to be sure, could someone give me the mail of the international/English support? I want to try to write a mail also to them.
Cheers
I got the M5 Pro from amazon.it and the warranty check showed that I get warranty in most European countries. I opened a ticked with the Austrian support providing all the info they needed. They said they dont know of the problem so far and will forward it. This was over 1 week ago and I did not receive any response yet.
Replacing the tablet will not solve anything because every M5 (at least the 10" versions) have this bug.
And no it is not an Oreo bug because my Mate 10 (also EMUI 8.0) works fine. I guess it is some code Huawei added to support the pen.
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
andrgin said:
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
Click to expand...
Click to collapse
Don't be so optimistic on that one, as Google themselves introduced an all new multi-touch bug in the 8.1 base. Thus one bug will maybe just be replaced by another one, as Google already stated that they'll have the bug fixed in the June update soonest. Let's hope Huawei uses the patched June base to upgrade our tablet to 8.1.
Sent from my HTC U11 using XDA Labs
Huawei already ships Android 8.1 with the P20 so I guess we are getting the same code. I never heard about multi touch problems there so I guess Huawei has already replaced that faulty Google code. With all the people complaining about late Android updates for existing devices, but there is a reason most vendors wait until they release a new Android version for the masses. Google phones are simply beta test devices.
I have the 8.4" wifi model. It suffers the multi-touch problem but not the sound delay problem. I tried the drum pad app, sounds play instantly as soon as I touch them.