Hi there,
I do not own this phone, but the Compact version, however I have tried both models extensively. I have been VERY pleased with the phones, but when I started playing PUBG Mobile I detected something odd, that avoided me to aim properly, sometimes the touchscreen wouldn't track the touches when they are very slow or precise.
I could try this in the XZ2 (not Compact) as well, and there's definitely a problem with the screen sensitivity, I'm not sure how to define it, but it feels like a dead zone that moves with your finger. The phone will not detect small movements, kind of a precision problem. The tracking is just not good enough.
I have a video and pictures to demonstrate the issue, comparing the sensibility to my other phone (Galaxy S8):
https://www.youtube.com/watch?v=Vc55o-36uC4&feature=youtu.be
And a picture:
https://imgur.com/a/LIzyV
I'm returning the phone, and I'll buy again if Sony fixes this via software (I hope they will!). I will gladly replace my S8 with this XZ2 Compact if we ignore this problem.
Comments are welcome.
Same problem with my XZ2 there's a dead zone easily noticeable when doing smalls movements on the touchscreen. FPS games are unplayables.
There's also huge imput lag like 150ms +
I will keep my XZ2 because I'm very pleased with it and I don't play games but I do not recommand this phone for gamers.
I hope it's software issue
Seb122 said:
Same problem with my XZ2 there's a dead zone easily noticeable when doing smalls movements on the touchscreen. FPS games are unplayables.
There's also huge imput lag like 150ms +
I will keep my XZ2 because I'm very pleased with it and I don't play games but I do not recommand this phone for gamers.
I hope it's software issue
Click to expand...
Click to collapse
Have you tried to contact Sony support? I'm a bit frustrated, they told me to apply whatever update there is, perform a factory reset, run the device diagnostics, and if the problem persists, that means it is hardware and I should contact local support to get it repaired or exchanged. They closed my support ticket after giving that response, without waiting for my response.
They obviously didn't understand or care about the issue here. The screen diagnostics test is passed, but the issue is still there.
I don't know what to provide in order to get somebody from Sony support look at the case and evaluate escalating the ticket to whatever team that handles bugs.
This is oreo problem actually. I'm surprised not many people realize this. I'm a YouTube tech reviewer and tested many phones. So far I've encountered this problem on oneplus 5t, Huawei p20 pro, and now xz2 all on oreo.
Oreo running phones that are free from this problem is s9, mi mix 2s, pixel 2 xl (though it has multi touch problem)
Allesa said:
This is oreo problem actually. I'm surprised not many people realize this. I'm a YouTube tech reviewer and tested many phones. So far I've encountered this problem on oneplus 5t, Huawei p20 pro, and now xz2 all on oreo.
Oreo running phones that are free from this problem is s9, mi mix 2s, pixel 2 xl (though it has multi touch problem)
Click to expand...
Click to collapse
So do you think this could be a software problem? If that's the case this may be solved with software update.
Has someone contacted and received an oficial comfirmation from oneplus, Huawei or Sony that they are aware of the problem? If it happens only on oreo maybe someone with technical knowledge can ask on google android forums.
Allesa said:
This is oreo problem actually. I'm surprised not many people realize this. I'm a YouTube tech reviewer and tested many phones. So far I've encountered this problem on oneplus 5t, Huawei p20 pro, and now xz2 all on oreo.
Oreo running phones that are free from this problem is s9, mi mix 2s, pixel 2 xl (though it has multi touch problem)
Click to expand...
Click to collapse
I have to admit when I saw your post I thought you were confusing this problem with some input lag or delay, and was very skeptic about your opinion. My apologies, because in the afternoon I went to some tech store and confirmed what you said, you're totally right. As you mentioned, I don't understand how is not everybody talking about this! Hawei P20 = same issue, Nokia phones = same issue (but maybe less pronounced). Only Samsung, Xiaomi and LG phones were free from it.
Then I went home and started googling, and people complained about similar things on the Pixels before the 8.1 update, and in the essential phone before the 8.1, etc. so basically in those phone that have "cleaner" android or closer to AOSP. Google messed up something in 8.0, ***probably*** fixed it in 8.1, but introduced the infamous multitouch issue instead.
The puzzling thing is that the previous generation, the XZ1, doesn't have this problem. Also came out with Oreo already.
Please let us know what is the name of your YouTube channel, you earned a lot of credibility for me with a single post
Although i'm very grateful for the explanation and trying to believe it, some things don't match together.
First i have to say that also my not yet mentioned U11 does not suffer from this problem.
I also tried the honor 9 some months ago and that device had similar issues (but worse) on Android 7 and 8, no difference.
Saying that 8.1 might solve it - don't you think there is a way the manufacturers COULD do it themselves before?
Flynnchen82 said:
Although i'm very grateful for the explanation and trying to believe it, some things don't match together.
First i have to say that also my not yet mentioned U11 does not suffer from this problem.
I also tried the honor 9 some months ago and that device had similar issues (but worse) on Android 7 and 8, no difference.
Saying that 8.1 might solve it - don't you think there is a way the manufacturers COULD do it themselves before?
Click to expand...
Click to collapse
You're totally right. The assumption here is that the error originated in AOSP but can be fixed by manufacturers as well, not only by Google.
Or maybe we are taking the wrong approach and it's exclusive to digitizers produced by certain manufacturer, like Synaptics, goodix, etc.
All in all, we can be 90% certain that it's a software thing. Potentially connected to some hardware choices from manufacturers, but almost definitely fixable by software, if they put the effort.
CaraMuuu said:
I have to admit when I saw your post I thought you were confusing this problem with some input lag or delay, and was very skeptic about your opinion. My apologies, because in the afternoon I went to some tech store and confirmed what you said, you're totally right. As you mentioned, I don't understand how is not everybody talking about this! Hawei P20 = same issue, Nokia phones = same issue (but maybe less pronounced). Only Samsung, Xiaomi and LG phones were free from it.
Then I went home and started googling, and people complained about similar things on the Pixels before the 8.1 update, and in the essential phone before the 8.1, etc. so basically in those phone that have "cleaner" android or closer to AOSP. Google messed up something in 8.0, ***probably*** fixed it in 8.1, but introduced the infamous multitouch issue instead.
The puzzling thing is that the previous generation, the XZ1, doesn't have this problem. Also came out with Oreo already.
Please let us know what is the name of your YouTube channel, you earned a lot of credibility for me with a single post
Click to expand...
Click to collapse
K2 gadgets is my YouTube channel but it is in Indonesian lol..
My wife's u11 on 8.0 suffers from this problem, but its not as pronounced. I can only experience it if I track REALLY slow and accurate, then the sudden jump in movement can be seen. not as pronounced as in the xz2.
The fact is that when we use touchscreen tester app, it detects instantly our finger touching the screen, but not detecting incremental movement after that. So I think it is not touchscreen lag. I think it's a matter of software problem, most likely a Google screw up. A driver/preference file such as this one https://www.xda-developers.com/fix-multi-touch-bug-google-pixel-2-xl-android-oreo/ may fix the whole thing.
It is like the phone intentionally disregarding slight movements on the screen as accidental swipes.
Why on earth this problem is not well known since it is happening in a lot of phones? I guess not many people move their fingers in such ways as avid fps gamers :laugh:
I have this problem too. Can't properly play Street Fighter IV CE. After 51.1.A.3.159 firmware update situation is much better but not 100% good.
Allesa said:
K2 gadgets is my YouTube channel but it is in Indonesian lol..
My wife's u11 on 8.0 suffers from this problem, but its not as pronounced. I can only experience it if I track REALLY slow and accurate, then the sudden jump in movement can be seen. not as pronounced as in the xz2.
The fact is that when we use touchscreen tester app, it detects instantly our finger touching the screen, but not detecting incremental movement after that. So I think it is not touchscreen lag. I think it's a matter of software problem, most likely a Google screw up. A driver/preference file such as this one https://www.xda-developers.com/fix-multi-touch-bug-google-pixel-2-xl-android-oreo/ may fix the whole thing.
It is like the phone intentionally disregarding slight movements on the screen as accidental swipes.
Why on earth this problem is not well known since it is happening in a lot of phones? I guess not many people move their fingers in such ways as avid fps gamers :laugh:
Click to expand...
Click to collapse
I remember in the old Galaxy S2 and the likes days, had the same annoying issue.
There was an App back then that resolved the issue completely - https://forum.xda-developers.com/ga.../ref-solving-touchscreen-sensitivity-t1161262
From what I gather, the minimum threshold to register a movement is there to allow convenient "Long Press". Long press is not triggered if the user for example is scrolling through home screens, so they added the threshold. If you ask me, long press should not be part of any touch os as it slows stuff down. Apple resolved it with Force touch.... (I hate apple and iOS)
On my HTC U11 i suffer the same issues, but I don't game much so I have not tried to fix it.
Also I have not tried but, maybe you should : https://play.google.com/store/apps/details?id=apps.redpi.touchscreenrepair&hl=en
I tried touchscreen repair app but nothing changed after calibration... I doubt about this app, it seems to be fake. How does it work to modify touchscreen attributes without root acces ?
Same here
According to this thread, the value is set by the vendor and overriding a default one set to 8dip compared to 20dip in our device. In other words ACTION_MOVE event is not generated before the touch point travels the distance value in any direction. Might be wrong, though.
I also get the issues in my XZ2
I can't write fast with my keyboard.
Keystrokes are getting lost.
Here is your fix.
https://issuetracker.google.com/issues/70344455
https://forum.xda-developers.com/pixel-2-xl/how-to/fix-touch-screen-issue-t3723717
kekistaneerefugee said:
Here is your fix.
https://issuetracker.google.com/issues/70344455
https://forum.xda-developers.com/pixel-2-xl/how-to/fix-touch-screen-issue-t3723717
Click to expand...
Click to collapse
Thank you, but I need twrp or root to do this.
We don't have twrp and rooting/unlocking will kill our drm keys.
I'm not using much apps/games that requires precision, so I haven't noticed this. The only issue I had with the touchscreen of my device (XZ2c) was selecting the radio button for the APN selection of Network management settings, that required high precision, too much for such a basic action.
Has anyone tried to enable Glove mode ? It's supposed to increase sensitivity, so it might help until a better fix is found. Or actually be worse, if the phone considers "bigger fingers" and increases the dead zone.
Glove mode doesn't change the existant dead zone, was one of the first things that i tried with my xz2 compact.
Btw i got a small update (0,7mb) today but no idea what it's for. Same security level (1. April) and no change in the touchscreen behaviour.
Anyone tried the Android P beta for the XZ2 whether did they fix it?
hotcakes_shinku said:
Anyone tried the Android P beta for the XZ2 whether did they fix it?
Click to expand...
Click to collapse
I see the Android P beta thread is getting some activity, so we would be grateful if somebody paid attention to this. Thanks in advance to whoever will test it!
Related
Hello everyone. I'm trying to decide between buying a TF700 for this Black Friday, or wait a bit longer and get a Nexus 10 (it's not available in my country yet). I'd like to know if there are still technical issues with the TF700 or if they were fixed by ASUS either by software updates or by improving their manufacturing process. I've heard a lot about slow I/O on this tablet, is this still a problem ? Are there other thing I should be aware of when purchasing (like the screen lift on the Nexus 7) ? Thank you
There are several things you should be aware of including:
Screen lift
screen bleed
Slow IO
Slow stock software
low quality volume buttons(really low feels extremely cheap)
Dead pixels
Also the keyboard dock might cause some damages to the tablet itself depending on the usage.
Well i bought mine 3 weeks ago and i still have the slow IO and the screen lift/screen bleed and needed to change to custom rom to make it
usable..
i believe that alot of these issues will never be solved...
also asus has some of the worst support i have ever experienced so long story short dont buy unless you are happy with a slow
buggy and Defect high end device that might end up destroying itself for no reason
Trying to get the screen lift and screen bleed repaired while being unlocked seems impossible as asus rejects it. atleast thats what they are doing to me.
Slow I/O and slow stock software is all I have. I have no hardware-related problems, like the ones mentioned above. If I had, I would probably have traded it in before I unlocked it.
papand7 said:
Screen lift
Click to expand...
Click to collapse
not my Infinity
screen bleed
Click to expand...
Click to collapse
not my Infinity
Slow IO
Click to expand...
Click to collapse
that's true. But if you want to unlock your device, there is a workaround!
Slow stock software
Click to expand...
Click to collapse
that's not true
low quality volume buttons(really low feels extremely cheap)
Click to expand...
Click to collapse
not important for me!
Dead pixels
Click to expand...
Click to collapse
i don't have dead pixels
Also the keyboard dock might cause some damages to the tablet itself depending on the usage.
Click to expand...
Click to collapse
i use the keyboard dock a lot and have no damage on my tablet
Well i bought mine 3 weeks ago and i still have the slow IO and the screen lift/screen bleed and needed to change to custom rom to make it
usable..
Click to expand...
Click to collapse
IMO it's very usable with stock, but with CustomRom this Tablet is outstanding!!!
i believe that alot of these issues will never be solved...
Click to expand...
Click to collapse
...but you don't know, except the I/O issue
also asus has some of the worst support i have ever experienced so long story short dont buy unless you are happy with a slow
Click to expand...
Click to collapse
that is also not true, ASUS bringing updates very quick
buggy and Defect high end device that might end up destroying itself for no reason
Click to expand...
Click to collapse
I'm extremely happy with my TF700!!!
The thing is this: Happy people are quiet people. They don't bother to go somewhere and leave a positive review. So what you'll find here is a handful of grumphy users, only a tiny segment of the thousands of buyers.
I'm very happy with my Infinity. No issues at all.
So a few games in the Playstore are listed as incompatible. How is this the device's fault?! (Yes, people are seriously whining about that.) That's like saying it's your cat's fault they don't sell Whiskas in the shop... Bloody ridiculous. The games work fine, anyway.
And yes, copying is a little slow. Ever tried to copy 3GB worth of images in Windows? Same bloody thing.
And the volume keys are perfectly solid. they don't wobbly, nothing. Respond immediately, too.
I use the keyboard literally all the time, as I also use it as a screen protection during travel. (and I write. A lot.) What damage? Stop spouting nonsense.
I had to Google screen bleed to know what the hell they meant. Nope, none to be found.
It's not slow. Stop trying to watch a film while you're gaming.
And I got mine a week before the release. so the first production line. (As the European Mainland also got it earlier than the US)
ShadowLea said:
The thing is this: Happy people are quiet people. They don't bother to go somewhere and leave a positive review. So what you'll find here is a handful of grumphy users, only a tiny segment of the thousands of buyers.
I'm very happy with my Infinity. No issues at all.
So a few games in the Playstore are listed as incompatible. How is this the device's fault?! (Yes, people are seriously whining about that.) That's like saying it's your cat's fault they don't sell Whiskas in the shop... Bloody ridiculous. The games work fine, anyway.
And yes, copying is a little slow. Ever tried to copy 3GB worth of images in Windows? Same bloody thing.
And the volume keys are perfectly solid. they don't wobbly, nothing. Respond immediately, too.
I use the keyboard literally all the time, as I also use it as a screen protection during travel. (and I write. A lot.) What damage? Stop spouting nonsense.
I had to Google screen bleed to know what the hell they meant. Nope, none to be found.
It's not slow. Stop trying to watch a film while you're gaming.
And I got mine a week before the release. so the first production line. (As the European Mainland also got it earlier than the US)
Click to expand...
Click to collapse
I wholeheartedly agree. If you search this forum you'll find lots of complaints of issues both real and unrealistic. I think many of the users with lag issues are pushing the tablet way beyond reasonable expectations. They represent a tiny portion of Infinity owners, the rest of whom are quite satisified the the tablet's quality, including myself.
Firebrazer said:
Slow I/O and slow stock software is all I have. I have no hardware-related problems, like the ones mentioned above. If I had, I would probably have traded it in before I unlocked it.
Click to expand...
Click to collapse
Well if i had known that the tablet would begin to have screen lift which would then escalade and cause screen bleed after the first 3 weeks of use.
i sure wouldnt have bought or unlocked it in the first place... it had nothing when i got it... i have done nothing to cause these problems..
i always carry my tablet in a sleeve and never even leaves it laying on a table without placing it on top of the sleeve...
also the volume rocker is getting looser and looser the more i use it which is getting on my nerves
and actually i do know that the hardware issues will never be fixed.. as they never did on the tf200....
and btw i see no usable workaround for the slow IO speeds as i need the micro sd card slot and have more than one card.. so i cant just be limited to a non removable sd card due to data2sd..
and actually i do know that the hardware issues will never be fixed..
Click to expand...
Click to collapse
That seems like something ASUS would do (or rather won't do). I have gone through 2 Nexus 7, both C90 that had the exact same issues that plagued the first batches (C50 and such). I returned them both and decided to choose a higher tier price product. I wasn't expecting something in this price range to have so many issues. Hope the Nexus 10 turns out better.
Some more questions :
- the problem with slow I/O, is it wide-spread ? Are all TF700 affected or only some depending on factors like : memory size, manufacturing date etc.
- does ASUS use the same numbering system as in the case of Nexus 7 ? C90 for a device made in 2012 (C in hex is 12), on the 9-th month - september ?
- is the dock really worth it, can I buy it without it for a lower price ?
1: Yes, it is very widespread. It can be fixed with CustomROMs though.
2: No idea, tbh. I haven't looked into it.
3: I believe the dock is worth it, but you can buy the tablet without it. I use the dock a lot, and it's nice to have the extra battery power. Comes in handy.
NK0d3R said:
Some more questions :
- the problem with slow I/O, is it wide-spread ? Are all TF700 affected or only some depending on factors like : memory size, manufacturing date etc.
Click to expand...
Click to collapse
It affects all units.
- does ASUS use the same numbering system as in the case of Nexus 7 ? C90 for a device made in 2012 (C in hex is 12), on the 9-th month - september ?
Click to expand...
Click to collapse
Interesting... Quite possibly so. I have a C60 and I bought it in early August. Most now I see are C80's.
is the dock really worth it, can I buy it without it for a lower price ?
Click to expand...
Click to collapse
Depends on what you use it for. It's got a USB port, SD slot and 4-7 hours of extra battery at intensive use. Plus it makes a great stand, and the keyboard is fully functional, it can be used to navigate, even. (it's 10'1"of OCD, so that helps keep the screen clean.) It also provides extra protection, as it closes like a laptop. (And charges whilst docked, even when asleep). I hate typing on a screen whilst holding said screen. it leaves marks, isn't comfortable and it gives me a sore neck. (I write entire novels. not 140 characters max.)
I don't know where you are, but some countries sell the tablet without dock, and some don't.
ShadowLea said:
The thing is this: Happy people are quiet people. They don't bother to go somewhere and leave a positive review. So what you'll find here is a handful of grumphy users, only a tiny segment of the thousands of buyers.
Click to expand...
Click to collapse
This argument is entirely correct. Forums always have a negative bias.
So a few games in the Playstore are listed as incompatible. How is this the device's fault?! (Yes, people are seriously whining about that.) That's like saying it's your cat's fault they don't sell Whiskas in the shop... Bloody ridiculous. The games work fine, anyway.
Click to expand...
Click to collapse
This ^^ and the fact that sideloading is so easy. You could even ask someone to install it temporarily and forward the apk or TiB files to you, and there are numerous sites that allow download of the apk files themselves anyway.
And the volume keys are perfectly solid. they don't wobbly, nothing. Respond immediately, too.
Click to expand...
Click to collapse
I've never understood the argument of presumably floppy volume buttons. How many times in a day do you actually adjust volume? It's practically always on Vibrate mode for me (and when I watch a movie or documentary, I changed it with a swipe on-screen -- DICE Player ftw). One of the most irrelevant arguments against the 700 in my opinion.
I use the keyboard literally all the time, as I also use it as a screen protection during travel. (and I write. A lot.) What damage? Stop spouting nonsense.
Click to expand...
Click to collapse
Same here -- only comes off when the kids play a game. I don;t have microscopically-enabled eyesight anymore (laser refraction surgery), but I cannot spot a single scratch either, no matter how tiny. Isn't that easy to accomplish on Corning's glass overall, unless you unleash unholy punishment on the screen. On any device, the odds are off, then... (I remember bragging about Gorilla Glass to some friends we were having over for dinner, and rubbing a metal spoon on the screen of my LG Optimux 2x. Very enthusiastically. It scratched. Clearly and obviously. )
I had to Google screen bleed to know what the hell they meant. Nope, none to be found.
Click to expand...
Click to collapse
Most LCD screens suffer from some form of light bleed due to the backlighting, but I've never had it to any appreciable degree on my device either.
It's not slow. Stop trying to watch a film while you're gaming.
Click to expand...
Click to collapse
Why did I not try this? Plants vs. Zombies with Stick It!-ed video. Wow. Good deal!
By the way: Plants vs. ZOmbies is a good example of a "not compatible" game. Sideload it, get the data folder from a shady site (hell, you may even pm me) and it runs. Initial loading and level endings are pretty slow, but in-game, runs nicely.
And I got mine a week before the release. so the first production line. (As the European Mainland also got it earlier than the US)
Click to expand...
Click to collapse
Breda? or Zwolle? I took a motorcycle to Breda -- had it almost three weeks before the European release. My 700 has no issues at all. Not a creak, not a lift, not a scratch. Only I/O -- all units have this -- but a cROm fixed that.
BTrack said:
I wholeheartedly agree. If you search this forum you'll find lots of complaints of issues both real and unrealistic. I think many of the users with lag issues are pushing the tablet way beyond reasonable expectations.
Click to expand...
Click to collapse
I noticied the I/O issue early, clearly and frequently. It was there on a low level as well, not only when pushing the device. As it stands, I would contest your statement.
They represent a tiny portion of Infinity owners, the rest of whom are quite satisified the the tablet's quality, including myself.
Click to expand...
Click to collapse
With the exception of ASUS'poor choice regarding internal memory (see above), the other issues are relatively infrequent (and probably not that severe in most cases; note the use of the term "relatively"). I'm *very* happy with my CleanROMmed 700.
papand7 said:
Well if i had known that the tablet would begin to have screen lift which would then escalade and cause screen bleed after the first 3 weeks of use.i sure wouldnt have bought or unlocked it in the first place... it had nothing when i got it... i have done nothing to cause these problems...
Click to expand...
Click to collapse
No, but you should've RMA'd the device. The cause is clearly on AUS'side, but you canot blame them for voiding your warranty before you actually made sure your device was OK. that's your responsibility as a buyer/unlocker. How do you know your actions (whatever they may have been) didn't cause or exacerbate the issues your device now seems to have? (I am not saying they did -- I do not know either.)
i always carry my tablet in a sleeve and never even leaves it laying on a table without placing it on top of the sleeve...
also the volume rocker is getting looser and looser the more i use it which is getting on my nerves
Click to expand...
Click to collapse
Mine is in a leather sleeve, but takes quite a beating for that scenario. No issues whatsoever.
and actually i do know that the hardware issues will never be fixed.. as they never did on the tf200....
Click to expand...
Click to collapse
No, should they magically replace parts in our devices long-distance? That would rock! Hell, if they just send that engineer, I'll make him a cup of tea -- he can even sleep in the guestroom!
and btw i see no usable workaround for the slow IO speeds as i need the micro sd card slot and have more than one card.. so i cant just be limited to a non removable sd card due to data2sd..
Click to expand...
Click to collapse
I/O is OK on CleanROM, and I do not have data2sd enabled.
NK0d3R said:
Some more questions :
- the problem with slow I/O, is it wide-spread ? Are all TF700 affected or only some depending on factors like : memory size, manufacturing date etc.
- does ASUS use the same numbering system as in the case of Nexus 7 ? C90 for a device made in 2012 (C in hex is 12), on the 9-th month - september ?
- is the dock really worth it, can I buy it without it for a lower price ?
Click to expand...
Click to collapse
1. All units are affected, and gicen ASUS'track record with the TF201, all units released to market in the future will be affected.
2. Nobody knows except ASUS. Might be worth taking to Gary Key. I have an early unit without any issues, and so have lots of others in here. I do not believe the serial number is an accurate preictor of sorts for any issues that particular device may or may not have.
3. Obviously, the device is available without the dock, but I love it. I would not even consider buying it without the dock. Prime selling point for me.[/QUOTE]
MartyHulskemper said:
Breda? or Zwolle? I took a motorcycle to Breda -- had it almost three weeks before the European release. My 700 has no issues at all. Not a creak, not a lift, not a scratch. Only I/O -- all units have this -- but a cROm fixed that.
Click to expand...
Click to collapse
Zwolle. (Bit closer ) Took them half an hour to find the thing in storage xD The idiot came back with an iPad at first. I think he's still a bit scared of me, saw him here recently at Media Markt, he ran away! xD
I'm really disappointed. Such a powerful CPU/GPU combo, such a good display (at least resolution-wise, there aren't many other Android tablets that can compete with the retina iPads from this point of view) and ASUS had to ruin it all by making these small mistakes (well, the I/O thing is not so small) and, even worse, not invest anything into fixing them. I think I'll wait for the Nexus 10 and hope that Samsung took its time designing it and ironing out all the bugs.
ShadowLea said:
Zwolle. (Bit closer ) Took them half an hour to find the thing in storage xD The idiot came back with an iPad at first. I think he's still a bit scared of me, saw him here recently at Media Markt, he ran away! xD
Click to expand...
Click to collapse
Are you such a scary lady? Mmmmh.... Hahaha! Mine was dumped in a framework container with some TF201 Primes -- unlabeled, no pricing, no advertising. The girl I asked first didn't know what I was talking about and went to some guy to ask, and he turned out to be the one who dumped them there just 15 minutes earlier. Hadn't even had the time to look up for which price they were leaving the store.
I'm sure you'll be happy to hear the Nexus 10 has ANR errors in the browser, too, then. ...Not happy with it? Oh well.
And there's plenty of Google Issue Reports regarding random freeze and reboots for the Nexus 10. This one, for instance: http://code.google.com/p/android/issues/detail?id=39879 Or even here on XDA: http://forum.xda-developers.com/showthread.php?t=1998496
Or maybe we should mention the WiFi issues? http://forum.xda-developers.com/showthread.php?t=1995833
Or maybe the Lightbleed?
How about the lousy battery life?
It doesn't have a MicroSD slot. For me, this is enough reason not to consider the N10.
MartyHulskemper said:
Are you such a scary lady? Mmmmh.... Hahaha! Mine was dumped in a framework container with some TF201 Primes -- unlabeled, no pricing, no advertising. The girl I asked first didn't know what I was talking about and went to some guy to ask, and he turned out to be the one who dumped them there just 15 minutes earlier. Hadn't even had the time to look up for which price they were leaving the store.
Click to expand...
Click to collapse
I'm generally considered rather frightening, yes.
Over here in the Media Markt they often enough don't even know it's called a Tablet, and not an iPad. They just assume iPad is the name for all tablets. And if you want a non-Apple product, they're somewhere in the far back corner behind all the junk.
The problems that seem to be hardware-related (an therefore not fixable through a software update) are the light bleed, the crappy battery life (which is not all that bad but, still, doesn't even come close to the iPad) and, maybe, the WiFi connectivity issue. I have to admit, those don't look too good. And I bet that, as time passes, more will be found. I always wondered why so many people go the iPad route instead of choosing an Android tablet. It's the apps, sure, but also the feeling of a higher quality product. So, in the end, what's the best high-res Android tablet ?
Hello there!
Now I know this has been discussed before but I will probably be buying this phone next week, and my main concern is the touch sensitivity issue.
How is it with the latest firmware? I thought it was no big deal but after seeing this video:
http://www.youtube.com/watch?v=f3mPDZfoW8o
I became quite concerned. Is this a common behavior for XL?
If so do any of the custom kernels (or Roms maybe) address this issue?
If someone could test their screen with a multitouch visualizer/tester app and post their opinion I would be grateful..
Touch sensitivity has improved a lot in 15.3.A.0.26 update.. You can go ahead and buy Xperia L..
Thanks for the reply!
See the thing is that I have also convinced my friend to buy the Xperia L and I don't want to have the responsibility for him as well if it turns out to have problems.
Is there anything else potentially serious I should know?
I read that the memory filling bug is fixed so I can't think of anything else..
I've noticed that the opinions about the touchscreen are a little different along people. It's true that the touchscreen was improved in the update, but i (this is my opinion) am not satisfied. I can't type or unlock my phone properly when i lay it down on the table(not holding in my hands). I have a screenguard, but had these problems too without it. But for the rest it's an awesome phone. If you're worried about the touchscreen, ask the seller(in the store) wether you can turn it on. I don't think it'll be much of a problem.
Hmm I see... I hope I can arrange for them to replace it and perhaps switch to another model..
What troubles me is that while I am a fan of sony in general (I like their design and the performance of their budget models) it seems that the latest line of phones all have problems with the touch screen, so even if I am tempted to spend some more and get an SP it would be a deal breaker.
I would even go for an Xperia M but the limited internal storage is bugging me (+ no apps to SD unless you swap internal and external)..
Maybe I will go for the Galaxy Ace 3 LTE which I can find for about 30 Euros more and has a little better specs (except for the camera) even if I am not a fan of the Samsung aesthetics..
maybe this link helps you
http://forum.xda-developers.com/showthread.php?t=2543980
don't buy and wait for new update.(maybe fix by new update)
The wife got me a shield for Christmas 2014. Had it for a couple months, then it started not responding or shutting down randomly. RMAed it. 3-4 months later the new tablet was recalled. Got a New one.... The new one never acted right studdered constantly. At that point I gave up, I used the tablet. But never really set it up, I just put games that I could save to the cloud with. And now it has started shutting down like the first one. So another RMA.
Am I the only one?
bucket81 said:
The wife got me a shield for Christmas 2014. Had it for a couple months, then it started not responding or shutting down randomly. RMAed it. 3-4 months later the new tablet was recalled. Got a New one.... The new one never acted right studdered constantly. At that point I gave up, I used the tablet. But never really set it up, I just put games that I could save to the cloud with. And now it has started shutting down like the first one. So another RMA.
Am I the only one?
Click to expand...
Click to collapse
The K1 is my first tablet. I'm gonna go out on a limb here and say its probably the worst tablet for $200. I've only had mine for a month. Already returned one cuz the OTA broke WiFi. WiFi sucks hard, constantly getting slow connection warnings on my favorite game (blame it on MM go ahead but my Nexus on MM doesn't have any issues), the reason I bought the tablet was to play it. Screen becomes unresponsive all the time, like 10x a day, sometimes I have to wait up to 5minutes just to open the app drawer, I've resorted to putting all my apps on my HS just to try to avoid this, doesn't help. Battery is horrid, stand by time is garbage, I have to turn it off just to have power when I want to use it again, Misc bug is not fixed. Charging is super slow, charge for hours only gains 20-30%. Support from Nvidia is non existent, posted on the support forums, not one response from anyone except users making excuses for this garbage.
I'm not rooted, completely stock, but maybe I should root to see if I can fix the issues myself but from what I read on multiple sites nothing helps. Will never buy a product from this company again. It's not just u
Yeah the software is buggy. Both Google and NV are to blame here. I've rolled back to Lollipop and Kitkat. Part of the problem is newer versions of Android tend to break apps that aren't updated anymore.
Don't expect companies to respond on forums. NV generally uses them only passively. Forums are a gas can of drama and lynch mobs waiting to explode. You can definitely contact them by other means.
swaaye said:
Yeah the software is buggy. Both Google and NV are to blame here. I've rolled back to Lollipop and Kitkat. Part of the problem is newer versions of Android tend to break apps that aren't updated anymore.
Don't expect companies to respond on forums. NV generally uses them only passively. Forums are a gas can of drama and lynch mobs waiting to explode. You can definitely contact them by other means.
Click to expand...
Click to collapse
i was contemplating about getting it becuase i need one, but it seems that unfortunately is down to the iPad or a Galaxy Tab S. As much as i dislike Sammy's SW update practice and Apple's lack of features, they are rock solid (i have both ipad air and tab s for my kids). Never had issues with them, but is time i stop hijacking my kid's galaxy tablet
I don't think the Shield is by any means a disaster. If you buy one, stay on the original Lollipop release until NV and Google get Marshmallow more refined. A lot of issues were cleared up with a recent update but it introduced wifi problems for a subset of users so they ceased distribution of it for the moment.
Shield is a neat tablet that is great for games and media. Fast for general apps too and just a great value for its price. Fun optional accessories and console mode capabilities too.
swaaye said:
Yeah the software is buggy. Both Google and NV are to blame here. I've rolled back to Lollipop and Kitkat. Part of the problem is newer versions of Android tend to break apps that aren't updated anymore.
Don't expect companies to respond on forums. NV generally uses them only passively. Forums are a gas can of drama and lynch mobs waiting to explode. You can definitely contact them by other means.
Click to expand...
Click to collapse
I totally understand about forums but if its an official NV support forum on their site I expect something from them. At least a mod response.
BTW lost 5% battery just typing this ????
I feel like the phrase "it's a good value for the price" is a weak point. It doesn't work.... If it's a good value it works.
Also not on 6.0. I really think its bad hardware and poor QC. I really don't think NVIDIA would have responded to anything.
I was looking at the Galaxy Tab A with Spen but..... The screen sucks. I like the Tab S but I wanted a pen. And there's the Zentab S... I am also playing with the wife's Surface 3 and Android emulators like Blue Stacks.
I've been using the K1 for a bit more than a month. I really haven't had much trouble with it. I've run their 4.4.2, 5.0.1, 5.1.1, and 6.0 releases on it. The problems I've had are primarily with apps not working on all OS versions and this is not really a NV specific problem.
The initial 6.0 had some quirks like the touchpad on their controller was non-functional. Yeah I have the controller. It's interesting and works well, including the gamepad mapper. There is also the apparent problem with the logd daemon hitting the CPU too much and wasting battery. I have not tried the newest 6.0 release. I'm waiting on NV to put it into the OTA system again. I'm not much impressed with 6.0 though because it's a lot like 5.x but adopted storage is not so hot and I preferred the old "move to SD" function (which is gone).
I own/have owned a bunch of different tablets and am used to fighting with Android quirks. I tend to go for fun projects like the old Nook tablets, some Chinese tablets, and Windows tablets. At the moment I have an Onda V919 Dual OS, Tegra Note 7, Venue 8 Pro, and the Shield K1. Samsung might be the way to go if you want the most solid experience. I would read the forums first on that though to be sure you aren't dreaming.
I think I might see if the replacement works. If not I'll sell it and move one.
Of course its not the best, but what do you expect for 200 bucks. That being said my only problem is the build quality, everything else works like it should. Im now since a week or so on 6.0 and everything works, its smooth and fast, no wifi issues. Performance wise its still one of the best Android devices till now, although its about 2 years old.
Here all fine...the only think i can't have working is the stylus only mode and lazo capture...back on MM update but even if I mod the build.prob nothing happen.
Waiting for 1.1 OTA
I find it bizarre that video and audio recordings created on either my S7 (which I purchased in July of 2016) or on my brand-new S7 Edge (which I just obtained yesterday) are plagued with persistent, intermittent static-type crackling sounds which can virtually ruin the shot video footage or captured audio.
But what I find even more bizarre is the fact that there are almost no posts about this problem that I've been able to find here on xda. First, I've been thinking it must be a relatively common issue considering that I've ended up with two new S7 devices that both experience it. And next, I've noticed identical pops/crackles on various YouTube videos shot with S7 or S7 Edge devices, but typically with no remarks about said noises from the individuals posting those videos. And the most peculiar thing is that I'm finding very few complaints on the Internet at large concerning the topic. Considering the huge number of Galaxy S devices in use, I would think that if this were actually a common problem there would be far more complaints out there.
Here is one thread on the topic at the Samsung support community website:
https://us.community.samsung.com/t5...s-have-strange-static-noises-at-the/td-p/1993
https://us.community.samsung.com/t5...icpage/board-id/GalaxyS/thread-id/1048/page/5
And here's the only thread I can find addressing the issue at xda (maybe I'm searching wrong?):
https://forum.xda-developers.com/galaxy-s7/help/problem-noise-clacking-popping-static-t3427910
I guess what I'm really wondering is whether I may have been unlucky enough to acquire two new devices suffering from the same rare problem? Or whether the problem is actually quite common (as suggested in the threads I've cited above where it's claimed that the issue has existed within Galaxy S devices all the way back as far as the S4)?
I would very much like to hear others' thoughts and/or experiences concerning this problem.
I have got the same issue but if i take a quick video or audio recording prior to actual video the crackling is gone... this leads me to believe that it is software based especially because it happens in the stock camera app and snapchat which just uses the camera's viewfinder instead of proper camera api's... I also think it is a software issue because apps like instagram do not have this problem when recording videos and I know instagram uses the proper api's. Some on the web say that this is a hardware issue but i really hope not. I have a 930u what model do you have?
I have a 930P and a 935P. They both do it; however the 930P only does a couple of chirps/crackles/pops on the first few seconds of the first video I've shot since at least an hour before. And if I keep shooting new videos it won't do it at all. It used to be a lot worse on the 930P. But the more videos I've shot as the months passed, the less severe the problem has become. I use the quick prior video technique you mention as well. But I can't really use it on footage that I decide to shoot on the spur of the moment when there's a surprise incident I want to capture.
I personally can't be sure whether the issue is software or hardware based. I can tell you, though, that it happens on audio (voice) recordings as well.... so it's not app-specific. And considering that the crackling usually happens when the recording software hasn't been used for a while, it almost suggests that it's a thermal issue (which would be hardware), or a electro-static charge issue (which would be hardware as well).
I'm surprised that Samsung hasn't had enough complaints on this issue to identify the cause and come up with a solution over the years. And I still don't get why more people aren't complaining about it. Whatever the answer, if Samsung repair technicians are actually able to fix this issue on the devices that people send in for having it fixed, why is it that they can't implement a permanent fix for it on their assembly lines?
I took quite a few videos yesterday with the stock Samsung camera app, 4k and 1080p 60fps on my Xynos S7 Normal and no popping or scratching noises. I do have a rubber type case on so if the popping is fingers moving on the phone that might be why I do not have this problem.
Jonathan-H said:
I took quite a few videos yesterday with the stock Samsung camera app, 4k and 1080p 60fps on my Xynos S7 Normal and no popping or scratching noises. I do have a rubber type case on so if the popping is fingers moving on the phone that might be why I do not have this problem.
Click to expand...
Click to collapse
The S7s I have are the SD820 models. I'm unsure whether any of the Exynos models suffer from this issue. But I think they may based on the regions some of the video clips I've seen (that contained the same sort of popping) have been shot in. Here's a link to one of the videos someone shot to demonstrate the problem:
https://www.youtube.com/watch?v=vj2Hd2hpnDs
With my phones it's not caused by hand or finger movements. It happens when the devices are perfectly still, even sitting stationary on a table. And it makes no difference whether a case is on or off of them.
Am I simply unlucky enough to have acquired an S7 and an S7 Edge that have this (possibly very rare) problem in common? Or is it a fairly common problem that goes largely unreported for some reason? I'm not sure.
God damn, i have that problem too. I dont notice it before
Video taken 5 minutes ago
https://youtu.be/MraHDORny4g
Sent from my SM-G930F using XDA-Developers Legacy app
olafsand said:
God damn, i have that problem too. I dont notice it before
Video taken 5 minutes ago
https://youtu.be/MraHDORny4g
Sent from my SM-G930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, you sure do. So this proves that the problem exists on the Exynos models as well. I think it also may suggest that many S7 users just haven't noticed the problem yet, like yourself. It could be that when some users hear these crackles, they think they are just background audio that was picked up during the recording. I wonder how many other S7/S7 Edge owners really have this issue but simply haven't noticed it? It's quite frustrating!
One thing I have just discovered: If I cover the bottom mic hole with my thumb and then start to record video (leaving my thumb over the bottom mic hole until I stop recording), when I play the video I've just recorded there is a muffled rushing sound for the first several seconds and the periodic pops can be heard in the background under that sound. But after those several seconds, with my thumb still over the lower mic hole, there is one final loud-ish pop, after which both the muffled rushing sound and the pops are seemingly gone. I have duplicated this 5 times so far. It has always behaved the same way. The impression I have from my testing is that upon the point at which the loud-ish pop occurs and the rushing noise vanishes, the device has somehow detected that the bottom mic has been blocked and thus auto ports its mic input instead from the device's top mic, simultaneously cutting off input from the bottom mic. Whereas if I perform a similar blocking of the top mic during a recording, nothing at all seems to happen. I can't even hear any change in noise from my finger touching the top mic hole. That is, until I force the switch by plugging the bottom mic hole.
So what does this all mean as far as the popping/crackling issue? One thing it seems to indicate is that the unwanted pops/crackles are introduced to the audio input circuitry when the device is listening through the bottom mic hole. So the problem may be within the circuitry connected to that lower microphone. If there were some way to force a permanent switch to the upper mic (or turn off the lower mic) during recording, it may solve the popping/crackling issue.
Thoughts anyone? Please test this on your devices and post back with your findings.
Wow! Here's a thread that I hadn't seen before just now (started in 2013):
https://forum.xda-developers.com/showthread.php?t=2317900
And here's a short YouTube vid that includes a discussion which I just found as well and it's right on point:
https://forum.xda-developers.com/showthread.php?t=2317900
The guy who posted the video confirms part of my findings, that the bottom mic is the one that typically produces the crackles when it's in circuit. He speculates that it may be a built up static condition on the lower condenser microphone. I was actually thinking the same thing. I mentioned it in post number 3 in this thread in fact. He mentioned that if you shoot a burst of compressed air into the lower mic hole the static goes away for a while. Yesterday, I discovered that, too. And that's what led me to the mic hole blocking tests I've been doing today.
This has been going on with Samsung devices for at least 3.5 years, and without being resolved! And when you call Samsung tech support about it they always tell you that they've never heard of it before. They did so with me concerning my S7's audio popping and they told some of the people in the discussions I've posted links for above the same thing 3.5 years ago.
I guess most people have just given up on this matter, since the problem is still seemingly built-in to many of Samsung's devices and there are so few new complaints posted anymore about it. What angers me the most is that Samsung continues to disavow any knowledge of this longstanding issue. They collect everyone's money for new devices that possess this flaw, but they have failed to fix the problem in over 3 years (have they even tried?), and they continue to tell those experiencing the issue that they've never heard of it before. Too bad everyone with the issue doesn't decide to organize and hold Samsung legally accountable for selling us these flawed devices at premium prices.
Update:
Yesterday evening I spent over one hour on the phone with Samsung customer support concerning this issue. The support representative was quite courteous. He was even outgoing, in terms of his willingness to check various resources during the course of our discussion. He proceeded to share the substance of my complaint with his supervisor and his second tier support contact person throughout our phone session. Nonetheless, my anger prevails.
I'm still angry because not only did this Samsung support representative claim that he'd never heard of this recorded audio popping/crackling issue among Galaxy S model devices before... he as well conveyed that neither his supervisor nor his second tier support person had ever encountered complaints about it either. Those responses simply do not comport with Internet reports to the contrary, some of which describe the issue being discussed with Samsung customer support personnel, and even being conferenced with cell carrier service support folks. Nor do they comport with the number of Internet forum complaints springing up on the problem ever since the S4 was a current device, not to mention with the two separately purchased S7 devices of mine, which both demonstrate said recorded audio crackling.
Another indication that this is a widespread flaw among Samsung Galaxy phones is the number of statements I've read from people who've experienced the crackling issue who claimed that after they had received replacement devices of the same models, those replacement devices demonstrated the identical recorded audio crackling. If those claims are in fact true --and I believe they are-- I think it's fairly conclusive that a serious design or quality control issue exists in the midst of Samsung's engineering and manufacturing. When someone pays $600 to $800 for a brand-new device, once they begin using the device's video recording function they shouldn't have to learn that said device will randomly ruin their video footage. While that's bad enough, Samsung's phone support people consistently disavowing awareness of the issue is unconscionably unacceptable to me. Selling flawed devices while pretending the problem doesn't exist is not a mark of integrity for a technology company. But unfortunately Samsung has no qualms in doing so while they become richer and richer.
I still can't understand why there aren't more folks currently concerned about this issue here on xda? It's hard to imagine that that's the case since I know there has to be quite a lot of crackling Samsung devices among xda's member base. Perhaps most Samsung-using xda members don't shoot much video so haven't noticed the problem... or maybe video and audio recording simply isn't very important to the majority of Samsung device owners here. But I have to say I find that somewhat difficult to believe.
Just tested making several videos and I really don't har any popping sounds but it's true that in the videos shared above it's very obvious. I have an Exynos model bought 3 months ago.
ciprigeorgiu said:
Just tested making several videos and I really don't har any popping sounds but it's true that in the videos shared above it's very obvious. I have an Exynos model bought 3 months ago.
Click to expand...
Click to collapse
I'm glad your device doesn't appear to have the problem. I'm unsure what the percentage of affected Samsung phones may in fact be. Even if it were, say, only 5%... that's a lot of phones considering how many of them are out there. That 5% would be 50,000 devices for every 1,000,000 sold. And I suspect that the figure is well above 5%. Thanks for testing and for sharing your result.
Now this guy is REALLY upset about the crackling:
https://www.youtube.com/watch?v=mXBtgcSDxsA
Please be warned before clicking, he uses lots of expletives.
S7 Exynos Model, bought in December.
I have no popping or crackling whatsoever. Just tested every resolution.
nothing like this on my g930f purchased in august 2016
I'm happy for those of you whose devices don't suffer from this recorded audio crackling problem... thanks for reporting on it. It's a shame though that so many Samsung phones in fact do demonstrate the problem. And it's disturbing that Samsung hasn't taken responsibility to isolate and fix the issue during the past 3.5 years of its presence. I find it especially unacceptable that Samsung refuses to even acknowledge that the issue exists after all of that time.
I am reasonably certain that these crackly pops are built-up static charges that tend to discharge during audio recording sessions, and that said static charges exist somewhere in the audio input circuitry, or perhaps in the lower microphone element itself. And I have actually found one way that seems to dramatically reduce the frequency of those discharges or, in some cases, even eliminate them altogether. I'll explain below.
If your device suffers from the recorded audio crackling problem, you might want to try an extended recording burn-in period. Simply bring up your camera app, hit the video recording button, then leave the device on a table. Allow it to record without interruption for at least one hour. After that, you can either review the footage to observe the periodic crackles bleeding down to nonexistence, or you can simply delete the footage. From that point you may seldom, if ever, notice any crackling again on your recordings. It seems to have worked on both of my S7s. It may or may not work for you, however. And I'm aware that the crackling may reappear at some point for me. But the results here have been good so far... so I think it's worth a try for you.
The best of luck with your crackling issues. If you perform a burn-in session, please report back here with the results.
Thanks
Really confused by the brief and uninformative descriptions.
I'm looking for a tablet with a good AMOLED screen to read manga and watch Youtube and Netflix on. Nothing particularly demanding.
Pretty sure I don't want the new 12.6 since I want it smaller for one-handed reading.
Are just the SoCs different between the $240-250ish 730/750 models and the $400 870s? Or is everything very different and these are two generations?
Also, is global firmware the one to go for to get Google Play and 5ghz Wifi (my home setup is a 3-piece Tenda Nova)? Heard something about wifi issues on the Chinese/English ROM
What I'm looking for is AMOLED + minimal screwing about to get it up and running. In all honesty I probably would have gone with Samsung if not for their crazy supply chain issues - I've had the S7+ in cart for at least 2 sales only for it to go out of stock before I could complete the transaction, and frankly don't want to pay full $699 to settle for a tablet larger than what I wanted after that... kept looking for Amoled S5/S6 models but they're all refurbs only now.
Lenovo looked cool...but sooo confusing.
Please advise.
PS i don't care about updates and in fact find the very idea of OTA updates an offensive infringement of my consumer rights. As long as Netflix, Youtube, and Tachiyomi or something like it run fine, I'm good with that, and would actually prefer something immune to involuntary system updates
Honestly there are issues with all of the Chinese tablets in one way or another.
I have the 2021 11" Xiaoxin and it's working well right now. There are others who have lost their L1 Widevine out of nowhere.
The WiFi issue is real and affects most people. You have to physically change the region of your router to Hong Kong or China to allow for full 5ghz WiFi. Its not ideal but does fix the issue without affecting other devices.
If you go on Holiday you may run into the same issue though?
Screen wise at first I had quite a downer on the OLED (note it is not an AMOLED e.g Samsung Brand on the 2021) as it has really bad dirty screen effect on dark grey. I am using justplayer and there was actually a bug where on HDR content the brightness would change after a few seconds and make the image look junk. It turns out if I set the screen to 60hz the issue goes away and the images look decent. (the dirty screen affect is still apparent, especially at low brightness. This website in particular shows it).
Due to the pixel arrangement I do find sometimes images /video/text particular reds can look a bit grainy.
I had a 12.6 for a time until I flashed the global firmware and fooked it. It had software issues I believe have since been fixed.
It was a much much better screen (Samsung E4 AMOLED) and speakers. It also had Dolby Vision Certification for netflix. The WiFi issue was still present.
If you were tempted to get the Samsung I'd ether wait or get the 12.6. If you look at them side by side they are nearly the same size. The Lenovo has a brighter screen.
The above is my experience so far. Tbh I find it difficult to recommend lenovo. I'm pretty pissed off with them right now for their buggy OS and unwillingness to provide Chinese ROM's to restore our tables like is a available in the Global Lenovo recovery software.