Possible MAJOR discovery regarding battery/red lite issue. - Nexus 4 General

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

Related

Dead

Hello,
Yesterday my Diamond had died I think
It was frozen and I did a soft reset, screen stays black and nothing happend anymore.
Pulled out the battery, put it back in, and try to turn it back on. It vibrates after a few seconds but the screen stays black.
every help would be great!
Greetings!
Michiel
It might be low on battery so have you tried recharging it?
when i connect it to the power cable nothing happens, the enter button isn't lighting up.
when i connect it to my pc I can browse to the internal storage normally, but it won't charge the battery.
now I'm really confused...
Take out your battery and sim card and leave it out for about 20 minutes and then put it back. During this time, also have your device plugged in (without the battery).
Reflash Everthing
I've pulled out the battery + sim for more than 30 minutes, reloaded the official HTC rom and still the screen is black.
It starts up, vibrates, makes the start sound but the screen remans black.
Now I want to put the orginal HTC SPL back on it, but it doesn't completes the procedure.
Anyone? thnx again!
I got exactly same problem
this has happened to me twice during the past year. the screen was black, although it did vibrate when I turned it on. both times it fixed by itself overnight, very strange.
what I saw is that both times it happened after a long ride with the car, I suspected that due to the prolonged exposure to air conditioning, when I took it out it condensed on the warm motherboard (it was used as a GPS) and some shortcircuit occured.
Unfortunately, 3 weeks ago, again after a long trip with the car, when I took it out it 'died' in 5 minutes (with 100% battery), did not even vibrate anymore when powered on, and never woke up eversince. It is now in service since the 15th of August, with a status on the website of the official HTC service company in Romania (Cirma Electronics) of: "waiting for spare parts" for 5 days...
My guess is that either the MB or the screen fried because of a design issue which caused the condensed vapors to form on some contacts inside...
It sounds as if the device is 100% operational with the exception that the LCD is out. Correct? Or, have you experienced other problems? Try powering up you Diam, then shine a flashlight directly at the screen. If you can see your interface then you have a dead backlight & need a new LCD. If you do not see the image then the LCD itself is defective {Apparently a common problem} & you'll need a new LCD. Either way you should contact HTC service as you have a 2 YR warranty.
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
If you have warranty return it to the store.
Humblehippie said:
@ cocomic: Where is Your Diam on these trips, A windscreen mount or a console mount? If it's a console mount, most likely you have an air vent blowing directly at it & that's just asking for moisture build up. But, if it was a "moisture" issue as you stated, then HTC would not be fixing it for free. They would see the oxidation from the moisture & say that it's your fault for getting it wet, & charge you out the ass for that part. {That's why ALL devices have LDIs} If you use a windscreen mount, then you have your device sitting in the sun for a long time! Sunlight KILLS LCDs!!! It may be more likely that you burned your screen by having it exposed for long periods. But it's probably just the issue that many people have. If you go to HTCforums you will see a lot of people have LCD issues.
Click to expand...
Click to collapse
I have a windscreen mount, the air vent doesn't blow directly on the device. furthermore, the sun couldn't have burnt the LCD as the last time it died (for good), it was 11 PM.
the phone is in service and has the online status on their website: "the phone is in the lab, waiting for spare part". this means that whatever the issue is, hopefully it's gonna be fixed under warranty.
nevertheless, I find it appalling that a device built in 2008 has huge design and construction faults causing it to malfunction whenever used in a car with the AC turned on...
I'll keep you posted on the outcome
later edit: update: I've just got off the phone with a secretary at the htc service. apparently the motherboard fried and they ordered a new one. from what she said only the case will remain the same, it may be that the lcd display was caught in the chain reaction . the bad thing is that I will probably have to wait for another week, the good thing is that I will get an almost new phone...
as they didn't say anything about the LDI, it's either that the condensed vapors didn't touch it, only the circuits, or the fault did not come from the humidity... one can only guess...
It may not have been condensation that caused the problem. It could be that your Mainboard had a problem that was amplified by your trips in the car. Either way, you get a factory refurbished Diamond, & that's jus' sweet. I have to call them this week about my Diam because my front cam isn't working. I never really use it, but if it's covered, I might as well make them flip the bill while I can.
no, really, do that... i remember that a few weeks before the 'incident' my rear camera stopped working, too... i never payed too much attention as i considered it to be just a spb mobile shell software issue which would have eventually gone away after a hard reset or something...
you are probably right, my MB was slowly dying, organs failing (i have just watched a house md rerun, sorry )... if you have the possibility to have it checked while it's still in warranty and have the camera fixed while at it, why not?
I'm moving this, as it has no pertinece to the original topic. This link; http://forum.xda-developers.com/showthread.php?p=4476473#post4476473 is a post I started to see if anyone else had these issues. Read the update on the first post

