New to the Note 4 - Galaxy Note 4 Q&A, Help & Troubleshooting

I just purchased my Note 4 (waiting on shipping lol) and was wondering if there are any bugs/glitches I should know about I'm going to be using metropcs's service since it's GSM and unlocked.

Hey there!
Well, I suppose the biggest and baddest thing you should be aware of is that the Note 4 is really, really prone to having the internal eMMC chip fail prematurely. If you're not afraid of that, your new phone is a truly awesome li'l device.
What's this eMMC brick bug? It begins with small lag spikes and ever-increasing delays in response to user input. Then come the random reboots, after which you usually have to remove the battery to get the device back up. The end result is always the same - your phone will be stuck in Odin mode with the mmc_read failed error message. This issue is probably due to a bad batch of eMMC 5.1 chips whose cells seem to age and fail way too fast, and the only permanent fix is a complete motherboard replacement.
Don't get me wrong, chances are that this isn't going to happen to your device - mine is still running smooth and so is almost every other Note 4 on this wonderful little subforum. Congratulations on your purchase and welcome to the community!
-odd

oddbehreif said:
Hey there!
Well, I suppose the biggest and baddest thing you should be aware of is that the Note 4 is really, really prone to having the internal eMMC chip fail prematurely. If you're not afraid of that, your new phone is a truly awesome li'l device.
What's this eMMC brick bug? It begins with small lag spikes and ever-increasing delays in response to user input. Then come the random reboots, after which you usually have to remove the battery to get the device back up. The end result is always the same - your phone will be stuck in Odin mode with the mmc_read failed error message. This issue is probably due to a bad batch of eMMC 5.1 chips whose cells seem to age and fail way too fast, and the only permanent fix is a complete motherboard replacement.
Don't get me wrong, chances are that this isn't going to happen to your device - mine is still running smooth and so is almost every other Note 4 on this wonderful little subforum. Congratulations on your purchase and welcome to the community!
-odd
Click to expand...
Click to collapse
Ahhhh, ok. I'm not too worried about that. But I do have good luck with phones (not with my last one, the S5, but that wasn't my fault .. probably something the previous owners did to it) though. I'll keep my fingers crossed. It's a refurbished one, with a 60 day warranty, so hopefully nothing goes wrong.

Related

My experience between two devices

