Hello there!
I'm having problems with this device, the Mi 10 Lite 5G (Monet) in particular.
Out of nowhere it started having an insane battery drain. To the point that if i unplug it from the charger before i go to sleep so the phone starts at 100% battery, when I wake up between 6 and 8 hours later, I find it at 30 to 50%, at an average of 7-8%/h.
I'm on all stock: latest MIUI, no bootlocker unlocked, no root, ironically I chose this device 'cause i didn't want any headaches.
Remembering my olden modding days, I remembered about the wakelock hunts, so that's the first thing i thought about. I tried multiple apps to do so and even the Battery Historian tool via a bugreport. Everything points to some kernel wakelocks that pretty consistently activate, not letting my CPU sleep at all, which makes sense as to why It would drain battery like that. The problem is I can't figure out what causes it. There's no app that does it, it seems to be all kernel stuff, I even factory reset and tested without installing anything. Either it's something with the system itself, that I can't quite pinpoint, or i'm starting to think it might be hardware. I don't wanna sway anyone, but my best bet is it could be a faulty usb-c charging port. Although I don't know how it could make it this bad, and I'm obviously not sure it even is it. Would suck to change it, spend money on it, and still have the problem.
Aside from the wakelocks, there's also another bit of info that makes me think that: when off, if i plug the usb cable in to charge it, the phone doesn't get to the battery charging animation, but it keeps showing me the Xiaomi logo screen, over and over. I haven't tested if it actually charges in the background or not, for fear of making things worse.
I even checked if there was something weird in the hidden battery stats by dialing the code *#*#6485#*#*, but aside from the phone going into "sink attached" mode at random intervals, which apparently means it's trying to provide charge to something else through the port or wireless charge (that this phone doesn't even have)...? I can't tell if there's anything weird with it or not.
I know my way around android a little bit, but I'm a little bit lacking when it comes to intricate information like this, and I couldn't find any information about this (these) particular wakelock(s) and everything else around 'em.
I'd really appreciate it if someone who knows this kind of stuff better than me could help me out with it. Even just to know what the problem is and there's no real solution.
I'll attach a couple screenshots from Battery Historian (my phone's been factory reset, so I have no apps on it, and don't plan on putting any on aside from the ones I absolutely need, in case I have to send in in for repairs, or root/mod it to try and mitigate or solve this) and alsothe bugreport itself, in case someone needs to look at it in detail to try and sniff out the problem.
Also, if this wan't the right place to post this, let me know. I went for the device, but maybe there's a better section to more in general help with these types of issues, but if there is i couldn't find it.
{
"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"
}
Thanks in advance to anyone who even only just thinks about helping me out!
EDIT: For anyone reading this, the problem was indeed a broken usb-c port/module. I bought a replacement and swapped it out myself and my battery is back to being perfect. Well, almost perfect... This quickly discharging business has lowered its health obviously.
I suspect some sort of short would make my phone believe something was continously being inserted and removed into the usb port, so the CPU would keep being woken up, and kept consuming extra power to try and read something off of it.
I hope this helps someone!
From what I can tell there is no problem. The battery is being consumed at a normal rate by the cpu, wifi and Bluetooth. If you're not using them just deactivate them.
Check the USB port for fluff etc stuffed deep down by repetitive compacting. Use something pin like but not metallic to scrape any foreign objects out.
shivadow said:
From what I can tell there is no problem. The battery is being consumed at a normal rate by the cpu, wifi and Bluetooth. If you're not using them just deactivate them.
Check the USB port for fluff etc stuffed deep down by repetitive compacting. Use something pin like but not metallic to scrape any foreign objects out.
Click to expand...
Click to collapse
While it does appear that it is being used normally, that graph stays the same if i turn everything off, either through airplane mode or by manually disabling wi-fi, bluetooth, GPS, or anything else. I can't turn off the CPU, so there must be something that keeps it up and running for no reason while it should instead be sleeping, and I can't for the life of me figure out what it is. Which is why i think it might be hardware.
I will do the deeper cleaning operation as soon as I can get my hands on a pin-like object small enough that's not metal. Everything i have is either slightly too big to reach more than just the surface of the port, or thin enough but metallic.
Related
Hi folks!
I tried to search the topic before starting a new thread but I couldn't find any.
So, here's my problem. I noticed that since I flashed the stock JQ1 Gingerbread from chainfire's thread apart from everything else being fantastic, the battery use statistics in Settings -> Status -> Battery Use I can see are stranger and stranger.
First I have noticed that my the battery usage of Display had frozen to 2%. It is completely impossible, comparing it to the Froyo before, where it often went beyond 50 or even 60% of total battery usage.
Then, I saw that the Android System was taking about 90% of the stats. At first I thought it may be the infamous Gingerbread battery drain. It is not that, however, because I do not feel the battery draining any faster than before.
Then came the realization that no matter what application I am running, it does not get reflected in the Battery Use - only Android System percentage grows bigger. The funny part is that from time to time the total of all percentage goes beyond 100%
And, finally, today I unchecked the background update of the PULSE application, because I do not really use it and checking the Battery Use again what did I see. See attachment:
{
"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"
}
Not only the display category had gone away totally, but half of the battery usage is now transferred to PULSE, which I don't use.
Please, do you have any ideas how to repair that?
I am on a European Galaxy Tab, JQ1 2.3.3 Android + CF-Root v3.3 for JQ1
Not anyone experiencing the same problem? Just a little update from me. I read half the cloud already, strange but it is the first time that I cannot really find my topic in Google.
I tried what not - no result. I wiped battery stats, which only helped to the extent that the PULSE has gone from battery use stats, and display is back but the readings are stuck at 2% no matter how much I am actually using the display.
I read somewhere that it could be the kernel, where some thing may have not been allowed or switched on??? But if that was the case I would not be the only one with the same problem, but all the people that have flashed the ROM + CF Root 3.3 from chainfire's thread????
Still no ideas?
Hey guy,
Once ago I had the same problem. I don't think that pulse realy eats your battery. But we all know that the battery statistics is incorrect. So don't worry. Do use "AntTek App Manager ☆ root" (its free) to remove the puls app and wipe the cach. Or just install the overcome rom. It's much better then the Sock Rom. Trust me Because after removing of puls, there are other false statuses. I don't remember but i think it will show you that the battery is eaten by the core apps for more then 70%.
Sorry guy... I know about my terrible english
Hey odysseus84,
don't worry about your English. I am glad that you tried to be helpful. It is not that bad. After all I understood what you mean. You are right, even without Pulse in battery stats, I am still missing statistics for practically everything.
It is interesting that the Battery Use fails to record third party apps. As you can see below, the usage for all main system processes like Idle, Standby, Bluetooth, Wi-fi, Voice Calls are there. The statistics for display usage is stuck at 2% as already mentioned, which is the most annoying part.
Another interesting thing is that everything seems to be put into Android System usage, because normally it wouldn't get more than 10% of the overall battery usage share.
May I ask for other people running Gingerbread 2.3.3 to post their battery stats here?
Look. It's just a Bug. There is "Android System"written but it means the % of the Display. There is "Display" written but it means something else. As you can see on the attached pic we have almost the same "Display" usage.
And the other thing is that the statistics nothing shows with less then 2% usage.
Finally you can just accept it or flash something else.
odysseus84 said:
Finally you can just accept it or flash something else.
Click to expand...
Click to collapse
I really liked that last sentence. It really seems that I am going to just accept things or flash the OVERCOME. From what I read the dev team have done a great job! Thanks.
Will someone help me with if theres anything else safe to disable??
I originally got it because of my battery randomly draining itself (in airplane mode, wifi, data, location, bluetooth all set to off manually - it stll happened).
i havent had that error again yet but i have noticed some weirdness within regular use as well.
would anyone be willing to help me decifer them? There are a few especially that stand out as strange to me.
Pawprints1986 said:
Will someone help me with if theres anything else safe to disable??
I originally got it because of my battery randomly draining itself (in airplane mode, wifi, data, location, bluetooth all set to off manually - it stll happened).
i havent had that error again yet but i have noticed some weirdness within regular use as well.
would anyone be willing to help me decifer them? There are a few especially that stand out as strange to me.
Click to expand...
Click to collapse
Post the results here and let me take a look at them.
A_Bunny said:
Post the results here and let me take a look at them.
Click to expand...
Click to collapse
Actually, since i had posted about this, i did have another random battery drop. So ill include those.
The ones in wakelock detector, that didnt make sense to me was the audio. i had sound off, nearly the whole time. even the games i played, i have the sound turned off within the games themselves, so i dont know where the 41 minutes of audio output came from? Also, what is keyguard? that seemed to have a fair bit of play to it too.
and also, i never use my phone as an alarm, ever. so why is "clock" in red, looking like its indicating lots of use??
I tried to include shots of all of the different categories in wakelock detector. but nothing seems like it would drain the battery quite *that* drastically... even the "awake" stats in the actual battery meter... ive had that show as continuously awake when the screen wasnt on before... that didnt even happen. Im not sure what to do?
Last time it happened, i did a battery pull and no issues for about a month... but im not sure what i can do/change? any advice would be great!
{
"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"
}
The power manager service showing over a thousand runs looks kind of strange too, but im not sure what that means.
ETA Im just noticing now, deleted wake locks, 50585???? why in the world so many?? Is this stats since i got the phone or something? I only installed the detector a couple days ago...
Pawprints1986 said:
Actually, since i had posted about this, i did have another random battery drop. So ill include those.
The ones in wakelock detector, that didnt make sense to me was the audio. i had sound off, nearly the whole time. even the games i played, i have the sound turned off within the games themselves, so i dont know where the 41 minutes of audio output came from? Also, what is keyguard? that seemed to have a fair bit of play to it too.
and also, i never use my phone as an alarm, ever. so why is "clock" in red, looking like its indicating lots of use??
I tried to include shots of all of the different categories in wakelock detector. but nothing seems like it would drain the battery quite *that* drastically... even the "awake" stats in the actual battery meter... ive had that show as continuously awake when the screen wasnt on before... that didnt even happen. Im not sure what to do?
Last time it happened, i did a battery pull and no issues for about a month... but im not sure what i can do/change? any advice would be great!
View attachment 3302098 View attachment 3302099 View attachment 3302100 View attachment 3302111 View attachment 3302112 View attachment 3302113 View attachment 3302114 View attachment 3302115 View attachment 3302116 View attachment 3302117
The power manager service showing over a thousand runs looks kind of strange too, but im not sure what that means.
ETA Im just noticing now, deleted wake locks, 50585???? why in the world so many?? Is this stats since i got the phone or something? I only installed the detector a couple days ago...
Click to expand...
Click to collapse
I have done some research and i think most of the wakelocks your having are caused by audio. If audiofx is on your phone (the default equalizer) you may want to disable that. Also other apps that play music can cause this as well.
A_Bunny said:
I have done some research and i think most of the wakelocks your having are caused by audio. If audiofx is on your phone (the default equalizer) you may want to disable that. Also other apps that play music can cause this as well.
Click to expand...
Click to collapse
I dont want to disable audio entirely though, still need the phone to ring for calls and texts, and the odd time i might watch a video on there. but majority for texts and calls.
Im just looking now, im not seeing anything to do with audio or equalizer within settings>applications. is there somewhere else i should look??
The minutes audio-wise definitely did not match my listening to anything, or even the amount of texts that i got that day. so its out of whack but i dont know why...
maybe ive greenified something i shouldnt have? I played it safe though and if i even wasnt totally sure what it was i didnt touch it.
i did take a few more screen shots though, last night just after i started up my phone, for some reason my battery stats allowed me to go in and look at all the packages involved. i havent gotten it to do that since, but im not sure if those would help? (like, i clicked on "android system" in the battery stats and it opened up a new screen with lists of awake and sleep time and packages. ive never seen it before and ive tried to duplicate it and cant. some fluke maybe? )
i have new, issue specific screenshots. the battery drain started happening, again. in airplane mode, again. it seems to be when in airplane mode and when left inactive for a few hours (i didnt think to look at the deep sleep time in wakelock)
When i googled the kernel wakelock, it says its the modem. but that makes no sense as ive run this rom for a good year before ever having this weird random battery drain... so why would the modem kernel start acting up now???
Then other times my phones behaves like this:
I dont get it. i dont treat it any differently or do anything very different at all... i dont get the occasional dropping thing.
Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Not sure if I'm right...but did you check in settings -> more connection (1st screen)-> looking for devices (2nd) if it is active or not (3rd)?
Sorry for my bad English...I'm Swiss ?
{
"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"
}
Gesendet von meinem SM-G930F mit Tapatalk
Your English beats the heck out of my German.
Yeah, it's called "Nearby device scanning" on the English phones, and I have it turned off.
Also just pulled the new VZW update. Things seem worse now than they were.
Cinco5 said:
Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Click to expand...
Click to collapse
I had the exact same issue with bluetooth battery drain. I posted something about it a while back. I never found a solution. I had to install an app called autobluetooth to turn off and on the bluetooth automatically. I use bluetooth mainly in my car and I use a wireless charger in my car. I set the bluetooth to only turn on while charging and my problem is solved. I drain about 1-2% per hour with the bluetooth off and about 3-4% per hour with it on.
Hope this helps.
Yeah, that wont work for me. Thanks anyway.
I think I am having the same problem since the update when I use my BT at work it's draining get horribly and getting hot. I really don't want to factory reset I just got everything how I wanted.
Sent from my SM-G930V using XDA-Developers mobile app
OK, so I think I found it. I enabled developer mode, and killed the Gattservice under Bluetooth Share. So far, things seem a lot better.
I have no idea which app is enabling that service, so unfortunately, I have to kill it each time I reboot the phone, but I can cope with that. It doesnt seem to affect anything else thus far.
I'll update again in a few hours. I'm only about 6 hours into this test.
Cinco5 said:
Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Click to expand...
Click to collapse
Which is the model of your phone?
I have the exact same issue. It started about a month back for me. I'm on the T-Mobile variant. I saw that Bluetooth share had high usage, so killed it and deleted data in that app. I suspect it might be a BLE app that I use - payrange.
My question is, is there a rooted app, something for Xposed, or any other tweak that would auto shutdown the device if the cpu or battery becomes overheated?
I have a media player that runs Android 6. It’s an Astell & Kern SP1000 with a Samsung Exyons 7 Octa 7420. The CPUs are usually set to max 400-1000 Megahertz. I can keep it plugged in charging all day playing music, downloading stuff without it even becoming warm. But for some reason around 1:00-3:00 am (usually while I’m sleeping) it always becomes very hot. I assume somethings running in the background at night that I shouldn’t of installed. Haha But I’ll deal with that later when I get back home and have my computer to reinstall the OS.
But today I just wanna focus my question on something that would be a failsafe if the CPU or battery becomes overheated.
Thank you in advance to anyone with help.
Julien222 said:
My question is, is there a rooted app, something for Xposed, or any other tweak that would auto shutdown the device if the cpu or battery becomes overheated?
I have a media player that runs Android 6. It’s an Astell & Kern SP1000 with a Samsung Exyons 7 Octa 7420. The CPUs are usually set to max 400-1000 Megahertz. I can keep it plugged in charging all day playing music, downloading stuff without it even becoming warm. But for some reason around 1:00-3:00 am (usually while I’m sleeping) it always becomes very hot. I assume somethings running in the background at night that I shouldn’t of installed. Haha But I’ll deal with that later when I get back home and have my computer to reinstall the OS.
But today I just wanna focus my question on something that would be a failsafe if the CPU or battery becomes overheated.
Thank you in advance to anyone with help.
Click to expand...
Click to collapse
Android has this feature built-in, you don't need an app that does this. Android devices automatically shutdown if it overheats by default, this feature is built-in to protect your device.
Sent from my LGL84VL using Tapatalk
Mine seems to not shutoff when too hot. I even said that in my post as I talked about it becoming way too hot. It’s running normal Android, it’s a very stripped down version.
So, I would appreciate it if anyone had actual advice, thanks.
Julien222 said:
Mine seems to not shutoff when too hot. I even said that in my post as I talked about it becoming way too hot. It’s running normal Android, it’s a very stripped down version.
So, I would appreciate it if anyone had actual advice, thanks.
Click to expand...
Click to collapse
Your device probably isn't getting hot enough to trigger the default shut-off.
Maybe you need to focus on finding the cause of the excess heat.
Sent from my LGL84VL using Tapatalk
The device is a big chunk of copper to help dissipate heat. It’s so hot that I can’t hold it. The CPU normally runs at 36°, if it’s processing something around 48°, when it’s too hot to hold it’s around 80°. So I time it starts going around 75 or higher it becomes too hot to hold.
It seems everyone keeps telling me what I should be doing instead of suggesting or helping me with my question. I think I even stated that I will solve the problem when I get back home and have my computer. So I’m not sure why you are even suggested that because I already told you I would be doing that when I get back home. So if anyone has useful suggestions of things I haven’t already said I would be do, that be great. I would love to have some actual useful information.
{
"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"
}
Julien222 said:
The device is a big chunk of copper to help dissipate heat. It’s so hot that I can’t hold it. The CPU normally runs at 36°, if it’s processing something around 48°, when it’s too hot to hold it’s around 80°. So I time it starts going around 75 or higher it becomes too hot to hold.
It seems everyone keeps telling me what I should be doing instead of suggesting or helping me with my question. I think I even stated that I will solve the problem when I get back home and have my computer. So I’m not sure why you are even suggested that because I already told you I would be doing that when I get back home. So if anyone has useful suggestions of things I haven’t already said I would be do, that be great. I would love to have some actual useful information.
Click to expand...
Click to collapse
Because there isn't anything you CAN do except solve the reason it is overheating.
Apps aren't very good for solving things like this, it's just something else to use battery and create heat, but, you can try the Cooler Master app, it has a feature to cool the device by killing overheating apps, in the meantime, you can manually power the device off if it gets too hot.
Sent from my LGL84VL using Tapatalk
I've had a Galaxy Note 10 Lite for some time now and it started displaying this behaviour where the screen stops working after some time of the phone being on.
There's no apparent connection to how hot the phone is.
I've also re-sat all the straps and cables and cleaned them with isopropyl alcohol.
Sometimes during use, I'll see some quick greenish/purple-ish glitches on the screen. But, apart from that, it'll look amazing the whole time.
Also, sometimes, as I use it, the screen will freeze during whatever is happening on the screen and the image will refresh if I press it down on the 2/4 area from the top down.
Then, if I leave the phone for a few minutes with the screen either on or off, I could come back to it being unresponsive. At first, I thought it was turning off. But if I press the screenshot buttons, it'll vibrate and save the screenshot that I'll be able to see after I soft reset the phone back to life (it'll reboot by itself from time to time, though).
The time it takes for it to "die" varies from seconds to minutes to hours. But it's become unreliable and had to buy a new phone.
I thought about replacing the screen, but it costs as much as a new phone here in Brazil.
What I'm thinking is maybe there's some cable or something I could access on the screen to inhibit this behaviour.
Can anyone help me out with insights?
Cheers,
Uriel
{
"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"
}
Try in safe mode.
Clear system cache.
Try a hard reboot.
Any uncased drops or water exposure?
Just tried safe mode and the screen started all messed up, with elements that should be organised scattered all over it.
Now... I'm soft rebooting it and it goes straight to a dark screen after showing the Samsung logo.
I was going to try clearing the cache next, but now I need to get access back to the system.
I've done a hard reboot to no avail.
It was exposed to water years ago, which resulted on a screen issue that was fixed by Samsung by replacing it.
Ok. I got safe mode successfully activated now. I'll give it time but I don't feel too optimistic about it.
urieljabes said:
Just tried safe mode and the screen started all messed up, with elements that should be organised scattered all over it.
Now... I'm soft rebooting it and it goes straight to a dark screen after showing the Samsung logo.
I was going to try clearing the cache next, but now I need to get access back to the system.
I've done a hard reboot to no avail.
It was exposed to water years ago, which resulted on a screen issue that was fixed by Samsung by replacing it.
Click to expand...
Click to collapse
May have water damaged ribbon cable contacts, or water damage on the mobo is now showing up; corrosion never sleeps. Maybe another display failure. Maybe a loose cable; carefully inspect all display cables on both ends and their sockets. A failed ribbon cable.
Finally a corrupted rom or user data partition.
These phones are relatively inexpensive now, even new ones can still be had. The N10+ be an upgrade if you like it. If repair doesn't work you have other options.
The newer Samsung's suck. This generation of Notes was the zenith for Samsung and the Note... in my opinion. I have two N10+'s and they run like bats out of hell. Solid, well built, work horses that just keep running. This one in my hand has over 8k hours on it, looks, feels and runs like it's new with one battery replacement. Zero display flaws, current load is over 2 yo, still fast and stable with minimal maintenance. That's what these phones are capable of.
urieljabes said:
Ok. I got safe mode successfully activated now. I'll give it time but I don't feel too optimistic about it.
Click to expand...
Click to collapse
Never know, could be a 3rd party app.
So, this happened. And it rebooted right after I stopped recording.
Yeah looks like the display but you won't know what it is without opening it up.
Don't think a factory reset or reflash will help... I could be wrong.
blackhawk said:
Yeah looks like the display but you won't know what it is without opening it up.
Don't think a factory reset or reflash will help... I could be wrong.
Click to expand...
Click to collapse
Yep. I'm pretty sure it's a hardware issue.
I don't know how to get access to the other end of the ribbons that go into the screen, though. I'll see what I can do.
Cheers!
urieljabes said:
Yep. I'm pretty sure it's a hardware issue.
I don't know how to get access to the other end of the ribbons that go into the screen, though. I'll see what I can do.
Cheers!
Click to expand...
Click to collapse
Watch some tear down vids. Have the right tools and take your time. With used ones going for a couple hundred that's another option.
I'm surprised how well my N10+ has held up, it's always cased. Water exposure is a killer. Even if it's IP68 rated, keep it away from water, especially salt water.
I hope is the backlight issue on the logic board