Temperature sensor incorrect - a5 2016 - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Hey there!
Long story short: Some sort of water damaged. Phone was dead for a week, now it's working but the temperature sensor is damaged. It wont let me load it because its constantly giving weird low °C's.
Its somewhat reflective of rl-temps (hand - warm, table not so much) but far from right.
Thing is, I wont even bother but just being able to load my phone while it is ontop of my heating isnt that nice (and far from healthy).
So, I guess I have to change that little sensor, if thats possible at least.
Anybody knows where this thing is located? And how I can change it?

Related

[Q] Finger print sensor- "way too hot"

Hey guys for some reason the past few days my finger print sensor has been on fire!!! I mean so hot it burns when I first touch it. No other part of my phone has excessive heat either that's why its bothering me so much. And its doing it while the phone is idle. So it has nothing to do with it being under load just to let you know. Any ideas? thanks
Edit: Just thought i could add a bit more info. I have taken the cover off and the battery is cool as can be. The screen is not hot or anything.

[Q] Kernel/rom that disables or modifies the proximity/light sensors?

I got one of these from Ebay and the thing was in great condition for costing 160. The only issue is that in very dark environments the screen can be a chore to turn on as it keeps turning itself off, likely due to my proximity sensor being a tad finicky or something (no issues in any reasonably lit environment, even street lamps at night, but it seems like I have to be like 1 foot away from the thing sometimes). Are there custom ROMs/Kernels that disable this functionality or make a workaround where if you say hold two of the keys at once the screen will turn on regardless? I think I'm describing something from a thread a few threads down but it's rather old. This is a really simple question. I know it's not good to ask for recommendations on ROMs/kernels but I'm asking for a very specific feature.
Bump I guess...
I think I figured out what the issue was, it seems to be the proximity sensor specifically. The light sensor seems to be working as expected because this doesn't happen in bright conditions. I also looked up where the proximity sensor is located and it looks like there are a few pieces of dust there or something. I guess since no one is making any suggestions on what has or hasn't worked, I'll just open it up and wipe that dust off by taking out the sensor. Looking at the teardown the top section doesn't look terribly complicated. I've had to fix my Vita's left joystick before so this shouldn't be too much different. I just hope those aren't scratches on the back of the glass or something.
Edit: Actually nevermind I just went ahead and did a Towelroot and then installed CM11. AFAIK all is well now and I'm also rooted, so 2 birds with one stone. Technically 3 since all that friggin bloatware is gone.

Overheating Issue On Galaxy Note 4 N910G.

