I welcome. I have the very untypical problem.
It all started with it around the phone started showing that the battery is unloaded, in spite of it around was loaded up. I thought cool it apparently a battery fell down. I bought new and unfortunately the same. Since the battery almost on max is loaded up the rally is loading it for moments and then loading is turning off. However an indicator of loading up on the nought and an announcement of the weak battery are demonstrating the system and it is disconnecting. I thought ok I will make hard reset and most probably he will help, however it turned out around not. Yeah rally loaded WM6 together with new ROM and unfortunately the same old story. I will still add around after this moment when is loading and an orange diode is shining and the indicator is showing the battery around loading is when he is finishing an indicator is appearing around empty battery and with stamp 'x'.
I hope around somebody here will help me. And perhaps somebody knows where in the register it is possible to change placing so that the system doesn't download details about loading the battery up and he wasn't mutually exclusive
Say what?
Can you please ask someone to translate so we can at least understand what your problem is?
ok I write it with my words.
When I switch on my phone battery indicator in main screen shows zero and sign '!' and the telephone switch off itself.
When I put usb cable or telephone battery charger and switch on my phone the phone charging about 10-20 seconds and after that battery indicator shows empty battery and sign 'x'. The phone still work but the indicator in Settings/Power Managment/Main Battery is completely empty.
I have new battery so battery is ok. I made hard reset and changed software from wm5 to wm 6.1 and the battery still isn't charging.
I hope that it is undertanding now.
Has the battery indicator ever worked while you've owned the phone, or is this something that has happened since upgrading your ROM? Having said that, this sounds more like a hardware issue to me. Try taking the battery out and cleaning the pins on the phone. If you've tried different ROM's, I don't believe it's a software issue and after a quick search of the forum, I haven't found anybody with a similar issue, which I would expect to if it were software related
The battery indicator worked normally and one day it stopped working. I upgraded ROM becouse i thought that it help.
I have second question. Whether it is possible to change the register this way so that the starting system doesn't read the level of battery charge out.
I have the same problem. Did you solve it?
Hi,
I've been experiencing some 'overnight' problems with the HTC Touch Pro lately.
The Pro is switched on for like 24/7 and works fine.
The thing is that it now and then happens that in the morning (so after a night standby time) the Touch Pro is all messed up.
Things that I have seen now:
- Device is turned off completely and needs to be turned on again (like the battery is down, but it's NOT).
- Device seems to have had a soft reset, since it shows the 'ENTER PIN' screen when I switch it on.
- TouchFLO 3D is all scrambled (see attached pictures for examples)
I think (read: hope) that it's all software and that it'll be fixed by a future ROM upgrade, since I've never had such problems with the Touch Diamond before. It's quite frustrating since the first two problems cause the fact that the phone is offline.
Do the problems sound familiar to you? I didn't find other topics concerning my experiences...
I think it may help if people also listed what apps they have installed. Up until last night, i had not had any issues with the device overnight. However after installing battery status last night, this morning the device had soft reset in the night. This is the first time in 3weeks.
The battery indicator is another issue which i think most people have. The indicator seems to get stuck and then when it updates it looks like a lot of battery has been used in a small amount of time. FOr instance my battery was reading 100% for over 4 hours then suddenly jumped to 95%. Also when charging i have had the TP stop charging at 87% and looking at the current level - only 80mA was being drawn, indicating that the battery was not charging. A soft reset later, corrected this. I am just wondering whether this is what is causing the soft resets in the night - ie the device detects that it has been charging for a long time with no battery level change and therefore resets. Just a hunch..........
- Device is turned off completely and needs to be turned on again (like the battery is down, but it's NOT).
I've had this a couple of times but hitting the power button doesnt work, I have to use the soft reset to get the phone back.
- Device seems to have had a soft reset, since it shows the 'ENTER PIN' screen when I switch it on.
Had the same thing a couple of times too.
- TouchFLO 3D is all scrambled (see attached pictures for examples)
Again, had this a few times
Not had TF3D scrambled, but had the other two. I'm pretty sure it has happened to me only when charging (other people report similar problems resuming from standby when charging). Perhaps, like me, you mainly charge the device at night?
I'm currently running with TF3D off (Settings, Today, Items, un-tick TouchFLO3D, tick some standard today items instead), and I haven't seen this problem since.
Cheers,
Graham.
hmmm...I'm very curious how this is coming...
Maby it are the installed programs that doesn't work correctly..
I'm curious if ya let the phone 'standard' so without installing all kinds of programs if the phone still has these problems.
Hello,
I bought a Lenovo S860 phone some time ago and I have several questions on how to get rid of some annoyances.
The phone has 2GB RAM, and Build Number = S860_ROW_S402_141108, Android v4.4.2
(I know there are some official updates, but I rooted the phone after I bought it, and I don't have enough free time nor patience to invest in a backup + unroot + update install + re-root + restore backup).
So here are my questions:
1. Every time I connect to WiFi or Data Connection, in the Apps section of the settings, under "Running" and "Cached Processes" there are always some which I don't use/want to be active. For example, google play services, hangouts etc. I always have to manually stop them but sometimes they get activated again even when there's no internet connection. So, is there any way to force the OS to disable caching of certain apps?
2. Sometimes the data connection on my first SIM card does not activate. I need to activate it for the second SIM, then for the first again. Known issue? Solvable?
3. Sometimes the signal for both of my SIM cards appears cut off (there's a small red X on both of the top right icons). Only way to fix it is to restart my phone (which takes forever), and the biggest problem is that it happens out of the blue (nothing else changes too, I keep the phone in the same place and suddenly I can't call anyone nor receive anything). Any ideas on what might be the problem?
4. After recharging the phone to 100% (and doing the calibration at the same time), the battery seems to drain a lot faster until I restart the phone. Another related issue (to recharging) is that the battery percent(%) is not always accurate. It happened many times that from 60-70% it got to 15% suddenly and started to give me warnings. Is there any way to make this batter sensor work properly?
5. How to speed up the time in which the GPS finds my current location? If I'm standing in one spot it takes even 5-6 minutes sometimes. After I start driving the car, it usually converges after 2-3 minutes. Other phones with the same Android do it in under 30 seconds (so I guess the OS is not really to blame).
6. How can I take a screenshot with this phone? I've tried like 5-6 apps and key combinations (like Power+VolumeDown) but nothing is working.
7. Is there any way to have the "flashlight" led open even when I lock the phone(i.e. Power button)? Again I've tried some flashlight apps but I have to keep the phone unlocked all the time or the led shuts off. I'm using a drawing pattern unlock with my phone.
8. There were some threads on these forums (but I can't find them anymore!) about Android 5.0 on Lenovo S860. Did it come out yet? or, at least, are there any stable 3rd-party versions of it?
9. Is there any custom OS that works well with Lenovo S860? (I'm thinking Cyanogen)
Thank you
Can anyone help with any of these questions?
I have an LeTV Max (x900), which is a Chinese made android phone. Quite high spec for its time. Anyway, it was flashed with an italian rooted ROM, can't remember exactly now as near 2 years ago.
Current problem is that: phone does not detect any wifi. When pressing "scan". nothing happens, not even any error message. Also, using the phone as a mobile hotspot no longer works.
Circumstances leading up to problem: the phone experienced excessive battery drain, it was quite warm and charging took nearly 10x as long. Eventually, the phone crashed entirely, and the little penguin logo came up on screen frozen. Had to hold power button for 20 secs to turn off. I thought it was battery suddenly dying (as had some trouble charging when low battery), but battery now suddenly seems fine again.
What have I tried: random wifi apps on play store, deleting / restoring hosts file (don't know if that makes difference).
Is this likely to be a software or hardware problem? A full reset is obviously the last option which I don't want to do unless I'm sure it's not hardware. Any definitive way to make sure? Thanks
G'day,
I've had some odd issues with two consecutive Xiaomi phones, and I'm hoping someone here can shed some light on it for me.
With both my Mi Note 2, and now my current Mi Mix 3, after less than a year of owning each one (respectively), out of nowhere, the battery life drops through the floor, the phone gets really hot, and most oddly, I got wicked battery drop while the phone is off (e.g. I turned the phone completely off at 77%, and about an hour later, I turn the phone back on and it's at 43%).
On both phones, I've tried a factory reset, but it didn't work. It was, for all intents and purposes, fecked. At the moment, I'm waiting for the 15 day countdown for my Mi Mix 3 bootloader to be unlocked so I can try flashing the EU MiUI ROM and see if that helps, but that's still a hell of a long time to wait with a phone that idles at 50+° C and has a battery life of about 3 hours with minimal SoT.
I've installed BetterBatteryStats (using ADB to provide permissions), CPU-Z, CPU Monitor and Ampere to see if I could get some more information. I found a few things:
1. Somehow, with mobile data and WiFi enabled, the system was drawing SO MUCH power (reported by Ampere) that it literally wouldn't charge while plugged into a 2A wall port. It was drawing like 1300mA when it wasn't plugged in, and when it was, it was STILL drawing about 130mA, meaning no matter what, while the phone was on, I was losing battery.
2. BBS reported the biggest battery killer was under the 'Alarms' tab, caused by Android, which were "Intent: *job.delay*" and "Intent: *job.deadline*". I have literally no idea what these are, what's causing them, or how to stop it triggering.
3. I've done a full factory reset. The first hint that something was wrong was when I noticed that the phone wasn't charging when it was plugged in and turned on. I did the full factory reset, didn't help.
I'm currently running Global MiUI 11.0.4.0, Android 9.
Does anyone have any ideas? I haven't manually updated anything, I'm not particularly rough with the phone, but for two phones in a row, this has come straight out of nowhere. It's a shame, because the Mi Mix 3 has spoiled me with it's 100% screen real estate (no hole-punch, no teardrop for front camera), but I think my next phone is gonna go with something else.
Cheers.
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Overloke said:
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Click to expand...
Click to collapse
I think it's an issue with your network operator
XDRdaniel said:
I think it's an issue with your network operator
Click to expand...
Click to collapse
Any ideas as to how I'd further troubleshoot? I've gone into *#*#4636#*#* and changed the sort of signal it looks for, but it doesn't appear to have fixed anything.
In case anyone is interested, I've attached on of my Bugreports (from running adb bugreport), which can be viewed through Google Battery Historian.
I'm not saying there's a cash prize for anyone who can tell me what is happening and why, but I'm also not saying that there isn't.
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
--
This looks to me like an hardware issue more than anything, what is the idle state of the cpu?
Overloke said:
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
Click to expand...
Click to collapse
Same problem. Any solution?