My Nexus 5 has burned in a few times over the past year, which is very unusual since I **never** leave it on when not in use (30 second dim time), but today I finally noticed the trend. When I charge the phone with certain chargers, they cause the screen to become fuzzy and distorted, with a colored tinge (what I *thought* was a burn-in). This is 100% reproducible. I've used a few chargers in America, 1 of which resulted in this, so it is not a problem native to Australia. Here in Australia, I use the following Samsung charger, which works perfectly: Model: EP-TA10HWE Input: 100-240V~ 50-60Hz 0.35A OUTPUT: 5.3V === 2.0A S/N: SE2FB04YS/B-E The bad one I used today, which triggered the problem again was also from Samsung: Model: ETA0U10HWE Input: 100-240V~ 50-60Hz 0.15A OUTPUT: 5.0V === 0.7A S/N: DK3G904HS/7-E N363 Here are the symptoms: 1. Plug the phone in, as per normal, with the screen off. Location, WiFi, Bluetooth, etc don't matter. (2 hours will do this - a full charge is not needed to replicate it.) 2. The screen gets a blue tinge, and duller colors. This worsens the longer it is charged. The tinge is noticeably less present at the edges of the screen. 3. Once unplugged, the screen will still get worse over time. This is especially true when using it - an hour of activity on the phone will result in.... 4. **Very** dulled colors, barely distinguishable, a fuzzy screen, and shadow images left wherever objects move. Vertical lines trail behind in these shadow images. Screen is completely white when viewing it from a 45 degree angle. Image album of the screen distortion as the phone charges: Facts and other info: - At the top of the screen, there are small parts which are somewhat immune to the blurring and fading. I have scribbled the bits out in this image: https://goo.gl/M7lbwJ - There is no image burned into the screen. It is only a blurring, fading, colored tinge (the color has been green, blue and purple so far), and shadow image (very noticeable dragging a white box across a black background. Dragging the box left means vertical black lines on the right side of the box). - It is impossible to see anything except white when the screen is viewed from a 45 degree angle. - I once cracked the screen (not badly), and had it replaced. It was at a relatively cheap store ($150 AUD), not by the manufacturer. I can't remember if the burn ever happened before the replaced screen. - This has happened about 6 times. Each time I solved it by leaving it on with the "Screen Burn-in Tool" overnight, on maximum brightness. It seems to take about 12 hours to fix it fully. - The phone behaves as normal once recovered - no one could tell the difference between my phone and another. Battery, brightness, etc, are all normal. - It always charges at the expected rate in all chargers. Nothing remarkable about the power graphs, or power usage of apps. The "bad" chargers work normally for other phones. - I've always had the phone in a case, and only ever dropped it that once. I take care of my stuff. ### UPDATE: It happened with a USB cable plugged into a laptop today. What's weird is that I've used this cable with this laptop about a dozen times before (it's only a few weeks old), but it hasn't triggered the effect in it before. There could be some kind of connection to heavily using the phone while it's charging, or right before charging it, as several of the times that this has triggered, I've been recently using my phone heavily (thus why it needed charging). For example, the other times I charged my phone (using the same cable and laptop), I'd only been topping it up, or charging it at the end of the day. ### UPDATE 2: Today I got a brand new Samsung Galaxy S5 for use at work. It came with a brand new charger and brand new cable too. Last night I plugged the new charger into the same wall socket as my old one usually goes in (it was in my luggage), with the new cable, and charged my Nexus 5. Today, I noticed the tint was coming back very slightly, but didn't realize why. When I charged my phone this evening, and it was 100% blurry and tinted, I realized. Everything about the actual charger is identical, except the S/N (Serial Number), and the country of manufacturing. Comparison: If we assume that the chargers are the same (it was plugged into the same wall socket), then that must mean that the cable is what's doing it to the phone, since the cables are very different. The new one has the text: E321011 ЯJ AWM STYLE 21104 80°C 30V VW-1 23AWG*2C LUXSHARE-ICT NON-PVC The old one has the text: E102671-0 ЯJ AWM 21445 80°C 30V VW-1 23AWG*2C 30AWG*2C KAYANG HX NT NON-PVC NON-P ### UPDATE 3: Using my good charger base with the new cable didn't cause any problems. Using my new charger base with the good cable __________. (testing now)

