So I'm sure SOME of you must have noticed that the Galaxy Nexus screen isn't as sensitive as.. lets say Nexus S or S2.
If you check, the pressure required to get a touch registered is around 0.30. This value is much lower on other phones (like about 0.15 on Nexus S).
There were apps for Galaxy S that fixed screen sensitivity issues.. What I'm wondering is, is there any such app for the Galaxy Nexus?
Well yes, check out my thread about it.
http://forum.xda-developers.com/showthread.php?t=1576739&goto=newpost
However I'm fine with 0.30, I can get to 0.28 even. But there is a bug after a few minuted of use it decreases and stops detecting values below 0.40. Locking the screen temporarily resets it. Someone should dig tgru the kernel code to see if we can change this.
Interesting. Maybe that's why I miss keys while typing. Seemed my G2x was great in this regard.
Sent from my Galaxy Nexus using xda premium
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
player911 said:
Interesting. Maybe that's why I miss keys while typing. Seemed my G2x was great in this regard.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I miss tons of key presses, so probably yes. When I lock then unlock the screen I miss none and its super sensitive again. Its like night and day difference.
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
ASKnASK said:
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
Click to expand...
Click to collapse
I think this is a very hard issue to diagnose. Must be some type of memory leak or something.
I have been noticing this more and more.. hope some dev figures out a way to up the sensitivity!
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
I've don't know if I experience the same issues you guys talk about but sometimes I can't use the softkeys. Like they're unresponsive... I have to pick up me GN or wait for a good 4 to 6 seconds before it registers my touch. I have no idea if it's because of the touch issue you guys are talking about. But has anybody any idea what causes this or if I'm on a totally different issue here?
Sent from my Galaxy Nexus
neotekz said:
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
Click to expand...
Click to collapse
I'm 99% sure this has no effect beyond placebo for the Galaxy Nexus. I installed it, thoroughly tried it out going back and forth between the options, and there was no increase in sensitivity. Light touches were still being missed.
neotekz said:
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
Click to expand...
Click to collapse
bengrulz said:
I'm 99% sure this has no effect beyond placebo for the Galaxy Nexus. I installed it, thoroughly tried it out going back and forth between the options, and there was no increase in sensitivity. Light touches were still being missed.
Click to expand...
Click to collapse
Placebo it is.
It doesn't work for the GNexus, though it DOES work for the Nexus S (reviews).
I wish someone would fix this :s
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
ASKnASK said:
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
Click to expand...
Click to collapse
Because we don't see the issue?
natious said:
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My phone responds to the touch of the skin on my leg, through my jeans pocket.
natious said:
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm pressing the screen EXTREMELY light, like barely touch inputs. When I do fast typing the finger tips kinda fly around on each letter.
It works fine and just as accurate as normal. Then the bug kicks in and the sensitivity reduces and suddenly misses about 50% of the presses. It feels mushy. Lock the screen and it fixes it back to normal. It must be some memory leak type issue.
How do you know it isn't a memory leak with an installed application?
adrynalyne said:
How do you know it isn't a memory leak with an installed application?
Click to expand...
Click to collapse
are you saying your gnex have not this issue?
please can you make a test?
go to dev setting and enable 'pointer location'; on up/dx of the screen you have 'prs' ... pressure of every your touch... try to register a touch at 0.30 or less pressure.... it's not possible, i think 0.27/0.28 is the limit... lighter touch don't register (gs2 or NS register this kind of touch)
Exactly, 0.28 is the best I can register. When the bug kicks in, suddenly you can't register below 0.40 or 0.45, no matter how much you try. Lock the screen and it fixes itself. So frustrating.
Lowest I got was 0.27 after playing with it for a minute or so. Anyways, I don't really notice a difference coming from an LG G2x. I guess there is, but I'm assuming I always press hard enough that I don't notice.
As to the other bug of not registering under .40 or higher, never had it. Running AOKP 37 + Franco M3 if that makes a difference.
I've the same problem with my 24h new Nexus are there devices without this bug ?
Inviato dal mio Galaxy Nexus con Tapatalk 2
I am having this exact same issue. Upon initial unlocking the deice registers key presses smoothly and will continue to do so until a lull of interaction. One the device is inactive but the screen remains on the screen comes highly unresponsive. I would say that those who are not experiencing on their stock devices probably have their screen lockout time low enough that the bug does not have time to appear prior to the phone requiring it be unlocked anew.
I have a 32 GiB Stock Nexus 7 running 4.1.1 Build JRO03D.
My screen timeout is set to 10 minutes.
Related
Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Just to make things perfectly clear, here is a video of the delay time:
http://www.youtube.com/watch?v=vqJc_nYuwac
*older update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.
mine is doing this too.. are you using a SD Card wallpaper? I am. not sure if thats affecting things.
I have not noticed any delays on mine.
I have noticed this as well. I'm using a stock wallpaper.
Sent from my SPH-D710 using xda premium
thedeadletters said:
Just picked up the phone today and noticed a long delay between pressing the power button and the screen waking up. When it is plugged in there is no delay at all. The delay occurs whenever the phone is disconnected from a power source. It is about a 2 second delay. Is anyone else experiencing this? Best Buy didn't have another unit and the Sprint store was useless and wouldn't unplug their demo unit to compare.
I saw a thread concerning the standard Galaxy S II, but nothing Epic 4G Touch specific.
Thanks.
*update*
Downloaded Soft Locker Free and it allows the phone to instantly wake with no delay by bypassing a deep sleep mode. I'm unsure about how detrimental this is to the battery, but at least it's a fix. I'd still like to know if all Epic Touch phones have the wake up lag, though.
Click to expand...
Click to collapse
You shouldn't do that, it will be detrimental to your battery. Deep sleep mode means that the processor is technically off, provided the phone doesn't have any tasks to run while the screen is off.
Its perfectly natural for your phone to wake up immediately when plugged in, because that's how samsung designed the galaxy's. No need to deep sleep when the phone's getting a charge.
By restricting your phone from sleeping (affectionately referred to as wake lock),your forcing your processor to run for nothing, most likely at 200mhz. When it's all said and done, I estimate you'll end up shaving off about 5 hours of battery life. Not worth it to me, just learn to deal with 1 sec it takes to wake up the phone.
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium
squshy 7 said:
On a lighter note, I find it amusing that you've installed an app that now makes the phone do something that is commonly known as a bug and a lot of people spend their time trying to squash. Lol.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.
daneurysm said:
+1LOL*10
The amount of threads I have read, the hundreds if not thousands of posts I have seen the hundreds of developers that have all chased wake-lock bugs are all disgusted right now. Thousands if not tens of thousands of man hours have gone into chasing the wake-lock bugs down on many many many devices....in roms, in kernels in conflicting apps. For years. Sometimes its simple, sometimes it's given up on completely.
You are right. Wow, just, wow.
Click to expand...
Click to collapse
Lol, I'm actually crying a little from laughter. The scenario you described was exactly what went through my head when I wrote that
EDIT: to the OP, this is all in jest, no offense meant. But seriously, don't wake lock your phone.
Sent from my SPH-D700 using xda premium
I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.
Don't wakelock the phone.
Voluntarily wake locking a phone? Haven't heard that before lol
Sent from my PC36100 using xda premium
Journeyjeans said:
I've noticed it too, but it isn't too bad of a lag. Not snappy like the EVO 4G, but not a dealbreaker, not on this.
Click to expand...
Click to collapse
Thanks for all the responses. My past Android phones (Evo and Evo 3D) didn't have any delay whatsoever, which is the origin of the original post. The power of the Galaxy S2 phones is pretty much legendary, which is why I'm surprised about this power saving feature. Reviews boast quick boot times, but I would argue that a regular wake time is much more useful and realistic to have. I do understand the basic premise that a powerful phone consumes more battery, but that didn't make any other dual core phone I've seen require this precaution.
Therefore, why is it that others forego this feature if it ultimately saves so much battery that Samsung has made it a default feature on their latest phones?
Updated the OP with a video. Please view and tell me if this is the norm.
I watched the video, mine is not that slow delay.
justwonder said:
I watched the video, mine is not that slow delay.
Click to expand...
Click to collapse
+1 return it
Sent from my SPH-D710 using XDA App
I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response
sling said:
I wouldn't return it Hold tight for custom rom.
I'm sure tweak will be around the corner to improve wake up response
Click to expand...
Click to collapse
Funny how mine has all my apps on it... (over 40) and a **** load of music... And for the life of me I cant get it go lag like that.... I had a refurbished evo 3d that did that... I called sprint.after factory reset and.a few battery pulls... Id just return it.
roms dont fix all bugs let alone one random wake lag problem and the op may have to deal with it as most of us dont have lag like that...
@op if you got it from a store id bring it in.... if a rep says its suppose to do that.... Tell them your older android phone didnt do it... Then ask to speak to a manager
Sent from my SPH-D710 using XDA App
Yeah... I had a feeling it was worse than it should have been. Though it's true a custom ROM could fix it, it would probably implement a fix similar to Soft Locker (which is obviously shunned for its battery draining ability). Also, I'd much rather have a device in proper working order to begin with. The Best Buy I got it from only had 2 on launch day, so here's hoping I find one that has it in stock.
Thanks for all the replies.
My delay is similar to the video. How does everyone else compare after seeing the video?
Sent from my SPH-D710 using xda premium
I had the same issue. Move the pic from ur sd card to ur internal. Open in using myfiles and set as lockscreen
Sent from my SPH-D710 using xda premium
Thanks. Stupid question but how do I move it. I only know how using root explorer on a rooted phone.
Sent from my SPH-D710 using xda premium
Hi,
A few months ago while I was watching Samsung announce the Galaxy Nexus for the first time, I remember them saying Face Unlock was so fast that they actually had a delay so that "it didn't look like there was no security at all".
That said, does that mean that there could be a possibility to remove that delay?
On our device face unlock takes a while because the camera needs time to start, then we have to wait for it to recognize our face. Maybe we can get it to work faster?
Discuss.
HanMan5000 said:
Hi,
A few months ago while I was watching Samsung announce the Galaxy Nexus for the first time, I remember them saying Face Unlock was so fast that they actually had a delay so that "it didn't look like there was no security at all".
That said, does that mean that there could be a possibility to remove that delay?
On our device face unlock takes a while because the camera needs time to start, then we have to wait for it to recognize our face. Maybe we can get it to work faster?
Discuss.
Click to expand...
Click to collapse
Dude mine works fast as hell its just lighting and all that if your saying the time it takes while its black try setting cpu higher see if it makes a difference
I tried the face unlock on the ICS rom and honestly I didn't even notice a delay the thing was fast as hell....
Face unlock is fast at recognizing the face, on our phone it takes 2-3 seconds for the camera to start up, at least for me and that's what the OP is talking about.
As far as I know that's not caused by a delay its just the camera software/hardware limitation maybe it can be improved in the future by Samsung but it could be a hardware limitation.
Also the phone may be waking up at a low frequency which could cause the delay as well.
Sent from my SPH-D710 using Tapatalk
It seems to forget my face after a while and I end up using the pin almost every time.
bbedward said:
Also the phone may be waking up at a low frequency which could cause the delay as well.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
This is what makes sense to me, and that's something people are just gonna deal with when you think about battery life of keeping the system able to pull up instantly.
I made a funny face and kept forgetting that I did. lol It was fun for a little while but low lighting it sucks.
Wonder if we could somehow get face unlock for v3.x.x ?
Sent from my SPH-D710 using xda premium
Did a quick search and didn't see anything. I don't know if it's my mind playing tricks on me or if it's just switching phones. Was on the SIII for a bit and just switched to a SII until more dev support is out.
The E4GT was 100% virgin stock earlier today.
I rooted and it was fine.
After installing Caluklin's 1.6 it seems like the picture quality dropped. Text seem to have rugged/fuzzy edges.
Am I imagining things or did I miss some dpi goods?
If this is crazy talk, just tell me. The only thing I changed was the display mode and set it to dynamic. Switched back to standard and it's still the same.
chrischoi said:
Did a quick search and didn't see anything. I don't know if it's my mind playing tricks on me or if it's just switching phones. Was on the SIII for a bit and just switched to a SII until more dev support is out.
The E4GT was 100% virgin stock earlier today.
I rooted and it was fine.
After installing Caluklin's 1.6 it seems like the picture quality dropped. Text seem to have rugged/fuzzy edges.
Am I imagining things or did I miss some dpi goods?
If this is crazy talk, just tell me. The only thing I changed was the display mode and set it to dynamic. Switched back to standard and it's still the same.
Click to expand...
Click to collapse
I brought this up about 2 months ago and it didn't get anywhere...The camera on this device is pure $hit...
hooover said:
I brought this up about 2 months ago and it didn't get anywhere...The camera on this device is pure $hit...
Click to expand...
Click to collapse
Well when I say picture, I don't mean the camera. I mean over all anything. Seems like something happened even on the home screen. The whole display looks rough.
Dynamic Screen Mode causing rough edges in ICS
I just received the over the air ICS update this morning and immediately noticed the same thing with the screen clarity.
After messing around with it all day I found out that it's only evident when the "Screen Mode" is set to "Dynamic"
A huge disappointment since the colors on the Epic 4G Touch pop like nothing else in dynamic mode.
But it seems ruined or at least not worth putting up with the jagged edges everywhere to have dynamic mode on now.
i have been asking about this for months. im glad to finally see someone else noticed it. it bothers me so much I am sticking to gb
http://forum.xda-developers.com/showthread.php?t=1693511
Sent from my SPH-D710 using xda premium
it never came across my mind that it was intentionally, especially because i was using custom roms from leaks, in fact because so little people even notice it, it would kind of defeat the purpose wouldnt it?
it clearly doesnt look as good as gb on more than one eg4t i have tried, i guess everyone has different eyesight, ICS doesn't work for me on this phone because of it. disappointing. thanks for your help
Funny that I never noticed this before. Most likely because I had my phone set to 'standard' instead of 'dynamic'. When I did the change to dynamic & tested different apps I did notice jagged edges while on ICS.
Wish i could
Using AGATS kernel On Samsung Epic 4G Touch on xda premium
burningkenshin said:
Funny that I never noticed this before. Most likely because I had my phone set to 'standard' instead of 'dynamic'. When I did the change to dynamic & tested different apps I did notice jagged edges while on ICS.
Click to expand...
Click to collapse
i always use dynamic...... hmm maybe i should try it with standard see how it looks
---------- Post added at 11:28 AM ---------- Previous post was at 10:51 AM ----------
wow! the problem does only exist on dynamic mode, this has been driving me crazy since the first ics rom
Is the rattle sound I hear near the camera housing on my S3 normal? Everything seems to be working fine. Just making sure and asking here since this is the only place where I can get real answers.
Thank you all,
AJ
That doesn't sound normal to me... there is no noticeable rattle on either of the Galaxy S III's I have access to. How long have you had the phone for?
kennkcna said:
That doesn't sound normal to me... there is no noticeable rattle on either of the Galaxy S III's I have access to. How long have you had the phone for?
Click to expand...
Click to collapse
about 5 months. My old S2 had it too. Someone told me a long time ago that it was the Auto Focus and that it was normal on it.
On my moto photon the lens rattles. If you start the camera app it stops.
Sent from my MB855 using xda premium
So this would be considered normal then? I'm hoping so LOL.
asjdwf said:
about 5 months. My old S2 had it too. Someone told me a long time ago that it was the Auto Focus and that it was normal on it.
Click to expand...
Click to collapse
I just double checked, my old Galaxy S II LTE (aka Skyrocket) has a noticeable rattle when you shake it but I'm not hearing it on the S III (perhaps it's more subdued?). A quick Google search however shows that several other people have experienced the same thing and the general consensus seems to be that it's nothing to worry over.
kennkcna said:
I just double checked, my old Galaxy S II LTE (aka Skyrocket) has a noticeable rattle when you shake it but I'm not hearing it on the S III (perhaps it's more subdued?). A quick Google search however shows that several other people have experienced the same thing and the general consensus seems to be that it's nothing to worry over.
Click to expand...
Click to collapse
Yeah I just finished looking too. Thanks all
AJ
Try dropping it a few times see if the rattle will stop
Sent from my SAMSUNG-SGH-I747 using xda premium
So it comes and goes now. Checked some of my buddies phones and there's don't do it but the att stores s3's all do it. So frustrating. LOL
This plus I can't upgrade to Jellybean because it kills data connection to my phone and battery drain!!
AHHHH
AJ
Send it in if ur not happy,, dosens samsung give u a year manufacturer warranty?
sent from outside ur window
I just shook my phone and heard the power button rattling back and forth. Put you finger on it and it stops.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
When I use my Nexus 7, sometimes the screen will flash a black screen shortly, I track the logcat using the adb. But didn't find any
error information, it seems like the surfacefinger problem in Android 4.3. Dose anybody find the same problem?
------------------------------------------------------------------------
Thanks XDleader555
Reconnect the cable of LCD can fix this problem!!!!!! the casing of nexus 7 need to be opened, but it's not hard!
If you are not able to fix it, try to use the JWR66N version!
Can't say I've seen this issue. Then again, I don't have any of the issues some are complaining about. I feel so lucky to have gotten one with no problems.
Does the black screen appear when you're doing something specific or is it completely random?
Sent from my Nexus 7 using Tapatalk 4
Yes, completely random. And the black screen flash in a short time. Normally it's difficult to meet.
Try to use clean ROM, but still happen. Hope the problem relate to the software but not Hardware.
isacclin said:
Yes, completely random. And the black screen flash in a short time. Normally it's difficult to meet.
Try to use clean ROM, but still happen. Hope the problem relate to the software but not Hardware.
Click to expand...
Click to collapse
I have the same issue. For a split second the screen will flash to black (off maybe) then back to whatever I'm doing. I had my tablet since the release date, but this issue started maybe a week ago.
Having the same issue myself on Clean Rom and can't figure out a pattern. Has anyone found a fix for this? Do I need to file for a replacement? Thanks!
Sent from my Nexus 7 using xda app-developers app
when I use stock rom, screen randomly darken for just 0.1 sec. after I change to cm10.2. it hasn't happened.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am on the 8-29 cm10.2 nightly. I've tried both with and without faux's kernel same issue. Wiped my device fully last night. No luck.
Sent from my Nexus 7 using Tapatalk 4
This is so frustrating. I just passed my 30 days so I can't turn it back in for an exchange at best buy
Sent from my Nexus 7 using xda app-developers app
myron317 said:
This is so frustrating. I just passed my 30 days so I can't turn it back in for an exchange at best buy
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You should still have a warranty. I think this might be some sort of bug that could be corrected maybe. It seems weird for something like this to occur out of the blue. I may go back to stock to test or try a different Rom that didn't use cm as a base.
Sent from my Nexus 7 using Tapatalk 4
Turn off auto brightness if its on. If it doesn't help you can try desabling HW overlays in Developers options settings
moosefist said:
You should still have a warranty. I think this might be some sort of bug that could be corrected maybe. It seems weird for something like this to occur out of the blue. I may go back to stock to test or try a different Rom that didn't use cm as a base.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes that's true and a good point. I just didnt feel like dealing with sending it in to ASUS and all that rather than just taking it back to best buy (laziness). I was thinking the same thing, that there would be a repair update and missed my easy exchange window. Never been on CM with this device so not sure if it's related. Fingers crossed, just an annoyance really... Thanks!
Sent from my Galaxy Nexus using xda app-developers app
Blackwidowman said:
Turn off auto brightness if its on. If it doesn't help you can try desabling HW overlays in Developers options settings
Click to expand...
Click to collapse
Doesn't seem to help. I'm starting to lean more and more to a hardware issue...
Sent from my Nexus 7 using Tapatalk 4
If the update and the factory reset doesn't work, I strongly recommend sending in the unit for RMA. While there, we can take a look at the hardware, and if needed, actually fix it for you.
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
XDleader555 said:
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
Click to expand...
Click to collapse
I am also experiencing the same problem. I assume you had to open up the tablet to do that? I might give that a try too.
Was anyone able to reproduce this fix?
XDleader555 said:
My screen flicker (random black screen for a millisecond) went away after I checked the connection. I unplugged the screen, blew a little compressed air into the connection, and popped it back on. No screen flicker in sight after that.
Click to expand...
Click to collapse
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
did it work?
isacclin said:
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
Click to expand...
Click to collapse
Isacclin, were you able to fix it?
I had the exact same issue and after reading this thread decided to take the plunge and check the connection. I am typing this on my Nexus now so I don't appear to have broken anything, however I think I have just seen the screen flash black so the problem may still be there.
Given disassembling the thing voids the warranty I would probably recommend not risking it for this issue. I'll let you know if I change my mind.
redders6600 said:
I had the exact same issue and after reading this thread decided to take the plunge and check the connection. I am typing this on my Nexus now so I don't appear to have broken anything, however I think I have just seen the screen flash black so the problem may still be there.
Given disassembling the thing voids the warranty I would probably recommend not risking it for this issue. I'll let you know if I change my mind.
Click to expand...
Click to collapse
I take this all back. After 24 hours of no black flashes I am very happy I took the risk.
The flash I saw when I was writing the above post must have been me being over sensitive to chrome redraws or something!
isacclin said:
Hi, that is a good suggestion! I am
testing now! Wish have a good luck!
Click to expand...
Click to collapse
redders6600 said:
I take this all back. After 24 hours of no black flashes I am very happy I took the risk.
The flash I saw when I was writing the above post must have been me being over sensitive to chrome redraws or something!
Click to expand...
Click to collapse
I looked at the iFixit pictures but they don't point out which cable is for the display. Can you advise which cable I should be cleaning?
thanks!