Related
Something really weird happened to my O2 mini s. I just saw all the LED lights flash and then the phone vibrated and went blank. I did a soft reset it restart but then the same thing happened. I did a hard reset it was all ok, then when the O2 software began installing it did the same. Flashed all LEDs including the flash led vibrated and went blank. I though it was the battery. Changed the battery and it would refuse to wake up, just switch on all LEDs and keep vibrating. This kept happening for several times, and then suddenly all was ok. Re-installed an all, all is fine now. But I wonder what happened? And will it happen again? Any explanation by anyone would help. Thanks in advance.
This sounds like a hardware fault to me.
Can you think of ANY outside influences? Things like extreme temperature exposure, exposure to high humidity, or very fast changes of temperature or humidity could all cause shorts or low resistance conditions. I don't know that any of these historically lead to the type of fault you experienced specifically in Wizards, but from an electronics standpoint, anything of this nature could cause bizarre but temporary faults. Even dropping it could cause you problems of an unusual nature.
If the answer to any of the above (except dropping) was yes, do this:
Gather up all the desiccant you can find. This stuff can be found in bags of jerky, and in just about any electronics box ever packed. Sometimes I find little "jars" of desiccant in medicine bottles (long-acting antacids, in particular). Put the phone in a plastic zip-top bag in a warm, dry place with all of the desiccant inside and seal it up tight. Leave it for at least 12 hours, but 24 would be better. Throw away the desiccant when you're done.
If you can't come up with an outside cause for the fault, you may just have to chalk it up to the age of these phones. They are far from new. Even if you just bought yours, chances are good that it is refurbished, and electronics, like fruit, will go bad eventually.
Thought so...
Thanks for your detailed reply. I think the temperature would be the reason. I am in India and that too in the Southern part and its been awfully hot these last few days (40 deg. C or more) yesterday I was in my room and had switched on the air conditioning, the phone was near the ac for a while. Then I did switch off the ac, probably this fluctuation caused to form moisture? It was behaving weird but its ok for the time being... for the last 12 hrs or so. I am waiting for 3G services in India before I decide on my new phone, so I hope this lasts for another 6 months. Hope! Thanks again, will try your method if this happens again.
The problem is back and won't go away. Should I bury my phone? Or is there hope? Any help would be appreciated. Thanks in advance.
If dessication didn't work, you can also try swapping batteries with someone (best to do this while the problem is presenting itself).
You can also try doing a hard reset as a last resort (remember to backup your PIM info!), but I doubt this will do you any good. However, it doesn't cost you anything, and is therefore worth a try.
See if your service carrier offers insurance on your phone. If they do, sign up, and turn it in a week later for replacement. Just remember to wipe out your personal data and remove any HardSPL/Unlocks you might have done.
If insurance fraud is distasteful to you, hit eBay. You can usually score a decent condition Wizard for around $120 USD.
I haven't really tried dessication, but I think its gone beyond that. Batteris I have 3 and none of them worked. Is it easy to open the phone and try and "air" it? Will that help. Unfortunately carriers in this country don't have insurance plans. So that leaves out that last option. And if I have to buy another phone then why... the same one... ;-) Thanks anyways..
Hi.I have an xperia x10 which has defective motherboard.I have sent it to service 2 times but they didn't fix it.The first time they just updated the software.The second time in the report says that they made a customisation update.Now my x10 doesn't turn on.The led light is not even blinking when i press the power button.I am charging it right now but nothing happens(no animation,no green light nothing).Can i do something else?I am feeling depressed about SE's service....
If it's not in the right section please move it.Thanks
HS! Go onto gripe.com, google or yahoo search. Sign Up, post gripe, and good luck!
Sent from my X10a using XDA App
Have you tried letting it sit a while after u held the power button on and it vibrated?
Have you tried removing the battery for ten seconds then trying again?
Sent from my X10i using XDA App
Do you have another battery? Try that. Might also be the USB charging cable. If you can, request another. They should replace mobile if still under warranty.
Sent from my X10a using XDA App
I am agree with you on the power up @kindred, you are totally right about that.
Sent from my X10a using XDA App
Thanks for your replies.Yes i tried a new battery.It 's the same.Phone is under warranty.SE should give me a new phone or replace the motherboard. :/
They wont give you a new phone, mine has the exact same problem an they trying to say it was dropped and got damaged that way, they gave me a replacement which condition older than one I sent in, then it died again couple months later. And now they wont do anything. I bought mine less than a year ago.
Sent from my Desire HD using XDA App
It's tragic..What can i do now???I have paid a lot of money for this cellphone. I am desperated...
same thing happens to me deffective motherboard
i cant get calls and when i listen to a song or video get stucked and bizzared sound come out
damn it SE
lildic said:
same thing happens to me deffective motherboard
i cant get calls and when i listen to a song or video get stucked and bizzared sound come out
damn it SE
Click to expand...
Click to collapse
Yes, that same happend to me.
or sometime when I am listen music no can have open the wifi, the x10 come to reboot.
who know where can get a new motherboard?
thanks
Take it back again and again and again.
Be persistent.
Sorry to hear that mate... if it would be in my hands, I've swapped it...
SEMC official routines doesn't include even Neocore for stress testing, as Desire has, few X10's had also defective Snapdragons, not that many as HTC had tough...
Just try again, maybe it will venture into more skillful repair technician...
I hope but i don't think so..I will try one more time and If they don't fix it i will sell it to ebay if someone want it for spare parts.
Motherboard Issue on x10a
I bought one of these second hand and I got ripped off. Without warranty I was pretty much stuck when the phone began freezing, rebooting, getting hot and just plain sucking. I upgraded the phone from 1.6 Android to 2.1 then to 2.3. Nothing helped. Beautiful phone but this one's a dud.
Well with nothing to lose I thought long and hard, explored the options and came to one conclusion. I was time to open this thing up and see if I could fix it myself. I downloaded the instructions from the net and went to work. The first time I opened it, cleaned it and flattened out the bubbles that I found on the CPU's copper tape.
I wasn't thinking that that was all that was wrong, and I was right. It still acted up and froze/rebooted. Well I ordered a new phone and when it arrived I decided to do something that I never would have done unless I had the replacement phone to use.
I opened up the X10a once again. Stripped out the PCB (mainboard) from the phone, removed all copper tape, and black tape that covered other components on the PCB. I then covered the PCB in tinfoil but clipped out around the CPU to let it bake more so than the rest of the board. I used a convection oven with the fan turned ON, set it to 210 degrees Celsius, let it heat up for a good long time (20 mins). Laying the PCB perfectly level was tricky, but not impossible. I made sure the CPU was facing up. I used an upside down ceramic plate for the baking surface. I placed the plate with the PCB into the convection oven and baked it for 10 minutes.
After 10 minutes, I shut the oven off, left the door closed for a minute then propped it partially open for another 2 minutes. After that I opened it up over half way and left it alone for 30 minutes. After that I removed it from the oven and let it sit for another 30 minutes. After that I put it all back together and prayed. Not literally.
I seems to have worked. Before this I couldn't play a game and listen to music or browse the web VIA WIFI and listen to music at the same time for longer than five minutes before the phone would reboot/freeze. I have been playing music and playing games for WAY longer than that now. Same with browsing and music. No problems..Yet. If you're even remotely interested I'll keep you updated. I recorded the entire process and I will be uploading it to youtube later.
I'm so glad this seems to have done the trick, but with a lot of re-bake / hack reflows It may only be a temporary fix. Well, IMO, better that then having a 1/4 functioning "smart" phone. It worked for me, it might now for you, so if you attempt it and over bake your phone's PCB mainboard don't blame me.
As a side note, I am typing this from a Dell Inspiron 9400 laptop. Last year this laptop died due to a flaw in the video card. I rebaked the video card in my home oven and it fixed the problem. Up until now, a year and counting I haven't had an issue with it. Knocking on wood (literally).
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.
So my battery, like many others, is severely degraded and shuts down early (was shutting down at 20%, now 40%)
As far as Huawei is concerned, I'm on my own.
*4 days out of warranty gets you nothing even if its a known defect that becomes apparent at around a year... definitely something to consider next time you think of buying from this company--Huawei.
I ordered a battery that comes with an install kit (probably not necessary since Ive worked with small parts before and have most or all of the tools.)
But can I really use a hair dryer with this? It seems logical, no doubt itll take a bit longer. Im just concerned theres an unforseen downside. Thanks.
KLit75 said:
So my battery, like many others, is severely degraded and shuts down early (was shutting down at 20%, now 40%)
As far as Huawei is concerned, I'm on my own.
*4 days out of warranty gets you nothing even if its a known defect that becomes apparent at around a year... definitely something to consider next time you think of buying from this company--Huawei.
I ordered a battery that comes with an install kit (probably not necessary since Ive worked with small parts before and have most or all of the tools.)
But can I really use a hair dryer with this? It seems logical, no doubt itll take a bit longer. Im just concerned theres an unforseen downside. Thanks.
Click to expand...
Click to collapse
Hair driers work fine. Trust me.
So something I noticed on my old note 4 is that the screen has a strip unresponsive to touch (pen works fine).
The thing that weirds me out is that when you reboot the phone, it works perfectly fine, but after being on for a few hours, the middle part of the screen just stops responding.
Rebooting revives the part of the screen, but not for long. Factory resetting it does nothing different and it's running completely stock firmware and software.
Any ideas as to what's causing this? I'm not sure if replacing the screen would help since it seems to work fine for the short duration that it does.
It sounds like a digitizer problem. I wonder also if the heat of the phone is causing something to change or even physically warp to cause the unresponsive part.
Unidave199 said:
It sounds like a digitizer problem. I wonder also if the heat of the phone is causing something to change or even physically warp to cause the unresponsive part.
Click to expand...
Click to collapse
Either a blown display or mobo.
A trace, solder joint, micro weld or junction failed.
It's possible it could be a connector/ribbon cable failure in which case easily repairable.
Check the display/mobo ribbon connectors...
Unidave199 said:
It sounds like a digitizer problem. I wonder also if the heat of the phone is causing something to change or even physically warp to cause the unresponsive part.
Click to expand...
Click to collapse
I'm pretty sure it's not heat since you can turn it on, leave it on a table, idle without anything running, and it'll be completely room temp and the part of the screen stops responding.
blackhawk said:
Either a blown display or mobo.
A trace, solder joint, micro weld or junction failed.
It's possible it could be a connector/ribbon cable failure in which case easily repairable.
Check the display/mobo ribbon connectors...
Click to expand...
Click to collapse
I'll give them a look over, hopefully reseating connectors may help
YellowSomething said:
I'm pretty sure it's not heat since you can turn it on, leave it on a table, idle without anything running, and it'll be completely room temp and the part of the screen stops responding.
I'll give them a look over, hopefully reseating connectors may help
Click to expand...
Click to collapse
Could be literally 100s of thousands of parts that could have failed; semiconductor junctions, resistors or caps.
Solder failures aren't uncommon either.
If you spare parts, use the process of elimination. If you really like that model having a few parts queens around is a plan.
Hopefully it's a connector contact... check all connections including grounds.
For $650 you can get a Note 10+ 512gb in excellent condition... don't got too nuts trying to fix it.
blackhawk said:
Could be literally 100s of thousands of parts that could have failed; semiconductor junctions, resistors or caps.
Solder failures aren't uncommon either.
If you spare parts, use the process of elimination. If you really like that model having a few parts queens around is a plan.
Hopefully it's a connector contact... check all connections including grounds.
For $650 you can get a Note 10+ 512gb in excellent condition... don't got too nuts trying to fix it.
Click to expand...
Click to collapse
i'm not using this phone, it's my dad's old phone that i just want to mess around with since he put it in a drawer a while ago. I don't really plan on putting much into it. just hopefully get it running well and to **** around with roms on it.
Also $650 still isn't cheap for a phone when you're paying cash outright :v
at least a lot more expensive than a $50 screen replacement or $35 motherboard
YellowSomething said:
i'm not using this phone, it's my dad's old phone that i just want to mess around with since he put it in a drawer a while ago. I don't really plan on putting much into it. just hopefully get it running well and to **** around with roms on it.
Also $650 still isn't cheap for a phone when you're paying cash outright :v
at least a lot more expensive than a $50 screen replacement or $35 motherboard
Click to expand...
Click to collapse
You're my hero... I am not good enough to mess with solders and digging that deep! Good Luck!
YellowSomething said:
i'm not using this phone, it's my dad's old phone that i just want to mess around with since he put it in a drawer a while ago. I don't really plan on putting much into it. just hopefully get it running well and to **** around with roms on it.
Also $650 still isn't cheap for a phone when you're paying cash outright :v
at least a lot more expensive than a $50 screen replacement or $35 motherboard
Click to expand...
Click to collapse
I gave you a top shelf example.
Lots S-10s etc.
There's no guarantee swamping out parts will fix anything. The devil is in the details.
blackhawk said:
I gave you a top shelf example.
Lots S-10s etc.
There's no guarantee swamping out parts will fix anything. The devil is in the details.
Click to expand...
Click to collapse
Fair enough
reseating things didn't help, may see if i can scrounge up an old parts phone or something
YellowSomething said:
Fair enough
reseating things didn't help, may see if i can scrounge up an old parts phone or something
Click to expand...
Click to collapse
Sorry to hear that.
Some devices seem to defy being repaired.
45 years ago Tom Schall owned a TV repair shop. He was an excellent technician with a engineering degree in electronics.
He swapped out a trouble filled Magnavox chassis with a known good one for a customer after repairing the original one at least twice only to have another circuit fail.
After a month he did the swamp but continued to try and fix the original. He repaired completely different sections of it only to have another one fail, HV, tuner, horizontal output, audio, and more.
Never once did it survive a couple days of burn in, sometimes only hours. It got to be a running joke. Hundreds of test point checks, scoped it, testing isolated components pondering how it could be so cryptic to repair. At this point no one else would even touch it... but Tom persisted for at least 3 more years in his spare time.
If there's a heaven or hell I'm sure Tom's still tinkering with that chassis. RIP
They weren't called Magotboxes for nothing
.
YellowSomething said:
So something I noticed on my old note 4 is that the screen has a strip unresponsive to touch (pen works fine).
The thing that weirds me out is that when you reboot the phone, it works perfectly fine, but after being on for a few hours, the middle part of the screen just stops responding.
Rebooting revives the part of the screen, but not for long. Factory resetting it does nothing different and it's running completely stock firmware and software.
Any ideas as to what's causing this? I'm not sure if replacing the screen would help since it seems to work fine for the short duration that it does.
Click to expand...
Click to collapse
See if this works for you, it did for me after i thinking digitser was kerputt.
on Dialler, dial: *#2663#
if a menu comes up, choose the top left option to upgrade the fw for touchscreen, wait for complete, then hit home button and see if it works. Maybe best to try after your screen goes funny, it should fix straight away
thewudz said:
See if this works for you, it did for me after i thinking digitser was kerputt.
on Dialler, dial: *#2663#
if a menu comes up, choose the top left option to upgrade the fw for touchscreen, wait for complete, then hit home button and see if it works. Maybe best to try after your screen goes funny, it should fix straight away
Click to expand...
Click to collapse
That worked at first, but I rebooted the phone and it seems to be doing it again. I tried to update the firmware again, and it's not working. Any advice? It worked fine for over a day without any issue after doing that at first, now it's back to doing it again.
YellowSomething said:
That worked at first, but I rebooted the phone and it seems to be doing it again. I tried to update the firmware again, and it's not working. Any advice? It worked fine for over a day without any issue after doing that at first, now it's back to doing it again.
Click to expand...
Click to collapse
Sorry late reply, I didnt get a notification. It worked for me and I haven't had to do it again, it likely sounds like you have a hardware issue unfortunately.
Only other option maybe, is putting on a custom rom, which will instigate a full system wipe and a new fresh software install to a more modern Android version. Possibly may be worth a shot?
thewudz said:
Sorry late reply, I didnt get a notification. It worked for me and I haven't had to do it again, it likely sounds like you have a hardware issue unfortunately.
Click to expand...
Click to collapse
Alright, update.
i tried again, and it fixed it, but a while later, it did it again. Since that seemed to fix it for a bit, i can't imagine it being solely a hardware problem.
thewudz said:
Only other option maybe, is putting on a custom rom, which will instigate a full system wipe and a new fresh software install to a more modern Android version. Possibly may be worth a shot?
Click to expand...
Click to collapse
honestly, that's the plan as of right now. As much as I like the S-pen features on this, it'd be for the better if it fixes it.
Update, TWRP + new rom installed. Still does it.
With Refined Nougat N7FE, I'm able to open the screen firmware menu from the dialer and update like with the stock rom. It sometimes fixes it for a while, but ends up doing it again.