Related
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
I want to say that I noticed something similar the other day, but it was short-lived, and I'm not 100% sure. It wasn't long enough or bad enough to make me think the phone is defective, but I'm a bit used to funky capacitive button responses from my N1 days.
I can't reproduce the issue right now, though. How much usage are you talking about needing to duplicate?
Does your phone get hot, or feel hotter than normal when this happens?
I'd see if there's some particular pattern or software that seems to trigger it if you're interested in trouble-shooting.
The problem goes away when I don't touch the phone for a while (it seems that 1 hour is enough to reset the problem).
It seems "recharging".
Then with normal usage, nothing in particular, just even browsing in the settings/maps/market/browser etc., in few minutes the problem appears. The button definitely loses his "power".
It's very annoying, and my friends confirmed the same behavior.
EDIT:
Forgot to sat that the phone is not getting hotter, everything else is really normal.
Cheers
Mine definitely can be used for much more than a few minutes without the problem you're describing appearing.
I'd take it back. Factory reset the phone to protect your private data before taking it back. After the factory reset, you might want to test the behavior again, if it went away, the phone's not defective, you just had some software glitch.
Reminder, factory reset erases everything on the phone, so if you do it as troubleshooting step, be prepared to have to set the phone up from scratch again...I'm sure you knew this, but just covering my butt in case you didn't. It's a good trouble shooting step no matter what if you don't mind the hassle of re-setting things up.
I have a similar experience with the back button. Not sure what to think yet.
Sent from my Nexus S using XDA App
I had a similar problem when I had the Vibrant. Just exchanged it and luckily I got a better one without any problems. I did find out though if you are using the screen protector that came with the phone, it can cause this type of problem.
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
michele72 said:
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
Click to expand...
Click to collapse
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
distortedloop said:
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
Click to expand...
Click to collapse
Thank you, giving it a try.
Anyway, today I factory-reset my telephone and the problem of the back button is still there. I am returning the device.
Back button non responsive
Hi,
I just got my new nexus S (about an hour ago) that I was really excited about and am faced with a problem with the back button too.
Its got factory settings, so it cannot be a downloaded software issue. Also, I have not yet charged the battery at all, its still running on the same battery power that it shipped with.
The other buttons at the bottom of the phone (home, menu and search) all respond fine, its only the back button that does not seem to work. After going through this thread, I tried long-pressing the button, hard-pressing it, pressing just above it, below it, etc. It just wont respond. I had removed the screen protector it shipped with, so that cannot be the issue either.
If this is a known hardware problem (i.e. others have faced it too), irrespective of whether it is acknowledged by Samsung / Google, I'll return the handset. I do not want to spend a fortune and be landed with a handset that does not work - forget working as desired, but it does not seem to be working as designed !
Thanks & Regards,
Rohan
Yep. Definitely a problem here with the back button. There's also two other threads here about it.
I'm having similar problems. I have to touch the button just right for it to work properly
Sent from my Nexus S using XDA App
I was experiencing the same thing with my Nexus S, wasn't sure if it was the case I was using! Took of case and still had problem. I eventually returned mine cause it seemed like it was getting worse! I have a new one worth no problems, definitely a hardware problem! Return it!
Sent from my Nexus S using XDA App
michele72 said:
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
Click to expand...
Click to collapse
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
same issue was with Nexus 1. less responsive buttons. thats why there is a bigger gap between the buttons and the screen for galaxy S phones. i dont know why they did such a thing again with the nexus S. its like samsung didnt learn from anything from HTCs mistake.
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
I think this is true ...
I have an HTC Desire with AMOLED screen.
When I play a finger intensive game, like "SkyForce Reloaded", after some times, the touch is not registered.
Then I must stop for a while, or change finger
Try that, you will know what I meant.
But, I don't have issue with the back button on HTC Desire because it is a hardware button. I am just trying to explain about loosing touch registration because finger interaction on (s)amoled screen.
PS: SkyForce Reloaded is an old school shot'em up game where you control a little space ship with your finger, shooting enemies.
ll_l_x_l_ll said:
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
Click to expand...
Click to collapse
The Desire's digitizer is the same Clearpad 2000 which is used in the Nexus One (and quite a few others), the problem there is that it's pants.
Rusty! said:
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
Click to expand...
Click to collapse
lol, isnt called like that because it registers the heat from your fingers. thats why if you try to use a pen, it wont register . and thus. the screen is NOT resistive type "where it will recognize anything since its being pushed by force ? "
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Rusty! said:
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Click to expand...
Click to collapse
from your link
"A capacitive touchscreen panel is one which consists of an insulator such as glass, coated with a transparent conductor such as indium tin oxide (ITO).[7][8] As the human body is also a conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. Different technologies may be used to determine the location of the touch. The location is then sent to the controller for processing.
I just got the 32G version transformer. There is a very annoying problem with the touch screen: sometimes it is not registering my touch at all, sometimes it seems that you have to push hard.
I am not sure if this is the touch screen problem or the system is busy with something else?
Anybody else having the problem? Any ideas to solve it?
The firmware is the latest version.
I too have noticed this issue from time to time. Not sure what it is though.
Sent from my Transformer TF101 using XDA Premium App
The touchscreen does seem a bit insensitive on my 16GB TF. Not necessarily unusable, but sometimes I have to touch a button a couple times to get it to respond. Most often the menu button that appears in the top right corner of some apps.
I am pretty sure this is a software related problem. Sometimes, the touch screen feels quite responsive.
What is the official way to report problems to ASUS?
cooldragon777 said:
I am pretty sure this is a software related problem. Sometimes, the touch screen feels quite responsive.
What is the official way to report problems to ASUS?
Click to expand...
Click to collapse
Indeed. The touch digitizer and even it's driver works flawlessly - start Fruit Ninja HD and you can enjoy most responsive multi-fingers (4 or maybe more) touch ever.
But everything except games is considerably less responsive to touch.
The touchscreen on mine just completely died. Completely not responsive. I wish I could blame it on a faulty app or something simple but I put it to sleep and when I woke it 20 minutes later, I can't do anything with it. It responds to all the physical buttons just fine and the screen rotates and everything but it just doesn't respond to any touch.
mrgilmorean said:
The touchscreen on mine just completely died. Completely not responsive. I wish I could blame it on a faulty app or something simple but I put it to sleep and when I woke it 20 minutes later, I can't do anything with it. It responds to all the physical buttons just fine and the screen rotates and everything but it just doesn't respond to any touch.
Click to expand...
Click to collapse
Did you try cold reboot? I experienced same issue one time.
Sent from my Transformer TF101 using XDA Premium App
Vadimus_ca said:
Indeed. The touch digitizer and even it's driver works flawlessly - start Fruit Ninja HD and you can enjoy most responsive multi-fingers (4 or maybe more) touch ever.
But everything except games is considerably less responsive to touch.
Click to expand...
Click to collapse
I just installed Fruit Ninja HD. Although I am a newbie in cutting fruits, I am pretty sure the touch screen just doesn't register sometimes, even in Fruit Ninja.
My firmware build number is: HRI66.US_epad-8.2.3.9-20110423
Coming from Xoom, although the TF's IPS is much better than Xoom, but the touch experience of the TF is much much worse.
Sometimes you have to press hard and longer to register, I am wondering if there is a way to change the touch screen's sensitivity?
Whatever reason it is, it should be very easy for ASUS to reproduce the problem and fix it!
Try the app Multitouch Test in the market. It seems to be a lot more sensitive than some of the other apps are (or even the OS) regarding touch sensitivity. (Or at least it seems to be)
https://market.android.com/details?id=de.greenrobot.multitouchtest&feature=search_result
dustindw said:
Try the app Multitouch Test in the market. It seems to be a lot more sensitive than some of the other apps are (or even the OS) regarding touch sensitivity. (Or at least it seems to be)
https://market.android.com/details?id=de.greenrobot.multitouchtest&feature=search_result
Click to expand...
Click to collapse
Thanks. Downloaded and tried.
When it's normal, it can track 10-finger touch easily. However, the main problem seems to be the response time for repetitive touches. The system seems to be not able to keep up with normal typing speed touches. It will register several touches, then non-responsive for a while. If you wait a while, like several seconds, it will respond again.
Is there a good APP to check CPU settings and utilization ratio?
Vadimus_ca said:
Did you try cold reboot? I experienced same issue one time.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
What do you mean by cold reboot? I have reset it a few times by holding down the power button.
Interestingly, this thing is mentioned in Engadget UK's review (http://hartantolestari.info/search/asus-eee-pad-transformer-screen-is-not-working)
A lack of responsiveness is also evident throughout the Android UI. Aside from a delay in activating the function you’ve selected, there are also troubling instances where input isn’t registered at all. That leaves the user with no less than three potential scenarios when she doesn’t see an immediate response — she could be looking at lag, an unregistered tap because of software, or an unregistered tap because the physical input was too light. Such uncertainty doesn’t build a great user experience and the Transformer, unfortunately, doesn’t offer a great user experience. Much of that is, regrettably, down to Honeycomb itself. It’s not a finished product yet. It’s actually a fair distance away from a finished product. Some apps are done to absolute perfection while a lot of the “glue” bits, the stuff that goes between the apps and basically makes up the OS, is either confused, not responsive enough, or broken in some other way. Let’s take these things in turn, starting with the good parts.
Click to expand...
Click to collapse
I would reccomend against pressing hard. That is a good way to damage the lcd panel and the digitizer hardware. Capacitive screens dont register pressure just electircal conductivity from skin touching the screen. I would say any lag you are seeing is most likely software based as others have said.
Sent from my Transformer TF101 using XDA Premium App
Hmm, I have tried rebooting the device many, many times and still no change. I wiped user data hoping it would help (nope). I just don't understand why the touchscreen would stop being responsive to any input. It wasn't jostled around or treated badly in any way. I just had it in my backpack, which I was carrying by hand and the Transformer was in a padded compartment.
Overall, I am rather disappointed and disillusioned with Asus. The Transformer's terrific when it works but I've had to deal with the deep sleep issue at least once a day and then to have the touchscreen go dead entirely is terrible. The first I can see being a software issue that can be fixed but the second is probably shoddy hardware.
mrgilmorean said:
What do you mean by cold reboot? I have reset it a few times by holding down the power button.
Click to expand...
Click to collapse
Cold reboot is holding power button until TF shuts down, ignoring shutdown dialog.
Sent from my Transformer TF101 using XDA Premium App
cooldragon777 said:
Interestingly, this thing is mentioned in Engadget UK's review (http://hartantolestari.info/search/asus-eee-pad-transformer-screen-is-not-working)
Click to expand...
Click to collapse
almost seems as if they didnt test the xoom. it feels faster than the tf bc its screen is more responsive.
i wonder if the screen could be calibrated manually with the config.ini lie the nook color.
Here is some update: after the TF slept for a night, I pushed the power button. The touch screen is just not responding at all on the lock screen. I let alone the TF for half an hour or so, pushed the power button again, now the touch screen worked fine. Unlocked and into the home screen, no problem with touch for about 30 seconds, then it becomes intermittent again.
I will call ASUS support tomorrow. Hopefully there will be some firmware update very soon to address this, otherwise, I will have to return it.
The weird thing is that if this is a software/firmware issue, lots of people should have reported it.
OK, I have created a case at vip.asus.com/eservice/techserv.aspx
Looking at some Youtube clips reviewing TF, their touch screen seems to be fine. So this might be a bad unit. I will return it next week (bought from local Fry's) and hopefully they have replacement units!
I have created a vote regarding the TF's touch experience.
cooldragon777 said:
OK, I have created a case at vip.asus.com/eservice/techserv.aspx
Looking at some Youtube clips reviewing TF, their touch screen seems to be fine. So this might be a bad unit. I will return it next week (bought from local Fry's) and hopefully they have replacement units!
Click to expand...
Click to collapse
Good luck! I got mine from Amazon and they are completely out of stock. The only option is to get a refund since they don't have an expected in-stock date so the CSR can't put a replacement order in for me. Every online retailer I've looked at is also OOS. Hopefully more come in soon.
I also spoke to Asus and they are willing to repair mine but not to give me a loaner or just outright replace it. That is really too bad. I was hoping they would be more like HTC, which has great customer service in my experience and gives out replacements at the drop of a hat. If the Flyer wasn't such a POS, they would have had my business.
Bad day today. This morning started out with a very difficult time getting the screen to work. Everything took 2-3 touches. Some things I had to give up on. This lasted all day. A short while ago I was reading some pages and it got so bad I just pulled out my tablet. 10 minutes latter I grabbed the phone and it would not activate...just a black screen. Battery pull required. I recalled reading about black screens of death.
Is this part of a normal pattern of quality decline I'm seeing? Ill keep an eye on it for a few days, I have a 30 day remorse period.
Thoughts, suggestions, words of wisdom? Just don't say root..won't root in the remorse period.
alodar1 said:
Bad day today. This morning started out with a very difficult time getting the screen to work. Everything took 2-3 touches. Some things I had to give up on. This lasted all day. A short while ago I was reading some pages and it got so bad I just pulled out my tablet. 10 minutes latter I grabbed the phone and it would not activate...just a black screen. Battery pull required. I recalled reading about black screens of death.
Is this part of a normal pattern of quality decline I'm seeing? Ill keep an eye on it for a few days, I have a 30 day remorse period.
Thoughts, suggestions, words of wisdom? Just don't say root..won't root in the remorse period.
Click to expand...
Click to collapse
Ummm.....
Rom?
Kernel?
Uv?
Profiles?
Oops didnt finish reading post. Root!
G2X
Sotty to say this mine does this.
Are you using auto brightness?
That's when my phone acts funny and don't want to wake up.
Sent from my LG-P999 using XDA Premium App
KRAZYADROIDMASTER said:
Sotty to say this mine does this.
Are you using auto brightness?
That's when my phone acts funny and don't want to wake up.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Everything is stock out of the box. If auto bright is selected by default then yes.
What timing for this to occur. My sensation just arrived in Seattle for delivery tomorrow. Was hoping for an honest comparison.
when i first bought the phone, the screen felt insensitive too, also 2-3 touch, especially that "touch android" in the beginning to set it up. It was ridiculous for first impression
But hey, i rooted it and flashed it with a rom & kernel so everythings all good
If it helps the first g2x I got 420 I didn't root and it wouldn't turn of after a week .. rooted replacement with faux and now its been good
Sent from my LG-P999 using XDA App
Sounds like after awhile the phone starts to misbehave on stock everything. I have seen other ppl complain having same issues while on stock.
I had a my phone getting hot and it rebooted after that and then apn would not stick. I'm glad I had apn backed up so it wasn't much of a problem.
Sent from my LG-P999 using XDA App
Well my sensation arrived this morning at 1113. Its now 137 and its still not running. Apparently are still downloading. On the G2x, same apparently 20 minutes tops.
First thoughts after that, sensation is only a few fractions wider. Side by side no wifi, g2x pulls 2 bars 4g. Sensation 2bars 2g.
Screen comparison ...toss up..both look good...better? ?? They are different...
Scrolling is different. G2x is smooth uni page, a continuous page action. Sensation is page by page.
So far I'm leaning strongly towards g2x...except for that touch screen worry. That plays very heavy here. With no fix in sight, g2x would go back. But I've got 30 days
Sent from my LG-P999 using XDA Premium App
Just perform a factory reset or reflash your rom and kernel to fix the black screen issue. Mine started doing it and that fixed it. Everytime I tried to unlock the screen it went black but was still on technically cuz I could unlock and open apps. I had to hit the unlock button and have mg finger on the screen already to keep it from going off, then I could unlock it.
JHaste said:
Just perform a factory reset or reflash your rom and kernel to fix the black screen issue. Mine started doing it and that fixed it. Everytime I tried to unlock the screen it went black but was still on technically cuz I could unlock and open apps. I had to hit the unlock button and have mg finger on the screen already to keep it from going off, then I could unlock it.
Click to expand...
Click to collapse
hes all stock but yea he could do a factory reset of stock rom i dont really see it doing anything unless there is a corrupt app and the way to fix that is factory reset then when it says restore backup data you uncheck it, this way it doesnt restore anything or any app that was corrupt and then start fresh one app at a time, and keep it on for a few days then if its good add another app. thats the real way to find out, it is tedious and time consuming but it u will find out what it is. but... after the remorse period he could add throw on another rom and kernel that solved my issue with sleep of death issues on stock
With stock there is a bug where it is always in engineering mode or something like that. There is a patch available in the development section, but don't remember if root is needed to apply it. How long since you last shut the phone off? If I remember right, that bug would cause everything to slow down really bad after a couple days. Try rebooting once a day and see if this issue comes back. If that works, you may be able to get by until you are willing to root.
jsapp said:
With stock there is a bug where it is always in engineering mode or something like that. There is a patch available in the development section, but don't remember if root is needed to apply it. How long since you last shut the phone off? If I remember right, that bug would cause everything to slow down really bad after a couple days. Try rebooting once a day and see if this issue comes back. If that works, you may be able to get by until you are willing to root.
Click to expand...
Click to collapse
Yes root is required because it requires ClockWorkMod to flash it.
This is why the phone boots up so quick out of the box because it doesn't preload anything but this causes it to become overloaded and run out of memory after some use and locks up.
The LG O2x had the same issues.
Stock REQUIRES the patch to function properly. Or just flash CM7 and enjoy the wealth of great features.
player911 said:
Yes root is required because it requires ClockWorkMod to flash it.
This is why the phone boots up so quick out of the box because it doesn't preload anything but this causes it to become overloaded and run out of memory after some use and locks up.
The LG O2x had the same issues.
Stock REQUIRES the patch to function properly. Or just flash CM7 and enjoy the wealth of great features.
Click to expand...
Click to collapse
My thinking...and pardon the train of thought....if something out of the box is broke...like this....then...rooting it still leaves me with a device that had to be fixed...by me. I had 10 days of no issues with the G2x. I ordered and received the Sensation only because my son has one...and its nice. I have 30 days to try them out. I wanted to test them side by side....for basic comparison, the way I use a phone. Once I decide which one to keep, then root will most likely follow. But rooting to be able to compare side by side....misses the point of the comparison.
3 hrs after starting the setup on the Sensation...the battery is charged and everything is setup to test. One of the first, less obvious things I noticed on the Sensation is the multi tasking....running things like restore and browsing at the same time...is way slower than the G2x. It took 90 minutes to download the apps from backup....on the Sensation....the G2x is maybe 20 minutes. That couldn't be right and I tried it again. Still a long time. Finally I tried it again..and just let the phone sit...didn't do anything else....it downloaded just like the G2x.
When considering which phone, do I think about that slowness...in comparison to say....the Touch problems, Black screen problems....and reported rebooting....sure...thats why I'm testing them side by side.
alodar1 said:
My thinking...and pardon the train of thought....if something out of the box is broke...like this....then...rooting it still leaves me with a device that had to be fixed...by me. I had 10 days of no issues with the G2x. I ordered and received the Sensation only because my son has one...and its nice. I have 30 days to try them out. I wanted to test them side by side....for basic comparison, the way I use a phone. Once I decide which one to keep, then root will most likely follow. But rooting to be able to compare side by side....misses the point of the comparison.
3 hrs after starting the setup on the Sensation...the battery is charged and everything is setup to test. One of the first, less obvious things I noticed on the Sensation is the multi tasking....running things like restore and browsing at the same time...is way slower than the G2x. It took 90 minutes to download the apps from backup....on the Sensation....the G2x is maybe 20 minutes. That couldn't be right and I tried it again. Still a long time. Finally I tried it again..and just let the phone sit...didn't do anything else....it downloaded just like the G2x.
When considering which phone, do I think about that slowness...in comparison to say....the Touch problems, Black screen problems....and reported rebooting....sure...thats why I'm testing them side by side.
Click to expand...
Click to collapse
And, as I'm sitting here....the G2x just did its first reboot. this kind of tells me...well... lets wait a week....and see.
I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Video - http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be
Simular to this issue
http://forum.xda-developers.com/showthread.php?t=1826676
legauxg said:
I have touch screen issues and I'm not sure if it is Hardware related or software.
I will be using my tablet and all of a sudden I lose 90% of control. Basically, I can't touch anything. I know most would say that hardware but, I cycle the power button (Not turning tablet off just screen off screen on) and touch comes back.
I noticed this issues when ICS just came out for our tablets and we were getting major RR and SOD.
Any one else experienced this or am I the only crazy person that this happen to.
Thanks in advance.
Ps. If you have experienced this please post solution.
Click to expand...
Click to collapse
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.
MasterDecker said:
It sounds like you may be on a different ROM then stock. I would recommend a couple of things. First back your system up, and do a clean install. Clear all cache and go. If your on a non stock ROM, then It would probably be a good idea to visit the thread of that ROM and see what they have had come up about the issue.
Click to expand...
Click to collapse
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.
legauxg said:
That is correct I am on Non- stock rom. Guess I should have said that. Should i go all the way back to original rom (HC) then up grade to ICS(stock)?
I have tried multiple custom roms but they all seem to do the same thing. Me being a comp. tech. the way I can restore touch by power cycling makes me think it is software.
Click to expand...
Click to collapse
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel
pops106 said:
I have had it before but very rare, power tap the power to turn off the screen then tap it again and it all comes back?
It is so rare I just live with it.
Probably been the most stable on eos3 81 with kat 69 kernel
Click to expand...
Click to collapse
From you response, this is why I am thinking this is related to software. I do not have the proper knowledge to research but I am asking help from a knowledgeable person.
I screen losses touch regularly now. it is taking away from my experience. Are there any drivers particularly for the screen input that can be updated or downgraded to a known working version.
Thanks for not making me fell like I am the only crazy person!
Video to show what Im talking about
http://www.youtube.com/watch?v=oO9-D2QJks0&feature=youtu.be
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
60puc said:
I noticed, that my 1+1 always works ok on stock roms (cm11,cm13 from this forum) and when i set up Android Oreo or Halogen (7.1.2 unoff) or even Flyme 6, my screen don't want to wake up from time to time, buttons vibrate, sound works, all works except screen. Even though, i noticed one way to wake it up, just repeat the touches some times, double tap to panel (i don't see it), and again, to block the screen... it wake up always, or reboot sometimes, but this is not a variant to use at real situations. somtimes headphones help, sometimes usb cable, but no 100% solution.
may be someone know how to solve this problem? i saw a lot of messages here about SOD, and no solution. just something about a modem or flash stock, but this is a software trouble, may be it is firmware.zip or just one .bin file inside (power management). may be this error can be solved?
I really want to go to Oreo and today i tried to do it, but when I suddenly understood that it doesn't work again (after stock) i decided to go back, no way to use it. may be i should take some files from stock?
Click to expand...
Click to collapse
This has happened to me before.What I simply did was replace the display.
Mr.Ak said:
This has happened to me before.What I simply did was replace the display.
Click to expand...
Click to collapse
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
60puc said:
that's the way, but not for me. i've just changed my display, i just can check old one, it is not broken, just a dead zone on the touchscreen. but it means that the revision is incorrect, it is something like a driver, i think. i already had the same situation with a old tablet, it didn't wake up anytime after boot, it was discussed at 4pda, so people found, that only one of the 3 revisions works ok at last firmware, i had 2 type of display and could to swith and check it. but it wasn't so good with colors, so i stayed at stock. it seems that situation is the same now.
Click to expand...
Click to collapse
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Mr.Ak said:
Nope,I'm pretty sure it's the display that you changed.Get a refund or replacement.
Click to expand...
Click to collapse
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
60puc said:
Why do yoy think so? Stock fw can realize all functions for that display, why custom can't do it at the hardware level? no reason to think so.
Just only one idea - is a revision. Now i can try my old display. And if i'd manage to change touchscreen, that can be a solution. But i don't.
Click to expand...
Click to collapse
As I already said,the same issue happened to me after I changed my display.I asked for replacement and replaced that damaged display,boom! I don't know what's so hard in it for you to understand.
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
60puc said:
Thank you for advice. I've just opened a dispute. Today it didn't woke up at stock firmware.
Click to expand...
Click to collapse
Aliexpress?
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
60puc said:
Yes. But at first everything was ok. And when i installed oreo it stops some times and Sod started. I tried to use 7.1.2, it SOD's anyway. Then the stock was the solution. I'm already relaxed, and decided that it is software error, but after a few days it started again.
I've accepted this display, but with your help it's not so late to open a dispute. I think it will be ok.
Click to expand...
Click to collapse
Get ready with a lot of proofs tho'!
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Gab_echelon said:
to me it happens, I do not know if it is the same as described, but unlocking the screen works everything but not touch, lock, unlock, and it works, what is it due?
Click to expand...
Click to collapse
See previous page,I've already explained what is the cause of the issue.
I just finished replacing my screen, been waiting for my broken antenna cable and volume button flex to arrive. Everything works except the damn SOD i never had with my old screen. Tried turning off the proximity sensor check and still a no go. The screen turns on fine initially and trying to wake it instantly works all the time, but if I leave it off for any longer than 5 sec probably it won't respond to anything - power button, volume button, double tap and plugging in the usb cable connected to a power source.
Does this sound more like a governor issue? The rom installed is lineageOS (just updated to 10-30 release). Looking up my purchase log to open a dispute...
tested it again, repeated lock/unlocks puts it into the SOD state, doesn't even take 2 sec to do it...
oh wow, it does this even in the twrp recovery. I have wiped cache and dalvik cache just for the hell of it but doubt that was the real cause...
Gab_echelon said:
works everything but not touch
Click to expand...
Click to collapse
we've got a reverse situation. touch, buttons, sounds, modem works, but not screen (if you lock/unlock it 10-20 times it can raise again without reboot.
Buratei said:
it does this even in the twrp recovery.
Click to expand...
Click to collapse
i've got the first SOD in twrp mode. it doesn't matter, but at first - no troubles were with that. and now it works so so at home. and if i use it outdoor it becomes very often, but at home it seems that it works ok, just only seems, because if i want - i can do some manipulations (use camera, lock/unlock it etc) and the SOD appears again. but custom os executes SOD more frequently. i think it can be real overvoltage, like people says.
there are many posts here and everyone advices not effective solutions (flash stock, modem, fw ...) at first it helped me, but now i know there is no way, i can just try but ...
long time ago i owned an old tablet iconbit matrix - it has just the similar issue. it boots, but if you go to a sleep mode - it didn't wake up every time. it lights works ok inside, but no image. i had two displays and if i used one in a custom rom it worked ok, but not another one. stock rom works ok with every display. the solution was a display driver, like at windows OS.
cause of developers bugs, it was a little different (not stock-based) and some revisions of display works ok, others aren't.
so, i think it can be fixed, but the solution for me - change a display like the first reply says. Ali seller read this topic and posted me this in a few days after i started this topic:
Your dispute has been processed and the money will back to you in 7~10 working days.
so could you give us a positive feedback, please?
Best regards.
so, i'll order another one, no trouble, i hope this will help me to enjoy my oneplus.
60puc said:
so could you give us a positive feedback, please?
Best regards.
Click to expand...
Click to collapse
They always ask for positive feedback in exchange for refund/replacement.Bastards,aren't they? @evronetwork
For the sake of other people that'll read your feedback and make their decisions upon it,don't do it! Just complain this bribery to aliexpress staff ffs!
well I wish I bought from aliepxress... I bought mine from ebay to pinch some pennies, and because I was waiting on other replacement parts (which were only needed due to damage occurred during a screen replacement op) to ge here I am way over the protection period. aw shiiiiit, I guess you live and learn
gotta tell you though, the screen is a bit wacky in other ways too. the capacitive buttons do light up but not completely (kinda dark in the corners) and the colors look a bit off. hopefully the seller would honor the refund/return request...
EDIT: whoa... kinda hard to believe, but I messed around with battery profile just for the hell of it and by some pure luck discovered that the "performance" profile (second one from the far right) works just fine and wakes the screen every time. The "balanced" profile and everything below that gives me an insta-death. go figure!
EDIT2: guess I spoke too soon. it sure as hell looked like fixed, but it came back after a while. maybe it is just more sporadic than I thought...
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
60puc said:
No solution yet? I think, that it can be some trouble with lights (this wire with 3 contacts), because touch starts, but no image. may be the signal comes to the matrix, but it is not enough energy to enable this diods. what can we do? im going to change the back side of the screen.
ow, no way, don't even try, it has combined technology. i disasabled the whole wire, no chance there...
http://i102.fastpic.ru/big/2017/1215/50/bd4e28b5b320ad2b4de26baf9d809350.jpg
http://i103.fastpic.ru/big/2017/1215/28/9803686e8a12d29baa902c3a2577de28.jpg
Click to expand...
Click to collapse
What happened to getting a new display?
I use this one, because it works ok, but only at home. As a home tablet. At the street it fails every time.
I can reboot it if it doesn't wake up. But it wakes up often, so i don't want to order new one now. I want to check my mainboard to be sure, that it is dispaly problem
a bit late, but thought I should update on the situation... all working fine after a (yet another) LCD replacement. Much better color balance to boot, points to QC problems at the supplier's end. If I ever have to do this again, I am definitely going to inspect the new LCD as soon as I receive I receive it.