just bought an S10+ and am buying a Tech21 case for it. I'm also looking at buying a right-angle charging cord (this is my first phone with USB-C port). I can't determine what the depth of the port cutout is from specs on Tech21's website. Here's a screenshot of the charging cable requirement: I realize this is extremely specific, but I'd like to know before I buy the cable that it would even work with that case. Hopefully a kind soul has an answer. 😊 Thankyou in advance.

Whenever I'm connecting my Samsung Galaxy A40 running Android 9.0 to a laptop or PC, I'm getting an annoying prompt to allow data transfer, and the following setting which I had set to "Charging phone only" gets reset to "Transferring files": However, I only want to charge the phone and absolutely never allow data transfer for security reasons as I frequently have to connect my phone to public or workplace PCs for charging. The service which throws the notification/prompt is called *Android System* and the icon looks a bit like this (only with filled font): I activated developer options and explicitly configured the USB connection settings to **not** allow data transfer. Why does *Android System* keep changing my settings and prompting for data transfer? Is this normal behaviour? Is there a way to regain control without having to root the device?

Nearly three years ago I have asked [this question](https://android.stackexchange.com/q/69477/20449) . It brought certain attention, but no answer. Of course there is no change in Nexus behavior and device discharges its battery up to 30-50 times faster when completely turned of than when it is turned on, but not used at all. To my complete surprise, after these nearly three years I have notice the very same behavior in many more mobile devices, irrespective of device type, manufacturer or even operating system. Recently I noticed this in: - Sony Xperia E, - Apple iPad Mini (first edition), - Microsoft Lumia 640 and 650. Is there any consistent theory or answer, why it is happening? Why device drains battery at all, when it is (should be) completely turned off? And why the discharge rate is so enormously1 high? I'm looking for an answer at least partially proven or grounded on some verifiable facts. Spy theories -- that it is due to fact that completely turned off device sends a lot of information to Google / Facebook / Apple / Microsoft / US Government -- are quite out of scope of this question. 1I'd say that even absurdly high, given the fact that device completely turned off can't stand more than 24 hours while turned on, but unused at all (lying on shelf) can last up to a week or at least a few days.

Recently, something has happened to my phone's temperature sensor. It's showing ridiculously high values for the temperature (over 100 degrees), even though it's very cold. This has caused my phone to refuse fast charging, and it charges very, very slowly. (~7 hours to charge) Is there anyway I could turn off a sensor or fake its value so that my phone charging returns to normal? Or is there anyway to force the phone to ignore the thermal limits during charging? (I know it's dangerous but I have no choice) Deleting the thermal engine file doesn't fix the issue. P.S: Android 10 | Qualcomm chipset | Rooted + Xposed

Samsung Galaxy S21 FE powering a portable external display over USB-C. The external display also has its own power connection to the wall via USB-C. Whenever the display isn't receiving power from the wall, it will draw power from the phone. Is there a way to prevent it from drawing power from the phone when the phone's display is off or at all?

My phone (Xiaomi Redmi Note 10, 2 years usage, the warranty just passed) suddenly shut down at 50% battery at normal usage when I clicked an app to open it and it will not boot up. I want to fix it myself due to privacy reasons, as I don't trust payed services and have experience in opening phones, but only to replace the screens. I tried to turn it on on safe mode - unsuccessfully. I tried to charge it but it didn't even pop the animation of charging. Nonetheless I left it for couple hours to charge and tried again - still not booting up. The USB connector is clean, dust-free and not loose. I tried different chargers. It is not detected by the computer when plugged in (checked in the Device Manager, Windows). I also called the phone from another phone to check if it's the screen's issue - I got "user out of service" message. I tried to troubleshoot the connector and it was a surprise to me: I own a MakerHawk UM34C USB 3.0 tester and tried it on my working phone - readings were reasonable, approx. 13W of charging power. I tried it on bunch of other devices, with correct readings. I also tested a device with physical on/off switch and the device showed voltage of 5V when turned off (charger voltage) and voltage + amperage when turned on (with propper readings). **So when I plugged it in the phone and if the connector were bad then I should have the same reading as in the device with off switch. But what I got was device (tester) restarting constantly without even showing me the data, as if the connection was ok but the phone "intentionally" disconnected it repeatedly.** This means that the phone recognises the charger and disconnects it immediately. What does it imply? Is it the software issue? I tried to open it like on the vid, using same tools but the glue seems to be too strong and it won't open so I can't check the battery itself without damaging the phone: https://www.youtube.com/watch?v=PhC37fp4o7Y **How should I troubleshoot the issue?** These threads provided no help: https://android.stackexchange.com/questions/171472/galaxy-s4-not-booting-up https://android.stackexchange.com/questions/247451/poco-m3-pro-5g-not-booting-up-after-unexpected-shutdown-it-does-not-charge-as-w

