Related
I've been obsessing over the N1 since launch. Android is super neat, and unlocked phones rock. The only thing that really held me back from the purchase was the multitouch issue. I could easily see having to reset my screen with a lock cycle would drive me crazy. That said, I love the idea of the N1, and wish to escape my iPhone prison.
I recently purchased a Galaxy S phone, but am annoyed by the lack of support (saw this coming) and non-functioning locational services. The GPS and Compass are totally and utterly busted. Sadly, Google stopped selling the N1 on the day I decided to order one. However, I have been given a second chance, by purchasing the dev phone (which I am now considering).
So, let's make this like ripping off a bandage. Have mercy, internet. I have questions that require honest answers. I'm sorry if you've heard it all before, but this kind of information is annoyingly hard to dig up. Lightning Round, Go!:
Is the multitouch problem with the N1 (inverse axis swapping when two points cross) still present with 2.2?
Do any custom ROMs, apps or tweaks solve this issue? I read that the Moto Droid had a software setting ticked that allows proper multitouch (a sort of software hack), that google had not opted to enable by default? Sounds a bit silly to me, but what's the deal?
Does your screen still lose track of your fingers (inputing the wrong characters on the keyboard), causing you to lock cycle your screen to reset the digitizer?
Are the touch-buttons difficult to use?
A fellow N1 owner I met told me that his phone showed no signs of the multitouch 'bug', when using 'Multitouch Vis Test'. He said he was running the Modaco ROM. Is it true that something in this ROM fixes the multitouch problem?
Thank you, Princes of Internet.
Personally i dont experience any multitouch issues on my n1. Im running stock froyo 2.2. I have only had to re-lock my screen once and it never happened again. The capicative buttons below the screen take a bit of time to get used to at first it might take you a couple of tries to register a click but a few hours of use you get the hang of it.
Sent from my Nexus One using XDA App
Thanks for the reply.
Would you mind taking the 'Multitouch Vis Test' app for a spin, to see if the problem is gone, or if you just don't notice it?
If the issue is gone, would you mind making a youtube vid of it?
The multitouch on the n1 will not be "fixed" unless google/htc decided to use different hardware. If you can live with a device that can only do pinch to zoom, but not true multitouch, then the n1 is fine.
Honestly at this point, I'd hold off until you see the rest of HTC's lineup that's coming up before december.
Jon C said:
Is the multitouch problem with the N1 (inverse axis swapping when two points cross) still present with 2.2?
Do any custom ROMs, apps or tweaks solve this issue? I read that the Moto Droid had a software setting ticked that allows proper multitouch (a sort of software hack), that google had not opted to enable by default? Sounds a bit silly to me, but what's the deal?
Does your screen still lose track of your fingers (inputing the wrong characters on the keyboard), causing you to lock cycle your screen to reset the digitizer?
Are the touch-buttons difficult to use?
A fellow N1 owner I met told me that his phone showed no signs of the multitouch 'bug', when using 'Multitouch Vis Test'. He said he was running the Modaco ROM. Is it true that something in this ROM fixes the multitouch problem?
Thank you, Princes of Internet.
Click to expand...
Click to collapse
1) It was possibly noticable in 2.1, in 2.2 in months now I havn't see it once. You can see with the visualiser you really have to know how to force it to get it to go, its just not something which will occur with correct commands you'll be doing.
2) Its down to the hardware, I'm not aware of any custom ROMs which have anything/anything significant.
3) The only time I EVER get this is with beta super bundles of ROMs, which is either the fault of the ROM, something going skitz in dalvic, how I installed it, or just a self generating bug. All of which are easily fixable. However if you were to stay with stock or more tested ROMs, you'd literally never see this.
4) For me they just work, at the start yes they wouldnt act the same a touch screen, but now they'll act like I want maybe 99% of the time. Sure friends using it to start with have to get used to it, but its not 'broken' if you will. The only thing I will mention is if your using it in weird orientations, there is a chance of hitting the buttons [mainly search] without meaning to with parts of your hand.
5) Again, this problem ONLY shows up if you know how to 'break' it. With 2.2+ its really hard to do it if you handed the phone to someone who's never used it before, because also again you wont be doing any commands which would conflict with the limitations, so you have to be misusing it in the first place to get the bug.
JCopernicus said:
Honestly at this point, I'd hold off until you see the rest of HTC's lineup that's coming up before december.
Click to expand...
Click to collapse
Agree with this.
Multitouch is completely crap on the n1. I loved it otherwise, yes every now and again it goes wack and registers the wrong thing... the capacitive buttons also suck and are hard to get used to... on Multitouch test its wacky and registers the wrong finger and won't register more than 2...
Great device, but galaxy is better.. I don't have any gps issues so can't complain about that.
No. No roms will fix the Multitouch issue. Nor make it any better.. if your into gaming with controls on the same axis forget about it, if ya want Multitouch keyboard forget about it...
I still have yet to ever experience the actual axis switch issue using this phone in real world. Sure the issue exists, but it just doesn't effect a single thing unless you use a certain game. But even that works fine, watch YouTube videos showing emulators on the nexus.
The point is, if you're looking for a reason to not get the nexus, The axis switch issue is not the reason that should sway your decision.
I recently came from an iPhone and I haven't noticed any difference in the multi-touch screen (except maybe in the typing on occasion, which I just attributed to my big fingers). I'd say for a good 95%+ of what you would do on the phone you can't tell any difference between the iPhone or N1 multitouch.
With the touch buttons on the bottom of the screen... Sometimes I hit one while typing, which takes me back to the home screen, but since the N1 has true multitasking all I have to do is reopen the app. A minor inconvenience. Or I could just type in landscape mode and not have any trouble at all.
RogerPodacter said:
I still have yet to ever experience the actual axis switch issue using this phone in real world. Sure the issue exists, but it just doesn't effect a single thing unless you use a certain game. But even that works fine, watch YouTube videos showing emulators on the nexus.
The point is, if you're looking for a reason to not get the nexus, The axis switch issue is not the reason that should sway your decision.
Click to expand...
Click to collapse
Games like toonWarz or nova will mess up. Has the controls on bottom right and shooting on bottom right. So when your running using the left controls and shoot real quick with the right, it'll now wig out and keep shooting even when you let go and the dude will walk a different way be cause now the sensor thinks your touching in a different spot..
Now you can let go of the left finger then shoot but when ya need precision in some shooting games you will be dead if you do that....
Pinch to zoom is fine and emulators with controls on the top and bottom vs just the bottom ( same axis), but for games like nova, heavy gunner, modern combat, ps1 emulator (unless it has opposite axis controls) which mine don't, took Warz, etc. It will not work properly ....
smashpunks said:
Games like toonWarz or nova will mess up. Has the controls on bottom right and shooting on bottom right. So when your running using the left controls and shoot real quick with the right, it'll now wig out and keep shooting even when you let go and the dude will walk a different way be cause now the sensor thinks your touching in a different spot..
Now you can let go of the left finger then shoot but when ya need precision in some shooting games you will be dead if you do that....
Pinch to zoom is fine and emulators with controls on the top and bottom vs just the bottom ( same axis), but for games like nova, heavy gunner, modern combat, ps1 emulator (unless it has opposite axis controls) which mine don't, took Warz, etc. It will not work properly ....
Click to expand...
Click to collapse
this is a good explanation of what is effected. if you're a big gamer then consider it, but things like pinch to zoom in the browser, maps, pics, works just as great as ever.
Thanks for the feedback, guys.
Coming from the Galaxy S, I imagine I will miss a few things. One of them being: media playback and overall storage.
I guess with the N1, I'd need to find a non-bootlegged 32GB microSD card. But my other question would be: is there an easy way to play all of the content that the Galaxy S can handle, or is the GPU in the Samsung phone so much better that the N1 can't keep up?
I really like that about the SGS: I just drop movies (mp4, xvid, divx and so forth) onto the internal ROM and they play without issue. Media capabilities are very nice.
Does the N1 play lots of videos like this out of the box? If not, is there a decent media application?
Also, about HTC's other devices: I'd love to wait, but I'm worried that the newer phones won't have nice accessories. The N1 has that awesome car dock, that I would use all of the time. The SGS doesn't have any accessories like that, and it makes me sad. Most of HTC's N1 follow-up lacked similar docks and cradles.
If I return this SGS (likely), I will probably be jumping to the N1, just for that 'official' feel of it (very sturdy, solid first-party accessories).
You have no idea how sad I was, when Google announced they were giving up on creating their own phones. Hate them all you want: but Apple really has that system (solid build, quality integration / lack of fragmentation) nailed. I was really hoping that Google could bring that unification to Android with their own branded devices.
Loving Android, though. Never going back to iOS.
Anyone saying the n1 doesn't suffer from multitouch issues is sadly mistaken. The one thing that bugs me about the n1 is the touch screen issue. You won't be able to play games like nova, or certain games on emulators (when using dpad plus buttons that are at the same level it has issues) and it does have issues when crossing the axises.
mjm128 said:
Anyone saying the n1 doesn't suffer from multitouch issues is sadly mistaken. The one thing that bugs me about the n1 is the touch screen issue. You won't be able to play games like nova, or certain games on emulators (when using dpad plus buttons that are at the same level it has issues) and it does have issues when crossing the axises.
Click to expand...
Click to collapse
everyone said the issue exists it just doesnt show up unless you...play....games. otherwise its a non issue.
The N1's touchscreen is totaly crap. There is a thread about touchscreen issues at oficial forum. It has more than 2000 posts explaning all problems of nexus one touchscreen. Check it out.
Sent from my Nexus One using XDA App
Jon C said:
Thanks for the feedback, guys.
Coming from the Galaxy S, I imagine I will miss a few things. One of them being: media playback and overall storage.
I guess with the N1, I'd need to find a non-bootlegged 32GB microSD card. But my other question would be: is there an easy way to play all of the content that the Galaxy S can handle, or is the GPU in the Samsung phone so much better that the N1 can't keep up?
I really like that about the SGS: I just drop movies (mp4, xvid, divx and so forth) onto the internal ROM and they play without issue. Media capabilities are very nice.
Does the N1 play lots of videos like this out of the box? If not, is there a decent media application?
Also, about HTC's other devices: I'd love to wait, but I'm worried that the newer phones won't have nice accessories. The N1 has that awesome car dock, that I would use all of the time. The SGS doesn't have any accessories like that, and it makes me sad. Most of HTC's N1 follow-up lacked similar docks and cradles.
If I return this SGS (likely), I will probably be jumping to the N1, just for that 'official' feel of it (very sturdy, solid first-party accessories).
You have no idea how sad I was, when Google announced they were giving up on creating their own phones. Hate them all you want: but Apple really has that system (solid build, quality integration / lack of fragmentation) nailed. I was really hoping that Google could bring that unification to Android with their own branded devices.
Loving Android, though. Never going back to iOS.
Click to expand...
Click to collapse
The gpu is OK. But definitely a lot less powerful than the sgs, you will notice in movies, live wallpapers and especially games... there's a decent video player called rockplayer that plays a lot of stuff like avi and xvid , but its not ad good as the sgs player ...
Put it this way, either stay sgs and have a not so well navigation but awesome everything elsex or go nexus with good GPS but a old touch sensor that will hardly recognize both fingers on anything other than pinch to zoom.....
The only real world scenario i have encountered the axis switch is when you do a pinch on an album in the gallery to have it flick through them, it switches often when doing that.
Nexus One multi-touch sucks for games. I've tried some fancy gameloft games that req two fingers on screen, or PS & gameboy emulators that req this and it drives me insane. Can be so frustrating for gaming and is the only thing that I find a let down for this device. I wish I knew before I purchased it because the gaming although not the only thing I brought it for is something that I thought would be cool on my phone.
Simply put, don't get the N1 if mobile gaming is important to you. I'm not talking about simple single tap games, but the intricate ones (PSX Emu, EA Sports, Gamesloft, etc). If you could live without it, the touchscreen is fine for regular day to day use.
Or just root and carry your favorite bluetooth game controller. I have a mini bt keyboard that works great for emulators
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
jeremy89632 said:
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
Click to expand...
Click to collapse
i sent him a mail. here are the responses:
it seems unlikely:
- I don't have the device
- it uses different touch controller than 10.1
- kernel doesn't support configurable parameters for 8.9
Click to expand...
Click to collapse
I'm speaking about driver provided for controller used in 8.9, it has
no possibility to change configuration. And the firmware of the
controller is a binary blob with no documentation.
Click to expand...
Click to collapse
looks like we are unlucky
being very upset with this problem i started poking around the build.prop
it might be placebo but i feel that when this is added:
Code:
windowsmgr.max_events_per_sec=300
it gets a little more responsive. still not what i want it to be but better than before.
Try Touchscreen booster
It seems to have helped mine.
thanks. seems a little more responsive.
here is the apk if anybody else was wondering:
http://forum.xda-developers.com/showthread.php?t=1261237
My 8.9 LTE is super sensative, probbly the most I have seen on any android tab.
I can just barely graze my screen with rhe back of my fingernail and it even picks that up.
Compared to my roomates ASUS Transformer Prime, wo cant even use his fingernail unless he really jams it down.
iinteresting but im on the tegra version which aparently has completely different hardware
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
MatteAce said:
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
Click to expand...
Click to collapse
Try TouchScreen Booster?
the_hatrix said:
Try TouchScreen Booster?
Click to expand...
Click to collapse
that's been the first thing I did, but the improvements it brings are very light.
Does the tablet really have different hardware between the wifi and the LTE version? (at least regarding the screen digitizer)
Loccy said:
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Click to expand...
Click to collapse
Hmm, is it really a sensitivity issue? If I swipe first then wiggle like you mention, the screen will wiggle slightly. It sounds like there is a threshold to switch from holding the finger down motionless, to scrolling from left to right.
Perhaps a threshold setting (if available) is sufficient to overcome this?
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Kasracer said:
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Click to expand...
Click to collapse
I have Samsung 3.2 OTA update and it really changes nothing.
Btw no answer yet from Samsung, and yes, the problem is just about some sort of accidental touch filter
I have only had my tf701 a day but Ive noticed sometimes when docked to the keyboard if you dont touch the mouse for a few seconds sometimes when you move the mouse again it will make a flicker around where the mouse is located, it doesnt always do it, just wondering if anyone has noticed this or is it a fault with my tablet?
I can live with it, but if there is a known fix it would be nice to sort it.
Thank You
After a bit of messing about I think it only does it with live wallpapers? Which isnt a problem as I wont be setteling on a live wallpaper anyway found them far too distracting.
Would still be nice to know this is fixable though.
Thank You
I was wrong its not to do with live wallpapers, just seems to do it on some apps, for example if I go to apex launcher then settings, if I leave the mouse for 10 seconds or more than rouch to move it, it makes the strange flash across the screen.
Could anyone else please test if theirs does this?
Thanks
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Yeah I am running 4.3?
I have noticed it does it on the drawer too, only when using the dock and leaving the mouse dormant for 8 seconds or more than moving it again it sends horizontal lines across the screen for a split second, is this the bug *ahem* feature you speak of?
Thanks
berndblb said:
Asus considers it to be a feature - not a bug - and calls it "smart backlight adjuster".
For most people it goes away upgrading to 4.3 which I guess you haven't done?
Click to expand...
Click to collapse
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
dougie175 said:
Also when you say adjuster, that sounds like it would be something that requires adjusting but it still does this with screen set to full brightness, or least brightness, with auto off, also wit outdoor on or off, it still does the strange flicker.
I can happily live with it, doesnt bother me that much just dont want it to be something that is going to get worse as Im very close to unlocking the device and dont want to blow all warranty if I already have a fault.
Thanks
Click to expand...
Click to collapse
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
berndblb said:
No what I had in mind was the screen dimming and brightening. What you describe sounds more like the "flashing black lines" the TF700 has (which seems to be due to some nvidia driver issue). I have not noticed those on the TF701 but then, I am so used to them from the 700 I probably wouldn't even notice. Have not read anything about them in the forums though, so I suspect your situation is unique.
Are you in the US? Get a Squaretrade warranty. I find the peace of mind is worth the $75 since they don't care about locked/unlocked...
Click to expand...
Click to collapse
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
berndblb said:
Don't have the keyboard for the TF701 - yet. So I can't help you with your test.
The black lines on the 700 are benign - I don't even notice them anymore. But I don't think my 701 has them, so there is a possibility that your tablet has a glitch...
Click to expand...
Click to collapse
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
dougie175 said:
No I am in the UK Im afraid, hmmmmm its deffo a tf701 not a 700 hehe
Can you please test for me open your drawer, leave the mouse in the centre for 10 seconds then move it and see if it does the black lines?
Also did the issue ever get resolved or get any worse on the 700 or is it just something the user gets used to?
Thank You
Click to expand...
Click to collapse
Just tried your test and I see no lines. Maybe because I'm not on the stock rom exactly?
dougie175 said:
Thanks, I have sent Asus an email to see if they will help me, I bought the tablet second hand though so they probably have no interest even though it is only 3 months old and hasnt been out long enough to be out of warranty.
If they will fix or replace it for me ill take that, if not i can happily live with it
Click to expand...
Click to collapse
I don't want to be negative here, but waiting for Asus' response is pretty useless. Their support staff has two answers for questions beyond: "Where do I find my pictures?" and they are:
a) Factory reset, and if that does not help:
b) Send it in for repair - which may or may not cost you a bundle...
If you do send it in get written confirmation that your tablet is still under warranty first and take pictures of your tablet documenting its condition, how you packed and shipped it etc.
Thanks for the replies
This is what I get
dougie175 said:
Thanks for the replies
This is what I get
Click to expand...
Click to collapse
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
berndblb said:
That is entirely different from what I thought it was and I have no idea what could be causing it. Do you get that ever when the dock is not connected?
Click to expand...
Click to collapse
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
dougie175 said:
No it cannot be replicated when the dock is not connected or when just touching the screen with or without the dock connected, it only does it on some areas of the system such as drawer and some apps if the mouse if left dormant for 8 seconds or so then moved.
I have done a factory reset and cold boot as requested by Asus, but the problem still persists as shown here in the new video
http://s9.photobucket.com/user/dougie175/media/Mobile Uploads/MOV_0020.mp4.html
Click to expand...
Click to collapse
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I have noticed one other thing, it will not do the fault on first reboot, until the screen is locked, once unlocked it starts doing this fault
Gesture mode made no difference
Also done the developer options and they made no difference :crying:
sbdags said:
Mine definitely doesn't do that. Try switching the cursor mode to gesture mode for me and see if that makes a difference. (I doubt it will but you never know)
Then go to the system settings, about and click the build number 7 times to enable developer mode. Then go into developer settings and look for force GPU rendering and disable hardware overlays. Check both. Reboot - any difference?
Click to expand...
Click to collapse
I was wrong disabling hardware overlays does seem to resolve the issue?
However each time I reboot the option is un ticked that's why I thought it didn't do it
YayYouFixedIt said:
Check the cables
When troubleshooting a screen flicker, I always check the cables first. Several TechRepublic members agree. Ian C B, Bruceb, Crjordan, and Aqmike all suggested checking the video and monitor power cables before doing anything else. Ian C B reminds us to confirm that the cables are screwed in tightly and to replace the cables with new ones to see if the problem persists.
"The color changes are almost always a faulty wire in the cable," Crjordan said. "Try working the cable back and forth near both connectors. If this causes the color change, you could have a broken wire in the cable, or a loose pin in one of the connectors. Make sure the cable is out of the way (from feet, hands, and other objects). You may also try zip-tying it to itself or another stable object until you can replace either the cable or the monitor."
Check the environment
If a cable isn't the culprit, then the user's workspace should be next on your hit list. Monitors are notoriously sensitive to magnetic fields. Speakers, florescent lights, fans, cell phones, radios, and any other electrical device can cause a wide range of monitor problems. (See Figure A.) "Check what's around the [monitors]," Vilefileman said. "Cell phones are known to cause screen flickers, among other things, and plugging a radio or fan into the same receptacle can also cause screen flickers."
Maybe its like some kind of electrostatic interefereence in your environment more to do with the power being supplied to the device. Check cables. Etc. I think its interference or something.
Click to expand...
Click to collapse
Theres not really any cables I can check, I have checked the connection is pushed in correctly which it is.
I have just tried to replicate the error outside with my phone turned off inside the house so no chance of interference and the error was still present.
Don't think this is quite the issue as it only does it when moving the mouse after leaving it on certain apps for 8 seconds.
Thank you for the help though
****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine
Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
anyone ?
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.
Hi devs!
Since i have this phone iam searching the function for double-tap to wake-up feature.
Esp, cause the previous models had this feature.
I've been through a few launchers and a few apps, but it seems with a fingerprint-sensor this feature has become unavailable?
Any people here managed to double-tap to wake-up their device?
Thanks in advance!
TGN said:
Hi devs!
Since i have this phone iam searching the function for double-tap to wake-up feature.
Esp, cause the previous models had this feature.
I've been through a few launchers and a few apps, but it seems with a fingerprint-sensor this feature has become unavailable?
Any people here managed to double-tap to wake-up their device?
Thanks in advance!
Click to expand...
Click to collapse
Sorry to say but that incredibly useful feature is missing from the XZ1c. It's not just a software thing, I believe it's missing at a hardware level. So either the screen is different or the kernel doesn't support it.
Wave up is a way of opening and closing the screen and has had some good reviews from XDA members.
Thanks for your reply.
Let's see if i can get used to this and finetune it a little.
Didgesteve said:
Sorry to say but that incredibly useful feature is missing from the XZ1c. It's not just a software thing, I believe it's missing at a hardware level. So either the screen is different or the kernel doesn't support it.
Wave up is a way of opening and closing the screen and has had some good reviews from XDA members.
Click to expand...
Click to collapse
I'm giving a shot myself with this app... It seems working great... Only doubt of course is the battery draining... Let's see after a few days of testing...
P. S. So Wave Up is for the waving hands thing... What about double tap to wake?
Dany XP said:
I'm giving a shot myself with this app... It seems working great... Only doubt of course is the battery draining... Let's see after a few days of testing...
P. S. So Wave Up is for the waving hands thing... What about double tap to wake?
Click to expand...
Click to collapse
Double tap to wake likely needs lower level support that isn't possible with a mere app.
BTW, I've been using the Wave Up app for months, did not notice any battery drain.
I personally love the wake screen after removing from pocket feature, it works like a charm and so handy to have. I now wonder how I lived for so long without it.
Also, you don't need to actually wave your whole hand, just flick a finger 2 or 3 times over the sensor area and boom. Although I'd still prefer DTTW, it's a great compromise.
mhaha said:
Double tap to wake likely needs lower level support that isn't possible with a mere app.
BTW, I've been using the Wave Up app for months, did not notice any battery drain.
I personally love the wake screen after removing from pocket feature, it works like a charm and so handy to have. I now wonder how I lived for so long without it.
Also, you don't need to actually wave your whole hand, just flick a finger 2 or 3 times over the sensor area and boom. Although I'd still prefer DTTW, it's a great compromise.
Click to expand...
Click to collapse
Yeah, I saw WaveUp recommended on XDA too and used it after trying and disliking Gravity Screen. It's been fantastic, and I actually don't notice a lot of battery drain from it either. I sometimes end up double-tapping the proximity sensor. That generally works pretty well. Sometimes even better than waving.
Just a little update about WaveUp.
Definitely, a must have for XZ1 Compact owners. ?????????????????. After a few days of testing I can confirm it has almost zero impact to battery (I can't notice any difference, in fact it doesnt even shown on Setting's Battery usage) but once u use it... U can't stay without it anymore!
I really i don't understand why Sony didn't include this functionality out of the box...
I am using Gravity Screen to wake my phone using the proximity sensor, but I noticed it keeps the sensor ON all the time even when the phone is locked. I think this is what WaveUp do as well. I'm kind of concerned with the sensor being awake all the time that it might affect the lifespan of the sensor and get damaged fast. I hope SONY put back that double tap to wake.
Hello, is there any app that turn on display when new notification is arriving?
WaveUp is really good!
Thanks to everybody for the suggestion!
rtimoff said:
Hello, is there any app that turn on display when new notification is arriving?
Click to expand...
Click to collapse
Might be a late reply, but an app called Glimpse Notifications does exactly what you want.
Update: WaveUp works, but can be annoying when cleaning the screen.
rtimoff said:
Hello, is there any app that turn on display when new notification is arriving?
Click to expand...
Click to collapse
I am using "Glimpse Notification"
They do it on purpose, they always take something away and then put it back in the next model. But the next model will miss a different detail, and so on ...