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
Related
I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?
Try leaving it charging for 6+ hours. Make sure it's plugged in all the way on both ends of the usb cable.
mtcstle said:
I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?
Click to expand...
Click to collapse
can you enter recovery or download mode?.. if not then you should be worried.......
Sent from my GT-N8000 using Tapatalk HD
mtcstle said:
I've wasted an hour at the Samsung website. When the chat turned out to be broken the send button didn't,t work, I tried email. After answering all the same questions, model etc, the drop down for model wouldn't work. It's a required field so again, i'm stuck. Does anyone know how to reach them?
i received a galaxy note 10.1 16 gig wi-fi only for Christmas. it was terrific until yesterday morning. I took it from my padded brief case, pressed the start button and nothing happpened. I assumed I'd left it on overnight and rrun the battery down. I just put it away until i went home to charge it. I left it on the charger for a couple of hours. When i again pressed the start buttton, still nothiing. What do i do next?
Click to expand...
Click to collapse
Call them. Very easy to reach by phone.
toenail_flicker said:
Call them. Very easy to reach by phone.
Click to expand...
Click to collapse
Does anyone know a phone number? That's one thing that's not on the website.
To answer the previous question, no it won't boot into download or Recovery.
I'll try the six hour charge, but I'm not hopeful.
Stay tuned for more on ...
mtcstle said:
Does anyone know a phone number? That's one thing that's not on the website.
To answer the previous question, no it won't boot into download or Recovery.
I'll try the six hour charge, but I'm not hopeful.
Stay tuned for more on ...
Click to expand...
Click to collapse
I found 1-800-SAMSUNG somewhere. It's seven digits I thought so, what the heck. Well a very nice woman talked me through all the trouble shooting steps I'd already tried. But, then she gave me an RMA and emailed me a shipping label. So far so good then. More to follow.
Before you write it off as dead, may I make a suggestion. Keep a finger on the touch screen while pessing the power button. This solution works for me when I've experienced the "sleep of death" after upgrading my GN 8013 to JB. Holding down the power button on mine didn't do anything. I found the solution I mentioned when I began googling in a panic. After removing one offending app, this awful sleep mode that resembles a dead device hasn't occurred again. Maybe you have an app that's triggered this. Good luck.
mke1973 said:
Before you write it off as dead, may I make a suggestion. Keep a finger on the touch screen while pessing the power button. This solution works for me when I've experienced the "sleep of death" after upgrading my GN 8013 to JB. Holding down the power button on mine didn't do anything. I found the solution I mentioned when I began googling in a panic. After removing one offending app, this awful sleep mode that resembles a dead device hasn't occurred again. Maybe you have an app that's triggered this. Good luck.
Click to expand...
Click to collapse
What was the offending app?
If all else fails, try the old fashioned way
{
"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"
}
Riki1kenobi said:
What was the offending app?
Click to expand...
Click to collapse
It was Sipdroid. (Knock on wood) deleting it has stopped my note from going into the sleep of death. Fortunately, the voip app csipsimple is very stable on JB 4.1.2 and has no audio or registreation issues so I've still got voip on my note.
Hi,
My wifi and bt modules didn't work for the past two months, and after searching trough the Q&A forums, I came to the conclusion that I have to change the ribbon cable, perhaps thats the problem.
So, I've ordered the panel, and it arrived yesterday, it was this piece:
{
"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"
}
I've swapped it with the old panel, phone fired up nicely, I even saw the BT connections logo appear on the status bar. Yay.
But.
The touch screen doesn't register my touches anywhere on the screen. I've checked the connections, everything connects good.
I've dismissed the idea of a faulty digitizer, since before the ribbon cable/panel switch, everything was working as it's supposed to be.
I'm fully out of ideas, so I'm doing these steps as a last resort: (I'm currently at the third step)
1. Discharge the phone all the way (until it shuts down).
2. Remove the battery and press the power button (as if you were trying to turn the phone on).
3. Leave the phone without the battery overnight (or for at least an hour).
4. Put the battery back and charge the phone without touching the screen.
Make sure you don't touch the screen whenever you're charging, until the issue disappears. This should happen within 2-3 days. If the problem persists, you ether did something wrong, or (as explained above) you have a different issue... Most common related problem is a faulty digitizer.
(source: http://forum.xda-developers.com/showthread.php?t=1239238)
Click to expand...
Click to collapse
If this fails, the last option I see could be this: http://forum.xda-developers.com/showthread.php?t=1360638 (thank god I have a backup)
Please note, that I've tried the responsiveness of the screen with both with and without the battery cover installed, so I've dismissed the little silver pin as the issue. And as I said the touch screen was fully working before the cable/ribbon swap. Touch doesn't even work in recovery.
So (after a long intro), my question would be, does anyone have any ideas, what could be wrong? TBH, I don't want to buy a new digitizer (even if thats the issue), because I don't want to spend any more $ on this phone (bought a new battery, battery door, some misc stuff)
PS:
I haven't changed anything software/firmware wise during/before/after the swap.
Current setup is:
ROM: latest android1234567 CM11
Kernel: Sultans r53, slight undervolt, slight underclock
Recovery: TWRP
S-OFF
Thanks in advance!
borgwarrior said:
Hi,
My wifi and bt modules didn't work for the past two months, and after searching trough the Q&A forums, I came to the conclusion that I have to change the ribbon cable, perhaps thats the problem.
So, I've ordered the panel, and it arrived yesterday, it was this piece:
I've swapped it with the old panel, phone fired up nicely, I even saw the BT connections logo appear on the status bar. Yay.
But.
The touch screen doesn't register my touches anywhere on the screen. I've checked the connections, everything connects good.
I've dismissed the idea of a faulty digitizer, since before the ribbon cable/panel switch, everything was working as it's supposed to be.
I'm fully out of ideas, so I'm doing these steps as a last resort: (I'm currently at the third step)
If this fails, the last option I see could be this: http://forum.xda-developers.com/showthread.php?t=1360638 (thank god I have a backup)
Please note, that I've tried the responsiveness of the screen with both with and without the battery cover installed, so I've dismissed the little silver pin as the issue. And as I said the touch screen was fully working before the cable/ribbon swap. Touch doesn't even work in recovery.
So (after a long intro), my question would be, does anyone have any ideas, what could be wrong? TBH, I don't want to buy a new digitizer (even if thats the issue), because I don't want to spend any more $ on this phone (bought a new battery, battery door, some misc stuff)
PS:
I haven't changed anything software/firmware wise during/before/after the swap.
Current setup is:
ROM: latest android1234567 CM11
Kernel: Sultans r53, slight undervolt, slight underclock
Recovery: TWRP
S-OFF
Thanks in advance!
Click to expand...
Click to collapse
I've the same problem also replaced the cable/ribbon. I've tried everything software related.
I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
{
"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.
- JasonVaritekMVP
Only other detail I have to add is that the charge screen works correctly after a flash-all. It is the process of installing twrp and then Magisk that seems to be borking the charge screen.
JasonVaritekMVP said:
I previously had an issue with this which was solved by re-flashing, unfortunately this isn't helping this time.
So as far as I can tell things work properly with the following exception.
When I power off the phone and leave it in to charge I get stuck on the black and white lighting battery screen. The screen stays on indefinitely. The phone will not power on except for a soft reset which then boots the phone.
For clarity this is what the phone looks like ... it just never turns the screen off.
Thanks.
- JasonVaritekMVP
Click to expand...
Click to collapse
Did you ever find a fix for this? My Pixel 2 XL does it as well!
MRL3GS said:
Did you ever find a fix for this? My Pixel 2 XL does it as well!
Click to expand...
Click to collapse
So this issue popped up for me when Magisk v17.0 came out and v17.1 didn't seem to fix it. Re-flashing did solve the problem but every time I tried to re-root the issue came back. Something about the latest Magisk and my flashing was causing the problem. I tried going back to earlier working versions of Magisk such as 16 and 16.5 but none of them seemed to work, whatever it was it stuck.
I finally ended up flashing the latest Pie along with the latest Magisk and that together allowed me to flash, root and solve the problem. I have not attempted to go back to Oreo.
Hope this helps.
- JasonVaritekMVP
this just happened to me. how do i fix this? I just want the thing to power up. I just got done using it. picked up phone and it was powered off.....
edit: phew. i panicked when i saw this. I just held the power button and it shut off. turned it back on and it booted up....had 2% battery. i guess it was just a low battery this time.
have the same issue too. Only happens when the phone dies after running out of juice. Hard reset reboot and boots up right back up afterwards. Also rooted with magisk 17.1
hard reset? like you lose everything? that sucks. im on 17.3 magisk.
psycho_maniac said:
hard reset? like you lose everything? that sucks. im on 17.3 magisk.
Click to expand...
Click to collapse
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.
eneka said:
whoops, i meant hard reboot. Pressed and held the power button for 5+ seconds and it booted right back up.
Click to expand...
Click to collapse
yup. thats what i did too. mine was due to low battery
Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!
fastracer said:
Anyone figure this problem out? I've had this problem for a while now. It was doing this a few months ago then I reflashed magisk and it went away. I did a monthly update a month later and it came back and I've tried a factory reset...reflashing etc.. Nothing helps. It only happens if the phone dies or you power it off. I'm not using TWRP... It's a magisk manager direct install. Thanks!
Click to expand...
Click to collapse
I've also had this issue since I bought the phone 2nd hand last June. I don't recall if it happen before rooting or not. The only pattern(?) I have noticed is that when I let the phone die completely, theres a chance when I plug it into the charger, it might get stuck on the screen as OP showed. However, as others noted, I think holding down the power button shuts the phone completely down again. Occasionally either I'm doing something wrong or the phone doesn't register the button presses all the time. In past I also tried holding the power button and volume down at the same time but I'm assuming the phone picked it up as me just holding the power button down or maybe that combo also works.
Hi all, new member here, so apologies for any mistakes I make.
A friend of mine has passed on to me his Nexus 5 (2013), stating that there were a number of issues he was having with it. After using the device myself for a couple days I can confirm that the following issues are present:
- The screen will sporadically freeze and become unresponsive to any touch input, and the only way to solve this is to lock the device and unlock it again. The time between instances of this is random.
- The screen will occasionally cut to black, but the display is still active (i.e. you can only see the backlight). This happens for a number of seconds before returning to normal on it's own.
- The camera is completely unresponsive/broken (See picture 1 below). Possible loose connection?
- The WiFi is stuck on 'turning WiFi on' in the settings, and stuck at searching for networks in the notification bar(See pictures 2 & 3 below).
The device was dropped at some point in the past, but the damage is typical (See picture 4 below) and I see no immediate reason why this damage should cause these issues in particular, but I'm by no means an expert, hence why I'm here. =) The device has only been dropped one time, and has not suffered any other damage, including water damage.
My first instinct was to boot into recovery mode (where it should be noted that the freezing and display issues I mentioned above didn't occur, leading me to believe it is more of a software issue?) and clear the cache partition, which did not solve the issue, and neither did a full factory reset.
So, with all that being said, what would you guys suggest? Should I try flashing the factory image to see if that works? Rooting? Flashing a custom ROM? Any suggestions would be most appreciated!
If you require any additional information let me know and I'll happily oblige.
Thanks in advance guys!
Picture 1
{
"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"
}
Picture 2
Picture 3
Picture 4
It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.
audit13 said:
It could be the motherboard or screen. You won't know for sure until you replace one or the other.
The wifi chips do fail on the Nexus 5. I a motherboard that also tries to turn on wifi but turns itself off after a few minutes.
Click to expand...
Click to collapse
My first thought was that it was a hardware issue to begin with, but due to the sporadic nature of the issues (excluding the camera obviously), and the fact that it didn't happen whilst in the recovery menu, I'm more inclined to believe it to be a software issue? I could be wrong of course, I'm just wondering if it's worth flashing the factory image on to see if that solves the issue?
You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.
audit13 said:
You may as well flash the stock image and see what happens.
The lines showing on the screen does not look like a software issue to me.
Click to expand...
Click to collapse
Those lines are what appear when I open the camera, they're not there otherwise. THAT is almost definitely a hardware issue, granted.
I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.
xsacter said:
I have a Nexus 5 that has the wifi issue. I flashed a bunch of different Android versions (like Android 7 and 6.0) which none have worked. At one point I opened my Nexus 5 and left it like that for about a month, then afterwards I assembled it back together and the wifi worked for a little bit and then went back to its broken state. I've concluded that it is a hardware issue since data was working fine and was the only way I could get internet on my phone.
Click to expand...
Click to collapse
Hmm. I have to be be honest after looking online it appears that wifi failure is a somewhat common issue on the Nexus 5 devices. It has to be a hardware based problem it would seem.
Thanks for letting me know, I appreciate your input. =)
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.