Hey,
I've Galaxy Note 4 N910G. It got heat up with use. It got so much heated up that it can iron clothes. I noticed that it happens when I increase screen's brightness, and one biggest thing to notice is that whole body is cool expect the upper part (where camera lies). And in upper portion, screen side is hot when touched. So I remove plastic case and check whether battery or camera, sensor are hot, but it didn't seems to, only the area that lies under receiver is hot when touched.
I concluded brightness factor due to following reason:
-I've played GTA LCS to a very long period in very low brightness and phone didn't heat up a lot, but yes, a little.
-I've then played the same for very same period but with mid brightness and phone started heating up, then a lot!
-I've used my Note 4 for a very long time downloading and installing apps in minimum brightness and it doesn't heat up.
-I've played on the music with screen off for a long time, and it still don't heat up.
-While backing up or doing anything in TWRP recovery it get heat a lot.
It doesn't mean that I should you Note 4 with minimum brightness. It was running on stock firmware, so I flashed Dr. Kretan custom Rom, I thought it would help, but it doesn't.
Please help me, what should I do?
Hmm that's a strange part that heats up since the CPU is on the side near the power button. https://d3nevzfk7ii3be.cloudfront.net/igi/rZAAWFWV4qobuSI4.huge
Normally when a device gets hot at a certain point other than the CPU it usually is water damage or a broken IC (component) on the mainboard.
Preet Juneja said:
Hey,
I've Galaxy Note 4 N910G. It got heat up with use. It got so much heated up that it can iron clothes. I noticed that it happens when I increase screen's brightness, and one biggest thing to notice is that whole body is cool expect the upper part (where camera lies). And in upper portion, screen side is hot when touched. So I remove plastic case and check whether battery or camera, sensor are hot, but it didn't seems to, only the area that lies under receiver is hot when touched.
I concluded brightness factor due to following reason:
-I've played GTA LCS to a very long period in very low brightness and phone didn't heat up a lot, but yes, a little.
-I've then played the same for very same period but with mid brightness and phone started heating up, then a lot!
-I've used my Note 4 for a very long time downloading and installing apps in minimum brightness and it doesn't heat up.
-I've played on the music with screen off for a long time, and it still don't heat up.
-While backing up or doing anything in TWRP recovery it get heat a lot.
It doesn't mean that I should you Note 4 with minimum brightness. It was running on stock firmware, so I flashed Dr. Kretan custom Rom, I thought it would help, but it doesn't.
Please help me, what should I do?
Click to expand...
Click to collapse
i guess its snapdragon chip problem, mine gets heat up but not until where i can iron clothes, as twrp backup doesnt heat mine, flashing and booting rom for the first time will heat up. i always try to cool it before anything bad happens
galaxy16 said:
i guess its snapdragon chip problem, mine gets heat up but not until where i can iron clothes, as twrp backup doesnt heat mine, flashing and booting rom for the first time will heat up. i always try to cool it before anything bad happens
Click to expand...
Click to collapse
SquirtingCherry said:
Hmm that's a strange part that heats up since the CPU is on the side near the power button. https://d3nevzfk7ii3be.cloudfront.net/igi/rZAAWFWV4qobuSI4.huge
Normally when a device gets hot at a certain point other than the CPU it usually is water damage or a broken IC (component) on the mainboard.
Click to expand...
Click to collapse
Thanks for your answers. I notice this thing again with Xposed module for CPU temperature in status bar. And you got it right, it is CPU issue, so, how can I fix it? Should I underclock CPU? Or is there anything on market like some heat sink compound! I really have no idea. Ironing of cloth is just saying to show what I'm talking about, currently when it get heat up, I put it in front of Air Conditioner! I appreciate your answering.
Preet Juneja said:
Thanks for your answers. I notice this thing again with Xposed module for CPU temperature in status bar. And you got it right, it is CPU issue, so, how can I fix it? Should I underclock CPU? Or is there anything on market like some heat sink compound! I really have no idea. Ironing of cloth is just saying to show what I'm talking about, currently when it get heat up, I put it in front of Air Conditioner! I appreciate your answering.
Click to expand...
Click to collapse
i do that too when i feel like its really getting hotter, you can underclock cpu abit but no too low. any other method to fix that heating im not sure. i guess underclock and play your phone in a cold room is the solution

Theory on Potential Partial Cure for Random Restarts/Freezing (Long Post)

