Whenever I leave the house, I unplug my Note to take it along but every time, before I stick it in my shirt pocket I have to turn it off first. That's because it on by itself just because I removed the charging cable. At first I thought this would just be a minor annoyance, but by the time I've needlessly turned off the thing a few hundred times the damn thing really starts to annoy me. And it's even worse when I try to charge it in my car because every time I turn the key one way or another I have to turn the phone off yet again. It's a bit more difficult because I have one of those silicon rubber protector things so it takes a little longer to find the off button. But I like the protection that this cover provides. I suppose I could just wait for the timeout (which I like at 5 minutes), but that would waste some battery power that I may need later. Plus it just annoys me if it is on when I'm not using it. (Actually it is the same problem when I plug it in to the charger as well!). So who decided on this ridiculous behavior? If it is an Android thing - shame on Google. If it is a Samsung thing - shame on them. (If so I might even switch phones ... although I haven't heard of another phone that can compete with the Note). Or is it just a quirk of my ROM? (I only used GB for an hour or so, and didn't have time to observe this behavior or not - then I flashed PA which I have been using ever since.) I love this ROM although I would switch in an instant if I could get rid of my only real annoyance with this phone.
~Paul
pmennen said:
Whenever I leave the house, I unplug my Note to take it along but every time, before I stick it in my shirt pocket I have to turn it off first. That's because it on by itself just because I removed the charging cable. At first I thought this would just be a minor annoyance, but by the time I've needlessly turned off the thing a few hundred times the damn thing really starts to annoy me. And it's even worse when I try to charge it in my car because every time I turn the key one way or another I have to turn the phone off yet again. It's a bit more difficult because I have one of those silicon rubber protector things so it takes a little longer to find the off button. But I like the protection that this cover provides. I suppose I could just wait for the timeout (which I like at 5 minutes), but that would waste some battery power that I may need later. Plus it just annoys me if it is on when I'm not using it. (Actually it is the same problem when I plug it in to the charger as well!). So who decided on this ridiculous behavior? If it is an Android thing - shame on Google. If it is a Samsung thing - shame on them. (If so I might even switch phones ... although I haven't heard of another phone that can compete with the Note). Or is it just a quirk of my ROM? (I only used GB for an hour or so, and didn't have time to observe this behavior or not - then I flashed PA which I have been using ever since.) I love this ROM although I would switch in an instant if I could get rid of my only real annoyance with this phone.
~Paul
Click to expand...
Click to collapse
First the silicon protector that you put in your phone because it cover also the power when put it in your pocket it keeps triggering it, its like a hair trigger.
Of course when you plug the charger it will trigger the screen to on.
Why dont you just adjust the screen time out to one minute.
I dont have this problem but anyway, a quick fix would be to use Tasker which lets you easily automate everything in your phone
jonpaslim said:
Why dont you just adjust the screen time out to one minute.
Click to expand...
Click to collapse
That would result in about as many needless and annoying presses of the power button as it turned off when I didn't want it to.
hotelier1984 said:
I dont have this problem but anyway, a quick fix would be to use Tasker which lets you easily automate everything in your phone
Click to expand...
Click to collapse
That would be great if Tasker could turn it off again for me when it was turned on automatically. I took a quick look at the hardware events that tasker can act on such as:
Display: Off/On/Unlocked
File: File Closed/Deleted/Modified/Moved/Opened/Attributes Changed
Hardware: Camera Button, Search Button Long-Press, Card Mounted/Removed/Unmounted
Misc: Gesture, Shake
Phone: Missed Call, Phone Idle/Offhook/Ringing, Received Text, SMS Send Success/Failure
Power: Battery Changed/Full/Low/Overheating
System: Device Boot, Device Shutdown, Device Storage Low, Locale Changed, New/Removed/Updated Package, Wallpaper Changed
However being plugged in or out is not in this list. So how can it be done?
~Paul
I'd like to know too.
I can understand "screen on when charging cable plugged in". But its annoying as hell to have the screen on when charging cable is removed. Since 95% of the time it's going right into my pocket.
press the power button and screen will go of...
baz77 said:
press the power button and screen will go of...
Click to expand...
Click to collapse
Sad to see such an ignorant reply. Or perhaps he just has a dry sense of humor. Hard to tell which.
~Paul
Deleted
let's understand this better:
Your phone is off and turns on upon disconnected from the charger, or it is already on, but you don't want the screen to lighten up when you disconnect?
If it's the first case, that's weird...mine never auto initiates...If the second case, really don't know what you could do.
If it's the first scenario, maybe a factory reset? But beware of the brick bug and flash a safe kernel first.
Enviado de meu GT-N7000 usando o Tapatalk 2
pmennen said:
Whenever I leave the house, I unplug my Note to take it along but every time, before I stick it in my shirt pocket I have to turn it off first. That's because it on by itself just because I removed the charging cable. At first I thought this would just be a minor annoyance, but by the time I've needlessly turned off the thing a few hundred times the damn thing really starts to annoy me. And it's even worse when I try to charge it in my car because every time I turn the key one way or another I have to turn the phone off yet again. It's a bit more difficult because I have one of those silicon rubber protector things so it takes a little longer to find the off button. But I like the protection that this cover provides. I suppose I could just wait for the timeout (which I like at 5 minutes), but that would waste some battery power that I may need later. Plus it just annoys me if it is on when I'm not using it. (Actually it is the same problem when I plug it in to the charger as well!). So who decided on this ridiculous behavior? If it is an Android thing - shame on Google. If it is a Samsung thing - shame on them. (If so I might even switch phones ... although I haven't heard of another phone that can compete with the Note). Or is it just a quirk of my ROM? (I only used GB for an hour or so, and didn't have time to observe this behavior or not - then I flashed PA which I have been using ever since.) I love this ROM although I would switch in an instant if I could get rid of my only real annoyance with this phone.
~Paul
Click to expand...
Click to collapse
Hey there Paul,
Man, that is one hell of an issue you have.
Anyway, I don't have much to advice you as I'm not using PA rom on my Note(for the moment ), but hey.. you said it for yourself that you were not able to test it thoroughly your Note before in GB right? only about an hour before flashing to PA?..hmm... logical advice I guess on my end would be to try to flash it back to GB again and observe it for 1 complete day to see if the same issue still occurs.
By the way.. you have a very sensitive Note there bud.
Again, going back to GB is the only way(if you we're to ask me), to confirm if the 'sensitivity' is still there or not anymore.
P.S. I might suggest to you to take out that screen rubber protector in the meantime also. Just use it 'naked' for a day on stock GB.
See how it goes after.
Cheers!
mtdelnero said:
let's understand this better:
Your phone is off and turns on upon disconnected from the charger, or it is already on, but you don't want the screen to lighten up when you disconnect?
If it's the first case, that's weird...mine never auto initiates...
Enviado de meu GT-N7000 usando o Tapatalk 2
Click to expand...
Click to collapse
It's the 1st case. My phone is off and charging. I remove the charging cord and the screen just turns on despite the fact that I have not hit the power button - or any button for that matter.
I think it is more weird that you don't have this problem than the fact that I do. I've googled this and found many people complaining about it, but no explanations anywhere why it works this crazy way or how to fix it. And "Noodled24" who responded to my post above is yet one more person who is annoyed by this problem. I suspect there are thousands more (maybe even millions?), most of whom don't vocalize their annoyance.
BTW I'm being pretty glib with my use of the word "off". I'm really just referring to "screen off" - i.e. what happens when you briefly press the power button. I'm aware that this is not really off in the more conventional sense. If I power down using the power button long press, then no ... I don't have any problem with it turning on all by itself. So if this is part of the confusion, sorry about that. In fact, like most phone users, I almost never do a reboot (true power off) unless something goes wrong with the phone.
And recently I've found some people complaining about this problem regarding other Android devices, so I no longer think that this is a problem just with the Note, or just with the particular rom that I am using. Although I still don't know how wide spread the problem is.
letters_to_cleo said:
By the way.. you have a very sensitive Note there bud.
Again, going back to GB is the only way(if you we're to ask me), to confirm if the 'sensitivity' is still there or not anymore.
Click to expand...
Click to collapse
I don't think my Note is "sensitive". I've very carefully removed the power cord many times (even without the rubber cover) to be sure that I am not touching the screen or any button whatsoever. And BTW the problem does not happen 90% or 99% or even 99.9% of the time. No - as far as I can tell the problem occurs 100% of the time!. So I wouldn't call my device "sensitive". I would just say that it has been improperly programmed to work in this bizarre fashion. Usually such programming mistakes can be fixed, which of course is why I have posted to this forum.
I don't think going back to GB will solve the problem. I think the same problem happened, although I can't be sure since as I mentioned before I didn't use GB for long before flashing to ICS (PA). However even if it did solve the problem, IMO going that far backwards wouldn't be a very attractive solution.
~Paul
So you don't have to go back to GB......screen turns on when unplugging my stock rooted GB. I think that is the normal behavior.
I agree, unplugging shouldn't turn on the screen, but Google does lots of things that don't make sense in real life usage.
kraz
Sent from my Beautiful, White GT-N7000 using xda premium
Related
Ok here is the Problem,
several times throughout the day i go to pull my phone out of its nice little holster and i hit the power button to wake it up and it was off.
very frustrating because it has to boot up and then i have like 5 emails 9 texts and the phone begins to ring telling me they have been trying to get ahold of me for the last 20 minutes or so. ooops soory run on.
here is what i have on my tilt
winterface
throttle launcher 9.5
s2u
s2v
live search
sirius wm5
google maps
Ygo!
PSNES
Diamond TV
core player
icontact
blah blah blah....
etc... the usuals.
i have uninstalled winterface and TL and tried it that way still no luck.
the holster that i use is this one.
http://www.daydeal.com/product.php?productid=13622&cat=2955
(it has a pouch for my blutooth and spare batt...)
Edit: i seem o recall someone saying not use a holster with a magnet or something? any truth to phone interferance from a magnet.?
Answer: (for when its figured out)
Please gurus throw me some ideas, and dont just say mean stuff just because i didnt search the forum first cuz i did. also people who are mean on the internet are usually punks or nerds in real life. I happen to be mean in real life and a nerd on the internet. lol...
Whew. thats a lot
Carefully clean the contacts on your battery and on the device...
mrphatpat said:
Edit: i seem o recall someone saying not use a holster with a magnet or something? any truth to phone interferance from a magnet.?
Answer: (for when its figured out)
Pl...
Whew. thats a lot
Click to expand...
Click to collapse
As to the case with magnet, i use one that has two in it, with no issues,
What are your power management settings ? incase you do not know, go to settings>power> then at the bottom advanced tab, un-check the turn off device box .
F2504x4 said:
What are your power management settings ? incase you do not know, go to settings>power> then at the bottom advanced tab, un-check the turn off device box .
Click to expand...
Click to collapse
Well in this case power off means to put the device to standby -- this is normally what you want to keep your battery from draining too fast.
It sounds like in his case the phone is actually turning off, since it has to boot.
hence my advice to check the contacts
burtcom said:
Well in this case power off means to put the device to standby -- this is normally what you want to keep your battery from draining too fast.
It sounds like in his case the phone is actually turning off, since it has to boot.
hence my advice to check the contacts
Click to expand...
Click to collapse
I agree, it's a good idea to clean the contacts carefully with a cotton bud and contact cleaner or IPA (applied to the cotton bud). Any grease (such as from fingerprints) will likely not be seen on the contacts, but it's effects will be felt in this way along with possible erratic indications of low battery charge state or charging probs. If that doesn't make a diff, the next thing to check would be to remove the blah blah blah package, that software company always makes unreliable programs
But seriously, the o/p is unlikely to find someone with the exact same combination experiencing the same problem so I think the easiest way to track down the culprit is to do a hard reset and then progressive reinstall, testing for a day or two after installing each package until you find which package, when installed, brings on the problem.
thank you for your answers folks.
here is what i have done, cleaned the battery contacts.
using a different case.(not sure if it matters but no magnets)
and removed Winterface...
so far there have not been any issues with the Phone's power being off.
(yeah i knew it after i wrote it the whole standby/off thing thanks)
so far no issues for 12 hours or so.
@F2504x4
How long have you used the magnet case, and do you use it everyday?
just curious...?
mrphatpat said:
thank you for your answers folks.
here is what i have done, cleaned the battery contacts.
using a different case.(not sure if it matters but no magnets)
and removed Winterface...
so far there have not been any issues with the Phone's power being off.
(yeah i knew it after i wrote it the whole standby/off thing thanks)
so far no issues for 12 hours or so.
@F2504x4
How long have you used the magnet case, and do you use it everyday?
just curious...?
Click to expand...
Click to collapse
first Glad to hear that you hopefully resolved the issue, but it will be hard to say just what fixed it, I drive racing karts, and one thing I learned is to only make one change at a time in order to figure out if it was helpful or not..something to think about..
As to the case, been using it for over a year just about 24/7 with both a 8525 and the Tilt, before I had a Pearl with a magnet , no issues , cool thing about the Pearl was that the magnet would cause the Pearl to go into sleep mode when holstered it, by design and would wake up as soon as you pulled it from the pouch .
so i do no think the case was the issue.
BTw the magnets are very strong and the flap will not open very easily.
Hey guys i just bought a nook color and had it shipped to my country but i think i am already regretting it now.
The touch screen starts behaving very weird randomly at any times, it automatically registers touches and keyboard automatically typing own it own, and what ever i touch just goes straight to hell and this continues as long a i don't lock and unlock it again.
Even when i am reading it automatically starts zooming.
I was think about rooting it and installing a custom Rom, will that fix the problem? because giving it back to B&N is not an option for me.
Also i don't have screen guard, and the screen is always smudged with fingerprints, can that trigger this sort of behavior?
I'm using mine in Australia and have a similar problem but only when using the supplied USB cable to charge it.
I've heard stories about faulty USB cables which might be the case as I don't have this problem when I use the cable for my desire. The problem with this is that the cable isn't long enough for practical use and the supplied cable apparently has extra pins which would explain why it still discharges (although slower) when using my desire micro USB cable.
For now I'm limited to only using my nook without the cable plugged in but I'm thinking about finding another cable as sending it back to B&N and then paying to ship it back here isn't really a viable option.
Let me know if you figure something out though.
Well the one with usb cable is a known issue and u can still use it otherwise, mine just happens randomly at any time, its almost unusable.
Does installing a custom rom help?
It wouldn't hurt to try. I know some kernals make changes to the touchscreen sensitivity but I don't know whether that would apply to your problem or not. A nook is very easy to un-root anyways so as far as I know (and don't quote me on this), you should be able to return it if you absolutely have to.
Don't give up though. I'm loving mine and for the price it's an awesome little accessory when it works.
Hi,
Make sure to clean the touch screen - last night I had a different looking
smudge on my screen that was causing huge problems - as soon as I cleaned
it off, back to normal. Are you in a humid location? Condensation will cause
problems too.
Also you may want to search for 'calibrate' in the forums, there is a way to
recalibrate the touchscreen sensitivity, I believe that this is mostly for
low sensitivity at the corners though.
Here are two links I found:
http://forum.xda-developers.com/showthread.php?t=943358&highlight=calibrate
http://forum.xda-developers.com/showthread.php?t=934500
Good luck!
Peter
My touch screen acts up as well. I turn the screen off for a couple minutes to "reset" it. It will work OK for a little, then it goes back to wonky.
Hey guys i finally found a solution to this problem, well my touch screen is behaving normally when its not not connected to the power cable. I hope thats a solution good enough for you.
Just go to
h**p://nookdevs.com/Recalibrate_the_NookColor_touch_screen
I tried all the custom roms but that didn't help very much, so i tried this on CM7
and so far my screen is giving totally normal tests results when not plugged in and lets hope that it stays that way.
My daughter had a similar wonky-screen problem when she plugged in a particular set of portable music player speakers. Not another pair she has, just that one.
And I was able to replicate it on my nook. It wasn't specific to her nook.
okay, it seems that my excitement didn't last that long but
After a lot of testing, it turned out that the only problems was my oily or moist fingers.
so i got a screen guard and tested it for more than two hours and i haven't had any problems yet. So even if i do see that happening again, once in two hours is not that bad.
rigy73 said:
okay, it seems that my excitement didn't last that long but
After a lot of testing, it turned out that the only problems was my oily or moist fingers.
so i got a screen guard and tested it for more than two hours and i haven't had any problems yet. So even if i do see that happening again, once in two hours is not that bad.
Click to expand...
Click to collapse
I think I'll try this cause I have oily fingers as well and I'm getting the wonky screen issue while NOT plugged in as well.
rigy73 said:
Hey guys i finally found a solution to this problem, well my touch screen is behaving normally when its not not connected to the power cable. I hope thats a solution good enough for you.
Just go to
h**p://nookdevs.com/Recalibrate_the_NookColor_touch_screen
I tried all the custom roms but that didn't help very much, so i tried this on CM7
and so far my screen is giving totally normal tests results when not plugged in and lets hope that it stays that way.
Click to expand...
Click to collapse
I'd add my vote to this link...worked for me:
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
Assumes you have ADB working via USB or wireless
My milestone has led a pampered and then rough life of music gigs and festivals back and forth and decided to give up it's ghost (or give me ghost-touches if you will) due to a failing digitizer after a Dillinger Escape Plan gig (http://www.youtube.com/watch?v=AyzQgysUOdU I'm right in the center of the mosh pit hehe).
I've since decided that I'd save a little more money and get a Galaxy Nexus, even if I'd very much prefer a Droid4 if only to have a proper QWERTY slider phone. They don't sell them here .
Anyway, being that I've had to continue using my POS (can you tell I'm pissed) phone, I decided to look for a way to disable the touch screen and see how feasible it is to control with only the keypad and a few touches.
Which led me to these 2 apps
https://play.google.com/store/apps/details?id=com.argotronic.touchblocker
Screen Lock / disable touch Argotronic
I've had it set up so that I can "lock" the touchscreen via shaking the device, and unlocking the screen in the same way. Despite disabling the touchscreen, the notification pulldown still remains active, so you can still pull it down and quickly tap yourself to whatever via the Dpad if necessary.
Now, of course, what use is all this if you can't swipe to unlock your ****?
https://play.google.com/store/apps/details?id=com.jiubang.goscreenlock
Go Locker
This, apart from still bringing up the stock lockscreen whenever you restart your phone (this goes away after 1-2 unlocks), solves that problem by allowing you to unlock your phone via long pressing the volume rocker.
I've found that it is entirely feasible to run the phone this way.
Apart from that, I bid this community a farewell as what little regular posting I used to do has already dropped tremendously the last few weeks, and much thanks to everyone who has helped me and the developers. <3 Kabaldan, get a galaxy nexus please! though I'd suppose your talents would be better suited to another poor locked up phone.
This community helped me get quickly familiar with Android, and in particular with a "difficult" phone, and I will never forget this. I'll probably get a new digitizer + keyboard and just put it on my desk as a... completely over powered clock. or something. Hey, when was the last time you said overpowered when talking about the Milestone?
Oh, and to solve the gig/festival problem so my Gnex doesn't meet a similar fate I'll be getting an Xperia Active as a secondary phone since that **** is hard as nails, waterproof, small (3") and reasonably priced.
EDIT: Reason I'm not just fixing up my Milestone to continue to use it is because I've always suspected that my mobile radio is a little faulty as I've always had trouble maintaining 3G+ connectivity/sync, I figure it'll just crap itself out eventually. It's also, and I'm sure most will agree, starting to become painfully slow hahah.
If you are willing to take a little risk, after taking out battery, SIM card and microSD card, worm up your phone by putting it in the oven over a towel or on a blow heater (yeah, for real) for a few minutes. Then, you will need to put it in a dry place (like drawer or something) during the night. Turn it up in the morning and it shall work.. it worked for me anyway, I was sure my phone was dead and the digitizer was damn busted.. it must have been moist from the inside, so I used to have very annoying ghost screen..
good luck mate..
oshosh said:
If you are willing to take a little risk, after taking out battery, SIM card and microSD card, worm up your phone by putting it in the oven over a towel or on a blow heater (yeah, for real) for a few minutes. Then, you will need to put it in a dry place (like drawer or something) during the night. Turn it up in the morning and it shall work.. it worked for me anyway, I was sure my phone was dead and the digitizer was damn busted.. it must have been moist from the inside, so I used to have very annoying ghost screen..
good luck mate..
Click to expand...
Click to collapse
Hmm, I completely forgot about this!
I had done some drying with a hairdryer, I had originally noticed that the ghost-touches would get more severe if it spent an hour or two in my pocket, but completely forgot about trying it to dry it a different way. I'll put in a bag of rice tonight!
Thanks
Putting your device in the oven could really fix your problem. I've heard of this before in a different context (fixing gaming consoles..). What it does is fixing soldering points by melting them. Connections between cables and the board are then (hopefully) fixed again.
There are several methods including the oven, microwave, hairdryer and so on..
moe6 thank you for you post
will try the screen lock app
i have no need for the go locker, with cm7 you can unlock the phone by sliding the keyboard.
i have two questions
how can i answer/end a call easily without the screen?
is there any way to have a back button routed to the key board?
i use "search+z" to start(swich) back to my launcher
i guess i will try the oven trick but i really concerned if i will break the milestone completely. should survive a few week.
that poor old thing
UnitedOceanic said:
moe6 thank you for you post
will try the screen lock app
i have no need for the go locker, with cm7 you can unlock the phone by sliding the keyboard.
i have two questions
how can i answer/end a call easily without the screen?
is there any way to have a back button routed to the key board?
i use "search+z" to start(swich) back to my launcher
i guess i will try the oven trick but i really concerned if i will break the milestone completely. should survive a few week.
that poor old thing
Click to expand...
Click to collapse
Good thing you thanked the top post, I would've missed your post otherwise .
Yeah I know you can unlock via keyboard slide but I have my phone caseless and its always in my pocket and it tends to slide open just enough to unlock it occasionally .
I answered calls by using the d-pad on the keyboard. Just tap it once and it should begin highlighting buttons on the screen, press d-pad center button to select. Unfortunately for you, my back button did still work as the "dead" part of my digitizer was on the right side of the phone where Home and Search is.
I think the drying tricks help mostly with ghost touches since I'd assume that the ghost touches are from small amounts of water/sweat/liquid. After drying it with a hairdryer, short bit in the oven and then stuck in a bag of rice, my ghost touches stopped 80% from what they were before. The digitizer is still dead on one side though.
Now all I need is a Droid/Milestone dock and a new digitizer so my old Milestone can live its life out as a very complicated desk clock
You can actually make it work real good without much issue. You'll need a CM ROM so you can enable the Menu to unlock option and then use v6 Supercharger Bulletproof Apps to lock the screen disabling software into memory so it doesn't crash and it doesn't run bad at all. Also, there is a really good app to remote control your phone from your computer so if you have adb and a data cable, you can get it working good.
Do you know what that app is called?
Sent from my Galaxy Nexus using Tapatalk
Chris.fowler said:
Do you know what that app is called?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I personally use AirDroid, it's amazing.
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Sjaakbanaan said:
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Click to expand...
Click to collapse
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
myfishbear said:
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
Click to expand...
Click to collapse
Thank you, let me try that. Couldn't find the right alcohol pct. so I'd have to use some generic screen cleaning liquid, would that be okay as well?
My screen was having issues too. So I turned the dot thing on from the dev part as well. The dot seems to freeze as I'm opening my keyboard. And the dot stays frozen in place until I close the scree again. Any ideas on how to fix it? Also if the screen is open and I touch a spot nothing happens, but then when I close the screen it will sense correctly where I touched while it was open.
Sounds like the same problem, so I'm getting the feeling it might be due to the connectors rather than the screen digitizer itself. After cleaning it, I didn't have any issues for a while, but they started occurring again now.
The replacement part is not available right now, a bit expensive, and excludes the price for the required tools which I don't have yet. Warranty may be tricky as I didn't get my phone from Verizon directly. So if it turns out to be a connector issue I will say goodbye to the Droid family and just get another non-QWERTY phone.. at least until Motorola starts selling them (as 'Milestone' since 'Droid' is a Verizon brand) in Europe again. The Droid 4 is the best phone I ever had, this is potentially making it unusable for me though. Glad I didn't order a Lapdock yet!
Motorola will repair your phone for 168... out of warranty and all... I found this cheaper and easier then fixing it myself and guaranteed done right in 5-7 days..
Sent from my DROID4 using xda app-developers app
Mine is still within the one year warranty. So I want to send it in. But I'm afraid they will check for the root stuff and they will consider voiding my warranty because I was rooted. I unrooted and did a factory reset to see if it would fix the issue. So this is my only chance left. I heard clearing the data wouldn't remove the qe process they use to know that I'm rooted. So I'm not sure if its worth the chance.
Flash SBF restores everything to my knowledge. No way to see what happened before the SBF flash.
I read in the original post for the DROID 4 ICS root tool that a sbf will not remove the part that says you were rooted at one point. I checked that first. An sbf flash is really easy. I was really hoping that it would work.
they dont take the time to check that stuff... if you sbf they wont know a thing...
bty found what u need on the cheap
Motorola DROID 4 XT894 Flex Cable Ribbon 27$
http://www.ebay.com/itm/Motorola-DROID-4-XT894-Flex-Cable-Ribbon-/150849219594
If they don't check it then why should I even bother? Does an sbf change something a factory reset doesn't? I've already reset it. I'll look into the fix though. It will depend on if I have the tools to do it or not.
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
The Old One said:
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
Click to expand...
Click to collapse
Cant be... it is glued in place and has connectors... how else could he sell you the cable by itself... http://www.ifixit.com/Teardown/Motorola-Droid-4-Teardown/7759/1
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
podspi said:
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
Click to expand...
Click to collapse
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Yes
Sent from my DROID4 using xda premium
myfishbear said:
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Click to expand...
Click to collapse
I agree it's probably not anything most people need to worry about... I still plan on sending my D4 in before the warranty is up, I've been having terrible wifi + 4G drops, even on stock (that's why I fastbooted in the first place)
I am a bit nervous though, because I've heard horror stories about Moto replacements. That being said, if Ops phone is under warranty, I'd send it in rather than trying to repair it. If it isn't under warranty, then I'd go for the flex cable, the Moto phones are built well and reasonably easy to work on.
Sent from my Galaxy Nexus using xda app-developers app
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Sjaakbanaan said:
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Click to expand...
Click to collapse
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
myfishbear said:
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
Click to expand...
Click to collapse
I still have tons of guitar picks so I just ordered a Torx set for this and future problems.. hope that pushing the connector around a bit can solve it already.
So I'm one of the people that's been having major issues with the red light/ no boot issue.
I think the issue (for me at least) is a hardware flaw. Upon completing the steps to reboot the phone (take case apart, disconnect battery, connect power, wait for battery charge indication, reconnect battery) I can get the phone to boot and function just fine.
I have discovered that upon screwing the battery connection back into the phone, it applies a bit too much pressure on the connection which sends the phone back into the redlite "no boot" mode.
TL;DR, If the battery is connected to the phone too "tightly" with the screws, the issue is caused.
Hardware flaw? I think so.
My Fix? Took out the connecting screws, the connection seems to hold without them and there is no more pressure on the connection without the added thickness of the screws (when putting the back of the case on)
EDIT: Here's a video of what I'm talking about, for those of you who haven't had to deal with this (yet?)
Video of Issue
Hey Google/LG, if you're reading this, Send me a new phone, please!! This is unacceptable!
Good find. Maybe you could try packing the back in places so that no pressure is put on the battery
Michealtbh said:
Good find. Maybe you could try packing the back in places so that no pressure is put on the battery
Click to expand...
Click to collapse
Good Idea, will try it if I encounter this problem again. Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case).
bump--I think people should really see this.
Nice find dude!
I always thought it was a software issue but turns out it is not!
It's still strange that most people have encountered the issue when benchmarking.
Sent from my Nexus 4 using Tapatalk 2
alwaysbboy said:
It's still strange that most people have encountered the issue when benchmarking.
Click to expand...
Click to collapse
Perhaps it's just a coincidence. I'll still stay away from benchmarking, though.
alwaysbboy said:
I always thought it was a software issue but turns out it is not!
It's still strange that most people have encountered the issue when benchmarking.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If the finding is true then here my theory on why it happens mostly during benchmarks.When you run benchmarks, your phone and battery heats up a lot. This can cause the connectors to expand causing screws to get tightened.
i can confirmed this find is true, altough its kinda late for me to read this thread.
here is my version.
im a proud owner of nexus 4. got my phone from the 1st batch order, and the original bumper also :angel:
this morning while watching my kid at school, got nothing to do but overclocking my nexus 4 with morfic's latest beta kernel.
silly i put the min and max at 1.8++ghz and run an antutu test on it. and in another 5 seconds the N4 turned off and practically dead. all buttons combo were negatives. as soon as i arrived home i plugged in the official charger. it just blinking red. few moments after i plugged in the N4 to my laptop. blinking red and driver installed notification showed up. then the red light gone. like forever... no red when i put it on charger nor when connected to the laptop.
ok its a dead meat. im in JAKARTA n got my n4 from the US. none of any LG service centre in my country could help me with it. and the RMA things just too far from me.
so since i left with zero to none option, i was wondering "what if i take off the battery?"
i remember read an article from ifixit about how to teardown the nexus 4 then i found the link.
here it is:
http://www.ifixit.com/Teardown/Nexus+4+Teardown/11781/1
what i did was:
1. follow steps number 6 [pictures #1 & #2]
2. number 7 [pictures #1 & #2]
3 and number 9. [pictures #1 & #2. no need do the pictures #3]
4. see the white wire with blue sticky tape right next to the battery? i dont know what is that but i unplugged the golden head off also.
i left it that way for 10 minutes before i put it back all together again [ including the screw battery port holder. just dont screwed them too tight. give a small effort to none power ]
all done and i pressed the power button. its ON like nothing happened before.
when im about to share my fixed in the other thread, i got someone direct me to this thread. so here i am confirming this fixed is legit
Wow!! This fixed my nexus that didn't even have an LED light. You are a life saver!
It's been dead for a week and I was just waiting on warranty. But now it's up and running like a bawse!
Hi
ethugp3pp3r said:
So I'm one of the people that's been having major issues with the red light/ no boot issue.
I think the issue (for me at least) is a hardware flaw. Upon completing the steps to reboot the phone (take case apart, disconnect battery, connect power, wait for battery charge indication, reconnect battery) I can get the phone to boot and function just fine.
I have discovered that upon screwing the battery connection back into the phone, it applies a bit too much pressure on the connection which sends the phone back into the redlite "no boot" mode.
TL;DR, If the battery is connected to the phone too "tightly" with the screws, the issue is caused.
Hardware flaw? I think so.
My Fix? Took out the connecting screws, the connection seems to hold without them and there is no more pressure on the connection without the added thickness of the screws (when putting the back of the case on)
EDIT: Here's a video of what I'm talking about, for those of you who haven't had to deal with this (yet?)
Video of Issue
Hey Google/LG, if you're reading this, Send me a new phone, please!! This is unacceptable!
Click to expand...
Click to collapse
This is simply a fault with your phone. Most likely a chip or component isn't soldered correctly or you have a dry joint. When the board is flexed by some force it is breaking or making the connection.
The time will come when even this "fix" for you stops working.
The reason the phone is sometimes failing during stress tests and not coming back on is a safety device. The lithium battery is reporting it is under stress or too hot and the phone shuts down to avoid an explosion. Because there is a big chance the battery is permanently damaged and so potentially dangerous the phone remains in a safety condition wanting to be returned to the manufacturer for testing. Lithium batteries if damaged can explode, imagine if a phone explodes next to your face while you are talking on it? The manufacturers, not wanting a law suit that disfiguring someone might bring, deliberately er on the side of caution.
It's a bit like the limp home mode some cars have when they detect some parameter outside of the norm. You might be able to reset that back to normal by some hack found on the internet but it hasn't fixed the underlying cause.
Regards
Phil
This thread should be stickied as this is a common problem with the Nexus 4.
Just wrote this to bump the thread back to first page so more people can see
Sticky This!
This needs to be stickied!
I'm having a similar issue with my completely stock nexus 4. I can only turn the phone on when it is connected to charger, but this is also very rare. If I manage to turn it on, it shows I have -22% battery left and this doesnt change. I can enter bootloader when charger is connected. I have left it charging overnight, but still it doesn't boot without the charger connected.
Any idea if the fix described here can help me? Can LG service somehow see that the phone has been opened?
I live in unsupported country, so I can't send the phone back to Google. My only hope is this fix here or my local LG service, but I'm not sure if my local LG can even help me, because the phone is not sold here.
Ahhh good thoughts. I've got a replacement battery on the way for that reason... Hopefully it's a problem there.
Sent from my Nexus 4 using xda app-developers app
Nexus 4, 8Gb, in UK
It arrived Sat (2 days ago) @ 80% charge & about 5 mins after unpacking I noticed it was the 8Gb & not the 16Gb I had ordered
Phoned google for RMA - currently awaiting replacement.
Repacked it, took it to work, had a play, installed maybe 3 apps, browsed a lot though - reboxed it afterward. as I had no case & as I didn't want to risk the RMA I decided not to take it next day.
Case arrives from amazon & I'm back to work today, so I decided to risk it - nexus battery almost dead & powered off.
Connected charger - nexus indicates charging on screen when power button is pushed.
As I lift the phone to power it on 20mins later, charging display blanks & red light starts blinking - swap cable, charger & check connections - all ok - nothing but a red light on a dead phone.
*panic*
read internet: wasted half an hour on button combos streetfighter would be proud of
Found this post here:
http://forum.xda-developers.com/showpost.php?p=37461951&postcount=3
"Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case)."
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Am glad I'm sending this unit back, if replacement does this within 30 days then I will give up on LG & wait for next gphone; between this and the glass cracking issues I read of, this may not be the best nexus ever quality wise.
tl;dr Almost virgin Nexus got red light & unresponsive on first charge. After all else failing, firmly pressing the back, directly above the battery connection area immediately revived it...
kwft said:
Nexus 4, 8Gb, in UK
It arrived Sat (2 days ago) @ 80% charge & about 5 mins after unpacking I noticed it was the 8Gb & not the 16Gb I had ordered
Phoned google for RMA - currently awaiting replacement.
Repacked it, took it to work, had a play, installed maybe 3 apps, browsed a lot though - reboxed it afterward. as I had no case & as I didn't want to risk the RMA I decided not to take it next day.
Case arrives from amazon & I'm back to work today, so I decided to risk it - nexus battery almost dead & powered off.
Connected charger - nexus indicates charging on screen when power button is pushed.
As I lift the phone to power it on 20mins later, charging display blanks & red light starts blinking - swap cable, charger & check connections - all ok - nothing but a red light on a dead phone.
*panic*
read internet: wasted half an hour on button combos streetfighter would be proud of
Found this post here:
http://forum.xda-developers.com/showpost.php?p=37461951&postcount=3
"Seems to hold up, though, even when pressing on the back of the case where the connection is made (down and to the left about 0.5cm from the "n" on the back of the case)."
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Am glad I'm sending this unit back, if replacement does this within 30 days then I will give up on LG & wait for next gphone; between this and the glass cracking issues I read of, this may not be the best nexus ever quality wise.
tl;dr Almost virgin Nexus got red light & unresponsive on first charge. After all else failing, firmly pressing the back, directly above the battery connection area immediately revived it...
Click to expand...
Click to collapse
So you didn't even take it apart to revive it? Interesting... I haven't had this issue myself in the 2 and a half months with this phone, but nice to know what to do if it arises.
It sounds like it could be dodgy solder joints, although I'm tempted to say that I'm currently ****ting myself. Things like glass cracking doesn't worry me, people are clumsy and that usually will cause that. However, we have no control over the quality of the circuitry inside.
The thing is, the poster above says wait for the next GPhone, it's been announced for next year. So you're going to be waiting a hell of a long time. This phone I hope will suffice while you do so however.
kwft said:
After pressing down around there, the red light clears instantly, small vibration & nexus is now charging again.
Click to expand...
Click to collapse
Nice to see that helps. I need a fix that allows me to "pull" on it and then push it again