Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
Well... if you're playing with CM, you're bound to get burned. There are a couple of reasons;
1) Everybody (and I mean *everybody*) throws stuff at the CM gerrit server (sometimes, even for comedy/trolling purposes), these bits being thrown at it are mostly independent and generally NOT tested in conjunction with all the other bits that get thrown at it. So what happens, is one of the maintainers sees a commit they like and adds it, sometimes not realizing the consequences of it, and major breakage happens.
2) Sometimes in the aforementioned situation, minor breakage happens, and it can persist for months, or even forever.
3) CM12 is very young, with lots of changes still flying. It is by no means stable, or even settled.
4) The CM definition of "stable" is that which nobody bothers working on any more. I.e., everybody right now is interested in Android 5.0, so 4.4 is not getting much attention... it is "stable" -- despite being horribly broken in many many ways.
If it works well with the factory system image, then you pretty much have the answer... it is a defect that has been introduced to CM. I think that CM has their own bug tracker that you can use, but I'm not sure if they have even opened it up to receive reports against 5.0 yet.
BTW: Sweet truck eh? I have a 2011. Pay some attention to the front cab mounts. If you look up into the cab mounts with a flashlight, you will notice that at the back where they are welded onto the main frame rails, there is a huge opening to the inside of the boxed section. When you drive through salty road slime in the winter, all that salt crap that flies off the front wheels gets sprayed up and into the INSIDE of the boxed section of the frame. Get a tube of roof repair tar from HD, and a couple of old CD's. Cut the CD's down to a diameter of 3.5 inch. Stick the cut down CD's up into the opening of the cab mounts and tar them in really well. While you are at it with the tar, plug up all the other holes into the frame around the front wheels (you may need some plastic plugs for this). That will keep the road sludge out of the frame, so it won't rust from the inside out.
I am running LiquidSmooth/franco kernel. I am running the 1/19 build because it was the last with the nice Dark UI and have no problems with Bluetooth in my Prius. I mainly use Pandora.
@ doitright
Thanks for the reply. I have a better understanding about cm roms from it and I have been searching this issue all over. It is definitely a cm problem.
As for my truck, yeah I love it. I have the double cab TRD off road 4x4 model. When the weather clears/warms up I will check the areas you mentioned. I know the history on Toyota frames all too well.
@ prod
I had the same issue with that rom as well.
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
jd603 said:
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
Click to expand...
Click to collapse
I had constant problems with this phone. I am not new to flashing roms or modding phone by any means but this phone had me beat. CM roms had the Bluetooth issue and I never got it fixed. Normal roms worked pretty good but the phone was still buggy.
I got so sick of it that I sold it. Though it has been a few months ago, maybe they got the bugs worked out, idk. I couldn't take it anymore.
I went got a 128gb iPhone 6 plus now and have never been happier. I haven't had an iPhone since the 4 and I forgot how flawless they operate out of the box.
Related
I take a walk everyday after lunch at the office and use RunKeeper to keep track of my progress. When I was using the Aria, I open the app, click the start button and never had trouble. With the Captivate, I have to stand on the street corner for 1 - 15 minutes before I get a GPS fix. This is unacceptable! I tried to follow the direction of the other posting and it's not helping much.
I feel like I made a bad decision to return the Aria and got the Captivate.
after reading tons of forums and post about the gps on captivate, I found out itis the google navigation software not the actual GPS, I got rid of all my problems once I switched the software to Sygic GPS, which is not free however; pm me and will hook you up!
Buy a different phone. After a year with the Captivate, no matter the tweak, GPS for navigation purposes or tracking purposes is not reliable. I used to use it with My Tracks for tracking my runs as well and it was shotty at best.
It is not Google Navigation either as Google Navigation on my Galaxy Tab 10.1 is freaking flawless.
The GPS on the Captivate sucks. Period. /endThread
After I got a refurb mine has worked and locks on quickly, but my previous Captivate did the same thing. It would take forever or sometimes not work at all.
Sent from my Captivate
The gps is spotty.. You can try turning on the control plane (hardware) also i noticed increase by removing case.. (hardware) other than that we have crappy chip with insufficient antenna..
sent from an alternate reality
The Captivate GPS is broken. Period. It doesn't work. Never has, never will. Anyone telling you anything else has low standards, poor testing, or is a liar.
With stock settings GPS is clearly broken.
That said changing the to the google SUPL server and occasionally running the "GPSRestore" app by samsung if I can't get a fix are pretty much the only GPS fixes I've ever needed.
I think my phone is a 1007.
But based on the majority of posts here my experience is not the norm.
What's the build date on your phone? I got mine recently with a Feb 2011 build date and the thing locked in seconds out of the box. I've used Co-Pilot to take me from Vancouver to Las Vegas with no issues. What bugs me about this phone is the battery life..
same
happens to me as well.
My stock captivate was great I'd get a 9 sat lock in 12 seconds nearly all the time.
I got hooked on flashing and my gps was usually crap on other roms.
Now I'm running apex 9 with a talon kernal and I'm getting a 9 sat lock in 10 to 12 again. So go figure
same here i think i got a bad phone so i send it back and a new one and everything works fine now.
Anyone telling you that the Cappy's GPS is broken is running Stock or doesn't know what they are talking about. It's not bad hardware, it's bad drivers. Use any ROM other than stock and they use updated drivers from other devices. I get a solid lock with 6-10 sats in less than 15 seconds as long as I can see the sky. the only time my GPS loses accuracy (it's usually at less than 5 meters, i.e. no circle in Google Nav) is when I go under a thick grove of trees or under a bridge.
asrrin29 said:
Anyone telling you that the Cappy's GPS is broken is running Stock or doesn't know what they are talking about. It's not bad hardware, it's bad drivers. Use any ROM other than stock and they use updated drivers from other devices. I get a solid lock with 6-10 sats in less than 15 seconds as long as I can see the sky. the only time my GPS loses accuracy (it's usually at less than 5 meters, i.e. no circle in Google Nav) is when I go under a thick grove of trees or under a bridge.
Click to expand...
Click to collapse
Congrats on your fortunate luck but to insinuate that your solution is a universal fix is naive.
newter55 said:
Congrats on your fortunate luck but to insinuate that your solution is a universal fix is naive.
Click to expand...
Click to collapse
There was quite a lengthy breakdown of the entire process for fixing the GPS, but basically it comes down to two problems.
1. The drivers that were shipped out with the stick ROM were HORRIBLE and did not work. through using the SGSII and Nexus S ROMS, as well as some config file fixes, they were able to fix the drivers.
2. There is a hardware bug, but it only manifests itself when the screen is oriented in landscape mode. While in landscape, the CPU has to do extra calculations which slows the phone down and also boggles up the GPS, since the GPS is CPU assisted. As long as you keep the phone in portrait mode with a clear view of the sky, you will get flawless locks. Even if you don't do these two things, you should still get decent locks with the new drivers, just not instantaneous and super accurate.
Anyone who has installed any of the latest gingerbread mods has noticed the huge increase in the GPS vs. Stock. Only a few people complain that it's not as accurate or fast as their (dedicated) TomTom's and Garmins. But no one I have seen has claimed that the GPS fix has not worked. I urge you to give a GB ROM a try.
asrrin29 said:
There was quite a lengthy breakdown of the entire process for fixing the GPS, but basically it comes down to two problems.
1. The drivers that were shipped out with the stick ROM were HORRIBLE and did not work. through using the SGSII and Nexus S ROMS, as well as some config file fixes, they were able to fix the drivers.
2. There is a hardware bug, but it only manifests itself when the screen is oriented in landscape mode. While in landscape, the CPU has to do extra calculations which slows the phone down and also boggles up the GPS, since the GPS is CPU assisted. As long as you keep the phone in portrait mode with a clear view of the sky, you will get flawless locks. Even if you don't do these two things, you should still get decent locks with the new drivers, just not instantaneous and super accurate.
Anyone who has installed any of the latest gingerbread mods has noticed the huge increase in the GPS vs. Stock. Only a few people complain that it's not as accurate or fast as their (dedicated) TomTom's and Garmins. But no one I have seen has claimed that the GPS fix has not worked. I urge you to give a GB ROM a try.
Click to expand...
Click to collapse
Wrong! You can argue your point all you want but you are incorrect. I ran GB ROMS, Froyo ROMs, all of the numerous GPS fixes throughout the forums and nothing worked. GPS on my Captivate doesn't work, it is broken, I know what I am doing, I have been flashing custom ROMS for a year on it, it is inaccurate, can't hold a lock and just sucks. After dumping the Captivate for an HTC Sensation I now know what a working GPS is, it works out of the box, no need for patches or fixes, it just works. I am happy with my new device, I get over a day on battery with 5 hours of screen time without turning the brightness all the way down, 4 hours of calls all on one charge. I don't regret my decision to get rid of a broken device, Samsung makes great tv's but I doubt I will buy another Samsung phones again.
Sent from my HTC Sensation 4G using Tapatalk
The gps on the captivate is either hit or a miss. For some it works other it doesn't. Its all in experience and opinion. You can make an excuse and try to get a captivate replacement with a better gps.
Other than the gps and a pentile screen the cappy is a pretty great phone
Gps On Mine is worthless as wel..
I find gps to be better on KF1 KH3 Roms rather than jvr, cm7, etc
Might be better but the fact is the older Captivate's have faulty gps. Newer builds have better gps performance.
I agree it's a phone issue.. had my 07/2010 Captivate for 11mos, 2 weeks.. tried everything.. one day it would lock great the next 5 days nothing.. with 2 weeks left on my warranty I went to an ATT warranty center, luckily one close to my work, and they reflashed it with brand new software from Samsung as of last week and that did nothing, they gave me a refurb( looks brand new) and running Stock Froyo I got a 9 second lock 3 times in a row, you can even tell the GPS anntenae is different than my previous phone. GPS is awesome on this new phone, old one was defective..period. Running Fasty II Gingerbread did not affect the GPS on either phone.. if anyone is under warranty, work ATT warranty support and see if they can get you to send it back for an exchange.. my wife's worked great out of the box, mine did not but the replacement is awesome!!!!!!!!!!!!!!!!!!!!!
Rhiannon224 said:
Wrong! You can argue your point all you want but you are incorrect. I ran GB ROMS, Froyo ROMs, all of the numerous GPS fixes throughout the forums and nothing worked. GPS on my Captivate doesn't work, it is broken, I know what I am doing, I have been flashing custom ROMS for a year on it, it is inaccurate, can't hold a lock and just sucks.
Click to expand...
Click to collapse
I agree with you. I've been posting on the FastyII Q&A forum about this. I bought my Captivate last August and have been flashing ROMs ever since. The only ROM that came close to nailing a GPS lock was Serendipity. I'm using FastyII now which is awesome, but, as usual, can't get GPS. BTW, how long are these things warrantied?
Hey guys,
Thought I'd post this here and keep you guys updated on further developments.
I live in the Netherlands and bought a 32GB version at Dixons at the 13th of November 2012
I had found the touchscreen a bit unresponsive sometimes in the past.
But couldn't really find out why it was acting up. I finally isolated the issue.
It is exactly the same as this guys vid:
(Thanks for the vid injahnet)
Together with a little backlight bleeding, I decided to send for repair.
(The problem persisted after a factory reset, no other apps were open when testing.)
I went back to Dixons and showed the problem to the Dixons dude.
He acknowledged there was an issue and sent it for repairs or replacement.
Due to the holidays this can take some time. Maybe even next year
I was about to open my tablet for a look inside one of these days, boy am I glad I didn't do that yet
Anyway to get a good view on this issue globally, are there more people that have the same issue?
You could go to: Settings > Developer options > and then under "Input" you can enable Show touches. and try to to the same procedure as in the vid. (Thanks Peterk-1)
Or you could test with MultiTouchTester like Injahnet.
The weird thing is, my dad's N7 16GB does the same.
Update 17-12-2012: Please do not test while plugged in as the device will be grounded and the issue will not occur. (Thanks dad)
Feedback is really appreciated!
Please vote in the poll above!
Cheers,
Daan
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
peterk-1 said:
If anyone thinks they have multi touch problems then loading an app isn't required. Just go into Developer Options and under Input you have two options to display touch and track detail.
Click to expand...
Click to collapse
Nice one. I'll add that.
khaytsus said:
I have zero problems with multitouch while using my Nexus 7. Working just fine, but you must disable any apps which interfere with gestures or it'll steal events.
Can't say I've ever used multitouch with the N7 laying on a random object however.
But sure, send it in for repair......... I'll keep using mine.
Click to expand...
Click to collapse
I've done a factory reset before I tested No apps are open except MultiTouchTester
It's in for repairs
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Yes, i have this problem. And only while device is laying on the table.
Wow, this is bizarre, thanks for pointing it out. I can confirm it happens when it's laying on my pillow, and doesn't when I'm holding it.
Thanks for the vote guys.
By the way, it seems obvious that the Nexus should not be plugged in while testing.
However I cannot test this 'cause mine is at the shop
Would anyone be willing to test?
I'll add that in the original post (+ a mention of your name and a thank you of course))
Cheers,
Daan
Mine was unplugged while testing.
Sent from my Nexus 7 using Tapatalk 2
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
herrrevo said:
if the two touch-points got the same X or Y coordinate my nex7 does only detect one of them. i don't think this is an issue.
Click to expand...
Click to collapse
However, zooming in Google maps for example will become quite difficult
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
ionstorm66 said:
Anyone try and see if taping the ground pin on the wifi antenna fixes the issue? This seams like a grounding problem.
Click to expand...
Click to collapse
Exactly! I was also thinking of this.
Do people who have this issue also have the flickering issue!?
ecoviws buttress
Just an FYI, I installed CM 10.1 with Trinty Seven. Now I get 10 touches on pretty much any surface.
I don't have a multitouch issue, but I do have an entire band on my screen which has stopped responding to touch at times. It all started when I let my tab shut down due to low battery. Initially, the Nexus 7 neither charged (when put on charging, obviously), nor did it boot up. After trying for several hours, somehow it started charging. And since then, sometimes certain areas of my touchscreen become unresponsive to touch. Since the band which is unresponsive is towards the upper part of the screen, using notifications becomes completely impossible. It keeps 'snapping back up' when I try to pull it down, cos while I am pulling it down, the notification tray encounters an unresponsive area, so it just goes back up. Called up Google and they will be sending a replacement device. All I am afraid about is that I have an 8gb version, and they would be sending an 8gb as well, so I hope it isn't refurbished or something, as Asus has stopped making the 8gig model.
I'm having an issue where the screen, ( mostly in a webpage or document,) starts moving up and down and zooming in and out without my input.
Sent from my Nexus 7 using xda app-developers app
Just tested this out and yes, my device is doing it too. Interesting. No other issues like screen flicker (except the auto brightness bug in 4.2). My n7 is c9O
DaanJordaan said:
Well... Over 200 views. And only 4 votes, which includes mine
Community feedback is failing hard.
Anyway, I'll keep you guys posted on the repaired Nexus.
At the moment of writing we know that three people are having this issue.
I know someone else with a nexus I'll check if he has the issue too.
Cheers,
Daan
Click to expand...
Click to collapse
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
dilldoe said:
community feedback is not failing hard, more like you're just starting a new thread without bothering to search if issue/topic already exist.
this isn't new and there is no fix, that is just how the touchscreen function. the N7 isn't the only device to have this.
Click to expand...
Click to collapse
Don't feed the trolls!
Must... not... feed... aaargh....
You are kinda missing the point of this thread.
It is to see how many people have this issue.
There is no thread capturing that in an easy way unless you want to count every post.
Now please tell your brain to start functioning again and leave this thread alone if you have nothing to add.
Asus Google Nexus 7 32GB touch death zone
Hi DaanJordaan,
Found out that my brand new N7 seems to have a similar "no touch zone" issue; an area the size of my little finger on the left lower part of my screen does not seem to react to touch! It interferes with typing the keyboard in portrait mode (no keyboard problems in up-side-down portrait mode).
When I use the Easylabs Multi Touch test I can see the dot changing color when I move over this area, doesn't happen anywhere else on the screen..
Using the developer tools (turning on the two options that allows to show touch/leave a trail of touch) it becomes even more clear that this area does not react to touch! I can "paint" lines around the "no touch zone" (it actually splits into 2 touch areas using one finger around the "death spot"), and the "no touch zone" reveals itself by not showing any trail/history line of touch..
Oh yes, and it does not matter if I lay the N7 on the table, or hold it in my hand, the issue is always there.
Therefore I returned the N7 back to the MediaMarkt, and they will send it in for repairs...
I've got a bad feeling about this | - )
I am curious to hear about experiences with your N7, once you have it back!
I'll report mine here, in three weeks or so (that's the outlook...).
Cheers!
NeverMind
I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
dude1001 said:
I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
Click to expand...
Click to collapse
Hi, I think you might find some more info here:
http://forum.xda-developers.com/showthread.php?t=2962949
It seems that this is a somewhat common issue.
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
dude1001 said:
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
Click to expand...
Click to collapse
No problem at all. I hope that a solution becomes available for this issue.
Hello,
because i bought a new phone i gave my "old" Nexus 6 to my wife. Since a updated to Marshmallow i had problems with the camera. It stuttered while making a video. But i dont often used the camera, so i ignored it. My wife is Snapchat addicted and she can't make good videos with the front camera of the N6....it's like a slide show....the record is not smooth. I searched at the internet and a lot of people have the same problem since Adnroid Marchmallow ....
I flashed her CM 14, because i thought it might be a problem with the stock rom , but the problem remained. So my question is. Because i know i had not the problem at Android Lollipop. Is there anybody who had the same problem and solved it with flashing another rom? Or is it worth to try another kernel? I looked at the "rom forum" and found the "sky dragon 5.0 with a "new" kernel and probably i will try this. So my question is....is it a problem with the rom? is it a problem with the kernel? is it a problem with the hardware? What you expert think its the best way to fix the problem (i tried tips in the internet like diasble geodata at the photos or disable the battery safer for the camera app).
I hope you are able to understand my english. Otherwise i will explain it in other words.
Thank you very much!
Flash a factory image (will wipe the phone 100% but take it back to bone stock). If the camera issue is present on stock rom, stock kernel, with no modifications, then it's a hardware issue.
i have had problems with stuttering camera app before but it was fixed by resetting the phone. not really sure why after installing a new ROM you still facing this issue.
have you tried other camera apps? download a free one from the store and see its the same deal.
My first Nexus 6 had no issues whatsoever. When I had to RMA that one for the massive battery bulge issue, my second Nexus 6 had the camera stuttering issue. It would happen whether I was taking still shots or video. Obviously it was more noticeable on video, but it still made taking stills difficult. I took a video at the time to post on here to see if other people where having the same problem, but actually never got around to posting it...
http://www.youtube.com/watch?v=k23njriKiDk
Anyway, I RMAed that phone for the camera issue but then the third N6 had the same issue. I decided to live with it though since (a) Motorola has a really frustrating return policy/procedure, and (b) since two different devices had it I didn't think there was any guarantee that an RMA would fix the problem.
Fortunately, I've noticed that lately (running Nougat now), the stutter has mostly gone away. I'd say that for still pictures it has gone away entirely. For videos, I think it is gone as long as you use the stock camera app. I've noticed that if you use other apps, like Instagram for example, my video still has issues. In that case though, it's more of a constant refocusing issue than a stutter issue.
So moral of the story is... for me at least, it seems to be ok on Nougat as long as you stick to the stock camera app.
****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.