hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
wave1990 said:
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
Click to expand...
Click to collapse
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Protonus said:
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Click to expand...
Click to collapse
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
wave1990 said:
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
Click to expand...
Click to collapse
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Protonus said:
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Click to expand...
Click to collapse
I do not know if you develop .... but you could create a fix that recalibrates the driver every tap on the screen!
is an idea =)
Related
My DHD has problems with the proximity sensor. I returned the device to the vodafone store (Netherlands), and they changed the device for a new one that worked.
Today, 1 day later, my second DHD is now having the exact same problem with the proximity sensor.
When I make a call, the screen immediately goes black, and the device no longer responds to any button (not even the power button on top). The ony way to get the device back to life is by removing and reinserting the battery.
Video of the problem
When I receive a call, the screen stays unlocked, even when the device is placed against my ear, so I end up with my ear pressing the active screen....
I've read more complaints about this exact problem on the tweakers.net forum. It is still unknown whether this is a hardware of software failure.
UPDATE
The problem seems to be related to the lightsensor, when holding a locked DHD in front of a bright light source, the device wil unlock (as long as you keep it in front of the light).
It might be, that when used in bright daylight a DHD will function properly.
Also, when calling using the headset, the problem does not occur. When inserting a headset in a "locked" DHD, it will wake up.
UPDATE2
Some facts, to "bust" some myths about the problem:
- It seems the problem can happen on all DHD's, not just devices with a particular S/N, software version, carrier (telco) or color.
- It has something to do with the light sensor (which is the same sensor as the proximity sensor) since the device unlocks when held in front of a bright lightsource, some users claim their device works well, as long as they are in daylight.
- The DHD uses a CM3602 proximity/light sensor, the same as a regular Desire
- The problem might not occur immediately after purchase, sometimes it takes a few days before it starts, thus switching your DHD for a new one might only solve your problem for a few hours/days (this is what happend to my second and third... yes third device)
Seems like the same kind of problem: http://forum.xda-developers.com/showthread.php?t=811282
Exactly the same post. Nice detail that I'm also a Dutch user bought it at a Vodafone store.
So, that's at least 3 devices reported with this problem.
Is there a way to turn off the proximity sensor? This would mean I have to turn the screen off manually when I make or receive a call, but that way, I don't have to reset the device every time I make a cell
Maybe you guys have found why it failed the google test ?
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
I wouldnt be very worried tbh, this is surely software related else they wouldnt release any batch of cellphones and delay the release for more than just a few weeks.
Can you make a Video and load it up on Youtube?
If we have a video it´s much easier to show HTC the problem... maybe we can load this video up on facebook to the HTC page...
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Edit: Ah I see 2x LeonM1234 and 1x WizardX. Forget this post
liorra3 said:
1-2-3 from the first stock - that is an failure that will come back to all of us...
did you try contact HTC ??
Click to expand...
Click to collapse
Will try contacting HTC Netherlands tomorrow, today is Sunday...
name_th said:
Really bad if this failure concerns all DHDs. But why 3 devices?
I only count LeonM1234 and WizardX?
Click to expand...
Click to collapse
This is my second DHD with this problem
P.S. Can any mod please remove the 1 post per 5 minutes limit, it is quite annoying... thanks!
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
www . techeye.net / mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
i think to cancel my DHD order until that issue will check.
Apache14 said:
A lot of HTC phones have a similer problem. Its S/W related (the desire had it when it was first out e.g. it the screen used to go black and not re-light untill you placed it on a table or the other person hung up)
I would be suprised if 3 phones have the same fault unless it SW related :-D
Click to expand...
Click to collapse
the solution with the desire was an software update ?
Milini said:
HTC's new Windows phone seems to have a similar error with the proximity sensor:
As I'm a new user I'm not allowed to post a working link. I try to write it so the system accept it.
http://www.techeye.net/mobile/one-day-after-launch-event-windows-phone-bug-spotted
If this turns out to be true it's more hardware related than software, isn't it?
Click to expand...
Click to collapse
There you go proper link and welcome!
liorra3 said:
i think to cancel my DHD order until that issue will check.
the solution with the desire was an software update ?
Click to expand...
Click to collapse
Yep was solved with a S/W update
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
mach03 said:
You can add one more to the list. Friend of mine had the same problem with his proximity meter. I will receive my D-HD either tomorrow or the day after, I'll let you know if it works properly.
Click to expand...
Click to collapse
Keep in mind, my device worked as it should the first day...
i don't understand how it can work fine one day and the following day it messes up lol
Apache14 said:
Yep was solved with a S/W update
Click to expand...
Click to collapse
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
liorra3 said:
hee
sorry for the noob one, but s/w - is ? they need make some software update ? or replace the phone ?
Click to expand...
Click to collapse
s/w is software... you practically answered your own question
As of late I've noticed that when I wake up my device it'll take me to my tile homepage, then quickly forward me to the lock screen where I'm prompted to enter my 4 digit pin. This never happened before and I'm wondering what's causing this.
Has anybody experiences this?
Yes, it's a tiny glitch that flashes the home screen then the lockscreen. Personally I had this with Windows Mobile 6.5, and it really bugged me.
Sad to see it here with WP7.
Maybe future updates will hopefully fix it?
bazinga said:
Yes, it's a tiny glitch that flashes the home screen then the lockscreen. Personally I had this with Windows Mobile 6.5, and it really bugged me.
Sad to see it here with WP7.
Maybe future updates will hopefully fix it?
Click to expand...
Click to collapse
Thanks for the reply. I figured it was a glitch. Hopefully it's fixed with an update. Ot only just started happening yesterday, and I've had my phone for about a week. :-(
Doesn't happen for me... although, after reading this, perhaps I should add "yet"!
It does not happen to the stock lockscreen wallpaper ... but when I change it, it jumps from the home screen to the lockscreen, hm
Weirdly enough, I got a Focus that had this same bug and it drove me crazy. However I had to return that Focus because Wirefly was threatening to charge me $300 if I used it on a different line on my family plan.
So a couple of weeks later I picked up the Focus from AT&T for the $99 price and now I don't have that bug! It's weird really...
Do you think this could be fixed with an update?
I had something similar happen with my HD7. Instead of flashing to my tile homepage, it would flash the color green. Then it would take me to my lock screen.
OGCF said:
Weirdly enough, I got a Focus that had this same bug and it drove me crazy. However I had to return that Focus because Wirefly was threatening to charge me $300 if I used it on a different line on my family plan.
So a couple of weeks later I picked up the Focus from AT&T for the $99 price and now I don't have that bug! It's weird really...
Click to expand...
Click to collapse
It's driving me crazy too.
bazinga said:
It does not happen to the stock lockscreen wallpaper ... but when I change it, it jumps from the home screen to the lockscreen, hm
Click to expand...
Click to collapse
I changed to the stock lockscreen wallpaper and it was still glitchy.
manny84 said:
I changed to the stock lockscreen wallpaper and it was still glitchy.
Click to expand...
Click to collapse
Did you do a factory reset?
My wallpaper is still glitchy too, but not as much. Maybe like 1/2 a second.
Edit: Don't factory reset it if you didn't! I'm just asking if you did
bazinga said:
Did you do a factory reset?
My wallpaper is still glitchy too, but not as much. Maybe like 1/2 a second.
Edit: Don't factory reset it if you didn't! I'm just asking if you did
Click to expand...
Click to collapse
I tried a factory reset the other day and it didn't help.
I just really hope that it's not the phone itself that's messed up.
manny84 said:
I tried a factory reset the other day and it didn't help.
I just really hope that it's not the phone itself that's messed up.
Click to expand...
Click to collapse
I don't know if its the phone itself, but some people claim that changing phones helped. Most of the videos I've seen on Youtube with Windows Phone 7 apparently don't have this problem though.
For me, I have an HD2 and I've been switching WP7 rom's regularly. Of all the ones I've tried, I seem to have this problem.
My brother, who also has an HD2, claims to not have this problem.
bazinga said:
I don't know if its the phone itself, but some people claim that changing phones helped. Most of the videos I've seen on Youtube with Windows Phone 7 apparently don't have this problem though.
For me, I have an HD2 and I've been switching WP7 rom's regularly. Of all the ones I've tried, I seem to have this problem.
My brother, who also has an HD2, claims to not have this problem.
Click to expand...
Click to collapse
Unfortunately, changing phones is not possible, as I have an unlocked Omnia 7 and the grace period for exchanges has passed.
It's a shame because I really love this phone and OS, but this bug is ANNOYING. It kills the experience.
If anybody else is experiencing this, please respond!
i guess your last hope is the upcoming update... hopefully it fixes it (and a lot of other bugs).
Video of the bug that I'm describing.
http://www.youtube.com/watch?v=isi5aKDjnws
This user (who uploaded this video) is also having problems with his Omnia 7. It's the same bug that I described.
I'm having this problem too, but I've found an easy way to fix it (at least on my Focus). Whenever I have the brightness setting on low or automatically adjust, it goes away.
oscardog777 said:
i'm having this problem too, but i've found an easy way to fix it (at least on my focus). Whenever i have the brightness setting on low or automatically adjust, it goes away.
Click to expand...
Click to collapse
Thank you so much!!!!!
Lockscreen bug
Hi all,
I have samsung omnia 7 and i am getting this lockscreen issue
Code:
http://www.youtube.com/watch?v=isi5aKDjnws
I would like to ask if some of you with different devices are experiencing the same or is it just with OMNIA 7??
This issue appears only if you have automatic brightness turned off..
There's been a few topics created about this. I believe it began because of users using PINs and wanting their information to be protected... That obviously has a bit of a security flaw. I'm sure it'll be fixed in the update.
Hi, i can also confirm this issue on my omnia 7. Fix is as described to turn on automatic brightness.. However, i would like to ask if this is WM7 bug or Omnia 7??
Drives me up the wall. Sometimes it's good and sometimes it's not.
Sent from my Nexus in Texas.
Aha. Well well.
Care to elaborate?
The multitouch issue were "multitouch" becomes wonky (for lack of a better word), after periods of use. Best example: playing a game that uses multitouch. The only workaround right now is to turn the screen off and turn it back on. The software resets when screen is toggled on/off. THIS IS A SOFTWARE PROBLEM.
I believe it's still an issue. I still have the problem on 4.0.3.
Multi-touch problems? Not on my phone. First i've heard of it.
kleverman said:
Multi-touch problems? Not on my phone. First i've heard of it.
Click to expand...
Click to collapse
You probably just didn't notice it. I didn't know about it until i read about it. Then i tested for it. Lo and Behold i had the same issue. It's probably a non issue to some people. This happens on any version of the GalNex
You will not see it until you play a game then test for it.
I have the multi touch in the bottom corners. It's an on/off and turning screen off temporarily relieves. It hasn't been a big problem, because I don't game often but just wondering if anything is on the table yet. I know it is software so it is easily fixed. Has anybody come up with a patch for it?
Sent from my Nexus in Texas.
Is there something in the OS that can invoke this bug to occur? I have a stock unrooted and locked bootloader GSM GN and when I had 4.0.1, I never had any of these multitouch problems on any game that I played. Now with 4.0.2, this problem keeps appearing. It's really annoying
I just tried to do same as the guy in the video.. Everything is fine at my phone...
Playing ShadowGun and Riptide GP on mine produce this issue, and turning the screen on and off works for a few seconds, then it happens again.
Waiting on a fix here too.
biffsmash said:
Playing ShadowGun and Riptide GP on mine produce this issue, and turning the screen on and off works for a few seconds, then it happens again.
Waiting on a fix here too.
Click to expand...
Click to collapse
You guys should go here --> http://code.google.com/p/android/issues/detail?id=23044 and star this as well as leave a comment. Hopefully this will help get the ball rolling. It's happening across every model of gnex. I think that it's almost impossible that google doesn't know about this yet but whatev, can't hurt.
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...
Hi Guys!~
Hope all is well !!
... recently I came across my rooted android 11 Pixel 3XL got a screen flashes with bright home screen background during the screen turning off and entering ambient display mode.
I try my best to find a solution but haven't found one yet.
I have tried to reflash to stock, also doesn't fix the problems.
... the only solution I found at this moment is to get android 12 beta which the transition animation from turning off the screen to the wake up of ambient display is totally different and I still prefer to stay with rooted android 11.
Your browser is not able to display this video.
Sounds like a hardware failure, display or mobo.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
haritvii said:
It only happens when the screen turning off from home screen or app.
Trying to shoot a vid to show the issue now.
Click to expand...
Click to collapse
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
blackhawk said:
Sounds like a hardware failure, display or mobo.
Click to expand...
Click to collapse
blackhawk said:
If you tried multiple roms especially the stock* one unless it's something you loaded after the flash, it's got to be hardware related. It's possible the non stock rom blew out some hardware too.
Try setting brightness to manual.
A rework around may be the only viable solution.
You ever wonder what happens when one or two of the billions of semiconductor junctions/resistors/caps fails in the chipset or display? You might be looking at an example
It could be a loose connection, or a faulty ribbon cable/connector, a subassembly maybe even battery (if so there be more symptoms).
*unless a known issue in this device.
Click to expand...
Click to collapse
Thank you so much, now I got a great reason to get a new Pixel 6 then
haritvii said:
Thank you so much, now I got a great reason to get a new Pixel 6 then
Click to expand...
Click to collapse
I could be wrong... and even if it is hardware that doesn't mean a work around doesn't exist to make it usable.
Play with it, Androids wuv attention