HOW TO: fix Droid/Milestone touchscreen lack of responsiveness and Ghost Touch issues

NOTE: THIS SOLUTION IS POTENTIALLY DAMAGING AND MAY NOT WORK FOR EVERYONE
PROBLEM: touch screen acts erratic, notification bar keeps opening, screen appears to be touched by someone else continuously (Ghost Touch), and parts of the screen DO NOT RESPOND TO TOUCH.
MY OWN SPECIFIC CASE: I had the Ghost Touch issue for 3 days suddenly without intro, which often used to go away after a reboot or two, then phone worked normally after I removed the battery and left it in a dry area (in a closed drawer between books, no air entering, very dry atmosphere), however the RIGHT SIDE of the screen (Search button, rightmost letters [L and Delete and sometimes ENTER] do not work. If the phone is in normal landscape, you cannot open the notification bar by dragging it normally.
DIAGNOSIS: for some people, the problem is more severe. The Digitiser itself could be malfunctioning and has to be fixed, while for others it could be a true problem with the screen itself. However, for MANY OF US, it is a problem of HUMIDITY. The humidity sensors are causing the phone to act like that. Some say part of this problem happens because the way the keypad affects the phone internally as you open and close it a lot.
SOLUTIONS:
1- To be safe: send the phone to the shop. Ask them to open the phone and apply an extra layer of insulation, in case the digitiser and the screen are okay.
2- If something is faulty, replace it at the shop.
3- MY OWN SOLUTION: based on something I read many times, the solution was to apply DRY HEAT for at least 45 mins. What I did, based on averaging out many experiences I read online, was to remove the SD Card and SIM, remove battery, I heated up a toaster oven for 10 minutes, waited until the temperature was at about 60-70 degrees Celsius, SHUT DOWN THE HEAT, put the phone on its screen on a plate, screen facing down and covered by a cloth to protect it from direct contact with metal, then all inside the oven. The oven is a relatively big one, so phone was AWAY FROM A SOURCE OF DIRECT HEAT. I closed the lid, then every while 15 minutes I would heat the oven for 40 seconds to maintain the temp. This is LIKE (ALTERNATIVE SOLUTION) leaving your phone in the glove compartment of your car while its parked in a sunny spot, to find it really hot in the morning and tough to touch for a while. TO CONTINUE, after the phone was out of the oven (I can't believe I am saying this), I left the phone overnight in a dry area for 8 hours (could need less time). Then, I put everything back in, plugged it, and THE PHONE IS WORKING PERFECTLY NOW!
NOTE that solution number 3 could affect your keyboard buttons if heat is too much. It may cause the glue holding the keys to melt a bit. Be delicate with your keyboard after you restore your phone.
Again, I only did this YESTERDAY. With the exception of some keypad stickiness, the phone is working perfectly now.
I hope this was useful
B.
EDIT: Today is the First of May, phone is still working without a glitch
N.B. Press the Thank you button if you wanna congratulate me on daring to toast my milestone in the name of scientific inquiry
SECOND EDIT: Phone did it again for 2 days. Applied the same method, and it worked again. I think partially it happened because I was in a very humid location.
That didn't work for me, I had no option but to replace the touchscreen/gorila glass.
I love the idea of toasting a milestone
Thought with all my aggression against Moto, I think I just might leave it in there
Luckily I dont have these problems so I wont get tempted
AirLancer said:
I love the idea of toasting a milestone
Thought with all my aggression against Moto, I think I just might leave it in there
Luckily I dont have these problems so I wont get tempted
Click to expand...
Click to collapse
I have to admit, I cared litte whether or not this actually worked. I just wanted to toast it But it did work, so
Pretty tempted to try this out, I think I will when I have free time.
My phone had the dead zone problem for 2 months now, but in some very rare cases, like when it's a very hot day, the screen will work normally for a minute or something. Then it goes back to dead part. I assume this would fix it?
Lesiroth said:
Pretty tempted to try this out, I think I will when I have free time.
My phone had the dead zone problem for 2 months now, but in some very rare cases, like when it's a very hot day, the screen will work normally for a minute or something. Then it goes back to dead part. I assume this would fix it?
Click to expand...
Click to collapse
If it DOES indeed work on hot days, then it means the phone is not entirely dead. But I would suggest you do something less drastic first, such as the Glove Compartment method. No responsibility though
If you're trying to remove moisture, you could also try putting it in a baggie of crystaline cat litter (NOT the clay kind!) - this stuff is sold at a MUCH higher price as a way to save a phone from water damage, but it's the exact same substance. Does a great job removing moisture. It's the same sort of silica gel that's in those packets in medicine/vitamins that says "Dessicant - do not eat".
Or you could just put it in a sealed bowl with raw rice for a couple of days... this is the best and cheapest way (and then you have the silicon "grains", the ones that you find in shoe boxes or computer parts boxes).
Sent from my Milestone using Tapatalk
CybeRNerO said:
Or you could just put it in a sealed bowl with raw rice for a couple of days... this is the best and cheapest way (and then you have the silicon "grains", the ones that you find in shoe boxes or computer parts boxes).
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
Pretty sure that rice doesn't do anything, I don't know how that started as a suggestion, but its not better than anything else; its not known to be absorbant, but the silicon is.
I've tried the method but the right segment of the digitizer still doesn't work.
My biggest issue with regards to "lack of responsiveness" are the 4 capacitive buttons. Pressing the Home key is always hit and miss. I know I hit it all the time because I can feel the vibration feedback but it only goes to homescreen 50% of the time.
Will also be testing this out as soon as I have the spare time. My screen started acting up after I accidentally put my milestone in a small beer spill at a party Hopefully this will work out for me too!
Abazel said:
I've tried the method but the right segment of the digitizer still doesn't work.
Click to expand...
Click to collapse
Luckily for me, I was still under warranty, heh. Cause I had insurance. This is my second Droid this has happened to. Hopefully my replacement won't do the same thing.
How many times did you reheat the oven? I tried just once and it didn't help. My phone has been having this problem since January.
decon89 said:
How many times did you reheat the oven? I tried just once and it didn't help. My phone has been having this problem since January.
Click to expand...
Click to collapse
I feel I am on a cooking show
Well, depends on your over. Mainly I was trying to maintain a temp varying between 50-60 c. Mostly 50, but sometimes 60 to up the ante a bit and make sure things stay warm. 30 minutes at least. However, I have to say that I did this twice in 6 weeks, and after that the phone just died again, and I found my warranty card and sent it there to be fixed, and they fixed it, but ruined something else.
If you have the warranty card, take your phone and send it to them Someone told me the method worked and the phone has been good for quite a while, but most of us seem to re-experience the issue after a while.
I've been having these issues for a few days now too, and I think I know why. I've been using this Milestone for 4 months now, and I never had this problem until a few days ago. What I noticed yesterday was that after some acting up, the phone started working properly again. So I ran Touch Test. And I noticed that if I pressed really hard on the top side of the phone(where the logo and the ear piece are located) it started acting up again. My first impression was that the glue holding down the gorilla glass was loose. So I left the phone as usual on my night stand and then I tried the same thing with the pressing on the same area. Guess what? It didn't happen again. Now there seems to be no problem. So I tried to remember what happened yesterday before the screen started acting up, and I remember talking to my wife for a while when I was in my car. Yesterday was a pretty hot day and I was a little sweaty when I talked to her. Now since only that specific part with the earpiece was causing this issue(I tried pressing equally hard on other areas without any problem my guess is that the insulation between the earpiece and the touchscreen has been breached. Maybe because of all the sweat that went in there in time. You know the salt and acids in the swear are known to melt things, and poor quality glue is among them.
How to fix this? I do not know yet, but I do have a good idea that I'd like to share. I want to buy a screen protector foil, and put just a little band around the ear piece. That would probably lower my in-call volume, but since the Milestone is very loud anyway I hope it the quality of the calls won't be too much affected. After that I'll use it in normal conditions again and see if the ghosting happens again.
try completely formatting your SD CARD/PARTITION.
& then reinstalling using (FAT 32/EXT 2, 3, or 4)
sometimes traces from the previous ROM might interfare with touch codecs (maybe)
just trying to help. had similar issue & this is what i did.
bandroid842 said:
NOTE: THIS SOLUTION IS POTENTIALLY DAMAGING AND MAY NOT WORK FOR EVERYONE
PROBLEM: touch screen acts erratic, notification bar keeps opening, screen appears to be touched by someone else continuously (Ghost Touch), and parts of the screen DO NOT RESPOND TO TOUCH.
MY OWN SPECIFIC CASE: I had the Ghost Touch issue for 3 days suddenly without intro, which often used to go away after a reboot or two, then phone worked normally after I removed the battery and left it in a dry area (in a closed drawer between books, no air entering, very dry atmosphere), however the RIGHT SIDE of the screen (Search button, rightmost letters [L and Delete and sometimes ENTER] do not work. If the phone is in normal landscape, you cannot open the notification bar by dragging it normally.
DIAGNOSIS: for some people, the problem is more severe. The Digitiser itself could be malfunctioning and has to be fixed, while for others it could be a true problem with the screen itself. However, for MANY OF US, it is a problem of HUMIDITY. The humidity sensors are causing the phone to act like that. Some say part of this problem happens because the way the keypad affects the phone internally as you open and close it a lot.
SOLUTIONS:
1- To be safe: send the phone to the shop. Ask them to open the phone and apply an extra layer of insulation, in case the digitiser and the screen are okay.
2- If something is faulty, replace it at the shop.
3- MY OWN SOLUTION: based on something I read many times, the solution was to apply DRY HEAT for at least 45 mins. What I did, based on averaging out many experiences I read online, was to remove the SD Card and SIM, remove battery, I heated up a toaster oven for 10 minutes, waited until the temperature was at about 60-70 degrees Celsius, SHUT DOWN THE HEAT, put the phone on its screen on a plate, screen facing down and covered by a cloth to protect it from direct contact with metal, then all inside the oven. The oven is a relatively big one, so phone was AWAY FROM A SOURCE OF DIRECT HEAT. I closed the lid, then every while 15 minutes I would heat the oven for 40 seconds to maintain the temp. This is LIKE (ALTERNATIVE SOLUTION) leaving your phone in the glove compartment of your car while its parked in a sunny spot, to find it really hot in the morning and tough to touch for a while. TO CONTINUE, after the phone was out of the oven (I can't believe I am saying this), I left the phone overnight in a dry area for 8 hours (could need less time). Then, I put everything back in, plugged it, and THE PHONE IS WORKING PERFECTLY NOW!
NOTE that solution number 3 could affect your keyboard buttons if heat is too much. It may cause the glue holding the keys to melt a bit. Be delicate with your keyboard after you restore your phone.
Again, I only did this YESTERDAY. With the exception of some keypad stickiness, the phone is working perfectly now.
I hope this was useful
B.
EDIT: Today is the First of May, phone is still working without a glitch
N.B. Press the Thank you button if you wanna congratulate me on daring to toast my milestone in the name of scientific inquiry
SECOND EDIT: Phone did it again for 2 days. Applied the same method, and it worked again. I think partially it happened because I was in a very humid location.
Click to expand...
Click to collapse
Thank you for that Solution.
It fixed the Issue of my friends MS without other problems
I'll have to try and the oven methode again. My phone has started to really act up again.
I've tried to install new roms, wipe ect. and it doesn't help with the screen.
Have anyone tried to replace the digiziter? They are pretty cheap on ebay
My milestone started freaking out just an hour ago. No more warranty here but I'm not brave enough to do the oven method. Had anybody tried the Rice alternative?

Auto power-on driving me nuts

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

Touchscreen Issues

Hi Guys; I recently got my new 2nd Generation Moto G but after setting it up and using it for 20 minutes or so I noticed that sometimes while scrolling through settings, contacts and webpages, that when i am swiping over a horizontal band in the exact center of the screen, the sensitivity of that region of the screen becomes very unreliable and the phone will often interpret scrolling as a press. While scrolling in my phonebook it has a tendancy to call people, when browsing the web it has a tendancy to press links i never wanted it to, and this same behaviour is repeated regardless of what application i am in.
It certainly seems to be more frequent and prominent while I am charging the phone, regardless of the charge current. I have charged it from my pc, 1000ma wall adapter and 850ma wall adapter; all with the same results.
Sometimes turning the screen off and on again can rectify this, but its usualy back again in no time
I have tried factory resetting the phone, with the screen protector both on and off, while on charge and off charge and while making sure nothing else could be interfering with the touch screen i.e., a case.
I only got this phone from ebuyer in the UK 3 days ago, 2 days earlier than it was actually ment to come! so its a real shame im having these problems, I've already spoken to Motorola about it and they have advised me to RMA the phone as they cant give me a definitive answer as to wether or not this is a Hardware or Software issue.
Has anyone else been having issues similar to those that I have experienced with their own new Moto G devices
I would RMA, mine is fine.
my moto(2014) has the same touch screen issues while phone is on charging. unresponsivene & its very annyoing. hpns only whn ph is charging
Sent from my GT-P3100 using XDA Free mobile app
xDDen said:
my moto(2014) has the same touch screen issues while phone is on charging. unresponsivene & its very annyoing. hpns only whn ph is charging
Sent from my GT-P3100 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using the official charger or some other one
Check u r charger or wall socket. its becoz of voltages issue.
ohh okk thnx guyz i was using samsung charger.
Sent from my GT-P3100 using XDA Free mobile app
Unfortunately my phone displays this behaviour both on and off the charger. It does however display the issue more frequently while on charge.
The chargers I'm using are all 5v which is typical of a phone charger. I have one at 850ma which charges painfully slow, I have another at 1000ma which charges much more quickly. And I use my Computers USB ports to charge at times, no matter how I charge the phone the problem remains.
Sometimes it will work fine for an hour or so then it will go insane on me. I have requested RMA with ebuyer. Had the phone only showed this issue on charge I may have been contempt with it, but the problem can happen anywhere, anytime and for a brand new phone that's not acceptable.
@ xDDen: have you tried charging the phone from any other source besides the Samsung charger you have?
yes now am charging with moto g's charger and it is working fine now without any issues
Sent from my GT-P3100 using XDA Free mobile app
Aileach XDA said:
Hi Guys; I recently got my new 2nd Generation Moto G but after setting it up and using it for 20 minutes or so I noticed that sometimes while scrolling through settings, contacts and webpages, that when i am swiping over a horizontal band in the exact center of the screen, the sensitivity of that region of the screen becomes very unreliable and the phone will often interpret scrolling as a press. While scrolling in my phonebook it has a tendancy to call people, when browsing the web it has a tendancy to press links i never wanted it to, and this same behaviour is repeated regardless of what application i am in.
It certainly seems to be more frequent and prominent while I am charging the phone, regardless of the charge current. I have charged it from my pc, 1000ma wall adapter and 850ma wall adapter; all with the same results.
Sometimes turning the screen off and on again can rectify this, but its usualy back again in no time
I have tried factory resetting the phone, with the screen protector both on and off, while on charge and off charge and while making sure nothing else could be interfering with the touch screen i.e., a case.
I only got this phone from ebuyer in the UK 3 days ago, 2 days earlier than it was actually ment to come! so its a real shame im having these problems, I've already spoken to Motorola about it and they have advised me to RMA the phone as they cant give me a definitive answer as to wether or not this is a Hardware or Software issue.
Has anyone else been having issues similar to those that I have experienced with their own new Moto G devices
Click to expand...
Click to collapse
Yea i have the same problem, what did u do.
mnishamk said:
Are you using the official charger or some other one
Click to expand...
Click to collapse
Mine actually didn't come with a charger. I was a bit surprised, but checking the Amazon page (for Germany, since I bought it here, though not from amazon) reveals that this seems correct/intentional. It did include the usual µUSB cable though (and it's not like I don't have enough USB chargers).
For completeness sake: I don't have the described problem, no matter if plugged in or not...
Touch issue
I'm using Moto G 2014 charger only and still facing issue bringing down notification panel.
Also i face issue when trying to unlock phone via pattern lock.
Flipkart offering me a replacement- Shall i go for it?
Been having a problem with the screen, mainly on the back soft button part of the screen, keep finger on it and it multi presses like a mad thing, doesn't happen all the time though, was driving me crazy. took off the Ultimate Shield screen protector and the problem went away, put the shield back on and the problem didn't come back, then couple of hours later (today) I got the ota update and the screen goes mad again, took shield off again and the problem continued, a few minutes later and it's all fine again. now (a few hours later) still all is fine.
Problem is I was all ready for doing a RMA to Amazon.co.uk for it, stuck on what to do now as if I send it back and they find no fault.
mtbgus said:
Been having a problem with the screen, mainly on the back soft button part of the screen, keep finger on it and it multi presses like a mad thing, doesn't happen all the time though, was driving me crazy. took off the Ultimate Shield screen protector and the problem went away, put the shield back on and the problem didn't come back, then couple of hours later (today) I got the ota update and the screen goes mad again, took shield off again and the problem continued, a few minutes later and it's all fine again. now (a few hours later) still all is fine.
Click to expand...
Click to collapse
Same issue here, but without any screen protector. OTA update hasn't changed anything. Sometimes it works and sometimes the screen recognizes double/triple taps where it should be only one...
mtbgus said:
Been having a problem with the screen, mainly on the back soft button part of the screen, keep finger on it and it multi presses like a mad thing, doesn't happen all the time though, was driving me crazy. took off the Ultimate Shield screen protector and the problem went away, put the shield back on and the problem didn't come back, then couple of hours later (today) I got the ota update and the screen goes mad again, took shield off again and the problem continued, a few minutes later and it's all fine again. now (a few hours later) still all is fine.
Problem is I was all ready for doing a RMA to Amazon.co.uk for it, stuck on what to do now as if I send it back and they find no fault.
Click to expand...
Click to collapse
Well the touch screen issues got way too much for me so I returned the phone to Amazon uk and got a refund, bought another moto g from Argos the same day I returned it and I'm glad I did, everything is ok with the new phone, no screen issues at all.
Moto G 2014 Tocuh Screen issues
Same issue here.
Bought phone 1 week ago from Argos. Initially fine, then suddenly cant use the swipe down notification bar.
Turned on the Show Touch indicator in Developer options and it clearly shows that the screen is registering the touches about 0.5cm down the screen from where I am touching. So you can never hit the notification bar when its doing that. I found that turning the screen off with the power button and then back on again usually clears the problem.
In the UK the phone only comes with a USB cable, so I use a variety of chargers.
I think mines going back as not functioning properly
I also having same issue you should post your emei. It might be I purchased defective from one of previous user having same issue. I'm at Singapore.
EMEI1: 359296054942769
EMEI2: 359296054942777
Android Version: 4.4.4
Based Version: MSM8626BP_1032.394.88.00R,EMEA_DSDS_CUST
Kernel Version: 3.4.42-g668a77b
[email protected] #1
Tue Aug 26 20:30:04 CDT 2014
System Version: 21.11.23.titan_retaildsds.retaildsdsall.en.03.reteu
Build Number: KXB21.85-23
DavidITunstall said:
Same issue here.
Bought phone 1 week ago from Argos. Initially fine, then suddenly cant use the swipe down notification bar.
Turned on the Show Touch indicator in Developer options and it clearly shows that the screen is registering the touches about 0.5cm down the screen from where I am touching. So you can never hit the notification bar when its doing that. I found that turning the screen off with the power button and then back on again usually clears the problem.
In the UK the phone only comes with a USB cable, so I use a variety of chargers.
I think mines going back as not functioning properly
Click to expand...
Click to collapse
I am currently having this problem
francescomulas said:
I am currently having this problem
Click to expand...
Click to collapse
Me too! I am very sorry to learn that it is a hardware problem.
I'm afraid to take it to the service center because the problem is intermittent and technicians could not detect it .
Any of you have solved?
If it was a hardware problem we could try asking a kind of compensation, I don't know, some free accessories, or maybe the change of the device...
Had a problem with mine, it would go mental pressing the back softkey, press it once and it would just keep doing it by itself, so a problem with lower left of the screen, sent it back to Amazon for refund and got another one from Argos, this one is mostly alright with the screen touches but will sometimes do a double press or think a press is a swipe anywhere on the screen, it's not been so bad that I kept it, but now other problems like the memory shortage making apps close is starting to really get to me, also the screen rotation get stuck in landscape now and then, even it sometimes goes to landscape by itself.
In the process of getting a different phone as this is starting to annoy too much.

Reflow Main Board @home

I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........
I say FASCINATING! How do you get it apart to get the main board out? Mine never gets LTE anymore, which sounds to me like an antenna came disconnected. Heating up the antenna connections might be worth a shot.
fatboyRICH said:
I was given this Verizon G2. The complaint was random reboots resulting in getting stuck at LG logo at boot. I Googled and found out that the internal SD card solder connection to the main board goes bad. So, I tried a standard conventional oven @ home reflow of the main board. I removed the G2 main board and baked it in the oven at 380° for 8 mins. I am typing this post from the phone. It successfully rebooted on the first try after reassembly. It has been up running CyanogenMod 12.1 (flashed before bake) for about 10 mins. I booted it and went straight to chrome and xda.com. I'll be back later. I'm gonna go make some calls and play games and see if I still get a reboot.
Update 1: I'm an hour or two in now and have made a 20+ minute phone call while using a Bluetooth headset and still using other apps like social media and reddit.
Update 2 -Final update: Since I got zero replies on this, I'll assume no one cares. If anyone does, the phone is still working. I've been using it as my daily driver for like 3 or 4 days now. I'm gonna keep using it for another couple weeks until my tax return gets in and I can buy an unlocked D851.
.........The End........
Click to expand...
Click to collapse
You will never be able to truly reflow any electronic devices in your typical household oven as they do not get hot enough. Standard leadfree reflow temperatures peak around 500F, after a ramp up and ramp down time that prevents thermal stresses from destroying the parts. Even with the proper equipment, reflowing BGA/CSP parts is difficult without removing the parts first and then re-balling them as the flux has already been cured during the initial solder process.
I would seriously caution anyone from attempting this without the proper tools and knowledge as you could permanently damage any one of a number of components - I've seen IC packages literally explode after absorbed moisture in the device's resin packaging vaporized by ramping too fast.
T
I care Rich, I care. I loved my G2 but it crapped out on me at school one day. No warning just froze and shut down. Got it back up long enough at one point to pull whatever data I could from it. I ended up getting an S6 Active after jumping between a few crap phones, and the G2 sat in a drawer until tonight when I was looking for some standoff screws in the drawer, and I saw my old flame. The pain from losing her never really went away, and for some reason, I think because I recently did a bit of soldering on a RPi, I thought what if I tried to re-flow this thing? What do I have to lose at this point. Googled g2 mainboard reflow, and your post lit up my life. I baked at 380F for some amount of time re-assembled and I have my G2 again! I may have tried it eventually, but your post inspired me to tear that **** out and turn on the oven right away. I mean, obviously I'm not going to ditch my S6 for the G2, but I'm happy to have it back. Maybe I'll use it for things. Thank you, Rich.
I care!
Mine stopped working.
Was getting pretty hot on a regular basis.
When plugged-in, no lights, just heating up.
Read about "solder re-flow" - don't know how to.

Categories

Resources