So I will start by saying I'm a very picky person when it comes to devices I own. Keep that in mind as you read through this.
I ordered my first nexus 6 On 12/26 and received it on 1/2. Great shipping time considering the holidays and weekend in between! I was so excited when it arrived, but had some immediate concerns, not all that different than some here have expressed. I had the two toned screen where the bottom was much warmer than the top. I also experienced significant lag in some games, and it was more than the coding of the games. How do I know you ask? Well, that's where my second nexus 6 comes into play. I sent the first one back within the 14 day return period and ordered a second from Motorola. The second arrived just as quickly, and to my liking, the screen had a nice uniform, although very warm color. I downloaded a few of the same games I was experiencing the lag in, and holy cow this was night and day different. A lot of folks have pick on coding for Madden Mobile. While that may be true, it played at least as good on my second nexus 6 as it did on my nexus 5 and HTC M8...if not better! Of course though, there had to be something wrong right?! Well, my second nexus 6 has the worst sounding vibration motor I've ever heard! My M8 had a bit of a loose rattle when haptic feedback was on, but this thing sounds like the vibration motor is about to break through the screen and take out an eye! On the first nexus 6 it was perfect. So back goes number two. I love using haptic feedback when typing.
The problem now is that no one has any available, and I want to get it back this week while I can, so fingers crossed that Google Play or Moto get some stock in by Wednesday. I'm going to try one more new one from either of those sources. If number 3 arrives with similar issues, it'll be off to a new device.
Anyway, sorry to rant. I just figured that since some others are seeing some of the same problems I've had, that my experience may help others understand what they should expect from the mystical perfect nexus 6.
Have you seen the memory thread? http://forum.xda-developers.com/nexus-6/general/nexus-6-internal-memory-chipsets-t2955045
Would have been interesting to see what the memory differences were between the two phones
If you still have your second phone you might want to see what it has and compare it to phone #3
Cheers
SP_Kenny said:
Have you seen the memory thread? http://forum.xda-developers.com/nexus-6/general/nexus-6-internal-memory-chipsets-t2955045
Would have been interesting to see what the memory differences were between the two phones
If you still have your second phone you might want to see what it has and compare it to phone #3
Cheers
Click to expand...
Click to collapse
Yep, I did take a peak at that thread early on, but haven't kept up with it. My first phone was:
eMMC = Samsung
DRAM = Hynix
This one is
eMMC = Sandisk
DRAM = Samsung
JHadley said:
Yep, I did take a peak at that thread early on, but haven't kept up with it. My first phone was:
eMMC = Samsung
DRAM = Hynix
This one is
eMMC = Sandisk
DRAM = Samsung
Click to expand...
Click to collapse
Nice - good job on saving that information :good:
Will have to see what you end up with for memory and performance with #3
I ended up with eMMC - Sandisk, DRAM - Hynix. I do not game on my phone so I cannot comment on performance there but I am happy with overall performance of daily usage
As noted in that thread it seemed Motorola just reached into a bag of chips and threw them at the phone, whichever ones stuck is what it got
SP_Kenny said:
Nice - good job on saving that information :good:
Will have to see what you end up with for memory and performance with #3
I ended up with eMMC - Sandisk, DRAM - Hynix. I do not game on my phone so I cannot comment on performance there but I am happy with overall performance of daily usage
As noted in that thread it seemed Motorola just reached into a bag of chips and threw them at the phone, whichever ones stuck is what it got
Click to expand...
Click to collapse
64gb white, stock, non-rooted
eMMC-Sandisk
DRAM-Hynix
Gaming is terrible, simple game of wsop texas holdem lags compared to my nexus 5, don't know if i should return/exchange the device due to the lag
psak said:
64gb white, stock, non-rooted
eMMC-Sandisk
DRAM-Hynix
Gaming is terrible, simple game of wsop texas holdem lags compared to my nexus 5, don't know if i should return/exchange the device due to the lag
Click to expand...
Click to collapse
That's a tough call man. I've contemplated keeping the one I have now because the vibration motor is my only issue, but I feel like there is a perfect one with my name on it somewhere. No guarantees though.
I can pretty much guarantee that the "who made the chip" game is meaningless. All the chips used in everything meet the same specifications. More likely there is some other variable at play, like perhaps the software (game) was updated between phone #1 and phone #2.

HTC M9 overheats and throttles...