First and foremost, I don't promise this will fix anything as it has only worked for myself, but let me share my experience/journey and see if this can help at least another person in the same boat as I am.
If you do not want to read the entire story, feel free to skip to the break below.
Back story:
I got the phone in Hong Kong back in November. It's a 505 H815TR. (Don't ask me why I ended up with a Turkish phone, I have no idea)
The phone worked fine for about two weeks, then it would one day start to restart randomly. It also started happening more and more frequent, and the phone might fail to boot at all.
Sometimes it would just freeze on a screen and there'll be artifacts like the GPU overheated. When that happens the phone wouldn't even respond to a hard power-off (holding power for 4 seconds+) and I'd have to take out the battery.
Unfortunately for me, I have since went overseas and LG would not honour the motherboard swap. I also didn't want to sell this otherwise great new phone to another unfortunate soul either. So I'm stuck with the few hundred bux worth of not-quite junk. Determined to not let the money go to waste, I still tried to use it as a daily driver but it had gotten so bad at one point that I had to keep taking the battery off and restarting every few minutes during a meeting like an idiot.
So I tried upgrading the firmware, in hopes that it'll at least improve the situation. It was the 20c firmware. I used LGUP to upgrade it and it got better, if only for a while.
I thought, hey it ran better! Maybe I can stick it out, and sucker up the less frequent restarts. It will run okay for a week or so with occasional restarts. Then it suddenly got bad one day I opened up Maps for navigation. It would suddenly go back to a few restarts an hour.
At this point my hypothesis is that apps/sensors that would require a hike in power can trigger the crash. (duh!) So I turned off Bluetooth/GPS/disable every other app that I can think of. While it help a BIT, it certainly did not alleviate the problem. It had only gotten worse as time goes.
A few weeks went by, 20d came around. Hoping situations would improve, I upgraded the phone.
The problem got WORSE. I thought that's weird, the new version should have came with optimizations and gave less work the phone - hence it should freeze less. Puzzled and disappointed, I flashed back to 20c and was prepared to bite the bullet and accept it as lost cause. To my surprise however, when 20c finished generating cache and booted up, things started looking better again. It would run a few DAYS without problems. I got even more confused. If the problem was purely triggered by spikes of load, going back to the old firmware should have little to no effect. Something else must be going on. Before long, the problems came back and I'm plagued by the restarts again.
I came up with 2 possible hypotheses:
1 - It had something to do with cache
2 - It had something to do with Doze optimizations
Number 2 was easy to test. I went to settings and ignored every possible optimization (****ty UI on that screen by the way. It takes forever to scroll to anything and the checkboxes don't save until you exit the menu. When a restart hits before I exit the menu all progress is lost and I had to start from beginning :crying: ). I ran for a few more days and it seemed to have little impact.
So I was fairly confident at one point that it had to do with cache. Unfortunately, the G4 (at least my G4) does not have an easy access to erasing cache (which was incredibly annoying LG!). The so-called stock recovery only has an option to wipe the phone and obviously I didn't want to do that. I also did not want to temper with bootloader for the same reasons aside from the risk of bricking the phone. I had remembered that when I upgraded the firmware the cache gets wiped and it'll be regenerated on first boot. So I thought I'll just flash the same firmware and I'll be done! To my demise, apparently flashing the same kdz does NOT trigger the cache generation process. What I had to do was to flash 20d, boot that, and flash 20c again.
Things started to look better here. It ran fine. It did not crash for about a week or so. I thought it was a fair compromise. I can deal with a quick refresh(flashing 20d and then 20c again) once a week. Whenever I see signs of the restarts, I would quickly refresh when I got home that evening and it will be good for a week or so. Here I was ready to finalize my theory until...
It crashed. Soon after one of my routine refresh. I thought this was interesting? If it had to do with some kind of cache buildup, surely it would not crash right after a refresh? What's weirder still was it stopped doing that after 2-3 times. Something ELSE MUST be contributing to this. What else was related to the process of cache generation that could affect the stability of my system?
Here ladies and gentlemen, is what my little pea brain have came up with, through trial and error, no engineering background, limited tech knowledge, and limited common-sense:
It had to do with the activity of the CPU; or more precisely, it may have to do with the extended heating process that caused some component around the area to change in some kind of state, and thus improving the stability for a duration until it gradually changes back with time.
Engineers are probably laughing at me right now. I know it probably makes no sense, but it's the best that I can come up with. So I come to you guys, maybe some may help shed some light on this issue that plagues those of us who are stuck with the problematic phones that are not eligible for exchanges/repairs.
Anyway, to test my theory out, I downloaded some kind of stress tester from Google Play (I used StabilityTest v2.7)
I would wait until the phone starts restarting again (and it will, and when it does happen the stability dropped SHARPLY, from no restarts to maybe 2-3 an hour).
Then, I would run StabilityTest. I chose the classic stability test, and just let it run.
The first time it ran, it did not survive the first 10-15 mins. The phone would restart, and I would try again.
This time it ran for 2 hours without restarting (double the time needed for generating cache twice on my phone). I manually stopped the test and started using it normally.
Lo and behold! It was rock solid stable! No crashes, no matter what I did! Wifi, bluetooth, GPS, games, maps, youtube,... all of the above?!
And it would stay this way for me for about 2 weeks. When the phone starts restarting again, I would run the stress tester for a couple of hours, and it would be stable again.
I have since tried the 20d firmware, which also ran fine. I also flashed 20e yesterday, and so far it has been very smooth. I have tried various amounts of times like 1hr, 3hrs, 10hrs, but it would seem that going longer than 3hrs have no impact on the interval between restarts. So personally I find 2hrs will last me 2weeks or so and that works best for me.
I may not have completely solved the problem, and I still don't understand why it works, but it is sort of working for me.
And I hope it would work for you as well!
So here you go! And thanks for reading this unnecessarily long post!
TL;DR
Summary - I have found that by putting the cpu on load for an extended amount of time will dramatically increase the stability of the problematic phone. Here's something you can try:
Disclaimer: I do not guarantee this will work on your phone. I am no engineer. I take no responsibility if it causes any problem on your phone or if it explodes. That being said, it has worked for me. Please try at your own risk!
1. Make sure the area is well ventilated, the phone has sufficient battery or is charging.
2. Download and run "StabilityTest (ROOT Optional)" from Play Store.
3. Run "CLASSIC STABILITY TEST"
4. Let it run for at least 2 hours. If your phone restarts during the test, try again.
*However I would keep an eye on the temperature. I normal at around 50-60 Celsius.
5. It SHOULD be okay now. Depending on how bad your particular problem is, you may have to repeat this process every week or two. Experiment with different load times and see where your sweet spot is.
Thanks,
cbpneuma
Thanks for writing up your experience and theory. I wonder if the additional stress load is generating a large amount of heat that is curing some type of mechanically related electrical fault like a cold solder joint or marginally loose connection.
Some people bake or freeze their phones once the phone is continuously bootlooping so that they can get it to boot up and stay operational long enough to pull their data off the phone.
LG should take responsibility of their shoddy product and replace all affected serial numbers now without questions or provide a 3 year extended warranty.
Wow
That's great TC.
This is the first real lead that anyone has made ( to my knowledge)
And may be why LG is quiet on the cause of the hardware failures
Similar heading would help red ringed Xbox 360 and yellow light ps3's back in the day
cbpneuma said:
Engineers are probably laughing at me right now. I know it probably makes no sense, but it's the best that I can come up with. So I come to you guys, maybe some may help shed some light on this issue that plagues those of us who are stuck with the problematic phones that are not eligible for exchanges/repairs.
Click to expand...
Click to collapse
Not laughing if anything your patience and dogged determination is inspiring.
Great write up
I have found out something !!!
After 6 months of use of my LG G4 H815 S/N 509 Germany... When I put it over heavy load and let it heat up pretty well ( about 70-80 degrees Celsius ) I used to take the back cover off !!! I smelled it several times through out this period !!! And guess what I used to smell ??? The smell of flux !!! which shouldn't be there... I used to work daily fixing Mobos and PCBs so I know how flux smells like !!! My theory is that there is an excess of flux with the solder on the board and as we know flux helps solder to melt at lower temps, so at certain high temps on the G4, flux is slightly boiling... which is causing these fumes ( no smoke though !!! ) !!! Which could cause either of both:
1. An isolation if flux wastes get between the solder and the PCB !!!
2. If solder is deforming or melting which might cause loose contact between the components and the PCB !!!
How to fix this, it is all about burning the flux away without causing damage to the mobo :
1. Heat the hell out of your LG G4 while it is sitting still on a table !!! ( AND I REPEAT, SITTING STILL !!! NOT MOVING AROUND !!! )
2. The better solution would be to fix it like we fix GPUs !!! And this will burn the flux away so the solution should work...
a. Disassembled your LG G4 and remove your mobo.
b. Turn on your oven and heat it to 200 Degrees Celcsus .
c. Place your mobo on the Aluminium foil stand onto a cooking sheet or Aluminium foil with the EMI shield Up.
d. Once Oven has reached the 200 Degrees Celsius... place it into the Oven and bake it for 7 min.
e. When time up, leave the Oven door opened and the it stand or cool down for at least 60 min. (but I recommend you wait 120 min. to be on the safe side !!! ). Do not touch it or move it or eat it ( LOL, that sounded dirty... ) !!! Be patient.
f. Finally, reassemble your G4 and turn it on !!! It should work fine now !!!
Don't attempt this fix unless you are aware of what you are doing !!! And only if LG refused to fix your precious device !!! Don't attempt to fix it if you lack the required experience and skills !!! Learn how to do things first...
" DISCLAIMER: "
I am not responsible of any damage you cause to your device, yourself, your surroundings... or even your entire god damn country !!! LOL... I am not responsible if you cause a thermonuclear war or get the USA and Russia into war trying to fix your device !!! So please be aware of what you are doing and be careful !!!
BTW I hear a weird sound ( similar to spinning HDD if you ever heard one ) coming from the SoC area on the LG G4 when I put it under heavy load !!! I wonder if it is normal or due to the loose contact which usually causes similar sounds to come out of electronic components !!! Does anyone else hear that ??? Is it normal ???
( btw before you start saying that, I know smartphones don't have HDDs !!! I was just describing the sound !!! )
Just a comment... flux does not actually lower the melting point of solder, but rather helps it to flow better to the metal traces of the components and printed circuit board.
From Wikipedia (https://en.wikipedia.org/wiki/Flux_(metallurgy))
In high-temperature metal joining processes (welding, brazing and soldering), the primary purpose of flux is to prevent oxidation of the base and filler materials. Tin-lead solder (e.g.) attaches very well to copper, but poorly to the various oxides of copper, which form quickly at soldering temperatures. Flux is a substance which is nearly inert at room temperature, but which becomes strongly reducing at elevated temperatures, preventing the formation of metal oxides. Additionally, flux allows solder to flow easily on the working piece rather than forming beads as it would otherwise.
The role of a flux in joining processes is typically dual: dissolving of the oxides on the metal surface, which facilitates wetting by molten metal, and acting as an oxygen barrier by coating the hot surface, preventing its oxidation. In some applications molten flux also serves as a heat transfer medium, facilitating heating of the joint by the soldering tool or molten solder.
cbpneuma said:
First and foremost, I don't promise this will fix anything as it has only worked for myself, but let me share my experience/journey and see if this can help at least another person in the same boat as I am.
If you do not want to read the entire story, feel free to skip to the break below.
Back story:
I got the phone in Hong Kong back in November. ...
Click to expand...
Click to collapse
Very interesting. Keep in mind that almost all of the bootloop problems are fatal - the phones won't boot up unless placed in a freezer, and eventually many of those phones won't boot up at all, even if placed in freezer. And the oven method doesn't provide for a long term fix.
For most of us, once it starts to bootloop, the phone is basically dead.
kwarwick said:
Just a comment... flux does not actually lower the melting point of solder, but rather helps it to flow better to the metal traces of the components and printed circuit board.
From Wikipedia...
In high-temperature metal joining processes (welding, brazing and soldering), the primary purpose of flux is to prevent oxidation of the base and filler materials. Tin-lead solder (e.g.) attaches very well to copper, but poorly to the various oxides of copper, which form quickly at soldering temperatures. Flux is a substance which is nearly inert at room temperature, but which becomes strongly reducing at elevated temperatures, preventing the formation of metal oxides. Additionally, flux allows solder to flow easily on the working piece rather than forming beads as it would otherwise.
The role of a flux in joining processes is typically dual: dissolving of the oxides on the metal surface, which facilitates wetting by molten metal, and acting as an oxygen barrier by coating the hot surface, preventing its oxidation. In some applications molten flux also serves as a heat transfer medium, facilitating heating of the joint by the soldering tool or molten solder.
Click to expand...
Click to collapse
You probably misunderstood me... But it is okay !!!
Flux helps the solder to melt faster ( not lowering the melting point of solder ) cuz it allows better heat transfer... It also helps soder to better stock to the PCB and the terminals of electronic components !!!
Flux with solder works like oil when you want to fry potatoes... It will make them get cooked faster !!! Without oil they will take longer time !!! I hope you get my point....
starfcker69 said:
Very interesting. Keep in mind that almost all of the bootloop problems are fatal - the phones won't boot up unless placed in a freezer, and eventually many of those phones won't boot up at all, even if placed in freezer. And the oven method doesn't provide for a long term fix.
For most of us, once it starts to bootloop, the phone is basically dead.
Click to expand...
Click to collapse
I feel like this more because of the **** implementation of CPU, since I disabled 2 main cores almost 3 or 4 weeks ago my phone is running pretty well and I'm even on a custom ROM.
Adam Myczkowski said:
I feel like this more because of the **** implementation of CPU, since I disabled 2 main cores almost 3 or 4 weeks ago my phone is running pretty well and I'm even on a custom ROM.
Click to expand...
Click to collapse
What was your phone doing before you disabled those two main cores and do you feel any performance decrease with them disabled?
divineBliss said:
What was your phone doing before you disabled those two main cores and do you feel any performance decrease with them disabled?
Click to expand...
Click to collapse
My wasn't completely dead, it was booting up sometimes, rarely but usually in the really low temps, I tried baking the mobo, worked for few hours and phone died, I put thermal pads on all the components what made pressure on them pushing them apart into the processor, phone worked, but again in REALLY low temps if it got up to like 27•C the phone constantly rebooting. ( I was on stock Marshmallow btw ). Then I found this reddit thread about disabling big cores, somehow it worked. Works only on 5.1, just saying. Anyway even though I disabled only 2 cores, the phone have been booting up only on 1 (WTF), what made it really slow and laggy. Fortunately, if you root your device you can enable all 4 cores in device manager. Or if you have H815 with unlocked bootloader as I do, you can flash any AOSP, CM, AOKP etc based ROM, with root and enable all for cores as well, I don't feel that big difference since I'm on pure android really. I already found a bug that disabling 2 cores is causing, on SUPERXE AOSP ROM this is somehow causing lockscreen settings to crash as I am not able to have any screen lock, weird bug... I didn't try any other ROMs.

Weird touch screen issue with my phone.

My LG G6 has a really weird kind of touch screen problem. When I prop my phone into a 90 degrees place (even sometimes I flatten the phone into flat surface) , the areas that I drew in the example starts to get inresponsive.
Is this a software problem or hardware problem?
The areas that have the problem on the screen: http://imgur.com/a/kDQ7B
The video: https://www.youtube.com/watch?v=UDdoai51TrM&t=3s (Can't talk English well)
Hi. Just realised that my G6 has the same problem as yours. Doesn't really affect me too much in everyday use, but it is irritating to know that the high end phone like this has such problem . Just wondering what happen to yours now? Have u found a way to fix it? Thanks.
warriorrr said:
Hi. Just realised that my G6 has the same problem as yours. Doesn't really affect me too much in everyday use, but it is irritating to know that the high end phone like this has such problem . Just wondering what happen to yours now? Have u found a way to fix it? Thanks.
Click to expand...
Click to collapse
I fixed it by removing my glass protection. That glass made the phone's screen pretty irresponsive at those areas.
Thank you for your reply. I actually thought of the tempered glass too, but didn't expect that as the real cause. Anyway, I'll just stick to what i have now as it doesn't really impact my everyday use. Or I might try another glass brand as I dont think i will survive without screen protector, haha.

Categories

Resources