I am interested in understanding the charging capabilities of the Google Pixel 9a. Specifically, I would like to know the maximum wattage it supports for both wired and wireless charging.

When watching video in fullscreen in landscape and plugging in my charger, the video changes to portrait. When unplugging my charger it goes back to landscape again. Why is this happening? I'm using a Zenfone 9 (Android 14) and have tested with Firefox (watch YouTube fullscreen) and DRTV app watching in fullscreen with same results. I remember having encountered the same issue on my last phone as well, but haven't tested yet (Sony XZ2C, Android 10). (At first I thought it was an intermitten issue with Youtube or Firefox, but then I figured out it was related to when the phone was charging and reproduceable with other apps.)

I'm trying to solve a problem that is affecting a **Moto G 2014 XT1069** device. What has happened is that the device did shutdown, then when trying to power it up again, it stayed stuck on the Motorola logo for some time. Another person trying to help, said that it was needed to format the cellphone and rebooted into recovery mode. The point is that when trying to factory reset an error appeared. This person then said that the device was bricked and needed to do something to correct it. Then using fastboot through a computer, I don't know what she did but the situation got somehow worse. The first thing is that she unlocked the bootloader. But after all the procedure what happens is that when the device powered up, it just got stuck in a screen with a message **WARNING BOOTLOADER UNLOCKED** and it *doesn't progress any further*. On that same screen it is possible, by pressing **PWR** + **VOL DWN** to access the bootloader, but even if we select "Normal Powerup" or "Recovery", the device just gets back to the screen **WARNING BOOTLOADER UNLOCKED** and nothing more happens. Furthermore, it seems that the battery became somehow "mad". After a *quite long* time interval charging, the device got to 29% of battery and after just a few minutes trying to correct all this mess, the battery got to 6%. I don't know what they did and how all of this happened. How can I fix this mess? How can I make the cellphone boot and make everything right again? If possible I want to avoid flashing the factory image for the reason that I don't have access to the image from the official source and I feel quite uneasy to get from one untrusted source, since it might compromise confidential data. What can I do to solve this? I believe there has to be a way to correct all of this.

I have a Google pixel-2. I like to use a Bluetooth keyboard and wired mouse via the USB-C-OTG canoe that came with the phone... But then I can't charge the phone. I wanted to buy something... To let me use the USB OTG and charge the phone at the same time. **Can you use USB OTG and charge at the same time?** I was thinking get a gadget that does USB-C to USB-A and USB-C... Where the USB-C would be for charging and the USB-A would be for a hub for the quoted keyboard and mouse.

My phone is overheating a little bit so the charging speed is much lower than typical. If I place my phone in the fridge for a few seconds, The temperature that AccuBattery indicates is much lower but the charging speed remains slow. How can I view the temperature that is used to determine the charging speed of my phone?

I usually disconnect my cellphone from the charger some time after it's fully charged because I'm afraid the battery could lose capacity over time if I don't. However, I believe modern electronics should be able to handle this kind of scenario and automatically stop charging the battery once it's full. Does this apply to modern Android phones? Or do I need to continue disconnecting it all the time?

Device : Moto X Play ( Rooted, Stock, Android 6.0.1, msm8916 Board, XT1562) ## Why do I want to limit charging ? ( Let's leave out whether my reasons are valid or not and accept that I **want** to, if you disagree with my reasons) To improve the longevity of battery , I wish to limit charging when it reaches 90%, as explained here https://android.stackexchange.com/q/156526/131553 ## Is it possible? Yes, at least on my previous device Honor 6, as brought out here https://android.stackexchange.com/q/92413/131553 , with two different ways of doing it I have tried unsuccessfully to identify the file responsible in which changing values would limit charging ## I am looking for the system file responsible for stopping charging, with it's true path (without symlinks) (as I saw on on my previous device, locating the path of file was a big challenge after identifying it) ----------