http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Applesexual said:
http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Click to expand...
Click to collapse
By all means, make up your mind based upon a blog's first-hand experience with a prerelease ROM and kernel.
Just sayin'.
And also phone is connected to charger
Applesexual said:
http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Click to expand...
Click to collapse
Perhaps you would be more enlightened/discouraged by reading about the exact same issue with the S6 HERE
In both cases, these are both devices running "bragging" ROM versions for MWC and also running a synthetic benchmark that is often derided as "non-representative" of reality.
Either way, I wouldn't be tempted to draw any conclusions yet. Early adopters pay over the odds in financial and ROM stability/performance terms.
odd move basing your buying decision on a phone thats being used constantly pre released and being charged at the same dam time smh
And all this is based on the fact that some would-be tech journalist from Romania tried to do some benchmark tests on a phone with non-final software on it and that has been on the charger for two-three days continuously, with its screen lit up most of the time and that has been played with by hundreds of people ... Let's be patient a little and wait for a test when the whole package is actually finished and shipped out for real reviews.
Applesexual said:
http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Click to expand...
Click to collapse
I had the same msg on my note 3... notting to worry about.. if your phone is at 57C, you'll see that msg in antututu if you want to benchmark
This should pretty much sum all this bafoonery up
Applesexual said:
http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Click to expand...
Click to collapse
Read this, kind of lengthy but very well written.
http://semiaccurate.com/2015/03/02/behind-fake-qualcomm-snapdragon-810-overheating-rumors/
Applesexual said:
http://androidheadlines.com/2015/03...-one-m9-running-antutu-benchmark-app-mwc.html
Well, time to go for the S6.
Click to expand...
Click to collapse
Even if this is true would rather have a heating phone than a glass back phone with no microsd and running sampoop software that never updates still waiting for lollipop on my Note 4 worse decision ever trying samsung again I've never had a good experience with samsung u can have all the nice specs but you need software to back it up all htc's are currently updated to lollipop and should we talk about the bootloader easily unlockable does anyone remember the fact it leaked samsung paid people to give bad reviews on phones they have alot of money to throw around best is to try the phone yourself thats what the 15 day return policy is for
nabzilla1990 said:
Even if this is true would rather have a heating phone than a glass back phone with no microsd and running sampoop software that never updates still waiting for lollipop on my Note 4 worse decision ever trying samsung again I've never had a good experience with samsung u can have all the nice specs but you need software to back it up all htc's are currently updated to lollipop and should we talk about the bootloader easily unlockable does anyone remember the fact it leaked samsung paid people to give bad reviews on phones they have alot of money to throw around best is to try the phone yourself thats what the 15 day return policy is for
Click to expand...
Click to collapse
Couldn't make sense of your point as there was no punctuation...I have tired head now.
Even if so, samsung would be the last company I turn my head to if I leave HTC (after apple that is, but goes without saying)
I thought this was a joke. The same post is in the Galaxy S6 forum.
Anywoot, simple solution to overheating. Custom kernel and undervolting.
watched this video https://www.youtube.com/watch?v=Eqez7e5JTcU running benchmarks side by side and no overheating warning popped up on either phone.
Overheating on a demo phone that probably has the screen on for hours on end and is tethered into a charger...yeah that makes sense
Yes indeed.. Antutu already alarms when your phone is at 58C... Screen and charger always on, a lot of people play with it and run benchmarks.. not so strange it's going to be around 60C and antutu gives a warning..
Even the S6 will do exactly the same in that situation. I've had it also with my Note 3, when on charger
Not a big fan of Samsung's take on Android (TW) and I know benchmark results are not always reflective of real world performance. However, these results look pretty darn good for the S6 devices. Seems like some good optimization work has gone into these devices. S6 is pushing a lot more pixels.. don't know how the tests are affected by that.
TwistyValhalla said:
Not a big fan of Samsung's take on Android (TW) and I know benchmark results are not always reflective of real world performance. However, these results look pretty darn good for the S6 devices. Seems like some good optimization work has gone into these devices. S6 is pushing a lot more pixels.. don't know how the tests are affected by that.
Click to expand...
Click to collapse
Optimization... On Samsung! Pufffth. It was evident in previous cases that the Note 3 had cheated on bench marks. I'm not saying HTC hasn't cheated either, but just something to realize that benchmarks aren't everything and can be easily fabricated with some from of performance setting (i.e. higher clocks or performance governor).
My insights below. Maybe biased in the eyes of Samsung
After owning both the One M7 and S5 - I had a better experience on the m7 and the screen on the Samsung is very thin that it broke after I dropped it on the ground. I personally see a lot of people with broken digitizer's on the bus and this is probably why. In my case, my next phone will either be a Sony or a HTC. If you guys are wondering if warranty protects against this, it doesn't unless the phone's digitizer doesn't respond at all that means I'm not covered by warranty at all. Something to realize when buying any from of warranty.
that is inevitable, cortex A57 is a big and hot core

eMMC Failure

After updating to 6.0.1 (Alexandar rom - which is pretty much stock + TW) from the 5.1.1
- worked ok for 1 week but used to get constant freezes and reboots
- suddenly one day - it became unbearable
- came up with eMMC failure
- could not flash with ODIN
- would boot up occasionally - but then after a few hours would go into download mode showing ODIN failure with eMMC write failure.
- Occasionally would flash new rom and would work - struggled with this for a couple of weeks, but needed constantly taking out the battery and keep pressing the power button.
- tried multiple factory reset, erasing the SD card, changing sim etc etc etc.....
- Tried PIT flashing - failed a few times, but ultimately went throught -> phone was pretty much useless, constant reboots
- was nearly giving up - thinking it would be a NAND failure
I realised that after installing stock rom with android recovery - it used to function properly. Once TWRP was installed, it would become slow and get random reboots and freezes.
Installed latest firmware using Kies - 6.0.1; phone seems to work a lot better.
Using odin - reflashed stock 5.1.1, rebooted and then installed TWRP - everything seem to work smoothly!!!
Installed Alexandar ROM ver 2.7 - phone is back to smooth functioning.
has anyone faced similar problems??
Sounds like it a problem with TWRP. Have you tried installing the latest version of TWRP on your device?
DarkGuyver said:
Sounds like it a problem with TWRP. Have you tried installing the latest version of TWRP on your device?
Click to expand...
Click to collapse
Yes - same with all old and new versions
Post wrong..delete...thz.
I had the same problem.. Contacted samsung and they swap my mainboard...
I think you have contact samsung for it..
Yes I've gone through 2 note 4s so far. And people complain about lg. Second one failed today. The emmc lasts about a year then dies at the exact October
My God! This news are scary! Same happened with Note 3 for me. If this happens with this one too then I am out of Samsung for good.
same here...after exactly two years. BOOM. emmc boot fail. I'm out of guaranty now.. and now my phone is at a center specialized care who will try to regenerate the motherboard without replacing it
same, emmc failure ratio seems to be quite high with note 4s
09mysh said:
same, emmc failure ratio seems to be quite high with note 4s
Click to expand...
Click to collapse
I wonder if one could replace the faulty chip on the mainboard...have 2 Note's, a third in spares with a faulty mainboard and another good replacement mainboard in case one of the our good note's may need them!
Came across this on my S3 where overnight I lost all data as the mainboard failed. Still cannot get my head around that a giant company like scamsung can continue producing crap like this and getting away with it.
They even have the nerves to ask prices at the same insane level as the gay-phones.
Who's willing to fork out 650€ and plus for a device like this and a year later its main memory chip fails?!
The only reason I am hanging onto my Note 4 is for the S-pen function. My Lenovo Zuk1 performs equally if not better than the flagship Note 4 and has only cost me around 200€...does not have the S-pen but come with dual SIM. I will never buy a new Samsung if I ever buy another Samsung, lots of cheaper alternatives that do the job equally.
edit. Sorry I misundersood your post, but I am leaving my reply as it is. Yeah it is sad when you pay so much for a phone and it fails after 2 years when the warranty is gone : (
I think the replacement of emmc can be done by skilled professional (only). You can buy emmc chips, but that would be very difficult repair. This is why changing the whole mobo swap is the most popular solution. Btw, I thinking about buying chinese n9100 mobo with dual slim slot. It is probably the cheapest you can get and it looks like maybe it would fit in n910x, maybe somebody can confirm this.
edit2
There is quite a lot of N4s with this issue on ebay nowadays, people buy them thinking they will root it, flash a cool rom and it will work flawlessly. Just another thread http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821
You are right...bought one of them with a "non working" display on ebay. Display remained black, on reboot the blue light would come on including audio...phone was recognised when connected to my laptop. Replaced the display only to confirm the mainboard was ready for the bin. There are several similar listings with so called broken displays while in reality these phones have mainboard issues...I stay well clear from Note 4's now, mine is not even 6 months old while the Note 4 from my wife is now 1.5 years old. Guess that's the one who will benefit first from my "spare" mainboard although I am not sure if the N910P ( American models) are affected as the N910F.
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI

Some Nexus 5X devices are getting stuck in bootloops after upgrading to Android 7.0

http://www.androidauthority.com/nexus-5x-android-7-nougat-bootloop-issue-717698/
So I read this article back on September 21st and thought, "Well I've been using 7.0 since it was N Preview 3 and upgraded to final release just fine. I should be good." Then two nights ago while I was just browsing online, it happened to me and I got an endless bootloop. Mind you, I am totally stock and unrooted (Support does ask if you are by the way) which is a first for me as I usually ended up rooting and customizing my previous phones. All I saw was the Google logo for 5-10 seconds, then it turn off, back to the logo, and repeat. I followed the trouble shooting steps to clear the cache and the factory reset. At first I couldn't even get to those options but letting the phone rest in power off for a few minutes fixed that. But it's still bootlooping on me. Good thing Google's customer support is 24/7, I'm within my 1 year warranty (Purchased Sept 2015 but didn't receive and activate until end of Oct 2015), and I'll be receiving my free replacement in the mail in the next few days.
Only "issues" are I'm going to lose my Ice Blue color and will be getting a black one, I splurged for the expedited shipping ($18.99 which I don't think they'll cover), and it'll be a little bit as it's 1-2 days for processing and 1 day (hopefully) shipping. They do put a hold on my credit card for the total price which they remove once the old phone gets shipped. I have 14 days to ship the old one which they do provide shipping and packing slips for free. That makes sense someone could try to lie and scam to get a free phone without some kind of collateral.
Overall, I was pretty satisfied with the support I got and was really tempted to splurge on the Googe Pixel and pay $27/month prior to this happening. But with this replacement, I'm hoping that my original unit was defective in performance (That's what comments would say) as it slowed down way more than it should on things that would be pretty simple especially websites. Guess I'll wait for the Pixel 2 next year.
Update:
Looks like the expedited shipping was covered by them. The hold was removed from my credit card and no shipping charge remaining.
EeZeEpEe said:
http://www.androidauthority.com/nexus-5x-android-7-nougat-bootloop-issue-717698/
So I read this article back on September 21st and thought, "Well I've been using 7.0 since it was N Preview 3 and upgraded to final release just fine. I should be good." Then two nights ago while I was just browsing online, it happened to me and I got an endless bootloop. Mind you, I am totally stock and unrooted
Click to expand...
Click to collapse
IMO the original information from the Google reply is confusing. In the context they were answering it makes it seem like the hardware problem is between 7.0 and the hardware. IMO the hardware problem is actually eMMC that is close to failing and it could have happened on MM as well (there have been sporadic posts of this happening since release). So Google is right, it is a hardware problem, but the implication that it is related to Android 7.0 and you'd be all safe with 6.0.x is IMO deceptive.
sfhub said:
IMO the original information from the Google reply is confusing. In the context they were answering it makes it seem like the hardware problem is between 7.0 and the hardware. IMO the hardware problem is actually eMMC that is close to failing and it could have happened on MM as well (there have been sporadic posts of this happening since release). So Google is right, it is a hardware problem, but the implication that it is related to Android 7.0 and you'd be all safe with 6.0.x is IMO deceptive.
Click to expand...
Click to collapse
Well hopefully there was an eMMC fix with the one I just received today. Let's see how it performs for me.
EeZeEpEe said:
Well hopefully there was an eMMC fix with the one I just received today. Let's see how it performs for me.
Click to expand...
Click to collapse
If it was manufactured later (or a refurb) there is at least the possibility the eMMC chip might be of different batch, but if it was manufactured back in 10/2015 timeframe, I doubt Google knew about the problem back then so there would be zero chance it has some newer eMMC chip. Even if it was manufactured after that there is no guarantee they knew about the problem and made a manufacturing change.
I don't think it is a highly prevalent problem, but it occurs more than what is usual with phones. There are plenty of 5x's which don't experience the problem. You will probably be fine.
IMO these eMMC chips that they used have a higher failure rate than normal but probably is still a low absolute number relative to number of phones sold. It doesn't take that many posts about permanently bootlooped phones to make it seem like an epidemic when it might not be when looking at the overall picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well if this fails again within 1 year I'll take another replacement. LOL. Probably sell it at that point and put it towards whatever Google is out with then.
Sent from my Nexus 5X using Tapatalk
It is possible it might be some different hardware defect with solder joints rather than eMMC chip itself. Just a working theory that the 5x may suffer a hardware problem acknowledged for its cousin the LG G4
http://forum.xda-developers.com/nexus-5x/general/5x-bootloop-cause-fix-t3476794
So after a good 3 days of use, I can say my original release day 5X probably did have some kind of defect. It's amazing how much smoother my replacement has been and I haven't changed my apps or usage. There are times of delay and lag here and there but not to the point where it wasn't usable like unscrollable web pages or non-responsive back, home, recent apps buttons like my old phone. Eventually it will catch up and things go back to working smoothly without the need to restart the phone. I should've requested a replacement months ago! I just didn't believe people when they said it was defective and I don't realize how easy and quick it was to get a replacement. Oh well.
Sent from my Nexus 5X using Tapatalk
I must say this thread is quite quiet...
Mine died a week ago while traveling.
It was actually running 7.0 for quite some time. but I think it's eMMC failing because the only major change I had was doing more videos in 4k (that sometimes stuttered).
Then one morning without warning it rebooted and died.
Hope they'll replace it as my purchase date was 10/9 ...
However, I'm afraid there's a defect similar to the G4 one because it seems very similar.
Also as written above, might be related to the reports of some users as I had prior to 7.0 betas of lags. my device felt really laggy when I first bought it.
What's your S/N number?
Happened to mine five days ago. Sent to repair (Norway) but got a New one anyway. To hard to switch phones after years on nexus. Got a New OTA update just now, related?
I sent mine in to LG after it randomly shut down and bootlooped using maps. They reported this issue was with the flash memory, so everyone saying the eMMC is likely correct.
Sent from my XT1058 using XDA Free mobile app
S/N: 510KPCA...
H790
Manufactured: 10/2015
Is the nougat bootloop problem will be resolved by google? I have Nexus 5x 32gb (h791 international version, manufactured 10/2015) with 6.0.1 and I'm too afraid to upgrade to 7.0 because officially Nexus 5x is not available in my country although there's LG smartphone service center here (I bought it online and let's just say it's virtually without warranty).
EeZeEpEe said:
Update:
Looks like the expedited shipping was covered by them. The hold was removed from my credit card and no shipping charge remaining.
Click to expand...
Click to collapse
This was my experience as well. I had an earpiece speaker die in my 5x, so I would have gladly paid the $19 anyway, but much to my surprise, I didn't have to. Very glad I bought the phone through the Play store now, the support and exchange process was excellent.
innov said:
Is the nougat bootloop problem will be resolved by google? I have Nexus 5x 32gb (h791 international version, manufactured 10/2015) with 6.0.1 and I'm too afraid to upgrade to 7.0 because officially Nexus 5x is not available in my country although there's LG smartphone service center here (I bought it online and let's just say it's virtually without warranty).
Click to expand...
Click to collapse
There's kind of a debate going on as to whether it's really the update or if it's an eMMC hardware issue.
Sent from my Nexus 5X using Tapatalk
The only reason I think it's eMMC or at least the connection with it is:
- My recovery won't always load also.
- TWRP would also freeze even if I try to boot into it without flashing it.
- I've flashed factory image without wiping data. result: It did boot once but got stuck and reboot after few minutes of hiccups.
- It freezes in different parts when loading.
- My device worked well for a long time with 7.0. more than a month / since the first day the 7.0 OTA from the 7.0 beta was out...
- I saw some hiccups few days before it died randomly when shooting 4K videos. felt like dropouts.
(placebo: my device was sluggish with 6.0 and 7.0 beta actually made it functional. with 6.0 I was quite disappointed with the performance).
ttg said:
The only reason I think it's eMMC or at least the connection with it is:
- My recovery won't always load also.
- TWRP would also freeze even if I try to boot into it without flashing it.
- I've flashed factory image without wiping data. result: It did boot once but got stuck and reboot after few minutes of hiccups.
- It freezes in different parts when loading.
- My device worked well for a long time with 7.0. more than a month / since the first day the 7.0 OTA from the 7.0 beta was out...
- I saw some hiccups few days before it died randomly when shooting 4K videos. felt like dropouts.
(placebo: my device was sluggish with 6.0 and 7.0 beta actually made it functional. with 6.0 I was quite disappointed with the performance).
Click to expand...
Click to collapse
It is definitely a hardware problem.
In many cases eMMC is involved.
It is unclear whether the chip is failing or the solder joints are failing.
LG has acknowledge a defect with the LG G4 (cousin of 5x) where the solder joints were failing.
There are videos showing heating the chip using SMD hot air rework station can restore functionality on a LG G4. I don't know of anybody who has tried same with 5x.
Given there were reports of phones on Marshmallow just rebooting in the middle of seemingly innocuous things like texting and then being stuck in a bootloop with all stock software, locked bootloader, IMO Android 7 has little to do with the problem and it is mostly coincidental it happens after an update. It is possible Android 7 runs the CPU a little more and maybe that exacerbates a solder joint problem for some phones, but the core problem would still be solder joints as melting point of lead-free solder is quite high (220C/428F)
ttg said:
(placebo: my device was sluggish with 6.0 and 7.0 beta actually made it functional. with 6.0 I was quite disappointed with the performance).
Click to expand...
Click to collapse
7.0 helped a lot with my old device but my replacement is way better than my original ever was.
sfhub said:
It is definitely a hardware problem.
In many cases eMMC is involved.
It is unclear whether the chip is failing or the solder joints are failing.
LG has acknowledge a defect with the LG G4 (cousin of 5x) where the solder joints were failing.
There are videos showing heating the chip using SMD hot air rework station can restore functionality on a LG G4. I don't know of anybody who has tried same with 5x.
Given there were reports of phones on Marshmallow just rebooting in the middle of seemingly innocuous things like texting and then being stuck in a bootloop with all stock software, locked bootloader, IMO Android 7 has little to do with the problem and it is mostly coincidental it happens after an update. It is possible Android 7 runs the CPU a little more and maybe that exacerbates a solder joint problem for some phones, but the core problem would still be solder joints as melting point of lead-free solder is quite high (220C/428F)
Click to expand...
Click to collapse
Yeah I think it's probably just coincidence that Nougat was released and eMMC failures were happening around the same time.
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
7.0 helped a lot with my old device but my replacement is way better than my original ever was.
Click to expand...
Click to collapse
Do you remember if you ever looked to see whether your "big" cores (CPUs 5 & 6) were often disabled?
I am wondering if a solder joint problem can sometimes manifest itself in CPU operating in degraded condition where it doesn't run the "big" cores as often or at all.
I noticed on a friend's 5x, it was always running hot for some reason, which triggered a thermal safety measure where the "big" cores are disabled. Whenever the 5x is in that condition, it runs very sluggishly, but once the phone cools down, it goes back to running normal/fast.
It would be funny if alot of the complaints about the 5x being sluggish ended up being because of bad solder joints. Then the people that reported sluggishness would be correct and the people who reported things being snappy were also correct, the former really just had hardware defects, but not the obvious type.
sfhub said:
Do you remember if you ever looked to see whether your "big" cores (CPUs 5 & 6) were often disabled?
I am wondering if a solder joint problem can sometimes manifest itself in CPU operating in degraded condition where it doesn't run the "big" cores as often or at all.
I noticed on a friend's 5x, it was always running hot for some reason, which triggered a thermal safety measure where the "big" cores are disabled. Whenever the 5x is in that condition, it runs very sluggishly, but once the phone cools down, it goes back to running normal/fast.
It would be funny if alot of the complaints about the 5x being sluggish ended up being because of bad solder joints. Then the people that reported sluggishness would be correct and the people who reported things being snappy were also correct, the former really just had hardware defects, but not the obvious type.
Click to expand...
Click to collapse
I never did check how the cores were running but I did have a widget monitoring the temperature and would notice pretty high spikes. That last statement you made is the exact situation I was in. I guess I would rather have a sluggish performance defect than a burning battery one. LOL
Sent from my Nexus 5X using Tapatalk

Can my Note 4 explode?

I'm using a ROM based on the Note 7 software. Exactly this one -> [N910G/F/T]Norma V6/ Aurora V3 N7 full Ports
But today i have read that Samsung still doesn't know what causes Note 7 devices to explode.
Outside experts have pointed to a range of possible culprits, from the software that manages how the battery interacts with other smartphone components to the design of the entire circuit.
Click to expand...
Click to collapse
Source: http://www.wsj.com/articles/the-fatal-mistake-that-doomed-samsungs-galaxy-note-1477248978
Should i really care? If its software, my Note 4 can also explode, right?
explode
That's a good question!! I also wonder whether the note 7 software it is good for our hardware Note 4 .Maybe other people who know something?
Well, in terms of software I believe the part of it for the battery load etc. is not part of the android os. It should be independent like a bios.
Anything else would be a problem, because if the OS is not running, nothing else will work
Yes, your Note 4 can explode, as with any phone with a Lithium Battery can.
I doubt the Note7's exploded due to software, or if it was software it would have to have bad hardware accompanying it.
Our phones have all sorts of sensors and power management chips that work to prevent overheating beyond what the components can handle.
via Galaxy Note 4 +128GB MicroSDXC
If your battery is faulty yes there is the possibility that your device will exploded. But if the battery is fine, then you are OK!
If you tie a quarter stick of dynamite to it, it will. LOL.
OK, let's be serious,
I also pondered this question, even though they say they don't know, I find it hard to believe that software can do that without faulty hardware. Also the parts of the OS that are being ported to run on our device is just cosmetic (UI, apps). It doesn't change the way your phone charges and such. I do believe that's all handled by the kernel or bootloader.
Someone can correct me if I'm wrong.
Plus I notice from running these Roms, my phone doesn't get any hotter than normal. Only thing I've noticed make my phone hotter is having a different kernel installed.
If it was anything to do with software that would've been the one thing Samsung could have dealt with precisely. Nothing to do with software.
Every phone with lithium battery can explode, but it's highly unlikely especially since Note 4 has a removable one. Some say that since Samsung made the Note 7 so compact and cramped inside, it causes the cathode and anode to meet with the slightest bend or so. So, avoid thin phones. Btw, more and more Samsung explosions are being heard, lately the S7 Edge. I think there's a conspiracy behind this, LOL.
I think the explosion thing is just a fabricated thing. Millions in Europe are still using it but since Samsung stopped production, have you guys heard of any explosion? Just asking.
kumuyi said:
I think the explosion thing is just a fabricated thing. Millions in Europe are still using it but since Samsung stopped production, have you guys heard of any explosion? Just asking.
Click to expand...
Click to collapse
LOL! Unbelievable! These corporate conglomerates are one of the filthy things of this world. So when they have stopped production of the unit, send OTA update for limiting battery charging to 60% and sorts, they are more than scared about it, and obviously they officially acknowledge the problem, the hardware defect.
Jeez!
Lol. The problem on note 7 which exploding the device isn't from software.. it was hardware issue...
felixjet said:
I'm using a ROM based on the Note 7 software. Exactly this one -> [N910G/F/T]Norma V6/ Aurora V3 N7 full Ports
But today i have read that Samsung still doesn't know what causes Note 7 devices to explode.
Source: http://www.wsj.com/articles/the-fatal-mistake-that-doomed-samsungs-galaxy-note-1477248978
Should i really care? If its software, my Note 4 can also explode, right?
Click to expand...
Click to collapse
I am preety sure our note 4 is not water proof but i am definitely sure that note 4 is fire proof
@ithehappy come on bro, according to sources they haven't discovered the cause yet
Since the issue was battery (hardware) related, rom itself can't make your phone explode.
Even if it was software related, It still can't happen. We would needed direct port of note 7 kernel (with faulty charging rates), which is impossible.
Yeah...good luck getting Samsung to share that
~N.A.W.Y~ said:
Since the issue was battery (hardware) related, rom itself can't make your phone explode.
Even if it was software related, It still can't happen. We would needed direct port of note 7 kernel (with faulty charging rates), which is impossible.
Click to expand...
Click to collapse

Categories

Resources