I've seen multiple posts on Reddit from Pixel 8 Pro users, claiming that the December Feature Drop for Pixels enabled an 80% battery charge limit feature. The setting looks like this: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> Does the regular Pixel 8 not support this feature? My battery settings look like this: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">

By battery insertion I mean current flowing on the battery pins, **not** the micro USB port. **Description** The phone in question is a Samsung Galaxy Xcover 4, the **bootloader** is **unlocked**, and I have **root access**. Its intended purpose is as a kiosk device that will be sealed inside an external hard plastic enclosure. This means that the power button is unavailable for booting the phone. The phone is powered directly from the wall by means of a custom-made battery eliminator PCB, and I need the micro USB port for host mode UART communication, which means it will never be charged/powered via the micro USB port. **What has been attempted so far** As mentioned, the device is rooted, so I've tried modifying the BOOT partition image and flashing an updated one. The modifications I've been looking at pertains to the program /init in the root directory. and its associated /init.rc /init.samsungexynos7570.rc /... files. For example, I was able to make the phone boot upon receiving charge via the USB port by overwriting the contents of the file /system/bin/lpm with the script #!/system/bin/sh echo b > /proc/sysrq-trigger because /system/bin/lpm is referenced in a service specified in the charging section of /init.rc. I was also able to make it boot via USB port charging by removing the existing "on charge" triggers in the init.*.rc files, and simply adding on property:ro.bootmode=charger: trigger late-init For more details about what I did, see this link . But this is **not a solution for me** because I want to make it boot simply by powering the battery pins, not the micro USB port (which is preoccupied with being in host mode, so it definitely can't be charged). **Further thoughts** However, since modifying the /init.rc file changed its behaviour even while "off" (i.e. it now boots upon micro USB charging as opposed to not), this seems to tell me that the phone is never really completely off when "off", and that the /init program is constantly running as long as there is enough charge on the battery pins (please derail this thought train asap if this is completely wrong). Which would mean the kernel and the /init program should start automatically when there's sufficient charge on the battery pins. So my thinking was to simply add something along the lines of trigger late-init or start (where *my_service* for example could be the lpm script I mentioned above) in an early init trigger stage, so that it would boot simply by virtue of the /init program running. But so far I've had no luck. Does anyone know whether something like this would possible? Thanks for your time.

I have a Google Pixel 6a with the latest updates. When I charge it, a "Check charging accessory" notification appears. The cable and power supply are not going to be changing, and the phone charges perfectly fine and exactly as we need it to in its remote location. It's just the message is flat-out wrong for this use in this location. It's going to be unattended for weeks at a time, in a very remote monitoring site, with multiple redundant power sources feeding it. If we lost contact with it for 15 minutes, we would know and the message keeps getting in the way. The reason why it is immaterial and I am not seeking any advice on cables, adapters, reasons why, etc., is because I simply want it gone. I don't want to see the message again. Any advice on removing it is very welcome.

I have a Moto G phone. I'm using LineageOS. Yesterday I notice my phone went dead. When I press power button, a white light in the camera flashes three times, which I understand to be no battery. It did have enough battery though. When I connect the phone to charge (using PC), the 0% battery charging screen shows up. But it's stuck there at 0%. I can get to the boot menu (power button and volume down), which shows me "battery low", but when trying to boot recovery or any option, the phone restarts but is again stuck at low battery. My guess is that the battery is gone. Since it cannot be charged, the OS doesn't have the power to load anything. However, it should load when the phone is connected and "charging". Perhaps the problem is not the battery itself but the phone recognising that the battery **does have enough charge**. Is this possible? Anyway, any idea is more than welcome.

I got a Pixel 4 a couple of months ago (it had been stored for years but barely used). I then installed rooted LineageOS and Kali NetHunter apps with chroot (this didn't cause the issue I think). Just yesterday, it was working fine when I started messing around with the WiFi card firmware in nexmon. I am not sure if the issue was caused by that because I don't see how the WiFi chip would affect the battery. Today, the battery indicator won't go down when not charging or up when charging. Also, the issue isn't LineageOS because I shut it down and it still has the issue on the charging but not on screen.

I use a Samsung Galaxy S23 Ultra. Sometimes, Android lock screen says "super fast charging". What does that exactly mean? I.e., how fast much charging be to be called "super fast"?